[15:15] <k1l> there is a settings in the system settings to enable natural scrolling for the touchpad.
[15:16] <comptekki> Are there any fixes for natural scrolling and no sleep on lock screen in gnome ubuntu 17.04?
[15:16] <comptekki> natural scrolling is turn on, but has no effect
[15:17] <comptekki> turn/turned
[15:28] <ducasse> comptekki: might want to read through this: http://askubuntu.com/questions/91426/reverse-two-finger-scroll-direction-natural-scrolling
[15:39] <comptekki> ducasse, ok - will look


[01:41] <snadge> i think i've got a fairly simple one i was hoping someone with some more kernel experience could help me with
[01:41] <snadge> yeah its a problem only with recent kernels and virtualbox.. but still
[01:41] <snadge> https://forums.virtualbox.org/viewtopic.php?f=7&t=47078
[01:42] <snadge> exactly the same oops as this guy has.. except hes using some 3.2 rc and mint.. im using ubuntu precise, and latest mainline nightly (3.3.0 #201203250407)
[01:42] <snadge> code dissassembly is the same.. and the same call trace
[01:43] <snadge> id like to know how to find module_put .. and the section of code that disassembly is referring to
[01:50] <snadge> no source packages for the mainline nightlies?
[01:51] <snadge> i suppose i have to use git for that
[02:00] <snadge> git://kernel.ubuntu.com/ubuntu/linux.git  <-- that is mainline ?
[02:17] <snadge> *tumbleweed* .. i wonder if i'll finish this git clone before anyone says anything
[06:51] <bullgard4> [Ubuntu 11.10 GNOME Shell <IP_ADDRESS>] Super key > Applications > System tools > Power statistics > Prozessor > Wake-up processes lists 2 types of wakeup processes: i.) Symbol is a rhombus, ii.) Symbol is a gear. What is the name of these two types?
[07:00] <RAOF> bullgard4: App vs IRQ handler, apparently.
[07:25] <smb> morning
[07:25] <ppisati> moin smb :)
[07:27] <smb> Just for forgetting to upgrade on Friday... now its about 230M... at least nothing that wants to get removed...
[07:28] <ppisati> did you reboot already?
[07:28] <ppisati> is it safe?
[07:28] <smb> no just started the dist-upgrade
[07:28] <smb> will let you know in a bit...
[07:29] <ppisati> 135 pkgs here...
[07:29] <ppisati> wtf?!?!? we still have evolution and banshee around, did we sack them in this release?
[07:29] <ppisati> *didn't
[07:30] <snadge> enjoy unity 5.8 ;)
[07:31] <snadge> for some people it causes a blank desktop upon login.. hehe
[07:31] <smb> ppisati, It probably won't get deleted when you got them already
[07:32] <ppisati> doh!
[07:32] <ppisati> snadge: unity2d?
[07:32] <ppisati> snadge: is it safe?
[07:32] <RAOF> unity2d works; and after a unity --reset, so should 3d.
[07:32] <ppisati> smb: btw i still have emacs around, but that's my heritage...
[07:33]  * ppisati uses only 2d, cool...
[07:33]  * smb pretends not to know those 5 letters... ;-P
[07:33] <ppisati> well, personally i really like unity (design-wise)
[07:34] <ppisati> is all i liked from windowmaker + a status bar with all the indicators&c
[07:34] <ppisati> btw, did they revert the secondo screen+second launcher thing?
[07:35] <RAOF> ppisati: It's now configurable in the “Displays” capplet; there's a toggle for on-all-screens/a drop box for which screen you want it on.
[07:36] <ppisati> RAOF: nice
[07:45]  * ppisati -> reboot
[07:46]  * smb reboot
[07:47] <snadge> unity2d is good
[07:51] <ppisati> so far so good...
[07:59] <smb> So far... as long as you are through the blank (or background only) screen, unity --reset segfaulting and compiz crashing parts...
[07:59] <ppisati> ouch
[08:29] <snadge> i ran unity --reset from console myself
[08:29] <snadge> but my work pc.. didnt need to.. so maybe its related to fglrx
[08:30] <snadge> work pc is intel
[08:30] <smb> This machine is on ati/radeon
[08:30] <snadge> possibly related to amd/ati then
[08:31] <smb> Running reset from console just hang, repeating went a bit further and finally running it again from gfx resulted in a segfault of the command.
[08:31] <snadge> thats pretty harsh
[08:31] <smb> (not really making one trust in its ability to fix things... ;-P)
[08:31] <snadge> maybe it'll work now
[08:32] <smb> I am up and running right now
[08:32] <smb> Fingers crossed
[08:32] <snadge> yeah it must be a new compiz setting or an old one that glitches with the update
[08:32] <snadge> theres a launchpad bug for it.. i dont have the link offhand
[08:34] <snadge> https://bugs.launchpad.net/unity/+bug/963633
[08:34] <ubot2> Launchpad bug 963633 in unity "Unity 5.8: Login to blank screen (all black or just wallpaper)" [Critical,In progress]
[08:34] <snadge> that one has the most heat
[08:34] <smb> Yep, sounds like it.
[08:34] <snadge> launchpad is great now that heaps of people use ubuntu
[08:35] <snadge> bug affects 56 people :P
[08:35] <snadge> reported 2 days ago
[08:35] <smb> And someone has assigned it at least. Well, there was a weekend in between... :)
[08:36] <snadge> 14 duplicates tagged already
[08:37] <snadge> i know this isnt a kernel problem.. but i *really* want someone to fix this
[08:37] <snadge> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/770283
[08:37] <ubot2> Launchpad bug 770283 in compiz-core "[fglrx]title bar does not update on non-maximized windows" [Medium,In progress]
[08:38] <smb> snadge, Then you may tell "them" in #ubuntu-unity... maybe
[08:40] <snadge> tried that ;) but yeah.. i will remind them hehe
[10:49] <fsancho> Hi all. Is there any good reason to not activate "CONFIG_DRM_GMA500=m", "CONFIG_DRM_GMA3600=y" and "CONFIG_DRM_GMA_600=y" in config for 3.3 kernel?
[10:59] <snadge> yes.. the universe will explode if you do
[11:00]  * ogra_ thought the universe does that anyway since the big bang
[11:01] <snadge> right.. but little did you know, thats what caused the big bang
[11:02] <snadge> some chose those specific kernel options.. and boom.. here we are now ;)
[11:02] <ogra_> ah, k ... thats the physics lesson i missed at school then :)
[11:03] <fsancho> i mean, these options are deactivated in 3.3 builds from kernel.ubuntu.com. Is there a good reason for that? Is there a way to ask the manager of the site to activate it?
[11:04] <snadge> well i dont know who manages the daily builds on kernel.ubuntu.com
[11:04] <snadge> but i can tell you that more often than not.. those builds suck
[11:05] <snadge> i tried out the radeon/drm stuff yesterday.. granted with experimental options and mesa from git
[11:06] <fsancho> snadge: My builds with make-kpkg doesn't look as good as those builds
[11:06] <snadge> but still.. it caused my computer to reboot after a few minutes of playing minecraft ;)
[12:08] <bullgard4> RAOF: Thank you very much for your help.
[12:23]  * ppisati -> lunch
[13:20] <cking> mjg59, what's the current state of play with the patch "PCI: ignore pre-1.1 ASPM quirking when ASPM is disabled" - you mentioned you were working on this: https://lkml.org/lkml/2012/3/19/408
[13:21] <mjg59> cking: Haven't been able to reproduce, nobody's sent me a bug report containing any worthwhile information
[13:24] <cking> mjg59, that's a bummer, we're seeing some machines hang with this patch, bug 961482
[13:24] <ubot2> Launchpad bug 961482 in linux "3.2.0-19 kernel fails to boot (-18 OK)" [Critical,Confirmed] https://launchpad.net/bugs/961482
[13:24] <mjg59> Yes, I know - but I can't reproduce and mere inspection doesn't seem to be getting me anywhere. I really need a full backtrace.
[13:25] <cking> ah, so in the short term, would pulling this patch be a more sensible option?
[13:26]  * cking trying to work out the pros vs cons of keeping this patch
[13:28] <mjg59> No, that breaks a different set of hardware
[13:31] <cking> mjg59, OK - so reverting 3c076351c4027a56d5005a39a0b518a4ba393ce2 "PCI: Rework ASPM disable code" may at least allow these machines to boot?
[13:31] <mjg59> I really don't know at this point
[13:32] <mjg59> I'd like to see some effort to fix the bug from people who have access to users who see the bug
[13:32] <mjg59> The ones who have contacted me about it are not especially useful in terms of actually giving me feedback...
[13:32] <cking> I realise this, just trying to explore options at the mo.
[13:33] <tgardner> cking, do we have any affected machines within OEM or somewhere else ni the company ?
[13:33] <mjg59> Reverting all ASPM changes back to the 3.2 baseline will probably boot things, but you'll be back to spending 5W extra per machine
[13:33] <cking> tgardner, not that I know of, I've seen zero reports on this from OEM
[13:35] <tgardner> cking, well, see if you can get one of the affected folks in the bug report to respond.
[13:35] <cking> tgardner, ack
[13:38] <cking> mjg59, so a *full* backtrace is required, anything else especially useful to add in?
[13:38] <mjg59> cking: They're probably going to need either a serial console or USB debug to get it
[13:40] <cking> sigh
[13:41]  * cking will check with OEM to see if we have one of the offending Dells
[14:38]  * ogasawara back in 20
[15:48] <jjohansen1> ogasawara, tgardner: is there going to be 1 more kernel upload before beta2?
[15:49]  * jjohansen1 knows the answer is no but needs to ask
[15:49] <tgardner> jjohansen1, certainly one more before freeze
[15:49] <tgardner> likely april 3
[15:49] <ogasawara> jjohansen1: I wasn't planning on one before beta-2, but definitely one more before kernel freeze
[15:49] <jjohansen1> tgardner: right, but not before beta2
[15:50] <jjohansen1> ogasawara: okay thanks
[15:50] <tgardner> jjohansen1, that would almost require a freeze exception from the release team
[15:50] <jjohansen1> tgardner: right, I will let the server team request that if they want
[15:51] <ogasawara> tgardner: I am concerned though about bug 961482 being unresolved for beta-2, but there does seem to be a workaround so I was going to release note it.
[15:51] <ubot2> Launchpad bug 961482 in linux "3.2.0-19 kernel fails to boot (-18 OK)" [Critical,Confirmed] https://launchpad.net/bugs/961482
[15:51] <tgardner> ogasawara, cking is working on it
[15:52] <ogasawara> tgardner: ack.  if we did get a fix in time for beta-2, I'd lobby the release team for an upload.
[15:52] <cking> ogasawara, I'm not sure yet if we can get a fix in time though, it's pretty tight
[15:53] <ogasawara> cking: indeed, we'd have to get something in by tomorrow which is not a large window.
[15:53] <ogasawara> cking: were you able to get a hold of anyone in OEM who could reproduce?
[15:54] <cking> ogasawara, not yet, but they possibly have some H/W which I will try and get shipped to me
[15:54] <ogasawara> cking: I think bryceh might have a system showing the issue?
[15:55] <cking> ogasawara, this kinda bug requires gathering most of the oops, so it's kinda serial console kinda work
[15:57] <jjohansen1> ogasawara, tgardner: sounds like server team is going to work around the issue for beta 2 so no freeze exception request for the kernel
[15:57] <tgardner> jjohansen1, ack. what was theissue ?
[15:58] <jjohansen1> tgardner: its around containers and apparmor confinement
[15:58] <jjohansen1> tgardner: there is a pseudo workaround, that they will use for beta2
[16:28] <cking> rats, hit an inode race bug in btrfs
[16:34] <henrix> smb: thanks for the background info on iscsitarget, in your email
[16:35] <henrix> smb: about the bug itself, in my (quick) investigation, i found that the bug has been solved already upstreams
[16:36]  * henrix kept a link to thread somewhere...
[16:36] <smb> henrix, welcome. Ok, I have not  seen a good pointer in the debian changelogs, but have not yet check upstream
[16:36] <henrix> smb: let me take a look at my notes, i'm sure i found a reference to this
[16:37] <smb> Seems version-wise we are back a few versions compared to debian testing but that late in the game I would rather not try to get someone to re-sync.
[16:38] <henrix> ah! found the reference
[16:39] <henrix> smb: https://bugzilla.novell.com/show_bug.cgi?id=676803
[16:39] <ubot2> bugzilla.novell.com bug 676803 in Kernel "iscsi enterprise target just hangs" [Critical,Resolved: fixed]
[16:39] <henrix> i guess it's the same issue, and they closed the issue with a newer version of the package
[16:43] <smb> Ok, <IP_ADDRESS> is newer than what the Debian version says. But I remember that there was an odd versioning thing with the sourceforge project. In their svn files there was references to the new number but not tarballed and released as is...
[16:45] <henrix> smb: yeah, can't remember the details, but when i was looking at that i found <IP_ADDRESS> only on the svn (or cvs...)
[16:45] <henrix> smb: but not on the tarballs
[16:45] <smb> Hm, so svn is at version470, if I read the Debian changlog correctly they went to 453
[16:47] <smb> the suse report has someone claiming it works with 466...
[16:54] <smb> henrix, Hm, that might be the relevant commit... http://iscsitarget.svn.sourceforge.net/viewvc/iscsitarget/trunk/kernel/iscsi.c?r1=462&r2=461&pathrev=462
[16:54] <henrix> smb: yeah, it could be
[16:55] <henrix> smb: i can take a closer look at this bug again if you want me to
[16:56] <henrix> smb: right now i'm working on the sru cycle, but i may get some time later on
[16:56] <henrix> smb: (tomorrow, probably)
[16:58] <smb> henrix, Since I have been poking at that package already, I could carry on as well. Just don't want to rip it from you in case you wanted to go on...
[17:00] <henrix> smb: well, from my activity report, this bug was not on my todo list anyway :)
[17:00] <henrix> smb: so, feel free to have some fun with it
[17:01] <smb> henrix, :) Ok, then let me try to find out whether we can fix it by that upstream change.
[17:02] <henrix> smb: cool. anyway, if you're busy, feel free to "delegate" it on me :)
[17:04] <smb> henrix, I would never say I am not busy (that just conjures new issues)... But it should fit in. ;)
[17:35] <tgardner> sforshee, are you seeing any video tearing on your MB Air ? maximize a shell, then click on the wi-fi icon a few times.
[18:09] <tgardner> cking, otp
[18:09] <cking> tgardner, ack
[18:11] <sforshee> tgardner, I haven't noticed any tearing, and I'm not seeing any doing what you described either
[19:29]  * tgardner relocates
[20:18]  * tgardner -> EOD
[23:04] <RAOF> We would appear to be missing some ivybridge fixes in our kernel.  The mainline build of drm-intel-next is stable, but our 3.2-20 kernel tends to hard-lock in Unity.
[23:05] <RAOF> I'm seeing if I can get some netconsole output when it dies to narrow down what the problem is.
[23:08] <ohsix> are there too many patches between drm-intel-next and 3.2-20 to see what one it may be?
[23:11] <RAOF> ohsix: There's almost two full kernel releases worth of development.
[23:11] <ohsix> ic
[23:11] <RAOF> Which is why I'm looking for some sort of error message other than “the system goes entirely unresponsive” - that should help point to a patch.
[23:18] <RAOF> Of course, now that I've got a netconsole hooked up it's not hanging.
[23:19] <ohsix> gpu hangs are scary
[23:24] <bryceh> RAOF, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961482
[23:24] <ubot2> Launchpad bug 961482 in linux "3.2.0-19 kernel fails to boot (-18 OK)" [Critical,Confirmed]
[23:25] <bryceh> (in case you hadn't already run across it)
[23:25] <bryceh> (and in case it's the same bug.  that one is not ivybridge-specific afaik)
[23:26] <RAOF> That's not it; the system comes up fine, and works for an indeterminate period of time.
[23:26] <RAOF> And then, at some point (usually associated with alt-tab?) it hangs.
[23:27] <bryceh> ok
[23:31] <RAOF> Bah.  That's highly annoying.
[23:32] <RAOF> netconsole stays around *just* long enough to print the timestamp of the kernel message when everything freezes.


[06:50] <beata|coyote> Trying to get Palm serial adapter to work, kernel 2.6.35, autoloaded kl5kusb105 driver shouts into kernel log about "usb 4-2: read status 30 0" and managed to actually crash the machine once.
[07:22] <beata|coyote> Going to load the generic driver when I have time.
[14:59] <dupondje> Hi! Somebody around that take care of daily kernel builds ? :)
[15:08] <dupondje> quite silent :)
[16:11] <bjf> dupondje, there was a problem with them yesterday, they were put on manual, they will be back tomorrow probably
[16:14] <dupondje> well thats not really the issue :)
[16:15] <dupondje> I just want to know if the .config that it uses can be modified a bit ?
[16:41] <bjf> dupondje: the best think to do is make a request on the mailing list
[17:48] <psusi> there seem to be a lot of kernel modules in the initrd.. to make the initrd optional, the system would have to determine that none of them are required to boot.  If it is smart enough to figure that out, why not just omit the specific modules that are not required, and use a much smaller initrd rather than none at all?


[09:40] <cjwatson> (fixed last night while I was asleep)
[10:37] <cpaelzer> hi - in regard to build is there anything on my end that is better than cancel+restart if a build is locked up in "pkgstripfiles: waiting for lock" ?
[10:37] <cpaelzer> This one is an example https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4640/+build/21964944
[10:37] <cpaelzer> we all have learned to expect riscv64 to build slow, so I didn't realize it before
[10:37] <cpaelzer> and while I've seen other builds (on any arch) to loop through that a bit this one seems to hang on it for hours
[10:43] <cjwatson> cpaelzer: there is not
[10:43] <cjwatson> cpaelzer: you could try debugging it though :-)
[10:44] <cjwatson> cpaelzer: it's probably in pkgbinarymangler or pkg-create-dbgsym somewhere, I forget which
[10:44] <cpaelzer> I have when I've seen it long ago and it was as racy and heisen-buggy as you would expect :-)
[10:44] <cpaelzer> mangler rings a bell
[10:45] <cpaelzer> I'll cancel and restart for now, maybe after f-freeze there is time revisit the problem if it becomes more common
[10:45] <cpaelzer> in my experience it scales with the number of binary packages in a build
[10:46] <cpaelzer> IIRC dpdk was the one I saw it most of the time and that has >100 binary packages
[10:46] <cpaelzer> thanks cjwatson for the answer that there is no obvious way I miss, that at least makes me feel better when restarting it


[05:48] <rb789> can anyone help me set up sprint mobile?
[05:48] <rb789> I got ip address, dns server etc but connection not working
[05:48] <rb789> not sure what is going on. I am not linux expert either
[09:05] <lool> derekS: We meet regularly and track progress on spec on the wiki and on launchpad
[09:05] <lool> https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Karmic
[14:09] <lbt> NCommander: YokoZar thought there was an #ubuntu-meeting re MID/Mer ....


[00:17] <blackshirt> hello, good morning
[00:21] <Hayate> hello,good morning
[00:22] <Hayate> is there class rom this morning?
[14:01] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2012/07/31/%23ubuntu-classroom.html following the conclusion of the session.
[14:04] <tumbleweed> Hello everyone
[14:04] <tumbleweed> Welcome to our little Debian RC bug squashing party
[14:04] <tumbleweed> glad to see there's already an audience of 2
[14:04] <tumbleweed> anyone else here? please say hi in the chat channel
[14:04] <tumbleweed> that's #ubuntu-classroom-chat, which is also the place to ask questions
[14:05] <tumbleweed> so, I'm Stefano Rivera, a Debian & Ubuntu Developer
[14:05] <tumbleweed> and I'm here to guide you through working with Debian, today
[14:05] <tumbleweed> I assume you all know that Ubuntu is derived from Debian
[14:05] <tumbleweed> in fact, about 75% of packages in Universe are entirely unmodified from Debian
[14:05] <tumbleweed> and that's a good thing
[14:06] <tumbleweed> there's no need for those packages to be modified in Ubuntu
[14:06] <tumbleweed> the vast majority of bugs that we'd encounter in them are relevant to both Debian & Ubuntu
[14:06] <tumbleweed> and it makes sense to fix them as close to the source as possible
[14:06] <tumbleweed> that means the least duplication of effort, and shares the benefit as widely as possible
[14:06] <tumbleweed> https://wiki.ubuntu.com/Debian/ForUbuntuDevelopers
[14:06] <tumbleweed> I hope at this point, you are aware of the advantages of working well with our upstream, Debian
[14:06] <tumbleweed> (and that I might have written up some of this beforehand, for pasting) :P
[14:07] <tumbleweed> so, what are we here to do today?
[14:07] <tumbleweed> Debain has frozen their next release, wheezy, and is now trying to fix all the remaining RC bugs in it
[14:07] <tumbleweed> we're going to try and help with that
[14:07] <tumbleweed> a lot of these are also relevant to Ubuntu, and it's generally in our interest for Debian to release quickly
[14:07] <tumbleweed> what's an RC bug?
[14:07] <tumbleweed> the Debian Release team has helpfully defined that for us
[14:07] <tumbleweed> http://release.debian.org/wheezy/rc_policy.txt
[14:07] <tumbleweed> how many need to still be fixed?
[14:07] <tumbleweed> far too many: http://bugs.debian.org/release-critical/
[14:07] <tumbleweed> we need to get the green line down to zero
[14:08] <tumbleweed> everyone still with me?
[14:08] <tumbleweed> what's the best way to find RC bugs?
[14:09] <tumbleweed> I suggest using this search: http://deb.li/fOvv
[14:09] <tumbleweed> that should find issues that are blocking the release of wheezy, and nobody has looked at yet
[14:09] <tumbleweed> if anyone has any more questions about that search interface, please ask me
[14:09] <tumbleweed> here's another query that may be interesting to us: http://deb.li/3Yc7n
[14:09] <tumbleweed> that will list bugs that may have been fixed in Ubuntu, but the patch hasn't been forwarded to Debian
[14:09] <tumbleweed> many of the bugs you'll see on these lists are not trivial to fix
[14:09] <tumbleweed> there's a reason that they've been open for a long time, and nobody has fixed them
[14:09] <tumbleweed> so, if you want to find something easy to work on, it's often best to look at 10 of them, and pick the easiest one
[14:09] <tumbleweed> but, of course, they all need to be fixed :)
[14:10] <tumbleweed> (or found to be not actually blocking bugs)
[14:10] <tumbleweed> how do you go about fixing these issues?
[14:10] <tumbleweed> I'm afraid there are way too many types of RC bug for me to answer that
[14:10] <tumbleweed> but we can take that on a case-by-case basis, if you point to a bug you aren't sure how to deal with, I'm sure someone can suggest the answer
[14:11] <tumbleweed> I can briefly explain the procedures
[14:11] <tumbleweed> when Debian is frozen, Debian package maintainers are strongly encouraged not to upload anything to unstable, that won't end up in the frozen release
[14:11] <tumbleweed> so, for most packages, the same version should be present in both unstable, and testing
[14:12] <tumbleweed> (if you don't know about debian testing, packages automatically migrate from unstable to testing after 10 days, if there are no issues that should stop the migration)
[14:12] <tumbleweed> but during the freeze, this is disabled
[14:12] <tumbleweed> we'll fix it in unstable, and then ask the release team to let it migrate through to testing
[14:12] <tumbleweed> this means that the fix should be as minimal as possible, as the release team will have to review it
[14:12] <tumbleweed> it should also be minimal, if we intend to NMU (non-maintainer upload) it
[14:14] <tumbleweed> the chat channel seems deathly silent, am I going way too fast?
[14:15] <tumbleweed> So:
[14:15] <tumbleweed> verify that the bug exists in wheezy (testing), and that the version is the same as unstable
[14:15] <tumbleweed> it may be so trivially obvious that it doesn't need to be verifified
[14:15] <tumbleweed> or it has enough commenters / logs to be sure it's real
[14:16] <tumbleweed> if not, you can always fire up a chroot / vm (and people around here can help you set that all up)
[14:16] <tumbleweed> You can see more information about the package at http://packages.qa.debian.org/$PACKAGENAME
[14:16] <tumbleweed> (when I say $packagename in this talk, I mean source package)
[14:16] <tumbleweed> or run rmadison -u debian $package
[14:17] <tumbleweed> pull-debian-source $package
[14:17] <tumbleweed> should get you the current source
[14:17] <tumbleweed> then you get to fix it (that's the easy bit, right? :)
[14:17] <tumbleweed> test-build against sid (unstable)
[14:17] <tumbleweed> generate a debdiff, and attach it to the bug, tagging the bug +patch
[14:17] <tumbleweed> has anyone here never used debian's bugtracker before?
[14:18] <tumbleweed> (it's probably very different to anything you are used to, so I can give you a crash course in it)
[14:20] <tumbleweed> it's worth noting that debbugs recently gained a new feature. You can now tag a bug +patch by making the first line of your e-mail
[14:20] <tumbleweed> Tags: +patch
[14:20] <tumbleweed> and then a blank line
[14:21] <tumbleweed> (in other words, all e-mail to debbugs can now take pseudo-headers)
[14:21] <tumbleweed> no need no cc<EMAIL_ADDRESS>[14:23] <tumbleweed> right. So. Once you've attached a patch to a bug and tagged it patch
[14:23] <tumbleweed> Chances are a Debian Developer who's looking at RC bugs will notice it and sponsor it, fairly quickly.
[14:23] <tumbleweed> But you can also ask for sponsorship. Usually, #debian-mentors on irc.debian.org is a good place.
[14:23] <tumbleweed> #ubuntu-motu / #ubuntu-devel would work too (be clear that it's a debian bug that you are looking for a sponsor for)
[14:23] <tumbleweed> and today, you can raise it in the classroom chat channel
[14:24] <tumbleweed> ok, that's everything I intended to cover in classroom style
[14:24] <tumbleweed> now, I'm entirely open to questions
[14:33] <ClassBot> Rcart asked: Fixed bugs are automatically removed from those lists?
[14:33] <tumbleweed> yes
[14:34] <tumbleweed> the RC bug search like I gave you doesn't ignore bugs which arceh marked as done
[14:34] <tumbleweed> *are
[14:34] <tumbleweed> (which is the traditional way to mark a bug as fixed)
[14:34] <tumbleweed> but instead relies on debbugs (the debian bugtracking system)'s version tracking feature
[14:35] <tumbleweed> it knows which version of a package a bug was found in, and wwhich in was fixed in
[14:35] <tumbleweed> (when people close bugs in the changelog, that is)
[14:36] <tumbleweed> you asked about logkeys
[14:36] <tumbleweed> $ rmadison -u debian logkeys logkeys | 0.1.0-1  | squeeze | source, amd64, armel, i386, ia64, mips, mipsel, powerpc, sparc logkeys | 0.1.0-1  | wheezy  | source, amd64, armel, i386, ia64, mips, mipsel, powerpc, sparc logkeys | 0.1.0-1  | sid     | source, mips, mipsel logkeys | 0.1.1a-3 | sid     | source, amd64, armel, armhf, i386, ia64, powerpc, sparc
[14:36] <tumbleweed> erk, that wasn't pretty
[14:36] <tumbleweed> http://packages.qa.debian.org/l/logkeys.html
[14:37] <tumbleweed> you can see the fixed version hasn't entered testing yet
[14:37] <tumbleweed> because it didn't build on some architectures
[14:38] <tumbleweed> https://buildd.debian.org/status/logs.php?pkg=logkeys
[14:38] <tumbleweed> it successfully built on some architectures in the past, that it isn't building on now
[14:38] <tumbleweed> so those old versions are holding the new ones back
[14:43] <ClassBot> chilicuil asked: all the rc bugs must be corrected in debian?, what about unity or some projects specific to ubuntu, can they be defined as RC?, if so, how can I find them?
[14:43] <tumbleweed> chilicuil: to answer the example first: unity isn't in Debian
[14:44] <tumbleweed> (although hopefully it will be, at same point)
[14:44] <tumbleweed> Ubuntu has its own definition of RC bugs
[14:44] <tumbleweed> but Ubuntu doesn't require all RC bugs to be fixed before releasing
[14:44] <tumbleweed> we do a time-based release, where we release on a particular day
[14:45] <tumbleweed> and do our best to fix all the show-stopper bugs before that date
[14:45] <tumbleweed> we'd love to fix all our RC bugs, but one can't do that and regular, timely, releases
[14:46] <tumbleweed> https://wiki.ubuntu.com/Bugs/Importance describes Ubuntu's bug importance levels
[14:47] <tumbleweed> but our RC bugs are usually bugs that are noticed during ISO testing. i.e. bugs that actually block releasing
[14:47] <tumbleweed> that and bugs that are critical enough that the release team is informed of them
[14:50] <ClassBot> UndiFineD asked: looking at the number of rc-bugs, the number seems to decrease, how many are caused by kfreebsd and can i easily check that ?
[14:50] <ClassBot> There are 10 minutes remaining in the current session.
[14:52] <tumbleweed> so, yes, Debian is releasing with kfreebsd as supported architectures, in wheezy
[14:52] <tumbleweed> http://release.debian.org/wheezy/arch_qualify.html
[14:53] <tumbleweed> the number decreases, because people put attention into fixing them
[14:53] <tumbleweed> (although, it generally climbs a bit after the freeze, as people notice bugs in all the last-minute uploads)
[14:54] <tumbleweed> freezing testing means developers aren't introducing new bugs (hopefully), and effort should mostly go into RC bug fixing
[14:55] <tumbleweed> as to bugs caused by kfreebsd. I see a bunch of usertags that may be helpful in finding them
[14:55] <tumbleweed> http://udd.debian.org/cgi-bin/bts-usertags.cgi?user=&tag=*kfreebsd*
[14:55] <tumbleweed> of course, not all of those will be RC
[14:55] <ClassBot> There are 5 minutes remaining in the current session.
[14:56] <tumbleweed> and many architecture-specific RC bugs can be solved by removing the binary packages from that architecture
[14:56] <tumbleweed> (assuming they have no significant reverse dependencies)
[14:56] <ClassBot> Rcart asked: can we use ubuntu's procedure to fix bugs in Debian? Like setting up an instance of Debian in pbuilder? I mean, fixing Debian bugs from Ubuntu?
[14:57] <tumbleweed> yes, you can easily set up a debian chroot in pbuilder
[14:57] <tumbleweed> pbuilder-dist create sid
[14:57] <tumbleweed> should work
[14:58] <tumbleweed> Debian and Ubuntu are incredibly similar, under the hood
[15:00] <ClassBot> Logs for this session will be available at http://irclogs.ubuntu.com/2012/07/31/%23ubuntu-classroom.html
[15:01] <tumbleweed> I guess that's it everyone. Thanks


[03:34] <vychune> o/
[21:27] <vychune> o/
[23:06] <vychune> o/
[23:27] <wrst> hey vychune
[23:27] <vychune> hey happy easter
[23:28] <wrst> happy easter to you vychune, how are you doing?
[23:28] <vychune> ok not great
[23:28] <vychune> mother decided my phone should play outside more
[23:34] <vychune> you?
[23:45] <wrst> ha ha
[23:45] <wrst> i'm good... does that mean your phone has disappeared?
[23:47] <vychune> yes
[23:57] <wrst> oh no and sounds forceably removed?


[00:11] <gnomefreak> why does floodbot +zb than right after -zb?
[00:13] <ubotu> In ubotu, Some_Person said: tets is Don't you mean test?
[00:14] <ubotu> In ubotu, Some_Person said: ccsm is To enable advanced customization of desktop effects in Ubuntu, install 'simple-ccsm'. A new option will appear in your appearance properties - See also !compiz - Help in #compiz-fusion
[02:03] <ubotu> XceII called the ops in #ubuntu ()
[02:18] <gnomefreak> is -ops-private still used channel?
[03:54] <ubotu> In #ubuntu, Teslaman said: ubotu, my problem is when i load up, I get a grub error, error 18, any ideas about what it is?
[03:56] <tonyyarusso> !bote > teslaman
[03:56] <tonyyarusso> bah
[03:56] <tonyyarusso> !bot > teslaman
[05:02] <ubotu> Pelo called the ops in #ubuntu (MrLinux)
[05:47]  * Hobbsee waves
[08:57] <Hobbsee> sigh.  uni is back tomorrow
[08:57] <Hobbsee> when will we redirect u-r-p?
[08:58] <stdin> soon probably, seem quite dead in there
[09:05] <jussio1> good morning all
[09:06] <nalioth> jussiol: hi
[09:06] <Hobbsee> morning jussio1
[09:08]  * jussio1 sighs... mornings :/
[09:09] <jussio1> morning Hobbsee and nalioth :)
[09:09] <nalioth> sleep well, jussiol ?
[09:16] <Seveas> Hobbsee, where to? #ubuntu or -offtopic?
[09:17] <Hobbsee> Seveas: hmmm.  -offtopic
[09:18] <jussio1> nalioth: meh... no. and who is jussiol ?
[09:18] <nalioth> jussio1: your multichannel clone?
[09:19] <jussio1> no, that would be jussi01 afaik..
[10:25] <Myrtti> whut the heck
[10:25] <Myrtti> [12:19] *** cia-spy<EMAIL_ADDRESS>has joined  #ubuntu
[10:25] <Myrtti> [12:22] < cia-spy> Myrtti: please release my nic you have my full attention.
[10:25] <Myrtti> [12:24] < cia-spy> t/y
[10:25] <Myrtti> [12:24] *** cia-spy<EMAIL_ADDRESS>has quit  [Client Quit]
[10:25] <Myrtti> @btlogin
[10:27] <Myrtti> ompaul: ^
[10:29] <Seveas> Myrtti, wth indeed :)
 BHSPitLappy,  RELEASE MY NIC
[10:30] <Seveas> kick-ban-gone
[10:31] <Myrtti> I bet he was that xce11 feller
[12:12] <ubotu> In #ubuntu, afancy said: ubotu: The problem is that in the Network settings, there is no Wireless connetion
[12:13] <jussio1> !bot > afancy
[12:42] <jussio1> icesword: How can we help you today?
[12:42] <icesword> why
[12:43] <jussio1> icesword: why what?
[12:43] <icesword> jussi01: what i did? i did nothing
[12:44] <jussi01> @btlogin
[12:44] <icesword> jussi01: what you mean
[12:45] <jussio1> icesword: where did you get forwarded from?
[12:45] <icesword> no, nothing, you start the conversation
[12:46] <jussio1> icesword: you have joined #ubuntu-ops. Please read the topic.
[12:46] <icesword> kk, but i said nothing
[12:46] <icesword> i will go away
[12:48] <jussio1> curious...
[13:01] <Hobbsee> now that nick sounds familiar....
[14:39] <ompaul> Myrtti, ack
[14:39] <ompaul> Myrtti, that was ii at the end of the nick
[14:44] <Amaranth> Have you guys ever seen #sparkle-ponies? :)
[14:45] <Hobbsee> no, but i'm sure it's something to do with mneptok
[14:47] <ompaul> Hobbsee, I suggest you run the command /cs info #sparkle-ponies
[14:47] <Hobbsee> ompaul: tasty.
[14:47] <ompaul> Hobbsee, perhaps
[14:48] <Hobbsee> well, it's out of our namespace.
[14:48] <Hobbsee> so that's fine by me
[14:48] <Hobbsee> then again, the topic is out of date
[15:33] <Myrtti> ompaul: what link was that?
[15:33] <Myrtti> (I'm again on tty with no X so no bonuses for me)
[15:33] <ompaul> a set of MS software adins
[15:33] <Myrtti> lol
[16:19] <jrib> releases.ubuntu.com seems to be down.  Suggestions for a different link for the topic in #ubunut?
[16:19] <jrib> #ubuntu even
[16:20] <ompaul> It's not just you! releases.ubuntu.com looks down from here.
[16:20] <ompaul> ;-)_
[16:21] <ompaul> http://downforeveryoneorjustme.com/
[16:22] <mc44> jrib: us.releases.ubuntu.com
[16:22] <robotgeek> thanks ompaul , that is a cool site.
[16:24] <ompaul> mc44, na - I went with the official release page
[16:24] <ompaul> any typos in that url
[16:24] <jrib> official release links to releases.ubuntu.com for the torrent though
[16:25] <jrib> us.releases.ubuntu.com seems like a better option
[16:25] <ompaul> lets watch the complaint count any more then two
[16:25] <ompaul> jrib, until it dies
[16:26] <ompaul> us.* has a bad rep for being up
[16:26] <mc44> well, it's currently doing better than releases.ubuntu.com ;p
[16:26] <ompaul> in terms of overall no ;-PPPPPPP
[16:26]  * ompaul notches it up a few levels
[18:40] <Seeker`> BunnyRevolution: hi
[18:40] <BunnyRevolution> hi Seeker`
[18:40] <Seeker`> BunnyRevolution: Would appear to be a bot from the hostmask
[18:40] <BunnyRevolution> you would appear to be a troll
[18:41] <BunnyRevolution> i'm amused
[18:41] <jussio1> hello Seeker`
[18:42] <BunnyRevolution> hi joejax
[18:42] <jussio1> hrm
[18:50] <jussio1> BunnyRevolution: which channel did you come from?
[18:51] <BunnyRevolution> jussio1 ?
[18:52] <jussio1> BunnyRevolution: I assume you joined here from being forwarded or banned from another channel.
[18:52] <BunnyRevolution> no.  i joined knowing the channel name
[18:53] <BunnyRevolution> on of your ops is bieng a troll/troublemaker
[18:53] <BunnyRevolution> s/on/one
[18:54] <jussio1> BunnyRevolution: ok. Who would that be? and where?
[18:54] <BunnyRevolution> Seeker` and mc44
[18:55] <BunnyRevolution> i won't mention the channel, as i think a number of peeps there have enough trouble as it is.
[18:56] <jussio1> Ok. Im going to leave this Issue to members of the community council.
[18:56] <BunnyRevolution> thank you
[18:57] <BunnyRevolution> it's that or i'm going to comb through *buntu logs and other channels and air the dirty laundry on the net
[18:57] <BunnyRevolution> via slashdot if necessary
[18:57] <PriceChild> BunnyRevolution: hello there.
[18:57] <Myrtti> oh joy
[18:58] <BunnyRevolution> PriceChild: hi
[18:58] <Myrtti> I always get the funky fuzzy feeling when there's threats in the air
[18:58] <Myrtti> fuzzy in the meaning of bread being fuzzy with mold after being left in some moist place inside a plastic bag
[18:58] <PriceChild> BunnyRevolution: you want to file a complaint against Seeker` and mc44? The latter isn't an op afaik..?
[18:58] <BunnyRevolution> what kind of mold is that anyway?
[18:59] <BunnyRevolution> then the latter is not a problem for the channel i guess
[18:59] <PriceChild> I like fish, especially cod.
[19:01] <BunnyRevolution> thank you
[19:01] <BunnyRevolution> bye bye for now
[19:02] <mc44> aww, no one's ever complained about me before :(
[19:02] <PriceChild> That was very odd.
[19:02] <PriceChild> Was half hoping it'd start talking about fish :/ Now I'm just confused and unsure.
[19:03] <Seeker`> PriceChild: It seems tobe an actual person, despite the hostmask
[19:08] <PriceChild> I can't make my clock applet on the gnome panel show unix time? :/
[19:09] <ompaul> happy power outages to me happy power outages to me - machines and router ok stupid hub locked solid
[19:09] <ompaul> that took a while to work out :-(
[19:10] <ompaul> and I was not around :-/
[19:10] <Seveas> what's with that bunny fool?
[19:11]  * jussio1 sighs...
[19:11] <Seveas> jussio1, 'sup?
[19:11] <Seveas> just point e to the relevant channel and I'll read the logs :)
[19:11] <jussio1> heya Seveas, not too much.
[19:12] <jussio1> Seveas: think uncensored...
[19:12] <Seveas> jussio1, ugh, nevermind then
[19:12] <Seveas> I'll stay blissfully ignorant :)
[19:12]  * Seveas hugs jussio1
[19:12] <ompaul> where is lp gone on me: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/223175
[19:12] <jussio1> :)
[19:12] <ubotu> Launchpad bug 223175 in linux "2.6.24-16: Xen patches contain unnessecary Kconfig.orig (causes compile failures)" [Undecided,New]
[19:12] <ubotu2> launchpad bug 223175 in linux: "2.6.24-16: Xen patches contain unnessecary Kconfig.orig (causes compile failures)" [Undecided,New]
[19:12] <ompaul> I am downloading stuff
[19:13] <ompaul> so it ain't so fast
[19:13] <ompaul> 7.10 8.10u and x all by torrent
[19:13] <ompaul> wow how to be slow
[19:13] <ompaul> ;-)
[19:14] <Seveas> you're typically ompaul today
[19:14] <Seveas> making no sense at all :)
[19:14] <ompaul> Seveas, read that bug I feel a bit queasy
[19:15] <mc44> PriceChild: /apps/panel/applets/clock_screen0/prefs/format to unix
[19:15]  * PriceChild highfives mc44
[19:16] <PriceChild> i want two clocks :/
[19:16] <PriceChild> i don't see clock_screen1 :/
[19:17] <PriceChild> anyway, fixed, thanks mc44
[19:37] <Myrtti> [21:37] <Arzu_adana> aykiz_ank@
[19:37] <Myrtti> [21:37] *** Arzu_adana<EMAIL_ADDRESS>[19:42] <Seveas> !staff
[19:42] <ubotu> Hey nalioth, jenda, rob, SportChick, seanw, Dave2, Christel or Gary,  I could use a bit of your time :)
[19:42] <Myrtti> that's the second one I've gotten today
[19:42] <Myrtti> but from a different one
[19:44] <nalioth> Myrtti: onjoin or out of the blue?
[19:46] <Myrtti> I did not look into it, was a bit busy at the time
[19:46] <Myrtti> I can check the logs for a timestamp though
[19:47] <Myrtti> 13:17 <Arzu_amerikLi> leylaank74@
[19:47] <Myrtti> 8+ hours ago
[19:48] <ompaul> Arzu_ << being the commaon part
[19:48] <ompaul> hmm wow a pattern
[19:49] <Myrtti> and yes, I log *ALL* my pm's to files named by the nick and date to folders according the network
[19:49] <Myrtti> I've got two years worth of logs with my ex
[19:49] <Myrtti> :-P
[19:50]  * ompaul shows Myrtti the joys of /dev/null ;-)
[19:50] <ompaul> I think a year of logs is enough but that is just me
[19:51] <Myrtti> I've lost too many phone numbers and urls and email addresses, even work related
[19:51] <Myrtti> snailmail ones
[20:10] <jrib> why do so many people think they have 8.10...
[20:11] <ompaul> cos they think
[20:11] <ompaul> but don't know?
[20:11] <ompaul> jrib, ask them how the time travel was
[20:11] <ompaul> :)
[21:00] <PriceChild> The open week starts tomorrow btw, would be nice to be around if you can just incase :)
[21:00] <PriceChild> the sabdfl isn't till fri
[21:13] <Myrtti> I'll always be here
[21:13] <Myrtti> *sigh*
[21:13]  * PriceChild huggles Myrtti
[21:15] <Myrtti> np. Elton John - Bitter fingers
[21:20]  * jussio1 huggles nalioth
[21:23] <Seveas> @hug Myrtti
[21:23] <Seveas> @hug Myrtti
[21:24] <Seveas> oh bloody hell...
[21:24] <jussio1> Seveas: ?
[21:24] <Seveas> botbug
[21:24] <jussio1> oh
[21:24] <jussio1> :/
[21:24] <Seveas> anyway
[21:24]  * Seveas hugs Myrtti twice, once for himself and once for the buggy bot
[22:08] <ikonia> alert please
[22:08] <ikonia>  kazol_> What is the equivalent of Ctrl+Alt+Delete?
[22:08] <ikonia> it's fujisio guy again (spelling
[22:13] <Myrtti> DAMNIT
[22:14] <ompaul> that was cory_
[22:15] <ikonia> did someone just try to clone me as ikonia_ or something like that
[22:15] <ubotu> In #ubuntu, aki_ said: ubotu, but sudo is the user and root is the superuser, right? I want to connect as root in order to upgrade from 5.10 to 6.06
[22:16] <Myrtti> watch out for runkku
[22:16] <Myrtti> his nick means w**ker in Finnish
[22:17] <ompaul> is he there?
[22:17] <Myrtti> should I ask him to change it?
[22:17] <ompaul> once if fail bf to here
[22:17] <Myrtti> bf?
[22:18] <jdong> banforward.
[22:18] <jdong> or boyfriend *starts rumors*
[22:18] <Myrtti> I'd rather ask him straight without bf's
[22:20] <Myrtti> I'm not that fluent with bf's
[22:22] <ompaul> Myrtti, ask - if fail I will bf
[22:22] <ikonia> did I say this in #ubuntu please
[22:22] <Myrtti> I did
[22:22] <Myrtti> nothing happened yet, he's idling
[22:22] <ikonia> what is the last think you saw me saw in #ubuntu please.
[22:22] <ikonia> I see this
[22:23] <ikonia> 21:39 < ikonia> itlivecd GUI would probably help you.
[22:23] <ikonia> I didn't say it
[22:23] <Myrtti> [00:20] < ikonia> beernutz: thats not fact
[22:23] <ikonia> Myrtti: good good
[22:23] <ikonia> Myrtti: something funny is going on
[22:23] <ikonia> thats the 3rd time tonight I've seen on my screen something I didn't say
[22:24] <ikonia> and my last log doesn't show 21:39 < ikonia> itlivecd GUI would probably help you.
[22:25] <Myrtti> [00:21] < Malaz> ihearthardy: Yes, you can.  easily.  But I thought you  didn't want to use the CLI, so a livecd GUI would probably help
[22:25] <ikonia> Myrtti: thats odd
[22:25] <Myrtti> ok, my irssi gets some funky screen error watching that too
[22:26] <Myrtti> that paste of mine
[22:26] <ikonia> I think I'll take a break for tonight and look into it
 J-Unit: thats nothing to do with ubuntu
 ikonia, lol ok im sry :(
[22:26] <ikonia> thank you for clarifying that
[22:26] <ikonia> ompaul: yup, that bit I did say
[22:26] <Myrtti> [00:25] < pwcca> weBut I thought you  didn't want to use the CLI, so a  livecd GUI would probably help
[22:26] <ompaul> ikonia, pm me and I paste my last log to you
[22:26] <Myrtti> that's what my paste on this channel looks right now
[22:27] <ikonia> Myrtti: looks like irssi is having a bit of a hard time
[22:27] <Myrtti> there's something funky there
[22:27] <Myrtti> are you using irssi too?
[22:27] <Myrtti> now the nick changed to what it was on the previous channel
[22:27] <Myrtti> [00:23] < iDN> i waBut I thought
[22:27] <ikonia> Myrtti: I am
[22:27]  * ompaul no
[22:28]  * ompaul uses evil gui program
[22:28] <gnomefreak> ikonia: on irssi no hard time other than bookmarks for browser
[22:28] <Myrtti> there's definitely something funky going on there
[22:28] <ompaul> do you need bigger buffers or scroll back or something
[22:28] <ikonia> gnomefreak: mine is going very funky
[22:29] <Myrtti> now that that paste is off the visible screen and I scroll back, it doesn't show any nicks
[22:29] <ikonia> Myrtti: there is something in that line as now that it's on sreen for me too, my time stamps have dissapeared
[22:29] <ikonia> until I /clear
[22:29] <gnomefreak> ikonia: try /reload
[22:30] <ikonia> gnomefreak: done
[22:30] <gnomefreak> hmmmm
[22:30] <Myrtti> ok, it's officially too late, dark and cold, I'm going to bed
[22:30] <ikonia> Myrtti: I'm of the same opinion
[22:30] <gnomefreak> that almosts sounds like fun


[11:50] <kserkses> s.a
[14:36] <turgay> selam
[14:37] <kserkses> a.s
[14:51] <murat> slmlr
[14:52] <murat> tum develler nasıl yuklenır acaba
[17:14] <genc> slm
[18:31] <kserkses> s.a
[18:34] <genc> as
[20:28] <ertl> hello, sorry for this OT question, but can someone please help me and translating the following quote into English? Thanks in advance!  "Demiryolları Refah ve Umran Tevhit eder" ... it should be a famous quote by Ataturk


[02:52] <macogw> are the things that you're working on putting ubuntu on smart phones or just for internet?
[08:12] <bspencer> Bo-ster
[08:12] <Bo> Hi, bob
[08:13] <bspencer> hey
[08:13] <Bo> johnV said I can find you here
[08:13] <Bo> : )
[08:13] <Bo> the hildon-control-panel build successfully now :)
[08:13] <Bo> thanks to johnV's help
[08:14] <bspencer> good to hear
[08:14] <bspencer> w/ osso-af-settings change?
[08:14] <Bo> yes
[08:14] <bspencer> is hildon-libs-base for control panel or hildon-desktop?
[08:14] <bspencer> because I can build hildon-desktop on my system and I don't have hildon-libs-base
[08:14] <Bo> we just have to start from a clean repo
[08:14] <bspencer> I think that tko said hildon-lib-base was outdated and no longer needed.
[08:15] <Bo> for control panel
[08:15] <bspencer> ok
[08:15] <bspencer> so control panel needs osso-af-settings and hildon-base-libs
[08:15] <Bo> absolutely :_
[08:15] <bspencer> and this is from the recent "refactoring" code Nokia pointed us at, right?
[08:15] <Bo> yes
[08:15] <bspencer> ok.  got it
[08:16] <Bo> I'm working on the clock thing
[08:16] <Bo> one little question
[08:16] <bspencer> yes
[08:16] <Bo> how do I config the length of my applet
[08:16] <Bo> seems that it's too short
[08:17] <bspencer> set the preferred size
[08:17] <HappyCamp-John> Who let Bo on here? ;)
[08:17] <Bo> ha, hi, JohnV
[08:17] <bspencer> gtk_widget_set_size_request (btn, 52, 52);
[08:18] <bspencer> just make it wider.
[08:18] <Bo> I see, doesn't see any change though
[08:18] <Bo> I didn't already
[08:18] <bspencer> the problem with the top marquee is that it uses a GtkHBox, so all the controls just get packed to the left
[08:18] <HappyCamp-John> Hi Bo!
[08:18] <Bo> I'll try
[08:18] <bspencer> hm... I tried this a few days ago and it seemed to work
[08:19] <Bo> maybe some other mistake :)
[08:19] <Bo> I can fix it, hah
[08:19] <Bo> :)
[08:19] <bspencer> i need to figure out how to make a plugin stretch to fill the max horiz space.
[08:19] <bspencer> I'm sure there is a way , but I don't know it off the top of my head.
[08:19] <bspencer> just make it fixed for now and we'll adjust it later.
[08:20] <Bo> OK
[08:23] <Mithrandir> morning
[08:24] <bspencer> Mithrandir, morning, or...not for another 30mins
[08:24] <Mithrandir> IRC greeting time.  Always morning. :-)
[08:25] <bspencer> checking out for the night
[08:25] <bspencer> Bo, anything else?
[08:26] <bspencer> Bo -- can you see if horaceli needs anything?
[08:26] <Mithrandir> Bo: what source package is hildon-libs-base built from?
[08:27] <Mithrandir> https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-base-lib/ ?
[08:27] <bspencer> I think we got it from https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-base-lib/
[08:27] <bspencer> yes.
[08:27] <Mithrandir> somehow that doesn't look too alive.
[08:28] <Mithrandir> last entry in the changelog is in october 2006
[08:28] <bspencer> I think there must be a lingering dependency inside the control panel code
[08:28] <bspencer> we just need to ferret it out
[08:28] <Mithrandir> if it's something we need, I'll be happy to get it into the repo, but I'm just a tad sceptical until some of the maemo guys tell me otherwise.
[08:29] <bspencer> yep
[08:29] <Bo> yes
[08:29] <Bo> from https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-base-lib/
[08:29] <bspencer> let's get tko or other Nokia guys to suggest a solution
[08:30] <Mithrandir> tko_: ^^ ; could you give us a hint as to whether hildon-base-lib is used or not?
[08:32] <bspencer> I'm going to sleep.  Take care.
[08:33] <Mithrandir> see you around
[08:34] <Bo> bye , Bob,
[08:34] <Bo> nice sleep :)
[10:30] <tko_> Mithrandir, it's not. the functionality is available in gnomevfs and inotify
[10:30] <Mithrandir> ok, thanks.
[03:24] <Mithrandir> agoliveira_BRB: so, I'm looking at matchbox-window-manager, and tbh, I'd rather just port the few fixes we want than use the maemo one.
[03:27] <tko_> it's that bad? :-]
[03:29] <Mithrandir> no, not really, but easy merging with Debian is something we care about.
[03:30] <Mithrandir> so it's actually more that it doesn't gain us anything significant to go with the maemo one.
[03:33] <agoliveira> Mithrandir: I agree with you but we need something fast for testing and Matt asked me to import this one in a different branch so I did it.
[03:36] <agoliveira> BTW, IIRC maemo's version is upstream + patches so it shouldn't be hard to sync anyway.
[03:37] <Mithrandir> the packaging seems to be based on an old debian snapshot
[03:39] <agoliveira> The packaging maybe but the code itself comes from a very new matchbox WM.
[03:40] <agoliveira> We can just revamp the packaging...
[03:41] <Mithrandir> the complete size of the diff is about 2.5kloc; it's not a big deal to fix.
[03:42] <Mithrandir> and most of that again is theme stuff
[03:46] <agoliveira> Mithrandir: Yes, that's true. Well, if you think so, it's the same to me.
[03:46] <Mithrandir> hm, we should probably get upstream's SVN imported
[03:47] <Mithrandir> any chance you could get it imported?  http://svn.o-hand.com/repos/matchbox/trunk/matchbox-window-manager
[03:47] <agoliveira> I still don't get power to do it. I can just prepare and ask.
[03:48] <agoliveira> But we already have it on main so what do you suggest?
[03:49] <Mithrandir> well, upstream's repo is the one listed above; I suggest we get that imported, branch into ~ubuntu-mobile and work on getting a good package there.
[03:51] <agoliveira> I understood that, I mean we already have a matchbox WM in the gutsy repository. Are you talking about replace it?
[03:51] <Mithrandir> oh, yes, or just update it with the patches we want
[03:52] <agoliveira> Ah, fine. I just tought that was exactly to not mess with the current package that Matt asked to import that one in a different branch.
[03:53] <agoliveira> that one = maemo's
[04:09] <Mithrandir> now, let's see if this thingabob builds.
[04:12] <agoliveira> Mithrandir: Are you talking about which one?
[04:12] <Mithrandir> matchbox-wm
[04:13] <agoliveira> Ok, so I think we should sync here :) Have you imported from svn and are building it or just building the one from maemo that I imported before?
[04:14] <Mithrandir> no. :-)
[04:14] <Mithrandir> I've taken the delta between maemo's svn version and the one already in the archive and blatted most of the delta onto the latter.
[04:15] <agoliveira> Got it.
[04:16] <Mithrandir> I'd like to get an import of upstream svn so we can look at what the delta there is and get it down.
[04:21] <agoliveira> Fine. I'll arrange that on LP.
[04:23] <agoliveira> Done. Just need to poke someone to import it.
[04:24] <Mithrandir> thanks a lot
[04:24] <agoliveira> (Less than 2.5 minutes - I'm getting good at this ;) )
[04:24] <Mithrandir> yup, you are. :-)
[04:24] <agoliveira> https://launchpad.net/matchbox-window-manager
[04:24] <Mithrandir> this compiled for me now, so I'll just upload it and hope it doesn't break too much
[04:24] <agoliveira> Cool
[04:24] <Mithrandir> my brain is about to melt so I'll go do something else for a bit
[04:26] <agoliveira> I know what is like :) I'm going lunch in a few minutes.
[04:27] <agoliveira> http://www.youtube.com/watch?v=HQgF0pRkjMc
[04:28] <Mithrandir> there, uploaded.
[04:28] <Mithrandir> go wild testing it when it's built?
[04:29] <agoliveira> Sure. I'll try it out as soon as it gets there.
[04:29] <Mithrandir> cheers
[04:50] <TeTeT> will Ubuntu Mobile support the Menlow platform? on the wiki most seem to be for McCaslin.
[05:12] <Mithrandir> TeTeT: yes
[07:25] <rusty> has anyone noticed that attempting to install "hal" in a chroot will now fail in the postinst script while attempting to start hal?
[07:26] <rusty> looks like something that happened over night
[07:56] <agoliveira> New matchbox window manager seens to be running ok. I've being playing with it a bit now with no crashes.
[07:59] <agoliveira> Mithrandir: Looks like your changes didn't break anything very basic. Let's see if the other guys find anything.
[07:59] <agoliveira> By "very basic" I mean anything so obvious that a can crash right away ;)
[07:59] <agoliveira> a/a/I
[08:00] <agoliveira> Geez... I think I need a coffee
[08:04] <agoliveira> rusty, bobux: New matchbox-window-manager is on the repository. Give it a shot if you dare ;)
[08:04] <rusty> what package version is that?
[08:10] <agoliveira> Version: 1.2-1ubuntu1
[08:11] <agoliveira> This is our matchbox wm with Maemo patches applied.
[08:42] <agoliveira> rusty: I would like to talk about the startup script when you have some time.
[08:43] <rusty> i can talk now... worse case there will be some delay when somebody ask me a question in the phone meeting i am in
[08:44] <rusty> crap... now i see why installing hal inside a chroot is breaking
[08:45] <agoliveira> rusty: Don't need to be now, I can wait a bit.
[08:45] <rusty> agoliveira, lets go ahead and chat
[08:46] <agoliveira> Fine. To me. So, what do you have in mind?
[08:46] <rusty> well... i think we need a mininalized display manager
[08:47] <rusty> where at the very least, we start with an upstart script that reads a config to find the default user, and then starts X and then starts a bunch of session scripts
[08:47] <agoliveira> As a mean to login? Multiple users?
[08:48] <rusty> eventually, this would provide the ability to have multi-user login
[08:48] <rusty> right now i have a helloworld upstart script that runs startx as root
[08:48] <rusty> and then have /root/.xinitrc that startsup hildon
[08:49] <agoliveira> If you think multi user is necessary (and I tend to agree), I would go for the minimal-gdm from start.
[08:49] <rusty> this is a bit of a hack, but works
[08:49] <rusty> what all does a minimal-gdm pull in?
[08:49] <agoliveira> BTW, minimal-gdm is a way of speak :) I don't actually know if there is one :)
[08:50] <agoliveira> I'll have to check if there is such a beast.
[08:50] <rusty> ok
[08:50] <agoliveira> But if there is, it will make things easier for us.
[08:50] <rusty> so then... what all does gdm bring in?
[08:52] <agoliveira> Well, from start, things like remote logins we don't need I guess.
[08:52] <rusty> yea
[08:52] <agoliveira> perhaps we could try XDM
[08:52] <rusty> i was thinking more long term
[08:53] <agoliveira> Hmmm...
[08:53] <rusty> hell, we can just have an upstart script and configure xinitrc
[08:53] <rusty> that is, configure xinitrc to startup hildon-desktop and all it's deps
[08:53] <agoliveira> I think we need to round up what we need and choose something based on this but, for starts, I don't think that we need to put our expectations very high or we might get in trouble with lots of libs, dependencies, etc
[08:54] <rusty> is there a mdm?  as in mobile desktop manager?
[08:54] <agoliveira> What about xdm? It's simple but flexible enough I guess.
[08:54] <agoliveira> Dunno
[08:55] <agoliveira> Give some time to reseach a bit
[08:55] <rusty> it's just if we created something real quick, where for starters it's a simple upstart script, then we could add a new package called something like mdm
[08:58] <agoliveira> Let's compromize then, give me today to research the subject and if I didn'y come out with something we do our way, is that ok?
[08:59] <rusty> ok
[09:00] <agoliveira> Deal
[09:48] <Mithrandir> use gdm with autologin?
[09:48] <Mithrandir> rusty: have you had any progress on the project-builder front, doing stuff as non-root?
[09:48] <Mithrandir> or would you like me to plunge into it?
[10:18] <agoliveira> Mithrandir: we are talking about having something lighter than gdm but with more or less the same main features.
[10:19] <Mithrandir> agoliveira: but why?
[10:19] <agoliveira> Mithrandir: Why what? No use gdm or use something similar? :)
[10:19] <Mithrandir> why not use gdm
[10:19] <Mithrandir> ?
[10:20] <agoliveira> It is an option but if we are thinking about reduce resurces, I want to check lighter alternatives.
[10:20] <agoliveira> reduce dependencies, etc
[10:21] <agoliveira> I did not eliminate the idea of using gdm, just want to be sure it's the best way.
[10:22] <Mithrandir> I think we should use gdm if we want to have multiuser support (something I'm not convinced we really want) or just an upstart script or similar if not.
[10:23] <agoliveira> I think that at least for webpads, multiuser is good as it's not a very personal device, it's expensive and, as such, tend to be shared.
[10:26] <Mithrandir> depends on where in the world you are, I guess.. I consider a laptop (which is even more expensive) a personal device which I don't share with anybody.
[10:28] <agoliveira> Mithrandir: Well, I don't share mine either but I do share my n770 with my wife (not now, I got her a Palm TX :) ) so, anyway, there's aways the option to autologin.
[10:29] <Mithrandir> yeah
[10:30] <agoliveira> Anyway, so far I didn't see much difference between using XDM or GDM, for instance. GDM is bigger, of course, but we do have space and GDM integrates better, looks nicer. So, I'm between use GDM or nothing, just a startup script.
[11:31] <rusty> Mithrandir, i still need to do the changes to project-builder


[15:06] <kramsmada> Hey all, I was trying to sign the Ubuntu Code of Conduct but I keep getting a "(7, 8, u'Bad signature')" error. Any ideas?
[15:37] <mdeslaur_> dobey: he's back again; https://bugs.launchpad.net/~mohgty
[17:21] <dobey> mdeslaur_: suspended
[20:57] <kramsmada> Hey all, I was trying to sign the Ubuntu Code of Conduct but I keep getting a "(7, 8, u'Bad signature')" error. Any ideas?


[11:12] <DasEi> I got a queston concerning generall habit in compiling, or better compiling advice
[20:50] <daubers> Hey all, after a few ... disagreements on a few things in the -uk channel, an etherpad doc of some loose guidelines has been cobbled together. I'm in the process of digging around for more input if you're interested. http://pad.ubuntu-uk.org/atS35AtTW5


[07:37] <Foxy-> Hello
[07:38] <Foxy-> hay?you can hear me?
[07:39] <Foxy-> oh,I want write-you can see me?
[07:44] <Foxy-> Hello?
[07:58] <Foxy-> Helloooooo!
[19:42] <nikolam> Seems to me that Select folder dialogue (when running baobab for example ) now does not allows me to enter and select a path entered with Ctrl+L ...
[19:43] <nikolam> Can someone re-check Ctrl+L and entering path in open dialogue (select folder) ?


[01:20] -queuebot:#ubuntu-release- Unapproved: python-tz (lunar-proposed/main) [2022.7.1-2 => 2022.7.1-3] (desktop-core, i386-whitelist) (sync)
[02:04] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Lunar Beta] (20230328) has been added
[02:13] -queuebot:#ubuntu-release- Builds: Edubuntu Desktop amd64 [Lunar Beta] (20230328) has been added
[02:21] -queuebot:#ubuntu-release- Builds: Xubuntu Minimal amd64 [Lunar Beta] (20230328) has been added
[03:00] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Lunar Beta] (20230328) has been added
[03:10] <vorlon> bdmurray, ginggs: so as I mentioned above, I'd like to un-NBS libevent-2.1-7a and libevent-core-2.1-7a; but I missed the freeze cutoff.  Should I upload it tonight?
[05:31] -queuebot:#ubuntu-release- Unapproved: libevent (lunar-proposed/main) [2.1.12-stable-8ubuntu2 => 2.1.12-stable-8ubuntu3] (core, i386-whitelist)
[05:32] <vorlon> bdmurray, ginggs: uploaded for consideration, it can always sit there until after beta
[05:47] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Lunar Beta] (20230328) has been added
[06:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Lunar Beta] (20230328) has been added
[06:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Lunar Beta] (20230328) has been added
[06:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Lunar Beta] (20230328) has been added
[06:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Lunar Beta] (20230328) has been added
[06:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Lunar Beta] (20230328) has been added
[06:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Lunar Beta] (20230328) has been added
[06:28] -queuebot:#ubuntu-release- Unapproved: openvswitch (jammy-proposed/main) [2.17.3-0ubuntu<IP_ADDRESS> => 2.17.5-0ubuntu<IP_ADDRESS>] (core)
[06:40] -queuebot:#ubuntu-release- Unapproved: debian-archive-keyring (lunar-proposed/universe) [2023.1ubuntu1 => 2023.2ubuntu1] (core)
[06:41] -queuebot:#ubuntu-release- Unapproved: gnupg2 (lunar-proposed/main) [2.2.40-1ubuntu2 => 2.2.40-1.1ubuntu1] (core, i386-whitelist)
[06:52] <LocutusOfBorg> ^^ fix for the autopkgtest sadness
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Lunar Beta] (20230328) has been added
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Lunar Beta] (20230328) has been added
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Lunar Beta] (20230328) has been added
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+icicle [Lunar Beta] (20230328) has been added
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+licheerv [Lunar Beta] (20230328) has been added
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+nezha [Lunar Beta] (20230328) has been added
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Lunar Beta] (20230328) has been added
[07:13] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+visionfive [Lunar Beta] (20230328) has been added
[07:21] -queuebot:#ubuntu-release- Unapproved: strace (lunar-proposed/main) [5.19-0ubuntu1 => 6.2-0.1ubuntu1] (core)
[08:44] -queuebot:#ubuntu-release- Builds: Ubuntu Core amd64 edge [Lunar Beta] (20230328) has been added
[08:44] -queuebot:#ubuntu-release- Unapproved: ipmitool (lunar-proposed/universe) [1.8.19-1ubuntu1 => 1.8.19-5] (no packageset) (sync)
[08:45] -queuebot:#ubuntu-release- Unapproved: accepted ipmitool [sync] (lunar-proposed) [1.8.19-5]
[08:55] <seb128> hum, bug #2012735, the recent ubuntu-advantage-tools landing broke ubuntu-manager
[08:55] -ubottu:#ubuntu-release- Bug 2012735 in ubuntu-advantage-tools (Ubuntu) "update-manager crashed with uaclient.exceptions.UserFacingError in get_lscpu_arch()" [Critical, Confirmed] https://launchpad.net/bugs/2012735
[08:56] <seb128> orndorffgrant, ^
[09:04] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop (Legacy) amd64 [Lunar Beta] (20230328) has been added
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted libevent [source] (lunar-proposed) [2.1.12-stable-8ubuntu3]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted strace [source] (lunar-proposed) [6.2-0.1ubuntu1]
[09:27] -queuebot:#ubuntu-release- Unapproved: accepted python-tz [sync] (lunar-proposed) [2022.7.1-3]
[10:01] -queuebot:#ubuntu-release- Unapproved: python-markdown (lunar-proposed/main) [3.4.1-2 => 3.4.3-1] (i386-whitelist, ubuntu-desktop, ubuntu-server) (sync)
[10:38] -queuebot:#ubuntu-release- Unapproved: rhythmbox (lunar-proposed/main) [3.4.6-2ubuntu2 => 3.4.6-2ubuntu3] (ubuntu-desktop)
[11:12] <fossfreedom> release-team - please can I ask when will Ubuntu Budgie pop out of the build factory?  TIA
[12:01] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Lunar Beta] (20230328) has been added
[12:01] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Lunar Beta] (20230328) has been added
[12:01] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Lunar Beta] (20230328) has been added
[12:01] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity riscv64 [Lunar Beta] (20230328) has been added
[12:01] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Lunar Beta] (20230328) has been added
[12:11] <ricotz> hello ubuntu-archive, I am still hoping for some progress at https://code.launchpad.net/~ricotz/ubuntu-archive-tools/+git/ubuntu-archive-tools/+merge/432979
[12:18] <seb128> ricotz, hey, I tried to ping Alberto about it
[12:19] <ricotz> seb128, hey :), thanks
[12:21] -queuebot:#ubuntu-release- Unapproved: rejected net-snmp [source] (bionic-proposed) [5.7.3+dfsg-1.8ubuntu3.9]
[12:22] <ricotz> regarding autopkgtests for libreoffice/i386, seems the numerous "results" are not picked up on update_excuses - https://autopkgtest.ubuntu.com/packages/libr/libreoffice/lunar/i386
[12:30] -queuebot:#ubuntu-release- Unapproved: libcamera (lunar-proposed/universe) [0.0.4-2ubuntu2 => 0.0.4-3ubuntu1] (i386-whitelist)
[12:31] -queuebot:#ubuntu-release- Unapproved: accepted libcamera [source] (lunar-proposed) [0.0.4-3ubuntu1]
[12:32] <jamespage> o/
[12:33] <jamespage> please can the openvswitch upload from january in the jammy UNAPPROVED queue be rejected - fnordahl has prepared a new version which incorporates the security update that was released after it was uploaded
[12:37] <seb128> jamespage, the new upload description doesn't really convey that, it states 'd/p/CVE-2022-433x.patch: Drop, included in 2.17.5 point release.'
[12:37] <seb128> https://launchpadlibrarian.net/658159822/openvswitch_2.17.5-0ubuntu<IP_ADDRESS>_source.changes
[12:40] <seb128> jamespage, also
[12:41] <seb128> $ debdiff openvswitch_2.17.5-0ubuntu<IP_ADDRESS>.dsc openvswitch_2.17.5-0ubuntu<IP_ADDRESS>.dsc | diffstat
[12:41] <seb128>  changelog |   16 ++++++++++++++++
[12:41] <seb128>  1 file changed, 16 insertions(+)
[12:41] <jamespage> hmm - letme check with Frode
[12:41] <seb128> thanks
[12:41] <jamespage> TBH we can fold the changelog entries together as the .1 never got accepted
[12:42] <seb128> well it's rather that the new upload only touch the changelog so what's the point?
[12:42] <seb128> something seems wrong
[12:42] <jamespage> it's acknowledging the security update that happened in the meantime
[12:42] <jamespage> the diff from the sec update to the .2 should be smalled
[12:43] <seb128> I would just have reuploaded .1 with the extra changelog entry
[12:43] <seb128> you can reuse versions which haven't been approved
[12:43] <seb128> the top entry is confusing as it is atm imho
[12:43] <jamespage> yes that's exactly the conversation I just had with fnordahl
[12:44] <jamespage> can you reject that one as well then and I'll upload a less verbose version
[12:45] -queuebot:#ubuntu-release- Unapproved: rejected openvswitch [source] (jammy-proposed) [2.17.5-0ubuntu<IP_ADDRESS>]
[12:45] -queuebot:#ubuntu-release- Unapproved: rejected openvswitch [source] (jammy-proposed) [2.17.5-0ubuntu<IP_ADDRESS>]
[12:45] <seb128> jamespage, ^
[12:45] <jamespage> seb128: lovely thanks :)
[12:45] <seb128> np!
[12:48] -queuebot:#ubuntu-release- Unapproved: openvswitch (jammy-proposed/main) [2.17.3-0ubuntu<IP_ADDRESS> => 2.17.5-0ubuntu<IP_ADDRESS>] (core)
[13:31] <jbicha> ubuntu-release: please unblock mutter & gnome-shell. gnome-shell fixes critical issue preventing starting Firefox LP: #2011806  mutter re-enables triple buffering where Desktop wants more testing
[13:31] -ubottu:#ubuntu-release- Launchpad bug 2011806 in snapd (Ubuntu) "[lunar] Snaps don't launch due to cgroup issue" [Critical, Confirmed] https://launchpad.net/bugs/2011806
[13:31] <jbicha> those 2 packages are also waiting for s390x autopkgtests but we don't support gnome-shell on s390x so I request those tests be ignored this time
[13:36] <ginggs> jbicha: ack, looking
[13:40] -queuebot:#ubuntu-release- Unapproved: network-manager (lunar-proposed/main) [1.42.4-1ubuntu1 => 1.42.4-1ubuntu2] (desktop-core, i386-whitelist)
[13:46] <seb128> could you also unblock software-properties, we need to rollback the Ubuntu Pro tab addition since the service isn't going to be ready for release
[13:46] <seb128> also we would like reverted in the beta build to avoid people picking that UI up in screenshots or talking about it when it's not going to be available in fact
[13:47] <seb128> also accountsservice fixes a crasher that could impact gnome-shell in some cases
[13:48] <seb128> and network-manager ^ fixes tests, it's not a must have for beta just a would be nice
[13:59] <ginggs> seb128: ack, looking
[14:06] <ginggs> seb128: software-properties and accountsservice unblocked
[14:07] <ginggs> is there a fix coming for LP: #2009543 soon, or would you like network-manager 1.42.4-1ubuntu1 as it is?
[14:07] -ubottu:#ubuntu-release- Launchpad bug 2009543 in network-manager (Ubuntu) "network-manager nm.py autopkgtest needs to be updated for 1.42" [High, In Progress] https://launchpad.net/bugs/2009543
[14:09] <seb128> ginggs, thanks
[14:09] <seb128> ginggs, the fix is the one in the unapproved queue
[14:10] <seb128> for n-m
[14:10] <seb128> http://launchpadlibrarian.net/658221787/network-manager_1.42.4-1ubuntu1_1.42.4-1ubuntu2.diff.gz
[14:11] <ginggs> seb128: ok, i see it
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted network-manager [source] (lunar-proposed) [1.42.4-1ubuntu2]
[14:17] <seb128> thanks!
[14:42] <fossfreedom> ginggs: any idea when the Ubuntu Budgie lunar beta build will be available?  TIA
[14:52] <vorlon> fossfreedom: no evidence that a beta candidate build has been triggered for ubuntu-budgie; let me see about taking inventory
[14:55] <fossfreedom> Cheers - guessing the same for Ubuntu Unity ... and for the "new ubuntu" rather than the legacy.
[15:13] <ginggs> fossfreedom: still waiting on some autopkgtests and availability of someone who can spins the images
[15:14] <ginggs> so maybe today still, or early tomorrow
[15:15] <vorlon> ginggs: is spinning the images not something you can do via the ISO tracker?
[15:15] <vorlon> anyway I'm around today so give me the signal when you want me to spin things
[15:16] <ginggs> vorlon: ack, thanks
[15:48] <ItzSwirlz> Hi release team. I see that sc-im is failing in lunar-proposed, but apparently (and I wasn't subscribed to the debian BTS for sc-im) there is a potential copyright problem in sc-im.
[15:49] <ItzSwirlz> So, i can fix it, but where should I go from here, does this necessitate a removal? Because this copyright file has been in there for over a year.
[15:55] <vorlon> ItzSwirlz: specific bug links helpful.  I see we're talking about Debian bug #1029570.  As this is a pre-existing issue in the package we currently ship in lunar, it has no bearing on whether the failures in lunar-proposed should be fixed; but also if you fix it then why would there need to be a removal anywhere?
[15:55] -ubottu:#ubuntu-release- Debian bug 1029570 in sc-im "sc-im: debian/copyright file seems to be inaccurate" [Serious, Open] https://bugs.debian.org/1029570
[15:55] <ItzSwirlz> vorlon: Just asking if one is warranted, at least until it gets fixed.
[15:55] <vorlon> nah
[15:56] <vorlon> it's in stable releases already, and this doesn't rise to the level of a bug that we would remove it from a release pocket over
[15:56] <ItzSwirlz> okay, so 0.8.3 has more features but, post-feature freeze so i'll put aside the build failure
[15:56] <ItzSwirlz> so, should i fix the copyright in a .debdiff and ask for it to be uploaded
[15:57] <vorlon> also fwiw this is a matter for the Archive Admin Team rather than the Release Team, but still happy to field such questions here
[15:58] <ItzSwirlz> well, the main issue is probably that third clause
[15:59] <ItzSwirlz> should i add it in or wait until the maintainer responds whether expat is fine
[15:59] <ItzSwirlz> but the LICENSE file would stay the same, so..
[15:59] <vorlon> um the license in debian/copyright should be fixed to match the license we know we have been given by upstream; there's no reason to wait
[15:59] <vorlon> if upstream later clarifies that a different license is ok, that's separate
[16:00] <ItzSwirlz> vorlon: expect debdiff in ~10 mins
[16:00] <vorlon> what do you mean wrt putting aside the build failure? this package was synced before feature freeze, the freeze is not applicable
[16:01] <ItzSwirlz> yeah i was just about to get to that, pull-lp-source is trying to pull 0.8.3. so should i fix the -proposed build + the copyright and send it in a debdiff?
[16:01] <vorlon> yes
[16:01] <ItzSwirlz> I was thinking i would just fix the copyright in 0.8.2 but since it was synced pre-feature freeze i'll fix that
[16:01] <vorlon> you don't get to back the package out of -proposed to land a debian/copyright fix :)
[16:01] <ItzSwirlz> im creating an sbuild right now
[16:02] <ItzSwirlz> so fix 0.8.2 or 0.8.3 (proposed)?
[16:02] <vorlon> 0.8.3!
[16:02] <ItzSwirlz> on it
[16:05] <ItzSwirlz> right, so looking at https://github.com/andmarti1424/sc-im/blob/b4cfc3fef326f78b8c683707f0819886ddcd82bd/LICENSE, and i just read the OAC page, is this still BSD-4?
[16:06] <vorlon> it is technically BSD-4-*like* because the actual BSD license references the University of California, but close enough for government work :P
[16:07] -queuebot:#ubuntu-release- Unapproved: anacron (kinetic-proposed/main) [2.3-33ubuntu1 => 2.3-33ubuntu2] (desktop-core)
[16:07] <vorlon> but yes it's BSD-4 (note the 4 bullet points), not BSD-3
[16:10] <ItzSwirlz> as suggested can i also change the debian/* license to match
[16:11] <ItzSwirlz> actually nvm, what i have works
[16:11] <ItzSwirlz> gpl-2+ is fine
[16:13] <vorlon> you cannot change the maintainer's declarations of license for the contents of debian/* without the maintainer saying so, nor should you have any reason to
[16:14] <ItzSwirlz> i am the maintainer of debian/*
[16:15] <vorlon> ah, I missed the Uploaders field
[16:15] <ItzSwirlz> no problem
[16:15] <vorlon> I should say "copyright holder" rather than "maintainer"
[16:15] <vorlon> (in this case, the same person)
[16:15] <ItzSwirlz> yeah, with my username I'm probably the last person you'd expect
[16:16] <vorlon> I just didn't see any connection between this package description and your other work ;)
[16:16] <Eickmeyer> Can confirm, he's on the Debian math team, part of his schooling.
[16:17] <ItzSwirlz> Linker still failing with ncursesw. yay.
[16:21] <Eickmeyer> vorlon: Just for a matter of opinion, I'm having trouble finding the incompatibility asserted in that bug report between BSD-4 and GPL-2. Thoughts?
[16:26] <cjwatson> GPLv2 section 6 "You may not impose any further restrictions on the recipients' exercise of the rights granted herein", and the advertising clause of BSD-4 is a further restriction over and above the terms of GPLv2
[16:28] <Eickmeyer> cjwatson: I see, so that is an incompatibility. The upstream of sc-im is being very staunch and unwavering on removing the fourth clause, so that means debian/* does need to change to something else, which is problematic for ItzSwirlz.
[16:28] <Eickmeyer> https://github.com/andmarti1424/sc-im/issues/50
[16:28] -ubottu:#ubuntu-release- Issue 50 in andmarti1424/sc-im "About the license" [Closed]
[16:28] <cjwatson> It's a very well-established incompatibility, e.g. mentioned on https://www.gnu.org/licenses/license-compatibility.html
[16:29] <Eickmeyer> I read that, but sometimes Stallman's opinion is overopinionated and not reviewed by a third party.
[16:30] <cjwatson> I realize RMS is ... RMS, but in this case I don't think it's a seriously contested opinion
[16:30] <ItzSwirlz> we don't talk about rms, no no no no
[16:30] <ItzSwirlz> But seriously, I don't think the OAC is that big of a deal
[16:30] <ItzSwirlz> But again I have a limited view of how licenses work
[16:30] <vorlon> Eickmeyer: no, there is no prohibition on the packaging having a different copyright than the upstream source
[16:31] <ItzSwirlz> Okay I FINALLY got the build to work. It was missing an LDLIB flag
[16:31] <vorlon> the copyright of debian/* almost never contaminates the package
[16:31] <Eickmeyer> vorlon: Ok, so then the opinion in the bug report is wrong and the bug should be closed.
[16:31] <ItzSwirlz> it can have a copyright of a different license but recently from what i've learned newer packages use the same
[16:31] <vorlon> the bug should not be closed if debian/copyright incorrectly documents the upstream copyrighT!
[16:31] <Eickmeyer> ...as soon as it's fixed with the BSD-4 being in there.
[16:31] <vorlon> right
[16:31] <cjwatson> I usually consider it risky for them to be outright incompatible, because (a) the resulting binaries are clearly derived works of both the upstream licence and the packaging licence, and (b) debian/patches/
[16:32] <vorlon> ItzSwirlz: "newer packages" meh it's entirely up to the individual maintainer
[16:32] <vorlon> yes, what Colin says wrt debian/patches
[16:32] <Eickmeyer> So, debian/patches/* can be a different license then.
[16:32] <cjwatson> This is definitely all possible but usually seems like gratuitously making trouble for oneself to me
[16:33] <vorlon> I mean, you can license your files however you want, and debian/copyright is just a container for expressing what that license is
[16:33] <vorlon> but if you write patches, put them in debian/patches, and declare them to have a license incompatible with that of the upstream code, we have a problem
[16:34] <Eickmeyer> That's pretty much what I'm getting at.
[16:34] <Eickmeyer> Declare the patches with a compatible license to the upstream code.
[16:34] <Eickmeyer> Of course, like cjwatson was saying, that does get rather atomic.
[16:37] <vorlon> I think my view on this differs slightly from cjwatson's because the UK unlike the US doesn't have a notion in law of "minimum creative input" in establishing copyright, and I'm stubbornly persistent in believing that on this one thing, US law is better and everyone else should just conform
[16:37]  * ItzSwirlz looks at what he has started
[16:38] <ItzSwirlz> With all respect your view in the UK is probably better than mine, with our 'liberty copyright'
[16:38] <vorlon> (and also that if you get it wrong the chances of actually being sued are negligible)
[16:38] <cjwatson> Also perhaps I've seen some pretty damn creative debian/rules files
[16:38] <vorlon> ItzSwirlz: you could've saved yourself time and just read 20 years of debian-legal mailing list archives
[16:38] <Eickmeyer> vorlon: XD
[16:39] <sarnold> lol
[16:39] <ItzSwirlz> vorlon: okay that's older than how I am so no way in heck im reading that
[16:39]  * cjwatson exchanges Zimmer frames with vorlon
[16:39] <ItzSwirlz> I'm running a final sbuild test, create a debdiff, put it on a paste and sent it to vorlon
[16:41] <vorlon> cjwatson: :D
[16:41] <ItzSwirlz> "E: sc-im changes: bad-distribution-in-changes-file lunar-arm64" my apologies lintian, you're just jealous that i'm running a better cpu
[16:42] <tobhe> ItzSwirlz: m1?
[16:43] <ItzSwirlz> tobhe: ?
[16:44] <ItzSwirlz> vorlon: https://pastebin.ubuntu.com/p/32XKVxJcW9/
[16:44] <tobhe> the cpu
[16:44] <ItzSwirlz> oh, i thought you said "M L" as in mailing list. Yep, M1.
[16:45] <ItzSwirlz> Faster than my gaming pc at home
[16:45] <ItzSwirlz> I'll stay on until vorlon can confirm everything is good
[16:45] <tobhe> nice :)
[16:45] <ItzSwirlz> wait
[16:45] <ItzSwirlz> wait
[16:46] <ItzSwirlz> why did the .patch file in the debdiff not have a description-
[16:47] <ItzSwirlz> vorlon, my ~20 rebuilds i did may have confused the debdiff so that's why it looks like there was already an empty patch file there
[16:50] <arraybolt3> ItzSwirlz: Actually I think that particular lintian warning is Lintian unhappy with the fact that you're using sbuild at all. I get those constantly and ignore them without a second thought.
[16:50] <arraybolt3> (re: bad-distribution-in-changes-file)
[16:50] <ItzSwirlz> (yeah that's the actual reason why, it also does with experimental and unstable)
[16:58] <jbicha> speaking of minimum creative input, Debian ftpmasters forced me to add a copyright reference for https://salsa.debian.org/gnome-team/text-engine/-/blob/debian/master/debian/patches/meson-set-soversion.patch
[17:02] <sarnold> ha
[17:03] <ItzSwirlz> okay, i don't want to fall behind in class. Email me if something goes wrong ith the patch
[17:03] <arraybolt3> Hey, I uploaded a fix in lubuntu-update-notifier that resolves https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2012823 and https://bugs.launchpad.net/ubuntu/+source/lubuntu-update-notifier/+bug/2012702, can someone wave my Lunar upload through the Beta Freeze?
[17:03] -ubottu:#ubuntu-release- Launchpad bug 2012823 in lubuntu-update-notifier (Ubuntu Lunar) "lubuntu-notifier.py crashes with a type mismatch error when packages are to be removed" [Undecided, New]
[17:03] -ubottu:#ubuntu-release- Launchpad bug 2012702 in lubuntu-update-notifier (Ubuntu) "Download progress indicators no longer appear in Lunar" [Undecided, New]
[17:03] <arraybolt3> I'd really like those two fixes in the Lubuntu beta.
[17:03] <arraybolt3> (There's also two SRU uploads that fix the first of the two bugs, but those can wait. I just need the Lunar ones to go through.)
[17:05] <arraybolt3> Also it looks like something's gotten Lubuntu builds hung up, /me looks closer
[17:08] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Lunar Beta] (20230328) has been added
[17:08] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64 [Lunar Beta] (20230328) has been added
[17:12] <arraybolt3> Found it, I need a MOTU to fix the dependencies on libqt5webenginecore5. It's depending on libevent-2.1-7, it should depend on libevent-2.1-7a, which replaces the earlier version.
[17:13] <arraybolt3> Lubuntu is unable to build since something in it pulls in qml-module-qtwebengine, which pulls in libqt5webenginecore5, which is pulls in libevent-2.1-7, which then conflicts with libevent-2.1-7a which is pulled in probably by transmission-qt.
[17:14] <arraybolt3> This may already be fixed I'm realizing, maybe qtwebengine is still buidling...
[17:15] <arraybolt3> Nope, it looks like it's not there yet.
[17:23] <arraybolt3> Either that needs changed *or* I need to find whatever's puling in qtwebengine in Lubuntu. Which, if I were to guess, is probably Discover... and that is probably not something we can just remove this close to release.
[17:41] <jbicha> arraybolt3: maybe that's already fixed by https://launchpad.net/ubuntu/+source/libevent/2.1.12-stable-8ubuntu3 (still in lunar-proposed)
[17:42] <arraybolt3> Oh thank goodness. Looks like you're right.
[17:42] <vorlon> Eickmeyer: if you see him before me, can you tell ItzSwirlz that pastebin is an absolutely terrible way to communicate patches? :P
[17:42] <Eickmeyer> vorlon: Will do. I'll tell him to file a bug report in the future.
[17:43] <arraybolt3> (Also it was indeed Discover pulling in qtwebengine.)
[17:44] <arraybolt3> OK, so in that instance all we need are is lubuntu-update-notifier to migrate and then I *think* we're set for the beta.
[17:44] <arraybolt3> s/are//
[17:49] <vorlon> Eickmeyer: also the debdiff he posted there contains no substantive changes
[18:02] <vorlon> seb128: the grub source package is grub2 not grub, please :)  (How I wish launchpad disabled reporting of bugs against source packages that are no longer published anywhere)
[18:17] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Lunar Beta] (20230328) has been added
[18:23] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Lunar Beta] (20230328) has been added
[18:24] <arraybolt3> jbicha: Actually that libevent change is ready to migrate and just needs let through.
[18:24] <arraybolt3> Oh, wait, it also has a ton of autopkgtests in progress.
[18:25] <arraybolt3> Sigh, why does Britney not list the most obstructive problem when it says something is blocked...
[18:41] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Lunar Beta] (20230328) has been added
[18:45] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Lunar Beta] (20230328) has been added
[19:01] <seb128> vorlon, ack
[19:27] <bdmurray> FYI bos01 is unusable so port queues are processing more slowly than normal :-(
[19:38] <seb128> the infra went really unreliable this cycle, I think that's something we should escalade
[19:38] <seb128> we can't work correctly on something that unreliable
[20:18] -queuebot:#ubuntu-release- Unapproved: sc-im (lunar-proposed/universe) [0.8.3+ds-1 => 0.8.3+ds-1ubuntu1] (no packageset)
[20:20] -queuebot:#ubuntu-release- Unapproved: accepted sc-im [source] (lunar-proposed) [0.8.3+ds-1ubuntu1]
[20:40] -queuebot:#ubuntu-release- Unapproved: spamassassin (kinetic-proposed/main) [3.4.6-1build3 => 3.4.6-1ubuntu<IP_ADDRESS>] (ubuntu-server)
[20:42] -queuebot:#ubuntu-release- Unapproved: spamassassin (jammy-proposed/main) [3.4.6-1build3 => 3.4.6-1ubuntu<IP_ADDRESS>] (ubuntu-server)
[20:43] -queuebot:#ubuntu-release- Unapproved: spamassassin (focal-proposed/main) [3.4.4-1ubuntu1.1 => 3.4.4-1ubuntu1.2] (ubuntu-server)
[20:57] -queuebot:#ubuntu-release- Unapproved: ledger (lunar-proposed/universe) [3.3.0-1 => 3.3.0-3] (no packageset) (sync)
[20:58] -queuebot:#ubuntu-release- Unapproved: accepted ledger [sync] (lunar-proposed) [3.3.0-3]
[21:02] -queuebot:#ubuntu-release- New source: testng7 (lunar-proposed/primary) [7.5~us1-0ubuntu1]
[21:49] <arraybolt3> ubuntu-archive: Sorry to be somewhat insistent here, but I'd really like to see a couple of bug fixes in lubuntu-update-notifier get into the Beta, and currently the update I pushed is stuck in the queue waiting to be unblocked. Bug reports are bug #2012702 and bug #2012823. Thanks!
[21:49] -ubottu:#ubuntu-release- Bug 2012702 in lubuntu-update-notifier (Ubuntu) "Download progress indicators no longer appear in Lunar" [Undecided, New] https://launchpad.net/bugs/2012702
[21:49] -ubottu:#ubuntu-release- Bug 2012823 in lubuntu-update-notifier (Ubuntu Lunar) "lubuntu-notifier.py crashes with a type mismatch error when packages are to be removed" [Undecided, New] https://launchpad.net/bugs/2012823
[21:57] <vorlon> arraybolt3: the queue being frozen is release team, not archive team. I have a meeting in a minute but will take a look after
[21:59] <arraybolt3[m]> Ah, OK.
[22:01] <vorlon> arraybolt3: ah this is easy, it's already accepted into -proposed an just needs unblocked; done
[22:15] <arraybolt3> Thanks!
[22:58] <bdmurray> bos01 is back
[23:17] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (kinetic-proposed) [0.54ubuntu0.2]
[23:24] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (jammy-proposed) [0.52ubuntu0.3]
[23:26] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (focal-proposed) [0.43ubuntu1.12]
[23:27] -queuebot:#ubuntu-release- Unapproved: accepted distro-info-data [source] (bionic-proposed) [0.37ubuntu0.16]
[23:54] <arraybolt3> I think we had better give the live system and installed system tests on the Beta images an extra-good workout since the GLib slice allocator removal has caused a lot of problems. First it was Openbox, then the timezone map in Ubiquity. Now it looks like it might be affecting Xubuntu with xfce4-power-manager, and I'm now reporting a bug in Caja in Ubuntu MATE that may be related.
[23:54] <arraybolt3> If there are too many problems, what are the chances we can switch back to the pre-slice-allocator-removal version of GLib?
[23:59] <sarnold> imho it'd be better to just go with it and collect bug reports from users -- that way we stand a better chance of getting all those programs fixed up before 24.04