=== 84XAAXM3W is now known as bradm === drizztbsd_ is now known as drizztbsd [00:11] can anybody here help me? [00:14] GanonKiller: Just ask your questino. If people are around and can assist, they will. [00:14] question [00:15] well pulseaudio keeps crashing [00:16] i am trying to fix it [00:16] i removed pulseaudio before & it killed gnome [00:16] How does it keep crashing? have you filed a bug? [00:16] yes i have filed a bug report [00:16] Do you have the bug number handy? [00:17] how do i find that out? [00:19] GanonKiller: If you know your launchpad username, then go to http://launchpad.net/~username/+subscribedbugs and you should find it there, unless you decided to unsubscribe yourself from the bug once you filed it. :) [00:21] i subscribed ... i just dont remember my info [00:23] GanonKiller: Check your email, you might have some email regarding the bug, which can tell you what bug number it is. [00:24] ok... well i sent the bug report via terminal command [00:25] Ok, let me see fi i can find it... [00:26] why ubuntu doesn't download and install packages in parallel? [00:27] well.. i think i need to change my sound profile [00:28] bencc: If you are using more than one mirror, I believe apt can download in parallel, as to why it doesn't download in parallel normally, I am ont entirely sure. As for installing, packages have to be installed in a specific order, to make sure dependencies are correctly resolved, as the install process of one package may rely on a previously installed package to complete. [00:29] TheMuso: the download order could be optimized so apt can install undependent packages while it downloads others [00:29] bencc: For parallel download I agree, but not for installing. [00:29] It needs all packages to be present to be able to work out the installation order. [00:30] TheMuso: I don't think so [00:30] TheMuso: if you want to upgrade apache and mysql at the same time [00:30] bencc: Others know more about this than I do, but I am pretty sure that this is just not possible. [00:30] it's possible that they don't share the same package so you can start upgrading mysql while downloading apache [00:32] TheMuso: I'm 99.99% positive it's posible [00:32] and I'm 100% positive it'll be cool [00:32] bencc: You might want to read up on apt and dpkg then, to find out how they currently do things. [00:33] too complicated... [00:34] :) [00:34] the fact that it's complicated doesn't mean my idea isn't simple or can't be done [00:35] trust me, it's the best thing since slice bread [00:35] I would have thought the implementation of your idea being complicated *did* mean that the idea wasn't simple, in practice :) [00:36] You'd need to do some deep dpkg diving; there's a bunch of global state in the form of package databases that you'd need to be sure won't be corrupted by multiple accesses. [00:36] RAOF: make things as simple as possible but not simpler than that [00:36] RAOF: now you are complicating stuff [00:36] I don't need multiple accesses [00:37] Yes, you do. [00:37] no, I don't [00:37] which is better... tunapie2 or rhythmbox? [00:37] you are just arguing for the sake of argument [00:37] GanonKiller: Ok I can't find any bugs that were recently filed against pulseaudio that have you're name, Dewey Van (Taken from whois on IRC). So unless you have a bug number, I am unable to help you further at this point. [00:37] probably tunapie2, because the 2 [00:37] ok [00:37] just kidding [00:37] You're installing two packages at once; that means you need to be able to access the package database (and debconf database, and such) from two separate installs. [00:38] RAOF: I'm not [00:38] i will take off rhythmbox [00:38] You're not installing two packages at once? [00:38] I thought that was your idea? [00:38] RAOF: no. I'm downloading and installing at the same time [00:38] it's different [00:39] installing two packages at once will be stupid [00:39] (I'm not) [00:39] That would indeed be easier; it's probably not *that* difficult. [00:40] right [00:40] and it's very very cool [00:40] Why don't you find out, by writing the patch? :) [00:40] maybe I will [00:40] do you want to help me with that [00:40] to share the glory [00:40] ? [00:41] ok.. i installing the other pulseaudio devices & removing rhythmbox [00:41] bencc: No, sorry; I've got other projects on my plate. [00:41] RAOF: like what? [00:41] what can possibly be more important than that? [00:42] ...like making your graphics work properly? [00:42] bencc: it's usually a good idea to have all the debs sitting on your disk before starting to install, in case something goes wrong that fucks up the network or something [00:42] Any number of things? C# bindings for libpulse, hacking on Do, gobject-introspection bindings for C#... [00:42] the odds of that are low, but I've definitely had situations where I was glad they were already there [00:42] is there to invert the 3d desktop cube? [00:43] taggart: Please be careful of your language in here, and abide by the Ubuntu code of conduct. [00:43] actually for really big upgrades I do "apt-get -d upgrade" first and get all the packages [00:43] TheMuso: bite me [00:43] RAOF: what is Do? [00:44] http://do.davebsd.com/ [00:44] bencc: Your idea sounds cool, but it's somewhat of a micro-optimisation. [00:44] hmmmm the alsa plugin is having issues... the volume is moving on its own [00:44] RAOF: ok [00:45] Do looks cool [00:46] themuso: The CoC doesn’t explicitly say anything about which words are good and which are bad. That’s very subjective. [00:47] ion: Ok. [00:47] I'm sure they don't want us to say fuck [00:47] oops :) [00:47] I think it's a pretty safe call that the word in question falls under ‘bad’. [00:48] Okay, i admit it was disrespectful towards the package that broke network. taggart: Please apologize to the package. [00:50] No. There are no rules for that in the CoC, that's about respect and raising disputes quickly and avoiding personal attacks and stuff. [00:50] Not using certain words is about our IRC guidelines. [00:50] !ohmy [00:50] Please remember that all Ubuntu IRC channels share the same attitude of providing friendly and polite interaction with all users of all ages and cultures. Basically, this means no foul language and no abuse towards others. [00:53] GanonKiller: When you say your alsa volume is moving on its own, what program are you looking at and using when it does this? [00:58] i forgot where to change the sound type? [00:58] oh lol... pulse audio volume control === jjohansen is now known as jj-afk [01:03] dang sound [01:04] i did install the vlc-plugin-pulse === BUGabundo is now known as BUGa_29plus1 [01:04] the alsa-playback volume keeps moving on its own [01:04] one of this days I'll get why PM tools work fine, and system suspend/hibernate doesn't [01:05] GanonKiller: When you are using vlc? [01:05] i am using VLC right now with tunapie2 [01:07] how do i restart the sound server'/ [01:07] GanonKiller: Why do you want to restart it? [01:08] it killed [01:09] right, as you previously stated. [01:09] sudo: /etc/init.d/alsa-utils: command not found [01:10] i cant restart [01:11] GanonKiller: Please reproduce the problem following this procedure: https://wiki.ubuntu.com/PulseAudio/Log and !pastebin it somewhere. [01:11] !pastebin [01:11] For posting multi-line texts into the channel, please use http://paste.ubuntu.com | To post !screenshots use http://tinyurl.com/imagebin | !pastebinit to paste directly from command line | Make sure you give us the URL for your paste - see also the channel topic. [01:19] heh... now my sound works [01:22] it turns the sound controller was controlling the app [01:22] *turns out [01:22] the volume was all the way down [01:23] i also had to change the output [01:24] thanks for your help muso === bjf is now known as bjf[afk] [02:32] Hallo. Who would I speak to about a dead official Ubuntu server? [02:33] Which one? [02:33] speglar.simnet.is [02:36] Let me call the person with the issue [02:36] persia: This is the person querying the server [02:36] You can get more information from them [02:36] This is Reykjavik,,,, do you read me? over......... [02:36] You could send a note to mirrors@ubuntu.com. Someone might be active in #ubuntu-mirrors. The admins at Siminn hf are the folks that really need to sort it. [02:36] :-) [02:37] * dasKreech leaves persia and Guest64905 :) [02:37] Yea thank you [02:38] Simnet.is is a big ISP its dificault to talk to them... the other server is in the uneversety [02:38] ubuntu.lhi.is [02:38] Guest64905, So, it looks like the administrator for that mirror has no public address on LP. You could try sending a note to mirrors@ubuntu.com reporting the mirror outage. You might find someone active in #ubuntu-mirrors (but I suspect not the Reykyavik admins at this hout) [02:38] Thank you I try [02:38] You could try using https://launchpad.net/ubuntu/+mirror/speglar.simnet.is-archive has a base set of information to contact the contact person, but without a public address, I presume they don't prefer to be contacted that way. [02:39] Good luck! [02:41] Oh, accursed heisenbug. [02:42] I am sending mirrors@ubuntu.com a message.... the ubuntu.lhi.is server is in the Icelandic part of this huge networ [02:42] http://www.nordu.net/ndnweb/nordunet___canarie_announces_icelink.html [02:42] What are my options for hunting down a memory corruption bug? Bug #651294 seems to be caused by something outside the resource code scribbling random(?) values over the memory held by the resource pointer, leading to badness when trying to free the resource. [02:42] Launchpad bug 651294 in xorg-server (Ubuntu) "X crash on KDM logout (still - yes, really)" [High,Confirmed] https://launchpad.net/bugs/651294 [03:25] RAOF, Well, if you happen to have a copy of the entire memory space, you can hope to find something meaningful in the otherwise random scribbling. [03:25] Or, I guess, set up some gdb watches on that memory address, and just eat the abysmal performance. [03:25] If you can reproduce, you can run large chunks of stuff through memory profilers (e.g. valgrind) at fairly slow speeds. [03:26] gdb is less abysmal than valgrind :) [03:26] But if you know the address that's being scribbled, it's not quite random ... [03:26] Oh, no. [03:27] The address is fixed; what's beeing written there seems random. [03:27] Or, rather, I know the address of the resource struct, and somewhere between being added and being freed something is scribbling on it. [03:27] In that case, you don't even need gdb: you could just poll that address repeatedly and spit out some output when it changes somewhere. [03:28] (still performance-bad, but less bad than all of gdb) [03:29] I might try the gdb watch approach; as I understand it, that _should_ get me a backtrace of what's actually doing the scribbling. [03:29] Sadly, it also means logging out of X will take in excess of 12 hours. [03:30] I doubt it. [03:30] Unless you are also running the scribbling bit inside gdb. [03:30] Depends whether your issue is localised to a single process or not. [03:31] I presume it is, but I guess that it's not guaranteed to be the case [03:32] Barring a kernel bug, though, a second process couldn't scribble over X's memory, right? [03:32] I guess it decided that poking /dev/mem or whatever it is is a fun way of communicating. [03:33] Wow. New binutils in natty is calling for more bits to be explicitly linked... At least thats what I am currently looking at in a test pulseaudio build... [03:38] RAOF, char *x = 32489716; x='Q'; [03:38] SIGSEGV? [03:39] Yeah, well, if it was that clean, we wouldn't have to worry so much about PIC and PIE :) [03:39] * persia isn't going to show something that really works here, and points at exploit documentation for those really interested [03:40] But if you can reproduce it reliably, there's a good chance that it is one process. [03:40] Yeah. It's going to be something in the X server. [03:40] Or, I guess it could be kwin doing something totally rediculous. [03:44] Could try trapping each with GDB over a multi-day period (one try each), and see if you can catch it. [04:19] i am having trouble opening a rar file [04:19] i have have 7zip installed & cant find the prog [04:19] GanonKiller: #ubuntu for support, you were helped earlier because you had a crash, but this is a general support query. [04:20] sorry [04:20] This channel is for development. [04:20] No proble,/. [04:20] problem [05:13] Is natty open for uploading? I can't find any information either way... [05:13] robert_ancell: /topic in -motu says it is [05:14] nigelb, thansk [05:15] np [05:19] robert_ancell, The formal answer to that question is always available from LP: e.g. https://launchpad.net/ubuntu/natty [05:21] persia, yeah, I've been looking at that but would it show there if it was in a freeze? [05:23] robert_ancell, "Status" was "Pre-release Freeze" about 6 hours ago. [05:23] https://launchpad.net/ubuntu/maverick may be an interesting comparison [05:24] persia, ah, thanks [06:26] Why not change this channel topic to reflect the fact that natty is open? [06:26] Just nobody did it. [06:26] persia: I am doing it now === persia changed the topic of #ubuntu-devel to: 10.10 released on 10/10/10 at 10:10:10UTC!! | Natty is open, more SRUs for Maverick | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper-maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs [06:27] Oh, heh, me too :) [06:27] :D [06:28] persia: günaydin, effendi. nasilsin? [06:30] Decidedly unurgaric :p === almaisan-away is now known as al-maisan === ivoks-afk is now known as ivoks [07:35] Good morning [07:35] that. [07:35] YokoZar: what was the bug ref # again? [07:36] pitti: 6222220 [07:36] err 622220 [07:38] RAOF, Would you have an interest in https://blueprints.launchpad.net/ubuntu/+spec/hardware-arm-n-irregular-input-device-handler ? Might be udev hinting, might be fiddling with gizmod or similar. [07:41] Hm. Looks interesting, but I've no experience with arm hardware. [07:41] From the perspective of knobs and buttons, it's not that different from anything else. [07:42] Just /dev/input/event entries. [07:42] YokoZar: uploaded [07:42] Adding "arm" is mostly intended to explain why someone should consider it critically important :) [07:42] pitti: thanks === ivoks is now known as ivoks-afk [07:54] hooray, natty thawed? [07:54] * pitti yays at the wave of "accepted" mails [07:57] Almost 9 hours ago :) [07:57] good morning! :) [07:59] dholbach: Good morning! [07:59] hey bilalakhtar === smb` is now known as smb === ara__ is now known as ara [08:54] pitti, There is a ti-omap4 proposed kernel for maverick waiting to be accepted which ogra has been winching about all along yesterday. Could you do him the favor and accept it? ;-) [08:54] right, it's been 15 hours since I processed SRU, high time :) [08:54] * pitti looks [08:55] * pitti tries to ignore the gazillion new .gitignore files [08:56] smb: hm, why does this have several new source files, like arch/arm/mach-omap2/powerdomain.c ? [08:56] or arch/powerpc/include/asm/immap_86xx.h (must be really important for omap..) [08:56] pitti, could this be a result of me doing a orig.tar.gz the first time? [08:57] ah, perhaps [08:57] sound/soc/omap/mcpdm.[hc] are also new [08:58] so, this needs some more testing then [08:58] pitti, Oh, actually they did some sound stuff [08:58] but as it is arm I have no idea what they do anyways [08:58] not in the changelog [08:59] anyway, sending builddwards [08:59] pitti, Thanks, they seemed quite keen to have it till Monday for some reason [09:00] and as it is a topic branch and this kernel is only used on some few board, regression potential is low [09:15] smb, pitti Regression potential is effectively zero, as nothing that kernel supports is currently available retail. [09:15] right, that's why I'm not too concerned about it; I just wondered about the diff [09:17] From the bug descriptions, sound/soc/omap/mcpdm.[hc] are required to make sound work at all. [09:22] pitti, that kernel change goes together with the alsa-utils upload [09:22] ah [09:22] (same bug) [09:33] doko: I have a build of newlib for ppc in a native PPA; do you want the build log over email to proof-check it? [09:57] mvo, is sw-center set to "always on top" ? (see bug 661003) [09:57] Launchpad bug 661003 in software-center (Ubuntu) "Debconf dialogs are hidden" [Undecided,New] https://launchpad.net/bugs/661003 [10:02] ogra: no, but it sounds like debconf should be [10:02] ogra: its probably focus stealing prevention [10:04] mvo, hmm, k [10:05] ogra: and yes, not cool ./ [10:06] well, minor usability glitch [10:06] would be worse if it was not shown at all :) [10:06] for some values of minor. [10:06] true that [10:06] (the not shown at all) [10:14] TheMuso: your linking question: see http://wiki.debian.org/ToolChain/DSOLinking [10:14] doko: ^- you might want to include a note about that in your mail about natty opening [10:23] lool: fine it it does build [10:23] cjwatson: yes, have to update it first [10:27] hi [10:28] can someone _please_ help us get SRUs for https://bugs.edge.launchpad.net/bzr/+bug/636930 ? [10:28] Launchpad bug 636930 in Launchpad Bazaar Integration "Upgrading a repository fails with 'Inter1and2Helper' object has no attribute 'source_repo'" [High,Triaged] === Claudinux_ is now known as Claudinux [10:45] poolie: sponsoring; will still need approval from another ubuntu-sru team member [10:45] but this will move it forward at least [10:45] thanks [10:45] I'll review it [10:45] it doesn't have to be today in particular [10:45] i just don't want it to stall forever [10:45] I'm doing SRU review every day now anyway, due to the maverick rush [10:46] pitti, how would i find out or establish a regular contact for this? [10:46] <\sh> mom is already running? [10:47] \sh: yes [10:47] poolie: hm, not sure; we should perhaps discuss on u-devel@, to find a permanent sponsor [10:47] <\sh> cjwatson: thx :) [10:48] might be better for maxb to seek per-package upload rights, if he's going to be a regular uploader [10:48] there are ubuntu devels who upload it, but nobody in the canonical platform team, and i think nobody who will regularly SRU [10:48] i'm going to work on getting per-package upload rights myself [10:49] doesn't have to be the canonical platform team [10:49] seems so far we mostly got them through Debian autosyncs? [10:50] right, which is good, i think [10:50] definitely [10:50] that works pretty well, but the main snag is SRUs [10:50] (in fact, I spy 2.3.0~beta2-1 in the pending natty sync queue) [10:50] we really want to do bugfix releases that fit well with SRUs, but i always seem to have to pester people to get them sponsored [10:50] so i think we must be doing something wrong [10:51] Which Ubuntu package inserts "%admin ALL=(ALL) ALL" to /etc/sudoers? That line is not present in Ubuntu fat chroots... [10:51] What do I need to do to be eligible for per-package upload rights? I've been getting bits and pieces sponsored here and there for a while, but never quite in sufficient volume to consider myself MOTU-eligible. [10:51] any time we find ourselves assembling a permanent sponsorship arrangement, we should probably be reaching for per-package upload instead [10:51] doko: Thanks; uploading [10:51] alkisg: the installer - specifically user-setup [10:51] Thank you cjwatson [10:51] Not, of course, that MOTU would help for bzr [10:51] maxb: https://wiki.ubuntu.com/UbuntuDevelopers#PerPackage [10:52] maxb: your sponsor needs to vouch that you have sufficient experience with the package you want to upload yourself [10:52] maxb: that's the main bit, and then some paperwork [10:52] poolie would surely be a shoe-in for bzr upload rights, and I expect maxb wouldn't have much difficulty either [10:52] (shoo-in?) [10:52] Sponsoring of SRUs has always lagged a lot: many folk don't seem to focus on that. === al-maisan is now known as almaisan-away [10:56] now should be enough subscribe ubuntu-sponsors. devs can review bug and patch. if it's acceptable, can upload [10:56] acceptable => test case exists in bug, patch is correct with policy and built fine [10:56] i know, but it basically never seems to happen without coming in here and asking several times [10:56] i know you're not lazy, so it suggests something is disconnected [10:57] poolie, I suspect it's a perception that bzr is cared for by someone, and so everyone leaves it to whoever cares for bzr. [10:57] Except, since nobody actually cares for bzr, this fails. [10:57] per-package upload rights is definitely the right fix in this case. [10:58] i don't think regular uploads are a problem, it's only or mostly SRUs [10:58] and aiui per-package uploads won't help with that? or will they [10:58] I believe they help from the date that you get per-package. [10:58] poolie: PPU works just as well for SRUs [10:59] So it may not help with maverick, but it will help with natty, ... once they release. [10:59] pitti, Does it? All the way back? [10:59] persia: it's another step in edit-acl.py, but yes [10:59] * persia was under the impression that packagesets were per-release [10:59] ok, brilliant, we should definitely do that then [10:59] persia: they are [10:59] pitti, Ah, so it *can* be done that way :) [10:59] persia: but we can edit them per-release [10:59] PPU isn't packagesets though [10:59] give me an example of somebody with PPU? [10:59] cjwatson, It isn't? [10:59] preferably LP username [11:00] cyphermox [11:00] tkamppeter? [11:00] Except we fail [11:01] till-kamppeter is the LP username [11:01] ~till-kamppeter [11:01] sorry, I should say, PPU isn't necessarily packagesets. it's perfectly possible to grant people direct upload access to a single package without creating a set for it [11:01] archive permissions can be attached to components, packagesets, or packages === diwic is now known as diwic_afk [11:02] cyphermox => ~mathieu-tl, and he has upload rights via team membership for a package set; package set access does have to be release-specific [11:02] so with PPU, maxb or I could upload to -proposed, and then someone from ~ubuntu-sru would check it, and copy to -updates? [11:02] (though we can always go back and extend things for older releases) [11:02] cjwatson, Did all of cyphermox's permissions get moved to packageset? He applied for PPU something like three times. [11:02] ~till-kamppeter has PPU access to several source packages, and that access isn't release-specific [11:02] persia: yes, I checked [11:02] Ah, OK. [11:03] poolie: right [11:03] (modulo LP bugs; not many people use per-package upload permissions for SRUs, so you may be trailblazing) [11:03] poolie, Note that this is the same procedure every Ubuntu developer needs to follow (even SRU members, who ask their peers to do the second part) [11:03] right. the SRU queue is better tended than the sponsors queue, I think, largely thanks to pitti being a hero [11:04] poolie: You missed a step, we could upload to -proposed, it would hit the queue, ~ubuntu-sru would accept it, it would need verification, and *then* it would be copied to -updates [11:05] maxb, Extra points for process knowledge ! [11:05] ok, i was oversimplifying a bit; but the big difference is that as cjwatson said it will get into a queue that's more actively polled [11:05] per https://wiki.ubuntu.com/ArchiveAdministration#Stable release updates [11:05] and a step forward in the process [11:05] so if you two will be so kind as to put this one into proposed, we'll see about getting PPU for next time [11:06] and 2.2.2 should also have clean test suites both in package build and after installation [11:07] poolie, And just to be clear, PPU is a one-time hurdle. We'll expect you to act as an Ubuntu Developer in full faith once it's granted, but you won't have to revisit the process repeatedly (except potentially iterating per-person) [11:08] sure [11:08] i have fixed a few bugs in other packages recently [11:08] well, for years, but more so recently [11:08] so, perhaps i should go for something more general afterwards [11:11] Best to apply for things as you find that folks sponsoring you do so confusedly expecting you to have done it already :) You'll likely end up with larger and larger portions of the archive over time. [11:12] * cjwatson flushes the initial natty sync queue [11:12] :) [11:12] I only had to beat sync-source.py with a stick once. Do you think Debian is frozen? [11:13] I don't understand why https://launchpad.net/ubuntu/+source/newlib/1.18.0-6ubuntu1 doesn't have any armel and amd64 build records [11:14] it did build on amd64 and armel in a non-virtual PPA [11:14] it's in Packages-arch-specific [11:14] %newlib: i386 powerpc ppc64 [11:14] doko_: there? What about the change you mailed about? [11:15] cjwatson: Oh ok; this is new then, as ithad built in maverick [11:15] does it build on other architectures in Debian? if so, the best fix would be to file a bug on buildd.debian.org about that [11:15] lool: see also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571256 [11:15] Debian bug 571256 in buildd.debian.org "buildd.debian.org: add Packages-arch-specific-version for newlib" [Normal,Open] [11:16] Yup, just found it in the Pas git log [11:16] hm, the bug appears to be "it builds but I didn't think it was useful" [11:16] maybe talk to Arthur about that? [11:16] why no explanation? [11:16] read down to the end of the bug [11:16] (that's all I know) [11:16] * lool searches for RM bug [11:17] Debian #597234 [11:17] Debian bug 597234 in ftp.debian.org "RM: newlib [ia64 amd64 hurd-i386 kfreebsd-i386 kfreebsd-amd64 sparc] -- ANAIS; excluded, see #571256" [Normal,Open] http://bugs.debian.org/597234 [11:17] not anything more [11:19] I poked the Pas bug [11:19] hence my suggestion to talk to Arthur :) [11:20] <\sh> guys, when I get such a build error like http://paste.ubuntu.com/513753/ <- what needs to be done for natty? I saw some uploads by Doko with a similar changelog entry...is there any doc on how to fix this? [11:21] someone ping me? [11:21] ari-tczew: 13:19 < cjwatson> hence my suggestion to talk to Arthur :) [11:23] cjwatson: thanks [11:24] \sh, maybe http://wiki.debian.org/ToolChain/DSOLinking ? [11:24] ari-tczew: I didn't mean you (I'd have spelled your name right :-) ); I was referring to the Debian bug above [11:25] My GTK program get the following: http://paste.ubuntu.com/513757/ during build - does someone know anything about this? [11:25] gusnan: install the libgdk-pixbuf packages [11:25] gusnan: but for such questions, go to #ubuntu-app-devel [11:25] not here [11:25] <\sh> persia: thx a lot friend :) [11:26] * persia is just an advanced backscroll filter sometimes [11:26] cjwatson: ok then :) [11:26] <\sh> persia: lol [11:26] bilalakhtar, thanks. === diwic_afk is now known as diwic [11:52] pitti, hi [11:56] hey tkamppeter, how are you? [11:57] fine, have you asked for me? [11:57] no, I didn't [11:57] tkamppeter, We were using you as an example of a per-package uploader. Sorry for the noise. [11:57] ah, right [11:57] pitti, what about bug 485383? [11:58] Launchpad bug 485383 in cups (Ubuntu) "Zebra driver not found" [Undecided,Triaged] https://launchpad.net/bugs/485383 [11:59] pitti, as you ahve all kinds of BZR repos for that, can you prepare a CUPS SRU only adding a cups-ppdc dependency to cups? [11:59] tkamppeter: feel free to push to bzr+ssh://bazaar.launchpad.net/~ubuntu-printing/cups/maverick/ [11:59] tkamppeter: (sorry, we have a deadline today, no time for Ubuntu) [12:00] pitti, for Debian? [12:00] neither, I'm afraid :) === MacSlow is now known as MacSlow|lunch [12:08] pitti, pushed it up now, rev 910. [12:18] pitti, SRU is uploaded to the queue now. === doko_ is now known as doko === amitk is now known as amitk-afk [12:31] doko: ping [12:41] mvo: would it be feasible to tweak update-manager to check for machine >= i586 and refuse to attempt the upgrade if it is noticed? [12:42] mvo: at the moment function 10.04 machines get hosed on upgrade to 10.10 once libc6 gets installed and starts generating illegal instruction traps [12:43] sladen: *gar* [12:43] sladen: sure, definitely [12:43] sladen: do you have more info what to check for in cpuinfo ? or a bug reference? [12:43] sladen: not the kind of message I was hoping for on a friday afternoon ;) [12:44] :) [12:44] mvo: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/587186 [12:44] Launchpad bug 587186 in eglibc (Ubuntu) "libc6 upgrade fails: illegal instruction" [High,Fix released] [12:44] sladen: thanks! [12:49] sladen: so it looks like checking the flags section for cmov should do the trick? [12:50] Does 10.10 run on the VIA C7M chips? I seem to remember they weren't quite i686 but had cmov. [12:50] (mind you, I'm remembering from intrepid, so I might be incorrect: C7M was the chip in early EeePCs) [12:51] persia: I don't know :) any help on this is welcome how to reliable detect it [12:51] persia: so either cpufamilty 5 -> fail or cpufamily 6+ and not cmov -> fail? [12:51] Anyone have a first-generation EeePC or similar device with C7M? [12:51] (5 or less) [12:52] mvo, I think so, but I worry about this special case that was cpufamily 5 + lots of extensions (including cmov). [12:52] That said, could be not so many folks have them, really. [12:53] mvo, if nobody volunteers with testable hardware for my corner case, I'd go ahead with the rule you described: maybe we get another bug, maybe we don't. [12:54] yeah, it will certainly help a lot of people and that worst that can happen is that people need to stay whereas currently it will break for them [12:54] so we error on the safe side [12:54] * mvo adds this code [12:55] thanks persia! [12:55] and sladen [12:55] * persia points at sladen, having mostly gotten in the way with an untestable corner case [13:03]