[02:12] <Unit193> `config channel plugins.PackageInfo.defaultRelease yakkety
[17:13] <tsimonq2> wxl: Yakkety! Do we have images yet?
[17:13] <wxl> well
[17:13] <wxl> i'm jumping the gun a bit tsimonq2
[17:14] <wxl> lp is set up
[17:14] <wxl> iso tracker is set up
[17:14] <tsimonq2> wxl: but we already have netboot images...
[17:14] <wxl> but archive isn't properly open yet
[17:14] <wxl> so once that happens, cronjobs will get turned back on
[17:14] <wxl> it's a coming
[17:14] <wxl> btw tsimonq2 did you see an email?
[17:15] <tsimonq2> Known Problems & Known Issues (Lubuntu) ?
[17:15] <wxl> nuh uh
[17:15] <tsimonq2> or lubuntu.me?
[17:15] <wxl> yep
[17:15] <Unit193> !info base-files
[17:15] <tsimonq2> I got both :D
[17:15] <wxl> Unit193: odn't ask me. i just know what release told me.
[17:15] <Unit193> wxl: What'd I ask you?
[17:15] <tsimonq2> wxl: BTW I'm already running Yakkety, so if you need me to test anything, shoot
[17:16]  * tsimonq2 uses the devel alias
[17:16] <wxl> Unit193: you didn't but it is strange that we've got yakkety things but the archive isn't properly open, i dunno
[17:16] <tsimonq2> Unit193: I got an update for that package this morning
[17:16] <wxl> tsimonq2: you have admin. use it wisely. dont' change anything about the setup  without advising with rafael first as he heavily tweaked it
[17:17] <tsimonq2> wxl: got it
[17:17] <tsimonq2> wxl: he already gave me an hour long speech when I became admin for /r/lubuntu
[17:17] <tsimonq2> :P
[17:17] <wxl> tsimonq2: he's good for that :)
[17:17] <tsimonq2> :)
[17:33] <Unit193> It'll happen when it happens...
[17:33] <tsimonq2> Unit193: in regards to?
[17:41] <tsimonq2> wxl: a bit later could you help me file an SRU for getting Julien
[17:41] <tsimonq2> *JUlien's abiword fix into Xenial?
[17:41] <tsimonq2> gosh darn enter key :P
[17:43] <tsimonq2> wxl: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure is the procedure
[17:43] <tsimonq2> wxl: 2 PM your time fine to sit down and do it?
[17:43] <wxl> i've never done one
[17:43] <wxl> so we'd have to figure it out together :)
[17:44] <wxl> but i'm booked for the workday
[17:44] <tsimonq2> alright
[17:44] <tsimonq2> should I just email you the draft and we work on it until it's done?
[17:45] <wxl> sure
[17:45] <tsimonq2> alright
[17:46] <tsimonq2> wxl: but first we need Julien to get it into Yakkety
[17:46] <tsimonq2> so I'll message him in a few hours unless you want to?
[17:46] <wxl> tsimonq2: is it going into debian?
[17:46] <tsimonq2> he just has to wait for the archive to open
[17:46] <tsimonq2> I don't think so because AFAIR it's an Ubuntu-only bug
[17:47] <wxl> ahhhh
[17:47] <wxl> k
[17:47] <wxl> then yeah have to wait for the archive
[17:47] <tsimonq2> and if he doesn't have access to upload something to the archive, then the sponsorship process...
[17:47] <tsimonq2> doesn't that take a looooooong time?
[17:47] <wxl> i'm sure he does, but i don't know ot be clear
[17:48] <tsimonq2> and even if he doesn't, it's essential to Lubuntu, right?
[17:48] <tsimonq2> so it's a higher priority I assume?
[17:48] <wxl> wellllll
[17:49] <tsimonq2> *shrug*
[17:50] <tsimonq2> I'm sure he knows *exactly* how to do this
[17:50] <wxl> probably
[17:50] <wxl> cc me in whatever communication
[17:50] <tsimonq2> alright
[17:56] <tsimonq2> wxl: you have an email
[17:56] <tsimonq2> and I;m off for now! o/
[17:57] <wxl> k bai
[20:37] <tsimonq2> wxl: "ACCOUNT PENDING: Your account is currently not active. An administrator needs to activate your account before you can login." - getting that when trying to log into lubuntu/me
[20:37] <tsimonq2> *lubuntu.me
[20:47] <tsimonq2> wxl: http://pix.toile-libre.org/upload/original/1461358036.png
[20:49] <phillw> tsimonq2: we know the message :P
[20:49] <phillw> I've pinged Rafael to approve you :)
[20:49] <tsimonq2> phillw: a man once said, "a picture is worth a thousand words" :)
[20:50] <phillw> can you approve simon onto lubuntu.me smile emoticonOh sorry.  I don't know WP well enough to be anywhere near admin!!!
[21:20] <wxl> heheheh
[21:20] <wxl> well, since tsimonq2 loves wordpress so much
[21:20]  * wxl ducks
[21:21] <phillw> I do now have a WP instance so I can learn.. with 16.04 out of the way.. I will go and have a play with it.
[21:21] <wxl> work decided to go with wordpress for their cms, which is mostly a blessing
[21:21] <wxl> the chat plugin is pretty freaking cool
[21:21] <tsimonq2> eeeew wxl
[21:23]  * tsimonq2 takes a swing at wxl XD
[21:24] <tsimonq2> \o/ Yakkety netboot ISO!
[21:24] <tsimonq2> seeing if it works
[21:25] <wxl> uh i think you're approved from what i can tell
[21:25] <tsimonq2> k trying again
[21:25] <phillw> wxl: step 6 on https://wiki.ubuntu.com/Lubuntu/Testing#Before_you_get_started is depreciated... I'd like to add in a 2nd warning about partial updates in its place. You okay with that?
[21:27] <tsimonq2> k what the hell wordpress, this is why I don't use wordpress!
[21:27] <wxl> i'm not sure it's deprecated, phillw. it's more that you can't set it on the tracker.
[21:27] <wxl> same thing tsimonq2 ?
[21:27] <tsimonq2> this loading time is worse than the wiki!
[21:27] <phillw> wxl: is it used anywhere?
[21:27] <tsimonq2> oh THERE
[21:28] <wxl> oh yueah loading is slow
[21:28] <wxl> not sure why
[21:28] <wxl> phillw: well that page is where it's used. scroll down to the table.
[21:28] <tsimonq2> k now I need to fix the links on the 16.04 post
[21:28] <tsimonq2> a couple are broken
[21:29] <phillw> wxl: chaching is not turned on on the server.. We're still on stability over speed at the moment. However, it has been freed of moin and wikimedia and is just some html and WP
[21:29] <wxl> nice
[21:30] <tsimonq2> \o/ links fixed
[21:30] <phillw> wxl: my specs are still there, but no one seems to mention them any more.
[21:31] <phillw> But, I'll leave #6 :)
[21:31] <phillw> +there
[21:31] <wxl> yeah i guess you're right
[21:31] <wxl> i moved the bit on partial upgrades up
[21:32] <phillw> Saw 1 on Fb today.... He was duly warned!!


[15:28] <tlo1337> hello and apologies if this is the wrong channel to ask, but i'm looking for guidance with an error im getting when trying to follow this guide: highlevelbitcoin.com/videos/how-to-setup-a-tor-website/ the error i get back after trying to run 'mariadb' is 'bash: mariadb: command not found' using a pinebook with ubuntu mate with php7.0 on it. not sure if that's an issue here since the guide asks for debian, but in my experience
[15:28] <tlo1337> debian and ubuntu commands are similar. idk though, im certainly not an expert!


[01:41] <JamesMR> Hi, is there an SVG of the Quetzal logo anywhere?
[01:41] <JamesMR> interweb searches have proven unsuccessful so far
[10:12] <Fudge> :D
[11:19] <BluesKaj> Hi all
[19:50] <FernandoMiguel> 2$ sudo mount -t cifs //nas/homes /mnt/NAS/homes
[19:50] <FernandoMiguel> darn CIFS
[19:50] <FernandoMiguel> not working :(
[20:45] <rye> FernandoMiguel: in quetzal specifically? Do you have cifs-utils installed?
[20:45] <FernandoMiguel> rye: let me check
[20:46] <FernandoMiguel> great
[20:46] <FernandoMiguel> now apt is locked
[20:46] <FernandoMiguel> it failed to install the latest updates :\
[20:46] <FernandoMiguel> rye:  cifs-utils:   Installed: 2:5.1-1ubuntu1
[20:47] <FernandoMiguel>  sudo rm -f /var/lib/dpkg/lock
[20:47] <FernandoMiguel> $ sudo dpkg --configure -a
[20:47] <rye> FernandoMiguel: you may want to check dmesg too
[20:48] <FernandoMiguel> [ 4970.737218] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[20:48] <FernandoMiguel> [ 4970.745213] JFS: nTxBlock = 8192, nTxLock = 65536
[20:48] <FernandoMiguel> [ 4970.761283] NTFS driver 2.1.30 [Flags: R/O MODULE].
[20:48] <FernandoMiguel> [ 4970.778022] QNX4 filesystem 0.2.3 registered.
[20:48] <FernandoMiguel> nothing I can spot there
[20:48]  * rye is not yet on quantal
[20:48] <FernandoMiguel> I already had lots of problems with CIFS on 12.04
[20:48] <FernandoMiguel> couldn't even use pass in fstab
[20:48] <rye> FernandoMiguel: actually I have to say I have none of them
[20:49] <rye> but i am not using passwords
[20:49] <FernandoMiguel> and now I can't even pass it on cli
[21:04] <FernandoMiguel> Error! Bad return status for module build on kernel: 3.4.0-2-generic (x86_64)
[21:04] <FernandoMiguel> oh I better not reboot


[07:56] <xu-help17w> Good morning.
[07:59] <xu-help17w> I'm installing Xubuntu in a lot of computers (about 50) using Clonezilla tu clone the same image to every computer and in some computers the clock is not working well. There are some computers where the time is 2 hours more than real time. I checked time clock in BIOS and there is ok. Do you have some idea about what's happening?
[08:00] <xu-help17w> BTW this is happening in computers with Xubuntu 18 and 20 version
[08:18] <well_laid_lawn> !bot
[08:19] <well_laid_lawn> !time > xu-help17w
[08:19] <well_laid_lawn> !time | xu-help17w
[08:44] <gnrp> xu-help17w: Btw, I know this is not really helpful... but clonezilla is nto really the preferred way of cloning a linux system. While it is good with windows since there the installation process is less transparent, with linux you have other good tools for an automated installation
[08:45] <gnrp> If you want, I can talk more about that, but if you are going to administrate these systems in the long run, it might be worth switching
[08:47] <xu-help17w> Well always is good to learn something so I'm open to listen your tips :D
[08:51] <xu-help17w> gnrp I forget tou mention you :/
[09:08] <gnrp> xu-help17w: Well, long time ago that I did this stuff myself. But there are scripts for automated installation like FAI and also debian has something integrated by now
[09:09] <gnrp> and for everything else, when you want to clone settings, you can use orchestration tools like puppet, ansible, etc.
[09:10] <gnrp> it is seven years ago that I worked with that, so other tools might be the hot stuff by now, but the principle stays the same. A byte-level clone of a linux system is not really necessary and can make trouble, e.g. with udev rules and MAC addresses
[09:35] <xu-help17w> I see, but this is just to automate process like install software etc if I understand it well, but not to clone a operating system so you have to deal with all the OS installation process for each of the computers
[09:36] <gnrp> you would usually combine this with a PXE boot or so
[09:36] <gnrp> so the computers boot up the appropriate image (could also be on a CD, or whatever), and the rest of the installation is completely automatic
[09:37] <gnrp> the setup we had back at the time was that on the server delivering the PXE images, we could set the computers to the PXE i mage, so if they boot, they automatically install a new system
[09:37] <gnrp> no interaction needed
[09:37] <xu-help17w> Ok, I will check that. But for now, I need to resolve the problem about the clock xD
[09:41] <gnrp> xu-help17w: What timezone are you in?
[09:45] <xu-help17w> UTC+1
[09:52] <gnrp> and could it be that on some computers the os assumes the time is set to utc, and in the other cases it assumes set to local time? Or rather that the bios times are set accordingly?
[09:52] <gnrp> I guess in utc+1 you just recently switched from utc+2 to utc+1?
[10:02] <xu-help17w> I didnt change anything. The clock update automaticly. I dont know if the clock assume set to local time or utc, even I dont know whats the difference. But if I change the time manually, after restart the computer the time goes wrong again.
[10:13] <gnrp> what does /etc/localtime point to?
[10:24] <dwadert> gnrp sorry I lost connection and I cant read what you said
[10:26] <gnrp> gnrp | what does /etc/localtime point to?
[10:28] <dwadert> I Dont know and the computers are switch of at the moment. I will check it later (computers are in shops and I dont have access to them right now)
[11:43] <jamesprada> I will take advantage and I will stay with windows7 and I will see
[11:47] <Maik> jamesprada: offtopic..... and windows 7 isn't supported anymore by the way
[13:33] <sorinello> Hello. Does somebody know if there is an issue with the lightdm gtk greeter in xubuntu 20.10 ? Or am I the only one having issues with it ?
[13:47] <gnrp> sorinello: What is your issue?
[13:49] <sorinello> gnrp, I think that there is some bad blood between lightdm-gtk-greeter and virtualbox
[13:50] <gnrp> sorinello: But what is the issue?
[14:13] <sorinello> gnrp, ok, I am running latest 20.10 Xubuntu instide a VM. After upgrading from 18.10, it seems that my greeter will not start. If I switch to another greeter, everything is fine. I am unable to assess if this is Virtualbox related or we have a bug in migration
[14:15] <sorinello> ** Message: 16:10:52.835: Starting lightdm-gtk-greeter 2.0.6 (Sep 18 2018, 01:17:10)
[14:15] <sorinello> ** Message: 16:10:52.838: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
[14:15] <sorinello> ** Message: 16:10:52.838: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
[14:15] <sorinello> libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
[14:15] <sorinello> libGL error: failed to load driver: swrast
[14:17] <xtao> hi. you're not the only one having issues
[14:18] <xtao> i've done a clean install of 20.10 on to my laptop so no upgrade cruft at all, and i find that lightdm-gtk-greeter crashes on startup 50% of the time. sometimes it works, other times it keeps throwing up errors about being out of memory (it's not) and unable to load pixmaps etc. systemd tries to restart it several times and then gives up leaving me with a black screen
[14:18] <xtao> ctrl-alt-del it and let it reboot, and it quite often then comes up and works fine and lets me login
[14:18] <xtao> didn't do this on 20.04.1
[14:19] <sorinello> xtao, hey, remember me, we discussed about this issue 2 weeks ago I think
[14:19] <xtao> yes. though that was a different issue. that was missing icons
[14:19] <xtao> i fixed the missing icon issue by doing the clean install. now the icons are working
[14:19] <xtao> but it still crashes randomly
[14:20] <sorinello> yeah ... I wonder how come we are the only 2 with this issue
[14:20] <sorinello> you're running on bare metal, I am running inside a VM
[14:20] <xtao> yes. i'd expect more people to say they have issues. especially as i see this on clean install bare metal
[14:20] <sorinello> ***MEMORY-ERROR***: lightdm-gtk-greeter[1198]: GSlice: failed to allocate 2032 bytes (alignment: 2048): Cannot allocate memory
[14:21] <sorinello> i have my VM plenty of memory, including 128M for video
[14:21] <xtao> (lightdm-gtk-greeter:1180): Pango-WARNING **: 08:52:25.710: scaled_font status is: out of memory
[14:21] <xtao> same here
[14:21] <xtao> there seems to be some serious issue with memory allocation
[14:22] <xtao> don't know what to suggest though other than finding other people who have same issue who are more in the know
[14:22] <sorinello> xtao, I had total success using another greeter instead of the default one. 0 issues with another greeter
[14:23] <xtao> i could try that. it's just odd that sometimes it works, othertimes it fails. so currently all i'm doing is rebooting it until it shows the login prompt
[14:23] <Quantos> I'm running XUbuntu 20.04 LTS x64 with XFCE4 - Everytime I start it up the DE resolution is wrong, it won't make a persistent change in settings>display
[14:24] <Quantos> Does anyone know what I should be looking at?
[14:26] <xtao> i don't personally i'm afraid. the default resolution it did on install works for me. will leave that for somebody else
[14:28] <Quantos> When it installed it had a decent resolution, didn't take up my entire second screen
[14:28] <Quantos> But when I reboot the VM the resolution is just wonkers
[14:28] <Quantos> Thanks for the reply though xtao
[14:29] <sorinello> xtao, when you get tired of this, try sudo apt-get -y install slick-greeter and remove lightdm-gtk-greeter
[14:29] <sorinello> I still don't understand how come nobody has this issue besides us :))
[14:30] <xtao> ok. thanks
[14:30] <xtao> yes. i was waiting to see if anyone else came in here asking about it. i don't know if it's just us having the issue, or if we're the only people that have upgraded to 20.10 which seems unlikely
[14:31] <sorinello> I only upgraded 2 VM's. The VMware one had the icon issue. The VirtualBox becomes unusable with the default greeter
[14:31] <Quantos> Oh, you guys must've upgraded to the Quantos variant - it's full of oddball problems  ;)
[14:31] <Quantos> Sorry, I just couldn't resist that
[14:31] <sorinello> :))
[14:32] <xtao> my icon issue went away when i did a clean install, so there must be something about the upgrade and that one
[14:36] <sorinello> xtao, check https://github.com/Xubuntu/lightdm-gtk-greeter/issues/77
[14:36] <xtao> ooooh
[14:36] <sorinello> check last comment from bluesabre
[14:37] <sorinello> I cannot understand much from the source code, but it seems we are not the only ones
[14:37] <xtao> oh that's interesting "but eventually starts after 2-3 minutes". i don't give it that long before hitting reboot :)
[14:37] <xtao> i guess systemd doesn't give up then and continues after a while
[14:38] <sorinello> lightdm-gtk-greeter:
[14:38] <sorinello>   Installed: (none)
[14:38] <sorinello>   Candidate: 2.0.6-0ubuntu1
[14:38] <xtao> so yes. we just need an update of the lightdm-gtk-greeter package then
[14:38] <sorinello> and the fix is in 2.0.7, which is not yet available in the repositories
[14:39] <sorinello> this was happening 9 days ago, I wonder what is the process of getting the updated version
[14:43] <sorinello> xtao, https://launchpad.net/lightdm-gtk-greeter I am trying to see if we can download the deb file from here, but my knowledge is very limited in how ubuntu is built and how updates are sent on channels
[14:43] <sorinello> seems that this greeter is part of Xubuntu's repo, so not part of Xfce ? I am really confused here
[14:44] <xtao> i'm not expert here. i've only used ubuntu on my laptop for the last 2 months or so. before that I was using freebsd + xfce on it
[14:47] <brainwash> sorinello: it's not part of Xfce
[14:48] <brainwash> for post-release updates see
[14:48] <brainwash> !sru
[14:50] <sorinello> thanks brainwash .. the rabbit hole deepens :))
[14:52] <sorinello> brainwash, I am able to see the package in the SRU list ... hope it will make it soom on the update channels
[14:53] <xtao> excellent
[14:54] <Maik> sorinello: not sure if this is related <seb128> could someone from the SRU team consider downgrading the recent bionic systemd out of updates back to proposed? <seb128> it's bricking user systems on derivative using some of the lightdm greeter
[14:54] <Maik> from the ubuntu-release channel
[14:55] <xtao> so claiming that it's actually a systemd issue?
[14:55] <brainwash> so, it's bug 1890394
[14:56] <Maik> xtao: ask them, i have no experience with it. I just follow that channel a bit.
[14:56] <brainwash> ohh. the github issue mentions the LP report already.
[14:57] <sorinello> brainwash, please, could you translate a bit ? so the issue was fixed by bluesabre on the greeters official github repo
[14:58] <sorinello> and then, seb128 took the fix and proposed that this new version to be pushed in our update channel ?
[14:58] <sorinello> new version of the greeter
[14:58] <brainwash> right
[14:58] <brainwash> the fix was applied to 21.04 (current dev release)
[14:58] <brainwash> and soon to 20.10
[14:59] <sorinello> aaah, I see, becvause since 20.10 is already released, the need do to some sort of backport
[14:59] <sorinello> and that backport needs to be tested/validated/approved
[14:59] <brainwash> indeed
[14:59] <brainwash> the SRU wiki article explains it
[15:00] <xtao> well if there's no other issues with the newer systemd then it makes sense to just update the greeter to the fixed version and leave systemd alone
[15:00] <xtao> but glad to see it's all in progress. will just await a fix :)
[15:00] <sorinello> systemd is ... huge
[15:01] <brainwash> the updated package is available in the -proposed repository/channel
[15:01] <brainwash> for testing
[15:01] <xtao> ah-ha. so i could add that
[15:01] <brainwash> if you want to test it and confirm that it works
[15:01] <xtao> will do
[15:01] <brainwash> it just needs to be enabled via the Software & Updates GUI
[15:01] <sorinello> interesting. I did not know that there is a proposed repository. Not that I'd know how to add that :)
[15:02] <xtao> yes. now i'm googling to find out how to add it :)
[15:02] <xtao> something in sources.list. just need to find the something.....
[15:02] <brainwash> ideally, you only want to update the lightdm-gtk-greeter package from that repository
[15:02] <brainwash> and skip all the other ones which are pending there
[15:03] <sorinello> brainwash, are you talking about pre-released updates (groovy-proposed) from the software center ?
[15:04] <brainwash> uhm yeah
[15:04] <sorinello> nice
[15:04] <brainwash> that fits the description pretty well, doesn't it? :P
[15:04] <sorinello> so if I enable this channel, and  run an apt update, I guess that all the packages from this proposed repo will be offered  for upgrade, right ?
[15:04] <xtao> probably want to do it manually using apt though, i guess software centre would do it with all packages, and we don't want that
[15:05] <sorinello> but I only need to install de greeter
[15:05] <brainwash> sudo apt install lightdm-gtk-greeter
[15:05] <sorinello> but how can you install only ONE package from a specific channel/source ?
[15:05] <sorinello> I see
[15:05] <brainwash> it should install version 2.0.6-0ubuntu2
[15:05] <sorinello> and after I install it, I disable the proposed channel, right ?
[15:06] <brainwash> notice the "2" at the end
[15:06] <brainwash> yes
[15:06] <brainwash> best to disable it afterwards
[15:06] <sorinello> brainwash, thanks. xtao, I await for your confirmation, since I am already using another greeter :)
[15:07] <xtao> trying it now
[15:08] <xtao> ok that installed
[15:08] <xtao> lightdm-gtk-greeter_2.0.6-0ubuntu2_amd64.deb
[15:08] <brainwash> good
[15:09] <xtao> ok. disabled the channel. will reboot and see what happens
[15:11] <xtao> that worked. greeter started first time
[15:11] <xtao> will see how it goes over next few days :)
[15:11] <xtao> thanks guys!
[15:11] <sorinello> xtao, donna try the fix on the VM which has the boken icons
[15:11] <sorinello> mayge they are related
[15:11] <sorinello> *broken
[15:12] <xtao> i think they could be. as with the missing icons it was also saying out of memory errors in the greeter log
[15:12] <sorinello> yeah, this is what I am thinking too
[15:13] <sorinello> rebooting the VM now
[15:18] <sorinello> xtao, icon/wallpaper issue has been fixed as well :D So it was an issue regarding the memory
[15:19] <xtao> yay
[15:38] <sorinello> thanks brainwash for all the help. I learned some new things today :)
[15:40] <brainwash> you're welcome sorinello
[15:47] <xtao> yes. thank you very much for your help there brainwash. i too have learnt some things today
[16:03] <pjstirling> hi, I seem to have enabled some kind of accessibility mode where my screen is zoomed, how do I disable that?
[16:04] <xtao> i get that if i use two finger gestures on the touchpad whilst the alt key is held down
[16:04] <pjstirling> ah, thanks, that was it
[16:04] <xtao> yes. i've done exactly that before accidently
[16:39] <Quantos> I'm having resolution issues with XFCE4 on XUbuntu 20.04
[16:39] <Quantos> When the xserver starts up I have a resolution of 1903x1000
[16:39] <Quantos> I have edited ~/.profile to include the following two lines
[16:39] <Quantos> xrandr --newmode "1360x768_60.00" 84.75 1360 1432 1568 1776 768 771 781 798 -hsync +vsync
[16:39] <Quantos> xrandr --addmode Virtual1 "1360x768_60.00"
[16:39] <Quantos> Now when the xserver starts it has the 1360x768 resolution, but after about 30 seconds it reverts to 1903x1000
[16:42] <Quantos> I'll brb, I'm just trying one more thing
[16:47] <Quantos> And no joy
[16:51] <diogenes_> Virtual1?
[16:51] <Quantos> Yes, it's a VM
[16:51] <diogenes_> eh
[16:52] <Quantos> That's how xrandr identifies the display - as Virtual1
[16:53] <diogenes_> i mean i don't consider virtual machine issues as Xubuntu issues.
[16:53] <Quantos> That's too bad for you
[16:54] <Quantos> I don't really care what you consider, not meaning to be rude, but...
[23:15] <xu-irc97w> Hello, does anyone know how to change the lock screen from xfce4-screensaver to light locker? Manjaro Xfce has this by default and I prefer it since it allows for more customisation of the lockscreen through the lightdm greeter settings
[23:46] <jamesprada> hi guys
[23:47] <jamesprada> this windows 7 runs quite nice... and my Toshiba P100 looks like Mercedes 300D


[00:10] <jpds> GunbladeIV: You still there?
[00:48] <Nafallo> wow
[00:53] <foxbuntu> Can someone tell me who an admin is for #ubuntu-server or give me a hand in there. I got someone swearing and refusing to move his chatter to -offtopic
[00:54] <blizzkid> foxbuntu: try #ubuntu-ops
[00:55] <foxbuntu> thanks
[00:55] <blizzkid> yw
[01:03] <foxbuntu> blizzkid, I can't seem to get a response from anyone
[01:03] <foxbuntu> anyone an admin?
[01:20] <jorgerosa> Hello all. Any avaiable authors for reviews, interviews, etc, etc? we need your help in www.ubuntumagazine.org (launched yesterday). Please check the "About" buttom. Thanks.
[01:24] <LjL> jorgerosa: did you actually spam that in all the channels your whois says you're in?
[01:24] <jorgerosa> LjL:  nope, im posting this only once, and thats it
[01:25] <LjL> err, yes, once in every channel you're in
[01:25] <LjL> apparently including ones which aren't even english speaking
[01:25] <jorgerosa> LjL:  that is true ;)
[01:25] <LjL> well that is not considered good practice on this network, i believe
[01:26] <jorgerosa> LjL:  im not english, other channels im joining are my home idiom
[01:26] <LjL> then you could have used your native idiom to speak in them
[01:29] <jorgerosa> LjL:  True, BUT i need authors who can understand english... see the idea?
[01:29] <LjL> i see spam
[01:29] <jorgerosa> ok
[03:47] <HardDisk> hi fellas, im chanop for #ubuntu-eg, just wanted to let you know that apparently there was word someone wanted to take over due to my inactivity, I just wanted to apologize for my absence, I was in the process of marriage and a new job meaning i now live between Egypt and the UAE.  Just to let you know Im still around and will continue support as always in a few days time.
[03:47] <HardDisk> take care.
[13:29] <niko> hi there
[13:30] <jpds> Hey niko
[17:58] <mterry> Heyo!  Can I please have a fancy ubuntu-member irc cloak?  My LP page is: https://launchpad.net/~mterry
[17:59] <erUSUL> mterry: do you have you nick correctly seted up with email and alternative nicks ? nalioth Pricey ping ^^^^^^
[17:59] <mterry> erUSUL: I have the alternate nick...  Maybe I don't have email.  Let me check instructions
[17:59] <Pricey> mterry: /msg nickserv help set email
[18:02]  * mterry is setting up email w/ nickserv
[18:03] <mterry> Pricey: OK, all set, and confirmed with nickserv
[18:04] <Pricey> mterry: all done
[18:05] <mterry> Pricey: Thanks!
[19:09] <jackjohnson> is topyli here
[19:09] <bazhang> jackjohnson, #ubuntu-ops for this
[19:33] <jester-> hi


[00:48] <pleia2> PaulW2U: nothing so far, I'll be on the lookout :)
[00:50] <pleia2> still some summaries to be written
[00:50] <pleia2> ahoneybun, jose, anyone else around to pitch in?
[00:52]  * pleia2 works on other prep in the meantime
[01:05] <pleia2> bullet-pointed Canonical news, and dropped the press article because it wasn't so impressive after what is covered in Canonical's own article on the topic
[01:06] <pleia2> so just 2 Planet posts to summarize and 3 under Blogosphere
[01:07]  * pleia2 other things for a bit
[05:51] <pleia2> wiki is being sooo slow
[05:51] <Unit193> So, the usual?
[05:51] <pleia2> heh, worse than usual
[05:51] <pleia2> I'll have a link for you soon though
[05:52] <Unit193> I'll make sure to hang around.
[05:55] <pleia2> woo error 500
[05:55] <pleia2> but it did take my change, so...
[05:55] <pleia2> Unit193: link check! https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue437
[06:02] <Unit193> Just one (unusual) FP, you're good!
[06:42] <pleia2> thanks :)
[06:42] <pleia2> sent off to editors
[06:42]  * pleia2 sleep &
[20:13] <PaulW2U> editorial review done
[20:25] <pleia2> thank you \o.
[20:25] <pleia2> \o/
[20:26] <Unit193> Still just the one (unusual) FP.


[02:17] <Zathrus> using cloud-init on CentOS 7.2 to inject a ssh key on their GenericCloud image (which has already had cloud-init run on it); I put my file in /etc/cloud/cloud.cfg.d/20-centos_sshkey.cfg. It does modify the default user's authorized_keys, but it's garbage: http://pastebin.centos.org/42526/
[02:34] <waldi> and what did you add to that config file?
[02:35] <Zathrus> #cloud-config / ssh_authorized_keys: /   - ssh-rsa [my key here]
[02:36] <waldi> please show it verbatim
[02:36] <Zathrus> sec
[02:37] <Zathrus> http://pastebin.centos.org/42596/
[02:40] <Zathrus> I've also confirmed that the authorized_keys file is empty if I do not add my file
[14:12] <smoser> Zathrus, i think that that is fixed in trunk.
[14:12] <smoser> i do recall the bug.
[14:14] <Zathrus> smoser: sigh. Thanks -- I'll have to see if I can find that bug so I can at least request it get fixed in RHEL7. Until then I'll go the ISO route.
[18:51] <cyrus_mc> http://cloudinit.readthedocs.org/en/latest/topics/examples.html#adding-a-yum-repository - how do you add multiple repositories within same .repo file
[21:42] <stanguturi> I am trying 'bzr push' and I am geting 'ssh connect to host bazaar.launchpad.net port 22: Operation timed out' errors. Any idea if the remote server is down?


[01:12] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/2296 Preparing packages
[01:14] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/2047 Merging branches
[01:38] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/2296 Successfully built
[08:40] -queuebot:#ubuntu-ci-eng- alf__, https://bileto.ubuntu.com/#/ticket/2293 Publishing packages
[08:51] -queuebot:#ubuntu-ci-eng- bzoltan, https://bileto.ubuntu.com/#/ticket/2315 Preparing packages
[08:55] -queuebot:#ubuntu-ci-eng- alf__, https://bileto.ubuntu.com/#/ticket/2293 Proposed pocket (zesty/repowerd). Release pocket (xenial/repowerd)
[09:41] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2314 Preparing packages
[09:43] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2314 zesty/unity8: Failed to merge https://code.launchpad.net/~mzanetti/unity8/appdrawer-improvements
[09:46] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2314 Preparing packages
[09:50] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 QA Signoff: Approved
[09:57] -queuebot:#ubuntu-ci-eng- bzoltan, https://bileto.ubuntu.com/#/ticket/2315 Successfully built
[09:58] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Publishing packages
[09:59] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Publish failed: Packaging diff requires ACK
[10:00] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Publishing packages
[10:02] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Publish failed: Packaging diff requires ACK
[10:02] <greyback> trainguards: can someone publish https://bileto.ubuntu.com/#/ticket/2160 please, seems I cannot approve the packaging diff myself
[10:03] <sil2100> \o/
[10:03] <sil2100> Sure
[10:03] <sil2100> Let me take a look at that
[10:06] <sil2100> greyback: hm, a small issue we might have
[10:06] <greyback> uh oh
[10:07] <sil2100> greyback: need to consult this, but generally qtmir is in main and it now has a new dep on miral, which is in universe - and this generates a binary-dependency on a universe library
[10:07] <greyback> oh feck
[10:08] <sil2100> So we might need to get miral into main now
[10:08] <sil2100> I would suppose this should be quite straightforward
[10:09] <greyback> sil2100: yep, you're right, miral will need to be in main
[10:10]  * greyback starts reading https://wiki.ubuntu.com/UbuntuMainInclusionRequirements
[10:11] <sil2100> Damn, there's no one from the MIR team around in our timezone now
[10:12] <greyback> sil2100: shall I create the MIR bug?
[10:12] <sil2100> greyback: yes, please ;) THe sooner the better, I can help driving that forward
[10:12] <greyback> sil2100: ack, on it
[10:12] <sil2100> Ah, doko should be around
[10:18] <greyback> sil2100: this ok? https://bugs.launchpad.net/ubuntu/+source/miral/+bug/1651384
[10:18] <ubot5`> Ubuntu bug 1651384 in miral (Ubuntu) "[MIR] miral" [Critical,New]
[10:22] <sil2100> greyback: I think we need to fill in all the fields in the bug, let me take care of that
[10:22] <greyback> ok, thanks
[10:23] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Successfully built
[10:35] -queuebot:#ubuntu-ci-eng- alf__, https://bileto.ubuntu.com/#/ticket/2293 Release pocket
[10:35] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2314 Successfully built
[10:43] <sil2100> greyback: ok, should be goodish now
[10:44] <sil2100> greyback: I'll poke doko about it - please check for his input there and reply if needed
[10:45] <greyback> sil2100: will do, thanks
[10:49] <sil2100> greyback: if doko won't have time today we'll have to wait for mterry
[10:49] <greyback> sil2100: yep, it is that time of year ;)
[10:50] <greyback> thanks for poking
[12:09] <jgdx> robru, sorry?
[12:11] <robru> jgdx: what is https://bileto.ubuntu.com/#/ticket/2312 about?
[12:15] <robru> Looks real strange to me
[12:16] <jgdx> robru, we're patching libgnome-desktop-dev-3 so that it uses XKB_CONFIG_ROOT and XDG_DATA_DIRS, but for x+o only
[12:16] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2288 Preparing packages
[12:16] <jgdx> zesty will come later, though
[12:17] <robru> jgdx: i don't understand why you'd want that in the overlay and not as an SRU. That can't possibly be on the phone, can it?
[12:19] <jgdx> robru, u8 snap session is built off of x+o, not sure what we gain from an sru
[12:19] <jgdx> but when seb acks the patches, it'll be uploaded to zesty
[12:21] <robru> jgdx: ah ok, just very surprising to me to see something called "gnome desktop" being used somewhere other than gnome desktop :-)
[12:21] <robru> SRU would put your patch in the hands of actual gnome desktop users
[12:24] <jgdx> robru, okay, I've filed a bug in gnome though, see bug 1644268
[12:24] <ubot5`> bug 1644268 in gnome-desktop (Ubuntu) "GnomeDesktop-WARNING **: Failed to load XKB rules file" [High,In progress] https://launchpad.net/bugs/1644268
[12:25] <jgdx> also, not sure if they are running systems where usr/share isn't at / :)
[12:26] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Preparing packages
[12:32] <robru> jgdx: ah, so it only affects snaps, that makes more sense, thanks.
[12:33] <jgdx> I'm going to make the description a bit more descriptive
[13:06] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Failed to build (zesty/telephony-service). Successfully built (xenial/dialer-app, xenial/telephony-service, zesty/dialer-app)
[13:11] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2288 Currently building (xenial/ubuntu-system-settings). Failed to build (zesty/ubuntu-system-settings). Successfully built (xenial/ubuntu-settings-components, zesty/ubuntu-settings-components)
[13:26] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2288 Preparing packages
[14:05] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Needs rebuild due to new commits (zesty/telephony-service). Successfully built (xenial/dialer-app, xenial/telephony-service, zesty/dialer-app)
[14:19] <sil2100> cjwatson: hmmm, sorry to disturb! We have two Bileto landings that introduce new source packages - do we need preNEW reviews of those or should I just publish and let them be reviewed in the NEW queue instead?
[14:20] <sil2100> cjwatson: IIRC Bileto only bypasses the binNEW queue, not the source one
[14:20] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2312 Abandoning ticket
[14:31] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2288 Pending binary packages (xenial/ubuntu-system-settings). Successfully built (xenial/ubuntu-settings-components, xenial/ubuntu-system-settings-online-accounts, zesty/ubuntu-settings-components, zesty/ubuntu-system-settings, zesty/ubuntu-system-settings-online-accounts)
[14:34] <cjwatson> sil2100: I think it's fine to just publish them
[14:35] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2314 Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/unity8)
[14:51] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2288 Successfully built
[15:04] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Preparing packages
[15:07] <dobey> Saviq, mzanetti: so is it ok to go ahead and land https://code.launchpad.net/~dobey/unity8/drop-payments/+merge/312500 as it seems there aren't any "landing" silos for unity8 at the moment, and they're all testing silos. i'd like to get this landed before EOY
[15:07] <Saviq> dobey, https://bileto.ubuntu.com/#/ticket/2160 is landing now
[15:07] <dobey> oh
[15:08] <Saviq> ah it just got ACKed
[15:08] <dobey> don't know why i didn't see that one
[15:08] <Saviq> mterry, can you publish ↑ please
[15:09] <mterry> k
[15:11] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Publishing packages
[15:17] <mterry> Saviq: ^
[15:19] <Saviq> mterry, thanks!
[15:21] <Saviq> dobey, to answer your question, I'll get a silo going later today or tomorrow morning, hopefully under QA in the evening
[15:22] <dobey> Saviq: ok, thanks. hopefully with that some more stuff we don't need will end up dropping out of the u8 snap build
[15:22] <Saviq> mterry, I'd like to include your installed-qmltest in ↑, but you'd need to rebase on lp:~ci-train-bot/unity8/unity8-ubuntu-zesty-2160
[15:24] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2302 Destination version missing from changelog (zesty/unity8). Needs rebuild due to new commits (zesty/unity-scopes-shell). Successfully built (xenial/unity-scopes-shell, xenial/unity8)
[15:28] <mterry> Saviq: got it
[15:30] <mterry> Saviq, dobey: dednick and I had been treating silo 2291 as a the next landing silo, if you need a place
[15:31] <Saviq> mterry, ack
[15:34] -queuebot:#ubuntu-ci-eng- dednick mterry, https://bileto.ubuntu.com/#/ticket/2291 Destination version missing from changelog (zesty/unity-api, zesty/unity8). Successfully built (xenial/qmenumodel, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/unity-api, xenial/unity8, xenial/unity8-desktop-session, zesty/qmenumodel, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/unity8-desktop-session)
[15:35] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2272 Destination version missing from changelog (zesty/qtmir, zesty/unity-api, zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, xenial/unity8, zesty/qtmir-gles)
[15:36] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Destination version missing from changelog (zesty/qtmir, zesty/unity-api, zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, xenial/unity8, zesty/qtmir-gles)
[15:36] <dobey> hmm
[15:43] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Proposed pocket (zesty/qtmir, zesty/qtmir-gles, zesty/unity-api, zesty/unity8). Release pocket (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, xenial/unity8)
[15:45] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Failed to build (xenial/telephony-service, zesty/telephony-service). Successfully built (xenial/dialer-app, zesty/dialer-app)
[15:54] -queuebot:#ubuntu-ci-eng- dednick mterry, https://bileto.ubuntu.com/#/ticket/2291 Destination version missing from changelog (zesty/unity-api). Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/qmenumodel, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/unity-api, xenial/unity8, xenial/unity8-desktop-session, zesty/qmenumodel, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/unity8-desktop-session)
[15:58] -queuebot:#ubuntu-ci-eng- alan_g, https://bileto.ubuntu.com/#/ticket/2317 Preparing packages
[16:19] -queuebot:#ubuntu-ci-eng- alan_g, https://bileto.ubuntu.com/#/ticket/2317 Successfully built
[16:38] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Preparing packages
[16:38] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 zesty/telephony-service: Failed to branch https://code.launchpad.net/~boiko/telephony-service/voip_support
[16:42] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2254 Preparing packages
[16:43] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Proposed pocket (zesty/qtmir, zesty/qtmir-gles, zesty/unity8).  You must supply either a Commit Message on your MP, or a custom debian/changelog entry
[16:46] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2289 QA Signoff: Approved
[16:47] <davmor2> Elleo: ^ please don't forget to rebuild 2300 once this has landed thanks
[16:47] <Elleo> davmor2: will do, thanks :)
[16:55] -queuebot:#ubuntu-ci-eng- Trevinho, https://bileto.ubuntu.com/#/ticket/2254 Ready to build
[16:57] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2289 Publishing packages
[17:06] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Failed to build (xenial/telephony-service). Needs rebuild due to new commits (zesty/telephony-service). Successfully built (xenial/dialer-app, zesty/dialer-app)
[17:11] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2289 Proposed pocket (zesty/ubuntu-keyboard, zesty/ubuntu-system-settings). Release pocket (xenial/ubuntu-keyboard, xenial/ubuntu-system-settings)
[17:12] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2288 Destination version missing from changelog (zesty/ubuntu-system-settings). Successfully built (xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, xenial/ubuntu-system-settings-online-accounts, zesty/ubuntu-settings-components, zesty/ubuntu-system-settings-online-accounts)
[17:12] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2248 QA Signoff:
[17:12] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2248 Destination version missing from changelog (zesty/ubuntu-keyboard). Successfully built (xenial/ubuntu-keyboard)
[17:16] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Destination version missing from changelog (zesty/unity-api). Needs rebuild due to new commits (zesty/qtmir, zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, xenial/unity8, zesty/qtmir-gles)
[17:21] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Preparing packages
[17:23] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2300 Destination version missing from changelog (zesty/ubuntu-keyboard). Successfully built (xenial/ubuntu-keyboard)
[17:29] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2295 QA Signoff: Approved
[18:15] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Destination version missing from changelog (zesty/qtmir, zesty/unity-api). Pending binary packages (zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, zesty/qtmir-gles). Uploading build (xenial/unity8)
[18:21] <robru> mzanetti: Saviq: can we do a hangout at some point?
[18:35] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Destination version missing from changelog (zesty/qtmir). Needs rebuild due to new commits (zesty/unity-api, zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, xenial/unity8, zesty/qtmir-gles)
[18:43] -queuebot:#ubuntu-ci-eng- Laney, https://bileto.ubuntu.com/#/ticket/2262 Diff missing (zesty/double-conversion). Needs rebuild due to higher version at destination (zesty/gyoto). Ready to build (zesty/qtdeclarative-opensource-src-gles). Release pocket (zesty/qtdeclarative-opensource-src)
[18:43] -queuebot:#ubuntu-ci-eng- Cimi, https://bileto.ubuntu.com/#/ticket/2302 Needs rebuild due to higher version at destination (xenial/unity8, zesty/unity8). Needs rebuild due to new commits (zesty/unity-scopes-shell). Successfully built (xenial/unity-scopes-shell)
[18:45] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/2024 Needs rebuild due to higher version at destination (xenial/unity8). Ready to build (zesty/unity8)
[18:49] -queuebot:#ubuntu-ci-eng- bschaefer, https://bileto.ubuntu.com/#/ticket/2209 Needs rebuild due to higher version at destination
[18:49] -queuebot:#ubuntu-ci-eng- Mirv tsimonq2 mitya57, https://bileto.ubuntu.com/#/ticket/1985 Failed to build (zesty/akonadi, zesty/maliit-framework, zesty/qtcurve). Needs rebuild due to higher version at destination (zesty/gcin, zesty/lxqt-qtplugin, zesty/qtmir-gles, zesty/qttools-opensource-src, zesty/qtubuntu, zesty/webbrowser-app). Needs rebuild due to new commits (zesty/qtmir, zesty/unity8). Ready to build (zesty/qtbase-opensource-src-gles, zesty/qtdeclarative-opensour
[18:49] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2248 Needs rebuild due to higher version at destination
[18:51] <robru> Wow, amazing how many tickets had that problem
[18:54] -queuebot:#ubuntu-ci-eng- artmello, https://bileto.ubuntu.com/#/ticket/2053 Needs rebuild due to higher version at destination (xenial/gallery-app). Ready to build (zesty/gallery-app)
[18:54] -queuebot:#ubuntu-ci-eng- dednick mterry, https://bileto.ubuntu.com/#/ticket/2291 Needs rebuild due to higher version at destination (xenial/unity-api, zesty/unity-api). Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/qmenumodel, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/unity8, xenial/unity8-desktop-session, zesty/qmenumodel, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/unity8-desktop-session)
[18:54] -queuebot:#ubuntu-ci-eng- josharenson, https://bileto.ubuntu.com/#/ticket/2031 Needs rebuild due to higher version at destination (xenial/unity8). Needs rebuild due to new commits (zesty/unity8)
[18:54] -queuebot:#ubuntu-ci-eng- andyrock, https://bileto.ubuntu.com/#/ticket/2112 Needs rebuild due to higher version at destination (xenial/unity-api, xenial/unity8). Needs rebuild due to new commits (zesty/unity-api, zesty/unity8)
[18:54] -queuebot:#ubuntu-ci-eng- oSoMoN Kaleo, https://bileto.ubuntu.com/#/ticket/1873 Needs rebuild due to higher version at destination (xenial/webbrowser-app). Ready to build (zesty/webbrowser-app)
[18:55] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2272 Destination version missing from changelog (zesty/unity-api, zesty/unity8). Needs rebuild due to higher version at destination (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir, zesty/qtmir-gles). Successfully built (xenial/unity-api, xenial/unity8)
[18:57] -queuebot:#ubuntu-ci-eng- Mirv, https://bileto.ubuntu.com/#/ticket/2055 Failed to build (zesty/qtdeclarative-opensource-src). Needs rebuild due to higher version at destination (xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-system-settings-online-accounts, xenial/ubuntu-ui-toolkit, xenial/ubuntu-ui-toolkit-gles, xenial/unity8, xenial/webbrowser-app). Ready to build (zesty/qtdeclarative-opensource-src-gles, zesty/qtmir, zesty/qtmi
[18:59] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2275 Needs rebuild due to higher version at destination (xenial/indicator-network). Successfully built (xenial/hud, xenial/indicator-display, xenial/indicator-sound, xenial/indicator-transfer, xenial/keeper, xenial/libqtdbusmock, xenial/libqtdbustest, xenial/mediascanner2, xenial/pay-service, xenial/persistent-cache-cpp, xenial/policykit-unity8, xenial/thumbnailer, xenial/ubuntu-app-launch, xenial
[19:01] -queuebot:#ubuntu-ci-eng- mterry, https://bileto.ubuntu.com/#/ticket/1679 Needs rebuild due to higher version at destination (xenial/gsettings-ubuntu-touch-schemas, xenial/ubuntu-touch-session, xenial/unity8, xenial/unity8-desktop-session). Needs rebuild due to new commits (zesty/gsettings-ubuntu-touch-schemas, zesty/lightdm, zesty/ubuntu-touch-session, zesty/unity8, zesty/unity8-desktop-session). Successfully built (xenial/lightdm)
[19:02] -queuebot:#ubuntu-ci-eng- jgdx, https://bileto.ubuntu.com/#/ticket/2140 Needs rebuild due to higher version at destination (xenial/qtmir, xenial/qtmir-gles, xenial/ubuntu-system-settings, zesty/qtmir-gles). Needs rebuild due to new commits (zesty/qtmir, zesty/ubuntu-system-settings)
[19:04] -queuebot:#ubuntu-ci-eng- greyback dandrader, https://bileto.ubuntu.com/#/ticket/2160 Proposed pocket (zesty/qtmir, zesty/qtmir-gles). Release pocket (xenial/qtmir, xenial/qtmir-gles, xenial/unity-api, xenial/unity8, zesty/unity-api, zesty/unity8)
[19:11] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2289 Proposed pocket (zesty/ubuntu-system-settings). Release pocket (xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, zesty/ubuntu-keyboard)
[19:12] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2111 QA Signoff:
[19:13] -queuebot:#ubuntu-ci-eng- oSoMoN, https://bileto.ubuntu.com/#/ticket/2111 Needs rebuild due to higher version at destination
[19:27] <dobey> robru: any chance to change the "Debs" editable to be a multi-line text entry instead of one really long line of text in a really tiny rectangle?
[19:28] <robru> dobey: could do. File a bug please
[19:28] <dobey> ok
[19:36] <robru> wow, 17 tickets failed the new 'higher version at destination' check. I'm amazed more people weren't clamoring to get that fixed
[19:42] <dobey> robru: is it not the same as "Missing changelog" or whatever the error was?
[19:44] <dobey> robru: https://bugs.launchpad.net/bileto/+bug/1651567
[19:44] <ubot5`> Ubuntu bug 1651567 in Bileto "Editable field for "Debs" is too small" [Undecided,New]
[19:52] <robru> dobey: no, as evidenced by the fact that i rolled out a new check and 17 tickets triggered it
[19:52] <robru> dobey: this one just checks that the version in the ppa is actually higher than destination archive
[19:53] <robru> dobey: thanks for the bug, will try to squeeze that in this afternoon
[19:53] <dobey> oh i thought i saw a couple that i saw earlier
[20:17] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Preparing packages
[20:35] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Currently building (xenial/qtmir, xenial/unity8, zesty/qtmir, zesty/unity8). Failed to build (xenial/unity-api, zesty/unity-api). Pending binary packages (xenial/qtmir-gles). Successfully built (zesty/qtmir-gles)
[20:55] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2313 Destination version missing from changelog (zesty/qtmir). Failed to build (xenial/unity-api, xenial/unity8, zesty/unity-api, zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles)
[21:02] <robru> dobey: a ha, here's an example: https://bileto.ubuntu.com/#/ticket/2275#audit_log of one that was 'Successfully built' and lander approved, where the version was higher at dest. it's because the changelog check only applies to MPs (eg, the primary series) while the version check applies to all packages in all series. but you're right that there's a lot of
[21:02] <robru> overlap generally
[21:07] <dobey> robru: that one is weird because the MP was landed in another silo, but the built package still exists in this one, and it's a pain to "fix" that because either have to find a trainguard to delete that package from the PPA, or just abandon and then rebuild everything (which is kind of crappy on large PPAs like that one)
[21:08] <dobey> robru: on the other hand, since you're here, mind deleting indicator-network from 2275 PPA? :)
[21:08] <robru> dobey: yeah no problem :-P
[21:14] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2275 Generating diffs
[21:16] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2275 zesty/thumbnailer: Failed to download DSC file https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2275/+files/thumbnailer_2.4+17.04.20161219-0ubuntu1.dsc
[21:28] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2275 Generating diffs
[21:37] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2275 Successfully built


[01:14] <nacc> infinity: also, i'm realizing (and it may not really matter, since it's zesty only), but the rebuilt ruby-rmagick migrated through, and won't work. I guess that's what you were asying earlier? I think the above debdiff, corrected a bit more, would hvae held it in -proposed until imagemagick also was able to migrate?
[01:19] <Bluefoxicy> I don't know if Ubuntu maintains the official Ubuntu Docker image, but we're having this spirited discussion on the Debian one:  https://github.com/tianon/docker-brew-debian/issues/56#issuecomment-264342985
[01:21] <tianon> yes, the Ubuntu official Docker image is produced and maintained in collaboration with Canonical ;)
[01:21] <sarnold> Bluefoxicy: https://wiki.ubuntu.com/YakketyYak/ReleaseNotes#GCC
[01:22] <Bluefoxicy> sarnold:  wow, that's bold.  We were discussing -fstack-protector-strong largely.
[01:23] <sarnold> Bluefoxicy: debian did much the same, https://launchpad.net/debian/+source/gcc-6/+changelog see 6.2.0-7
[01:23] <sarnold> Bluefoxicy: oh cool
[01:24] <Bluefoxicy> My observation is mainly that lots of official images (nginx, java, apache, anything based on java e.g. tomcat, php, ...) are based on debian:jessie, and publishes upstream releases by compilation mainly with autoconf.  End result is a lot of off-hand compilation without stack protection.
[01:24] <sarnold> indeed
[01:24] <sarnold> that kind of thing is why we changed our gcc dfeaults rather than just dpkg-builflags mechanisms. so much software build outside of our archive...
[01:24] <Bluefoxicy> so the options are A) tell every single upstream to add CFLAGS= to their downstream Dockerfile; B) add the appropriate flags to the upstream image; or C) modify the compiler.
[01:24] <Bluefoxicy> nod
[01:25] <Bluefoxicy> modifying the compiler environment catches anything with autoconf, but nothing without it
[01:25] <Bluefoxicy> I'm uncomfortable modifying the compiler in drastic ways
[01:25] <Bluefoxicy> although in DEbian/Ubuntu that's no big deal
[01:25] <sarnold> well, it wasn't without detractors :)
[01:26] <Bluefoxicy> in GCC upstream, you get oddness like muslc not providing certain facilities, and then you compile stuff with -D_FORTIFY_SOURCE=2 and things magically break
[01:26] <sarnold> kernel git bisect got more difficult.. sigh.
[01:26] <Bluefoxicy> and then all of alpine-linux developers are pissed
[01:27] <Bluefoxicy> sarnold:  -Wl,-O1 -Wl,--hash-style=both btw ;)
[01:27] <Bluefoxicy> not sure if that's default now?
[01:27] <sarnold> no idea..
[01:27] <Bluefoxicy> https://lwn.net/Articles/192624/
[01:29] <Bluefoxicy> -Bdirect never went anywhere; the other three are sane
[01:30] <Bluefoxicy> ... hash style defaults to "sysv", linker optimization defaults to -O0
[01:34] <sarnold> Bluefoxicy: there's so many interesting things in the world. nice comments ten years ago btw :)
[01:34] <Bluefoxicy> although it looks like at least /bin/ls has dynsym, dynstr, and gnu hash
[01:34] <Bluefoxicy> so obviously the Ubuntu build servers are doing the right thing
[01:34] <Bluefoxicy> sarnold:  I was a bit brighter ten years ago
[01:34] <sarnold> Bluefoxicy: doko takes pride in having the fastest userspace builds around :D
[01:34] <sarnold> Bluefoxicy: hehe
[01:35] <Bluefoxicy> sarnold:  still embarrassed by Firefox taking like 47 seconds to load while Firefox built on anything else took 6 seconds to start back in Warty?
[01:35] <Bluefoxicy> the world's come a long way in ten years
[01:36] <Bluefoxicy> how did we ever get from one distribution loading a Web browser extremely-slowly being front-page news for months to a world where half the Internet is down because Dyn is under attack by twelve-year-olds?
[01:37] <sarnold> I'm more surprised that 25 years ago I still had fun on computers that weren't connected to any other computers :)
[01:38] <Bluefoxicy> apt-get install super-methane-brothers ?
[01:39] <sarnold> worse, even qbasic gorillas.bas  was fun
[01:46] <Bluefoxicy> gorillas nothing, what I need is cats
[01:47]  * Bluefoxicy grumbles at mouse
[06:03] <infinity> nacc: debian/ruby-rmagick/DEBIAN/shlibs won't work because that's for documenting shlibs of libraries that ruby-rmagick ships.
[06:05] <infinity> nacc: I'd probably also strip the "-6.Q16" off the end of your regex to avoid having to fiddle with that too much with every libmagickcore bump.  If you really think ruby-rmagick could end up linked to two different libmagickcore libraries, there are bigger issues afoot.
[06:06] <infinity> nacc: Otherwise, looks reasonable enough to me.  If there's a way to divine "RMagick2.so" from other files in debian/ to avoid specifying it in rules (I dunno, a gross grep of debian/foo.install or something) that might be "nice", but also pretty sure that doesn't change often enough for it to be a big deal.
[06:07] <nacc> infinity: ah! ok, that makes more sense, i must have misunderstood that part of the manpage
[06:07] <nacc> infinity: ack on the regex
[06:07] <nacc> infinity: thanks for taking a look!
[07:28] <pitti> Good morning
[10:51] <Laney> doko: Can you help with insighttoolkit4/ppc64el please? You enabled the build for all arches a while ago, and now it gets ENOSPC on ppc64el
[10:51] <Laney> (the build log on launchpad isn't helpful)
[10:52] <doko> Laney: how should I help? filing a bug against the buildds that they run out of disk space, or massage the build to take less disk space, maybe not building with -g?
[10:54] <doko> https://bugs.launchpad.net/ubuntu/+source/insighttoolkit4/+bug/1595485 ask for the removal
[10:54] <Laney> doko: The latter, see #launchapd-ops
[10:55] <Laney> it failed when installing the package at the end so maybe not that much more is needed
[10:55] <Laney> or if you want to rip it all out, that's fine by me
[10:55] <Laney> there's a lot of rdeps and untangling all of that doesn't seem like much fun :-)
[11:02] <doko> debian buildds don't like it either ... even on x86 archs: https://buildd.debian.org/status/package.php?p=insighttoolkit4
[11:03] <Laney> looks like its in progress?
[11:03] <Laney> probably going to build everywhere else in zesty at least
[11:03] <doko> no, apparently manually uploaded
[11:04] <doko> Laney: I would try with -g -O2 first /using STRIP/APPEND options
[11:05] <Laney> doko: Just strip O3 and append O2?
[11:05] <Laney> there's already a commented out block for that in rules
[11:06] <Laney> from you ;-)
[11:06] <Laney> ok, I'll try it
[11:06] <Laney> 22 hour build time is not fun
[11:10] <Laney> doko: https://paste.ubuntu.com/23567354/ ok?
[11:10] <doko> maybe I should turn on compressed debug info by default ... but I'm not sure what else that would break ...
[11:11] <doko> sure, looks fine
[11:11] <Laney> O2 makes smaller binaries?
[11:12] <doko> it should with inlining off.
[11:14] <Laney> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2253/+build/11289814
[11:21] <jgdx> seb128, hey, how's that unity8 situation? Closer to being resolved?
[11:33] <Laney> doko: trying a build with -gz -feliminate-dwarf2-dups on ppc64el too
[11:33] <Laney> man gcc -> search "compress"
[11:35] <Laney> I don't need to set anything in LDFLAGS as well do I?
[11:37] <doko> it should, --compress-debug-sections=...
[11:38] <Laney> you need both?
[11:38] <Laney> I thought -gz would make them compressed in the first place
[11:39] <Laney> ah well, let's see
[11:39] <Laney> all good fun
[11:40] <doko> Laney: -gz needs to be passed to the linker too, the driver translates that to --compress-debug-sections=zlib for ld
[11:41] <Laney> ah
[11:46] <doko> hmm, I think that needs a test rebuild, and then be turned on when we open z+1 ...
[12:28] <Saviq> pitti, hey, re: resolved, I rely on "additional search domains" at home, my dhcp is sending them and they always ended up in resolvconf; I've had trouble with that since upgrading to zesty, and having installed NM from proposed now it doesn't work still - configuring them in the connection editor doesn't seem to work either, any idea how this should work? should the domains end up in resolv.conf?
[12:31] <Saviq> resolved only responds to FQDN, and that's correct, AFAIK - and `ping foo` works, but `ping bar.baz` (bar.baz.search.domain being the FQDN) does not
[12:50] <pitti> Saviq: no, they can't end up in resolv.conf -- it has a too limited syntax for that
[12:50] <pitti> Saviq: you should see them in "systemd-resolved --status"
[12:50] <pitti> Saviq: /etc/resolve.conf should only have <IP_ADDRESS>, unless you have another resolvconf client installed (like unbound or whatnot)
[12:51] <Saviq> pitti, ok I see them there, still, resolved doesn't seem to respect them?
[12:52] <pitti> Saviq: hm, mind filing a bug
[12:52] <Saviq> pitti, will do
[12:52] <seb128> jgdx, it was resolved yesterday no?
[12:52] <pitti> Saviq: oh, sorry, I misread "additional search domains" as "domain-limited DNS servers" somehow
[12:52] <pitti> Saviq: just curious that this didn't work with NetworkManager/dnsmasq either
[12:53] <Saviq> pitti, it worked before zesty - after upgrading my setup was a bit wonky (bug #1637700)
[12:54] <Saviq> this might've been a IPv6 issue now I think about it (have disabled v6 for now due to other issues)
[12:55] <jgdx> seb128, okay, great! thanks
[12:56] <seb128> jgdx, yw! do you still have issues or did you just ask out of curiosity?
[12:56] <Saviq> jgdx, seb128, we've a problem with oxide now
[12:56] <Saviq> on xenial+overlay
[12:56] <jgdx> seb128, my silo's just not getting published
[12:56] <Saviq> a new oxide was released into xenial-security, newer than the one in overlay
[12:57] <seb128> jgdx, k, I don't know what the specific issue is but unity8 migrated yesterday
[12:57] <Saviq> so qml-module-ubuntu-web is uninstallable
[12:57] <seb128> oh
[12:57] <Saviq> https://bileto.ubuntu.com/#/ticket/2148
[12:57] <seb128> what Saviq said then
[12:57] <Saviq> this fixes it, but will take a day still to land
[12:57] <Saviq> jgdx, which silo, btw?
[12:57] <jgdx> Saviq, this is holding up silo 2194?
[12:57] <jgdx> ^
[12:58] <pitti> Saviq: bug 1592721 landed late in yakkety, and IIRC that correlated with several bug reports
[12:58] <pitti> Saviq: which at least sounds related to your pre-resolved observations
[12:58] <pitti> could still be that it doesn't send these to resolved either
[12:58] <pitti> ah no, you said that you do see them in --status
[12:59] <Saviq> pitti, bug #1636375 sounds even more related
[13:00] <Saviq> kinda
[13:00] <pitti> Saviq: ah, is it that one? i. e. unqualified names are expanded, but not qualified prefixes?
[13:01] <Saviq> pitti, to some extent, yes - but I only have resolved in resolv.conf
[13:01] <pitti> well, that's fine -- and for the most part, /etc/resolv.conf is entirely irrelevant these days
[13:01] <pitti> (except for chromium)
[13:01] <pitti> or if you stop resolved
[13:02] <Saviq> sure, I just mean that stopping resolved won't help here (or will it? /me tries)
[13:02] <pitti> ah no, it won't
[13:05] <Saviq> pitti, yeah, I'd have to add the nameserver and search bits into resolvconf manually, but I suppose the real issue is the same as the bug says
[13:05] <pitti> Saviq: so can you resolve unqualified names with search expansion?
[13:05] <pitti> i. e. "foo",  not "foo.bar"
[13:05] <Saviq> pitti, correct
[13:05] <pitti> and it would try "foo.baz" if you have "search baz"
[13:05] <pitti> Saviq: ah good, then it's that bug too
[13:07] <Saviq> I have "bar.name" and "name" as search domains, foo resolves, as does foo.bar.name, but not foo.bar
[13:11] <Saviq> pitti, https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636375/comments/5 - let me know if you need more details please
[13:12] <Saviq> make that https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1636375/comments/6
[13:12] <pitti> Saviq: ack, thanks; a bit confusing to mix sawicz.net and foo.name in that way, but I know what you mean
[13:12] <Saviq> pitti, sorry, fixed the comment now
[13:12] <Saviq> or not
[13:12] <pitti> *nod*
[13:12] <Saviq> one more try
[13:12] <pitti> well, close enough :)
[13:45] <mdeslaur> doko: I'm stealing your nss merge
[13:45] <doko> Laney: did you start that insighttoolkit4 build with -gz in both CXXFLAGS and LDFLAGS?
[13:45] <doko> mdeslaur: it's your's anyway ;p
[14:28] <dobey> doko: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1646064/comments/1
[15:11] <Laney> doko: gcc -gz gives an error
[15:11] <Laney> -Wl,--something seemed to work
[15:24] <LocutusOfBorg> [16:17:26] <LocutusOfBorg> hi, is anybody there console-setup savvy?
[15:25] <LocutusOfBorg> [16:17:44] <LocutusOfBorg> wrt launchpad bug lp: #1443853
[15:25] <LocutusOfBorg> [16:17:46] <ubot5> Launchpad bug 1443853 in kbd (Ubuntu) "Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display" [Undecided,Confirmed] https://launchpad.net/bugs/1443853
[15:25] <LocutusOfBorg> [16:17:54] <LocutusOfBorg> the fix might be simple
[15:25] <LocutusOfBorg> forwarding from -release ^^ maybe better to talk here
[15:38] <doko> Laney: ok, -gz works in gcc-7, will need to find out why not in 6 ...
[15:44] <doko> ok, needs a back port
[15:45] <Laney> looked like it was something set up at build time
[15:48] <doko> found it, both gcc-5 and gcc-6 are missing the backports
[15:49] <Laney> hope it still makes a difference with just the linker option
[15:50] <doko> sure, it das. checked with the bash binary
[15:51] <Laney> :)
[15:51] <doko> $ ls -l *essed
[15:51] <doko> -rwxrwxr-x 1 doko doko 2464104 Dez  2 16:25 bash-compressed
[15:51] <doko> -rwxrwxr-x 1 doko doko 4691648 Dez  2 15:52 bash-uncompressed
[15:51] <doko> unstripped binaries
[15:52] <Laney> with -Wl,--compress-debug-section=soemthing?
[15:53] <Laney> nod, that's what I tried too (on a hello world), made some difference
[15:54] <doko> no, built a binutils defaulting to compressed debug sections
[15:55] <Laney> k
[15:57] <doko> https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc/+sourcepub/7209526/+listing-archive-extra (still building there)
[16:46] <nacc> infinity: in the shlibs.local file, I have to specify the SOVERSION (aiui) -- is it appropriate for me to just extract that from the library version? Since I am using that specific library to determine which package provides it?
[16:48] <infinity> nacc: Well, if you insist on specifying it as shlibs.  I'd just inject the dep directly, if I were you.
[16:49] <nacc> infinity: ack, that is probably much easier :)
[16:49] <infinity> nacc: So, move that mess from override_dh_shlibdeps to override_dh_gencontrol, and inject the dep there.
[16:50] <nacc> infinity: yep, thanks!
[16:50] <infinity> nacc: dpkg-gencontrol is smart enough to reduce "foo (>= 1.0), foo (>= 2.0)" to just "foo (>= 2.0)", so shlibdeps will give you the "right" one, and you'll inject the new one, and it'll sort it out.
[16:51] <nacc> infinity: ah that was what I was going to test, great!
[16:52] <infinity> nacc: But to answer your question more directly, yes doing what you suggested would be appropriate. :)
[16:53] <infinity> nacc: (Just less code to do it the dep/control way instead of the shlibs way)
[16:53] <infinity> Less code, more readable, and probably more obvious to the next passer-by how it works.
[16:54] <nacc> infinity: agreed! :)
[16:55] <infinity> nacc: So, yeah, you can probably ditch the \n from the dpkg-query return, stuff it in a make var, and feed that variable to dpkg-gencontrol, and Bob's your uncle.
[16:56]  * infinity handwaves over the details, since it's too early to be pastebinning examples.
[16:56] <doko> infinity: do you expect glibc to migrate today, or will it take some more time?
[16:56] <infinity> doko: I expect to be uploading a new one.  Is there some urgency?
[16:56] <doko> ok, then starting the test rebuilds now without it
[16:56] <infinity> (And if there was urgency, is there a reason you didn't ask me to merge it instead of just taking it on yourself to do so?)
[16:56] <doko> well, I did ...
[16:57] <infinity> doko: The only thing I have from you is a request to fix the ppc build failure on the next upload.  There wasn't a time limit attached to it. :P
[16:57] <infinity> Anyhow, redoing the merge, since your merge wasn't actually a complete merge.
[16:57] <infinity> And fixing the other bits that were staged for that upload.
[16:58] <infinity> And still investgating weird regressions.
[16:58] <infinity> But I don't think any of it should be relevant to the test rebuild.
[16:59] <nacc> infinity: right, that's what i'm thinking as well -- working on it now
[18:08] <bdmurray> flexiondotorg: What's the status of bug 1623856?
[18:45] <nacc> infinity: http://paste.ubuntu.com/23568890/ seems to extract the correct value into the resulting binary package
[19:13] <infinity> nacc: Why the eval?
[19:13] <nacc> infinity: I found that without that, the variable wouldn't get defined in the target section
[19:13] <nacc> infinity: as it needs to be resolved at run-time, not parse-time?
[19:13] <infinity> Oh indeed.
[19:14] <nacc> basically, makefile gotcha :)
[19:14] <infinity> nacc: Yeah, not braining well.  Haven't slept much. :P
[19:14] <nacc> infinity: np! i hit my head against it for a while until i bothered googling a bit :)
[19:14] <infinity> nacc: Looks sane enough, and if it tested okay too, yay.
[19:15] <nacc> infinity: yep, i'm sending it to debian for comments
[19:15] <infinity> nacc: Could perhaps use a comment explaining why all that evil exists.
[19:15] <nacc> i've bisected the php-imagick failure too, it's an imagemagick change which maybe broke the testcase's assumption
[19:15] <nacc> infinity: yep, agreed :)
[19:18] <nacc> infinity: with a small comment: http://paste.ubuntu.com/23569056/
[19:19] <infinity> nacc: I'd include a ref to the Debian bug where the imagemagick maintainers told you to piss off.
[19:20] <nacc> infinity: oh good point!
[19:20] <infinity> (Not for political reasons, but just so that future ruby-rmagick and/or imagemagick maintainers can easily find the history of the hack.
[19:20] <infinity> )
[19:21] <nacc> infinity: agreed
[20:03]  * doko watches kees rising from the dead ...
[20:04] <kees> ;p
[20:04] <kees> gdb haaaaaack
[20:07] <doko> kees: please send it upstream
[20:08] <kees> doko: yeah, that's my intention. I always get the Changelog formatting wrong, but I'll give it a shot. ;)
[21:46] <kees> doko, bdmurray: sent upstream!
[22:41] <doko> Laney: -gz now recognized in 6.2.1-5ubuntu2
[22:57] <doko> infinity: I'm (mis)using the https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc PPA for the compressed-debug-info test rebuild. please don't change anything in this ppa for zesty (at least you didn't in the last few years ;)


[00:02] <drguildo> can somebody please confirm for me that 204536 and 219605 are the same bug?
[00:03] <persia> bugs #204536 and #219605
[00:04] <persia> drguildo, They aren't the same bug.  They desscribe the 100% problem for two different methods of adjusting volume.
[00:06] <drguildo> isn't the volume set and read from one place?
[00:06] <drguildo> i.e. alsa
[00:07] <drguildo> i'm sure you're right and i'm missing something but i'm just trying to understand what it is
[00:13] <persia> drguildo, The volume can be set in hardware, in alsa (master, front, PCM, etc.), in pulse, and in each application.
[00:13] <persia> Recommendation by audio experts is to set everything but hardware to maximum for best reproduction.
[00:13] <persia> Since not all hardware has accessible switches, this doesn't work for some people (plus some people like to mix with different levels from different software).
[00:15] <drguildo> persia, thanks for the clarification
[03:32] <bucket529> bug 59102 is a typo. The package appears to be maintained by core-dev. A patch went upstream, and their tracker shows it was accepted. But it stopped getting updated in Debian, so Hardy -before the patch- is the last version in Ubuntu. Should this be marked 'Fix Committed' since upstream accepted the patch, or 'Invalid' (Wontfix) since a new version with the patch seems quite unlikely?
[03:33] <bucket529> Correction: bug 59012
[03:43] <bucket529> Aha. Debian removed them because upstream withered. Ubuntu SRU seems unlikely because they don't affect the stability of the program. So Invalid it is.
[03:44] <hggdh> bucket529, I think evms is not even packaged anymore
[03:44] <bucket529> hggdh: Apparently not.
[03:44] <hggdh> last package was on Hardy
[03:44] <hggdh> then it was dropped
[09:49] <mr-russ> can somebody with privilege mark #63141 as triaged.  It's as good as it's going to get, including patches and links to patches.  Thanks.
[10:28] <persia> bug #63141
[10:34] <persia> mr-russ, Which tasks should be "Triaged"?
[10:46] <mr-russ> persia: all, they are all the same bug.  caused by the postgresql fault.
[10:46] <mr-russ> I would have thought they should all be marked as triaged, but maybe just the postgresql one.
[10:46] <mr-russ> what's the policy on triage in this type of case, where a bug presents in one package, but the root cause is in another?
[10:49] <mr-russ> in the case, the bug presents in php, but is caused by postgresql client libraries.
[10:50] <persia> As long as the cause is understood in both affected packages, triage is fine.
[10:50] <mr-russ> I hope I've explained it well enough along the way then :)
[10:51] <persia> For different classes of bugs, that manifests differently, so sometimes it's only one task that is triaged, and sometimes all of them.
[10:51] <persia> Looks like it's manifesting in moodle as well, but we don't need more tasks.
[10:51] <mr-russ> ah, I understand.  In this case it's known for all cases.
[10:52] <persia> (moodle because of php because of postgresql)
[10:54] <persia> Marked "Triaged".  Only other thing that might be worth doing is opening a Debian bug on postgresql and attaching an adjusted patch, and linking it, or submitting the postgresql patch upstream, depending on your motivation level.
[10:55] <mr-russ> and I had to beat the pg developers around a bit to accept responsibility.
[10:56] <mr-russ> My debain bug skill level is basically 0.
[10:56] <persia> Oh, right.  Looking more carefully, the patch is already upstream.  Cool.
[10:56] <persia> (meaning in postgresql trunk)
[11:16] <mr-russ> thanks persia.  I'm off for the night.  bye.
[11:52] <chrisccoulson> anyone have any idea where bug 298628 shoud be? nautilus or sshfs?
[11:52] <chrisccoulson> i can confirm the bug exists but i don't know which package is at fault really
[11:56] <persia> Might even be gvfs (although I'm not sure either)
[11:57] <chrisccoulson> yeah, i'm really not sure. i can still copy files to the fuse mount with the terminal, but it's just nautilus that fails
[11:57] <chrisccoulson> so it's probably not a sshfs issue
[11:59] <chrisccoulson> i can also copy files in to the mount using gvfs-copy, so it is probably just a nautilus problem then
[12:01] <persia> What does df -k report?
[12:01] <persia> My weak understanding is that gvfs actually performs a mount of some sort, but I could well be mistaken.
[12:03] <chrisccoulson> 1 second. just need to fire up my virtual machine again
[12:03] <ogra> can you make sure the user is running the proper 8.10 ssh version ?
[12:03] <jrib> hi, I can't figure out how to unsubscribe from bugs for a certain package.  I click on my profile, bugs and then I've clicked everywhere (except the right place of course).  I'm on edge by the way
[12:04] <ogra> the fix that sshfs reports proper values works only with openssh >5.0
[12:04] <chrisccoulson> ogra - i'll chck that on my system then, because i can recreate the bug
[12:04] <ogra> i'm not sure, might even be that 5.1 is needed on both sides
[12:06] <jrib> ok, I had to go to the package page and look ask to *subscribe* in order to change settings so that I could unsusbscribe :)
[12:06] <jrib> s/look//
[12:07] <chrisccoulson> ogra - i'm running 5.1 on both sides and i still see the incorrect free space reported
[12:07] <ogra> weird
[12:08] <ogra> its likely related to debian bug 464138
[12:09] <ogra> but it shouldnt report 0 bytes according to that
[12:10] <chrisccoulson> yeah, it looks like it was fixed in 2.0-1
[12:11] <chrisccoulson> but i'm running 2.0-2
[12:11] <chrisccoulson> very strange. so, i'll assign it to sshfs for now if you agree?
[12:12] <ogra> yeah
[12:13] <ogra> probably also refer to the debian bug
[12:13] <chrisccoulson> i'll do that. thanks
[12:13] <ogra> it might be a regresseion between -1 and -2
[14:57] <Araneidae> `apt-get install kubuntu-desktop` doesn't produce a working kubuntu (can't actually log in).  Is this a known problem?  (Haven't found it on https://launchpad.net/ubuntu/+bugs?field.searchtext=kubuntu-desktop&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&
[14:57] <Araneidae> field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package= yet, and launchpad is painfully slow.)
[14:58] <Araneidae> Oops.  SOrry about the crappy link, didn't realise it was quite so large and useless -- just a search link into launchpad ubuntu
[15:03] <Araneidae> Hmm: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/260744
[15:28] <ToHellWithGA> ubuntu likes to set my wireless rate to 1Mbps
[15:29] <ToHellWithGA> i thought it was a problem with the chipset on my desktop, now it's doing the same thing to my laptop
[15:31] <ToHellWithGA> i have an ralink chipset using the rt2x00 series of modules on the desktop and an atheros chipset using the ath9k module
[15:31] <ToHellWithGA> *on the laptop
[16:32] <asac> ToHellWithGA: intrepid?
[16:33] <asac> ToHellWithGA: did you try the backport modules?
[16:35] <asac> ToHellWithGA: also ... how sure are you that its 1 mpbs
[16:35] <asac> could be that its just displayed that way
[16:35] <asac> while you get full speed in practice
[16:57]  * davidw is trying to figure out if something even is a bug:
[16:57] <davidw> CPLUS_INCLUDE_PATH=/usr/include/ g++-4.3 -o hm hm.cpp <- fails
[16:57] <davidw> CPLUS_INCLUDE_PATH=/usr/include/ g++-4.2 -o hm hm.cpp <- ok
[16:58] <davidw> hm.cpp is: #include <ext/hash_map> \n \n int main () { __gnu_cxx::hash_map<int, int> t; return 0; }
[17:23] <davidw> https://bugs.launchpad.net/ubuntu/+source/gcc-4.3/+bug/298774
[17:23] <davidw> ok... we'll see where that goes
[18:21] <chrisccoulson> james_w - are you there?
[19:36] <mnemo> i have a reproducible SEGV in rhythmbox that I would like to fix but I dont know what to do next... basically I can run the repro under gdb and this is what I see: http://rafb.net/p/SRqDMM84.html   whats the next step to analyze this? for example, how can I tell which variable caused the bad memory read or bad write?? if I knew that I could trace it back upwards in the stack, but I dont know how to see which variable read/write caused the SEGV
[20:06] <wake> Hi, there is a guy who has problems with his DVR. It can not read DVD-Rs after they have been burnt
[20:06] <wake> is this a kernel bug?
[20:09] <wake> where should CD rom and DVR bugs be filed?
[20:11] <mnemo> wake: what exactly is the problem with the CD ?
[20:12] <wake> There is a guy who has filed a bug saying his DVR does not recognise DVD-r after they have been burnt
[20:12] <wake> thus, the disc can not be verified after a burn. although it works fine on other drives in his computer
[20:13] <mnemo> hmm, not sure about that one.. maybe someone else knows..
[20:13] <wake> ok. thanks anyway :p
[20:16] <ToHellWithGA> asac: i know it fails to load regularly
[20:16] <ToHellWithGA> i did much better when ubuntu had no module
[20:17] <ToHellWithGA> at least at that point when i build madwifi from source the module loaded at every boot, worked, and worked with suspend/resume
[20:17] <ToHellWithGA> the state of ubuntu on an intel 945 chipset macbook is terrible
[20:18] <ToHellWithGA> hardy worked great but for wireless and now intrepid is thoroughly broken
[20:18] <ToHellWithGA> asac: how would i determine if it is just reporting the incorrect speed?
[20:29] <davidw> ToHellWithGA, wireless seems to be a pretty serious issue
[20:41] <asac> feel free to rant here, but dont expect me to jump on that ;)
[20:43] <ToHellWithGA> i don't really
[20:43] <ToHellWithGA> i just wish i could figure out what was happening
[20:44] <asac> ToHellWithGA: driver front is difficult. try the linux-backport-modules
[20:44] <asac> thats a package with top-notch wireless drivers
[20:44] <ToHellWithGA> i'll look into it
[20:44] <ToHellWithGA> thanks for the suggestion
[20:44] <asac> just install it and see if things improve
[20:44] <ToHellWithGA> asac: on an unrelated note, i believe a bug i file was incorrectly marked as a duplicate
[20:45] <asac> ToHellWithGA: which bug?
[20:45] <ToHellWithGA> i file a bug against the "systemsettings" package for having no useful controls when installed under gnome and it was marked as a duplicate of having no controls whatsoever
[20:45] <ToHellWithGA> i'll go get the number
[20:45] <asac> is that networking related?
[20:46] <ToHellWithGA> bug 296023
[20:46] <ToHellWithGA> not at all
[20:46] <asac> i am completely disconnected from kubuntu. cannot say whats going on ;)
[20:46] <ToHellWithGA> because gnome users run kde applications it is useful to install a kde control panel
[20:46] <ToHellWithGA> i only run gnome
[20:47] <asac> ToHellWithGA: well. we dont want to install kde stuff in gnome
[20:47] <asac> (and we cannot technically)
[20:47] <asac> that would be bloat for most users
[20:47] <ToHellWithGA> when i run k3b i like the mouse to behavie as i expect, single click to hilight, double click to open
[20:47] <asac> what kinders you to install the kde kontrol application?
[20:47] <asac> doesnt that work?
[20:47] <ToHellWithGA> in the past, the "kcontrol" package handled mouse configuration
[20:47] <ToHellWithGA> kcontrol is gone
[20:48] <ToHellWithGA> the new kde4 package doesn't have any mouse settings so i'm stuck on funkycrazyclick mode
[20:48] <ToHellWithGA> bummer, huh?
[21:45] <andresmujica> ..
[22:44] <andresmujica> it seems 5-a-day it's broken
[22:45] <andresmujica> all the bugs i've sent
[22:45] <andresmujica> shown a 104 error message...
[22:45] <andresmujica> :(
[22:45] <nhandler> andresmujica: I just used the applet, it appeared to work
[22:45] <andresmujica> hmmm...
[22:45] <andresmujica> funny..
[22:46] <nhandler> I would just wait a little bit and then try again later. Your connection might be having a problem
[22:46] <andresmujica> that could be the cause..
[22:46]  * Hobbsee wonders what error 104 actually is
[22:46] <andresmujica> well one day without stats...
[22:46] <andresmujica> let me try again
[22:47] <andresmujica> unknown failure sending error bug #whatever
[22:47] <andresmujica> error code 104
[22:48] <andresmujica> how can i sent it vua console?
[22:48] <andresmujica> i'm too used to the applet.. :)
[22:48] <nhandler> andresmujica: 5-a-day --add BUGNUMBER
[22:54] <andresmujica> it shown a different error...
[22:55] <andresmujica> http://pastebin.ubuntu.com/73106/
[22:56] <nhandler> andresmujica: Try running 'bzr break-lock lp-46046992:///~andres-mujica/5-a-day-data/main/.bzr/branch/lock
[23:01] <andresmujica> bzr: ERROR: Unsupported protocol for url "lp-46046992:///~andres-mujica/5-a-day-data/main/.bzr/branch/lock"
[23:01] <lifeless> nhandler: the url returned is garbage
[23:01] <lifeless> andresmujica: bzr break-lock lp:/~andres-mujica/5-a-day-data/main
[23:02] <andresmujica>  bzr break-lock lp:/~andres-mujica/5-a-day-data/main
[23:02] <andresmujica> Break lock<EMAIL_ADDRESS>[23:02] <andresmujica> held by<EMAIL_ADDRESS>on host crowberry [process #10538]
[23:02] <andresmujica> locked 2 hours, 15 minutes ago? [y/n]: y
[23:03] <andresmujica> upps.. sorry..
[23:04] <andresmujica> ok, GREAT!!
[23:04] <andresmujica> it's working now.
[23:04] <andresmujica> i've should asked before...
[23:04] <andresmujica> maybe i've  suspended the laptop while sending a bug....
[23:04] <andresmujica> thanks!
[23:52] <andresmujica> which packages is responsible for loading firmware when a device is plugged?  udev or hal?


[12:32] <BenC> bronson: Ok, sounds good
[12:33] <BenC> bronson: You may want to look at how the xen package in edgy is done
[12:33] <bronson> Good call, will do.
[03:13] <zul> hey
[12:36] <AnAnt> BenC: ping
[12:37] <crimsun> AnAnt: it's 6:37a in his timezone, surely you don't expect him to be awake?
[12:37] <AnAnt> crimsun: err, I wake up before 6:37 sometimes
[12:38] <AnAnt> crimsun: I mean it depends on each one's habit
[12:38] <crimsun> 6:37a on a Sunday is a bit of a stretch.
[12:38] <crimsun> -maybe- in 8 hours.
[12:39] <AnAnt> oh
[12:39] <AnAnt> it is sunday
[12:39] <AnAnt> ok
[03:56] <arvind_> I grabbed: linux-source-2.6.19-2.6.19 but my build (invoking fails with make-kpkg --initrd --append-to-version=-0.2 kernel_image kernel_headers
[03:57] <arvind_> dh_installdirs: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> grep: ../../../config/archmap: No such file or directory
[03:57] <arvind_> Use of uninitialized value in string eq at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
[03:57] <arvind_> dh_installdocs: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> Use of uninitialized value in string eq at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
[03:57] <arvind_> dh_installchangelogs: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> dh_compress: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> dh_fixperms: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> dh_shlibdeps: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> Use of uninitialized value in string eq at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
[03:57] <arvind_> dh_installdeb: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> Use of uninitialized value in string eq at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
[03:57] <arvind_> Use of uninitialized value in string eq at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
[03:57] <arvind_> dh_gencontrol: Compatibility levels before 4 are deprecated.
[03:57] <arvind_> Use of uninitialized value in string eq at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 655.
[03:57] <arvind_> dpkg-gencontrol: error: package linux-headers-2.6.19-rc6-ubuntu1-0.2 not in control info
[03:57] <arvind_> dh_gencontrol: command returned error code 65280
[04:02] <pmjdebruijn> arvind_, please use a pastebin next time.
[04:16] <arvind_> ok==
[04:16] <arvind_> how2 does one fix that pmjdebruijn
[04:16] <pmjdebruijn> no clue, sorry
[04:17] <arvind_> what the correct way to build linux-source-2.6.19-2.6.19=
[04:20] <arvind_> pmjdebruijn?
[04:25] <pmjdebruijn> arvind_, you can find that one the wiki I think
[04:26] <pmjdebruijn> arvind_, anyway, I'm not an expert
[04:26] <arvind_> i followed wiki custom kernel building
[04:40] <AnAnt> BenC: ping
[04:42] <okaratas> [BenC PING reply] : 0secs
[04:42] <okaratas> -
[04:42] <okaratas> [BenC PING reply] : 1sec
[04:44] <AnAnt> errr, I mean is he awake or not
[04:50] <BenC> AnAnt: yo
[04:53] <AnAnt> BenC: hello, remember the SD problem that I told you about ?
[04:53] <BenC> yeah
[04:53] <AnAnt> BenC: I just installed feisty yesterday
[04:53] <AnAnt> BenC: I tried the SD with it, it works, but dmesg gives out some errors
[04:56] <AnAnt> BenC: shall I send you those errors in email ?
[04:56] <BenC> sure
[04:56] <AnAnt> BenC: btw, I had to modprobe tifm_sd
[04:59] <AnAnt> ok
[05:04] <mjg59> BenC: I was chatting to Kyle about wireless support
[05:04] <mjg59> BenC: I think we probably want to be regularly pulling from wireless-2.6
[05:05] <mjg59> BenC: But probably getting bcm43xx and p54 from dscape instead
[05:05] <mjg59> (possibly one or two other drivers as well)
[05:05] <mjg59> By dscape, I mean drivers/net/wireless/d80211/ from wireless-dev
[05:05] <mjg59> Which also means pulling in net/d80211 from there
[05:06] <BenC> mjg59: I'd have to look into that...last time I started doing that, the ieee80211 changes started breaking some of our third-party drivers, and I ended up having several (more) versions of the 80211 stack in the tree
[05:06] <mjg59> That gives us the option of pulling madwifi as well
[05:06] <mjg59> BenC: The wireless-2.6 changes, or the wireless-dev ones?
[05:07] <mjg59> The -2.6 ones are likely to land during the 2.6.20 timeframe, so we'd probably be screwed anyway
[05:07] <BenC> mjg59: I think in dapper, the wireless changes we pulled in for bcm43xx and some other stuff was breaking even in-tree wireless drivers
[05:07] <mjg59> Right, that was because there was a fairly large delta between upstream and us
[05:07] <mjg59> That's not true at the moment
[05:08] <BenC> mjg59: If it comes in during 2.6.20, then the third-party drivers usually get fixed up before release by their upstream
[05:08] <mjg59> I'll take a look into it, anyway
[05:08] <BenC> or we can fix them easily (I had to do a lot of ESSID-1 fixes for 2.6.19 at first)
[05:09] <BenC> mjg59: I'm not against it...I'd have to check the trees to see what were getting into
[05:09] <mjg59> -2.6 just gets us fixes that are based off the current stack
[05:09] <mjg59> -dev gets us much more crack, but it's also where all the bcm43xx development is happening
[05:10] <BenC> hopefully -2.6 will get into 2.6.20...if not, we can probably pull it anyway
[05:10] <BenC> -dev would probably be best as added to ubuntu/ for whatever drivers we want to take in
[05:10] <mjg59> Yeah
[05:10] <BenC> and dscape
[05:10] <mjg59> I wasn't planning on pulling that directly
[05:11] <BenC> dscape was broken last I checked...wouldn't even compile against 2.6.20
[05:11] <mjg59> My main machine's drive died last night, so I'm going to have to get another dev machine together
[05:11] <BenC> I still need to see how much shit is going to break in LRM against 2.6.20 :/
[05:12] <mjg59> Heh
[05:13] <mjg59> That's one reason for being interested in dadwifi
[05:13] <kylem> dadwifi?
[05:13] <BenC> does dadwifi have a free hal?
[05:13] <siretart> is it usable yet?
[05:13] <mjg59> wireless-dev still seems to be 2.6.19-rc6
[05:13] <mjg59> kylem: madwifi but on dscape rather than net80211
[05:13] <mjg59> BenC: Yes
[05:13] <mjg59> siretart: No clue. Easy to find out.
[05:14] <BenC> hmm...I should test it on my friends laptop, he has a madwifi chipset that even madwifi CVS doesn't work with
[05:14] <BenC> had to use ndiswrapper
[05:14] <mjg59> It might not work
[05:14] <mjg59> But you stand a better chance of bodging it into doing so
[05:33] <kylem> BenC, https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.19/+bug/75107
[05:33] <kylem> *blink*
[05:45] <BenC> kylem: Yeah, that's a nice one :)
[05:45] <mjg59> NR_CPUS is 1?
[05:46] <kylem> it's not though.
[05:46] <kylem> it's 8... in /ALL/ the configs since ubuntu-2.6.git was created.
[05:46] <BenC> of course it isn't enabled
[05:46] <BenC> he is running the -386 kernel, not -generic
[05:46] <kylem> oh.
[05:46] <kylem> HAH.
[05:48] <BenC> grub seems to prefer -386 over -generic when both of the same version are installed
[05:56] <JanC> grub orders kernels alphabetically AFAIK?
[05:56] <JanC> or more precise: in ASCII order  :)
[05:58] <BenC> I think there's a little more to it
[06:03] <_MMA_> Hi BenC. I just wanted to let you know Im still getting that spec together.
[06:03] <_MMA_> I met with crimsun yesterday and he gave me some things to think about.
[06:32] <lehaid> hi, i'm using baseline ubuntu kernel, compiling, doing make modules_install, and it doesn't updat ethem, why ?
[06:33] <lehaid> it updates to a diff /lib/modules, why is that ?
[06:36] <mjg59> Because you haven't passed EXTRAVERSION
[06:36] <lehaid> passed it where?
[06:37] <lehaid> i used the .config from /boot
[06:37] <mjg59> make EXTRAVERSION=-10-386 or whatever
[06:37] <lehaid> where is that defined ?
[06:37] <mjg59> It's generated by the buildsystem under debian/rules
[06:37] <lehaid> if i manually compile the kernel?
[06:39] <lehaid> can i cp the /lib/modules to the correct one
[06:39] <mjg59> No
[06:39] <lehaid> or will it bork up ?
[06:39] <lehaid> so can you tell me what needs to be done ?
[06:39] <lehaid> in manual compiling
[06:39] <mjg59> I did
[06:39] <mjg59> make EXTRAVERSION=-10-386 or whatever
[06:40] <lehaid> ahh, and what should be in 6.06 something like
[06:40] <mjg59> No
[06:40] <lehaid> make EXTRAVERSION=-27-386 ?
[06:40] <mjg59> Whatever comes after the base kernel version
[06:40] <mjg59> Oh, right
[06:40] <mjg59> Yes
[06:40] <lehaid> k
[06:40] <lehaid> blah
[06:40] <mjg59> Then the same for modules_install
[06:40] <lehaid> so now it will RECOMPILE ALL THE KERNEL ?
[06:40] <mjg59> Yes
[06:40] <lehaid> ARGGGGGGGG
[06:40] <lehaid> just finished 1 hour compile of it
[06:41] <lehaid> where is this documented?
[06:42] <lehaid> https://wiki.ubuntu.com/KernelCustomBuild?highlight=%28CategoryKernel%29 <-- is that for 6.10 only ? since i dont have "debian/config/ARCH" anywhere on the HD
[06:44] <lehaid> mjg59 ?
[07:02] <bronson> Anyone know where the Xen Edgy git tree is?
[07:02] <bronson> Been googling for a bit...  can't find it.
[07:13] <bronson> Maybe this hand-assembled URL...?   git clone git://dev.laptop.org/projects/ubuntu-xen-2.6.17