[00:14] <valorie> DarinMiller: can I copy the above links and instructions in a blog post, crediting you?
[00:14]  * valorie blogs as the linux grandma
[00:17] <valorie> unless you blog, and your should -- in which case, you should be on the planets!
[00:23] <DarinMiller> Valorie: Sure, anytime.
[00:24] <valorie> excellent
[00:27] <valorie> DarinMiller: any particular reason you asked them to install gksu?
[00:27] <valorie> kdesudo works and is standard install
[00:28] <DarinMiller> :) I used GNome and those were notes from my old days.  I need to update my notes. Thanks!
[00:28] <valorie> heh
[00:29] <valorie> so python-glade2 is still needed?
[00:30] <DarinMiller> Uhhh, maybe some more stale notes... I will have to verify on a fresh install... possibly needed for GUI.....
[00:32] <valorie> I'll leave it in
[00:32] <valorie> !info python-glade2
[00:32] <valorie> hmmm
[00:42] <valorie> http://www.unixmen.com/howto-install-and-configure-samba-share-in-ubuntu/ works, btw
[00:42] <valorie> a bit old
[01:18] <DarinMiller> Updated my SMB notes so less likey to give marginal advice in the future.  Thanks for the feedback. :)
[07:55] <eeos> hi everybody, I have deleted a folder from an ext4 artition by mistake. Unfortunately I cannot unmount the directory.
[08:01] <eeos> Cannot use ext4undelete .... any other solution you know of?
[08:01] <hateball> !undelete
[08:24] <knro> What version of KDE Frameworks 5 will be available in 16.04?
[08:24] <knro> I see 5.15 in Xenial repos, but isn't that a bit old?
[08:26] <valorie> we've got some slow uploading happening
[08:28] <knro> valorie: you know what the plan is? KF5 5.19?
[08:28] <valorie> FW 5.18 is what we have in landing
[08:28] <acheron88> 5.18 if the packages in the landing/staging ppas make it in I think?
[08:28] <valorie> yes, if the FFEs got filed
[08:30] <valorie> if not, hopefully that will happen later today
[08:30] <acheron88> as LTS I assume it will keep going with a few stable upgrades anyway, no matter what is there on release
[08:31] <valorie> right
[08:31] <valorie> only well-tested stuff
[08:31] <valorie> which is why we'll miss the newest Qt
[08:31] <acheron88> yes
[08:49] <eeos> hateball: thanks!
[12:25] <BluesKaj> Hi folks
[12:53] <hazamonzo> Howdy BluesKaj
[12:53] <BluesKaj> Hey hazamonzo
[12:55] <hazamonzo> BluesKaj: So check this. Kubuntu has been working pretty well so far but just recently... its happened twicw.. but the UI has frozen
[12:55] <hazamonzo> Not the mouse or the OS as such
[12:55] <hazamonzo> just the ability to click anything
[12:55] <hazamonzo> I thought i could drop out into a terminal (ctrl+alt+F1)
[12:55] <hazamonzo> then try restarting plasma or something
[12:56] <BluesKaj> hazamonzo, can you moce the mouse or see the cursor move?
[12:56] <BluesKaj> move
[12:56] <hazamonzo> yeah i can
[12:56] <hazamonzo> its like trying to click a photo of your desktop
[12:56] <hazamonzo> calt alt-tab windows either
[12:56] <hazamonzo> *can't
[12:57] <BluesKaj> 15.10?
[12:57] <lordievader> hazamonzo: Can you still activate krunner?
[12:57] <lordievader> When that happens.
[13:00] <hazamonzo> BluesKaj: lordievader krunner....
[13:00] <hazamonzo> Im not sure what that is!
[13:00] <hazamonzo> 2 secs
[13:01] <hazamonzo> ahh, the little terminal at the top of the desktop?
[13:01] <hazamonzo> I've pulled that up by accident many times before but im not sure if it works during the freeze
[13:01] <hazamonzo> whats the shortcuy keys for that so i can test next time it happens?
[13:01] <hazamonzo> BluesKaj: 15.10 yeah
[13:02] <hateball> hazamonzo: alt+space by default
[13:02] <hazamonzo> hateball: Good to know! Cheers
[13:02] <hateball> hazamonzo: it may be useful binding ctrl+alt+T to launch Konsole :)
[13:03] <lordievader> hazamonzo: If so, you could issue 'kquitapp plasmashell && kstart plasmashell' there, it might fix things.
[13:03] <hazamonzo> i usually drop out to a terminal using ctrl+alt+F1 to F6
[13:04] <hazamonzo> lordievader: Okay. Im going to take a noteof that for the next time it happens
[13:04] <hazamonzo> I was looking for something like this to simply restart my desktop
[13:04] <hazamonzo> or desktop UI
[13:05] <BluesKaj> hazamonzo, yakuake is a good alternative
[13:06]  * hazamonzo googles
[13:07] <BluesKaj> to the terminal. that is
[13:08] <soul_> Yakuake is <3
[13:09] <BluesKaj> soul_, to me that indictes it's less than 3
[13:11] <soul_> hahaha, very good one BluesKaj!
[13:12] <BluesKaj> if you were trying to show some kind of image there, it's beyond my understand ..I don't use text images except for smileys
[13:13] <BluesKaj> understanding rather
[13:13] <hazamonzo> o7
[13:13] <soul_> <3 → means a heart x)
[13:14] <BluesKaj> ok
[13:14] <hazamonzo> yakuake seems pretty nice
[13:14] <BluesKaj> doesn't look like that to me ;-)
[13:15] <BluesKaj> yakuake is great, been using it for many yrs, F12 and it's there
[13:16] <soul_> I use the "Pause" key on my laptop keyboad
[13:16] <soul_> since I don't use it at all
[13:44] <GreenDay> hello
[13:44] <GreenDay> does deezer rocks under kubuntu?
[13:44] <Frank__> Help with printer drivers
[13:45] <chaithanya> Hello, I  installed Kubuntu 15.10 in  Lenovo G50-70, I'm unable to connect to the wireless networks. Can anyone please guide me through this?
[13:45] <Frank__> I have Kubuntu 14.04 and have just purchased a canon MF216n printer and cannot find any drivers for it and the system will not recognize it as being there.
[13:45] <hateball> GreenDay: Do you mean if you can use Deezer in Kubuntu? It seems to be some web based thing, so probably
[13:46] <hateball> chaithanya: what chipset is the wifi? "lspci |grep Net" will show
[13:46] <BluesKaj> GreenDay, deezer is a Unity web app, not KDE/Plasma
[13:46] <hateball> You can probably just use the website tho
[13:48] <BluesKaj> doh!
[13:49] <hateball> oh they left
[13:49] <hateball> Looking at https://www.usa.canon.com/internet/portal/us/home/support/details/printers/black-and-white-laser/mf216n it seems to have a linux driver at least. the autodetect of OS fails tho
[13:52] <chaithanya> hateball: 02:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01)
[13:53] <hateball> chaithanya: Open the driver manager and add the restricted firmware for it
[13:54] <hateball> alternatively, "sudo apt-get install bcmwl-kernel-source", let it work its magic and reboot
[14:03] <chaithanya> hateball: I ran the command, now reeboting
[14:04] <hateball> Let's hope for the best then!
[14:08] <chaithanya> hateball: It worked! Thanks a ton :)
[14:08] <hateball> chaithanya: :)
[14:14] <GreenDay> now i listen to scorpion online ;)
[14:15] <BluesKaj> !OT | GreenDay
[14:15] <GreenDay> oh
[16:23] <irawansyah> shorcut application blender and android studio gone when i install kde, how to fix it
[16:23] <six86> Hello, since a while now (came with an update) my kubuntu 15.10 with Backports doesn't shutdown when I chose to shutdown, but instead it just logs out. From there I then can manually shutdown. Is this known? How can I fix it?
[16:25] <BluesKaj> irawansyah, which kubuntu and how did you install kde?
[16:26] <BluesKaj> or 'buntu rather
[16:27] <BluesKaj> six86, have you updated and upgraded today?
[16:27] <six86> BluesKaj: No. Not yet.
[16:27] <BluesKaj> then do so
[16:28] <six86> :-D Fix incoming?
[16:28] <irawansyah> i install kubuntu through ubuntu software centre
[16:50] <six86> BluesKaj: Upgrading didn't help.
[16:53] <soul_> I don't have audio using headphones in my laptop. Can somebody help me to figure out how to solve the issue, please?
[16:55] <BluesKaj> six86, what does uname -a show?
[16:56] <BluesKaj> soul_, disable automute in alsamixer
[16:57] <Jeeten> hey if i update-qt lib 4.8 to 5.5 on my kubuntu plama 15.10 than there are any problem generated on my system?
[16:59] <Jeeten> hey can anybody help me?
[16:59] <soul_> I already did, BluesKaj. Still nothing :/
[17:00] <Jeeten> i am trying to install Ampps Web developing app but when i run
[17:01] <BluesKaj> Jeeten, suggest you leave the default qtlibs alone and do the normal upgrades for your system
[17:01] <Jeeten> Cannot mix incompatible Qt library (version 0x40806) with this library (version 0x40805)
[17:01] <Jeeten> i have error
[17:02] <Jeeten> Blueskaj, i have error Cannot mix incompatible Qt library (version 0x40806) with this library (version 0x40805)
[17:02] <BluesKaj> Jeeten, if you're fooling around with Qt libs you'd beter know what you;'re doing
[17:05] <Jeeten> Blueskaj , i want to install {http://www.ampps.com/} app on my Kubuntu and i don't know about qt libs ! This app making on QT.
[17:06] <BluesKaj> Jeeten, no idea, sorry , not a web dev'
[17:06] <Jeeten> ok thanx
[17:08] <agile_prg> hi all, I just loaded kubuntu, is there a way to add a bottom task bar?
[17:09] <agile_prg> oh wait I see it
[17:11] <soul_> Seems impossible for me to solve this. Is there a place to ask about this kind of problem?
[17:11] <six86> BluesKaj: Linux pc 4.2.0-27-generic #32-Ubuntu SMP Fri Jan 22 04:49:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
[17:16] <rattking> soul_: have you poked around phonon settings? in Hardware -> Multimedia -> Phonon
[17:29] <BluesKaj> soul_, have you checked phonon as rattking suggested and your pulseaudio output settings as well as thevolume ctrls for the appropriate outputs in alsamixer
[17:37] <agile_prg> how do I add a desktop shortcut?
[17:38] <BluesKaj> agile_prg, do you mean icons to the desktop?
[17:38] <agile_prg> ya
[17:39] <BluesKaj> just drag them out of the kmenu
[17:39] <agile_prg> what if they are not in the kmenu?
[17:40] <BluesKaj> if they aren't in th ekmenu then they are most likely not installed. Which app are you referring to?
[17:40] <agile_prg> qtcreator
[17:42] <soul_> rattking: BluesKaj... This is what I have: http://imgur.com/a/l6PP5
[17:42] <soul_> Do those images tell you something?
[17:45] <BluesKaj> agile_prg, http://askubuntu.com/questions/540464/creating-a-shorcut-for-application
[17:45] <six86> Hello, since a while now (came with an update) my kubuntu 15.10 with Backports doesn't shutdown when I chose to shutdown, but instead it just logs out. From there I then can manually shutdown. Is this known? How can I fix it?
[17:48] <BluesKaj> soul_, plug you 'phones into the lineout on your soundcard
[17:52] <agile_prg> BluesKaj is there no graphical way to make a desktop shortcut?
[17:53] <BluesKaj> agile_prg, dunno
[17:58] <agile_prg> Is there a trash can I can add to the kubuntu desktop?
[18:00] <BluesKaj> agile_prg, yes right click on the desktop , add widgets type trash in the search
[18:00] <soul_> The screenshots are taken with the earphones connected, BluesKaj
[18:00] <agile_prg> can I add a top panel with apps to launch from it?
[18:02] <BluesKaj> you can use a launcher in widgets
[18:02] <agile_prg> oh ok
[18:02] <BluesKaj> agile_prg, recommend you reads about the kde/plasma desktop and what it can do for you
[18:05] <BluesKaj> agile_prg, https://www.linux.com/learn/tutorials/811704-how-to-use-kde-plasma-desktop-like-a-pro
[18:10] <agile_prg> I added an empty panel but it is to the left, I want it to be located on the bottom
[18:10] <agile_prg> can't figure out how to move it down there ;<
[18:12] <agile_prg> figured it out nm
[18:20] <BluesKaj> soul_, open alsamixer in the terminal and make sure your headphones and line/out controls are turned up
[18:27] <Guest83036> Hi , is still possible on KDE 5 to have different background for different desktop ?
[18:28] <marco-parillo> Plasma 5 can support different backgrounds for different activities.
[18:30] <BluesKaj> the virtual desktops separate wallpapers are no longer supported in plsama 5, you have to set them in activities, Guest83036
[18:33] <Guest83036> BluesKaj:  why ?, I mean are two different things
[18:35] <Guest83036> so I can still use until 20 desktop but with the same background, maybe isn't so usefull, at least to me
[18:36] <BluesKaj> yes they are and I was upset about it, but separtate wallpapers are no longer supported in plasma 5 , ...I have 8 differnt actitvities setup with different wallpapers , works ok.
[18:38] <Guest83036> yeah but you can't switch between activities as easy as you can between desktop, I'm wrong ?
[18:43] <Guest83036> I'm testing kde5 and it seems stable and nice but for what I can see there are few usefull things still missing, like for example the plasmoid for the application menu on the top bar, different backgrounds for different desktop and so on .....
[18:46] <marco-parillo> Maybe you could re-assign the default key to switch activities in System Settings > Short Cuts > Global Keyboard Shortcuts > Walk through Activities
[18:49] <Guest83036> well I just non need to use activities, why should I do it ?, When I think about something new I alays think about new possibilities and for me is absurde remove nice features on new version of software
[18:52] <Guest83036> I use Kubuntu since 9.04 and I never used activities and in my opinion they are completelly useless, but I never thought should be removed :D
[18:53] <Tux_> Everytime i download Kubuntu 15.10 it gets to the last sec then download fails ?
[18:55] <BluesKaj> Guest83036, you can assign apps to each actitvity then place the app icons in quicklaunch in th epanel and the actitviies will switch to the background/app that you choose
[18:57] <Guest83036> doing it by the scroll wheel sounds much better to me, anyway .....
[18:59] <BluesKaj> well Guest83036 , that's your call , do what you want , I was merely suggesting
[19:01] <KNRO_> Guest83036: I, on the other hand, use Activities all the time. One "General" activity, another for Gaming stuff, another for development, and another for my observatory stuff
[19:02] <Guest83036> of course BluesKaj and I appreciate your suggestion, but I don't like to be force to change my way to work because someone decide to remove some features
[19:04] <Guest83036> I mean, which one of the features I'm currently using daily will be removed next ?, should I trust it or drop it since now ?
[19:06] <BluesKaj> Guest83036, that's why I nstill have 14.04 with kde4 on my pc as my fallback OS :-)
[19:07] <Guest83036> me ti BluesKaj, but the new kernel on latest version of kubuntu has a much greater support for new hardware and you cannot use kde 4 on Kubuntu 16.04 I guess ....
[19:09] <BluesKaj> Guest83036, no kde4 for 16.04 I'm afraid :/
[19:09] <BluesKaj> or for 15.10
[19:10] <Guest83036> so If I buy a new model I'm forced to use the less complete kde5 instead of kde 4
[19:10] <Guest83036> shouldn't happen !!
[19:12] <BluesKaj> technically there is no kde5, it's now known as kde/plasma5
[19:13] <Guest83036> yeah , that one :D
[19:13] <BluesKaj> don't ask me why ;-)
[19:59] <BluesKaj> !kde/plasma
[19:59] <BluesKaj> !kde | GreenDay
[20:01] <Mylon> So Star Nomad 2 is free for Linux players: http://steamcommunity.com/games/414950/announcements/detail/645508898228502336
[20:02] <Mylon> I just thought I'd spread the word.  It looks like a good quality game.
[20:09] <GreenDay> too bad newsgroups are deprecated today
[20:09] <GreenDay> to the profit of mailing lists
[20:09] <GreenDay> heh
[22:36] <em> hey anyone here?
[22:37] <hazamonzo> em: Best just to ask your question and take a seat
[22:37] <em> sure
[22:37] <hazamonzo> if anyone can help you then they will :)
[22:37] <em> cool thanks
[22:37] <hazamonzo> No worries!
[22:38] <em> well i have the most bizzare problem i have every experienced with Kubuntu.  Usually when I restart it, either to turn it back on or after it suspended for some reason from inactivity, when i restart it, I find that all the icons and pannel has been rearranged, stuff added, stuff randomly put here and there and made bizzare. Look at what my desktop looked like when I turned it on: http://i.imgur.com/LniX8cB.jpg
[22:39] <em> look how its random stuff all over the place
[22:39] <em> look at the madness of the lower pannel.
[22:39] <em> everything randomly moved all around and millions of copies of stuff added that i never asked for.
[22:39] <em> and all those notes and even tiny versions of notes...
[22:43] <em> To clarify: that isn't stuff i had on my desktop that got moved around, its literally stuff I never put there, randomly there, multiple copies and randomly all over the place.
[22:43] <em> i don't even know how the tiny versions of the note thingy was made
[22:43] <em> here again is an image: http://i.imgur.com/LniX8cB.jpg
[23:44] <BlueProtoman> I think I borked my system.  I tried a PPA for Qt 5.5.1, but that broke Plasma.  I removed the PPA via aptitude on the command line and reinstalled some packages, so now I can log in normally.  How can I ensure that I cleaned up properly?
[23:58] <genii> !ppa-purge


 LUBUNTU
 17.10 BETA 1
 GET IT WHILE IT'S HOT
 :3
 It's always hot, which is why you should always have it 😎
 😏
 When's the LTS?
 @AceHW, Not this release, it'll land in April of 2018
 (18.04)
 Dang!
 @tsimonq2, Meh 😄


[16:00] <mdeslaur> o/
[16:01]  * slangasek waves
[16:01] <slangasek> stgraber: I believe you're on point?
[16:01]  * teward waves and then silently sits in the corner
[16:01] <infinity> o/
[16:01]  * stgraber waves
[16:02] <stgraber> #startmeeting Ubuntu Technical Board
[16:02] <meetingology> Meeting started Tue Jul 21 16:02:03 2015 UTC.  The chair is stgraber. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:02] <meetingology> Available commands: action commands idea info link nick
[16:02] <stgraber> #topic Action review
[16:02] <stgraber> slangasek: any progress with legal?
[16:02] <slangasek> stgraber: have not yet referred it to them
[16:02] <slangasek> (maybe you want to quote the action items in question?)
[16:03] <stgraber> ACTION: slangasek to forward complaint to Canonical legal
[16:03] <slangasek> :)
[16:03] <stgraber> ok, so carrying that one forward again
[16:03] <stgraber> #topic Scan the mailing list archive for anything we missed (standing item)
[16:04] <stgraber> we've got a few requests for MREs but those require a single TB hack and discussoin appears to be ongoing.
[16:04] <mdeslaur> I acked the oslo one this morning, and I'll add it to the wiki after the meeting
[16:04] <stgraber> anyone feels like we should discuss any of those threads here?
[16:05] <slangasek> stgraber: sorry, there were other action items from last meeting that I think we've skipped
[16:05] <infinity> I'd take the silence as a no.
[16:06] <stgraber> slangasek: ah? the wiki doesn't list any
[16:06]  * teward raises his hand
[16:06] <slangasek> http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2015/ubuntu-meeting-2.2015-07-07-16.01.html
[16:06] <slangasek> (is the convention that the previous chair transcribes these into the agenda for the next meeting?)
[16:06] <stgraber> yes
[16:07] <slangasek> ok, sorry for missing that
[16:07] <stgraber> #topic Action review
[16:07] <stgraber> ACTION: slangasek to document maas, juju, docker exceptions on https://wiki.ubuntu.com/StableReleaseUpdates#Special_Cases
[16:07] <slangasek> not done, also carry over
[16:08] <stgraber> ACTION: pitti to propose amendment to general SRU policy for new features in LTS
[16:08] <stgraber> no pitti around and I don't believe I've seen a thread on that yet, so will carry over too
[16:08] <infinity> Seems not done, unless he proposed it very quietly.
[16:08] <stgraber> ACTION: all to respond to the Ubuntu Fan SRU proposal on list
[16:08] <stgraber> so far all == pitti I believe, though he's been asking good questions :)
[16:08] <infinity> pitti responded to the fan thing.  I recused myself, since I was involved in the implementation.
[16:09] <infinity> But I'm happy with pitti's ACK.
[16:10] <stgraber> ok. I'll keep the action around and will answer to the thread, hopefully some of the other members will too
[16:10] <slangasek> I had intended to, but it's on the TODO pile in the corner
[16:11] <stgraber> #topic Scan the mailing list archive for anything we missed (standing item)
[16:11] <stgraber> so back to that, sounded like nobody at anything they wanted to bring here for discussion
[16:11]  * teward raises his hand
[16:11] <stgraber> (waiting for wiki.ubuntu.com to log me in...)
[16:11] <stgraber> teward: hi
[16:12] <stgraber> teward: I'm assuming that's about nginx?
[16:12] <teward> stgraber: hello, and greetings to the Ubuntu Technical Board.  While the silence to your inquiry to things to be brought up for discussion will stand, and I will not bother the TB for a decision today, I'd like to bring into view the request I sent to the mailing list with regards to NGINX for X-series.
[16:12] <teward> stgraber: correct, and the only reason I raised my hand is to say that while a decision is not needed today, it is needed soon, as the course of action decision does impact Wily to a point
[16:13] <mdeslaur> teward: sorry, I didn't get a chance to look at it yet, but I will look at it this week
[16:13] <teward> (as part of the nginx message requests a general opinion with regards to the proposed course of action for both X-series and Wily)
[16:13] <teward> mdeslaur: no problem, thank you for letting me know.
[16:14] <teward> I did however at least want to make sure it was on the radar.  :)
[16:14] <mdeslaur> yes, it is
[16:14] <teward> thank you.  that is all from me on it.  :)
[16:15] <mdeslaur> I gather the others simply haven't had time to look it over either
[16:15] <infinity> I've not given it a ton of thought yet, but it's in the back of my mind.
[16:15] <stgraber> my feeling is that this doesn't really need TB input
[16:16] <infinity> Well, it does if the ultimate plan results in a post-release update to a new version.
[16:16] <teward> stgraber: the only reason I say otherwise is that Daviey of the Release Team suggested it shoudl be elevated to TB
[16:16] <stgraber> what version to get into wily as we're not in any kind of freeze is basically up to the server team, if the intend is to get the stable for next release, then doing the same thing as openstack would be appropriate.
[16:16] <stgraber> that is, package the rc releases during the X cycle
[16:16] <stgraber> then get a FFe if those do somehow include new features
[16:17] <stgraber> and as soon as final is released, upload it either to the dev release (if not released yet) or as an SRU
[16:17] <stgraber> since going from rc to final isn't an actual major version bump and is supposed to be bugfix only, the existing process does cover that nicely
[16:17] <rbasak> The difference is that upstream doesn't really do the same sort of RC as openstack. If you consider their "mainline" to be the RC for their "stable", which is what we're doing, then there's still no upstream "feature freeze" between the two.
[16:17] <teward> ^ that
[16:17] <teward> (i was ninja'd)
[16:18] <rbasak> It's not guaranteed to be bugfix only.
[16:18] <rbasak> But we still think it's the best option available to us.
[16:18] <stgraber> hmm, so they don't fork mainline to stable a bit ahead of the stable release?
[16:18] <teward> stgraber: no, they do not, their 1.10.x stable release will be cut from the final state of 1.9.x at cut time
[16:18] <teward> no pre-releases
[16:19] <teward> (as 1.9.x versions in mainline are considered stable enough for production use, they don't have a pre-1.10.x release/cut)
[16:19] <teward> that is, the tagged 1.9.x versions in the upstream repository.
[16:19] <infinity> teward: Is there any guaranteed roadmap from upstream that 1.10 will come out when you think it will?
[16:19] <stgraber> ok, so yeah, consider 1.9.x as the rc then, if you keep it updated regularly, the delta at the end should be minimal and may not even need a FFe, if there are new features then a FFe would be needed from the release team
[16:20] <rbasak> stgraber: so even if the final 1.10 arrives post-release, you still consider a release team FFe acceptable for a subsequent 1.10 SRU?
[16:20] <teward> infinity: only the assurances of our contact, the Senior Developer Advocate at nginx.  A better roadmap for 1.10.x release date will likely be available closer to the end of this year, however they always cut stable from mainline in April
[16:20] <teward> exactly *when* in april appears to be slightly variable
[16:20] <stgraber> if the final 1.10 is tagged after X releases and the delta between the 1.9.x shipped in X and the upstream 1.10 does contain new features, then the SRU team will likely ask you to come to the TB
[16:21] <teward> stgraber: given that it's possible it will be that way, as the actual cut date for 1.10.x is not yet in stone, that's probably why Daviey suggested we elevate to the TB via a parallel discussion thread
[16:21] <rbasak> stgraber: that's my understanding, and that's what we'd like to have an exception for. We want a decision to be made now, since otherwise we don't think it makes sense to move to 1.9 in Wily now.
[16:21] <infinity> Given when we intend to release 16.04, the odds of 1.9.x in mid-April and 1.10 in late April being much different seem slim.
[16:22] <stgraber> rbasak: well, you'll understand that I won't give you an exception for code that doesn't exist yet :)
[16:22] <teward> infinity: that's the general idea, yes.
[16:22] <rbasak> stgraber: if an FFe or SRU were denied in the future, we'd be stuck shipping a dead and upstream unsupported 1.9 (or 1.8).
[16:22] <infinity> teward: Have you been involved in previous stable releases upstream?  Do you know how much junk goes into mainline while they're winding down to a release?
[16:22] <rbasak> stgraber: we think that would be useless to Ubuntu nginx users
[16:23] <mdeslaur> well, wily is only supported for 8 months anyway...
[16:23] <teward> infinity: I have not been involved upstream, however judging from the traffic on the devel list and commits at the end of 1.7.x before the 1.8.x cut it was mostly bugfixes between the last 1.7.x release and the first 1.8.x release
[16:23] <infinity> mdeslaur: Yes, but they don't want to have to revert from 1.9 to 1.8 between W and X.
[16:23] <infinity> mdeslaur: Wily being 1.9 is fine, X being 1.9 isn't.
[16:23] <rbasak> Right.
[16:24] <rbasak> And X being 1.8 is maybe better, but still will probably be considered old and generally useless in X.
[16:24] <mdeslaur> oh, sorry, april, got it now
[16:24] <infinity> teward: Right, if that's their usual MO, sort of a soft freeze while attempting to cut a stable, then I think I'm okay with saying "yes, ship 1.9 and push 1.10 as soon as it's ready", but with a caveat of "please keep 1.9 as up to date as reasonable during the last couple of months of the cycle, so the final delta is tiny and reviewable".
[16:24] <mdeslaur> as I said, I didn't have time to read over the proposal
[16:24] <rbasak> So we'd rather ship 1.10 in X so that the nginx package is relevant to users during X's lifetime.
[16:25] <teward> infinity: that echos my proposed course of action
[16:25] <rbasak> (s/ship/bump post-release/ if you like)
[16:26] <teward> infinity: which is assuming the TB accepts the course of action, merge 1.9.x from Debian throughout Wily, and do the same through X, mirroring Debian and likely some manual packaging if Debian has any freezes in between now and 1.10.x.
[16:26] <teward> s/1.10.x/1.9.x final/
[16:26] <teward> and then depending on the 1.10.x cut date, it either gets in pre-X release or post-X release as rbasak has said
[16:26] <mdeslaur> I think getting in the latest 1.9.x versions and then updating to 1.10.x post-release sounds like the sane thing to do for an LTS
[16:27] <infinity> teward: Unless the Debian maintainers upload a LOT, I'd take that one step further and say you want to keep uploading 1.9 snapshots after FF to make sure all the upstream bits are being tested before release and, again, to keep that final 1.10 delta low.
[16:27] <mdeslaur> as long as it's in the release notes, and happens before 16.04.1
[16:27] <teward> infinity: Correct, that's the proposed course of action
[16:27] <teward> infinity: although Debian tries to stay on top of 1.9.x when they do follow the mainline releases
[16:27] <infinity> teward: Alright, then a +1 from me on that.
[16:28] <rbasak> So you're proposing to effectively an FFe and a post-release SRU subject to these conditions?
[16:28] <infinity> rbasak: Yeah.  I mean, as stgraber says, it's hard to decide on code that doesn't exist yet, but I also get why you need to plan this so far in advance.
[16:29] <infinity> rbasak: So, I'd say "yeah, this sounds sane", but if features land post-FF that do look super scary, we're going to want solid test plans other than "yeah, it built" to make sure this won't bite us.
[16:29] <rbasak> infinity: I just want to clarify what action to take when we're ready to upload. Just upload if it's sane (including features after FFe), or get/expect review from release team or TB before upload?
[16:30] <rbasak> (after X FFe I mean)
[16:30] <teward> infinity: a decent gauge would be to track any bugs/issues that come up on the Mainline PPA, as I know people use that, and that's already keeping up to date as possible with nginx upstream releases (give or take a week right now due to some undue stress of last week preventing me uploading there)
[16:30] <infinity> rbasak: I think if it warrants an FFe (which isn't "new version" as people think, but "new features" or, "complete rewrites of existing features"), then file an FFe, but refer back to this discussion/decision.
[16:31] <stgraber> when you get to FF, get a FFe for the next upstream snapshots including 1.10. If 1.10 is tagged before release, yay, if not, then you'll need a chat with the SRU team
[16:31] <rbasak> OK, that's clear. Thanks.
[16:31] <infinity> rbasak: The TB certainly has the power here to pre-approve, but I'd rather do it conditionally on the "well, if it needs an FFe, that means you need to prove it works".
[16:32] <teward> I'll keep an eye on the changelogs as they come out as well, nginx is usually very adamant on identifying what's a bugfix or a feature change, etc. on the changelogs
[16:33] <teward> which can be used to determine if an FFe is needed or not there.
[16:33] <infinity> teward: Keep an eye on diff size.  If a new upload has a 500k diff (that isn't all in testsuite code), there's a fair chance that even if there wasn't a new "feature", someone went and rewrote a subsystem in the name of a bugfix, and you want to pay special attention to what that might have broken and test it.
[16:33] <teward> correct.
[16:34] <teward> I usually have to track that anyways, upstream changes have sometimes prompted news entries in Debian which in turn require me to make a note about that, usually on my blog, cross-linked over my twitter
[16:34] <teward> (due to substantial changes or such)
[16:34] <infinity> Alright.  I feel like, despite this being a thing one of us could JFDI a decision on, perhaps this warrants a vote for peace of mind for the server team?
[16:36] <rbasak> Yes please. It sounds like you've basically approved our plan but want a manual release team review step on FFe upload and SRU team review step on SRU upload.
[16:36] <rbasak> (at which point you could nak if you see insanity)
[16:36] <infinity> stgraber: Something like "Pre-approve potential FFe and one-time (possible) post-release version bump exception for nginx 1.9/1.10 in 16.04, conditional on acceptable review and testing being done?"
[16:38] <infinity> Assuming the chair is still awake.
[16:38] <stgraber> #vote Approve plan to go with nginx 1.10 in 16.04 with final upload potentially post-release. Pre-approve FFes required to keep 16.04 close to final 1.10 pre-release and one-time version bump post-release if needed. Conditional on standard review and testing.
[16:38] <meetingology> Please vote on: Approve plan to go with nginx 1.10 in 16.04 with final upload potentially post-release. Pre-approve FFes required to keep 16.04 close to final 1.10 pre-release and one-time version bump post-release if needed. Conditional on standard review and testing.
[16:38] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[16:38] <stgraber> sorry, was typing :)
[16:38] <infinity> +1
[16:38] <meetingology> +1 received from infinity
[16:38] <mdeslaur> +1
[16:38] <meetingology> +1 received from mdeslaur
[16:38] <stgraber> +1
[16:38] <meetingology> +1 received from stgraber
[16:39] <slangasek> +1
[16:39] <meetingology> +1 received from slangasek
[16:39] <infinity> I think the 1s have it.
[16:40] <stgraber> yup
[16:40] <stgraber> #endvote
[16:40] <meetingology> Voting ended on: Approve plan to go with nginx 1.10 in 16.04 with final upload potentially post-release. Pre-approve FFes required to keep 16.04 close to final 1.10 pre-release and one-time version bump post-release if needed. Conditional on standard review and testing.
[16:40] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[16:40] <meetingology> Motion carried
[16:40] <rbasak> Thanks!
[16:40] <teward> Thank you very much for looking at this!
[16:40] <stgraber> #topic Check up on community bugs (standing item)
[16:40] <stgraber> nothing, as usual
[16:40] <infinity> teward: In the name of us all being super lazy^wbusy people, care to follow up to your own thread with a pointer to the IRC log, so we can easily refer back later?
[16:41] <stgraber> #topic Select a chair for the next meeting (next from https://launchpad.net/~techboard/+members)
[16:41] <stgraber> that would be infinity
[16:41] <infinity> Then kees, yes.
[16:41] <teward> infinity: i will be glad to follow up to that thread and point to the IRC logs here for the vote on this, yes.
[16:41] <stgraber> #topic AOB
[16:42] <infinity> teward: http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2015/ubuntu-meeting-2.2015-07-21-16.02.log.txt
[16:42] <rbasak> o/
[16:42] <rbasak> I had one AOB
[16:42] <teward> infinity: ack, thanks.
[16:42] <infinity> Which is disturbingly up to date.  It must have just ran the job...
[16:42] <teward> infinity: very possible :)
[16:42] <rbasak> I noted that fridge.ubuntu.com doesn't list the TB meeting any more, so I find it quite hard to find the schedule
[16:42] <rbasak> (before the minutes are updated)
[16:42] <rbasak> Would someone please add it?
[16:43] <rbasak> (unless I'm missing something)
[16:45] <infinity> rbasak: It does indeed seem to not be there anymore.  Weird.
[16:45] <rbasak> I would have JFDI but I didn't want to presume your schedule. I _think_ it's every two weeks?
[16:45] <slangasek> it is
[16:45] <infinity> It is.  For now.  We've been discussing maybe changing that.
[16:46] <rbasak> Then I'll JFDI if you like.
[16:46] <rbasak> But please remember to change it if your schedule changes.
[16:46] <infinity> Well, we already have a meeting.
[16:46] <infinity> Since it notifies me every two weeks.
[16:46] <infinity> We probably just need to invite the fridge.
[16:46] <rbasak> OK, I'll leave it to you then :)
[16:47] <infinity> Huh.  And the fridge *is* invited.  Even weirder.
[16:47] <infinity> Should look into that, I guess.
[16:48] <rbasak> "Under Add Guests, invite<EMAIL_ADDRESS>[16:48] <rbasak> From
[16:48] <rbasak> https://wiki.ubuntu.com/Fridge/Calendar
[16:48] <infinity> Yeah, I know.  I'm in the same place. :P
[16:48] <slangasek> maybe the fridge has a busy social life and has declined our invitation
[16:48] <infinity> It did decline, actually.
[16:48] <mdeslaur> we're not cool enough for the fridge
[16:49] <rbasak> It is cool in the fridge. You just need to be let in :-)
[16:51] <mdeslaur> rbasak: was that your AOB?
[16:51] <rbasak> Yes
[16:51] <mdeslaur> ok
[16:52] <stgraber> ok, sounds like we're done then
[16:52] <stgraber> #endmeeting
[16:52] <meetingology> Meeting ended Tue Jul 21 16:52:07 2015 UTC.
[16:52] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting-2/2015/ubuntu-meeting-2.2015-07-21-16.02.moin.txt
[16:52] <mdeslaur> thanks everyone!
[16:52] <rbasak> Thanks all!
[16:52] <teward> infinity: i'd like you to spot-check my wording, if you wouldn't mind, before I send this:  http://paste.ubuntu.com/11915402/  I'll add in the link as well, but before I send i'd like a sanity check
[16:53] <rbasak> teward: link to IRC logs please
[16:53] <rbasak> teward: otherwise lgtm
[16:53] <teward> rbasak: just said i'll ad it
[16:53]  * teward points at "I'll add in the link as well"
[16:53] <slangasek> thanks, all
[16:53] <infinity> teward: WFM.
[16:53] <rbasak> Oh, sorry.
[16:54] <infinity> rbasak: Fridge calendar happier now.
[16:54] <rbasak> \o/
[16:54] <rbasak> Thanks!
[16:54] <teward> infinity: rbasak: sending now, with the logs, and also the link to the meeting minutes that meetingology created so people don't absolutely have to go digging to find the vote :)
[16:56] <teward> thanks again to all of the TB :)


[01:31] <wgrant> cjwatson: Should I revert your pytz upgrade?
[07:19] <cjwatson> wgrant: I think so, haven't heard anything from stub as yet regarding my pytz fixes
[07:19] <stub> ?
[07:19] <cjwatson> 13:19 <cjwatson> stub: Would it be possible to get a new pytz release with https://code.launchpad.net/~cjwatson/pytz/smarter-utcoffset/+merge/245472 or similar soonish, or should I be looking to revert my Launchpad commit that upgraded to 2014.10?
[07:21] <stub> cjwatson: Is this https://bugs.launchpad.net/pytz/+bug/1319939 ?
[07:21] <mup> Bug #1319939: 2014.3 tz change in US/Central looks wrong <pytz:Opinion> <https://launchpad.net/bugs/1319939>
[07:25] <cjwatson> Hm, possibly related
[07:25] <cjwatson> Does that mean you think the LP test suite should just avoid exercising these cases?
[07:26] <cjwatson> (I didn't find that bug because Opinion.)
[07:28] <wgrant> Aha, hi.
[07:28] <wgrant> Welcome to the team.
[07:29] <cjwatson> Thanks :-)
[07:33] <wgrant> cjwatson: It looks like only that one test is broken because of it?
[07:33] <wgrant>     >>> sending_date = datetime(
[07:33] <wgrant>     ...     2008, 5, 20, 10, 5, 47, tzinfo=pytz.timezone('Europe/Prague'))
[07:33] <wgrant> evil!
[07:33] <wgrant> Easy fix :)
[07:33] <stub> cjwatson: You should avoid those cases, because using the 'latest' timezone may break too.
[07:34] <stub> cjwatson: Or better yet, fix things to correctly construct the localized datetime instances.
[07:34] <stub> I need to steel myself to write some C code, so I can get this all sorted in Python core :-P
[07:35] <stub> Unless I can find a volunteer
[07:36] <cjwatson> wgrant: There were two or three, I think.
[07:36] <stub> Ahh... there is the MP. In my 'reviews' folder, with 16k other unread emails. I think I need to improve those filters.
[07:36] <wgrant> cjwatson: The others all look like the AxxT short name changes.
[07:37] <cjwatson> Oh, no, you're right, it was just that one.
[07:37] <wgrant> (upstream was finally convinced to prepend "A" to all the Australian timezonse)
[07:37] <cjwatson> Yeah, already have a testfix branch for that.
[07:37] <wgrant> Which we've been wanting for well over a decade.
[07:37] <wgrant> Excellent.
[07:37] <cjwatson> OK, I'll soup it up to fix the bugnotification test too to avoid that
[07:37] <cjwatson> The default timezone __repr__ just seemed sufficiently bizarre that I thought that was going to need a fix :-)
[07:42] <wgrant> Heh, yeah...
[07:43] <wgrant> now really does seem like a better option, but perhaps that's an argument for why it shouldn't be the default.
[07:43] <wgrant> At least this makes the bug obvious.
[08:13] <cjwatson> wgrant: https://code.launchpad.net/~cjwatson/launchpad/testfix-pytz-2014.10/+merge/245547
[08:13] <wgrant> cjwatson: Yay
[08:13] <wgrant> Thanks.
[08:14] <cjwatson> Landing
[11:49] <cjwatson> wgrant: Do you have a bootstrap.py incantation handy that works in lazr.anything?
[11:49] <cjwatson> I keep getting variants of "pkg_resources.VersionConflict: (setuptools 0.6c11 (/tmp/tmpQjsW5z/setuptools-0.6c11-py2.7.egg), Requirement.parse('setuptools>=8.0'))", and my attempts to fix this aren't making things better ...
[11:52] <stub> Your only going to get a version of setuptools that recent via pip or buildout
[11:52] <wgrant> cjwatson: Where did you obtain that bootstrap.py, and how are you invoking it?
[11:52] <wgrant> There was also a setuptools debacle recently.
[11:52] <wgrant> Where they unreleased a version.
[11:53] <wgrant> Though that was setuptools 10.2, so not relevant.
[11:56] <cjwatson> wgrant: lazr.yourpkg
[11:56] <cjwatson> and "python bootstrap.py", after symlinking in download-cache and eggs per https://dev.launchpad.net/HackingLazrLibraries
[11:57] <cjwatson> (in a precise LXC instance)
[11:58] <cjwatson> actually, sorry, I replaced that bootstrap.py with http://downloads.buildout.org/1/bootstrap.py after previous problems ...
[11:58] <cjwatson> stub: yeah I don't actually want a newer setuptools and haven't asked for that; have not been able to puzzle out where that requirement is coming from
[11:58] <stub> I imagine one of the buildout dependencies is modern setuptools, so it needs to be installed before buildout (in the python venv, or package or pip I guess?)
[11:59] <cjwatson> wgrant: but lazr.restful (say) behaves this way if invoked via "python bootstrap.py" on precise
[12:00] <cjwatson> oh, here, "python bootstrap.py --setup-source=ez_setup.py --download-base=download-cache/dist --eggs=eggs --version=1.7.1" at least bootstraps ... what a mess
[12:01] <stub> That is a polite way of putting it
[12:01] <cjwatson> (but then bin/buildout fails)
[12:01] <wgrant> cjwatson: The incantation should be in the various makefiles of things that have been touched recently.
[12:04] <cjwatson> I don't suppose you have an example?  The only ones I can find that have a Makefile just have python bootstrap.py or python -S bootstrap.py.
[12:05] <cjwatson> And lazr.uri make fails in both precise and vivid.
[12:05] <wgrant> lazr.restful(client) should work.
[12:05] <wgrant> I think
[12:05] <wgrant> Let me see.
[12:05] <xnox> i have been removing bootstrap support and moving towards "normal" setuptools + python setup.py test
[12:06] <xnox> however there is a magical set of commands that do work with bootstrap/buildout
[12:06] <xnox> (none of them work with python3, and one needs to do bootstrap of the bootstrap utils first to make sure none of the system things (e.g. setuptools) are used)
[12:07] <xnox> sigh, my working rebootstrap script is in ~/bin/ on my laptop and not with me atm, so I can't share it with you.
[12:23] <cjwatson> Maybe I should just leave whatever broken bootstrap crap comes from lazr.yourpkg in place, ignore it, and just use setup.py directly.
[12:23] <cjwatson> But I kind of want to get versions.cfg right.
[12:27] <xnox> yes, versions.cfg is nice. but it's a pain to use/update at the moment. As most of versions listed there are obsoleted (e.g. much newer stuff is on pypi and in precis/trusty)
[12:28] <xnox> and it does not work in python3.
[12:28] <xnox> =/
[12:33] <cjwatson> Sure, but for something that will be imported into the main Launchpad tree I need to make sure that it's at least buildout-compatible.
[12:36] <wgrant> cjwatson: The versions.cfg in the lazr project is only relevant for development.
[12:37] <wgrant> Likewise any buildout or bootstrappery.
[12:37] <wgrant> Launchpad's buildout and versions.cfg are used when it's imported into LP
[12:38] <wgrant> xnox's approach is probably best, at least for simple cases like this.
[12:45] <xnox> cjwatson: wgrant: Happy New Year! =) all the awesomely best in this year ;-)
[12:46] <wgrant> xnox: Likewise! Hope you're doing well in your new role.
[12:48] <xnox> wgrant: i think so ;-)
[12:50] <wgrant> :)
[14:23] <cjwatson> OK, using a venv to run bootstrap.py and then using "bin/buildout buildout:install-from-cache=true buildout:download-cache=download-cache buildout:eggs-directory=eggs buildout:allow-picked-versions=false -v" appears to be working somewhat better
[16:31] <cjwatson> wgrant: Do you want to have a look over lp:lazr.sshserver before I call it 0.1?  I have an LP branch that uses it and passes the relevant tests.
[22:18] <wgrant> cjwatson: Were you able to reuse anything from lazr.yourpkg?
[22:57] <cjwatson> wgrant: Saved me figuring out the skeleton from scratch, I guess, and writing the basic generic docs
[22:57] <cjwatson> wgrant: I kept most of buildout.cfg too
[23:00] <wgrant> cjwatson: Sounds good. I'd split out poppy to make sure it's sufficiently reusable before releasing it, though.
[23:01] <cjwatson> Fair.
[23:02] <cjwatson> I'll grab that task and do it tomorrow.
[23:03] <wgrant> Thanks. The most non-trivial bit is probably the config.
[23:04] <wgrant> (txlongpoll was in a similar situation, and nowadays uses a yaml config file)
[23:09] <cjwatson> Yeah, that would make sense.  Its config isn't very complicated.
[23:10] <wgrant> It's also currently weird because it takes the path on the commandline, but the rest of the config in lazr.config.
[23:11] <cjwatson> wgrant: Used to; I don't think it does any more.
[23:12] <wgrant> Oh, true.
[23:30] <cjwatson> poppy will have to end up as lazr.poppy I guess, because
[23:30] <cjwatson> https://launchpad.net/poppy
[23:31] <elmo> pretty please rename it entirely?
[23:32] <elmo> it's one of the old katie style names
[23:32] <elmo> albeit less obvious than some
[23:32] <wgrant> Yeah, we always rename things when they're extracted.
[23:32] <wgrant> Or moved.
[23:32] <wgrant> If they had stupid names before.
[23:32] <cjwatson> Yeah, also fair.
[23:35] <cjwatson> lazr.uploadserver?  Bit generic but ftporsftpuploadserver is just no
[23:36] <wgrant> It is quite Debian-specific
[23:36] <elmo> anonymousdebianuploadserverbutcouldbeconceivablyusedforotherthings
[23:36] <wgrant> In that it has special behaviour on .changes files, etc.
[23:36] <cjwatson> Or maybe launchpad- since it's not really a reusable component in the lazr sense.
[23:36] <wgrant> I wouldn't call it lazr-, no.
[23:36] <wgrant> But it also won't be using any Launchpad-specific interfaces within a couple of months.
[23:37] <cjwatson> wgrant: changes> It does?  AFAIK its special behaviour is more about (S)FTP sessions.
[23:37] <elmo> heh, yeah, I stumbled across a bug from iwj complaining about that the other day
[23:37] <elmo> (suggesting it special case .changes instead)
[23:37] <elmo> 4 digit bug or something
[23:37] <wgrant> Huh, indeed.
[23:37] <cjwatson> Well, there's the distro detection thing
[23:38] <wgrant> The only special handling it has is for the .distro files, which are dreadfully obsolete anyway.
[23:38] <wgrant> I thought we deleted that code years ago...
[23:39] <wgrant> Oh, it used to have the .changes special case when it checked signatures.
[23:40] <cjwatson> Meh, will think about it tomorrow.


[08:46] <Laney> cjwatson: thanks for fixing cdimage/kylin for me
[09:32] <cjwatson> np
[12:37] <lool> Hey, would someone mind giving back the autopkgtests for network-manager on i386: https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-network-manager/lastBuild/?
[12:37] <lool> they failed only on i386, and I suspect it's just racy
[12:37] <lool> (passed on amd64)
[12:37] <cjwatson> sure, let me just switch VPN
[12:38] <cjwatson> I only know how to give them back on all arches
[12:38] <cjwatson> hopefully that'll do
[12:38] <Laney> was there an upload to fix it?
[12:38] <Laney> ubuntu-devel chatter earlier suggested it was a real failure
[12:39] <cjwatson> oh yes, indeed it did
[12:39] <cjwatson> lool: so no, see #ubuntu-devel scrollback
[12:42] <lool> ack, found the logs now; thanks
[15:26] <ogra_> stgraber, we might want to promote an rtm image today ... iirc there was something with empty target channels i will have to regard ?
[15:27] <stgraber> ogra_: can't think of any obvious problem with copying between 14.09-proposed and 14.09, let me know if something goes wrong
[15:27] <ogra_> (rtm never had a promotion before)
[15:27] <ogra_> stgraber, thanks, just wanted to make sure in advance
[17:45] <zul> can someone figure out whats going on with python-oslo.utils, it is in main but there is no debs when i look at the archive for it
[18:06] <slangasek> zul: rmadison shows that the binaries are all in universe, and http://people.canonical.com/~ubuntu-archive/component-mismatches.txt shows that there's nothing holding the source in main
[18:11] <zul> slangasek: yeah its a new dependency of keystone
[18:11] <zul> which currently ftbfs
[18:12] <slangasek> zul: well, so worry about fixing the ftbfs, and when that's fixed component-mismatches will tell us to DTRT
[18:12] <slangasek> until then, the source shouldn't have been promoted to main anyway, because now it just shows up on c-m going the wrong direction
[18:13] <zul> slangasek: erm https://launchpad.net/ubuntu/+source/keystone/1:2014.2~b3-0ubuntu1/+build/6330454
[18:30] <slangasek> zul: oh, well then
[18:30] <slangasek> zul: yes, http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.txt shows the correct info
[18:31] <slangasek> (and when do we get python3 openstack? :)
[18:31] <zul> slangasek: its being worked on :)
[19:06] <Laney> I just realised that making the huge wallpapers package native might not have been the best idea
[19:06] <Laney> will change that back soon. :-)
[20:16] <Noskcaj> Can someone please look at https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1330037
[20:28] <stgraber> Noskcaj: why would you want to SRU that?
[20:28] <Noskcaj> crap *FFe
[20:29]  * Noskcaj quietly walks away
[20:30] <Noskcaj> The only thing that isn't ready is ubuntu-system-settings, since it's patch needs a refresh


[07:38] <dholbach> good morning
[07:47] <MooDoo> hrllo all
[07:47] <MooDoo> morning
[07:48] <dholbach> hi MooDoo
[07:50] <MooDoo> Hi Daniel, are there plans for a first meeting?  or you waiting to get more members?
[07:52] <dholbach> MooDoo: we did a couple of meetings already
[07:53] <dholbach> MooDoo: czajkowski was planning the next meeting
[07:55]  * MooDoo ah sorry, was just looking at the wiki :)
[07:55]  * MooDoo puts glasses back on
[08:34] <czajkowski> it's updated on the wiki... https://wiki.ubuntu.com/NGO/Meeting
[08:34] <czajkowski> just not in the header as no idea why it's not pulling the info in
[08:40] <dholbach> czajkowski: fixed it - just need to update NGO/NextMeeting
[08:40] <dholbach> czajkowski: and it'll update both
[08:40] <czajkowski> ahhh ok
[08:41] <czajkowski> dholbach: *hugs* thank you
[08:41]  * dholbach hugs you back
[08:41]  * MooDoo waits for a hug too
[08:41] <MooDoo> :)
[13:09] <txwikinger> Morning folks
[13:09] <MooDoo> morning
[13:09] <txwikinger> hi MooDoo
[13:09] <MooDoo> howdy
[20:19] <HanifBaloch> i have problem with my gnome pppp
[20:30] <MooDoo> hello all


[18:08]  * enyc meows
[21:52] <LocutusOfBorg> ubuntu-archive: please move conserver from multiverse to universe?
[21:52] <LocutusOfBorg> the license is not clarified


[08:31] <davidcalle> dholbach: hey o/ I'm wary about upgrading swift/keystone right now, we know that the current stack works and that's a potential can of worm I don't think we should open this time, we already have enough on our plate : https://code.launchpad.net/~dholbach/developer-ubuntu-com/update-pip-components/+merge/280323
[08:31] <dholbach> good morning
[08:32] <dholbach> ok, wfm
[08:32] <dholbach> once we have cleared the pipe of landings, we can take a look at this again if we want
[08:32] <davidcalle> ok, acking then :) How are things?
[08:32] <davidcalle> +1
[08:32] <dholbach> good good - how about you? :)
[08:33] <dholbach> I might need an additional coffee or two today, the cat woke me up in the middle of the night... :)
[08:37] <davidcalle> dholbach, wait until the dog barks at the cat in the middle of the night, waking up one kid crying, that wakes up the other :p
[08:38] <dholbach> davidcalle: I wasn't exactly complaining about my situation :-)
[08:38]  * dholbach hugs davidcalle
[08:40] <davidcalle> dholbach: we should find a way to remove old deps in the dependencies branch, things that are not even used in django 1.6 anymore, it's getting pretty heavy to download :)
[08:40] <davidcalle> dholbach: I know, I know, just need to vent :p
[08:41] <dholbach> yes, I agree
[08:41] <dholbach> although with the branch we are going to have the problem that it will be heavy in any case
[08:41] <dholbach> maybe we should do a  push --overwrite  at some stage
[08:41] <dholbach> and rewrite it with empty history
[08:41] <dholbach> I don't see why we need the history of binary packages :)
[09:56] <dholbach> davidcalle: also very useful  manage.py test <app>.tests.<class>  (or <app>.tests.<class>.<method>) - that way you can iterate on tests more quickly
[09:56] <davidcalle> dholbach: thanks!
[14:58] <mhall119> davidcalle: did you see my ping yesterday about the js scopes doc package missing data.json?
[15:02] <davidcalle> Missed it. I remember specifically asking Alex to stop removing the file at build time, in a merge proposal comment. Let me check why it's still missing...
[15:03] <davidcalle> mhall119 ^
[15:06] <mhall119> davidcalle: thanks, I couldn't get very far testing without that
[15:18] <davidcalle> mhall119:  "make doc" on the project works fine. /me asks alex


[20:36] <emptythevoid> Just saw this in my RSS reader today.  Is it safe to expect that this patch will get backported to the version of Samba on 18.04 (4.7 series)? https://nakedsecurity.sophos.com/2022/07/27/critical-samba-bug-could-let-anyone-become-domain-admin-patch-now/amp/
[20:38] <mdeslaur> emptythevoid: it's unlikely to get backported to 18.04...if you are running AD on 18.04, you should update to a more recent version of Ubuntu
[20:38] <emptythevoid> Understood.  Thank you


[14:22] <xperia> persia: are you online ?
[14:23] <persia> I am.  You wanted to talk about packaging?
[14:23] <xperia> yes exactly. do you have any time now or should we make it other day ?
[14:24] <persia> I have some time.
[14:24] <persia> For me, the hardest part of packaging is documenting the authorship and licensing.
[14:25] <persia> And I recommend doing that first.  It's less frustrating to get stuck there before you do anything else, then after you have a nearly working product.
[14:25] <xperia> ohh great. i am ready. i have built everything allready on my host so it need only packaging.
[14:25] <xperia> okay then say me what do i need to have and execute
[14:25] <persia> For copyright, you'll want to go through *every* file in the source, and document the author, the copyright holder, and the license.
[14:26] <persia> These days, I tend to use http://dep.debian.net/deps/dep5/ as  a format for that document
[14:28] <xperia> persia. ihave allready a LICENSE.GPL file inside the sources
[14:28] <xperia>  The Qtopia Environment is Copyright (C) 2000-2001 Trolltech AS and
[14:28] <xperia>   other authors as specified in the file headers.
[14:28] <xperia>  You may use, distribute and copy the Qtopia Environment under the terms
[14:28] <xperia>  of GNU General Public License version 2, which is displayed below.
[14:28] <xperia> .....
[14:29] <persia> Understood.  You need to redocument it, to demonstrate that you've done the review as part of the packaging.
[14:29] <persia> If everything is truly licensed properly, and all under the same license, this can be very quick and easy.
[14:30] <xperia> okay then i will now install dep5 and start it
[14:30] <persia> Most of the time I find a few files that aren't documented properly, and need to go chase the authors to make sure the right license headers may be added, etc.
[14:30] <persia> Nothing to install.  It's just a text file.
[14:33] <xperia> exist some full example that i can modify only or do i need to read the whole site
[14:34] <persia> There are some examples on that page.
[14:34] <persia> But only that page should be sufficient, including examples.
[14:35] <xperia> persia: ahh okay i see it now at the end
[14:43] <xperia> persia: i have it now. http://paste-bin.com/view/f851b18d
[14:47] <persia> xperia: That was fast :)
[14:48] <persia> xperia: I'd recommend just listing yourself for debian/* so that you don't need to add file headers to each file.
[14:48] <persia> Also, You list copyright 2000-2001 : did you maybe mean 2000-2010?
[14:48] <xperia> it has to go forward :-) used the first example
[14:49] <persia> OK.  So, how does this build?
[14:50] <xperia> well it build great.
[14:50] <xperia> ./configure
[14:50] <xperia> make
[14:50] <xperia> works great
[14:50] <xperia> without any problems
[14:50] <xperia> maybe  need to specifiy some prefix-install folder now
[14:51] <persia> Unpack your source.
[14:51] <persia> make a directory debian/ in the source
[14:51] <xperia> okay will do
[14:52] <xperia> okay done
[14:53] <persia> copy the file you created from the DEP5 guide to debian/copyright
[14:53] <persia> Copy /usr/share/doc/debhelper/examples/rules.tiny to debian/rules
[14:53] <persia> echo 7 > debian/compat
[14:54] <persia> dch --create to start a changelog: add the package name, ${version}-0ppa1 (we'll start with a ppa, and can go from there), target lucid, urgency low, changelog entry "Initial Packaging"
[14:55] <xperia> is debian/copyright the folder or the file i have now debian/copyright/copyright
[14:55] <persia> Next create debian/control in a text editor: http://www.debian.org/doc/debian-policy/ch-controlfields.html documents the fields and relevant policies.
[14:55] <persia> debian/copyright should be the text file.
[14:59] <xperia> persia: what if i have allready a existing big ChangeLog file ? Do i need still to create a new one ?
[15:00] <persia> Yes.
[15:00] <persia> Basically you want to separate the changelog for the packaging from the changelog for the software.
[15:00] <persia> debian/changelog should only contain changes to how it's packaged.
[15:00] <persia> ./ChangeLog contains the changes to trunk, etc.
[15:01] <persia> When there's a new release of the software, just add "New upstream version" in debian/changelog.
[15:02] <persia> But most debian/changelog entries will end up being stuff like "Rebuild against new libfoo", "Adjusted udev rules to match new semantics", "Update to standards-version x.y.z", etc.
[15:02] <persia> (this is a luxury you will have because of your close relationship with upstream.  If the people writing the software and the people packaging the software are very different, more complex things may apepar in debian/changelog)
[15:04] <xperia> okay. wotking on creating the change log. with dch --create
[15:04] <xperia> does this changelog file need to be moved later to the debian folder
[15:04] <xperia> becouse i am outside of the debian folder all the time
[15:06] <persia> dch --create will automatically create it in the debian folder
[15:09] <xperia> Is this here corect writen this way in my console ?
[15:09] <xperia> PACKAGE opie, (VERSION)1.2.5-0ppa1 UNRELEASED; urgency=low target lucid
[15:09] <xperia>   * Initial Packaging. (Closes: #XXXXXX)
[15:09] <xperia>  -- administrator <administrator@localhost>  Fri, 19 Mar 2010 16:05:48 +0100
[15:10] <persia> Not quite.
[15:10] <xperia> or do i need
[15:10] <xperia> opie 1.2.5-0ppa1 urgency=low target=lucid
[15:11] <persia> You want the parentheses.
[15:11] <persia> And you can't use the name opie : it's been taken since before your project started.
[15:11] <persia> So you need to have a different package name.
[15:11] <xperia> ohh man how should i named it then. it exist allready a package from 2004 but dont know how it is called
[15:11] <persia> maybe "opi-env" ?
[15:12] <xperia> good tip. i will use opie-desktop as gnome-desktop or ubuntu-desktop
[15:13] <persia> That works,.
[15:13] <xperia> just need to know if i need to remove the Words like PACKAGE and so on
[15:14] <xperia> is this here needed
[15:14] <xperia> opie-desktop 1.2.5-0ppa1 urgency=low target=lucid
[15:14] <persia> You want something like:
[15:14] <xperia> or this here
[15:14] <xperia> PACKAGE opie-desktop (VERSION)1.2.5-0ppa1 UNRELEASED; urgency=low target=lucid
[15:15] <persia> opie-desktop (1.2.5-0ppa1) lucid; urgency=low
[15:17] <xperia> awesome have done it :-)
[15:17] <xperia> cat debian/changelog
[15:17] <xperia> opie-desktop 1.2.5-0ppa1 lucid; urgency=low
[15:17] <xperia>   * Initial Packaging. (Closes: #XXXXXX)
[15:17] <xperia>  -- administrator <administrator@localhost>  Fri, 19 Mar 2010 16:05:48 +0100
[15:17] <persia> Well, fix your name and email :)
[15:18] <persia> You need those to match an identity from `gpg --list-secret-keys`
[15:20] <xperia> okay great ! thanks for the Tip.
[15:20] <xperia> will change that direct now
[15:22] <xperia> have change it: http://paste-bin.com/view/305b942d
[15:22] <xperia> now on to creating this control file
[15:23] <persia> This is the most manual part after copyright, but if you just follow down the page in the debian policy manual, there's a good chance you'll end up with something mostly right.
[15:24] <xperia> hmmm this is a litlle more tricky now :-) cant find any examples at first sight
[15:25] <persia> Aside from Description, it's mostly just key-value entries, in RFC822 format.
[15:25] <persia> So:
[15:25] <persia> Source: opie-desktop
[15:25] <persia> Maintainer: ${name & email from changelog}
[15:25] <persia> Section: ${pick one}
[15:26] <xperia> ahh great thanks
[15:26] <persia> Priority: optional
[15:26] <persia> ...
[15:26] <persia> Put a blank line between the source paragraph and any additional paragraphs.
[15:26] <persia> And read the docs on Description closely: there's a very specific format
[15:31] <xperia> what should i write for
[15:31] <xperia> Architecture
[15:31] <xperia> the package build great on a i386
[15:31] <xperia> it should work too on a arm or other arch
[15:31] <xperia> the main goal is having it for arm
[15:32] <xperia> but also for i386
[15:32] <persia> any works
[15:33] <persia> That will try to compile for each available architecture separatly.
[15:35] <xperia> okay
[15:38] <xperia> persia: have done it
[15:38] <xperia> http://paste-bin.com/view/bc526299
[15:40] <persia> Almost.
[15:40] <persia> You need to start with Source:
[15:40] <persia> Package: belongs inthe second paragraph.
[15:40] <persia> Both Source: and Package: should be opie-desktop
[15:40] <persia> That's the name being assigned, not that actual source.
[15:40] <persia> Version: doesn't belong there
[15:41] <persia> section, priority, maintainer, homepage belong in the Source: paragraph.
[15:41] <persia> Architecture & Description belong in the Package: paragraph.
[15:41] <persia> The order should ideally be that shown on the policy page.
[15:41] <xperia> hmmm i have study the section 5.3 :-) and it looks like i needed to look at section 5.2
[15:42] <persia> heh
[15:48] <xperia> persia: i think i have understand it now. http://paste-bin.com/view/f1d96cc0
[15:49] <persia> Section, Priority, and Homepage are preferred in the first paragraph instead of the second, if they can go there.
[15:49] <persia> So delete them from the second paragraph (no need for duplication)
[15:50] <xperia> oky have done it. the control file should be done now if i am not wrong
[15:50] <persia> Not quite.
[15:51] <persia> You'll want to add Build-Depends to the first paragraph, and Depends to the second.
[15:51] <persia> Depends: is probably just:
[15:51] <persia> Depends: ${shlibs:Depends}, ${misc:Depends}
[15:51] <persia> Build-Depends needs to come from you, but should start with "debhelper (>= 7)"
[15:52] <xperia> ohhhhh that is now a step more heavy
[15:52] <xperia> can i write the line Depends: ${shlibs:Depends}, ${misc:Depends}
[15:53] <xperia> exact the same way in the control file or do i need to specify exactly what for packages are needed
[15:53] <persia> For Depends: you can start with the exact same way.
[15:54] <xperia> okay
[15:54] <persia> With Build-Depends, you'll need to add all the -dev libraries you need to build.
[15:57] <xperia> okay i think that should be very easy
[15:57] <xperia> all the dev-libs that i need are written here http://opie.handhelds.org/cgi-bin/moin.cgi/BuildOpie
[15:58] <persia> Right.
[15:59] <persia> Add all the required ones and all the optional ones.
[16:01] <xperia> Build-Depends: debhelper (>= 7), libfreetype6-dev, libjpeg62-dev, libpam0g-dev, libpng12-dev, zlib1g-dev, libasound2-dev, libsysfs-dev, libpcsclite-dev, pkg-config, libbluetooth-dev, libobexftp0-dev, libopenobex1-dev, libpcap-dev, libsqlite3-dev, libxine-dev
[16:01] <xperia> is that good from thy syntax point of view ?
[16:03] <persia> Yep.
[16:03] <persia> So let's see the entire control file, all assembled.
[16:04] <xperia> okay http://paste-bin.com/view/1d24b0be
[16:05] <persia> Ideally the order of the various entries should match the order in which they are presented in policy
[16:05] <persia> Other than that, looks pretty good.
[16:05] <persia> Oh, and Description needs changing.
[16:05] <persia> Go read policy about Description again.
[16:06] <xperia> okay changed the order and look now at Description
[16:09] <xperia> so what does i need to change in the description field.
[16:09] <xperia> do i need to encapsle the lines with < >
[16:09] <xperia> or o i need to make more than one space between the first and the second  Text Phrase ?
[16:12] <persia> xperia: After Description: you want a single line synopsis.  This should complete the cloze "${PACKAGE} is (a/the) ${SHORT_DESCRIPTION}".
[16:12] <persia> Below that line you should have at least three lines going into detail about the package, each proceeded by a single space.
[16:13] <persia> see policy 5.6.13 and 3.4
[16:16] <xperia> ohh this rules drives me crazy. how about his now ?
[16:16] <xperia> http://paste-bin.com/view/44d042f9
[16:17] <persia> Try to keep each line of the description under 70 characters :)
[16:17] <persia> But that's the last edit for now.
[16:17] <persia> So, now you're ready to build a source package.
[16:18] <xperia> ohhhh cant beleve it. need to shorten this lines
[16:18] <persia> Do you have a release tarball of opie that you unpacked when you started?
[16:18] <persia> Just description.  Leave build-depends alone for now
[16:18] <xperia> wait wait need to shorten the description lines
[16:19] <xperia> okay done.
[16:19] <xperia> no i have builded from trunk. it is very stable
[16:20] <xperia> the rlease version is a litlle old and dont has the newest changes
[16:21] <xperia> i have followed step by step this howto. it is very easy and and works great.
[16:21] <xperia> http://opie.handhelds.org/cgi-bin/moin.cgi/BuildOpie
[16:22] <persia> Well, that's a little frustrating, because it makes it a bit messy, but we can try to work around that.
[16:22] <persia> Grab the release tarball anyway.
[16:26] <xperia> are you sure ? the release is heavy outdated
[16:26] <xperia> http://opie.handhelds.org/cgi-bin/moin.cgi/Source
[16:26] <xperia> i have worked only as described on the page with this
[16:26] <xperia> git clone git://gitorious.org/opie/opie.git
[16:26] <xperia> if i am not wrong it should exist a snapshot of this git tree as tarball
[16:27] <persia> Well, we need a tarball.
[16:27] <persia> So we can make a tarball of the snapshot *or* we can use the old tarball.
[16:27] <persia> We'll use the snapshot source in either case.
[16:27] <xperia> let me find it http://gitorious.org/opie/opie
[16:28] <xperia> http://gitorious.org/opie/opie/archive-tarball/master
[16:28] <xperia> this should it be
[16:28] <xperia> http://gitorious.org/opie/opie/trees/master
[16:29] <xperia> okay i have the .tar.gz
[16:29] <xperia> should i extaract it or just save it
[16:30] <persia> Just save it.
[16:30] <persia> What version is the tar.gz ?
[16:31] <xperia> the newest 1.2.5 (trunk)
[16:32] <xperia> it is named opie-opie-master.tar.gz
[16:32] <persia> OK.
[16:32] <persia> Rename that to opie-desktop_1.2.5.orig.tar.gz
[16:33] <xperia> does it need to be copyed to debian/
[16:34] <persia> Nope.  It needs to be in the directory above the source.
[16:36] <xperia> okay have done the renaming
[16:38] <persia> OK.  Now, add a changelog entry
[16:38] <persia> (just run dch)
[16:38] <persia> Report that you updated to a git snapshot with today's date and the SHA hash
[16:41] <xperia> well have done dch but for some reasn i am getting this
[16:41] <xperia> http://paste-bin.com/view/f1724819
[16:42] <persia> Somehow debian/changelog got messed up.
[16:42] <persia> Delete it, and recreate it.
[16:42] <persia> Oh, I see.
[16:42] <persia> You missed the () around the version.
[16:45] <xperia> persia: you are right. the problem was the missings ()
[16:45] <xperia> okay it works now reporting the change in the changelog
[16:46] <persia> Excellent.  paste your new modified changelog?
[16:48] <xperia> need only to add the SHA hash number. is that the SHA Hash number from the gitorious page or should i create a new one ?
[16:49] <persia> You want the hash from the git tree so others can replicate your work.
[16:49] <persia> I believe that date + SHA hash identifies a unique state of source.
[16:56] <xperia> okay have done it
[16:57] <persia> OK.  So paste the debian/changelog
[16:57] <xperia> http://paste-bin.com/view/c40a7231
[16:58] <persia> I usually delete the [NAME] stuff when it's just me, but doesn't matter for now.
[16:58] <xperia> okay
[16:58] <persia> Next, run `debuild -S -i -I `
[16:58] <persia> This *should* build you a source package.
[16:58] <persia> If it doesn't, we'll hunt down the errors.
[16:58] <xperia> okay now it is getting interessting :-)
[16:59] <xperia> debuild: fatal error at line 685:
[16:59] <xperia> found debian/changelog in directory
[16:59] <xperia>   /media/usbdisk/LinuXperiaOS/opiehome/opie
[16:59] <xperia> but there's no debian/rules there!  Are you in the source code tree?
[16:59] <persia> Did you copy /usr/share/doc/debhelper/examples/rules.tiny to debian/rules ?
[17:00] <xperia> ohh i have rules.tiny
[17:00] <xperia> okay it works :-)
[17:01] <persia> So you have a diff.gz and .dsc?
[17:02] <xperia> dpkg-source: info: building opie-desktop using existing opie-desktop_1.2.5.orig.tar.gz
[17:02] <xperia> it is working at this line here at the moment
[17:02] <persia> That'll take a while.  It's preparing a diff between the git snapshot and the tarball
[17:03] <xperia> ahhh okay. in my case this will sure go abaout 30 min as i have a slow build host
[17:04] <xperia> persia: in this case i recomend to meet us in 30 min again here. till then we make a litlle break
[17:05] <persia> heh
[17:05] <xperia> :-)
[17:05] <xperia> this will sure need some 30 min :-)
[17:05] <xperia> ahh no it proceed :-)
[17:06] <xperia> ohhh that dont look gooog :-)
[17:06] <xperia> good
[17:07] <persia> What happened?
[17:07] <xperia> have a lot of this lines here
[17:07] <xperia> dpkg-source: error: cannot represent change to opie/core/launcher/.obj/x86-linux/moc_qprocess.o: binary file contents changed
[17:07] <xperia> dpkg-source: error: cannot represent change to opie/core/launcher/.obj/x86-linux/moc_mediumwidget.o: binary file contents changed
[17:07] <xperia> dpkg-source: error: cannot represent change to opie/core/launcher/.obj/x86-linux/moc_mediadlg.o: binary file contents changed
[17:07] <xperia> dpkg-source: error: cannot represent change to opie/core/multimedia/opieplayer/modplug/.obj/x86-linux/tables.o: binary file contents changed
[17:07] <xperia> dpkg-source: error: cannot represent change to opie/core/multimedia/opieplayer/modplug/.obj/x86-linux/memfile.o: binary file contents changed
[17:08] <xperia> it works still
[17:08] <persia> No, it doesn't.
[17:08] <persia> Did you run any build commands in that source before we started?
[17:08] <xperia> really ? what si wrong
[17:08] <xperia> well yes :-) wanted to know if it builds
[17:09] <persia> OK.
[17:09] <persia> Well, that's the issue.
[17:09] <persia> SO
[17:09] <xperia> did not wanted to have some strange surprises
[17:09] <persia> Make a new directory.
[17:09] <xperia> okay
[17:09] <persia> get your snapshot
[17:09] <persia> copy the entire contents of the debian/ directory we constructed in there.
[17:09] <persia> Put the orig.tar.gz one level down.
[17:10] <persia> run `dbuild -S -i -I` again.
[17:10] <persia> (in the new directory)
[17:10] <persia> You need the tree *before* it's built.
[17:13] <xperia> so okay i have created now in /media/usbdisk/opiehome the dir "debian-packager"
[17:13] <xperia> will now clone the git sources there with git clone git://gitorious.org/opie/opie.git
[17:14] <xperia> copy the debian folder from previous
[17:14] <xperia> and look that the snapshot file opie-desktop_1.2.5.orig.tar.gz
[17:14] <xperia> is located in /media/usbdisk/opiehome
[17:17] <persia> Right.
[17:17] <persia> And then build the source package.
[17:25] <xperia> persia: the thing is that the extracted sources need some symlinking to other files and packages
[17:25] <xperia> http://opie.handhelds.org/cgi-bin/moin.cgi/BuildOpie#head-263fce4b2279b68f6de230fff90c8d725add4c0f
[17:25] <xperia> how can this be solved so it can be done automagicly
[17:26] <persia> Do you need these to build, or to run?
[17:27] <xperia> uic compiler is needed to compile opie
[17:28] <xperia> and qfvb is needed for runnning
[17:28] <persia> Then you first need to package the uic compiler.
[17:28] <persia> And qfvb
[17:28] <persia> (unless they are already packaged)
[17:28] <xperia> ahhh dont we have them allready in the package repo. let me see if they exist
[17:31] <xperia> persia: uic-qt2 dont looks like it is in the repo but it can be find precompiled here
[17:31] <xperia> http://linuxtogo.org/~mickeyl/tools/
[17:32] <persia> You need to have it compiled in the repo, not use precompiled sources.
[17:32] <persia> The same recipe we used for opie-desktop can be used for that.
[17:33] <xperia> ohhh okay
[17:33] <persia> Note that this recipe produces buggy packages (but a buggy package can be debugged, and a non-existent package can't be)
[17:34] <xperia> okay i understand. in this case i will start now to create two dirs for creating the needed packages.
[17:34] <xperia> need some 20 to 40 minutes
[17:35] <persia> No worries.  I think you'll end up needing a bunch of time over 2-3 weeks, as a rough estimate.
[17:36] <xperia> ohhhh nooooo
[17:36] <persia> ?
[17:36] <xperia> such long :-)
[17:38] <persia> Well, making a package takes 20 minutes.
[17:38] <persia> Then it's buggy.
[17:38] <persia> So you have to fix the bugs.
[17:39] <persia> You're proposing to package a compiler, which tends to have odd, hard to track down issues, a virtual framebuffer, which ends up being all sorts of odd to configure and use, *and* a comprehensive integrated suite of applications.
[17:39] <persia> So I'm expecting you'll run into a lot of issues along the way.
[17:49] <xperia> mmmmhhhh okay in this case i will look to try first to package the uic compiler and the virtual frambuffer.
[17:49] <xperia>  have thinked it should be more easy to package opie as it nearly compile for every architecture from the sources in open embedded
[17:50] <xperia> maybe have to look also how the whole thing with compiling works in open embedded. i know 100% that it fetch allways the newest sources from the git repo and compile it for the different archs. for the arm arch however if i am not wrong they use qemu
[17:52] <persia> qemu can also be used in Ubuntu.
[17:53] <persia> I think the difference is that Ubuntu requires everything to be packaged first, whereas OE provides a framework that supports a mix of packaged and unpackaged software.
[17:54] <xperia> the most easy thing in this case would be to look in open embedded how they compile uic and qtvfb. hmm let me just see it as i have it her on my usbdisk
[18:02] <xperia> hmmm open embedded has packages that are fully missed in ubuntu-mobile
[18:02] <xperia> xqt
[18:02] <xperia> xqt2
[18:02] <xperia> http://xqt.sourceforge.jp/
[18:03] <xperia> ohh man that looks like a lot of work :-(
[18:10] <xperia> persia: i will rethink the whole think with packaging opie for debian. it is way to high for me ! will probably stick with open embedded for the moment
[18:10] <persia> xperia: OK.  I understand.
[18:11] <xperia> thanks a lot for your very helpfull time. have learned somevery good stuff about what is needed for packaging.
[18:12] <persia> No problem.  At least I know it's a mountain of work next time someone asks me about packaging OPIE.
[18:13] <xperia> okay see you next time persia and a lot of success with ubuntu-mobile !
[18:13] <xperia> bye.


[07:47] <tax> how do you turn off autocomplete when bookmarking and typing in tags?
[18:12] <llwalahoop> Hello! I'm running Firefox on ubuntu 14.04. Where shall my bookmarks be stored?
[18:17] <gQuigs> you're profile is stored in .mozilla/firefox
[18:17] <gQuigs> then some name like q5kpy03j.default/
[18:18] <gQuigs> not sure where bookmarks are in there
[18:20] <llwalahoop> ok, gQuigs. I'll try to find something like that. I'm guessing it's in my home directory?
[18:21] <gQuigs> yup
[18:21] <gQuigs> it's hidden
[18:22] <llwalahoop> do you mean hidden with a dot in front?
[18:22] <gQuigs> yup
[18:23] <llwalahoop> ok, thanks!