[00:58] <karora> chilts: I'm trying to use the latest cil from Debian Unstable.
[00:59] <chilts> righto
[00:59] <karora> When I add an issue or edit an issue the stuff I type into my editor does not seem to end up in the issue :-(
[00:59] <chilts> hmm
[01:00] <chilts> so after cil add, does it complain, create the file (with nothing in it) or create the file with something (but not the right thing) in it?
[01:01] <chilts> which version? v0.07?
[01:01] <karora> The issue is created, but there's no description.
[01:02] <karora> It just says "Description ..." at the bottom of it.
[01:02] <karora> Yeah, this is 0.07.00
[01:02] <karora> From Debian.
[01:02] <chilts> so you had deleted that line and put your own description there?
[01:03] <karora> No, not yet.
[01:03] <chilts> then the description was saved as 'Description ...'
[01:03] <chilts> I should change that placeholder text to 'Description (change me) ...'
[01:03] <karora> When I went "cil add blah blah blah blah" an editor came up with an empty document, so I typed my description into that.
[01:03] <chilts> it doesn't do anything with the blah blah blah
[01:04] <karora> Was that editor supposed to be displaying the whole issue?
[01:04] <karora> What's your normal workflow for creating an issue?
[01:04] <chilts> so 'cil add' doesn't take anything on the command line
[01:05] <karora> The "blah blah blah" is now the summary for the issue, but other than "vi issues/whatever" I can't
[01:05] <karora> OK.
[01:05] <karora> That's not what the man page says.
[01:05] <chilts> I usually go "cil add --commit"
[01:05] <chilts> the type in the title and the description
[01:05] <chilts> (sorry title=summary)
[01:07] <chilts> not sure I know where that is, maybe that's been added by someone else for Debian
[01:07]  * chilts will check
[01:08] <chilts> what does the line of the manpage say, and I'll grep for it?
[01:08] <karora> OK.The man page was probably something fmarier did.
[01:08] <karora>        add [--mine] [summary]
[01:08] <karora>            Adds an issues after you have edited the input.  Text passed after 'add' will be used as the bug summary line.
[01:08] <chilts> yeah, do a 'cil --help' and you can see the add command takes nothing afterwards
[01:10] <karora> I noticed that.
[01:10] <chilts> karora: as it turns out, I no longer maintain cil (really) and asked a guy if he wanted to take over development (though I heard nothing back from him after that)
[01:10] <chilts> so yeah, I don't really use it anymore :)
[01:10] <chilts> sometimes I think I should
[01:10] <karora> And I thought "Surely I can pass in an issue title on the command line", so I checked the man page :-)
[01:10] <karora> Heh.
[01:10] <chilts> yeah, that would probably be a good idea
[01:10] <karora> OK.
[01:11] <chilts> lols ... in the code, it _does_ do the summary from the command lien :)
[01:11] <karora> I was just starting to track issues for a new project and it seemed to me like it would be a good way to deal with "confirmed issues that we know need fixing"
[01:11] <chilts> heh, I never knew
[01:11] <karora> Yeah.
[01:11] <karora> That bit actually worked.
[01:11] <chilts> seems to work with my version here
[01:12] <karora> But then it threw up this empty editor window in front of me.
[01:12] <karora> EDITOR=gvim
[01:12] <chilts> if you say it worked, then an empty editor would mean that it didn't?
[01:13] <karora> No, an empty editor probably means that the temp file the editor was supposed to be editing has a different name, or something like that.
[01:13] <chilts> can you try it with EDITOR=vim and see if that works?
[01:13] <karora> Yeah, OK.
[01:13] <chilts> yeah, you're probably right
[01:13] <chilts> mine works with vim and emacs
[01:14] <karora> Yep.
[01:14] <karora> Works with EDITOR=vim
[01:14] <chilts> cool
[01:14] <chilts> not sure about gvim then
[01:14] <chilts> sorry
[01:14] <karora> So that's an acceptable workaround for me, and I can file a bug against the Debian package :-)
[01:15] <karora> Which $SOMEONE can push to the upstream...
[01:15] <karora> And the normal service of this channel can be returned to witnessing the passing of the days.
[01:15] <karora> afternoon
[01:16] <chilts> hehehe
[01:16] <chilts> afternoon
[01:18] <karora> Amusingly the --commit option is also *not* documented in the manpage.
[01:19] <karora> or the --help :-)
[10:28] <Bacta> Hai
[18:41] <ibeardslee> morning
[18:57] <Atamira> mornin
[19:20] <ol> morning
[19:26] <ajmitch> morning
[19:51] <karora> morning :-)
[19:52] <karora> And what a beautiful, calm, cloudless morning it is!
[20:00] <mwhudson> morning
[20:21] <Atamira> nice and warm here..cloudy.but still a lovely day
[20:30] <thumper> morning
[21:53] <snail> is there something special about https://launchpad.net/ubuntu/jaunty/+package/amaya ? it doesn't seem to be in the archives for installation...
[21:53] <ajmitch> it's jaunty?
[21:53] <ajmitch> which is now end-of-life
[21:56] <ajmitch> it was removed from debian & subsequently ubuntu due to numerous bugs & security issues
[22:09] <snail> oh, ok, thanks


[02:35] <ScottK> mfisch: change it from arch: all to arch: powerpc.
[02:37] <mfisch> ScottK: that was the fix I assumed, if it's worth doing
[02:38]  * ScottK did that for something and it did work.
[07:55] <dholbach> good morning
[08:32] <iulian> Morning dholbach.
[08:33] <dholbach> hi iulian
[09:09] <geser> ScottK, mfisch: but wouldn't this make the package (here  slof; powerpc firmware to use with qemu) unavailable to non-powerpc?
[09:16] <Laney> you'll still be able to install it using multi-arch
[09:30] <geser> but only if you add "powerpc" to your sources, right?
[09:31] <Laney> yeah, you'll have to enable it
[09:31] <Laney> better than no package though
[09:32] <geser> true
[10:17] <Laney> hmph
[10:23] <Laney> anyone using raring & lighttpd? userdir is broken on it here
[10:24] <Zhenech> debian stable here :P
[10:24] <Laney> ah
[10:24] <Laney> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680755
[10:24] <Laney> silly silly silly
[10:31] <Nafallo> hi. anyone loooking at this bug at all? https://bugs.launchpad.net/ubuntu/+bug/262433
[10:32] <smartboyhw> Wow it dates back from Hardy....
[10:33] <smartboyhw> Nafallo, all the wiki links are invalid in the bug
[10:33] <smartboyhw> So no one knows where the source code is...
[10:35] <Nafallo> http://wiki.sipfoundry.org/display/sipXecs/Home
[10:36] <smartboyhw> Nafallo, thx
[10:36] <Laney> someone please tell me how to make arch:all reprepro uploads work
[10:36] <Laney> using 'reprepro include'
[10:37] <Nafallo> and I believe here: http://download.sipfoundry.org/pub/sipXecs/
[10:39] <Nafallo> https://www.calivia.com/bk/sipx/sipx-on-debian
[14:36] <mfisch> geser: that's what I was thinking, the package is really an all since it's for qemu but needs to be built on PPC. Hence I'm not doing anything with it.
[19:57] <TheLordOfTime> are universe sync requests still accepted for raring?
[20:03] <micahg> TheLordOfTime: yes
[20:04] <TheLordOfTime> thanks.
[20:07] <TheLordOfTime> micahg, is it normal for requestsync to error out for newly-uploaded-to-experimental packages?
[20:07] <TheLordOfTime> s/newly/recently/
[20:07] <micahg> possibly
[20:07] <micahg> did LP pick it up yet?
[20:08] <TheLordOfTime> not sure, the upload was 10:07 UTC today.  (it was really early morning for that one)
[20:08] <TheLordOfTime> (upload to Debian)
[20:08] <TheLordOfTime> (early morning relatively speaking, ~05:10 here)
[20:09] <TheLordOfTime> if i use  -C in requestsync, will it ask me to provide the relevant changelogs if it can't pull the data?
[20:09] <TheLordOfTime> its a minor change to the package, but the sync'll close LP bug 1085742
[20:10] <TheLordOfTime> (the Debian "compromise" was to set a recommends on the g++ compiler)
[20:12] <TheLordOfTime> ... yep, requestsync -C ... worked and is asking me to fill in the changelog by hand.  *grabs data from packages.debian.org*
[20:13] <TheLordOfTime> ... stupid encoding issues...
[20:16]  * jtaylor would have left the bug at won't fix
[20:16] <TheLordOfTime> okay, so apparently PuTTY can't work with the character "ä" correctly.
[20:16]  * TheLordOfTime kicks his  computer
[20:17] <tumbleweed> TheLordOfTime: https://wiki.ubuntu.com/RaringRingtail/ReleaseSchedule up until Feature Freeze. Then it starts needing good reasons and paperwork
[20:17] <TheLordOfTime> ah, well then.  :P
[20:18]  * TheLordOfTime notices emails stating his system's imploding.
[20:18] <TheLordOfTime> ... oops
[23:07] <psusi> valgrind complains about an invalid read of size 8 then says: Address 0x6bfdb98 is 8 bytes inside a block of size 12 alloc'd.  If it's 8 bytes inside a block of 12, how is that invalid?
[23:10] <jtaylor> 8p8 e 16
[23:11] <jtaylor> 8+8 = 16, block is only size 12
[23:11] <jtaylor> psusi:
[23:11] <jtaylor> it reads 4 byte to much
[23:22] <psusi> jtaylor: why are you adding 8 to 8?
[23:23] <jtaylor> 8 byte read 8 byte into a block of size 12
[23:23] <jtaylor> if the block starts at 0 the read is starts at 8 and goes to 16
[23:24] <jtaylor> e.g. *(double *)(0x0+8)
[23:24] <psusi> OHH... I interpreted that as just 8 bytes somewhere inside the 12 byte block, it means it starts 8 bytes into it


[00:00] <genii> Probably some fglrx bug then
[00:01] <Nikon> well, i did send it in for a broken fan a while back
[00:01] <Nikon> maybe its that
[00:01] <Nikon> but also
[00:02] <Nikon> my computer uses some program to control the fan
[00:03] <genii> aticonfig  has some option to directly control the fan
[00:04] <Nikon> it wasnt the card fan, it was the main cooling fan
[00:05] <genii> Ah. Since it's EFI I guess no ACPI or such. Unfortunately I don't know much about EFI/UEFI
[00:07] <Nikon> yea
[00:07] <genii> Sorry not to be of more help.
[00:07] <Nikon> No worries c:
[00:07] <Nikon> genii
[00:08] <Nikon> how much space should i give ubuntu?
[00:08] <Nikon> i have 106 gb free at the moment
[00:08] <genii> So probably 80-100
[00:09] <Nikon> correction
[00:09] <Nikon> lets see
[00:09] <Nikon> i just cleaned out my hdd again
[00:09] <Nikon> 122
[00:09] <Nikon> gb
[00:10] <Nikon> er 126
[00:10] <genii> The settings if you choose Guided mode are usually the optimal for what you have
[00:10] <Nikon> okie dokie
[00:10] <genii> At any rate, I need to leave work :)
[00:10] <Nikon> and it should install beside windows right?
[00:10] <Nikon> oh okay
[00:10] <Nikon> thank you for the help
[00:10] <genii> You're welcome, and good luck!
[00:10] <Nikon> and have a good rest of your day!
[00:10] <Nikon> thank you :3
[00:11] <genii> :)
[00:30] <Nikon_m> Hey, I'm back
[00:30] <Nikon_m> So my laptop is having some overheating issues with 12.04.3
[00:31] <Nikon_m> So much so I can't get the live cd working long enough to install ubuntu
[06:17] <BobJonkman1> If Nikon_m comes back, tell him I've had the same problem. I had to pop the cover off the laptop (non-trivial!) to remove the encrusted dirt on the heat-sink grille. Now I have enough fur to make my own kittens!
[21:58] <azend> Ubuntu Hour Guelph in an hour
[21:58] <azend> If you're in the area, c'mon out


[19:33] <astraljava> Hi gang, we have a slight problem with Xubuntu, and its default terminal, xfce4-terminal. When you hit F1 for Help, and you still have Firefox as the default browser, you're facing this error message: http://astraljava.kapsi.fi/xfce4-terminal_Help-F1_firefox.png
[19:33] <astraljava> With chrome, it works as expected.
[19:34] <astraljava> What sort of problem do you think we're dealing with? Does that look like a proper way to launch the file into the browser from firefox's POV?
[19:34] <astraljava> Should I test with more browsers?
[19:35] <micahg> astraljava: that's weird, it should fail for both as it never gets to the browser
[19:36] <astraljava> micahg: Yeah but I tested it both on Studio and Xubuntu, works with both if chrome is set as the default browser. Doesn't, if FF is.
[19:37] <micahg> astraljava: it should probably be escaping the url, try to call that manually with the URL in single quotes
[19:37] <astraljava> But I won't argue it being the proper way to do it, I haven't looked that deep into the code, yet.
[19:38] <astraljava> micahg: Yeah, with: /usr/bin/firefox 'file:///usr/share/doc/xfce4-terminal/C/index.html#' it launches the browser correctly.
[19:39] <micahg> and without the quotes it fails?
[19:40] <astraljava> Hmm... no, it works then, too. Also works directly from xfce4-terminal with Opera set as default.
[19:42] <astraljava> There's a bug about this on LP, bug #964483
[19:42] <ubot2> Launchpad bug 964483 in exo "Terminal help is inaccessible" [Undecided,New] https://launchpad.net/bugs/964483
[19:43] <astraljava> But I'm unsure whether this is actually an exo bug, as firefox so far is the only browser where it fails.
[20:02] <astraljava> Wonder if it actually is an exo problem, when firefox is set as default, I'm facing with "Error: No running window found" in the debug log file.
[20:19] <cousin_luigi> PepperFlash works on Chromium 19: now I'm happy:)
[20:25] <micahg> cousin_luigi: did you end up with a local build?
[20:32] <cousin_luigi> micahg: yes
[20:33] <cousin_luigi> micahg: I couldn't wait:)
[20:33] <micahg> cousin_luigi: ok, I'll let you know when the PPAs are active again
[20:35] <cousin_luigi> micahg: by the way, do you know if there's sensible data in the bazaar config dir ?
[20:35] <micahg> cousin_luigi: which dir?
[20:35] <cousin_luigi> .bzr
[20:35] <cousin_luigi> micahg: I found it in a package and wondered if I had to tell the maintainer
[20:36] <cousin_luigi> sensitive*
[20:37] <micahg> hmm, there shouldn't be a .bzr dir except in a checkout
[20:39] <cousin_luigi> I assume he included it by mistake, somehow...
[20:39] <micahg> cousin_luigi: which package wherẻ
[20:41] <cousin_luigi> micahg: a PPA source http://ppa.launchpad.net/webupd8team/java/ubuntu/pool/main/o/oracle-java7-installer/oracle-java7-installer_7u3-0~webupd8~9.tar.gz
[20:41] <cousin_luigi> not your concern I suppose:)
[20:41] <micahg> yeah, not our problem


[03:43] <cmaloney> http://openmetalcast.com/2017/04/10/open-metalcast-episode-152-death-by-algorithms/
[10:23] <rick_h> morning
[13:17] <cmaloney> morning
[13:19] <brousch__> Correct
[13:19] <shakes808> morning
[14:03] <widox> heyo
[14:04] <cmaloney> btw: MUG tonight.
[14:04] <cmaloney> Me talking about an Introduction to Debugging in PYthon
[14:05] <cmaloney> and Tony Bemus talking about firewalls
[14:05] <Zimdale> Trying out your talk for Pcon?
[14:05] <cmaloney> Yep
[14:05] <rick_h> cmaloney: awesome!
[14:05] <rick_h> cmaloney: you submit to #pyohio?
[14:05] <cmaloney> Not yet
[14:07] <cmaloney> Thinking about it though
[14:07]  * rick_h nudges cmaloney poke poke
[14:07] <cmaloney> it's only been 10 years since I've been going. I might as well start now
[14:07] <rick_h> lol
[14:07] <rick_h> something like that
[16:31] <cmaloney> http://decafbad.net/2017/04/11/regrets/
[23:05] <cmaloney> https://plus.google.com/b/109767935477156086705/events/c45ep2a4n0couhokqcunq4u58d8 < Mug Meeting


[07:37] <NicksSpleen> Hi. I always install gnome right after I install ubuntu. I was just wondering if there are any cons/considerations to using this disto instead?
[11:20] <pascalts> Hay, I have got a little problem with UbuntuGNOME 13.0 amd64. Everytime I open the menue and search somethin (e.g. firefox) after 1 sec or so the whole system freezes for 1 second. After that the system runs normal. I have an AMD 6-core CPU & an AMD Graphic-Card with the last drivers from AMD installed. May you help me?
[11:20] <pascalts> *13.04
[11:25] <pascalts> here is a screen-record: https://www.dropbox.com/s/76wxvtydp78tacn/VID_20130506_132156.3gp
[19:21] <atrus> so, with 13.04 + gnome3ppa + staging ppa.... how does one get into the "classic" gnome desktop? Ie, the new gnome-shell based on in 3.8? (if I understand this correctly)
[19:24] <camelinahat> atrus, It's a separate package just trying to find the name again (not installed by default)
[19:25] <atrus> hm. there is a gnome-session-fallback version 3.8.x in the ppas...
[19:26] <atrus> but ... huh. that still seems to want gnome-panel, which doesn't exist in 3.8.....
[19:31] <camelinahat> Ah it may be that you need the 'testing' PPA as well. Which I'd really not recommend on any production machine.
[20:57] <jaysonr> atrus: if you upgraded to 3.8 from the PPA install 'gnome-shell-extensions' and then you will have GNOME Classic as an option at logon
[20:57] <atrus> jaysonr: ah, of course, that makes sense.
[20:58] <atrus> hard to get from A to B as a user of course. maybe ubuntu-gnome-desktop should depend on that?
[21:01] <jaysonr> atrus: it should at least be better documented, I think. I had to google around to figure it out, and then ended up not even liking it and using Shell instead :-/
[22:13] <atrus> also, is it possible to get the monitor-edge-pressure things that are supposed to work with gnome3.8 to work under 13.04?
[22:30] <darkxst> atrus, it is, but not easily
[22:30] <darkxst> you need to install x-staging and then rebuild mutter
[22:31] <atrus> hm. not so-so bad.
[22:31] <darkxst> https://launchpad.net/~canonical-x/+archive/x-staging
[23:00] <atrus> neat. that does indeed seem to work right.


[05:44] <zeises> someone please help me with this bug
[05:45] <zeises> there is no file transfer indicating at the top of window after installing 17.10
[14:43] <p7f> hi: i've just updated to ubuntu budgie 17.04. I've noticed that now if i'm in a directory in the file manager, and write a letter, it starts a search instead of going to the first file starting with that letter... how can i revert this?
[15:37] <fossfreedom> p7f, as far as I know that is a nautilus feature.


[01:22] <Ahmuck-Sr> good evening.  are there any "gotcha's" i should be aware about doing a 81.0 to 9.04 upgrade on a ltsp server?
[01:34] <Ahmuck-Sr> has anyone done a dist upgrade?
[02:36] <Ahmuck-Sr> well, here goes nothing.  /me hopes nothing breaks
[03:09] <Ahmuck-Sr> wow, upgrade is 900+ megabyte download
[03:10] <Ahmuck-Sr> i'm suprised no one has come up with a upgrade tool that backs up configuration and then uses the release as the upgrade cd
[18:06] <Ahmuck-Sr> upgrade broke some things
[18:15] <Ahmuck-Sr> do i need to rebuild the ltsp client after upgrading to 9.04?
[19:47] <jc2it> I have VIAChrome9 HC3 Integrated Graphics in an HP t5545 thin client. I am trying to get it to pxe boot from Ubuntu 8.04 LTS + LTSP, but I think I have a video driver problem. What driver do I use for the VIAChrome9 HC3 Integrated Graphics chipset?
[19:47] <jc2it> This is the lts.conf that I have been playing with:
[19:47] <jc2it>         [default]
[19:47] <jc2it>                 XSERVER = openchrome
[19:47] <jc2it>                 X_VIDEO_RAM = 16438
[19:47] <jc2it>                 LDM_DIRECTX=True
[19:47] <jc2it> #       HP t5545 TC
[19:47] <jc2it>         [00:22:64:28:ad:68]
[19:47] <jc2it> #               XSERVER = openchrome
[19:47] <jc2it> #               X_VIDEO_RAM = 65752
[19:47] <jc2it>                 SCREEN_07=ldm
[19:47] <jc2it>                 SCREEN_02=shell
[19:47] <jc2it> #               SCREEN_03=wy60
[19:47] <jc2it> #               TELNET_HOST = <IP_ADDRESS>
[19:47] <jc2it> Results:
[19:47] <jc2it>    Ubuntu boots, shows the progress bar and then starts BLINKING the screen on and off.
[19:48] <jc2it> The default section works great for my Neoware C50 and 16mb of shared video RAM.
[19:48] <HedgeMage> jc2it: Pastebins are your friend.
[19:49] <HedgeMage> That said, I'm not much help with your config, I'm afraid I have little experience pxe-booting, and even less (meaning none) with that graphics chipset :/
[19:49] <HedgeMage> sorry :(
[20:34] <Ahmuck-Sr> after update last evening, my hp laserjet 1200 printer is spitting out garbage
[20:37] <Ahmuck-Sr> fixed, deleted all printers and added back
[21:58] <jc2it> http://pastebot.ltsp.org/311


 wxl: I could solve the problema I had, db_helper needed python2 tools. But the way to dela with .desktop is giving me a hedach.
[16:50] <wxl> @HMollerCl did you figure it out?
 wxl: nope
 apaprently is a combination between setup.cfg wit i18n_build and debian/*.install
[16:51] <wxl> huh
[16:52] <wxl> i thought if the file was there in the source, it's just a simple matter of listing it in .install
 the way I'm guessing is that the setup.cfg takes the .desktop.in and convert it to .desktop
[16:53] <wxl> maybe that's if an only if you use the .in format
 the other option is that dpkg-buildpackage needs to be run with othe roptions
 but I couldn't found if tehre is somewhere an idea of how it is use for every package. update-manager and software-properties use the .desktop.in
[16:58] <wxl> i don't know if it's still a thing but there's an #ubuntu-packaging
[17:01] <wxl> there's also #packaging on oftc. mainly for debian but still
 will try to reach them, I can't from here cause proxy blocks irc
 wxl: this is what software-poperties and update-manager use https://launchpad.net/python-distutils-extra
 wxl: I ended up doing with pure .desktop and .install no distutils, no .in
 Have one question with the copyright file, which one shoudl I use?
[19:17] <wxl> @HMollerCl copyright files are the hardest part of the whole thing, but are you asking which license you should use for what you created?
 Yes
[19:20] <wxl> @lynorian: is the master branch what builds on manual.l.m?
 19.04 is now and I wasn't the one that switched it actually
[19:21] <wxl> so i should push changes to 19.04?
 yes you have changes :D
 but also get them in master as that is what will conitue and eventually be branched to 19.10 stuff
[19:26] <wxl> my main thing was to get rid of the 18.10 language in the updating section
 ok
 sorry I didn't notice that
[19:30] <wxl> should i bother or do you want to do it?
[19:30] <lynorian> I don't really want to do that been a bit busy
[19:30] <wxl> k
[19:31] <wxl> how do you usually deal with making the changes on both branches?
 usually make changes in master and then merge master to 19.04
[19:32] <wxl> is that just `git checkout 19.04 && git merge master`?
 yes
[19:44] <wxl> @lynorian: can you add me to the documentation team?
[19:45] <lynorian> on phab?
[19:45] <wxl> yeah
[19:45] <wxl> it's the only way i can push
[19:45] <wxl> and only project members can add
[19:45] <wxl> i can probably force it thruogh the back end but i'd have to dig for it
[19:46] <lynorian> or others could use arc if we really wanted to
[19:46] <lynorian> but I trust you enough
[19:47] <lynorian> and done
[19:47] <wxl> thx
[19:49] <wxl> ok changes made. still needs a new screenshot to not be entirely 18.10 specific but c'est la vie
[19:52] <wxl> does the manual get autobuilt after every push? doesn't seem like it. i also don't see a crontab on the phab machine
 @wxl [<wxl> does the manual get autobuilt after every push? doesn't seem like it. i al …], It's in its own container
 And yes, it's on hourly cron.
[20:02] <wxl> ugh i keep forgetting abotu the containters
 containters
 wxl, I think your keyboard needs reprogrammed
 @teward001 [wxl, I think your keyboard needs reprogrammed], So does yours :P
 wxl: I manage to get the .deb package and it's working
 I'm only getting problemas during it's installation
 https://paste.ubuntu.com/p/c8yzDHw24W/
 in plain english https://paste.ubuntu.com/p/cKsbpNwRND/
[22:18] <wxl> @teward001 you need reprogrammed
[22:19] <wxl> oh wow jeez i have no idea!
 that's when I instyall with "dpkg -i" any other option?
[22:25] <wxl> no i mean that's the way to do it but it seems that some call to py3compile isn't behaving right
[22:26] <wxl> that seems to be a postinst script?
 yes
 THings get installed
 might be some signing issues?
[22:27] <wxl> link me to that script please
 since I created the package with "dpkg-buildpackage -us -uc -tc"
 @wxl [<wxl> link me to that script please], To which script?
[23:55] <wxl> @HMollerCl postinst
 It should be in the .deb?
[23:58] <wxl> probably but it's probabl/y easier to just show me the code :)


[16:59] <mparillo> Looks as if the Lunar Beta was marked as ready. I have a draft news post (needs links to the larger Ubuntu Beta) and wiki (https://wiki.ubuntu.com/LunarLobster/Beta/Kubuntu) post ready for review
[18:06] <ahoneybun[m]> I don't see anything from Ubuntu about the beta.
[18:09] <ahoneybun[m]> Found the email to the list: https://lists.ubuntu.com/archives/ubuntu-announce/2023-March/000288.html
[18:09] <ahoneybun[m]> Added it to the post.
[18:10] <ahoneybun[m]> Maybe this: https://discourse.ubuntu.com/t/lunar-lobster-release-notes/31910
[20:24] <mparillo> Thank you. I removed the Testing Week reference from the wiki post. It seems as if testing week came and went unremarked.