From goffi at goffi.org Thu Sep 4 19:35:56 2014 From: goffi at goffi.org (Goffi) Date: Thu, 04 Sep 2014 19:35:56 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] keyboard shortcuts refactoring Message-ID: <5408A2FC.4000603@goffi.org> G'day, I have refactored keyboard shortcuts in Urwid SàText/Primitivus. Now everything is in a keys module, and actions have names (for example APP_QUIT for... quitting the application). See both keys modules to see the currently defined actions. The system can seems complexe but it's not really, and it had a couple of check to avoid conflicts. When you add a new action, you add it either it's name directly (then there will not be namespace check), or with one or several namespace. You can't add an action which already exists. examples: ### CODE ### from urwid_satext.keys import action_key_map action_key_map.update( { # Edit bar ("edit", "MODE_INSERTION"): "i", ("edit", "MODE_COMMAND"): ":", ("edit", "HISTORY_PREV"): "up", ("edit", "HISTORY_NEXT"): "down", }) ### CODE ### means INSERTION, MODE_COMMAND, HISTORY_PREV and HISTORY_NEXT are in "edit" namespace. We could use two namespace: action_key_map[(("edit", "modal"), "MODE_COMMAND")] = "i" or no namespace at all: action_key_map["MODE_COMMAND"] = "i" Namespaces are used to check conflicts. If "i" key is used more than one time in "edit" namespace, then a ConflictError will be raised. You can also specify namespace links. For example, if you know that "input" keys are often in dialogs ("dialog" namespace), you can specify it in a tuple: action_key_map.set_close_namespaces((("input", "dialog"),)) note that this tuple is itself in a tuple. That means that if a key is used both in "input" namespace and "dialog" namespace, a ConflictError will be raised. A second argument can be used in set_close_namespaces, this one indicates namespaces that should always checked. For example, in Primitivus, we have: action_key_map.set_close_namespaces(tuple(), ('global', 'focus', 'menu_global')) That means that no key used in 'global', 'focus' or 'menu_global' namespaces can be used elsewhere. So if somebody want to use "ctrl x" in e.g. chat panel, it's not possible because it's already used in APP_QUIT which is in menu_global namespace. If you want to replace a shortcut, you must use replace_shorcut (for one) or replace (for several at once). In this case the action must already exists, and you must not use namespace (which has no sense in this case). Keys can now be changed in sat.conf, in the [primivitus] section. to change a key, use its action name with "key_" prefix (case insensitive). In case of error (e.g. a conflict), config parsing will stop, and you'll have an error popup, with details available in logs (:messages command). example: you want to use [shift tab] to switch focus: you put this in sat.conf ### CONF ### [primitivus] key_focus_switch = shift tab ### CONF ### But when you try it, you fin an error popup. You type in command mode [Esc + ":"] the :messages command, you find this: ERROR: configuration error: shortcut [shift tab] is used both in namespaces "edit" and "focus" Indeed, [shift tab] is used for completion, so you change your sat.conf as follow: ### CONF ### [primitivus] key_focus_switch = shift tab key_edit_complete = tab ### CONF ### And now that works ! You can change focus with [shift tab] and complete with [tab]. Enjoy Goffi From goffi at goffi.org Tue Sep 9 11:27:21 2014 From: goffi at goffi.org (Goffi) Date: Tue, 09 Sep 2014 11:27:21 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?Salut_=C3=A0_Toi_v0=2E5?= Message-ID: <540EC7F9.7090801@goffi.org> english below, Salut à vous, un court message pour vous annoncer la sortie de Salut à Toi version 0.5, l'annonce de la version est disponible sur DLFP uniquement pour le moment: https://linuxfr.org/news/salut-a-toi-version-0-5 N'hésitez pas à nous faire vos commentaires L'équipe de dev -- G'day all, a short notice to announce the release of Salut à Toi version 0.5. There is no english announce yet (we are in a hurry because we are moving to XMPP summit in Berlin), we hope to put it tonight. Feebacks welcome Dev team From mcy at lm7.fr Tue Sep 9 23:33:48 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Tue, 9 Sep 2014 17:33:48 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [fr] Wix et wxPython 3.0 Message-ID: <20140909173348.cff660433019759f585d7b4e@lm7.fr> Salut, Pour le moment le paquet Debian de Wix dépend de python-wxgtk2.8, mais il y a une transition en cours et on nous demande de migrer à python-wxgtk3.0 : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759059 Je n'ai pas essayé les outils dont ils parlent, je préfère avoir votre opinion en premier et savoir quelle version vous avez utilisée pour le développement et s'il y a quelque chose de particulier à faire à votre avis. Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From mcy at lm7.fr Wed Sep 10 00:41:10 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Tue, 9 Sep 2014 18:41:10 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [fr] Wix et wxPython 3.0 In-Reply-To: <20140909173348.cff660433019759f585d7b4e@lm7.fr> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> Message-ID: <20140909184110.81f03e0f770da562430f99a7@lm7.fr> On Tue, 9 Sep 2014 17:33:48 -0400, Matteo Cypriani wrote: > Salut, > > Pour le moment le paquet Debian de Wix dépend de python-wxgtk2.8, mais il y > a une transition en cours et on nous demande de migrer à python-wxgtk3.0 : > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759059 > > Je n'ai pas essayé les outils dont ils parlent, je préfère avoir votre > opinion en premier et savoir quelle version vous avez utilisée pour le > développement et s'il y a quelque chose de particulier à faire à votre avis. Bon quelqu'un vient d'envoyer un patch. Apparemment il y a un problème d'icône manquante. Je pense qu'on va juste appliquer ce patch pour l'instant, mais comme il dit ce serait bien de résoudre le problème en amont de manière plus satisfaisante (càd en ajoutant l'icône en question). -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From souliane at mailoo.org Wed Sep 10 12:57:49 2014 From: souliane at mailoo.org (Adrien) Date: Wed, 10 Sep 2014 12:57:49 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Bfr=5D_Wix_et_wxP?= =?windows-1252?q?ython_3=2E0?= In-Reply-To: <20140909184110.81f03e0f770da562430f99a7@lm7.fr> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> <20140909184110.81f03e0f770da562430f99a7@lm7.fr> Message-ID: <54102EAD.5070200@mailoo.org> Hi, that icon is actually shipped with sat_media. The directory should be pointed in .sat.conf, for example: media_dir = ~/workspace/sat_media The default value is /usr/share/sat/media. I'm not sure how sat_media should be shipped: with the sat-xmpp-core package on with an additionnal sat-xmpp-media package? Cheers, Adrien On 09/10/2014 12:41 AM, Matteo Cypriani wrote: > On Tue, 9 Sep 2014 17:33:48 -0400, Matteo Cypriani wrote: >> Salut, >> >> Pour le moment le paquet Debian de Wix dépend de python-wxgtk2.8, mais il y >> a une transition en cours et on nous demande de migrer à python-wxgtk3.0 : >> >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759059 >> >> Je n'ai pas essayé les outils dont ils parlent, je préfère avoir votre >> opinion en premier et savoir quelle version vous avez utilisée pour le >> développement et s'il y a quelque chose de particulier à faire à votre avis. > > Bon quelqu'un vient d'envoyer un patch. Apparemment il y a un problème > d'icône manquante. Je pense qu'on va juste appliquer ce patch pour l'instant, > mais comme il dit ce serait bien de résoudre le problème en amont de manière > plus satisfaisante (càd en ajoutant l'icône en question). > > > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev > From mcy at lm7.fr Wed Sep 10 16:31:03 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Wed, 10 Sep 2014 10:31:03 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Ben=5D_Wix_et_wxPython_3?= =?utf-8?q?=2E0?= In-Reply-To: <54102EAD.5070200@mailoo.org> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> <20140909184110.81f03e0f770da562430f99a7@lm7.fr> <54102EAD.5070200@mailoo.org> Message-ID: <20140910103103.89877f57266d0ffb91714efe@lm7.fr> On Wed, 10 Sep 2014 12:57:49 +0200, Adrien wrote: > The default value is /usr/share/sat/media. I'm not sure how sat_media > should be shipped: with the sat-xmpp-core package on with an additionnal > sat-xmpp-media package? Since it's a different upstream tarball, we'll have to create a new package for it. Did we ever resolve the problem of the tarot deck's license? By the ways it's not really obvious on the website that one is supposed to get the sat_media archive (or where to get it, for that matter). Maybe the download link should point to a page explaining what to get instead of directly to sat.tar? -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From mcy at lm7.fr Wed Sep 10 19:20:00 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Wed, 10 Sep 2014 13:20:00 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] Questions regarding urwid-satext Message-ID: <20140910132000.5879d1e95bf701b17ba2cdfa@lm7.fr> Hi there, Two question I asked Goffi recently but it's apparently better to repost here: 1. In SàT 0.5, README4PACKAGERS still indicates that Primitivus depends on urwid-satext >= 0.3.0, but if I understood correctly what Goffi told me, that should actually be >= 0.4, is that right? 2. The documentation of urwid-satext doesn't indicate the minimal version of urwid which is required. Version 0.3 depended on urwid >= 1.1, is that still okay? Cheers, Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From mcy at lm7.fr Wed Sep 10 19:41:09 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Wed, 10 Sep 2014 13:41:09 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] python-setuptools minimal version Message-ID: <20140910134109.e4c6c18e6a385547af093746@lm7.fr> Hi again, I noticed the minimal version of setuptools asked for in the new versions of SàT and urwid-satext is 5.7 ("DEFAULT_VERSION = 5.7" in ez_setup.py), but version 5.5 seems to work fine. In the Debian packages, I patched ez_setup.py so that setuptools 5.7 doesn't get downloaded by ez_setup.py each time the package is built. If there is no problem in doing so, you may want to lower the version upstream as well. Cheers, Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From souliane at mailoo.org Thu Sep 11 10:21:31 2014 From: souliane at mailoo.org (Adrien) Date: Thu, 11 Sep 2014 10:21:31 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_Wix_et_wxP?= =?windows-1252?q?ython_3=2E0?= In-Reply-To: <20140910103103.89877f57266d0ffb91714efe@lm7.fr> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> <20140909184110.81f03e0f770da562430f99a7@lm7.fr> <54102EAD.5070200@mailoo.org> <20140910103103.89877f57266d0ffb91714efe@lm7.fr> Message-ID: <54115B8B.9050108@mailoo.org> Hi, On 09/10/2014 04:31 PM, Matteo Cypriani wrote: > On Wed, 10 Sep 2014 12:57:49 +0200, Adrien wrote: >> The default value is /usr/share/sat/media. I'm not sure how sat_media >> should be shipped: with the sat-xmpp-core package on with an additionnal >> sat-xmpp-media package? > > Since it's a different upstream tarball, we'll have to create a new package > for it. Did we ever resolve the problem of the tarot deck's license? We didn't move about that, but since nobody is complaining, we guess it's OK... > By the ways it's not really obvious on the website that one is supposed to > get the sat_media archive (or where to get it, for that matter). Maybe the > download link should point to a page explaining what to get instead of > directly to sat.tar? Yes that's right. We'll do that and we also want to remake a bit the website. Thanks, Adrien From souliane at mailoo.org Thu Sep 11 10:28:51 2014 From: souliane at mailoo.org (Adrien) Date: Thu, 11 Sep 2014 10:28:51 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_Questions_?= =?windows-1252?q?regarding_urwid-satext?= In-Reply-To: <20140910132000.5879d1e95bf701b17ba2cdfa@lm7.fr> References: <20140910132000.5879d1e95bf701b17ba2cdfa@lm7.fr> Message-ID: <54115D43.2010103@mailoo.org> Hi, On 09/10/2014 07:20 PM, Matteo Cypriani wrote: > Hi there, > > Two question I asked Goffi recently but it's apparently better to repost here: > > 1. In SàT 0.5, README4PACKAGERS still indicates that Primitivus depends on > urwid-satext >= 0.3.0, but if I understood correctly what Goffi told me, that > should actually be >= 0.4, is that right? Yes >= 4.0. > 2. The documentation of urwid-satext doesn't indicate the minimal version of > urwid which is required. Version 0.3 depended on urwid >= 1.1, is that still > okay? Yes >= 1.1. I will add it to the README. Thanks, Adrien From souliane at mailoo.org Thu Sep 11 10:34:08 2014 From: souliane at mailoo.org (Adrien) Date: Thu, 11 Sep 2014 10:34:08 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_Questions_?= =?windows-1252?q?regarding_urwid-satext?= In-Reply-To: <54115D43.2010103@mailoo.org> References: <20140910132000.5879d1e95bf701b17ba2cdfa@lm7.fr> <54115D43.2010103@mailoo.org> Message-ID: <54115E80.9030702@mailoo.org> On 09/11/2014 10:28 AM, Adrien wrote: >> 2. The documentation of urwid-satext doesn't indicate the minimal >> version of >> urwid which is required. Version 0.3 depended on urwid >= 1.1, is that >> still >> okay? > > Yes >= 1.1. I will add it to the README. Sorry that's >= 1.2 actually. It would work with 1.1 except the "disable_mouse" option. From robotux at celest.fr Thu Sep 11 17:34:16 2014 From: robotux at celest.fr (Thomas Preud'homme) Date: Thu, 11 Sep 2014 23:34:16 +0800 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Bfr=5D_Wix_et_wxPython_3?= =?utf-8?q?=2E0?= In-Reply-To: <54102EAD.5070200@mailoo.org> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> <20140909184110.81f03e0f770da562430f99a7@lm7.fr> <54102EAD.5070200@mailoo.org> Message-ID: <1918171.YJW7XcqkIu@mallow.celest.fr> [resending as I used the wrong identity] Le mercredi 10 septembre 2014, 12:57:49 Adrien a écrit : > Hi, > > that icon is actually shipped with sat_media. The directory should be > pointed in .sat.conf, for example: > > media_dir = ~/workspace/sat_media > > The default value is /usr/share/sat/media. I'm not sure how sat_media > should be shipped: with the sat-xmpp-core package on with an additionnal > sat-xmpp-media package? The former is more difficult because it's in a different tarball and would require us to use multi-tarball Debian source package. However I suppose sat_media and sat evolve in lockstep so that might make sense. I need to think more about this. Matteo, any opinion about it? Best regards, Thomas -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: signature.asc Type: application/pgp-signature Taille: 819 octets Desc: This is a digitally signed message part. URL: From mcy at lm7.fr Thu Sep 11 17:55:20 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Thu, 11 Sep 2014 11:55:20 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Bfr=5D_Wix_et_wxPython_3?= =?utf-8?q?=2E0?= In-Reply-To: <1918171.YJW7XcqkIu@mallow.celest.fr> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> <20140909184110.81f03e0f770da562430f99a7@lm7.fr> <54102EAD.5070200@mailoo.org> <1918171.YJW7XcqkIu@mallow.celest.fr> Message-ID: <20140911115520.572b26ca14733ee059630106@lm7.fr> On Thu, 11 Sep 2014 23:34:16 +0800, Thomas Preud'homme wrote: > Le mercredi 10 septembre 2014, 12:57:49 Adrien a écrit : > > I'm not sure how sat_media > > should be shipped: with the sat-xmpp-core package on with an additionnal > > sat-xmpp-media package? > > The former is more difficult because it's in a different tarball and would > require us to use multi-tarball Debian source package. However I suppose > sat_media and sat evolve in lockstep so that might make sense. I need to > think more about this. Matteo, any opinion about it? I had forgotten about multi-tarball source packages, so I didn't consider that, but why not. For now sat_media is about 2 MiB, which is not huge. Is there a big advantage in not creating a separate package? If we do that, we could split sat_media and put the files in the appropriate packages. For example, the icons used only by wix would go in the wix package, the libervia directory in the (future) libervia package, etc. Not sure whether or not it makes sense. Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From robotux at celest.fr Thu Sep 11 18:11:37 2014 From: robotux at celest.fr (Thomas Preud'homme) Date: Fri, 12 Sep 2014 00:11:37 +0800 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Bfr=5D_Wix_et_wxPython_3?= =?utf-8?q?=2E0?= In-Reply-To: <20140911115520.572b26ca14733ee059630106@lm7.fr> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> <1918171.YJW7XcqkIu@mallow.celest.fr> <20140911115520.572b26ca14733ee059630106@lm7.fr> Message-ID: <3974903.r81o20l6Ia@mallow.celest.fr> Le jeudi 11 septembre 2014, 11:55:20 Matteo Cypriani a écrit : > > I had forgotten about multi-tarball source packages, so I didn't consider > that, but why not. For now sat_media is about 2 MiB, which is not huge. Is > there a big advantage in not creating a separate package? One less binary package or more if we try to have icons associated with the right package. However the size might not make it worth it. > > If we do that, we could split sat_media and put the files in the appropriate > packages. For example, the icons used only by wix would go in the wix > package, the libervia directory in the (future) libervia package, etc. Not > sure whether or not it makes sense. It does. It's another good point for this. Doing it with a separate source package would be possible but lead to more binary package and you know our dear FTP masters don't like this. I'd say if we go to the route of multi-tarball source package (which might be fun, just to try that out) it makes sense to assign them to the right package. Otherwise let's just have one sat-media package as the size is not very big. Best regards, Thomas -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: signature.asc Type: application/pgp-signature Taille: 819 octets Desc: This is a digitally signed message part. URL: From mcy at lm7.fr Sat Sep 13 01:12:02 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Fri, 12 Sep 2014 19:12:02 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] A bunch of (minor) patches Message-ID: <20140912191202.09e8cb175e6c795403b014e2@lm7.fr> Hi there, Please find attached a bunch of patches that fix various more or less minor things. The first two are integrated in Debian, the other ones are just fixes that could be useful upstream but not critical enough to be integrated in our package. 0002-Avoid-setting-a-bad-icon.patch allows Wix to start even when tray_icon.xpm can't be found (i.e. when sat_media is not installed, as discussed in another thread). You may or may not want to apply that upstream, my personal opinion is that it can't hurt. 0003-Lower-default-setuptools-version.patch, as its name indicates, lowers the default version of setuptools from 5.7 to 5.5 in ez_setup.py, which allows to build on systems where an older version is available. It works perfectly here with Debian's setuptools which is still 5.5. information_typo.patch fixes a recurring error in the source, namely ?informations? in a plural form (which is incorrect because ?information? is uncountable in English). README4PACKAGERS.patch mainly adds precision about the dependencies. I replaced ?Urwid-satext >= 0.3.0? with ?Urwid-satext 0.4?, since it seems that a version of SàT is tied to a given version of Urwid-satext (I know this can change, but I think you told us that for now backward compatibility is not guaranteed in Urwid-satext). Another notable change is that I removed the section about Libervia; since it is packaged independently it didn't make sense to have that there IMO, but you may want to keep it nonetheless (after all, you probably had a good reason for putting it there in the first place). README.patch fixes various typos in the README. I also took the liberty to precise that I'm one of the co-maintainers of the Debian package :-) Please also check out bug #51, where I put a new version of the patch to fix the problem of missing PYTHONPATH: https://bugs.goffi.org/show_bug.cgi?id=51 Oh and before I forget, we maintain manual pages in Debian since it is required by the Policy. I think this was discussed before and that you did *not* want to include them upstream for some reason, but if this has changed or if I'm mistaken, feel free to grab the updated version of the files (sat.1, jp.1, primitivus.1 and wix.1) on our VCS and to ship them with SàT 0.5.1: http://anonscm.debian.org/cgit/collab-maint/salutatoi.git/tree/debian Cheers, Matteo P.S.: the Debian package for 0.5.0 should be ready soon, everything works now. I'm just waiting for a review from my dear co-maintainer (wink wink Thomas); if you guys are faster than he is, we may upload 0.5.1 directly. -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: 0002-Avoid-setting-a-bad-icon.patch Type: text/x-diff Taille: 1612 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: 0003-Lower-default-setuptools-version.patch Type: text/x-diff Taille: 815 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: information_typo.patch Type: text/x-diff Taille: 9213 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: README4PACKAGERS.patch Type: text/x-diff Taille: 1546 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: README.patch Type: text/x-diff Taille: 4540 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From mcy at lm7.fr Sat Sep 13 05:48:57 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Fri, 12 Sep 2014 23:48:57 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [en] A bunch of (minor) patches In-Reply-To: <20140912191202.09e8cb175e6c795403b014e2@lm7.fr> References: <20140912191202.09e8cb175e6c795403b014e2@lm7.fr> Message-ID: <20140912234857.5e9647f645cc76ea36222481@lm7.fr> Hi, me again! Here are two more patches. INSTALL.patch: various English corrections in the INSTALL file. hastings_uris.patch: apparently, Steve Hastings (the author of pyfeed and xe) moved his website to another domain; this patch updates the URIs. It should be applied after all the other patches I sent you. Cheers, Matteo -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: INSTALL.patch Type: text/x-diff Taille: 3486 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: hastings_uris.patch Type: text/x-diff Taille: 3237 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From mcy at lm7.fr Sat Sep 13 06:04:59 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Sat, 13 Sep 2014 00:04:59 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= [fr] Erreur pip sous DragonFly BSD Message-ID: <20140913000459.8ee65e9e1ed25304ce44e8f7@lm7.fr> Re-re-salut, et désolé pour le spam, (Je fais celui-là en français le temps d'investiguer le problème, et j'ouvrirai un bug si besoin quand je comprendrai mieux ce qui se passe.) J'ai joué un peu à essayer d'installer SàT sous DragonFly, sans succès pour l'instant. Avec le setup.py, tout avait l'air de marcher et de s'installer correctement, sauf que twistd ne se lance pas pour une obscure raison (il ne trouve pas twistd.tap ou un truc comme ça), mais je ne sais pas si ça vient du paquet de la distrib, s'il manque des dépendances, ou si c'est l'installation qui est foireuse. Bref, ensuite j'ai tenté pip install . comme le suggère le fichier INSTALL. Et là, c'est le drame, il télécharge pas mal de trucs, et plante en essayant de configurer urwid_satext. Oui, satext, vous m'avez bien lu, et c'est justement pour ça que j'en parle ici. L'erreur : Running setup.py (path:/tmp/pip_build_root/urwid-satext/setup.py) egg_info for package urwid-satext Traceback (most recent call last): File "", line 17, in File "/tmp/pip_build_root/urwid-satext/setup.py", line 4, in from ez_setup import use_setuptools ImportError: No module named ez_setup Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 17, in File "/tmp/pip_build_root/urwid-satext/setup.py", line 4, in from ez_setup import use_setuptools ImportError: No module named ez_setup J'attache le log complet pour référence. Bon là encore je ne suis pas sûr de moi, j'ai peut-être mal fait quelque chose vu que je ne suis pas familier des installations de programmes en Python. Ah et au fait, on en a déjà parlé et je sais qu'on a un désaccord philosophique sur ce point, mais je me sens obligé de le signaler quand même : sur une console de 80 colonnes, vos fichiers texte sont affreux à lire. ;-) (Et oui, BSD c'est « comme au bon vieux temps ». Et non, ne me répondez pas que c'est le boulot de l'éditeur de texte de couper les lignes où il faut, less n'est pas assez malin pour ça.) Matteo P.S. : je vais encore passer pour un râleur, mais ce serait sympa que la ML ne me renvoie pas mes propres messages, y'a pas moyen de configurer ça ? -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: pip_failure.log Type: application/octet-stream Taille: 49701 octets Desc: non disponible URL: -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From goffi at goffi.org Mon Sep 15 12:55:00 2014 From: goffi at goffi.org (Goffi) Date: Mon, 15 Sep 2014 12:55:00 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Bfr=5D_Erreur_pip?= =?windows-1252?q?_sous_DragonFly_BSD?= In-Reply-To: <20140913000459.8ee65e9e1ed25304ce44e8f7@lm7.fr> References: <20140913000459.8ee65e9e1ed25304ce44e8f7@lm7.fr> Message-ID: <5416C584.4060504@goffi.org> Salut, on n'a pas été trop dispo depuis notre départ à Berlin, je vais essayer de me m'occuper de la longue liste de choses à faire le plus rapidement possible. J'ai aussi l'erreur que tu as sur mon buildbot, je vais regarder ce qu'il se passe et te tiens au courant, ça ne me semble pas grand chose à première vue, probablement un fichier oublié. Pour les 80 colonnes, c'est moi personnellement qui suis contre: c'est une limite qui avait un sens à l'époque où tous les terminaux étaient en 80 colonnes, mais aujourd'hui on peut avoir moins (un split dans un vim) ou bien plus (dans ce cas ça n'est pas désagréable mais on perd de la place), et du coup ça va faire une lecture désagréable dans tous les autres cas que 80 colonnes. Un éditeur est censé adapter la ligne comme il faut. Si less ne fait pas ça, un « vim -R » le remplacera avantageusement. Je viens de te désactiver l'écho sur la liste de diffusion. ++ Goffi On 13/09/2014 06:04, Matteo Cypriani wrote: > Re-re-salut, et désolé pour le spam, > > (Je fais celui-là en français le temps d'investiguer le problème, et > j'ouvrirai un bug si besoin quand je comprendrai mieux ce qui se passe.) > > J'ai joué un peu à essayer d'installer SàT sous DragonFly, sans succès pour > l'instant. Avec le setup.py, tout avait l'air de marcher et de s'installer > correctement, sauf que twistd ne se lance pas pour une obscure raison (il ne > trouve pas twistd.tap ou un truc comme ça), mais je ne sais pas si ça vient > du paquet de la distrib, s'il manque des dépendances, ou si c'est > l'installation qui est foireuse. > > Bref, ensuite j'ai tenté pip install . comme le suggère le fichier INSTALL. > Et là, c'est le drame, il télécharge pas mal de trucs, et plante en essayant > de configurer urwid_satext. Oui, satext, vous m'avez bien lu, et c'est > justement pour ça que j'en parle ici. L'erreur : > > Running setup.py (path:/tmp/pip_build_root/urwid-satext/setup.py) egg_info > for package urwid-satext Traceback (most recent call last): > File "", line 17, in > File "/tmp/pip_build_root/urwid-satext/setup.py", line 4, in > from ez_setup import use_setuptools > ImportError: No module named ez_setup > Complete output from command python setup.py egg_info: > Traceback (most recent call last): > > File "", line 17, in > > File "/tmp/pip_build_root/urwid-satext/setup.py", line 4, in > > from ez_setup import use_setuptools > > ImportError: No module named ez_setup > > > J'attache le log complet pour référence. Bon là encore je ne suis pas sûr de > moi, j'ai peut-être mal fait quelque chose vu que je ne suis pas familier des > installations de programmes en Python. > > Ah et au fait, on en a déjà parlé et je sais qu'on a un désaccord > philosophique sur ce point, mais je me sens obligé de le signaler quand même : > sur une console de 80 colonnes, vos fichiers texte sont affreux à lire. ;-) > (Et oui, BSD c'est « comme au bon vieux temps ». Et non, ne me répondez pas > que c'est le boulot de l'éditeur de texte de couper les lignes où il faut, > less n'est pas assez malin pour ça.) > > Matteo > > P.S. : je vais encore passer pour un râleur, mais ce serait sympa que la ML > ne me renvoie pas mes propres messages, y'a pas moyen de configurer ça ? > > > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev > From goffi at goffi.org Mon Sep 15 13:33:51 2014 From: goffi at goffi.org (Goffi) Date: Mon, 15 Sep 2014 13:33:51 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Bfr=5D_Erreur_pip?= =?windows-1252?q?_sous_DragonFly_BSD?= In-Reply-To: <20140913000459.8ee65e9e1ed25304ce44e8f7@lm7.fr> References: <20140913000459.8ee65e9e1ed25304ce44e8f7@lm7.fr> Message-ID: <5416CE9F.6030702@goffi.org> Bon le problème était un fichier non renommé dans MANIFEST.in, c'est le fichier qui indique ce qui doit être fourni pour une distribution « source », et du coup il manquait ce fichier. Ça devrait être réglé avec la version 0.4.1 de Urwid SàText (et le problème n'est pas spécifique à DragonFly BSD). ++ Goffi On 13/09/2014 06:04, Matteo Cypriani wrote: > Re-re-salut, et désolé pour le spam, > > (Je fais celui-là en français le temps d'investiguer le problème, et > j'ouvrirai un bug si besoin quand je comprendrai mieux ce qui se passe.) > > J'ai joué un peu à essayer d'installer SàT sous DragonFly, sans succès pour > l'instant. Avec le setup.py, tout avait l'air de marcher et de s'installer > correctement, sauf que twistd ne se lance pas pour une obscure raison (il ne > trouve pas twistd.tap ou un truc comme ça), mais je ne sais pas si ça vient > du paquet de la distrib, s'il manque des dépendances, ou si c'est > l'installation qui est foireuse. > > Bref, ensuite j'ai tenté pip install . comme le suggère le fichier INSTALL. > Et là, c'est le drame, il télécharge pas mal de trucs, et plante en essayant > de configurer urwid_satext. Oui, satext, vous m'avez bien lu, et c'est > justement pour ça que j'en parle ici. L'erreur : > > Running setup.py (path:/tmp/pip_build_root/urwid-satext/setup.py) egg_info > for package urwid-satext Traceback (most recent call last): > File "", line 17, in > File "/tmp/pip_build_root/urwid-satext/setup.py", line 4, in > from ez_setup import use_setuptools > ImportError: No module named ez_setup > Complete output from command python setup.py egg_info: > Traceback (most recent call last): > > File "", line 17, in > > File "/tmp/pip_build_root/urwid-satext/setup.py", line 4, in > > from ez_setup import use_setuptools > > ImportError: No module named ez_setup > > > J'attache le log complet pour référence. Bon là encore je ne suis pas sûr de > moi, j'ai peut-être mal fait quelque chose vu que je ne suis pas familier des > installations de programmes en Python. > > Ah et au fait, on en a déjà parlé et je sais qu'on a un désaccord > philosophique sur ce point, mais je me sens obligé de le signaler quand même : > sur une console de 80 colonnes, vos fichiers texte sont affreux à lire. ;-) > (Et oui, BSD c'est « comme au bon vieux temps ». Et non, ne me répondez pas > que c'est le boulot de l'éditeur de texte de couper les lignes où il faut, > less n'est pas assez malin pour ça.) > > Matteo > > P.S. : je vais encore passer pour un râleur, mais ce serait sympa que la ML > ne me renvoie pas mes propres messages, y'a pas moyen de configurer ça ? > > > > _______________________________________________ > dev mailing list > dev at goffi.org > http://lists.goffi.org/listinfo/dev > From goffi at goffi.org Mon Sep 15 14:51:37 2014 From: goffi at goffi.org (Goffi) Date: Mon, 15 Sep 2014 14:51:37 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_A_bunch_of?= =?windows-1252?q?_=28minor=29_patches?= In-Reply-To: <20140912191202.09e8cb175e6c795403b014e2@lm7.fr> References: <20140912191202.09e8cb175e6c795403b014e2@lm7.fr> Message-ID: <5416E0D9.6010406@goffi.org> Hi, first of all, thanks for all these contributions. For all patches I have adapted the commit message to our policy (see http://wiki.goffi.org/wiki/Howto_contribute/en ). Below you can find comments for each patches: > 0002-Avoid-setting-a-bad-icon.patch allows Wix to start even when > tray_icon.xpm can't be found (i.e. when sat_media is not installed, as > discussed in another thread). You may or may not want to apply that upstream, > my personal opinion is that it can't hurt. Commited, I have added Olly Betts to contributors in a later commit. > 0003-Lower-default-setuptools-version.patch, as its name indicates, lowers > the default version of setuptools from 5.7 to 5.5 in ez_setup.py, which allows > to build on systems where an older version is available. It works perfectly > here with Debian's setuptools which is still 5.5. commited, we should probably do the same for urwid SàText then. > information_typo.patch fixes a recurring error in the source, namely > ?informations? in a plural form (which is incorrect because ?information? is > uncountable in English). Oh, that's a gotcha, we'll try to avoid this mistake in the future. > README4PACKAGERS.patch mainly adds precision about the dependencies. I > replaced ?Urwid-satext >= 0.3.0? with ?Urwid-satext 0.4?, since it seems that > a version of SàT is tied to a given version of Urwid-satext (I know this can > change, but I think you told us that for now backward compatibility is not > guaranteed in Urwid-satext). Another notable change is that I removed the > section about Libervia; since it is packaged independently it didn't make > sense to have that there IMO, but you may want to keep it nonetheless (after > all, you probably had a good reason for putting it there in the first place). This one was a bit modified: first the version of urwid SàText was updated meanwhile, but I have changed it to 0.4.1 because of the install fix that I've just pushed. And you're right, urwid SàText is tied to SàT releases, so they should be synchronised (Urwid SàText was formely a part of SàT, but it was moved in a separate library to allow other projects to use it). I haven't commited the removal of Libervia section because that's how we work: Libervia is linked to SàT and is released at the same time with the same version number (except minor updates), it's outside the main package because it's a big project by itself, and it had some particularities (mainly the compilation by pyjamas). But for all files (README, CHANGELOGS), it's really redundant and unpractical to have them in both repositories, so we have a minimal bunch of legal files in Libervia, and we ask to use the ones of SàT core (which has to be installed anyway to use libervia). This way is more handy for us (we just have to check at one place for INSTALL, CHANGELOG, and README files). > README.patch fixes various typos in the README. I also took the liberty to > precise that I'm one of the co-maintainers of the Debian package :-) Good, commited > Please also check out bug #51, where I put a new version of the patch to fix > the problem of missing PYTHONPATH: https://bugs.goffi.org/show_bug.cgi?id=51 This one is not OK for me: it erase the PYTHONPATH when SàT is launched from the repository (i.e. without installation), and force it when SàT is installed. This is bad because PYTHONPATH is dependant of the way we want to launch SàT, for example I have two scripts: sat and sat_dev which launch SàT with different PYTHONPATH (the one for my main instance, and the one for the dev version, as explained here: http://wiki.goffi.org/wiki/Howto_launch_several_S%C3%A0T_instances); with you patch the scripts would not work anymore. As I'm not sure of the issue that you have, can you attach a complete backtrace to the bug report ? It's also better to continue the discussion there because else it will be difficult to track bug history. > Oh and before I forget, we maintain manual pages in Debian since it is > required by the Policy. I think this was discussed before and that you did > *not* want to include them upstream for some reason, but if this has changed > or if I'm mistaken, feel free to grab the updated version of the files > (sat.1, jp.1, primitivus.1 and wix.1) on our VCS and to ship them with SàT > 0.5.1: > http://anonscm.debian.org/cgit/collab-maint/salutatoi.git/tree/debian We do want include them mainstream ! If I remember correctly, our discussion was about the commands in jp, and the fact that I want to make an automatic tool to generate the manpage. But as we are too busy for that right now, we are happy to include your manpages. I'll do that soon. > P.S.: the Debian package for 0.5.0 should be ready soon, everything works now. > I'm just waiting for a review from my dear co-maintainer (wink wink Thomas); > if you guys are faster than he is, we may upload 0.5.1 directly. Great :). We wait a bit for 0.5.1 as we have already found several issues, it would be better to wait a couple of days to be sure thing are stable. Thanks again for your help/contributions/support. Goffi From goffi at goffi.org Mon Sep 15 16:00:02 2014 From: goffi at goffi.org (Goffi) Date: Mon, 15 Sep 2014 16:00:02 +0200 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?windows-1252?q?=5Ben=5D_A_bunch_of?= =?windows-1252?q?_=28minor=29_patches?= In-Reply-To: <5416E0D9.6010406@goffi.org> References: <20140912191202.09e8cb175e6c795403b014e2@lm7.fr> <5416E0D9.6010406@goffi.org> Message-ID: <5416F0E2.8010000@goffi.org> On 15/09/2014 14:51, Goffi wrote: >> Oh and before I forget, we maintain manual pages in Debian since it is >> required by the Policy. I think this was discussed before and that you >> did >> *not* want to include them upstream for some reason, but if this has >> changed >> or if I'm mistaken, feel free to grab the updated version of the files >> (sat.1, jp.1, primitivus.1 and wix.1) on our VCS and to ship them with >> SàT >> 0.5.1: >> http://anonscm.debian.org/cgit/collab-maint/salutatoi.git/tree/debian > > We do want include them mainstream ! If I remember correctly, our > discussion was about the commands in jp, and the fact that I want to > make an automatic tool to generate the manpage. But as we are too busy > for that right now, we are happy to include your manpages. I'll do that > soon. We have added some keyboard shortcuts in 0.5, I have to update the wiki, we can talk about this on the muc room... From mcy at lm7.fr Mon Sep 15 17:07:09 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Mon, 15 Sep 2014 11:07:09 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Ben=5D_A_bunch_of_=28min?= =?utf-8?q?or=29_patches?= In-Reply-To: <5416E0D9.6010406@goffi.org> References: <20140912191202.09e8cb175e6c795403b014e2@lm7.fr> <5416E0D9.6010406@goffi.org> Message-ID: <20140915110709.6bb62fb5c064dc4df26b538e@lm7.fr> On Mon, 15 Sep 2014 14:51:37 +0200, Goffi wrote: > For all patches I have adapted the commit message to our policy (see > http://wiki.goffi.org/wiki/Howto_contribute/en ). Sorry, I didn't really pay attention to the comments. > > 0003-Lower-default-setuptools-version.patch, as its name indicates, lowers > > the default version of setuptools from 5.7 to 5.5 in ez_setup.py, which > > allows to build on systems where an older version is available. It works > > perfectly here with Debian's setuptools which is still 5.5. > > commited, we should probably do the same for urwid SàText then. Yes, I forgot to mention that this patch applied for both. > I haven't commited the removal of Libervia section because that's how we > work: [?] Got it, that makes sense. > > Please also check out bug #51, where I put a new version of the patch to > > fix the problem of missing PYTHONPATH: > > https://bugs.goffi.org/show_bug.cgi?id=51 > > This one is not OK for me: it erase the PYTHONPATH when SàT is launched > from the repository (i.e. without installation), and force it when SàT > is installed. Indeed, PYTHONPATH="" is not ideal, I figured it was OK because it wasn't used at all, but I guess this might not be always the case. What about PYTHONPATH="$PYTHONPATH" ? > This is bad because PYTHONPATH is dependant of the way we want to launch > SàT, for example I have two scripts: sat and sat_dev which launch SàT > with different PYTHONPATH (the one for my main instance, and the one for > the dev version, as explained here: > http://wiki.goffi.org/wiki/Howto_launch_several_S%C3%A0T_instances); > with you patch the scripts would not work anymore. > > As I'm not sure of the issue that you have, can you attach a complete > backtrace to the bug report ? It's also better to continue the > discussion there because else it will be difficult to track bug history. I'll do that. But basically the issue is that we install everything in /usr/share/salutatoi, so without setting PYTHONPATH, the piece of python in sat.sh fails to import SàT modules (and then I think twistd can't find the SàT plugin). > > Oh and before I forget, we maintain manual pages in Debian since it is > > required by the Policy. I think this was discussed before and that you did > > *not* want to include them upstream for some reason, but if this has > > changed or if I'm mistaken, feel free to grab the updated version of the > > files (sat.1, jp.1, primitivus.1 and wix.1) on our VCS and to ship them > > with SàT 0.5.1: > > http://anonscm.debian.org/cgit/collab-maint/salutatoi.git/tree/debian > > We do want include them mainstream ! If I remember correctly, our > discussion was about the commands in jp, and the fact that I want to > make an automatic tool to generate the manpage. But as we are too busy > for that right now, we are happy to include your manpages. I'll do that > soon. Great! > > P.S.: the Debian package for 0.5.0 should be ready soon, everything works > > now. I'm just waiting for a review from my dear co-maintainer (wink wink > > Thomas); if you guys are faster than he is, we may upload 0.5.1 directly. > > Great :). We wait a bit for 0.5.1 as we have already found several > issues, it would be better to wait a couple of days to be sure thing are > stable. I uploaded 0.5.0 yesterday, it was an emergency because of the transition to wxPython 3.0 (otherwise SàT was going to be removed from testing in a few days). > Thanks again for your help/contributions/support. You are very welcome. -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From mcy at lm7.fr Mon Sep 15 17:17:35 2014 From: mcy at lm7.fr (Matteo Cypriani) Date: Mon, 15 Sep 2014 11:17:35 -0400 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Bfr=5D_Erreur_pip_sous_D?= =?utf-8?q?ragonFly_BSD?= In-Reply-To: <5416C584.4060504@goffi.org> References: <20140913000459.8ee65e9e1ed25304ce44e8f7@lm7.fr> <5416C584.4060504@goffi.org> Message-ID: <20140915111735.5f02818cb74c3046a30316a6@lm7.fr> On Mon, 15 Sep 2014 12:55:00 +0200, Goffi wrote: > J'ai aussi l'erreur que tu as sur mon buildbot, je vais regarder ce > qu'il se passe et te tiens au courant, ça ne me semble pas grand chose à > première vue, probablement un fichier oublié. Merci d'avoir réglé le souci, je retenterai quand vous aurez sorti les nouvelles versions. Si tout marche bien j'en profiterai peut-être pour faire une recette pour les ports, comme ça SàT sera dispo pour FreeBSD et DragonFly (je n'ai jamais fait, je ne garantis rien mais il paraît que c'est facile). > Pour les 80 colonnes, c'est moi personnellement qui suis contre: c'est > une limite qui avait un sens à l'époque où tous les terminaux étaient en > 80 colonnes, mais aujourd'hui on peut avoir moins (un split dans un vim) > ou bien plus (dans ce cas ça n'est pas désagréable mais on perd de la > place), et du coup ça va faire une lecture désagréable dans tous les > autres cas que 80 colonnes. J'entends ces arguments. Personnellement, je trouve que même avec un écran plus large, 72 ou 80 colonnes est plus agréable à lire (des lignes trop longues sont perturbantes), mais pour le cas d'un écran ou d'un tampon vim moins large, c'est toi qui as raison, c'est très désagréable d'avoir la fin de chaque ligne qui dépasse. > Un éditeur est censé adapter la ligne comme > il faut. Si less ne fait pas ça, un « vim -R » le remplacera > avantageusement. Non, pas avantageusement. Le lancement de Vim n'est pas instantané, la navigation est moins pratique que dans less (pas possible de monter et descendre d'une ligne avec les flèches ou j/k, il faut que le curseur soit tout en haut ou tout en bas pour que ça marche). Et en plus, encore faut-il que Vim soit installé et configuré pour couper les lignes entre les mots. > Je viens de te désactiver l'écho sur la liste de diffusion. Ah merci, j'ignorais que c'était un paramètre personnel. -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: non disponible Type: application/pgp-signature Taille: 819 octets Desc: non disponible URL: From thomas.preudhomme at celest.fr Wed Sep 10 15:23:47 2014 From: thomas.preudhomme at celest.fr (Thomas Preud'homme) Date: Wed, 10 Sep 2014 13:23:47 -0000 Subject: =?utf-8?b?W1PDoFQgZGV2XQ==?= =?utf-8?q?=5Bfr=5D_Wix_et_wxPython_3?= =?utf-8?q?=2E0?= In-Reply-To: <54102EAD.5070200@mailoo.org> References: <20140909173348.cff660433019759f585d7b4e@lm7.fr> <20140909184110.81f03e0f770da562430f99a7@lm7.fr> <54102EAD.5070200@mailoo.org> Message-ID: <3572318.4memVpTLBz@mallow.celest.fr> Le mercredi 10 septembre 2014, 12:57:49 Adrien a écrit : > Hi, > > that icon is actually shipped with sat_media. The directory should be > pointed in .sat.conf, for example: > > media_dir = ~/workspace/sat_media > > The default value is /usr/share/sat/media. I'm not sure how sat_media > should be shipped: with the sat-xmpp-core package on with an additionnal > sat-xmpp-media package? The former is more difficult because it's in a different tarball and would require us to use multi-tarball Debian source package. However I suppose sat_media and sat evolve in lockstep so that might make sense. I need to think more about this. Matteo, any opinion about it? Best regards, Thomas -------------- section suivante -------------- Une pièce jointe autre que texte a été nettoyée... Nom: signature.asc Type: application/pgp-signature Taille: 819 octets Desc: This is a digitally signed message part. URL: