[12:01] <jbailey> Bah.
[12:02] <jbailey> I just retested locally, and it doesn't fail there.
[12:33] <lamont__> jbailey: minimal chroot?  (maybe missing build-deps?)
[12:34] <jbailey> Right, I usually test in a chroot I use for development.
[12:35] <jbailey> I don't see how it built before if it was missing a build-dep, but I've slimmed down the chroot for this build.
[12:36] <jbailey> I think I need to hack glibc (and maybe cdbs) so that if a build fails at configure time that config.log is spit to stdout.
[12:45] <jbailey> Mm, missing build-dep on the bit the provides libcgcc_s_64
[12:46] <jbailey> erm
[12:46] <jbailey> or not.
[12:46] <jbailey> That's provided by gcc-3.4 supposedly.
[01:15] <jbailey> doko: Still around?
[01:28] <doko> yep
[01:29] <jbailey> doko: I figured it out.  collect2 was acting strange, but I hadn't realised that gcc would change its arguments to collect2 based on what was available.
[01:29] <jbailey> lamont__: In Debian (and in Ubuntu if you know...) is libc6-dev-sparc64 usually already in the base chroots / is it part of build essential?
[01:30] <jbailey> lamont__: I'd like to have ppc64 be consistant with current practice for sparc/s390
[01:30] <lamont__> jbailey: nfc
[01:30] <lamont__> for it to be there (properly), it needs to either be essential, or a Depend: of build-essential
[01:33] <doko> only for sparc, not s390
[01:34] <BenM> Hey doko, tseng sent me to you
[01:35] <doko> BenM: i
[01:35] <doko> BenM: hi
[01:35] <BenM> mono is failing its regression test on gcc4
[01:36] <BenM> and tseng thought you might be able to help out
[01:36] <doko> jbailey, lamont__: b-e lists the 64bit dev only for sparc, not s390
[01:36] <doko> BenM: I do? hmm. all of them?
[01:37] <BenM> well, one specific test case gets a segfault
[01:37] <BenM> we are pretty sure something is getting miscompiled
[01:38] <BenM> http://primates.ximian.com/~bmaurer/mono-1.1.8.tar.gz
[01:38] <BenM> its reproducable on that
[01:38] <BenM> you just have to configure; make; make check
[01:38] <doko> what does happen, if you reduce the optimization level? any warnings?
[01:39] <BenM> it happens both on -O2 and -O0
[01:39] <BenM> no warnings for the file other than pointer signedness
[01:39] <doko> ahh, you know the file. does gcc-3.4 work?
[01:41] <BenM> yes
[01:41] <BenM> well, by that i mean "the file where the backtrace says the segfault happens"
[01:42] <BenM> there isn't anything suspcious in the entire build log though
[01:44] <jbailey> lamont__: Any objection to it being added to b-e?
[01:50] <doko> so, if you compile the testcase with 3.4, the testcase works? or a file from the distribution?
[01:51] <lamont__> jbailey: that gets back to the question of whether or not it is build-essential...
[01:51] <BenM> well, the test case is c# :-)
[01:51] <lamont__> jbailey: for which, I'd recommend a discussion with the build-essential maintainer
[01:51] <lamont__> == keybuk
[01:52] <BenM> the issue is, if I compile mono using gcc4, it fails
[01:52] <BenM> if i compile mono with gcc!=4, it works fine
[02:47] <jbailey> lamont: I couldn't remember your email address, so I didn't cc: you, but I've emailed scott.  If it turns out that it gets added to b-e, we just need to respin the build, otherwise I'll need to add the build-dep
[02:48] <jbailey> lamont: Did you keep your ubuntu.com address?  I remember that sabdfl was talking about them being available to members, so thought you might be  testcase. =)
[03:03] <lamont> jbailey: yes, still have ubuntu.com
[03:03] <jbailey> Luvly
[03:08] <BenM> doko, gotten a chance to try that tarball yet
[03:08] <BenM> ?
[06:18] <fabbione> morning
[06:26] <fabbione> lamont: ping?
[06:26] <lamont> ack
[06:27] <fabbione> lamont: we will need to revert the gcc-3.4 b-d stuff...
[06:27] <lamont> fabbione: having difficulty verifying that ipsec traffic is passing back through INPUT once unencapsulated.
[06:27] <lamont> iz annoying
[06:27] <lamont> fabbione: why?
[06:27] <fabbione> unfortunatly we need the latest gcc and latesr k-p to build
[06:27] <lamont> on all architectures?
[06:27] <fabbione> 11753
[06:27] <fabbione> no only i386
[06:27] <lamont> because the relaxed check made it so that I could build... :-)
[06:29] <fabbione> yeah i know
[06:29] <lamont> ah, so make the build-dep be powerpc i386
[06:30] <fabbione> yeah that too
[06:32] <fabbione> kernel-package (>= 8.135ubuntu4) [powerpc] , kernel-package (>= 8.132ubuntu2) [!powerpc]  ???
[06:32] <fabbione> kernel-package is arch all
[06:33] <fabbione> but we will need to upgrade that too :/
[06:34] <fabbione> gcc-3.4 (>= 3.4.4-0ubuntu6) [powerpc i386] , gcc-3.4 [!powerpc !i386]
[06:34] <fabbione> does it look sane?
[06:34] <fabbione> i can never remeber how to add more than arch to []
[06:35] <lamont> I believe that's it
[06:35] <lamont> (comma is right out..)
[06:37] <fabbione> yeah i did check with other packages too :)
[06:39] <fabbione> lamont: what did you change in the configs?
[06:41] <lamont> fabbione: I added the missing lines.
[06:41] <lamont> R2[45] 00, SQUASHFS, HOSTAP
[06:41] <fabbione> ah ok
[06:41] <fabbione> it was just an update
[06:42] <lamont> well, it was a 'fix hppa configs since they didn't get updated with the addition of the drivers'... but I shortened that...
[06:42] <fabbione> humm
[06:42] <fabbione> sorry.. i might have done that in a different way recently
[10:02] <chmj> jbailey, thanks for the patch
[11:41] <jbailey> chmj: Glad to show it to you. =)  IT's just really nice to have all that information for tracking.
[11:41] <jbailey> chmj: We found that we were starting to lose track of where things things came from and why we did them. =)
[11:43] <chmj> oh ok, that format sure has enough info
[11:45] <jbailey> doko: I thought sparc killed the wrapper a couple years ago on the grounds that it was unpredictable and that it sucked?
[11:46] <jbailey> lamont, fabbione: ping re: builds of glibc on your archs. =)
[11:46] <fabbione> jbailey: i am still building gcc-*
[11:46] <fabbione> jbailey: once it's done i will do glibc
[11:47] <jbailey> fabbione: Cool.
[11:47] <fabbione> it's running the test-suite right now
[11:47] <fabbione> it shouldn't take too long
[11:47] <jbailey> Any idea how the hack is going to get the build-logs onto people so I can just see them myself?
[11:47] <doko> jbailey: no, the thread on d-sparc
[11:48] <doko> jbailey: so you upload a glibc with fixed b-d's?
[11:48] <jbailey> doko: Ah, a'ight.
[11:48] <fabbione> jbailey: i didn't manage to talk with elmo in a few days
[11:48] <fabbione> jbailey: i will need to check with him
[11:48] <jbailey> doko: I haven't.  If we're adding it to build-essential, it just needs a give-back.
[11:49] <jbailey> doko: (I've also been awake for about 10 minutes)
[11:52] <doko> jbailey: as you like it, but for packages like zlib1g and others, we should explicitely add it.
[11:52] <jbailey> Why?
[11:52] <doko> push back a package to Debian and it will fail
[11:53] <doko> it's not a big job to add that b-d for these few packages
[11:53] <jbailey> True.  I just hate b-d'ing on b-e packages.
[11:55] <doko> so we should add amd64-libs-dev to b-e as well?
[11:55] <jbailey> That's the question. =)
[11:56] <jbailey> Or should sparc be made like the others and have sparc64 dropped from b-e?
[11:56] <doko> no, then we have to change the gcc wrapper as well ...
[11:57] <jbailey> We should be treating biarch configs consistently.
[11:57] <doko> but what about an update for amd64-libs to match our current glibc before we go multiarch?
[11:57] <doko> Mithrandir: ^^^
[11:58] <jbailey> But I tend to fall on the side of thinking that the sparc-gcc wrapper is teh suck.
[11:58] <jbailey> right!  That's what I was going to ask you yesterday! =)
[11:58] <jbailey> To just clarify the include directories so I could do the glibc work for i386/amd64 and amd64/i386 biarch
[12:01] <doko> jbailey: I don't like it either, but BenC defends it
[12:01] <jbailey> Is benc the only one who defends it?  At this point I'd take joshk's word over ben's for the sparc port.
[12:02] <fabbione> jbailey: did you complete the kernel build with a ppc32 kernel?
[12:02] <doko> I would have to look
[12:02] <jbailey> fabbione: BAh, that's what I was supposed to do last night, sorry.  No, lemme reboot and start it now.
[12:02] <fabbione> eheh ok :) thanks
[12:02] <fabbione> there is no rush really
[12:02] <fabbione> i am not going to upload anytime soon
[12:02] <fabbione> i need to go and prepare food
[12:02] <fabbione> bbl
[12:06] <jbailey> doko: I'm just updating the status of my stuff for the wiki.  Want me to update ToolChainRoadmap?  I was thinking "C++ transition still in progress, ppc64 uploaded"
[12:06] <doko> sure
[12:07] <jbailey> Mm, and java bits in main?
[12:08] <jbailey> and C++ done for main
[12:21] <doko> still waiting for the OOo2 build ...
[12:23] <jbailey> glibc with added build-dep uploaded
[12:52] <infinity> doko : Which OOo2 build are you waiting on?
[12:52] <infinity> doko : It was successful on i386/ppc, failed on amd64/ia64.
[01:21] <doko_> infinity: oh, nice, I didn't see them succeed, you know, the upload was done some months ago ;)
[02:39] <lamont> ln -sf /usr/include debian/libc6-dev/usr/hppa64-linux-gnu/include
[02:39] <lamont> ln: creating symbolic link `debian/libc6-dev/usr/hppa64-linux-gnu/include' to `/usr/include': No such file or directory
[02:40] <lamont> jbailey: that's the error I get from -5...
[02:40] <lamont> seems kinda familiar.. :-)
[02:41] <lamont> -6 is downloading now, build will happen sometime today, I expect.
[03:20] <Mithrandir> doko: amd64-libs is utterly uninteresting to me and jbailey have some things up his sleeve to get rid of it, afaik.
[03:22] <doko> Mithrandir: ok, would it be possible to keep building gcc-4.0 biarch in unstable ? would be a good thing to point people to it as a test for 64bit compatibility
[03:23] <Mithrandir> doko: yes, I think that would be a good thing.
[03:25] <doko> Mithrandir: asking, because it's NOT possible to build gcc-4.0 biarch in breezy at the moment
[03:25] <doko> I think we face the same problem in unstable once glibc get's updated?
[03:51] <jbailey> lamont: Don't bother with -6 then.
[03:56] <Mithrandir> doko: why isn't that possible?
[03:58] <doko> Mithrandir: build failure, just try to build the package with an installed amd64-libs-dev.
[03:58] <doko> IIRC, even if biarch is disabled
[04:12] <jbailey> doko: ln: creating symbolic link `debian/libc6-dev/usr/hppa64-linux-gnu/include' to `/usr/include': No such file or directory
[04:12] <jbailey> doko: Who provides /usr/hppa64-linux-gnu ?
[04:12] <jbailey> Do we?
[04:12] <doko> hmm, glibc should provide that
[04:13] <jbailey> 'kay, I'll add the mkdir.
[04:13] <doko> it doesn't hurt. ok, it' currently not yet available, because I didn't build a hppa64 compiler yet.
[05:49] <doko> infinity, lamont, lamont__: please requeue binutils for powerpc, if this is built and in the archives, then gcc-3.3 and gcc-3.4 for powerpc.
[05:51] <lamont__> doko: binutils kicked
[05:52] <doko> lamont__: thanks
[06:18] <jbailey> doko: Thanks
[06:18] <jbailey> lamont__: If you can do the same for ppc that would be lovely.
[06:18] <jbailey> err
[06:18] <jbailey> gdb on ppc
[06:25] <lamont__> jbailey: ok.  but grumbling about gdb just doesn't seem kind until after an incomplete statement of work. :-)
[06:25] <lamont__> there -you happy>
[06:25] <jbailey> Wha...? =)
[06:26] <lamont__> you just want it given back?  or do I need to actually _do_ something to the chroot first?
[06:26] <lamont__> ah, same 'needs new procfs.h' issue
[06:26] <jbailey> Sorry, I had assumed this was in the queue after the "updates chroots on ppc" =)
[06:26] <lamont__> lol
[06:27] <jbailey> Bad optimiser!  Stop applying yourself to human interactions!
[07:46] <elmo> doko: have you seen this fun "gcc-4 miscompiles glibc" bug?
[08:36] <jbailey> elmo: Doesn't affect us, we use gcc-3.4 to compile glibc.
[08:40] <elmo> score
[08:41] <elmo> can we make it a goal to not be using gcc-3.4 for anything by breezy?
[08:41] <elmo> or is there anything that's unlikely to be compilable by 4.0 by release?
[08:41] <jbailey> I think we'd planned on glibc and the kernel staying with 3.4
[08:41] <jbailey> We still need 3.4 in the archive for g77 anyway, so we're not losing much.
[08:41] <elmo> whine
[08:41] <elmo> ok
[08:42] <jbailey> Neither upstream is advocating gcc 4 anyway.  glibc 2.3.5 doesn't compile with gcc-3.4 without patches.  The bug you're thinking of is for CVS HEAD of glibc.
[08:44] <elmo> yeah, it just makes me cry that we're carrying 4 compilers around
[08:44] <elmo> and using one of them to only compile basically two packages
[08:45] <jbailey> 4?
[08:45] <elmo> 2.95/3.3/3.4/4.0
[08:45] <jbailey> I thought we had dropped 2.95 already
[08:45] <elmo>   gcc-2.95 | 2.95.4.ds15-22 | breezy/universe | source
[08:45] <jbailey> Oh, hmm.
[08:45] <jbailey> NEeded to compile silo for sparc still.
[08:45] <elmo> it's kind of nice for some commerical crap too
[08:46] <jbailey> Feh
[08:46] <elmo> well, if you have a better way to monitor hardware raid array on big 3 servers, lemme know :p
[08:46] <jbailey> But 3.4 will probably need to stick around until the 4.2 timeframe when fortran catches up.
[08:46] <elmo> that long?  ouch
[08:47] <jbailey> Follow 4.1, it doesn't look like fortran is moving fast to get the old g77 specific bits in.
[08:47] <jbailey> s/Follow/I've been following
[08:47] <jbailey> Is it build errors in software that you can change, or linking problems from precompiled modules?
[08:48] <elmo> latter
[08:48] <elmo> not modules tho, just binary progs
[08:48] <elmo> usually linked to old libstdc++
[08:49] <elmo> it's not a huge problem, there are newer versions for FC 4 and so on, but I've had other problems with them
[08:49] <elmo> (glibc symbol errors RUN AWAY)
[08:49] <jbailey> afk a sec
[09:03] <jbailey> Right.  Those should probably all work fine against the breezy glibc.
[09:03] <jbailey> elmo: (And everyone knows that backports of glibc are a good idea.. Right kids?)
[09:07] <lamont__> jbailey: B4CKP0R75 RUL3Z!
[09:08] <lamont__> hey, I know.  lets backport breezy to Bo.
[09:08] <lamont__> All of it.
[09:08] <jbailey> lamont__: package by package or feature by feature?
[09:08] <lamont__> package-by-package in one fell swoop
[09:09] <lamont__> and build it twice, of course. :-)
[09:09] <jbailey> (/me fears how hard allowing bo to seamlessly dist-upgrade to breezy would be)
[09:09] <elmo> jbailey: chicken
[09:10] <lamont__> jbailey: best accomplished via rapid injection of lead into the crainal cavity
[09:10] <lamont__> cranial?
[09:10] <jbailey> I'm a tofudebeast, a far fiercer animal.
[09:10] <lamont__> jbailey: call the result frankenstein - people will expect seams that way.
[09:26] <fabbione> jbailey: right now silo is building with the default gcc... i removed the strict b-d to allow silo in main
[09:28] <jbailey> fabbione: Ah?  I thought benc said it didn't work?
[09:28] <fabbione> it doesn't ALWAYS work
[09:28] <fabbione> it does most of the time
[09:30] <jbailey> But..  it's *silo*
[09:30] <jbailey> That's the way it is even with gcc-2.95 compiling it.
[09:37] <fabbione> jbailey: tough.. i am not going to commit to support gcc-2.95 in main because of silo
[09:37] <fabbione> if it boots.. good.. otherwise bitch upstream to fix silo :)
[09:37] <jbailey> benc doesn't answer *questions* I have, I can't imagine him answeing me asking him to do actual work. =)
[09:38] <fabbione> jbailey: he is busy working to make his own business
[09:38] <fabbione> but i can still ping him on irc when he is around
[09:38] <fabbione> : idle     : 61 hours 24 mins 0 secs (signon: Sun Jun 12 08:14:43 2005)
[09:39] <fabbione> anyway
[09:39] <fabbione> time to be with my wife :)
[09:39] <fabbione> cya tomorrow guys


[00:45] <xu-irc93w> hello, i'm trying to get xubuntu working properly on an old samsung laptop and when i shut the lid and open it again the display fails to re engage.
[00:46] <xu-irc93w> is there any way for me to get some kind of output log from this?
[00:46] <xu-irc93w> i don't even know where the failure is.
[01:02] <xu-irc93w> here is the model number, the BIOS was recently updated and it did not correct the issue. np300v5a-a06us
[01:07] <xu-irc93w> the screensaver also crashes every time i log in to the computer
[01:45] <xu-irc93w> i found a somewhat sloppy fix, i set the system to ignore the lid
[06:27] <sorinello> Hello. Any idea when Xubuntu will be available for do-release-upgrade  ?
[08:41] <frank_> ciao
[08:41] <frank_> ciao
[08:44] <PeGaSuS> sorinello: LTS will be valid on April 2024.. you can upgrade to the regular release with `do-release-upgrade -d`, iirc
[08:46] <PeGaSuS> s/valid/released/
[10:26] <xu-help12w> Hi All and thanks for being here.  I am seasoned linux user but an irc newbe.
[10:33] <xu-help12w> I have a stable xubuntu 22.04.lts setup with mirrored zfs on root and apt triggered snapshots.  I cannot remember if I installed zfs myself or if it was available out of the box.  I would like to move this to newer faster hardware.  In the past I used apt-clone on a raspberry pi and it worked perfectly.  Could anyone please offer up the best
[10:33] <xu-help12w> way to achieve this ?
[12:25] <xu-help12w> While waiting I installed xubuntu 22.04.3 LTS with ZFS on root so should my question be posed to the ZOL forum ?
[13:00] <xu-help12w> Has anyone here moved/copied a ZFS on root system to new hardware ?
[16:01] <sorinello> PeGaSuS, thanks for the info, but I have "For any new version" checked when to notify of new updates.
[16:02] <sorinello> so I don't want to upgrade to a devel release
[16:03] <PeGaSuS> sorinello: remember that you always need `apt update` and `apt dist-upgrade` before :)
[16:06] <sorinello> ran them both, but do-release-upgrade still does not work. It doesn't find new versions
[16:19] <rfm> sorinello, do-release-upgrade won't find a new release until it is added to https://changelogs.ubuntu.com/meta-release . mantic isn;t there yet.
[16:36] <sorinello> rfm, thanks for the explanation. Do you happen to know the reason why it wasn't added yet ?
[16:36] <sorinello> because I am sure there is one
[16:37] <rfm> sorinello, no, I don't.
[17:35] <tomreyn> sorinello: it's entirely normal that release upgrades aren't enabled at the very same time as a release happens, though. sometimes there are days between those events, sometimes it's months (for LTS releases it won't happen before YY.MM.1 is released).
[17:35] <tomreyn> xu-help12w: you're more likely to find people with zfs experience in #ubuntu, just because there are more people there.
[17:36] <tomreyn> (and the foundations of Xubuntu and Ubuntu are identical)
[17:44] <xu-help12w> Thank you v.much will ask there.  Thanks again for all the xubuntu work.
[17:46] <tomreyn> i'd say "you're welcome", but i don't do any. ;-)
[17:59] <xu-help12w> You replied. Thanks.


[06:36] <anom01y> hey guys I am trying to get my hauppauge pvr 150 to work, do I need v4l2 or ivtv ?
[06:41] <foxbuntu> anom01y, its ivtv v3.x in mythtv-setup
[06:41] <foxbuntu> not analog v4l device
[06:44] <anom01y> foxbuntu, v4l2 is analog ?
[06:45] <anom01y> so I need mythtv to watch tv from /dev/video0 ?
[06:45] <anom01y> I can see it with v4l2 but its crappy quality
[06:45] <foxbuntu> anom01y, thats because thats the wrong set of codecs for the pvr-250
[06:45] <foxbuntu> er
[06:45] <foxbuntu> pvr-150
[06:46] <anom01y> ahh ok, so in ubuntu is there a package to install the necessary software ?
[06:46] <anom01y> and, do I need mythtv ? or can I just use ivtv and mplayer ?
[06:46] <foxbuntu> anom01y, you do not need to install anything extra with mythbuntu for that card to work
[06:48] <foxbuntu> anom01y, you just need to reconfigure it in the MythTV Backend Setup
[06:48] <anom01y> foxbuntu, mythbuntu is a whole new ubuntu o/s
[06:48] <anom01y> ?
[06:49] <anom01y> can I just install mythtv ?
[06:49] <foxbuntu> anom01y, Im sorry, I misunderstood your orig. question
[06:49] <foxbuntu> anom01y, there are ways to watch tv from that card without mythtv
[06:50] <foxbuntu> anom01y, but you need a player that can control the tuner
[06:51] <anom01y> ok, xawtv can do that can
[06:51] <foxbuntu> anom01y, if you already have Ubuntu you can add MythTV, or convert to Mythbuntu quite easily
[06:51] <anom01y> can't it ?
[06:51] <anom01y> well I would just like to get mythtv, I have done alot of work to this ubuntu installation
[06:51] <foxbuntu> anom01y, I am not familiar with that app
[06:52] <anom01y> ok well I am going to try it
[06:52] <foxbuntu> anom01y, I suggest just installing Mythbuntu-Control-Centre than using that to add the mythtv roles
[06:52] <foxbuntu> ...if you want MythTV
[06:53] <anom01y> ok
[06:58] <anom01y> what about tvtime ?
[07:00] <foxbuntu> that one shoudl work
[07:00] <foxbuntu> should*
[19:24] <derekS> hey guys. i am looking for a small, low power pc with hdmi to use as a mythubuntu box, do you guys have any reccomendations?
[19:31] <rhpot1991> derekS: I have been looking at this myself lately: http://system76.com/product_info.php?cPath=27&products_id=95
[19:31] <rhpot1991> will need karmic for full potentional though
[20:14] <derekS> rhpot1991: lemme look :)
[20:26] <derekS> rhpot1991: not bad, not too expensive either
[20:28] <rhpot1991> derekS: only thing is that you'll need mythtv .22 to unleash the full power of the graphics with it
[20:28] <rhpot1991> http://www.mythtv.org/wiki/Vdpau
[20:29] <derekS> interesting
[20:29] <orificium> I'
[20:30] <orificium> I'm using VDPAU right now with an onboard nForce 750a chipset.
[20:30] <rhpot1991> they just gave me a coupon for meerkat and meerkat ion: mythbuntu-meerkat
[20:30] <rhpot1991> will get you $10 off :)
[20:30] <orificium> For some reason, my CPU utilization is way down, but 720P videos still are jittery
[20:31] <rhpot1991> orificium: I'd assume your chipset is the issue there
[20:31] <orificium> it's supposed to be equivalent to a 9300/9400
[20:31] <rhpot1991> I've heard you want your video card to have access to 512+ of ram as well
[20:31] <orificium> Using 180.xx
[20:32] <orificium> I may try 185 to see if it helps
[20:32] <orificium> or see if there are any xorg options I can add
[20:32] <orificium> I have my bios set to use 512 for video memory.
[20:36] <orificium> I've been meaning to switch back to a different renderer to see if it makes a difference.  This is a new install of 9.04 + the mythbuntu repos.  I set it right to VDPAU.  When I was using the 8.10, I could watch 720P with very few issues.
[20:36] <orificium> weekly build repos
[20:37] <orificium> The graphite theme seems to be more taxing than the terra theme also.
[20:49] <NOT_guru> well hi there everybody,  just playing with myth and hating the card setup (ati HDTV tuner and a pvr-250-b (beyond tv branded MCE )
[20:49] <NOT_guru> I have decided time is worth more to me and was looking at the HDHomerun
[20:50] <NOT_guru> does this device seem to be working decently with mythbuntu?  does it have a strong Tuner?
[20:51] <NOT_guru> has anyone mixed OTA HD and Cable Tuning?
[20:51] <NOT_guru> TIA
[20:55] <rhpot1991> orificium: havne't used VDPAU yet so I can't help much there, I'd open up a forum thread or check the mythtv-users mailing list
[20:55] <rhpot1991> HDHR works very well NOT_guru
[20:56] <rhpot1991> NOT_guru: http://www.silicondust.com/hdhomerun/channels
[20:56] <NOT_guru> awsome rhpot
[20:56] <rhpot1991> you can look up your channels there
[20:57] <orificium> NOT_guru: The biggest problem I have with the HDHomeRun is the the mythbackend starting before my network.  So I'd have to restart the mythbackend after a reboot.
[20:57] <orificium> You'd only have to do it once pre reboot though
[20:57] <NOT_guru> my thats no real problem
[20:57] <orificium> And there are some work-arounds.  Most of them didn't seem to resolve my issue compeltely though
[20:58] <NOT_guru> my server room is in the basement   but I am down there at least once a day anyways
[20:58] <orificium> like re-ordering /etc/init.d/ stuff
[20:58] <NOT_guru> and did you build mythtv on ubuntu or use the distro ( I downloaded mythbuntu 9.04 )
[20:58] <NOT_guru> should I consider using a more mature build? 8.10
[20:59] <orificium> Otherwise, I love the HDHR.  I split my local cable network line and can record all the local HD channels on two signals.
[20:59] <NOT_guru> everything is working fine for me with no tuning currently
[20:59] <NOT_guru> I am seeing the device on the egg for $138  so I am really tempted
[21:00] <NOT_guru> mainly because I am getting older and don't have the time to get my ATI HDTV wonder going
[21:00] <orificium> Yeah, Newegg is where I bought mine.
[21:00] <orificium> Great site
[21:00] <NOT_guru> well  looks like I have to order this today so I can have it by the weekend
[21:00] <orificium> I waited for a deal as well.
[21:00] <NOT_guru> yah  they have the $10 code now
[21:00] <NOT_guru> so seems a good deal to me
[21:01] <NOT_guru> of the none PCI / PCI-e devices
[21:01] <orificium> Unforunately I've misplaced my power adapter and haven't been able to test it on 9.04 + weekly builds (latest trunk build)
[21:01] <NOT_guru> I was thinking this looked the most robust ( HDHOMERUN )
[21:01] <NOT_guru> they have a BR burner on sale for $139 as well
[21:02] <NOT_guru> just dunno if my system will be able to handle it
[21:02] <orificium> 9.04 seems pretty stable though.  Karmic is just around the corner.
[21:02] <NOT_guru> ath64 3000+ with a NV6800 vid card
[21:02] <NOT_guru> karmic will be 9.10?
[21:02] <orificium> Yeah
[21:02] <NOT_guru> and thats when we MAY see .22?
[21:02] <NOT_guru> of myth
[21:02] <orificium> Not sure.  But you can try it out now by installing the weekly builds repos.
[21:03] <orificium> I'm using it
[21:03] <orificium> with the new MythUI and VDPAU
[21:03] <orificium> But VDPAU wouldn't work on your card
[21:03] <orificium> XvMC is the way to go on the 6800 I believe.
[21:03] <rhpot1991> NOT_guru: bluray and linux don't mix very well currently
[21:03] <NOT_guru> I may... I amn just trying to get the whole concept of myth ironed out
[21:03] <rhpot1991> what with drm and all
[21:03] <NOT_guru> no worries
[21:03] <NOT_guru> just saves me money
[21:04] <NOT_guru> I have played a couple MKV files on the system ( UFC's) and they ran just dandy
[21:04] <NOT_guru> MAYBE at most 40% proc load
[21:04] <superm1> NOT_guru, 0.22 will most likely be in 9.10
[21:04] <superm1> it's already in the repos
[21:04] <NOT_guru> now it just needs more storage
[21:04] <NOT_guru> awsome
[21:04] <orificium> I never burn media.  I watch something once and look for something new :)
[21:04] <superm1> so unless something really bad happens,  it will stick
[21:04] <NOT_guru> now to just order the HDhomerun and a couple WDC 1TB green drives  LOL
[21:05] <NOT_guru> oh  I didn't burn them... I just copied the MKV's to the backend
[21:05] <NOT_guru> but that 250 is filling quick
[21:05] <NOT_guru> and I don't even have tuning going
[21:05] <orificium> I was referring to your interest in buying a bluray burner.
[21:05] <NOT_guru> the DVD ripping is wonderful
[21:05] <NOT_guru> ah  yes sir
[21:06] <NOT_guru> just seemed like a decent deal
[21:06] <NOT_guru> but I really want media to some down some more
[21:06] <NOT_guru> well..
[21:06] <NOT_guru> you guys rock
[21:06] <NOT_guru> I appreciate the input
[21:06] <NOT_guru> thank you ALL so much
[21:06] <NOT_guru> OH
[21:06] <NOT_guru> last thing
[21:06] <NOT_guru> flash video on mythbuntu 9.04
[21:07] <NOT_guru> was going to try the flash10.deb from adobe
[21:07] <NOT_guru> any reason not to go that route or do you have a suggested route?
[21:07] <NOT_guru> I have it working on a VM right now
[21:07] <NOT_guru> but as you would assume full screen no worky
[21:09] <NOT_guru> oh  and does the "media Library" imdb poster downloader working in 0.22 of myth
[21:09] <NOT_guru> and director
[21:09] <NOT_guru> I just manually downloaded them for my test system
[21:09] <NOT_guru> =0
[21:15] <orificium> I've been using the new ttvdb script mostly successfully
[21:15] <orificium> for TV Shows
[21:16] <orificium> it's a little quirky, but its pretty easy to add your own poster art for a TV+Season
[21:16] <orificium> er TV show + season
[21:17] <orificium> Honestly, I haven't tried to update metadata for a movie.  I'm assuming it'll scan thetvdb.com and imdb.com both using the same option in MythVideo?
[21:18] <NOT_guru> seems to
[21:18] <NOT_guru> I saw a new script was being developed
[21:18] <NOT_guru> but there was question of whether it would be included with myth because it uses IMDB
[21:19] <NOT_guru> and scraping IMDB is technically against the rules
[21:19] <orificium> That's the issue with Apple Movie Trailers now
[21:19] <NOT_guru> so they were yabbing about using something like movie poster .com or something
[21:20] <NOT_guru> I also have yet to decide if I want to sign up for schedules direct.  I hate siging up for things
[21:20] <NOT_guru> especially when they demand my home address
[21:20] <NOT_guru> I like being an anonymouse
[21:21] <NOT_guru> but I tried mythtv about 4 or 5 years agi
[21:21] <rhpot1991> the imdb one is dead, http://www.mythtv.org/wiki/Tmdb.pl
[21:21] <NOT_guru> and it was just so frustrating
[21:21] <rhpot1991> NOT_guru: sign up, they provide a good service for cheap
[21:21] <NOT_guru> just sent that link hoime   thank you
[21:21] <rhpot1991> also its run by a bunch of open source guys, so no worries
[21:21] <rhpot1991> they give you 2 weeks for free too
[21:22] <NOT_guru> can I not just scrape the EIT that comes on a OTA digital signal?
[21:22] <NOT_guru> 7 days now
[21:22] <rhpot1991> you can try to and see if it works for you
[21:22] <NOT_guru> also  I used to be a FTA say junkie...
[21:22] <orificium> I use Schedules Direct pretty successfully and $20/year is not bad at all.  I used a PO Box when I signed up if that helps with the anonymity issue :)
[21:22] <NOT_guru> 97.1 bird and such
[21:22] <NOT_guru> oh the price is not the issue
[21:23] <NOT_guru> I agree its reasonable
[21:23] <NOT_guru> its just me and my overbering privacey concerns
[21:23] <NOT_guru> has anyone here tried a twinhan DVBs card
[21:23] <NOT_guru> true FTA of course
[21:23] <NOT_guru> I like strange channels
[21:24] <NOT_guru> and I am hoping I can find a good BBC source on a freebird
[21:24] <NOT_guru> need to check lyngsat again
[21:24] <NOT_guru> if I get eit going I may just donate to the cause and not sign up
[21:25] <NOT_guru> give my $20 straight to myth
[21:25] <NOT_guru> =)
[21:25] <orificium> I believe there are some alternative methods to grabbing schedule data, but SD keeps it simple.  Though depending on how your channels come up, you may need to manually edit the channel IDs
[21:25] <NOT_guru> or maybe just make a buddy sign up for me
[21:25] <NOT_guru> LOL
[21:26] <NOT_guru> oh  and of course last night I got sdlmame going on the box itself
[21:26] <NOT_guru> ( god I forgot how much I love galaga
[21:32] <NOT_guru> thatnks again for this link http://www.mythtv.org/wiki/Tmdb.pl   just readin over it
[21:33] <NOT_guru> looks pretty straight forward
[21:36] <NOT_guru> OH  I know... are you on the latest HDHOMERUN firmware (Release 20090806) or is there a specific FW I should run for Myth?
[21:40] <NOT_guru> ah sweet  hdhomerun has there own channel on irc
[21:40] <NOT_guru> wee\
[22:53] <NOT_guru> thanks again for all the info
[22:53] <NOT_guru> have a great night eveeryone


[02:30] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (focal-proposed) [1:4.0.6-0ubuntu1~20.04.1]
[03:01] <hallyn> say - there appear to be two versions of livecd-rootfs in https://launchpad.net/ubuntu/focal/+queue?queue_state=1  :)  the older one ( 2.664.22 vs  2.664.23) ought to be an easy reject?   though the signature doesn't check out on the newer one...
[03:01] <sarnold> o_O
[03:02] <hallyn> that would be jibel 's....
[03:02] <hallyn> i dunno :)
[03:06] <sarnold> hallyn: last week cjwa_tson said that you could only reject things from that queue if you had sru or queue admin memberships.. I'm curious, do you have the 'reject' button on that page? if so, did you expect to have that button on that page?
[03:07] <sarnold> hallyn: I've got one and I don't know if I've actually got a membership for that, or if that button is shown to all logged-in users, and just nothing happens if you click on it
[03:07] <sarnold> why is there always a tantalizing tangent to chase down when it's time to eod
[03:24] <hallyn> sarnold: no i do not have a reject button :)
[03:24] <hallyn> you must have a special badge :)
[08:16] -queuebot:#ubuntu-release- Unapproved: mesa (focal-proposed/main) [20.2.6-0ubuntu<IP_ADDRESS> => 21.0.1-2~20.04.1] (core, i386-whitelist, xorg)
[08:16] <tjaalton> sil2100: I got tired of waiting for the final mesa 21.0.x so here's the first version, which will be bumped later on ^
[08:17] <tjaalton> sil2100: plan being that we'll keep it in proposed until we have the final version tested and green
[08:17] <tjaalton> sil2100: there's also llvm-toolchain-12 which is prepwork for migrating mesa llvm-11 -> llvm-12
[08:18] <tjaalton> that's for both hirsute and focal
[09:52] <sil2100> tjaalton: oh, I like that plan! Looking in a minute
[10:29] <sil2100> tjaalton: ok, I'll look at llvm-12 now and then mesa
[11:11] -queuebot:#ubuntu-release- Unapproved: accepted llvm-toolchain-12 [source] (hirsute-proposed) [1:12.0.0-3ubuntu1~21.04.1]
[11:23] <tjaalton> sil2100: excellent, thanks
[11:23] -queuebot:#ubuntu-release- New binary: ceph [s390x] (impish-proposed/main) [16.2.4-0ubuntu1] (ubuntu-desktop, ubuntu-server)
[11:23] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-12 [source] (focal-proposed) [1:12.0.0-3ubuntu1~20.04.1]
[11:24] <sil2100> Ok, llvm-12 approved, we still need to look out for the binaries to appear for both series (hirsute for libclc-12)
[11:26] <sil2100> tjaalton: ah, so the mesa in the focal queue still uses llvm-11?
[11:26] <doko> bryce__: in the past we had transition trackers for php. why not for php8.0?
[11:38] <tjaalton> sil2100: yep
[11:39] <tjaalton> sil2100: so you're free to ack that, we can enable it in a later build
[11:40] <sil2100> tjaalton: ok, the upload looks good, althought there seems to be some cruft in the main directory! I see mesa_21.1.0-4.dsc and mesa_21.1.0-3.dsc inside the source
[11:41] <sil2100> tjaalton: could you clean those up and re-upload? I'll accept it then
[11:41] <tjaalton> oh bummer
[11:41] <tjaalton> yes
[11:41] <tjaalton> damn syncpackage
[11:43] -queuebot:#ubuntu-release- Unapproved: mesa (focal-proposed/main) [20.2.6-0ubuntu<IP_ADDRESS> => 21.0.1-2~20.04.1] (core, i386-whitelist, xorg)
[11:46] <sil2100> \o/
[11:47] -queuebot:#ubuntu-release- Unapproved: rejected mesa [source] (focal-proposed) [21.0.1-2~20.04.1]
[11:48] -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (focal-proposed) [21.0.1-2~20.04.1]
[12:08] <doko> sil2100, vorlon: please could you reset the cif2cell/i386 autopkg test? it's not in the release pocket, so shouldn't be marked as a regression
[12:38] -queuebot:#ubuntu-release- New binary: ceph [ppc64el] (impish-proposed/main) [16.2.4-0ubuntu1] (ubuntu-desktop, ubuntu-server)
[13:20] <doko> didrocks999, vorlon: what the status of tasksel, nor merged for a few years. looking because bfh-metapackages references some packages not built by tasksel
[14:48] <bryce__> doko I don't know, I miss the tracker too
[14:50] <bryce__> doko, although tbh it didn't help me get through the transition since it seemed things were in the wrong order.  But meanwhile I'm relying on the wki page I set up for tracking state of the various pieces.
[15:42] -queuebot:#ubuntu-release- New binary: ceph [amd64] (impish-proposed/main) [16.2.4-0ubuntu1] (ubuntu-desktop, ubuntu-server)
[15:46] -queuebot:#ubuntu-release- New binary: llvm-toolchain-12 [s390x] (focal-proposed/universe) [1:12.0.0-3ubuntu1~20.04.1] (i386-whitelist)
[16:11] -queuebot:#ubuntu-release- Unapproved: enigmail (bionic-proposed/universe) [2:2.1.6+ds1-1~ubuntu<IP_ADDRESS> => 2:2.2.4-0ubuntu<IP_ADDRESS>] (mozilla) (sync)
[16:11] -queuebot:#ubuntu-release- Unapproved: thunderbird (bionic-proposed/main) [1:68.10.0+build1-0ubuntu<IP_ADDRESS> => 1:78.8.1+build1-0ubuntu<IP_ADDRESS>] (mozilla, ubuntu-desktop) (sync)
[16:11] -queuebot:#ubuntu-release- Unapproved: jsunit (bionic-proposed/universe) [0.2.2-1~ubuntu<IP_ADDRESS> => 0.2.2-1~ubuntu<IP_ADDRESS>] (mozilla) (sync)
[16:13] -queuebot:#ubuntu-release- Unapproved: accepted jsunit [sync] (bionic-proposed) [0.2.2-1~ubuntu<IP_ADDRESS>]
[16:14] -queuebot:#ubuntu-release- Unapproved: accepted enigmail [sync] (bionic-proposed) [2:2.2.4-0ubuntu<IP_ADDRESS>]
[16:14] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [sync] (bionic-proposed) [1:78.8.1+build1-0ubuntu<IP_ADDRESS>]
[16:43] <doko> bryce: the tracker isn't auto-magic, it needs setting up manually
[16:48] -queuebot:#ubuntu-release- New binary: llvm-toolchain-12 [amd64] (hirsute-proposed/universe) [1:12.0.0-3ubuntu1~21.04.1] (i386-whitelist)
[16:50] -queuebot:#ubuntu-release- New: accepted jaraco.classes [sync] (impish-proposed) [3.2.1-1]
[16:50] -queuebot:#ubuntu-release- New: accepted jaraco.text [sync] (impish-proposed) [3.5.0-1]
[16:50] -queuebot:#ubuntu-release- New: accepted ceph [amd64] (impish-proposed) [16.2.4-0ubuntu1]
[16:50] -queuebot:#ubuntu-release- New: accepted ceph [s390x] (impish-proposed) [16.2.4-0ubuntu1]
[16:50] -queuebot:#ubuntu-release- New: accepted ceph [ppc64el] (impish-proposed) [16.2.4-0ubuntu1]
[16:51] <bryce> doko I gather as much, but it's not clear who to ask to do that.  There does not appear to be a way I can do it directly
[16:51] <bryce> doko, last time I emailed the mailing list and someone set it up for me, I was hoping that process would work here
[16:52] <doko> ok, I'm looking
[16:52] <doko> but isn't that a core-dev thing?
[16:54] <bryce> doko even if it is, I looked in the code repo and couldn't find like a config file or something where I could append "php8".  I also looked in wiki and the codebase for a howto.  I didn't spend a ton of time but it was not obvious how to do a PR to add to it
[16:55] <bryce> doko again, at least for me the tracker is of limited usefulness since it just shows what's not transitioned, and doesn't let me write in what the problems are that need fixed
[16:55] -queuebot:#ubuntu-release- New binary: jaraco.text [amd64] (impish-proposed/none) [3.5.0-1] (no packageset)
[16:55] <bryce> however it would be nice to have just for anyone needing a higher level view of state
[16:57] -queuebot:#ubuntu-release- New: accepted jaraco.text [amd64] (impish-proposed) [3.5.0-1]
[16:58] <doko> bryce: you don't need a config file, just add it in monitor/ongoing (now done)
[16:59] -queuebot:#ubuntu-release- New binary: jaraco.classes [amd64] (impish-proposed/none) [3.2.1-1] (no packageset)
[17:02] -queuebot:#ubuntu-release- New: accepted jaraco.classes [amd64] (impish-proposed) [3.2.1-1]
[17:03] <bryce> doko, do you mean at https://people.canonical.com/~ubuntu-archive/transitions/ ?  I see no place in the web ui for adding things
[17:04] <bryce> oh here it is - https://bazaar.launchpad.net/~ubuntu-transition-trackers/ubuntu-transition-tracker/configs/revision/871
[17:05] <doko> bryce: it's just a repo. no UI
[17:07] <bryce> doko, I'll remember this for next time, and will update it if I can commit there.
[17:22] -queuebot:#ubuntu-release- New binary: llvm-toolchain-12 [ppc64el] (focal-proposed/universe) [1:12.0.0-3ubuntu1~20.04.1] (i386-whitelist)
[17:24] <bryce> doko, just fyi this seems not very well documented.  There is a link at the bottom of https://people.canonical.com/~ubuntu-archive/transitions/ to a bzr repo, but not to the place where that config file needs added.  That would be useful if other core-devs need to figure out how to update that page.
[17:32] <sarnold> hallyn: aha! security team members have queue admin privs over -security pocket only -- I could reject uploads that involve that pocket but nothing else :)
[17:44] <hallyn> sarnold: :)
[17:44] <hallyn> i just - i want to "help out" with the queue, it's jsut not clear to me how to go about it.
[17:45] -queuebot:#ubuntu-release- New binary: thunderbird [s390x] (bionic-proposed/main) [1:78.8.1+build1-0ubuntu<IP_ADDRESS>] (mozilla, ubuntu-desktop)
[17:49] <sarnold> hallyn: my guess is reviewing the debdiffs, but that might not be what you're after, hehe
[17:51] <hallyn> sarnold: i'm happy to review debdiffs and test-build - in fact started doing that - but i don't knwo what to do with the output :)
[17:51] <hallyn> other than mention it here, but i don't think that does what is needed
[17:51] <sarnold> feedback on the bugs?
[17:51] <hallyn> maybe i should email some ubuntu-* mailing list?
[17:51] <hallyn> oh - they don't all have associated bugs.  For those that do, yeah, i could do that.
[17:51] <hallyn> Not sure anyone other than submitter will notice it, but i can try that
[17:51] <hallyn> but i.e. the youtube-dl one doesn't have a bug i don't think
[17:57] <sarnold> wow that's almost a year old
[18:09] -queuebot:#ubuntu-release- New binary: llvm-toolchain-12 [i386] (focal-proposed/universe) [1:12.0.0-3ubuntu1~20.04.1] (i386-whitelist)
[18:13] -queuebot:#ubuntu-release- New binary: thunderbird [ppc64el] (bionic-proposed/main) [1:78.8.1+build1-0ubuntu<IP_ADDRESS>] (mozilla, ubuntu-desktop)
[18:17] <bdmurray> hallyn: Are you talking about reviewing SRUs or reviewing backports in the queue?
[18:21] <bdmurray> hallyn: If it is reviewing SRUs you could let the SRU team member on duty for the day what you think of them.
[18:26] -queuebot:#ubuntu-release- New binary: thunderbird [amd64] (bionic-proposed/main) [1:78.8.1+build1-0ubuntu<IP_ADDRESS>] (mozilla, ubuntu-desktop)
[19:47] -queuebot:#ubuntu-release- New binary: thunderbird [i386] (bionic-proposed/main) [1:78.8.1+build1-0ubuntu<IP_ADDRESS>] (mozilla, ubuntu-desktop)
[19:56] <hallyn> bdmurray: how do i find out who that is? :)  i haven't seen it under /topic here
[20:04] <kryten> vorlon: Is it time yet to remind you of my pending CD Image merge proposal?  I appreciate that it may involve quite a bit of work to update sufficiently many past publishing trees along with it, but.. >_>
[20:06] -queuebot:#ubuntu-release- New binary: thunderbird [arm64] (bionic-proposed/main) [1:78.8.1+build1-0ubuntu<IP_ADDRESS>] (mozilla, ubuntu-desktop)
[20:21] -queuebot:#ubuntu-release- New binary: jaraco.collections [amd64] (impish-proposed/universe) [3.2.0-1] (no packageset)
[20:26] <bdmurray> hallyn: https://wiki.ubuntu.com/StableReleaseUpdates#Publishing
[20:32] <hallyn> bdmurray: thanks
[20:33] <hallyn> (marked in my notes file for next time i'm sitting down to look at srus,w hich should be soon)
[22:40] -queuebot:#ubuntu-release- New binary: thunderbird [armhf] (bionic-proposed/main) [1:78.8.1+build1-0ubuntu<IP_ADDRESS>] (mozilla, ubuntu-desktop)
[23:28] -queuebot:#ubuntu-release- New: accepted jaraco.collections [amd64] (impish-proposed) [3.2.0-1]


[12:35] <santa_> hi everyone
[12:36] <santa_> RikMills: futuresql still needs uploading: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/futuresql
[12:36] <santa_> needed for newer angelfish
[12:38] <RikMills> santa_: hi. will try to look later. does it have a 'needs packaging bug'?
[12:38] <santa_> RikMills: I don't think so, thanks for having a look :)
[12:39] <RikMills> santa_: https://bugs.launchpad.net/ubuntu/+bug/2021510
[12:39] -ubottu:#kubuntu-devel- Launchpad bug 2021510 in Ubuntu "[needs packaging] ktextaddons" [Wishlist, Fix Released]
[12:40] <RikMills> needs a bug like that
[12:40] <RikMills> referenced in the intila release to ubuntu line
[12:40] <RikMills> *initail
[12:40] <RikMills> ffs
[12:41] <RikMills> lol
[12:41] <santa_> I know, I don't have time atm, but maybe later
[12:41] <santa_> lol @ typos
[12:42] <RikMills> ok
[12:43] <santa_> maybe you want to reconsider your keyboard? XD https://switchandclick.com/mechanical-keyboard-switch-guide/
[12:43] <santa_> I didn't know there was so much "science" behind mechanical keyboards
[12:44] <RikMills> hmm
[23:17] <santa_> RikMills: https://bugs.launchpad.net/ubuntu/+bug/2043147
[23:17] -ubottu:#kubuntu-devel- Launchpad bug 2043147 in Ubuntu "[needs packaging] futuresql - database framework for Qt" [Undecided, New]


[00:51] <Takyoji> Meeting tonight?
[00:59] <tonyyarusso> hmm, we should, but I don't think we have an agenda yet and I neglected to announce it...should we consider trying a different day so we can push for more people to know about it in advance?
[01:04] <katakaio> Hey team - long time, no see
[01:05] <katakaio> Normally I work during our monthly meeting time . . . are we still meeting right now?
[01:07] <Takyoji> ahh
[01:08] <katakaio> Was that an "ahh" as in surprise and alarm?
[01:12] <Takyoji> tonyyarusso: hmm, we should, but I don't think we have an agenda yet and I neglected to announce it...should we consider trying a different day so we can push for more people to know about it in advance?
[01:13] <Takyoji> (as a text quotation; not a statement directed towards tonyyarusso)
[01:15] <katakaio> If that makes more sense, that sounds good. I feel bad for working right when our meeting is . . . :(
[01:16] <tonyyarusso> What would be better times for you?
[01:22] <katakaio> Hmm . . . let's look.
[01:23] <katakaio> Sunday nights and Tuesday nights are good
[01:32] <tonyyarusso> fair enough, I could probably do either of those
[01:32] <katakaio> Cool . . . we'll see what other people have to say about that
[01:33] <katakaio> I'll just plan on being in the channel those evenings and we'll see who joins us
[01:33] <katakaio> brb
[04:26] <Takyoji> I almost completely forgot again
[04:26] <Takyoji> For any of the installfests, we should also do keysigning.
[21:29] <Takyoji> So today then, or Sunday?