Re: [Owfs-developers] 3.1p1 release, anyone?

Jan Kandziora wrote: > Yeah, I'm going to include the > 100-fix-netlink-w1-status-message-detection.patch. Do you have an email > address of marcin1j so we can attribute it properly? Unfortunately not. I just found the discussion on

Re: [Owfs-developers] 3.1p1 release, anyone?

Jan Kandziora wrote: > I think it's enough stuff for a new release, since the last one which was > in March. Would you mind adding these patches as well: https://github.com/marcin1j/openwrt-packages/tree/develop/utils/owfs/patches Without them owfs won't work on recent Raspbian

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 01.12.2015 um 14:06 schrieb Sven Geggus: > Jan Kandziora wrote: > >> I think it's enough stuff for a new release, since the last one which was >> in March. > > Would you mind adding these patches as well: >

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 25.11.2015 um 01:13 schrieb Stefano Miccoli: > I have a bug on my RPi: (no time to investigate right now, but reporting, > just in case it can be reproduced). > > start owserver as > > owserver --tester=DS18S20 —debug > > and run (in another terminal) > > owread /10.10EF > > and

Re: [Owfs-developers] 3.1p1 release, anyone?

On 25/11/15 14:56, Jan Kandziora wrote: > Am 25.11.2015 um 10:03 schrieb Stefano Miccoli: >> Cannot check right now, but if I didn’t do something terribly wrong I >> should be at the latest commit on master, so below e85572. >> >> It seems to me that actually e85572 introduced the bug: >> >>

Re: [Owfs-developers] 3.1p1 release, anyone?

On 26/11/15 23:06, Jan Kandziora wrote: > Am 26.11.2015 um 22:55 schrieb Johan Ström: >> Re-adding the -EISDIR check fixes the issue (but, I assume, restore the >> original external issue). >> If we have no proper fix for the original external issue right now, I >> suggest re-adding this check

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 26.11.2015 um 22:55 schrieb Johan Ström: > > Re-adding the -EISDIR check fixes the issue (but, I assume, restore the > original external issue). > If we have no proper fix for the original external issue right now, I > suggest re-adding this check until we do have a proper fix, so at least

Re: [Owfs-developers] 3.1p1 release, anyone?

> On 25 Nov 2015, at 14:56, Jan Kandziora wrote: > >> I understand that ow_get cannot be scrapped right now, but >> it should at least be deprecated. > Well, please suggest a mechanism which does not break existing ownet > language bindings. Or you have to clean up the mess all on

Re: [Owfs-developers] 3.1p1 release, anyone?

Cannot check right now, but if I didn’t do something terribly wrong I should be at the latest commit on master, so below e85572. It seems to me that actually e85572 introduced the bug:

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 25.11.2015 um 10:03 schrieb Stefano Miccoli: > Cannot check right now, but if I didn’t do something terribly wrong I > should be at the latest commit on master, so below e85572. > > It seems to me that actually e85572 introduced the bug: > >

Re: [Owfs-developers] 3.1p1 release, anyone?

I have a bug on my RPi: (no time to investigate right now, but reporting, just in case it can be reproduced). start owserver as owserver --tester=DS18S20 —debug and run (in another terminal) owread /10.10EF and owserver segfaults: CALL: data.c:(144) Read message DEBUG:

Re: [Owfs-developers] 3.1p1 release, anyone?

> On 24 Nov 2015, at 20:03, Matthias Urlichs wrote: > > Not reliably. Killing it (systemctl stop), running it manually under > strace, killing *that* (assuming it doesn't segfault then, which it > sometimes does) and then restarting it (via systemctl start) always > works.

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 25.11.2015 um 01:13 schrieb Stefano Miccoli: > I have a bug on my RPi: (no time to investigate right now, but reporting, > just in case it can be reproduced). > > start owserver as > > owserver --tester=DS18S20 —debug > > and run (in another terminal) > > owread /10.10EF > > and

Re: [Owfs-developers] 3.1p1 release, anyone?

On 25.11.2015 00:42, Stefano Miccoli wrote: > are you sure that owserver is *really* dead? Of course I am. I'll try to investigate more, the next time that happens. Shouldn't be too long. :-/ -- Go from Idea to Many App

Re: [Owfs-developers] 3.1p1 release, anyone?

On 23.11.2015 19:33, Johan Ström wrote: > So, Matthias needs to take a look at what happened with the merges, as > some of the changes (the above + my transaction fix at least) seems to > have been lost. Owch. I seem to have missed that during the branch cleanup I did yesterday. I'll take a

Re: [Owfs-developers] 3.1p1 release, anyone?

On 24.11.2015 17:10, Matthias Urlichs wrote: > I'll take a look ASAP. I have rebased my "master" branch. Seems I mistyped a branch name yesterday. Sorry about that. I'd be even happier with the idea of releasing if somebody found the cause for the persistent hang I have on my raspberry pi, which

Re: [Owfs-developers] 3.1p1 release, anyone?

On 24/11/15 17:56, Matthias Urlichs wrote: > On 24.11.2015 17:10, Matthias Urlichs wrote: >> I'll take a look ASAP. > I have rebased my "master" branch. Seems I mistyped a branch name > yesterday. Sorry about that. Great! For you git new-comers, 'git pull' will most likely not work properly here

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 24.11.2015 um 17:56 schrieb Matthias Urlichs: > On 24.11.2015 17:10, Matthias Urlichs wrote: >> I'll take a look ASAP. > > I have rebased my "master" branch. Seems I mistyped a branch name > yesterday. Sorry about that. > > I'd be even happier with the idea of releasing if somebody found the

Re: [Owfs-developers] 3.1p1 release, anyone?

On 24.11.2015 18:57, Johan Ström wrote: >> > > Great! For you git new-comers, 'git pull' will most likely not work > properly here (due to rebase). I suggest a new checkout (git clone > https://github.com/M-o-a-T/owfs.git) A faster way to do the same thing is: $ git fetch $ git reset --hard

Re: [Owfs-developers] 3.1p1 release, anyone?

On 24.11.2015 19:54, Jan Kandziora wrote: > What do you restart? owserver or the calling program? owserver. After this rigmarole is done and "owdir -s localhost" works again, of course I need to restart the client too. I observe this on a Pi running Jessie. NB, the client is fairly aggressive

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 23.11.2015 um 19:15 schrieb Colin Reese: > No, I am indeed using: > > https://github.com/M-o-a-T/owfs.git > > Where is the main archive? > $ git clone git://git.code.sf.net/p/owfs/code owfs-code Kind regards Jan

Re: [Owfs-developers] 3.1p1 release, anyone?

On 23/11/15 20:20, Jan Kandziora wrote: > Am 23.11.2015 um 19:15 schrieb Colin Reese: >> No, I am indeed using: >> >> https://github.com/M-o-a-T/owfs.git >> >> Where is the main archive? >> > $ git clone git://git.code.sf.net/p/owfs/code owfs-code > > Note that it is the main *owfs* repo. There is

Re: [Owfs-developers] 3.1p1 release, anyone?

I see. I did not grasp that the sf repo was in fact a git repo. That is where I had been grabbing things from, but not with git. C On Mon, Nov 23, 2015 at 11:30 AM, Johan Ström wrote: > On 23/11/15 20:20, Jan Kandziora wrote: > > Am 23.11.2015 um 19:15 schrieb Colin Reese: >

Re: [Owfs-developers] 3.1p1 release, anyone?

Yes, I'm on master. Thanks, Colin On 11/23/2015 10:15 AM, Jan Kandziora wrote: > Am 23.11.2015 um 19:01 schrieb Colin Reese: >> To double check can you point me to it? I've lost things in this pile of >> mails. >> > I see now Matthias has merged the newest changes from the main > repository

Re: [Owfs-developers] 3.1p1 release, anyone?

Actually, it seems the master branch of https://github.com/M-o-a-T/owfs is broken.. In July, a similar bug was fixed (segfault on owdir), which was fixed with https://github.com/M-o-a-T/owfs/pull/2. This has been working fine since then, but after the latest merges into master

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 23.11.2015 um 19:01 schrieb Colin Reese: > To double check can you point me to it? I've lost things in this pile of > mails. > I see now Matthias has merged the newest changes from the main repository two days ago. So there shouldn't be a problem if you'd recompiled the host code yesterday.

Re: [Owfs-developers] 3.1p1 release, anyone?

No, I am indeed using: https://github.com/M-o-a-T/owfs.git Where is the main archive? I don't think I've even ever pulled from that, and a quick google doesn't reveal an obvious location to me. I have been rebuilding 2.9 for some time previous to trying to get these Moat slaves working.

Re: [Owfs-developers] 3.1p1 release, anyone?

I've got my DS490R up and recognizing my Moat device, with a DS18B20 also connected I get: 28.246A5005 alarm F0.18FDE6789C56 simultaneous structure uncached 81.D39F2D00 bus.0 settings statisticssystem Reading the directory gives the following: ls

Re: [Owfs-developers] 3.1p1 release, anyone?

Another datum: Same result on i2c with DS2483. C On 11/23/2015 12:51 AM, Colin Reese wrote: > I've got my DS490R up and recognizing my Moat device, with a DS18B20 > also connected I get: > > 28.246A5005 alarm F0.18FDE6789C56 simultaneous structure uncached > 81.D39F2D00 bus.0

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 23.11.2015 um 09:51 schrieb Colin Reese: > I've got my DS490R up and recognizing my Moat device, with a DS18B20 > also connected I get: > > 28.246A5005 alarm F0.18FDE6789C56 simultaneous structure uncached > 81.D39F2D00 bus.0 settings statisticssystem > > Reading

Re: [Owfs-developers] 3.1p1 release, anyone?

I did not rebuild my slave. Everything else is nice and fresh as of last night. C > On Nov 23, 2015, at 5:42 AM, Jan Kandziora wrote: > >> Am 23.11.2015 um 09:51 schrieb Colin Reese: >> I've got my DS490R up and recognizing my Moat device, with a DS18B20 >> also connected I get:

Re: [Owfs-developers] 3.1p1 release, anyone?

Am 23.11.2015 um 18:22 schrieb Colin Reese: > I did not rebuild my slave. Everything else is nice and fresh as of last > night. > Ok, I ask more specifically: Matthias' owfs archive clone is a bit dated. Did you use that one or have you exported the moat patch and merged it into your main

Re: [Owfs-developers] 3.1p1 release, anyone?

I checked out moat and merged. > On Nov 23, 2015, at 9:56 AM, Jan Kandziora wrote: > >> Am 23.11.2015 um 18:22 schrieb Colin Reese: >> I did not rebuild my slave. Everything else is nice and fresh as of last >> night. > Ok, I ask more specifically: Matthias' owfs archive clone is

Re: [Owfs-developers] 3.1p1 release, anyone?

To double check can you point me to it? I've lost things in this pile of mails. > On Nov 23, 2015, at 9:56 AM, Jan Kandziora wrote: > >> Am 23.11.2015 um 18:22 schrieb Colin Reese: >> I did not rebuild my slave. Everything else is nice and fresh as of last >> night. > Ok, I ask

[Owfs-developers] 3.1p1 release, anyone?

Hi all, we have had some important fixes recently * Paul merged his regex branch. * Johan Ström added support for the LINK aux line. * Paul added some basic support for the Hobbyboards Multitemp. * Thomasz Torcz and Stephano Miccoli fixed the libusb0 problems * I myself fixed the "external"

Re: [Owfs-developers] 3.1p1 release, anyone?

I now have moat version built fine on both 14.04LTS and deb armhf and will do some testing this afternoon/evening with devices. Surely, however, Matthias, has a better idea of whether it's ready for release. C On 11/22/2015 12:39 PM, Jan Kandziora wrote: > Hi all, > > we have had some