[pkg-fso-maint] [openBmap] Inclusion in debian feeds for FSO
onen.om at free.fr
Sun Jun 7 08:46:14 UTC 2009
Sebastian Reichel wrote:
>>> W: openbmap-logger: desktop-entry-contains-unknown-key /usr/share/applications/openBmap.desktop:11 SingleInstance
>> I will try to see if OE uses it.
>> If yes, does it hurt to let this warning?
>> If no, then I will remove it too.
> well it's not part of the freedesktop.org standard for desktop entry
> files . If you won't remove it I can add a patch to the Debian
Interesting link, thanks. I'll try further to get in touch with Open
Embedded people to see if this key is useful. I will then let you know
if I remove it for good.
>> Please, if you do test the package built from something other than a
>> stable version, do not upload. (We can detect and remove the data, but
>> it is easier not to have to ;-) ).
> You should have said so before. The current version in pkg-fso is:
> Sun, 17 May 2009 16:11:45 +0000 (18:11 +0200)
> This is 2 two commits after 0.3 tag. Is this still ok for you or should
> I go back by one commit?
Yes, I should have been clearer, my bad.
No it should be fine. I usually commit stable and tested things. But I
do make more tests before stable, and versionning for the data in
database expects version to correspond to a stable label. As I plan to
label a new stable for you, this won't be an issue any more.
>> Let me know how I can assist you in tests ans so forth. When the git
>> tree has a shape which is good for your packaging, I will test it, and
>> label it to a new stable version.
> A new tag for the next stable version is enough for me. But it would
> be nice if you send a ping to the mailinglist, that there is a new
> version available :)
So where we stand right now. Are the distutils satisfying?
Is the general package, structure, etc. satisfying for your packaging?
Is the logger working fine?
If so, then it means I could label a new stable for you. Otherwise, I
have to make further modifications.
More information about the pkg-fso-maint