Re: [MeeGo-dev] [Meego-qa] No scrub meeting for bugs assigned to triaget...@meego.bugs
On Mon, Aug 1, 2011 at 6:38 AM, Andre Klapper aklap...@openismus.com wrote: The proper fix probably would be to not allow queries embedded in MeeGo wiki pages to list Security tickets in Bugzilla. That's not the proper fix. The proper fix is to either fix the API, or fix the security bug reporting process so that less critical information is exposed by the bugzilla API for security bugs. For example http://bugs.meego.com/buglist.cgi?quicksearch=NielsMayerctype=csvcolumnlist=all will return a CSV of all my bugs and http://bugs.meego.com/buglist.cgi?quicksearch=NielsMayerctype=jscolumnlist=all will return the same as JSON formatted data. Although not containing the contents of potential security bugs, the API will expose the title, reporter, assignee, status, etc. This is one of the many issues I had to deal with over a decade ago when I hacked together Issuezilla for collabnet, against my will, but it was an emergency, the pie-in-the-sky bugtracker wasn't ready, and openoffice.org needed to launch... our system was somewhat different as bugzilla ran inside sourcecast using its authentication system; as it was also designed for use in private extranets with two-factor auth and x509 personal certs, there was a much more sophisticated way of gating private from public issues in Issuezilla. One of the examples I just got running for Qtzibit ( http://code.google.com/p/qtzibit ) is a mild modification of BugXhibit ( http://www.visophyte.org/blog/2009/05/28/bugxhibit-exhibit-on-bugzilla-results/ ) and makes use of the above API. Looks like: http://nielsmayer.com/meego/qml/bugxhibit.png http://nielsmayer.com/meego/qml/bugzhibit-timeline.png Feel free to try it yourself in your browser (or compile the app in qtcreator from qtzibit.pro)... the timeline sliders work pretty nicely on a touchscreen, although they can conflict with their flickable containers (thus the option of unchecking 'flickable' button in the examples). * svn checkout http://qtzibit.googlecode.com/svn/trunk/ qtzibit * firefox qtzibit/exhibit/src/webapp/examples/Bugxhibit/bugxhibit.html Or run it on your Nokia N950 or N9: * http://nielsmayer.com/meego/qml/qtzibit_0_0_3_armel.deb -- Niels http://nielsmayer.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] LF will not permit apps.meego.com : say hello to apps.formeego.org
cc'ed meego-dev as this may be of interest. Followup to meego-community please. Also cc'ed relevant forums. Over the past few weeks a few of us who have been involved in the MeeGo community infrastructure have been trying to solve a problem relating to MeeGo Apps : apps.meego.com After a few weeks when it became clear we could not resolve this problem we asked for a deadline when the LF would announce this restriction to the community. Eventually I proposed that the community start discussing this issue with or without an announcement from the LF on Tuesday 2nd August - and here we are. Last week I suggested that the following statement summed up my understanding and although I asked for an alternative, one did not appear: The Linux Foundation have told us in private conversations that they will not permit apps.meego.com to be served from the MeeGo.com infrastructure hosted by them. They do not have the resource at this time to provide a statement giving their reasons. We can not assess what other services may be impacted in the future. Ibrahim, if you have anything to add we would be grateful. I have tried to present a factual problem statement and some options at : http://wiki.meego.com/MeeGo_Apps/Problem_Statement Obviously, since we don't know what the problem is, it is hard to work out a solution - but I have proposed some options. In the meantime we have moved ahead to provide apps.formeego.org (thanks to Thomas for acquiring that domain - see https://bugs.meego.com/show_bug.cgi?id=20531). There are plans being worked on to setup infrastructure to host apps there - the community needs to decide how to manage that infrastructure and domain. On a personal note I am very disappointed by the Linux Foundation's response to this situation. There has been no open discussion, the verbal reasons provided were vague (although, I must emphasise, I am not doubting that there are valid concerns given the nature of the legal framework in the US) and insufficient effort has been made to assist the community in resolving (or even understanding) this problem - as I mention, since we're not clear about what the reason is we have no idea what other services may be impacted. David Forum Links: http://forum.meego.com/showthread.php?p=27975#post27975 http://talk.maemo.org/showthread.php?p=1062657 -- Don't worry, you'll be fine; I saw it work in a cartoon once... ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Meego-qa] No scrub meeting for bugs assigned to triaget...@meego.bugs
On Mon, 2011-08-01 at 23:27 -0700, Niels Mayer wrote: On Mon, Aug 1, 2011 at 6:38 AM, Andre Klapper aklap...@openismus.com wrote: The proper fix probably would be to not allow queries embedded in MeeGo wiki pages to list Security tickets in Bugzilla. That's not the proper fix. The proper fix is to either fix the API, or fix the security bug reporting process so that less critical information is exposed by the bugzilla API for security bugs. True (and thanks for elaborating). Could you file a report against bugs.meego.com in bugs.meego.com? andre ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [Meego-qa] No scrub meeting for bugs assigned to triaget...@meego.bugs
-Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Andre Klapper Sent: Monday, August 01, 2011 9:39 PM To: Ware, Ryan R Security bugs are private for a reason. See http://lists.meego.com/pipermail/meego-qa/2011-July/002109.html (which remained unanswered). The proper fix probably would be to not allow queries embedded in MeeGo wiki pages to list Security tickets in Bugzilla. Yeah, that's right, agree with Andre, we have to find a approach to get this issue fixed, or we will always facing a potential risk of unintended leaking info of security bugs. andre -- Andre Klapper (maemo.org bugmaster | MeeGo QA) http://blogs.gnome.org/aklapper/ | http://www.openismus.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] LF will not permit apps.meego.com : say hello to apps.formeego.org
On Tue, Aug 2, 2011 at 9:44 AM, David Greaves da...@dgreaves.com wrote: cc'ed meego-dev as this may be of interest. Followup to meego-community please. Over the past few weeks a few of us who have been involved in the MeeGo community infrastructure have been trying to solve a problem relating to MeeGo Apps : apps.meego.com Thanks David for bring this important issue to the community's attention. I'm certain the community can solve this issue more quickly and effectively than the LF. The Linux Foundation have told us in private conversations that they will not permit apps.meego.com to be served from the MeeGo.com infrastructure hosted by them. They do not have the resource at this time to provide a statement giving their reasons. We can not assess what other services may be impacted in the future. This type of behavior is fundamentally anti-community. This shows the Linux Foundation's complete disinterest in users and developers, they're beholden to the corporate sponsors and donors who pay their bills. In the meantime we have moved ahead to provide apps.formeego.org (thanks to Thomas for acquiring that domain - see https://bugs.meego.com/show_bug.cgi?id=20531). There are plans being worked on to setup infrastructure to host apps there - the community needs to decide how to manage that infrastructure and domain. Shouldn't the same folks who do the Maemo forums and garage be involved? They have experience in this sort of infrastructure. On a personal note I am very disappointed by the Linux Foundation's response to this situation. There has been no open discussion, the verbal reasons provided were vague (although, I must emphasise, I am not doubting that there are valid concerns given the nature of the legal framework in the US) and insufficient effort has been made to assist the community in resolving (or even understanding) this problem - as I mention, since we're not clear about what the reason is we have no idea what other services may be impacted. I agree David and I must say I'm disappointed too, but I cannot say I'm surprised. Regards, Jeremiah ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Unable to create a new image (libXrandr rpm cannot be found)
Turns out it was a bug in MIC2, upgrading to the latest version available from gitorious solves this. I've opened https://bugs.meego.com/show_bug.cgi?id=22288 to track this (i.e. request to upgrade MIC2 package available in MeeGo 1.2 repositories). Geoffroy -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of VanCutsem, Geoffroy Sent: Thursday, July 28, 2011 3:08 PM To: meego-dev Subject: [MeeGo-dev] Unable to create a new image (libXrandr rpm cannot be found) Hi folks, I was trying to build my own image but it keeps failing with the following error message (full MIC2 logs attached): Error: failed to create image : URLGrabber error: [Errno 14] HTTP Error 404 : http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages//i586 /libXrandr-1.3.0-5.1.i586.rpm : http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages//i586 /libXrandr-1.3.0-5.1.i586.rpm This file can be found here: http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages but not in the URL as fully specified in log (additional /i586/ that does not exist). Anyone else has seen this (I was using the original MeeGo IVI 1.2 kickstart file) Thanks, Geoffroy Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Compiling Pulseaudio
- Original Message - Hi, I am trying to compile pulseaudio, with no success. Specifically, the 200+ patches have a number of them that don't seem to apply cleanly. As pusleaudio binaries are in the repo -- I figure I must be doing something wrong. I am getting the files from http://download.meego.com/MeeGo/snapshots/testing/1.2.80/latest/repos/ and am using rpmbuild to try and get this to work. I have already got configure to go all the way through without issue. I would love some pointers on this, thanks in advance So, Does anyone know if all those pathces in pulesaudio are still relevant? I'd like to stay as close to *standard* as possible, so I'd hate to remove patches from my build that are still necessary... Nasa ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Compiling Pulseaudio
Have you tried cloning the pulseaudio package in the build server and letting OBS build it for you? This is what most of the dedicated MeeGo developers do for projects that don't have a meego gitorious home. That's also why they don't notice when rpmbuild doesn't work ... because they never use it. regards Joel -Original Message- From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Nasa Sent: Tuesday, August 02, 2011 5:34 AM To: meego-dev Subject: Re: [MeeGo-dev] Compiling Pulseaudio - Original Message - Hi, I am trying to compile pulseaudio, with no success. Specifically, the 200+ patches have a number of them that don't seem to apply cleanly. As pusleaudio binaries are in the repo -- I figure I must be doing something wrong. I am getting the files from http://download.meego.com/MeeGo/snapshots/testing/1.2.80/latest/repos/ and am using rpmbuild to try and get this to work. I have already got configure to go all the way through without issue. I would love some pointers on this, thanks in advance So, Does anyone know if all those pathces in pulesaudio are still relevant? I'd like to stay as close to *standard* as possible, so I'd hate to remove patches from my build that are still necessary... Nasa ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Compiling Pulseaudio
On 8/2/2011 8:46 AM, Clark, Joel wrote: Have you tried cloning the pulseaudio package in the build server and letting OBS build it for you? This is what most of the dedicated MeeGo developers do for projects that don't have a meego gitorious home. That's also why they don't notice when rpmbuild doesn't work ... because they never use it. OBS uses rpmbuild to build. if something does not work outside of OBS, there's some environmental difference... but not rpmbuild :-( ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Compiling Pulseaudio
On Tuesday, August 02, 2011 8:59 AM Arjan van de Ven [mailto:ar...@linux.intel.com] wrote: On 8/2/2011 8:46 AM, Clark, Joel wrote: Have you tried cloning the pulseaudio package in the build server and letting OBS build it for you? This is what most of the dedicated MeeGo developers do for projects that don't have a meego gitorious home. That's also why they don't notice when rpmbuild doesn't work ... because they never use it. OBS uses rpmbuild to build. if something does not work outside of OBS, there's some environmental difference... but not rpmbuild :-( We've seen other failures of rpmbuild outside of OBS, for example most 1.2 kernel builds fail outside of OBS because rpmbuild is waiting for user input which OBS satisfies with /dev/null. Joel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Compiling Pulseaudio
On Tuesday, August 02, 2011 8:59 AM Arjan van de Ven [mailto:ar...@linux.intel.com] wrote: On Saturday July 30, 23:18:26 UTC Nasa wrote I am trying to compile pulseaudio, with no success. Specifically, the 200+ patches have a number of them that don't seem to apply cleanly. As pusleaudio binaries are in the repo -- I figure I must be doing something wrong. I am getting the files from http://download.meego.com/MeeGo/snapshots/testing/1.2.80/latest/repos/ and am using rpmbuild to try and get this to work. I have already got configure to go all the way through without issue. I would love some pointers on this, thanks in advance Have you tried cloning the pulseaudio package in the build server and letting OBS build it for you? This is what most of the dedicated MeeGo developers do for projects that don't have a meego gitorious home. That's also why they don't notice when rpmbuild doesn't work ... because they never use it. OBS uses rpmbuild to build. if something does not work outside of OBS, there's some environmental difference... but not rpmbuild :-( I expect there could be several other reasons why PulseAudio builds successfully in OBS and fails with just rpmbuild separately in developer environment. I admit I'm just guessing and suggesting an alternative since the MeeGo PulseAudio maintainer hasn't answered Nasa's question. regards Joel ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Compiling Pulseaudio
- Original Message - On Tuesday, August 02, 2011 8:59 AM Arjan van de Ven [mailto:ar...@linux.intel.com] wrote: On Saturday July 30, 23:18:26 UTC Nasa wrote I am trying to compile pulseaudio, with no success. Specifically, the 200+ patches have a number of them that don't seem to apply cleanly. As pusleaudio binaries are in the repo -- I figure I must be doing something wrong. I am getting the files from http://download.meego.com/MeeGo/snapshots/testing/1.2.80/latest/repos/ and am using rpmbuild to try and get this to work. I have already got configure to go all the way through without issue. I would love some pointers on this, thanks in advance Have you tried cloning the pulseaudio package in the build server and letting OBS build it for you? This is what most of the dedicated MeeGo developers do for projects that don't have a meego gitorious home. That's also why they don't notice when rpmbuild doesn't work ... because they never use it. OBS uses rpmbuild to build. if something does not work outside of OBS, there's some environmental difference... but not rpmbuild :-( I expect there could be several other reasons why PulseAudio builds successfully in OBS and fails with just rpmbuild separately in developer environment. I admit I'm just guessing and suggesting an alternative since the MeeGo PulseAudio maintainer hasn't answered Nasa's question. regards Joel Joel, I do appreciate you looking after me! I was getting ready to look at OBS and see if I can do what I am looking for there. Nasa ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] LF will not permit apps.meego.com : say hello to apps.formeego.org
Hi, On 08/02/2011 11:59 AM, Jeremiah Foster wrote: On Tue, Aug 2, 2011 at 9:44 AM, David Greavesda...@dgreaves.com wrote: The Linux Foundation have told us in private conversations that they will not permit apps.meego.com to be served from the MeeGo.com infrastructure hosted by them. They do not have the resource at this time to provide a statement giving their reasons. We can not assess what other services may be impacted in the future. This type of behavior is fundamentally anti-community. This shows the Linux Foundation's complete disinterest in users and developers, they're beholden to the corporate sponsors and donors who pay their bills. It's certainly easy to characterise things this way - but I think it's a cheap shot, and not a fair reflection on the Linux Foundation. From where I am standing, with no special knowledge at all, it looks like the Linux Foundation is simply a risk-averse organisation, conscious of the potential knock-on effects that any legal issues could cause for their members and the projects they host. It looks to me like legal counsel has a pretty big say in some strategic decisions the foundation makes, more so than corporate members (in fact, there are a couple of examples of corporate members pushing for things which met with some resistance in the Linux Foundation). If my impression is correct, then you're not achieving anything with this characterisation - on the contrary, our potential advocates inside the foundation and among their members are reading what you write, while the legal advisors responsible for the decision are not; you're potentially forcing potential allies to circle the wagons, so to speak. I obviously hope that we find a way around the issues - perhaps EU hosting, a different domain name, or a second legal opinion judging that the risk is acceptable - but let's try not to be too hasty with the finger-pointing. Cheers, Dave. -- Dave Neary GNOME Foundation member dne...@gnome.org Jabber: nea...@gmail.com ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [MeeGo-community] LF will not permit apps.meego.com : say hello to apps.formeego.org
Hi, Am Dienstag 02 August 2011 schrieb Dave Neary: From where I am standing, with no special knowledge at all, it looks like the Linux Foundation is simply a risk-averse organisation, conscious of the potential knock-on effects that any legal issues could cause for their members and the projects they host. It looks to me like Honestly, a company being afraid of legal consequences is fine. But a linux company fearing consequences when distributing community developed stuff is a bit odd considering the fact that this is exactly the way linux is being developed in general. Really, what do they expect? Linux in general is based on stuff some student wrote for fun in dark finish winters. And now they suddenly realize that there may be the risk of violating patents? Till ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] [MeeGo-community] LF will not permit apps.meego.com : say hello to apps.formeego.org
On Tue, 02 Aug 2011 20:27:28 +0200 Dave Neary dne...@gnome.org wrote: Hi, On 08/02/2011 11:59 AM, Jeremiah Foster wrote: On Tue, Aug 2, 2011 at 9:44 AM, David Greavesda...@dgreaves.com wrote: The Linux Foundation have told us in private ... This type of behavior is fundamentally anti-community. This shows the Linux Foundation's... ... From where I am standing, with no special knowledge at all, it looks like the Linux Foundation is simply ... ... If my impression is correct,... Exactly. It would be very valuable for the Linux Foundation to tell us what they are doing in this regard, what they are not doing, and why. The Linux Foundation is effectively stopping reasonable progress, and not saying anything. That naturally leads to all kinds of speculation about their motives. The best remedy for that is for the Linux Foundation to say something, officially. The longer they wait, the more people will speculate, and negative opinions will flourish. We're listening. Bernd ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
