[00:29] <lfaraone> kees: hey, did you have a chance to look at uploading the branch attached to bug 538471 to karmic-security?
[00:31] <crimsun> carstenh: fixed & uploaded, thanks.
[00:36] <arand> Is there an easy way to do the intent of "patch -R < 1.patch > 1_reverse.patch" ?
[00:37] <carstenh> crimsun: thanks for the quick fix :)
[01:26] <lfaraone> For GPL projects, all of the project source files do not need a GPL header and authorship information, do they? (http://dev.laptop.org/ticket/6891 doesn't make sense to me)
[01:26] <jdong> lfaraone: they do.
[01:27] <lfaraone> jdong: mk. a "this package is free software, you may..." in README isn't enough?
[01:28] <jdong> no
[01:28] <jdong> lfaraone: https://wiki.ubuntu.com/PackagingGuide/Complete#Copyright Information
[01:28] <jdong> For all files it must be clear under which license they fall. Source code files should usually have a short comment at the top which points out the license.
[01:51] <carstenh> jdong: this doesn't sound correct and your link does not justify your statement, nor does common sense
[01:51] <jdong> carstenh: what doesn't sound correct? that each source file should have a copyright header stating its license?
[01:52] <jdong> feel free to get someone else here to clarify that point, but that was always my understanding of what the archive administrators expect to see.
[01:52] <carstenh> jdong: well, should != must
[01:52] <jdong> carstenh: should as in I've had several packages rejected in my 3-4 years of packaging around here for that reason :)
[01:52] <jdong> so should \approx must.
[01:53] <carstenh> jdong: do you know an example (without looking it up, this wouldn't be woth the effort)?
[01:55] <jdong> carstenh: examples are hard to find in that archive rejections usually are handled by a private email from an archive admin, and the history is not recorded in LP
[01:56] <carstenh> jdong: i wanted more example for a rejected source than the rejection itself
[01:56] <carstenh> but only if you remember a name without looking it up
[01:56] <jdong> looking on REVU should give you plenty of examples
[01:57] <ScottK> crimsun: Why did you change the VCS stanzas in topgit?
[01:57] <carstenh> zcat (shell script) in bzip2 is a trivial example for a gpl source without gpl header
[01:59] <ScottK> There are pleanty of cases where the GPL header is missing.
[01:59] <ScottK> These are bugs and should be fixed.
[02:00] <ScottK> As long as the upstream intent for licensing is clear and well documented, then the lack of the header won't get a package rejected from the archive.
[02:00] <ScottK>  !rejected != bug free
[02:32] <crimsun> ScottK: pitti started me doing it some time ago
[02:32] <ScottK> crimsun: OK.   We had a discussion about it on #ubuntu-devel.  I hadn't seen it before.
[02:32] <ScottK> Seems like overkill to me for minor package changes.
[02:33] <ajmitch> apache2 is where I'd seen it before, packaging changes are a bit more in-depth there
[02:33] <ScottK> Makes more sense to me in that kind of context.
[02:33] <ScottK> In Kubuntu we replace the Debian ones with pointers to our own.
[02:34] <crimsun> ScottK: I'm happy to revert it, but I do it from force-of-habit these days.
[02:34] <ScottK> crimsun: No, it's fine.
[02:40] <ajmitch> ScottK: we don't need to subscribe -release for minor changes yet, do we?
[02:40] <ScottK> ajmitch: Not for bug fixes in Universe, no.
[02:40] <ajmitch> great, ~ubuntu-archive it is
[02:42] <ScottK> ajmitch: If it's an upload, you can just upload and it'll get reviewed in the queue.
[02:42] <ajmitch> it's a sync
[02:42] <ScottK> OK
[02:42] <ajmitch> and it's just to fix a FTBFS, so probably low priority
[02:43] <psusi> YES!@ got e2defrag working with extents
[02:44] <ScottK> ajmitch: No, we want those.
[02:44] <ScottK> (I hope you were being sarcastic)
[02:44] <ajmitch> ScottK: low compared to needing to get something fixed ASAP for release
[02:45] <ajmitch> A package that works but can't be rebuilt cleanly can probably be fixed in a SRU
[02:45] <ScottK> I think having a maintainable archive for LTS is very important.
[02:45] <ScottK> True.
[02:45] <ajmitch> & with only a few days left to get fixes in, you probably want to make the most of that time
[02:46] <ScottK> OTOH, the builders are sitting idle right now.
[02:46] <ajmitch> That's unusual, noone has uploaded gcc & OO.o today?
[02:46] <ScottK> Nope.
[02:46] <ScottK> gcc was yesterday.
[02:47]  * ajmitch shouldn't leave fixing stuff so late for 10.10
[02:48] <ScottK> Better late than never.
[02:48]  * micahg has a fix if a sponsor wants to upload :)
[02:48] <micahg> bug 562737
[02:49] <ScottK> ajmitch: ^^^ - If I upload it, I can't review and accept it.
[02:49]  * ajmitch spots java in the name & runs :)
[02:50] <ScottK> It'll be fun.
[02:50] <ajmitch> fetching now, it may take some time to testbuild
[02:50] <micahg> ajmitch: it's a one line change in rules :)
[02:50] <micahg> ajmitch: builds fast :)
[02:50] <ajmitch> but will probably require 100MB of packages to build it
[02:50]  * micahg doesn't recall
[02:51] <ajmitch> and worse, it requires xulrunner-1.9.2-dev just to run the clean target
[02:51]  * ajmitch hates packages that do stupid stuff in clean:
[02:51] <micahg> ajmitch: just trying to make sure it can build :), file a bug w/debian if you don't like that
[02:52]  * ajmitch is not on a fast connection at the moment
[02:53] <ajmitch> I'll have to leave it until later
[02:55] <micahg> ajmitch: k, no rush
[02:55] <ScottK> ajmitch: You'd have to move to fix that.
[02:56] <ajmitch> ScottK: DSL isn't too bad at home, as long as I fetch from a NZ mirror
[02:56] <ScottK> Good point.  I forgot about local mirrors
[02:56]  * ajmitch isn't at home right now, but will be in an hour or so
[03:01] <imbrandon> xulrunner for :clean
[03:01] <imbrandon> wow
[03:03] <ajmitch> imbrandon: it's more the use of ant for everything
[03:03]  * ajmitch may have misread the requirement for the xulrunner package, but ant is annoying
[03:05] <micahg> ajmitch: no, I think it actually uses xul inside the package
[03:09] <ScottK> Any MOTU here who cares about syncevolution working might want to investigate Bug #528326 and make a recommendation.
[03:39] <crimsun> ScottK: makes more sense to sync syncevolution from testing.
[03:40]  * maco giggles at that sentence
[03:42] <ScottK> crimsun: Please say so in the bug if you haven't.
[03:42] <ajmitch> is that still possible to do so now?
[03:42] <ScottK> Yes.
[03:42] <ScottK> I got yours on the list I gave to slangasek already
[03:43] <ajmitch> ah, it was libsynthesis that got synced from sid, not syncevolution
[03:43] <ajmitch> ScottK: I meant in reference to that specific case, where <IP_ADDRESS> got synced
[03:44] <ajmitch> but I got confused as to which package was synced :)
[03:44] <ScottK> Ah
[03:45] <ajmitch> but thanks for passing on the other sync request
[04:44] <imbrandon> ok so i got a question that may seem a little off but google is giving me too much info
[04:45] <imbrandon> i want to format an external usb drive with a filesystem that can handle usb permissions BUT is graceful on ripping it out without unmounting it
[04:45] <imbrandon> ~320gb
[04:45] <imbrandon> extX dosnt seem like it would be graceful on a unclean dismount
[04:45] <imbrandon> hum
[04:47] <jdong> imbrandon: ouch, you're probably gonna have to find that next to the good tasting diet soda and fat free donuts...
[04:48] <imbrandon> hahaha
[04:48] <jdong> the caching semantics on USB externals are apparently horrible at guarding against any sort of unexpected disconnect
[04:49] <imbrandon> i dont really care about nthe file integrity ( wont hold anything important ) mostly just dont wanna have to fschk it every other mount because i yanked it
[04:49] <jdong> well the cache is blind to data vs metadata. it'll lose both without discrimination :)
[04:49] <jdong> and some of the kinds of corruption that'll cause will likely be irreparable via fsck even.
[04:49] <imbrandon> hum
[04:50] <crimsun> if you really don't care, ext4 or btrfs
[04:50] <jdong> yeah it's not a pretty picture
[04:50] <jdong> I don't recommend btrfs
[04:50] <jdong> it still oopses all over the place with any metadata corruption
[04:50] <jdong> and it relies on barrier semantics to prevent said metadata corruption
[04:50] <crimsun> hence the "if you really don't care"
[04:50] <ScottK> And if jdong doesn't recommend something, you really don't want to use it.
[04:50] <jdong> HAHAHAHA
[04:50] <imbrandon> lol
[04:51] <jdong> I'd have to say ext4 is your best choice
[04:51] <jdong> physical block journaling should minimize corruption, and the fsck is one of the fastest.
[04:51] <imbrandon> fat32 does what i want as far as not having to fsck the damn thing, but no unix permissions support sux
[04:52] <imbrandon> ok, ext4 it is then
[04:52] <jdong> well fat32 technically needs to be fscked way more than ext3/4
[04:52] <imbrandon> hehe well the mounter dosnt complain about it
[04:52] <jdong> you can have all kinds of fun structural issures with dirty fat32's
[04:52] <jdong> lol no the mounter doesn't complain
[04:52] <jdong> but it's a far more hazardous situation
[04:53] <crimsun> 7 minutes to take advantage of the newegg 80 GB intel X25-M SSDSA2MH080G2R5 for US$214.99 ;-)
[04:53] <jdong> hahaa
[04:53] <jdong> esata is probably better
[04:53] <jdong> but I don't assume change-of-interface is an option
[04:53] <imbrandon> well this thing is gonna just be sneakernet use mostly , for movies and such between my wii and my laptop and desktop
[04:54] <imbrandon> jdong: and no, i have a cheap usb enclosure i'm ussing on my 2.5in sata western digital 320gb drive ;)
[04:54] <jdong> :)
[04:54] <imbrandon> but its easy to stick 100gb of movies on to watch on the wii
[04:54] <imbrandon> :)
[04:55] <jdong> yup :)
[04:55] <imbrandon> ( and the kids cant scratch the disks )
[04:56] <imbrandon> crimsun: wow, i wish i had the money, just seen what you said about the ssd
[04:56] <imbrandon> the next laptop i purchase i'm going to get a ssd for ( even if i have to buy it seperate and replace the internal drive )
[04:59] <imbrandon> i could just splurge on wired networking for the wii and keep the drive perm attached, lol
[04:59] <imbrandon> that would seem to easy though
[08:24] <dholbach> good morning
[08:25] <joaopinto> anyone familiar with packages which include upstart scripts ?
[08:31] <persia> joaopinto: I've seen a few: generally dh_installinit does the right thing.
[08:32] <joaopinto> bug 530179 needs some love
[08:33] <joaopinto> the vboxsf support module needs to be loaded from  a startup script.  prior to mountall
[08:34] <persia> *prior* to mountall?
[08:35] <persia> Ah, reading the bug log: along with starting mountall.
[08:36] <persia> OK.  So have you tried with a local /etc/init/virtualbox-ose-guest-utils.conf ?
[08:36] <joaopinto> well, was trying, but failed and I was too tried to debug it
[08:37] <joaopinto> but I guess it will be easier for someone with upstart scripts experience
[08:37] <joaopinto> I find upstart scripts hard to debug
[08:37] <persia> Ah.  I know lots about how to deploy them correctly.  I know much less about the contents/
[08:38] <joaopinto> I will need to ping  Scott
[08:39] <persia> He's exceedingly rarely in this channel: -devel might be better.  That said, it may just wait on him to respond to the bug, based on the last comment asking him for input.
[08:41] <joaopinto> as i understood that last comment will cover the error aspect of the bug, on the mountall, not the packaging issue :)
[08:41] <persia> Oh.  I read it as asking for input on the content of the upstart script that should be included.
[08:42] <joaopinto> persia, ops, you are right
[08:51] <joaopinto> still about the vboxfs issue, if there are packages providing filesystems from external modules we may get the same problem
[11:59] <Roobarb-Work> ScottK: ping
[14:57] <zul> gday
[15:39] <dharmatin> :)
[15:54] <tarzeau> could someone take ppa packages and get them into official ubuntu if they are perfect, lintian like?
[15:55] <c_korn> tarzeau: packages are not included from PPAs. you want to upload them to http://revu.ubuntuwire.com/ for REVU
[15:56] <warsocket> who is responsible for revu here?, the wiki siad I should state it here if my upload wont show up in REVU
[15:57] <tarzeau> c_korn: thanks, i'm looking at that page
[15:57] <tarzeau> c_korn: and that's for already in but newer version packages, and completely new packages?
[15:58] <sistpoty|work> warsocket: which package?
[15:58] <warsocket> gsmartdimmer0.0
[15:59] <warsocket> gsmartdimmer_0.0-0ubuntu1 in full
[16:00] <sistpoty|work> warsocket: hm, can't find such a package, not even in the rejected queue
[16:00] <warsocket> weird
[16:00] <sistpoty|work> warsocket: do you still have a .upload file?
[16:00] <warsocket> yes
[16:00] <sistpoty|work> warsocket: can you pastebin it please?
[16:00] <warsocket> Successfully uploaded gsmartdimmer_0.0-0ubuntu1.dsc to upload.ubuntu.com for ubuntu.
[16:00] <warsocket> Successfully uploaded gsmartdimmer_0.0-0ubuntu1.tar.gz to upload.ubuntu.com for ubuntu.
[16:00] <warsocket> Successfully uploaded gsmartdimmer_0.0-0ubuntu1_source.changes to upload.ubuntu.com for ubuntu.
[16:01] <jpds> warsocket: That went to ubuntu, not REVU...
[16:01] <sistpoty|work> warsocket: ah, you didn't dput to revu, but to ubuntu (it'll just get silently dropped there)
[16:01] <warsocket> oh
[16:01] <warsocket> the wiki siad dput automaticlly would upload it it the right oplace
[16:01] <warsocket> but ill have a look how to change that
[16:02] <warsocket> thank you
[16:02] <sistpoty|work> warsocket: dput revu <changesfile>
[16:02] <sistpoty|work> ;)
[16:02] <warsocket> ok tmx
[16:02] <warsocket> k, done
[16:03] <warsocket> now I hope to see it in 5 mins,  thanx for the help
[16:04] <sistpoty|work> yw
[16:06] <warsocket> Package is for "Maverick" but only packages for "lucid" are currently accepted.
[16:06] <warsocket> I thought lucid was alredy closed?
[16:06] <shadeslayer> it is
[16:06] <shadeslayer> archive is frozen....
[16:07] <warsocket> so basicly I cant upload my package to a single distro
[16:07] <lfaraone> warsocket: you have to wait for lucid to be released before uploading to maverick.
[16:07] <warsocket> lucid is frozen maverick is not yet active
[16:07] <warsocket> ok
[16:07] <shadeslayer> warsocket: yes,what you can do is upload to your PPA
[16:08] <shadeslayer> that way you can get out new packages
[16:08] <shadeslayer> warsocket: then port them to maverick and upload
[16:08] <warsocket> erm stupid question maybe
[16:08] <warsocket> whats a PPA
[16:09] <shadeslayer> !ppa | warsocket
[16:10] <warsocket> oh ok I get it tnx
[16:10] <shadeslayer> np
[16:10] <shadeslayer> warsocket: support in #launchpad
[16:10] <warsocket> you btw have soem experience with gambas
[16:10] <warsocket> I also have a error that i cant have build depends when creating a package for all architectures
[16:11] <warsocket> but the build depends on gambas2-dev
[16:11] <warsocket> *was just a long shot
[16:11] <warsocket> but tnx for the PPA will have a look
[22:21] <fabounet> Hi there !
[22:21] <fabounet> We have some last-minute bug-fixes for the Lucid package of Cairo-dock, and we need someone to ack these so that they can be pushed in Lucid.
[22:21] <fabounet> Please see https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/568083 for the complete description of the fixes.
[22:24] <matttbe> this 'little' release is important because it fixes a crash with libxml
[22:25] <matttbe> only appeared on Lucid
[22:26] <matttbe> and this crash appears when the user changes theme, or with weather applet, etc.
[22:29] <persia> So, looking at the bug, it seems all bugfixes, which typically means no barriers to upload.
[22:29] <persia> The bug seems to indicate lp:ubuntu/cairo-dock should be uploaded, but the last revision there is fom 2009-10-05
[22:29] <fabounet> yes, it's only 3 nano versions that we wish to push into the Lucid package
[22:30] <persia> Is that branch accurate, or are there updates?
[22:30] <matttbe> persia: there was a bug with lp:ubuntu/cairo-dock
[22:30] <persia> What's the bug?
[22:30] <persia> Or do you mean bugs in the software in that branch?
[22:31] <matttbe> no a bug with the branch... in fact there is no rev11
[22:31] <matttbe> I already have reported this bug
[22:32] <persia> OK.  How would rev11 get there?
[22:32] <persia> Who pushed it?  Where?  When?
[22:32] <persia> (and what's the bug you reported about the branch?)
[22:32] <matttbe> this bug was confirmed by James Westby
[22:33] <persia> I believe it's a bug :)
[22:33] <persia> I'm just trying to collect enough information to 1) make sure that either processes are followed, or I can tell you what needs doing, and 2) get the necessary bits to upload something.
[22:33] <matttbe> I don't know where is this rev :)
[22:34] <persia> OK.  How do you know that it existed?  Do you know if it exists somewhere else?
[22:34] <matttbe> it exists on my branch : https://code.launchpad.net/~cairo-dock-team/cairo-dock-core/ubuntu
[22:34] <persia> Great!
[22:35] <persia> There's a revision 12 there too.  Is that also something that should be uploaded?
[22:35] <matttbe> the rev 11 was the version 2.1.3-6 of CD => http://packages.ubuntu.com/lucid/cairo-dock
[22:36] <matttbe> and the rev 12 fixes some other bugs (and a crash with libxml)
[22:36] <persia> So rev 11 is the current state of the repository, and rev 12 is the desired state?
[22:36] <matttbe> yes :)
[22:37] <persia> OK.  There's two things I'd like to see then.
[22:37] <persia> 1) Please link the branch and the bug.
[22:37] <matttbe> oh yes, sorry :)
[22:37] <persia> 2) Please submit a merge proposal for lp:~cairo-dock-team/cairo-dock-core/ubuntu into lp:ubuntu/lucid/cairo-dock
[22:38] <persia> Next: this also affects the cairo-dock-plug-ins source?
[22:38] <persia> Err, "cairo-doc-plugins"
[22:38] <fabounet> yes for the plug-ins, it also contains some bug-fixes
[22:39] <persia> OK.  Please also link that branch, and submit a merge proposal from that branch into the lucid branch.
[22:39] <matttbe> ok, the two branches have been linked
[22:40] <persia> (Yes, this is busywork since I'm going to upload, but this procedure also causes automated notification, which *should* reduce your need to come hunt folks in IRC in the future)
[22:40] <persia> Great!
[22:41] <persia> OK.  I see both branches.  Each should have a merge proposal.
[22:41] <persia> *also*, the bug shoud get a cairo-doc-plugins task: "also affects distribution"..."Ubuntu"/"cairo-dock-plugins"
[22:42] <matttbe> ok, merge proposal done
[22:42] <matttbe> ok
[22:43] <persia> Excellent.
[22:43] <matttbe> project added!
[22:43] <matttbe> thanks :)
[22:44] <persia> Now, as soon as the branch discovery tool runs, this would show up on http://qa.ubuntu.com/reports/sponsoring/
[22:44] <persia> And if you get it on that list, the sponsors know they are supposed to upload it.
[22:44] <persia> This isn't a guarantee it gets uploaded (or reviewed) sadly (lack of developers checking the list), but it can let you confirm that you've followed the right procedure to request the sponsoring.
[22:45] <persia> (and most of the time should save you a visit here to catch someone).
[22:45] <persia> Now, I've no idea if it will actually appear there, as I plan to try to figure out how to upload it now, and I may succeed before the sponsoring report includes it.
[22:45] <matttbe> ok, so we just have to wait for a new sponsorship
[22:45] <persia> Right.
[22:46] <matttbe> do we have to add some tag?
[22:46] <matttbe> s
[22:46] <persia> And the sponsor should be assigning themselves when they claim it, so you will get bugmail saying that something is happening.
[22:46] <persia> Nope.  No tags requied.
[22:47] <matttbe> great :)
[22:48] <Laney> good reminder
[22:48]  * Laney does some sponsoring
[22:48] <matttbe> :)
[22:49]  * persia gets sick of watching bzr download at 20KB/s and does it the old way
[22:49] <Laney> wait
[22:49] <YokoZar> persia: Wine upstream's sound guy commented on https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/565071
[22:49] <Laney> what are the semantics of the ubuntu branches request on https://code.edge.launchpad.net/~voronov84/ubuntu/lucid/ubuntu-dev-tools/lucid/+merge/23577 ?
[22:50] <matttbe> Do we need to add subscribers? SRU Verification, ubuntu-sru, etc. ?
[22:50] <Laney> Does it mean "Uploaded to Ubuntu?"
[22:50] <persia> matttbe: A merge proposal should automatically appear in the sponsors report.  You can also subscribe ubuntu-sponsors if you attached a debdiff.  We're currently supporting two workflows.
[22:50] <YokoZar> persia: I want to SRU wine 1.2 when it fully releases in about 2 months to Lucid.  So we either put OpenAL 1.12 in now or do it then  (and in the meantime I bundle openal 1.12 in the wine ppa and test it there)
[22:50] <persia> (because some people find bzr easier to use, and some people like http being 100x faster)
[22:51] <Laney> should we be cherrypicking important fixes now?
[22:52] <persia> YokoZar: Thanks for getting the testcase: I'm completely satisfied (but I'm not on the release team, so you need someone else's ACK)
[22:52] <persia> Laney: We're only allowed to upload bugfix stuff now: cherrypicking may be the easiest way to do that.
[22:52] <Laney> persia: I mean scanning the sponsoring list for "important" bug fixes
[22:53] <Laney> (the sponsoring overview page doesn't make this easy)
[22:53] <persia> Laney: If you like.  Alternately, just go through all of it, and milestone some of it for ubuntu-later
[22:53] <Laney> I don't know what that milestone does, but alright
[22:54] <persia> I think it means we'll do it later (post-release).
[22:54] <persia> I may be mistaken.
[22:54] <persia> But obviosly, pick the important stuff first (but don't fuss too much about it if it's good bugfixes)
[22:55] <persia> Grrr!!!  bzr is painfully slow, and LP is giving me 502s trying to make LP use bzr locally and give me diffs over http.
[22:57] <Laney> I'm lost
[22:57] <Laney> how can I subscribe to a merge request so that I can ask the submitter a question?
[22:57]  * persia has no idea, and just comments in bugs
[22:58] <matttbe> persia: do you want that I add a diff a both branch?
[22:58] <Laney> I'm so out of touch with this stuff.
[22:58] <Laney> Just clicked through to the bug after asking if it should be deferred and it looks like the package has been uploaded already.
[22:59] <persia> matttbe: No, I'll work around it.  Thanks for the offer.
[22:59] <Laney> but the merge proposal is still pending
[22:59]  * persia routinely fights with LP, but is generally quiet about it, but 100x was too much to take today (2MB/s vs. 20KB/s)
[23:00] <Laney> persia: It's the libticalcs stuff that it seems you looked at. These merge requests can be close out, right?
[23:00] <persia> Laney: Then just mark it merged.
[23:00] <Laney> I thought it was supposed to be automatic, hence the confusion
[23:00] <persia> Laney: I haven't looked at them in a really long time, and I'm not sure.
[23:00] <Laney> ok then
[23:00] <persia> I thought it was all automatic, and I wonder if kamalm submitted additional changes.
[23:02] <persia> Based on what I see of merge proposal management in other projects in LP, I have the impression that updating a branch on which there is an active merge proposal ends up updating the merge proposal, so if someone doesn't purge all their branches regularly and give them new names, and the merge proposals aren't cleared regularly, there may be confusion.
[23:02] <geser> Laney: merge proposol get auto marged "merged" when you push the (packaging) branch back to LP, an upload alone does only update the (packaging) branch but doesn't update the pending merges (the upload doesn't contain any info about done merges)
[23:02] <persia> (note that I really like how merge proposals work in projects in LP: I just don't understand how they work in Ubuntu)
[23:02] <Laney> geser: So the uploader didn't push back to lp?
[23:03] <geser> if the MP is still pending, then yes
[23:03] <Laney> ok then
[23:03] <persia> Oh :(  Then I'm probably breaking it by not waiting for bzr
[23:04] <geser> I usually do "bzr bd -S", test-build, "bzr mark-uploaded", "bzr push", "dput"
[23:05] <Laney> yeah, that's the workflow
[23:05] <Laney> I usually forget the tag though
[23:05] <persia> Someone else want 568083 then?
[23:05]  * persia is unwilling to download 59MB at 20KB/s
[23:06] <Laney> I'll see how fast it downloads
[23:06] <persia> Laney: If it's slow for you, I have all the code locally, and can process it easily, just not with bzr.
[23:06] <Laney> bzr init-repo is the trick to make it share state isn't it?
[23:06] <matttbe> persia: sure that you don't want the (bzr) diff :) ?
[23:06] <geser> Laney: yes
[23:06] <persia> matttbe: I have the diff already.
[23:06] <matttbe> ok great
[23:07] <persia> matttbe: https://code.launchpad.net/~cairo-dock-team/cairo-dock-core/ubuntu/+merge/23889/+preview-diff/+files/preview.diff is an example diff URL.
[23:07] <persia> What I lack is the bzr metadata.
[23:08] <Laney> persia: It's fast here; I'll take it
[23:11] <geser> Laney: re subscribing to MP: have you tried to add yourself as reviewer?
[23:11] <persia> Laney: Thanks.
[23:11] <Laney> geser: No (it's not clear that that's what it does)
[23:12] <Laney> should "bzr diff ../branchtomerge/" work?
[23:13] <geser> no, that would show the diff for the file "../branchtomerge"
[23:13] <Laney> can I do it like that?
[23:13] <geser> what diff do you want?
[23:13] <Laney> between the branch I'm on and the branch I am about to merge
[23:14] <Laney> or do I just merge it and then check from there?
[23:15] <geser> either that or as branchtomerge should have a common accestor with the branch you are on: bzr diff -r123
[23:15] <Laney> yeah I thought it would be able to figure that out
[23:16] <geser> perhaps "bzr diff --old a --new b" works too
[23:16] <Laney> bzr diff lp:... would have worked I think
[23:16] <geser> that works too
[23:16] <Laney> which isn't too different to ../someotherbranch
[23:18] <geser> if you do this often, you could branch lp:... and do "bzr diff --old ../lpbranch" to save network traffic
[23:19] <Laney> I usually branch the thing that needs sponsoring and the packaging branch
[23:20] <geser> me too, in that case bzr diff --old ... should work
[23:20] <Laney> from which branch?
[23:22] <geser> "cd sponsorbranch; bzr diff --old ../pkgbranch" or "cd pkgbranch; bzr diff --new ../sponsorbranch" (although I only use the 1st and never tried the 2nd)
[23:22] <Laney> alright
[23:22] <Laney> will try it in a minuet
[23:33] <persia> geser: Do you know if there's a good way to make https://code.launchpad.net/~voronov84/ubuntu/lucid/ubuntu-dev-tools/lucid/+merge/23577 go away?
[23:33] <Laney> Do we care about not-binnmuable-all-depends-any?
[23:33] <persia> Ah, Laney appears to have already fixed it.
[23:34] <persia> Laney: Not enough to upload to Lucid at this point.
[23:34] <Laney> persia: I don't know, I think maybe that should stay open until the package is uploaded
[23:34] <persia> Laney: That makes sense.
[23:35] <Laney> persia: but you could push to the lp:ubuntu/ubuntu-dev-tools branch to make it go away
[23:36] <persia> Well, except that I merged in on top of DktrKranz's stuff, which wasn't there and doesn't share revision history.
[23:37] <ajmitch> surely there'd be some shared history that'd be used as an ancestor?
[23:37] <persia> ajmitch: None whatsoever.
[23:38] <persia> ajmitch: Because the one branch is where we've always done work and the other is constructed based on the history of uploads.
[23:38] <ajmitch> how annoying
[23:38] <ajmitch> and you get file conflicts when trying to merge, I suppose?
[23:38] <persia> No, you can't merge.
[23:39] <persia> "No common ancestor" error.
[23:39] <ajmitch> not without some forced hackery, I think
[23:39] <ajmitch> at which point you'd probably run into those conflicts
[23:39] <persia> To my knowledge, bzr has no file-content-comparison merge feature directly.
[23:40] <persia> Given a common ancestor, you can init a bzr branch on the common ancestor, branch that branch, apply monolithic patches to both sides, and then use bzr merge to reconnect.
[23:40] <persia> This is annoying, but works nicely, if you like how bzr merges.
[23:40]  * persia doesn't happen to like bzr merge at all, but mostly because of the format of the conflict markers, rather than anything about how the algorithms work
[23:41] <ajmitch> merging with no common ancestor is done against revision 0..-1 or similar, I think
[23:42] <persia> When I tried it, bzr gave me an error, so I constructed a series of patches that did the right things, and applied those with interim commits.
[23:43] <persia> Someone with more patience or less joy in building patch series may have better luck.
[23:43] <ajmitch> much patience is required at times, I think
[23:45]  * persia will eventually be assimilated
[23:46]  * micahg gave up on bzr merge for archive merges after it didn't delete files properly
[23:47] <Laney> oh, bah, I forgot to do merge-package again
[23:47] <Laney> I hope there's not much difference between merge and merge-package
[23:49] <persia> I think merge-package is upstream tarball aware or something.
[23:49] <ajmitch> persia: I've been stuck in my old-fashioned ways of not using bzr for package branches
[23:50] <persia> ajmitch: Then you too, will someday, be assimilated.
[23:50] <YokoZar> ScottK: what's this about Wine being a part of Ubuntu studio seeds?  I can't see any rdepends for it anywhere
[23:50] <persia> I actually like using bzr and debcommit for native packages in bzr (e.g. u-d-t, installer stuff, etc.)
[23:50] <persia> YokoZar: Because of the VST plugins.
[23:51] <YokoZar> persia: you mean the ones that don't build at all at the moment because we're waiting on the Wine update?
[23:51] <persia> YokoZar: RC will be out *really soon now*
[23:51] <persia> YokoZar: Yeah, but we're not going to get enough testers to handle a DVD respin in time for RC.
[23:51] <Laney> matttbe: Uploading cairo-dock
[23:51] <Laney> thanks for your work
[23:51] <Laney> (please fix that lintian error for the next upload)
[23:52] <matttbe> many thanks Laney !
[23:52] <matttbe> Laney: which lintian error?
[23:52] <YokoZar> persia: what I mean is as I understand it ScottK waited on my wine1.2 package update because of ubuntu-studio, but I needed to do that update (and then another wine one) in order to prevent the VST FTBFS
[23:52] <Laney> the one about it not being binNMUable
[23:52] <Laney> matttbe: run lintian -i blah.dsc and you'll see it
[23:53] <matttbe> ok
[23:53] <YokoZar> persia: so it's a mystery to me how the Ubuntu Studio image is being built at all if it actually depends on it
[23:53] <persia> YokoZar: Right, so in fact the piece that was affeted was completely broken.  That said, it's not critical enough to respin the images and make the testers test again.
[23:53] <matttbe> Laney: don't forget 'cairo-dock-plug-ins' ;)
[23:53] <Laney> surely not, I'm looking at that one now
[23:53] <persia> YokoZar: It fails to include that bit, which is a bug.
[23:54] <matttbe> Laney: great! thank you very much :)
[23:55] <YokoZar> persia: ok, makes sense.  I'm just a bit uneased that I didn't notice this problem before, and we're pretty much at the last possible moment here
[23:55]  * YokoZar should start using Ubuntu Studio...
[23:56] <persia> YokoZar: No point  reinstailing: the main bit you'd notice is the VST stuff: if you have *some* VST host, you'll encounter the entirety of the bugs.
[23:56] <Laney> matttbe: Are the plugin dependencies on cairo-dock-dev tight enough?
[23:56] <persia> But the upload can surely happen as soon as RC is released.  It's just that if it happens now, and the images are respun, they won7t get tested, and there will be no US RC.
[23:56] <Laney> it says that they will work on any future version of cairo-dock-dev
[23:57] <matttbe> Laney: you have to compile CD-plug-ins with the same version of CD (core)
[23:57] <Laney> matttbe: yeah, that's not what the build-dependency says
[23:58] <matttbe> cairo-dock-dev (>= 2.1.3-9)
[23:58] <Laney> that would be satisfied by any future version
[23:58] <Laney> do you need a << too?
[23:58] <matttbe> Laney: should it be cairo-dock-dev (= ${source:Version}) ?
[23:59] <Laney> nope, as they could be different
[23:59] <Laney> should that be -10-lucid anyway?
[23:59] <matttbe> yes


[14:59] <tseliot> apw: what value do you use for the MovementBottomEdgeArea or whatever is called of your touchpad
[14:59] <tseliot> ?
[14:59] <apw> 4100 i think
[14:59] <apw> are we aiming to get that to happen magically ... its pretty annoying
[15:00] <apw> xinput set-int-prop "SynPS/2 Synaptics TouchPad" "Synaptics Area" 32 0 0 0 4100
[15:00] <apw> tseliot, ^^
[15:01] <tseliot> apw: yep, this is why I asked
[15:01] <hyperair> speaking of touchpads, for some reason, my bottom left corner has become trigger for circular scrolling that scrolls horizontally
[15:01] <hyperair> not that i'm complaining or anything, but isn't there documentation about this?
[15:01] <hyperair> it seems like an unexpected and welcome feature that's undocumented and may have been the result of some bug or other
[15:03] <tseliot> hyperair: circular scrolling? Isn't that disabled by default?
[15:03] <hyperair> yes it is
[15:03] <hyperair> (i wish it were enabled by default though)
[15:03] <hyperair> or at least some way of configuring it in gnome
[15:04] <hyperair> i've got circular scrolling explicitly enabled in an fdi file here
[15:04] <tseliot> a UI should be available for Lucid
[15:04] <hyperair> that's nice
[15:05] <hyperair> while that's done, i think it'd also be awesome to enable middle button configuration for both mouse and touchpad
[15:05] <hyperair> in particular, my use case is middle button emulation for touchpad but not mouse
[15:05] <hyperair> bunch of fdis to handle that
[15:06] <jcristau> doesn't the gnome pointing device stuff handle those things?
[15:06] <tseliot> that depends on the gnome-settings-daemon
[15:06] <jcristau> ah..
[16:20] <mac_v> tormod: hi... regarding comment > https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/436546/comments/6  i'm on x-updates ppa.. how do i revert to the karmic mesa? doesnt the x-updates have the fix?
[16:20] <tormod> mac_v: ppa-purge
[16:21] <tormod> mac_v: x-updates does not have the fix, because it is just upstream, packaged
[16:21] <tormod> mac_v: there hasn't been an upstream fix yet
[16:21] <mac_v> tormod: isnt the ppa purge only for edgers?
[16:21] <mac_v> rather from edgers ppa
[16:21] <tormod> mac_v: no it purges any ppa you specify
[16:22] <tormod> mac_v you can also use apt-get install PACKAGE=VERSION or PACKAGE/karmic
[16:23] <mac_v> tormod: is the ppa purge available only from the edgers ppa?... i cant seem to find it
[16:23] <tormod> mac_v: yes it's only there ATM
[16:23] <mac_v> ah... thanks. will do
[16:24] <tormod> reminds me I have been working on it and I should publish a new version
[16:26] <tormod> can't believe they're so slow fixing that mesa crasher upstream though. it's crashed, regression, and in the 7.6.1 release
[16:26] <tormod> *crasher
[16:28] <mac_v> tormod: its crashing even when i switch windows a tad faster :/
[16:28] <tormod> guess it doesn't help that the guy who wrote that code seems to have vanished
[16:28] <mac_v> lol
[16:28] <tormod> mac_v: it crashes with the new karmic packages?
[16:28] <mac_v> tormod: no , the x-updated one..
[16:29] <tormod> oh good :)
[16:29] <mac_v> havent yet ,switched to karmic packages
[16:37] <tseliot> apw: the next revision (i.e. ubuntu7) of synaptics will have that option set to 4100 by default. Just FYI
[16:37] <apw> tseliot, cool, is that just for dell 10v, presume so
[16:37] <tseliot> apw: yes, it's just for 2 models
[16:38] <apw> very cool
[16:44] <tseliot> :-)
[18:09] <mac_v> hmm , the ppa purge wasnt very useful for x-updates... how do i revert the x-updates packages all at once? is apt-get for the individual packages the only option?
[18:18] <mac_v> bryce_: any suggestions? ^ how to revert from x-updates back to karmic packages


[03:03] <superm1> yo Daviey
[03:03] <superm1> and majoridiot
[03:03] <superm1> and Xenocide
[03:03] <superm1> and everyone else here :)
[03:03] <majoridiot> hola
[03:04] <superm1> so i spent the last 7 hours working on a freaking lab assignment
[03:04] <superm1> really stupid debugging error early on
[03:04] <superm1> that made things horrible to track down :(
[03:04] <majoridiot> anything interesting?
[03:04] <superm1> single cycle implementation of a cpu
[03:04] <superm1> mips architecture
[03:04] <majoridiot> hehe
[03:04] <superm1> yyup
[03:05] <superm1> i've still got the multicycle yet to do tonite
[03:08] <superm1> ah good
[03:08] <superm1> imbrandon, u present?
[03:34] <superm1> majoridiot, nice page for the known hardware list
[03:34] <superm1> i just saw
[03:34] <superm1> looks good
[03:34] <majoridiot> ty
[03:34] <majoridiot> still picking at it
[03:34] <superm1> as for the cards that *may* require cx88_dvb modprobed
[03:34] <superm1> its not just if there is a pvr-150 in the box
[03:34] <majoridiot> i'm making a common mythv_firewire page, as the info is not edgy-specific
[03:34] <superm1> its in all cases
[03:35] <majoridiot> ah
[03:35] <majoridiot> will change that.
[03:35] <superm1> they should just add to /etc/modules
[03:35] <majoridiot> ty
[03:35] <superm1> yup
[03:35] <Xenocide> superm1 i got the replacement card
[03:35] <superm1> and :)?
[03:35] <Xenocide> its in, but i haven' ttried the IR yet
[03:35] <superm1> you scared?
[03:36] <majoridiot> superm1: so modprobe cx88_dvb and add it to /etc/modules?
[03:37] <superm1> yes
[03:37] <majoridiot> k
[03:38] <superm1> just cat >> /etc/modules << EOF
[03:38] <superm1> cx88_dvb
[03:38] <superm1> EOF
[03:38] <superm1> should do it
[03:38] <superm1> oh wait u have to do it with sudo dont ya
[03:39] <superm1>  sudo sh -c "echo "cx88_dvb" >> /etc/modules"
[03:39] <superm1> should do it then
[03:40] <majoridiot> yes
[03:43] <superm1> afaik that bug wont be fixed until 2.6.21
[03:43] <Xenocide> it probabbly won't work
[03:43] <Xenocide> lol
[03:44] <majoridiot> ;)
[03:44] <superm1> Xenocide, i'd be scared too.
[03:44] <Xenocide> anyone want to buy a sprint sanyo 8400 phone?
[03:44] <superm1> i think i'd probably break a window at that point
[03:44] <superm1> na i'm happy with my nextel
[03:44] <Xenocide> hehe
[03:44] <Xenocide> i just got the moto Q today
[03:44] <Xenocide> so i need to sell my old one
[03:44] <superm1> www.howardforums.com is probably a good place
[03:45] <Xenocide> yea
[03:45] <Xenocide> i put it on sprintusers and craigslist
[03:46] <superm1> you should get a bite or two then
[04:19] <Xenocide> my back end keeps crashing
[04:19] <Xenocide> randomly
[04:19] <superm1> oh?
[04:19] <Xenocide> idk why
[04:20] <majoridiot> anything in the log?
[04:21] <Xenocide> where is the log again
[04:22] <majoridiot> /var/log/mythtv/mythbackend.log
[04:23] <Xenocide> 2007-03-29 22:00:00.508 Finished recording American Dad "With Friends Like Steve 's": channel 1011
[04:23] <Xenocide> 2007-03-29 22:00:00.629 TVRec(2): Enabling Full LiveTV UI.
[04:23] <Xenocide> 0: start_time: 157.691 duration: 149.003
[04:23] <Xenocide> 1: start_time: 157.662 duration: 148.997
[04:23] <Xenocide> stream: start_time: 1751.805 duration: 1655.899 bitrate=5495 kb/s
[04:23] <Xenocide> 2007-03-29 22:00:00.743 AFD: Opened codec 0xad627680, id(MPEG2VIDEO) type(Video)
[04:24] <Xenocide> 2007-03-29 22:00:00.861 AFD: Opened codec 0xad616950, id(MP2) type(Audio)
[04:24] <Xenocide> 2007-03-29 22:00:00.963 TVRec(2): RingBufferChanged()
[04:24] <Xenocide> 2007-03-29 22:00:01.067 Finished recording American Dad "With Friends Like Steve 's": channel 1011
[04:24] <Xenocide> 2007-03-29 22:01:00.861 TVRec(1): Changing from RecordingOnly to None
[04:24] <Xenocide> 2007-03-29 22:01:00.874 Finished recording Grey's Anatomy "My Favorite Mistake": channel 1004
[04:24] <Xenocide> 2007-03-29 22:01:00.913 Event socket closed. No connection to the backend.
[04:24] <Xenocide> [mpeg2video @ 0xb722fa68] invalid cbp at 14 28
[04:24] <Xenocide> [mpeg2video @ 0xb722fa68] Warning MVs not available
[04:24] <Xenocide> 2007-03-29 22:01:26.804 Connecting to backend server: <IP_ADDRESS>:6543 (try 1 of 5 )
[04:24] <Xenocide> 2007-03-29 22:01:26.813 Connection timed out.
[04:24] <Xenocide> You probably should modify the Master Server
[04:24] <Xenocide> settings in the setup program and set the
[04:24] <Xenocide> proper IP address.
[04:24] <Xenocide> thats all i got
[04:24] <Xenocide> it crashes every other day or so
[04:25] <majoridiot> does the address of the backend dynamically change?
[04:25] <Xenocide> uh...
[04:25] <Xenocide> they are both on the same machine
[04:25] <majoridiot> i just saw that
[04:25] <majoridiot> <IP_ADDRESS>
[04:25] <majoridiot> hm
[04:26] <majoridiot> look at your older logs and find other crashes... see if there is any similarities
[04:30] <Xenocide> meh
[04:30] <Xenocide> all my roomies are still bitching quality isnt' as good as the tv
[04:31] <majoridiot> did you adjust the capture resolution?
[04:48] <Xenocide> yes
[04:48] <Xenocide> 720x480
[04:48] <majoridiot> then tell yer roommates to piss off.
[04:48] <majoridiot> hehe
[04:48] <majoridiot> can *you* see a noticeable difference?
[05:37] <Xenocide> yes
[05:37] <Xenocide> wow im not checking thsi window at all LOL
[05:37] <majoridiot> um.. nope.
[05:37] <majoridiot> what tuner?
[05:43] <Xenocide> pvr150
[05:44] <majoridiot> using a splitter on the cable?
[05:56] <majoridiot> time to kick back and relax...
[06:00] <majoridiot> got a few more new pages started... plugins included.
[06:00] <majoridiot> superm1: when you get a chance, here's another of the new pages from today: https://help.ubuntu.com/community/MythVideo
[06:30] <superm1> ah nice majoridiot
[06:30] <superm1> sorry for the delay
[06:31] <superm1> just finishing up senior design stuff
[06:31] <majoridiot> ;)
[06:31] <majoridiot> starting to fill in the blanks a little
[06:31] <superm1> i wish that feisty was coming out a few months later
[06:31] <superm1> so that there didnt have to be this hectic rush
[06:31] <superm1> to get last minute stuff in
[06:32] <majoridiot> well, there's always G-g G.
[06:32] <superm1> G-g G?
[06:32] <majoridiot> typo
[06:32] <majoridiot> whatever comes next... G
[06:32] <superm1> oh you mean feisty +1
[06:32] <superm1> i wonder when they decide on the title
[06:33] <majoridiot> grumpy goana?
[06:33] <superm1> well i think grumpy kinda adds a negative connotation though?
[06:33] <majoridiot> hehe.  yup.
[06:34] <superm1> ha
[06:34] <superm1> yup
[06:34] <majoridiot> ok...
[06:34] <majoridiot> giddy gifelte?
[06:34] <majoridiot> lol
[06:34] <superm1> well right when i put my first packages up on my mythtv repo for feisty
[06:34] <superm1> the description was
[06:35] <superm1> packages designed for a mighty deer overlord
[06:35] <majoridiot> i did see that
[06:35] <superm1> so they better get something good, i need to remain my whittiness
[06:36] <majoridiot> when do you think the feisty guide links should go on the main page?
[06:36] <superm1> at or later than release candidate
[06:36] <superm1> i say we make that the goal date to have them ready by
[06:37] <majoridiot> is there an eta on rc?
[06:37] <superm1> yes
[06:37] <superm1> on the feisty schedule
[06:37] <superm1> let me see if i can find a link
[06:37] <superm1> https://wiki.ubuntu.com/FeistyReleaseSchedule
[06:37] <superm1> so by april 12th
[06:38] <superm1> gives about two weeks
[06:38] <majoridiot> not bad
[06:38] <superm1> to have everything ready by
[06:38] <superm1> i'm not sure mythbuntu will be ready in time though
[06:38] <majoridiot> i was thinking around 2 weeks
[06:38] <superm1> imbrandon still hasn't got all the webspace stuff squared away
[06:38] <superm1> and jetsradiem is having lots of troubles with ubiquity
[06:38] <superm1> so it might have to be staggered to be a post feisty release
[06:39] <majoridiot> no need to rush it
[06:39] <superm1> exactly
[06:40] <superm1> i'm not sure if Daviey got the splashes redone yet either
[06:40] <superm1> haven't heard from 'im in a few days
[06:40] <majoridiot> he was in earlier
[06:40] <superm1> oh i'll have to read the log then
[06:40] <majoridiot> mid-afternoon
[06:40] <majoridiot> ish
[06:40] <superm1> k
[06:41] <superm1> well i gotta run.  i have to catch the last bus back from campus
[06:41] <superm1> have a good night.  catch up with ya tomorrow
[06:41] <majoridiot> start looking appx 2: 30 pm central.
[06:41] <majoridiot> k
[06:41] <superm1> k
[06:41] <majoridiot> ttyl
[06:42] <majoridiot> relaxin time..
[05:06] <superm1> hey jono
[05:07] <jono> hey
[05:07] <superm1> jono, i wanted to ask you on the liklihood of sponsorship to UDS?
[05:07] <superm1> any ideas?
[05:07] <jono> sponsorships have already been decided I am afraid
[05:08] <superm1> oh thats a shame :(
[05:08] <superm1> is next UDS in the states by chance?
[05:10] <superm1> jono, was there an application process for it, or moreover, was there a lot handed out?
[05:10] <jono> not sure where the next UDS is
[05:10] <jono> we generally hand pick people
[05:10] <superm1> ah
[05:10] <jono> who are working on particular projects
[05:11] <superm1> jono, well mythbuntu should be further along by next UDS, so perhaps there will be more of a chance for sponsorship next time around then :)
[05:12] <jono> :)
[05:13] <superm1> imbrandon, are you here?
[05:20] <superm1> keescook, what do you think about bug 86358?
[05:21] <superm1> ubotu, didn't get it.  odd: try again: bug #86358
[05:21] <ubotu> Malone bug 86358 in user-setup "user-setup allows mythtv to be chosen for a username" [Undecided,Needs info]  https://launchpad.net/bugs/86358
[05:27] <superm1> keescook, nvm.  i pinged cjwatson and he said he'd add it
[05:32] <keescook> superm1: cool
[05:32] <superm1> this being the case, the only package that we will have that is non ubuntu servers will be ubiquity
[05:33] <superm1> i can pull user-setup from our bzr branc
[05:57] <_MMA_> The next UDS looks like it will be in Boston, Massachusetts (USA)
[06:05] <jetsaredim> sweet


[02:11] <fabioluciano> Anybody use unit193  ubuntu core iso?
[02:12] <Unit193> A couple people do.
[02:12] <fabioluciano> Hi :)
[02:13] <fabioluciano> Seems that the team release the bionic iso, but unfurtenely doesnt seems to work. The ubiquity crashes
[02:14] <Unit193> ubiquity can be quite the pain.  What arch, vbox or hardware?
[02:15] <fabioluciano> hardware
[02:16] <Unit193> Do you see permission errors in /var/log/syslog?  In the past, as a bug in ubiquity or somewhere one had to run it as root. ;/
[02:18] <fabioluciano> @unit193 A lot of them on syslog.
[02:19] <fabioluciano> https://pastebin.com/RpXUMuQ9
[02:20] <fabioluciano> On the paste i just pasted where the error occours
[02:20] <fabioluciano> @Unit193 amd64 :)
[02:22] <Unit193> fabioluciano: And is this installing from the boot menu, or live session?
[02:22] <fabioluciano> @unit193 i tried both.
[02:24] <Unit193> The errors you pasted weren't really troublesome, installer passing deprecated args and stuff like that.
[02:30] <fabioluciano> @Unit193 https://paste.ee/p/tVnrH
[02:31] <Unit193> That's the permission denied I was thinking of yeah.
[02:32] <fabioluciano> :|
[02:33] <Unit193> In the past, running the installer as root worked around the issue, but isn't really a fix...
[02:33] <fabioluciano> In moments like that i feel sad to not help in the tests...
[02:34] <fabioluciano> And i also tested the command in the launcher in the terminal
[02:34] <fabioluciano> sudo --preserve-env=DBUS_SESSION_BUS_ADDRESS,XDG_RUNTIME_DIR sh -c 'ubiquity gtk_ui'
[02:34] <fabioluciano> i tried a lot of things hehehe
[02:45] <Unit193> (In case you were wondering, I was looking around https://paste.ee/p/tVnrH#s=0&l=3901)
[03:07] <Unit193> fabioluciano: Are you in a live session now, btw?
[03:17] <fabioluciano> sorry
[03:17] <fabioluciano> yes
[06:02] <USERNAME00> There is an error on the dl site btw https://xubuntu.org/download#lts
[06:02] <USERNAME00> Just thought you should know.
[06:03] <USERNAME00> codename xenial xerus
[06:09] <enyc> USERNAME00: and the release note link below
[06:10] <enyc> https://xubuntu.org/news/xubuntu-18-04-release/  does exist already, at least
[06:13] <USERNAME00> people make mistakes no worries just figured i would let you know
[07:43] <badrihippo> Can I upgrade from xenial to bionic directly?
[07:44] <badrihippo> I ran do-release-upgrade but it seems to be doing artful instead
[09:33] <robinsmith> hey everyone! anyone had a chance to install and run xu 18.04? how's it looking? stable?
[09:35] <robinsmith> is there nobody here?
[09:35] <robinsmith> anybody there?
[09:35] <hycer> just sit back and enjoy your dist-upgrade
[09:35] <robinsmith> okay!
[09:36] <robinsmith> I am on 16.04 (fully updated) ...
[09:36] <robinsmith> will "sudo apt-get update && sudo apt-get upgrade && sudo apt-get distupgrade" get me 18.04?
[09:36] <robinsmith> do I need to run any new commands?
[09:38] <hycer> you probably have to update to 17.04 before, if using GUI updater
[09:39] <Unit193> There's LTS to LTS, will be offered in July.
[09:39] <Unit193> (First point release.)
[09:39] <robinsmith> oh! okay, @unit193
[09:39] <Spass> hello robinsmith, if you want 100% stable experience just wait for 18.04.1 point release, you will get update notification then
[09:39] <robinsmith> @Unit193
[09:40] <robinsmith> got it, spass. thanks for the tip!
[09:40] <robinsmith> so, then I can continue doing "update and upgrade" only till .1 is out, right?
[09:40] <Spass> although I think I'll upgrade my system sooner, 18.04 looks stable enough for me now
[09:41] <Spass> yes, then you will get a message that a new LTS is ready/released and it will ask you if you want to upgrade
[09:42] <Spass> I'm talking about GUI updater built-in
[09:44] <Spass> your 16.04 install is still supported for another year, so if you don't really need to have 18.04 now, I think it's better to just wait for that .1 release
[09:44] <Spass> that's more like a stable, natural progress developers intended for LTS users
[09:46] <Spass> said all that, 18.04 is ready to go :) so if you need to install a fresh Xubuntu somewhere - use 18.04 ISO
[09:51] <robinsmith> thanks bud!
[09:51] <robinsmith> hey ... one more thing ... probably not xu specific ...
[09:51] <robinsmith> i want a good epub reader. any suggestions?
[09:52] <robinsmith> not entire calibre or fbreader (not free anymore)
[09:52] <robinsmith> I actually want the book-reader from calibre, but, I don't know how to extract only that binary from the package. any tips?
[09:58] <Spass> sorry, I don't use any epub reader on my system, but you should stay here for longer, maybe someone will help
[11:15] <mdm_> is xubuntu 18.04 live
[11:20] <enyc> mdm_: released... yes
[11:20] <enyc> !isitoutyet
[11:37] <manuel_> buenas tardes tengo una pregunta tengo el xubuntu 16.04 y acaban de sacar el 18.04 . como ago para actualizar sin tener que formatear
[11:38] <krytarik> !es | manuel_
[11:39] <manuel_> gracias
[13:52] <MapMan> Hi! How can I upgrade from xubuntu 16.04 to the latest LTS version?
[13:53] <cfhowlett> wait until 18.4.1 drops in July or do a clean intall now, MapMan
[13:55] <MapMan> a clean install is the preffered way to go?
[13:56] <MapMan> preferred*
[13:56] <cfhowlett> IMHO yes, but I'd still wait for the first point release
[13:58] <MapMan> I'm kinda on a schedule so I can't wait until June
[13:58] <MapMan> July*
[13:58] <cfhowlett> then torrent the iso
[13:59] <MapMan> Ok I'll do a clean install, thanks
[13:59] <cfhowlett> happy2help!
[14:00] <MapMan> cfhowlett: is there any reason you're suggesting waiting for the point release? Are there any known bugs you have in mind or you're thinking more in terms of best practices?
[14:01] <cfhowlett> .1 collects the first round of bug fixes which appear whenever a new OS is released.  this is my sanity saving policy
[14:01] <cfhowlett> of course YMMV MapMan
[14:02] <MapMan> Ok I see, thanks
[16:21] <jollyjester> hello
[16:30] <jordan4ibanez> Hello, I have created an ubuntu installer usb multiple times over multiple usb drives and I always get this kernel panic. https://i.imgur.com/AvFf4tZ.png
[16:30] <jordan4ibanez> I even used one of my spare hard disks as usb and I still get the panic, I'm using a z400 workstation with xeon 1366 processor and gtx 750 ti
[16:31] <jordan4ibanez> Is the new kernel just incompatible with my chipset/processor? 17.10 doesn't do this, yet 18.04 does
[16:35] <Spass> hello jordan4ibanez, what do you use to create that bootable USB? are you sure the ISO is not corrupted? maybe try re-downloading it
[16:39] <jordan4ibanez> Multiple isos
[16:39] <jordan4ibanez> Multiple usbs
[16:39] <jordan4ibanez> Etcher, unetbootin, dd, rufus
[16:40] <jordan4ibanez> And then I use a 17.10 iso and it works perfectly first try, I'm just not sure what to do, if there's a syncing command that could stop this that'd be great
[16:42] <jordan4ibanez> Doing an upgrade causes my usb ports to be inoperable
[18:08] <marcelodsl> olá!
[18:09] <marcelodsl> Estava utilizando o 17.10 e meu note hibernava normalmente, agora com o 18.04 não hiberna... alguma dica?
[18:10] <krytarik> !br | marcelodsl
[18:12] <marcelodsl> obrigado!
[23:57] <Aberts10> Hi.
[23:58] <Aberts10> I am trying to setup a program from peppermint OS on xubuntu 18.04  called advert-block... Since gksu is no longer in the repos, i tried switching to pkexec... But whenever i launch the program with pkexec, it asks for my password, and then does nothing further except say "Error executing ./block-advert.sh: No such file or directory"
[23:58] <Aberts10> Any ideas?


[01:20] <diddledan> perl 6 is magic: http://mirror.as35701.net/video.fosdem.org//2015/devroom-perl/perl6_for_mortals.mp4
[01:23] <OerHeks> Perl 6 is comming out in december?
[01:23] <diddledan> it's coming out?
[01:24] <diddledan> :-p
[01:24] <OerHeks> err or released
[01:24] <diddledan> it's gonna get released? :-p
[01:25] <diddledan> I thought they were just going to develop it forever

[01:25] <OerHeks> You must be a python guy .. ow haha
[02:42] <daftykins> OerHeks: yeah don't mind diddledan ;)
[02:42] <diddledan> I'm the resident ignoramous
[02:54] <daftykins> diddledan: https://www.dropbox.com/s/5y8stpjzb2jn71p/IMG_20150509_022419.jpg?dl=0
[02:54] <daftykins> :D
[02:55] <diddledan> \o/
[02:55] <diddledan> kitty wins the internet!
[02:55] <diddledan> since when has dropbox had a discussion thingy?
[02:55] <daftykins> it's annoying
[02:55] <daftykins> couple of weeks, if you hover over the # of people that get notified, it previously said my real name
[02:55] <daftykins> i had to log in and change it =|
[02:56] <daftykins> i was seriously peeved at dropbox for that move
[02:56] <diddledan> mr kins. dafty kins.
[02:56] <daftykins> the very same :D
[03:02] <daftykins> oh also - https://www.dropbox.com/s/ybtepv4tpuvhrn4/VID_20150509_022253.mp4?dl=0
[03:03] <diddledan> nawww
[03:04] <diddledan> danglies were invented for cats. or vice versa
[03:04] <daftykins> :>
[03:31] <mappps> waaaaaaaaah
[03:31] <mappps> gt sunburnt
[03:31] <mappps> grmpf
[03:34] <daftykins> D:
[03:35] <daftykins> tut tut
[03:35] <daftykins> do you look lobster-like?
[03:42] <mappps> just a bit red on my arms
[03:43] <mappps> i live 2mins from where i was relaxing on the rocks bu the sea
[03:43] <daftykins> :>
[03:43] <mappps> contemplated going back to get suncream..figured nah il be ok
[03:43] <mappps> lol
[03:43] <daftykins> how're the temps of late?
[03:44] <mappps> like  25c
[03:44] <mappps> hot hot hot
[03:44] <mappps> shorts weather all the time
[03:49] <daftykins> :D
[03:49] <daftykins> hell i'm in shorts at 12-14
[03:50] <mappps> ;D
[03:50] <daftykins> https://www.dropbox.com/s/ybtepv4tpuvhrn4/VID_20150509_022253.mp4?dl=0
[03:50] <mappps> yea course but i mean now its too hot to consider jeans
[03:50] <mappps> would be all hot and sticky and yuck
[03:51] <daftykins> mmhmm
[03:51] <mappps> i carry suncream in my bag..so incase i go somewhere/play tennis or say go to the beach i have it
[03:51] <mappps> just didnt think i needed any didnt realise it was that hot heh
[03:53] <daftykins> it'll sneak up on you
[05:00] <diddledan> hmm, when did daylight happen?
[07:56] <brobostigon> morning boys and girls.
[07:56] <diddledan> allo
[07:57] <brobostigon> morning diddledan
[09:24] <diddledan> so. who's running wily yet?
[09:24] <diddledan> :-p
[09:28]  * zmoylan-pi waits for a few months when new versions come out before making the leap in case there are any whoopsies
[09:29] <diddledan> wily's out?
[09:30] <diddledan> hmm, I wonder if cortana can answer that
[09:31] <zmoylan-pi> ask cortana if siri knows if wily's out :-)
[09:31] <diddledan> or ask cortana if siri knows if google now's it's wily is out
[09:39] <diddledan> gotta love my electricity supplier: "Important Security Information: To log in to your account simply click on the secure link above. To help you identify this email is genuine and as an extra security measure, your full account number is shown at the top of this email."
[09:39] <diddledan> note the links in the email are all http:// (no s!)
[09:40] <zmoylan-pi> could have been worse.  they might have started demanding signatures for every electron delivered...
[09:40] <moreati> diddledan: I'll see your leccy merchant and raise you a local council
[09:41] <moreati> "Dear Mr Willmer, We have an update about your Request."
[09:41] <zmoylan-pi> or someone went dumpster diving and made a fake site...
[09:41] <moreati> No where in the email is there an indication of what the update is, or a link to the request
[09:42] <diddledan> so my leccy is named after a local province in the uk, suggesting it be a british corp, yet they email from "Received: from FEXHESLAR01.euro.iberdrola.local (unknown [<IP_ADDRESS>])"
[09:42] <diddledan> err wrong paste
[09:42] <zmoylan-pi> go to the suppliers site and see if there's an email address or a notice about this notice
[09:42] <diddledan> Received: from iberdrola.es (<IP_ADDRESS>) by FEXHESLAR01.euro.iberdrola.local
[09:43] <diddledan> I emailed my bank a while back moaning that they emailed me purely to tell me that they want to email me
[09:44] <diddledan> now I keep getting emails asking me to fill out a survey letting them know how well they did in not resolving my moan
[09:44] <bigcalm> Good morning peeps :)
[09:45]  * diddledan feels relaxed all of a sudden
[09:45] <diddledan> oh ello bigcalm
[09:50] <bigcalm> :)
[09:53] <diddledan> "how big is your calm": https://www.youtube.com/watch?v=XpqqjU7u5Yc
[10:00]  * bigcalm puts on his name sakes album
[14:15] <SuperEngineer> Been looking for a copy of Sidekick for my freedos usb.  Some might call me peed off with the lack of success
[14:28] <SuperEngineer> A simple search for it does show "sidekick dos free download, cfos dos for dos, sidekick unlock, bingo sidekick and more."...
[14:29] <SuperEngineer> freedownload3.com/downloads/sidekick_dos.html ..but hmmmm, would you trust that site
[14:29] <SuperEngineer> ?
[15:46] <SuperEngineer> DARN! just downloaded Sidekick 1.5 & copied to a floppy, then to FreddDos USB...
[15:46] <SuperEngineer> ... "Sorry, unknown vwrsion PCDOS version. Please report to Borland"  :(
[15:46] <SuperEngineer> ... "Sorry, unknown PCDOS version. Please report to Borland"  :(
[15:47]  * penguin42 wonders if you can tell it what to answer as the version
[15:48]  * SuperEngineer wonders if he can shout it loud enough!
[15:50] <SuperEngineer> but can't think of a way round your suggestion penguin42 - maye editing the .com file with a hex editor - but not sure where info is hiden or what to change it to if found
[15:50] <shauno> have you tried calling borland?  ;)
[15:51] <penguin42> they still exist
[15:52] <shauno> (ancient stuff isn't always hopeless.  we seem to do well because there's two old guys who love being able to lord that no-one else has any idea about 20yo stuff)
[15:52] <penguin42> the guys in the balcony?
[15:53] <SuperEngineer> hmmm. that would be the same same Borland that wants to sell an old copy [5.25 disk only] for highly extortionate amounts?
[15:54] <SuperEngineer> shauno, when you "ancient stuff", are you refering to youurself & myself?  OUCH
[15:55] <penguin42> not Statler and Waldorf ?
[15:56]  * SuperEngineer hums Muppets song
[15:59] <SuperEngineer> hang on! interesting info coming in on #freedos for me :)
[16:09] <foobarry> https://www.kickstarter.com/projects/krita/krita-free-paint-app-lets-make-it-faster-than-phot/description
[16:10] <simondbull> Hey all, having a few issues with running Telegram Desktop on Ubuntu MATE. Works fine on Unity. I've run it through gdb, http://pastebin.ubuntu.com/11045856/ Any ideas or help would be much appreciated :)
[16:49] <ali1234> here is back trace?
[17:06] <simondbull> ali1234, link to back trace can be found here :) http://pastebin.ubuntu.com/11046761/


[02:52] <joelteon> how do I make a service start at boot?
[02:54] <xnox> joelteon: specify start on condition, see cookbook http://upstart.ubuntu.com/cookbook/. something like "start on runlevel [2345]" should do it.
[02:56] <joelteon> hmmm
[02:56] <joelteon> okay
[02:58] <joelteon> so if you have normal conditions *and* a runlevel condition, is that bad?


[22:18] <cholcombe> charmers: if anyone would be willing to give this a second look/chance I'd really appreciate it: https://bugs.launchpad.net/charms/+bug/1469213
[22:18] <mup> Bug #1469213: Submitting a Gluster Charm for Review <Juju Charms Collection:In Progress> <https://launchpad.net/bugs/1469213>
[22:19] <cholcombe> I ran into a roadblock last year with juju storage being in development.  I've since fixed that and added support storage
[22:19] <cholcombe> support for storage*