Menu
▾
▴
opensync-devel — The place to coordinate the development of OpenSync
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(9) |
Apr
(84) |
May
(18) |
Jun
(12) |
Jul
(6) |
Aug
(7) |
Sep
(10) |
Oct
(31) |
Nov
(59) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(53) |
Feb
(15) |
Mar
(43) |
Apr
(40) |
May
(63) |
Jun
(142) |
Jul
(54) |
Aug
(31) |
Sep
(30) |
Oct
(39) |
Nov
(36) |
Dec
(64) |
| 2007 |
Jan
(128) |
Feb
(261) |
Mar
(156) |
Apr
(127) |
May
(76) |
Jun
(131) |
Jul
(83) |
Aug
(124) |
Sep
(83) |
Oct
(88) |
Nov
(180) |
Dec
(90) |
| 2008 |
Jan
(86) |
Feb
(93) |
Mar
(117) |
Apr
(104) |
May
(65) |
Jun
(35) |
Jul
(38) |
Aug
(111) |
Sep
(58) |
Oct
(33) |
Nov
(102) |
Dec
(194) |
| 2009 |
Jan
(193) |
Feb
(74) |
Mar
(111) |
Apr
(77) |
May
(31) |
Jun
(20) |
Jul
(1) |
Aug
(3) |
Sep
(57) |
Oct
(125) |
Nov
(50) |
Dec
(3) |
| 2010 |
Jan
(26) |
Feb
(5) |
Mar
(13) |
Apr
(3) |
May
(3) |
Jun
(12) |
Jul
(27) |
Aug
(47) |
Sep
(105) |
Oct
(53) |
Nov
(34) |
Dec
(21) |
| 2011 |
Jan
(115) |
Feb
(17) |
Mar
|
Apr
(6) |
May
(16) |
Jun
(15) |
Jul
(85) |
Aug
(21) |
Sep
(13) |
Oct
(12) |
Nov
(28) |
Dec
(23) |
| 2012 |
Jan
|
Feb
(13) |
Mar
(4) |
Apr
|
May
(1) |
Jun
(5) |
Jul
(5) |
Aug
(31) |
Sep
(8) |
Oct
|
Nov
|
Dec
(1) |
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(33) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(4) |
| 2016 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: Michael B. <mb...@gm...> - 2010-09-17 09:30:30
|
On Wed, Sep 15, 2010 at 03:10:48AM -0400, Chris Frey wrote: > On Wed, Sep 15, 2010 at 03:01:45AM -0400, Chris Frey wrote: > > and with 0.22 gone in Debian > > Just to clarify, there is no opensync in the next release of Debian stable, > which will be Squeeze. Neither 0.22, nor 0.39. There is no danger > of conflict if 0.39 is in unstable. It will certainly be possible to support opensync-0.3x in backports once squeeze is released and opensync stabilizes. Michael |
|
From: Emanoil K. <del...@ya...> - 2010-09-17 08:16:36
|
svn co https://svn.opensync.org/plugins/akonadi-sync/trunk akonadi-sync so this should be it. let me know if I miss something regards |
|
From: Chris F. <cd...@fo...> - 2010-09-17 05:45:04
|
On Thu, Sep 16, 2010 at 01:46:51PM -0700, Emanoil Kotsev wrote:
> [1284668404.203389] ERROR: Broken Pipe
Hi Emanoil,
This usually means one of the plugins crashed. Make sure to turn on
core dumps, be sure to set your plugin to run as a process, and then
it is usually something like this to get a backtrace:
gdb /path/to/osplugin core
You can set to run as process with a patch like this in your
get_sync_info() function:
@@ -220,6 +220,7 @@ osync_bool get_sync_info(OSyncPluginEnv *env, OSyncError **error)
osync_plugin_set_initialize(plugin, evo2_initialize);
osync_plugin_set_finalize(plugin, evo2_finalize);
osync_plugin_set_discover(plugin, evo2_discover);
+ osync_plugin_set_start_type(plugin, OSYNC_START_TYPE_PROCESS);
if (!osync_plugin_env_register_plugin(env, plugin, error))
goto error;
- Chris
|
|
From: Chris F. <cd...@fo...> - 2010-09-17 05:38:21
|
On Thu, Sep 16, 2010 at 10:54:48PM -0400, Adenilson Cavalcanti wrote: > Your fix was really appreciated, You're welcome... it's good to improve the state of computing bit by bit. > I hope to see new contributions coming from you in a near future. :-) Speaking of which, does my const patch look good enough to include in 0.9.7? :-) - Chris |
|
From: Adenilson C. <cav...@gm...> - 2010-09-17 02:54:57
|
Chris Sweet! Let's hope that libgcal 0.9.6 gets packaged fast for Debian. Your fix was really appreciated, I hope to see new contributions coming from you in a near future. :-) Best regards Adenilson On Thu, Sep 16, 2010 at 8:10 PM, Chris Frey <cd...@fo...> wrote: > Hi Adenilson, > > I just noticed today that you had released libgcal 0.9.6 back on the 7th. > I've updated the google-calendar to use it, and the plugin now requires > version 0.9.6 due to the segfault fix. > > I'm about to file a release-critical bug for Debian Squeeze, so that > the libxml segfault fix gets in before release. > > Thanks for the new version, > - Chris > > |
|
From: Chris F. <cd...@fo...> - 2010-09-17 00:10:24
|
Hi Adenilson, I just noticed today that you had released libgcal 0.9.6 back on the 7th. I've updated the google-calendar to use it, and the plugin now requires version 0.9.6 due to the segfault fix. I'm about to file a release-critical bug for Debian Squeeze, so that the libxml segfault fix gets in before release. Thanks for the new version, - Chris |
|
From: Daniel G. <go...@b1...> - 2010-09-16 23:51:34
|
On Friday, September 17, 2010 06:27:51 am Emanoil Kotsev wrote: > I had a good progress and now discover is working at 100%. However the > tricky sync part is still an issue, but I think one would like to have a > look. So what about this svn access? Please create an account in opensnyc.org trac and send me your username. Subversion directory got already created. But i need your username to assign you write access. Best Regards, Daniel -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner Linux Consultant & Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
|
From: Emanoil K. <del...@ya...> - 2010-09-16 20:46:57
|
yes, please,
I have a very interesting messages in the trace which is beyond my knowledge ATM. I'm working on the actual data sync now, but it looks like I would need some more time.
The thing is to get the actual handling of the changes to work.
[1284668404.196505] <<<<<<< osync_archive_create_changes
[1284668404.196530] >>>>>>> osync_db_query(0x2329e90, DELETE FROM tbl_changes W
HERE objtype='contact', 0x7f9913621cf8)
[1284668404.196616] <<<<<<< osync_db_query
[1284668404.196639] <<<<<<< osync_archive_flush_changes
[1284668404.196660] <<<<<<< osync_mapping_table_flush
...
...
...
[1284668404.201398] <<<<<<< osync_archive_create_changelog
[1284668404.201423] >>>>>>> osync_db_query_table(0x2329e90, SELECT memberid, ma
ppingid, changetype FROM tbl_changelog WHERE objtype='todo' ORDER BY mappingid, 0x7f9913621cf8)
[1284668404.201539] <<<<<<< osync_db_query_table: (nil)
[1284668404.201575] >>>>>>> osync_db_free_list((nil))
[1284668404.201596] <<<<<<< osync_db_free_list
[1284668404.201616] <<<<<<< osync_archive_load_ignored_conflicts
[1284668404.201636] <<<<<<< _inject_changelog_entries
[1284668404.201656] <<<<<<< osync_obj_engine_initialize
[1284668404.201677] >>>>>>> osync_obj_engine_command(0x24e7600:todo, CONNECTED, 0x7f9913621cf8)
[1284668404.201699] >>>>>>> osync_client_proxy_connect(0x247ca00, 0x7f9928d60630, 0x7f990c000d2
0, todo, 1, 0x7f9913621cf8)
[1284668404.201725] >>>>>>> osync_queue_send_message_with_timeout(0x24d9230, 0x24d8140,
0x7f990c002370, 30, 0x7f9913621cf8)
[1284668404.201748] Setting id -8041691830782491556 for pending reply
[1284668404.201789] <<<<<<< osync_queue_send_message_with_timeout
[1284668404.201812] <<<<<<< osync_client_proxy_connect
[1284668404.201833] >>>>>>> osync_client_proxy_connect(0x24d88f0, 0x7f9928d60630, 0x7f990c000d5
0, todo, 1, 0x7f9913621cf8)
[1284668404.201857] >>>>>>> osync_queue_send_message_with_timeout(0x24dea00, 0x24deda0,
0x7f990c0024d0, 30, 0x7f9913621cf8)
[1284668404.201880] Setting id -8041691830773854619 for pending reply
[1284668404.201944] <<<<<<< osync_queue_send_message_with_timeout
[1284668404.201968] <<<<<<< osync_client_proxy_connect
[1284668404.201988] <<<<<<< osync_obj_engine_command
[1284668404.202009] <<<<<<< osync_engine_command
[1284668404.202029] <<<<<<< _command_dispatch: Done dispatching
[1284668404.203127] >>>>>>> _incoming_dispatch(0x24d8140)
[1284668404.203157] queue->pendingCount = 5, queue->pendingLimit = 0
[1284668404.203180] Dispatching 0x24e6ae0:22(OSYNC_MESSAGE_QUEUE_HUP), timeout=0, id=0
[1284668404.203216] >>>>>>> _osync_client_proxy_message_handler(0x24e6ae0, 0x247ca00)
[1284668404.203237] proxy received command 22
[1284668404.203258] <<<<<<< _osync_client_proxy_message_handler
[1284668404.203280] Dispatching 0x24e8ae0:12(OSYNC_MESSAGE_ERRORREPLY), timeout=0, id=-8041691834889726164
[1284668404.203302] >>>>>>> _osync_queue_remove_pending_reply(0x24d8140, 0x24e8ae0, 1)
[1284668404.203323] Searching for pending message id=-8041691834889726164
[1284668404.203344] Found pending message id=-8041691834889726164: 0x24e6c10
[1284668404.203365] >>>>>>> _osync_client_proxy_connect_handler(0x24e8ae0, 0x24e6e90)
[1284668404.203389] ERROR: Broken Pipe
[1284668404.203426] >>>>>>> _osync_engine_connect_callback(0x247ca00, 0x23124d0, 0, 0x7f990c002
3c0)
[1284668404.203456] >>>>>>> osync_status_update_member(0x23124d0, 0x21713d0, 3, (null),
0x7f990c0023c0)
[1284668404.203482] >>>>>>> member_status(0x7f990c002810, (nil))
[1284668404.203526] <<<<<<< member_status
[1284668404.203548] <<<<<<< osync_status_update_member
[1284668404.203649] <<<<<<< _osync_engine_connect_callback
[1284668404.203671] <<<<<<< _osync_client_proxy_connect_handler
[1284668404.203691] <<<<<<< _osync_queue_remove_pending_reply
[1284668404.203714] Dispatching 0x24e7aa0:12(OSYNC_MESSAGE_ERRORREPLY), timeout=0, id=-8041691834889726164
[1284668404.203736] >>>>>>> _osync_queue_remove_pending_reply(0x24d8140, 0x24e7aa0, 1)
[1284668404.203756] Searching for pending message id=-8041691834889726164
[1284668404.203777] <<<<<<< _osync_queue_remove_pending_reply
|
|
From: Björn R. <bjo...@go...> - 2010-09-16 18:42:03
|
Daniel, could you create an akonadi-sync plugin directory? I really would like to look at the code :-) Thanks in advance! Am 16.09.2010 um 20:27 schrieb Emanoil Kotsev: > hi, > > I had a good progress and now discover is working at 100%. However the tricky sync part is still an issue, but I think one would like to have a look. So what about this svn access? > > regards |
|
From: Emanoil K. <del...@ya...> - 2010-09-16 18:27:57
|
hi,
I had a good progress and now discover is working at 100%. However the tricky sync part is still an issue, but I think one would like to have a look. So what about this svn access?
regards
|
|
From: Juha T. <Juh...@ik...> - 2010-09-16 08:46:39
|
On Thursday 16 September 2010 00:23:23 Michael Banck wrote: > On Wed, Sep 15, 2010 at 12:56:59PM +0300, Juha Tuomala wrote: > > Yes he has. let's just not forget, that opensync project's deliverable > > is only library - much like glibc. > > Eh - opensync ships plugins and a reference client implementation as > well. Yes it does. Tuju -- Better to have one, and not need it, than to need one and not have it. |
|
From: Michael B. <mb...@gm...> - 2010-09-15 21:23:32
|
On Wed, Sep 15, 2010 at 12:56:59PM +0300, Juha Tuomala wrote: > Yes he has. let's just not forget, that opensync project's deliverable > is only library - much like glibc. Eh - opensync ships plugins and a reference client implementation as well. Michael |
|
From: Emanoil K. <del...@ya...> - 2010-09-15 14:59:34
|
Hi,
--- On Wed, 9/15/10, ope...@li... <ope...@li...> wrote:
> From: ope...@li... <ope...@li...>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 15 Sep 2010 03:01:45 -0400
> From: Chris Frey <cd...@fo...>
> Subject: Re: [Opensync-devel] Updating debian unstable
> To: Daniel Gollub <go...@b1...>
> Cc: ope...@li...
> Message-ID: <201...@fo...>
> Content-Type: text/plain; charset=us-ascii
>
> On Wed, Sep 15, 2010 at 06:56:13PM +1200, Daniel Gollub
> wrote:
> > Actually we asked all distros to not package 0.3x ...
> i guess thats the
> > reason. I would prefer to keep it like that, without
> complete capabilities
> > implementation a slow-sync will cause data-loss or
> every single entry
> > duplicated. Without this and with 0.3x packages in
> Distros, people would
> > install them and turn their "productive" device into a
> "testing" device
> > without knowing it ...
>
> Oh no, not for official release, but there is already a
> libopensync1exp7
> package in debian unstable which is out of date, and with
> 0.22 gone in
> Debian, there's no harm anymore in 0.39 staying in the
> unstable and
> experimental trees.
>
I don't think that 0.22 is useful for anything especially for me with 3-4 different phones and KDE in the past few years ... If someone is using this really for syncing mobiles then please let me know what kind of phone (vendor, model) are you using and how you are doing it?
Time ago when I asked about it, someone told me, he is doing one way sync ??! It's too long to explain, but well, so doesn't matter what comes shipped it's not working and it will most probably not work at least for me. That's why I decided to have at least a look into the code and see why?!
I've checked now squeez and there is no opensync in there. It means that there will be no opensync in next stable as sid is frozen for some time now
In sid there is 0.39 and 0.22. My goal is to help porting testing documenting whatever needed to get it somehow working and useful for/in the next debian life cycle.
It can not be considered working until it can sync contact/calendar/event and todos with most widly used phones ... i.e. syncml
So as for debian you better push 0.4X to go into sid NOW, as it will become very soon testing.
regards
|
|
From: Juha T. <Juh...@ik...> - 2010-09-15 09:57:09
|
On Wednesday 15 September 2010 12:11:21 Chris Frey wrote: > On Wed, Sep 15, 2010 at 11:36:48AM +0300, Juha Tuomala wrote: > > We had such blurp for long time and for reason. denisq during his > > front page editing hosed > > > > http://opensync.org/wiki/WikiStart?action=diff&version=139&old_version=138 > > > > is for some reason, my guess is that he thought that makes opensync sound > > like unfinished - something that it is. > > I don't think such a blurb needs to be on the front page. > Under the "development version", yes. It was decided quite some time ago that it needed to be there. > Quentin has done good work, and given the front page a much needed > facelift. Yes he has. let's just not forget, that opensync project's deliverable is only library - much like glibc. > If others care enough to do the work, and good work at that, > why complain about it? We *need* someone to take care of the wiki. Shall we not mix complaining and argumenting with valid points please. That was put there because we were worried that people were associating dataloss and opensync to each other. And actually also worried that it *is* possible to lose information. It's hard to notice that from phone interface if you have few hundred entries and some of them have lost some field's content. There is a reason why 0.2x branch was ditched, why the 0.4 has not been released yet, just like dgollub already pointed out in earlier message. Tuju -- Better to have one, and not need it, than to need one and not have it. |
|
From: Juha T. <Juh...@ik...> - 2010-09-15 09:51:20
|
On Wednesday 15 September 2010 11:48:17 Daniel Gollub wrote: > On Wednesday, September 15, 2010 08:36:48 pm Juha Tuomala wrote: > > My question is, what is the gain from having anyone to log in and > > change wiki compared to manually created accounts? It would kill spamming > > that we've been targeted for years at least. I've a feeling that > > nobody of old farts is looking after what goes on in wiki these days. > > Good point ... could you start a different thread about that? So, does that wiki/trac support it if we would want to switch off that open account creating? There were couple other admin tasks too, but waiting for 0.4 release. Should we do them before if this release is still going to take some time? Tuju -- Better to have one, and not need it, than to need one and not have it. |
|
From: Chris F. <cd...@fo...> - 2010-09-15 09:11:29
|
On Wed, Sep 15, 2010 at 11:36:48AM +0300, Juha Tuomala wrote: > We had such blurp for long time and for reason. denisq during his > front page editing hosed > > http://opensync.org/wiki/WikiStart?action=diff&version=139&old_version=138 > > is for some reason, my guess is that he thought that makes opensync sound > like unfinished - something that it is. I don't think such a blurb needs to be on the front page. Under the "development version", yes. Quentin has done good work, and given the front page a much needed facelift. And considering that I use both 0.22 and 0.39 in development, and have not run into this "losing all your data" bug, I assumed it was getting close to finished as well. > The fact is that until those folks who can write those missing core > parts, there is not that much that others can do. I can write it, and I'm trying to get up to speed so I can write it soon. It is not rocket science, even though we tend to complicate matters a fair bit. I'm also trying to encourage anyone willing to pick up a compiler and port a plugin. The more we help each other, the closer we'll get. > I've a feeling that nobody of old farts is looking after what > goes on in wiki these days. If others care enough to do the work, and good work at that, why complain about it? We *need* someone to take care of the wiki. - Chris |
|
From: Chris F. <cd...@fo...> - 2010-09-15 08:53:30
|
On Wed, Sep 15, 2010 at 08:22:45PM +1200, Daniel Gollub wrote: > Too make it more scary .. just add "... contain serve bugs, which cause > complete data-loss or duplicate all your data". Duplicating all your data, I know, and potentially hanging in a busy loop, but which bug causes complete data-loss? Is this an engine bug? - Chris |
|
From: Daniel G. <go...@b1...> - 2010-09-15 08:49:01
|
On Wednesday, September 15, 2010 08:36:48 pm Juha Tuomala wrote: > We had such blurp for long time and for reason. denisq during his > front page editing hosed > > http://opensync.org/wiki/WikiStart?action=diff&version=139&old_version=138 > > is for some reason, my guess is that he thought that makes opensync sound > like unfinished - something that it is. Could you move that back on the front page? > > The fact is that until those folks who can write those missing core > parts, there is not that much that others can do. Removing that warning > label from front page is just going to make people upset again > what it did earlier and why it was put there in the first place. > > Loosing your valuable contacts during your first attempt of backuping > with opensync is something that I would get pissed off too. > > My question is, what is the gain from having anyone to log in and > change wiki compared to manually created accounts? It would kill spamming > that we've been targeted for years at least. I've a feeling that > nobody of old farts is looking after what goes on in wiki these days. Good point ... could you start a different thread about that? -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner Linux Consultant & Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
|
From: Juha T. <Juh...@ik...> - 2010-09-15 08:37:00
|
On Wednesday 15 September 2010 10:26:45 Chris Frey wrote: > Can you write a quick warning blurb in reply, that we can use on the wiki? > Something that includes what functionality is missing, so that developers > might be tempted to fix it. > > A page on the wiki that points to binary packages for testing purposes > would be helpful, and should have such a warning for all to see. > Quentin or I can set that up. We had such blurp for long time and for reason. denisq during his front page editing hosed http://opensync.org/wiki/WikiStart?action=diff&version=139&old_version=138 is for some reason, my guess is that he thought that makes opensync sound like unfinished - something that it is. The fact is that until those folks who can write those missing core parts, there is not that much that others can do. Removing that warning label from front page is just going to make people upset again what it did earlier and why it was put there in the first place. Loosing your valuable contacts during your first attempt of backuping with opensync is something that I would get pissed off too. My question is, what is the gain from having anyone to log in and change wiki compared to manually created accounts? It would kill spamming that we've been targeted for years at least. I've a feeling that nobody of old farts is looking after what goes on in wiki these days. Tuju -- Better to have one, and not need it, than to need one and not have it. |
|
From: Daniel G. <go...@b1...> - 2010-09-15 08:23:18
|
On Wednesday, September 15, 2010 07:26:45 pm Chris Frey wrote: > On Wed, Sep 15, 2010 at 07:18:19PM +1200, Daniel Gollub wrote: > > I see. But please make sure that people know what they are really doing > > once they install those packages. > > Point taken. > > Can you write a quick warning blurb in reply, that we can use on the wiki? > Something that includes what functionality is missing, so that developers > might be tempted to fix it. > > A page on the wiki that points to binary packages for testing purposes > would be helpful, and should have such a warning for all to see. > Quentin or I can set that up. > > If I wrote the blurb, I'd probably be too optimistic. :-) We used to have this on the WikiStart page: ---8<-- Releases 0.22 (and 0.2x svn branch) and before are considered stable and suitable for production. 0.3x releases introduce major architecture and API changes and are targeted for developers and testers only and may not even compile or are likely to contain severe bugs. 0.3x releases are not recommended for end users or distribution packaging. --->8-- http://opensync.org/wiki/WikiStart?version=57 Too make it more scary .. just add "... contain serve bugs, which cause complete data-loss or duplicate all your data". Best Regards, Daniel -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner Linux Consultant & Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
|
From: Chris F. <cd...@fo...> - 2010-09-15 07:36:18
|
On Wed, Sep 15, 2010 at 09:22:28AM +0200, Michael Banck wrote: > It is not out of date, it is the currently released development release, > as far as I know. Also 0.22, is still in the stable release, it is not > gone from Debian entirely, just from testing/unstable. (There was talk > about reviving 0.22 just for the python plugins, which apparently seem > to work well for some people still, but I did not get around it so far, > and with the freeze in effect I doubt it is doable) If 0.22 could return to Squeeze, that would be great. Let me know how I can help, because that would make my life easier. > We could package subversion snapshots as well, but for the first part of > 2010, I was not aware of any major advances in opensync which would have > warranted that. I think it is less about progress made or not, and more about having an automated system for creating binary packages for people who just want to run a quick test and help developers. > Note that libopensync1exp* has to be manually approved for each new > version right now as the API keeps changing and so does the package > name, so I am not sure very frequent uploads make that much sense. That's something I didn't know... so perhaps Debian unstable is the wrong place to do this package work. It is just a prime target, because Debian is a great place to get software. :-) When I saw 0.39, I assumed great things. > There's no danger of Debian shipping 0.3x in the next stable release, at > least :) :-) - Chris |
|
From: Chris F. <cd...@fo...> - 2010-09-15 07:26:55
|
On Wed, Sep 15, 2010 at 07:18:19PM +1200, Daniel Gollub wrote: > I see. But please make sure that people know what they are really doing once > they install those packages. Point taken. Can you write a quick warning blurb in reply, that we can use on the wiki? Something that includes what functionality is missing, so that developers might be tempted to fix it. A page on the wiki that points to binary packages for testing purposes would be helpful, and should have such a warning for all to see. Quentin or I can set that up. If I wrote the blurb, I'd probably be too optimistic. :-) Thanks, - Chris |
|
From: Michael B. <mb...@gm...> - 2010-09-15 07:22:38
|
Hi, On Wed, Sep 15, 2010 at 03:01:45AM -0400, Chris Frey wrote: > On Wed, Sep 15, 2010 at 06:56:13PM +1200, Daniel Gollub wrote: > > Actually we asked all distros to not package 0.3x ... i guess thats the > > reason. I would prefer to keep it like that, without complete capabilities > > implementation a slow-sync will cause data-loss or every single entry > > duplicated. Without this and with 0.3x packages in Distros, people would > > install them and turn their "productive" device into a "testing" device > > without knowing it ... > > Oh no, not for official release, but there is already a libopensync1exp7 > package in debian unstable which is out of date, and with 0.22 gone in > Debian, there's no harm anymore in 0.39 staying in the unstable and > experimental trees. It is not out of date, it is the currently released development release, as far as I know. Also 0.22, is still in the stable release, it is not gone from Debian entirely, just from testing/unstable. (There was talk about reviving 0.22 just for the python plugins, which apparently seem to work well for some people still, but I did not get around it so far, and with the freeze in effect I doubt it is doable) We could package subversion snapshots as well, but for the first part of 2010, I was not aware of any major advances in opensync which would have warranted that. Note that libopensync1exp* has to be manually approved for each new version right now as the API keeps changing and so does the package name, so I am not sure very frequent uploads make that much sense. > > Once capabilities support got implemented i'm happy with realsing 0.40 and > > lift the package ban. Anything else would be releasing software which is > > broken. > > I don't want to see any distro including 0.39 in official releases. > This is for testing. Users would test things for us if there > were binary packages available. Right now I end up on IRC trying to > help people compile, or trying to figure out why old binary packages > don't work. :-) There's no danger of Debian shipping 0.3x in the next stable release, at least :) Michael |
|
From: Daniel G. <go...@b1...> - 2010-09-15 07:19:20
|
On Wednesday, September 15, 2010 07:01:45 pm Chris Frey wrote: > > Once capabilities support got implemented i'm happy with realsing 0.40 > > and lift the package ban. Anything else would be releasing software > > which is broken. > > I don't want to see any distro including 0.39 in official releases. > This is for testing. Users would test things for us if there > were binary packages available. Right now I end up on IRC trying to > help people compile, or trying to figure out why old binary packages > don't work. :-) I see. But please make sure that people know what they are really doing once they install those packages. -- Daniel Gollub Geschaeftsfuehrer: Ralph Dehner Linux Consultant & Developer Unternehmenssitz: Vohburg B1 Systems GmbH Amtsgericht: Ingolstadt Mobil: +49-(0)-160 47 73 970 Handelsregister: HRB 3537 EMail: go...@b1... http://www.b1-systems.de Adresse: B1 Systems GmbH, Osterfeldstraße 7, 85088 Vohburg http://pgpkeys.pca.dfn.de/pks/lookup?op=get&search=0xED14B95C2F8CA78D |
|
From: Chris F. <cd...@fo...> - 2010-09-15 07:10:58
|
On Wed, Sep 15, 2010 at 03:01:45AM -0400, Chris Frey wrote: > and with 0.22 gone in Debian Just to clarify, there is no opensync in the next release of Debian stable, which will be Squeeze. Neither 0.22, nor 0.39. There is no danger of conflict if 0.39 is in unstable. - Chris |
90 messages has been excluded from this view by a project administrator.
