Re: GNOME 3.14 Blocker Bugs (week 33)
On Tue, 2014-08-12 at 18:32 +0200, Andre Klapper wrote: > Thanks everybody for cleaning up last week's list by fixing and > reassassing quite some items! > There are only eight items left marked as blockers: I think we should add https://bugzilla.gnome.org/show_bug.cgi?id=734298 signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: git.gnome.org changes and new doap file requirements
On Sun, 2014-08-03 at 01:33 +0200, Olav Vitters wrote: > 1. New categories: Core, Core Apps, Apps >Note: Not every module has been put into right category. If you > spot >errors, please let release-t...@gnome.org know. I'm planning to add >some cross checks in the release team scripts to ensure everything >is and stays aligned. This check seems to be overaggressive. I'm trying to add a module that does not fit into any of those categories: $ ssh mcatanz...@git.gnome.org finish-import libgames-scores --- ERROR: libgames-scores.doap is not valid: doap:category property should be one of: apps,core,core-apps,deprecated,infrastructure Please see: https://wiki.gnome.org/Git/FAQ --- ERROR: Cannot clear pending flag as DOAP syntax is invalid So I decided to pretend to be an app, to get past the checker, but it didn't work: I still get the same error no matter what I do. Am I making a mistake or is this a bug on your end? Here is my doap: http://www.w3.org/1999/02/22-rdf-syntax-ns#"; xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"; xmlns:foaf="http://xmlns.com/foaf/0.1/"; xmlns:gnome="http://api.gnome.org/doap-extensions#"; xmlns="http://usefulinc.com/ns/doap#";> libgames-scores Track players' scores history. A library that records players' scores and presents a scores dialog. https://wiki.gnome.org/Apps/Games"; /> http://download.gnome.org/sources/libgames-scores/"; /> http://api.gnome.org/doap-extensions#apps"; /> Michael Catanzaro mailto:mcatanz...@gnome.org"; /> mcatanzaro signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: git.gnome.org changes and new doap file requirements
On Sun, 2014-08-24 at 12:45 -0500, Michael Catanzaro wrote: > So I decided to pretend to be an app, to get past the checker, but it > didn't work: I still get the same error no matter what I do. Am I > making > a mistake or is this a bug on your end? Here is my doap: Actually I'm sorry, it's my fault. False alarm! signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Bugs (week 33)
On Sun, 2014-08-24 at 11:29 -0500, Michael Catanzaro wrote: > On Tue, 2014-08-12 at 18:32 +0200, Andre Klapper wrote: > > Thanks everybody for cleaning up last week's list by fixing and > > reassassing quite some items! > > There are only eight items left marked as blockers: > > I think we should add https://bugzilla.gnome.org/show_bug.cgi?id=734298 All user comments seem to be about 3.10 but none about 3.12 (yet)? Is there any indication that this is still a problem in 3.12/3.13 code? In any case, a comment by a g-o-a maintainer would be extremely welcome on that ticket (if g-o-a has maintainers). Too silent. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Bugs (week 33)
On Sun, 2014-08-24 at 11:29 -0500, Michael Catanzaro wrote: > I think we should add https://bugzilla.gnome.org/show_bug.cgi?id=734298 Google has recently imposed some new restriction, apparently. I think the E-D-S CalDAV backend will need tweaked to work around it. > OPTIONS /caldav/v2/xx%40gmail.com/events/ HTTP/1.1 > Soup-Debug-Timestamp: 1408911513 > Soup-Debug: SoupSessionSync 1 (0x2ab4100), SoupMessage 1 (0x7f41cc05b8b0), > SoupSocket 1 (0x7f41cc0298b0) > Host: apidata.googleusercontent.com > User-Agent: Evolution/3.12.4 > Connection: close < HTTP/1.1 403 Forbidden < Soup-Debug-Timestamp: 1408911513 < Soup-Debug: SoupMessage 1 (0x7f41cc05b8b0) < Content-Type: text/html; charset=UTF-8 < Date: Sun, 24 Aug 2014 20:18:33 GMT < Expires: Sun, 24 Aug 2014 20:18:33 GMT < Cache-Control: private, max-age=0 < X-Content-Type-Options: nosniff < X-Frame-Options: SAMEORIGIN < X-XSS-Protection: 1; mode=block < Server: GSE < Alternate-Protocol: 443:quic < Connection: close < < Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Bugs (week 33)
On Sun, 2014-08-24 at 21:18 +0200, Andre Klapper wrote: > All user comments seem to be about 3.10 but none about 3.12 (yet)? Is > there any indication that this is still a problem in 3.12/3.13 code? > > In any case, a comment by a g-o-a maintainer would be extremely > welcome > on that ticket (if g-o-a has maintainers). Too silent. > > andre The problem started occurring for 3.12 users several months ago, around April or so, then started occurring for 3.10 users more recently. I've seen at least three or four distinct bug reports for the same problem that haven't been marked as duplicates yet; I just picked one with a recent comment to suggest.It seems likely that there are multiple underlying bugs causing the same symptom (authentication dialog appears unexpectedly and rejects valid passwords). For instance, some users report that the authentication dialog always accepts their password on the second attempt (I think these are 3.12 users) while for me on 3.10 my password is never accepted. Other users report that disabling gnome-online-accounts and adding the account in evolution directly solves the problem, someone somewhere pointed out a particular Fedora release of g-o-a and says reverting that update resolves the issue (no I don't remember where I read this), g-o-a developers say it's an e-d-s bug, someone somewhere says it's only a bug with calendar I have no idea what's actually going on, it seems like a confused mess to me. Hopefully Matthew can sort it out now that he's found a problem. signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GNOME 3.13.90 releases
Hi all, In the course of packaging up GNOME 3.13.90, I was advised to switch to webkit2gtk-4.0 (version 2.5.x) as the new epiphany browser would be making use of this. So I jumped into the trouble, adjusted all the packages that depended on webkit2gtk-3.0 (I try to keep the number of variations low if possible) and basically everything is set... BASICALLY: up to this date, there hasn't been a single epiphany release in the 3.13.x cycle. Is this still going to happen? Or are we no longer supposed to package epiphany for distributions? :) I'm sure it's just an oversight, but it happened in all 3.13.x releases so far. Looking forward to get a release of epiphany 3.13.90 to showcase to our users! Dominique / DimStar -- Dimstar / Dominique Leuenberger ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME HIG: Feedback Wanted
On Fri, 2014-08-22 at 08:47 +0100, Allan Day wrote: > Hi all, > > A new version of the HIG is in the works, to be released along with > GNOME 3.14 [1]. I'm currently looking for feedback. I'm about halfway done reading. I have a few suggestions, all minor: * The Visual Layout page discusses how many pixels to use as margins. This is easy for developers to use, but it caused some confusion on LWN given that on hidpi displays twice as many pixels will be used. Maybe this should be clarified. * On the Dialogs page: "In particular, it is currently not recommended to make the Close button the default in an instant apply window, as this can lead to users closing the window accidentally before they have finished using it." I think you can remove the word "currently," unless you're planning to change your mind. :) * Regarding the keybindings page: Ctrl+Alt+Delete is power off, not log off, and it is not disabled default, although it shows up in g-c-c as log off. [1] * Throughout the HIG, you're mostly consistent in using ' and " instead of the ’ and “ characters that are mandated by the Typography page. Some search and replace might be appropriate here, to set a good example. :) * On the index page: "If you have never read the Human Interface Guidelines before, it is recommended that you start with the essentials section, in particular the design principles page, before continuing to learn about the design patterns." But this text is in the description for the Interface elements section, not the Patterns section. [1] https://bugzilla.gnome.org/show_bug.cgi?id=675005 signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GNOME 3.14 Blocker Bugs (week 33)
I was about to file a bug report concerning EDS and Google calendar... (and/or GOA). Last week Evolution suddenly stopped syncing my default Google calendar - created with GOA. I know, it's not directly related to the release, but Evolution is a pretty big part of common Gnome installations, so having it work as expected may be important for 3.14... On Sun, 2014-08-24 at 16:30 -0400, Matthew Barnes wrote: > On Sun, 2014-08-24 at 11:29 -0500, Michael Catanzaro wrote: > > I think we should add https://bugzilla.gnome.org/show_bug.cgi?id=734298 > > Google has recently imposed some new restriction, apparently. > > I think the E-D-S CalDAV backend will need tweaked to work around it. > > > > OPTIONS /caldav/v2/xx%40gmail.com/events/ HTTP/1.1 > > Soup-Debug-Timestamp: 1408911513 > > Soup-Debug: SoupSessionSync 1 (0x2ab4100), SoupMessage 1 (0x7f41cc05b8b0), > > SoupSocket 1 (0x7f41cc0298b0) > > Host: apidata.googleusercontent.com > > User-Agent: Evolution/3.12.4 > > Connection: close > > < HTTP/1.1 403 Forbidden > < Soup-Debug-Timestamp: 1408911513 > < Soup-Debug: SoupMessage 1 (0x7f41cc05b8b0) > < Content-Type: text/html; charset=UTF-8 > < Date: Sun, 24 Aug 2014 20:18:33 GMT > < Expires: Sun, 24 Aug 2014 20:18:33 GMT > < Cache-Control: private, max-age=0 > < X-Content-Type-Options: nosniff > < X-Frame-Options: SAMEORIGIN > < X-XSS-Protection: 1; mode=block > < Server: GSE > < Alternate-Protocol: 443:quic > < Connection: close > < > < Daily Limit for Unauthenticated Use Exceeded. Continued use requires signup. > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
