On Tue, 17 Oct 2017 00:12:15 +0200, Klemens Nanni
wrote:
> Updated diff below.
Thanks, committed. I removed pkg/MESSAGE, users should read release
notes.
Cheers,
Daniel
On Mon, Oct 16, 2017 at 06:04:52PM -0400, Daniel Jakots wrote:
> On Mon, 9 Oct 2017 23:21:29 +0200, Klemens Nanni wrote:
>
> > -HOMEPAGE= http://isync.sourceforge.net/
> > +HOMEPAGE= https://isync.sourceforge.net/
>
> It doesn't work here.
>
> $ curl -I http://isync.sourceforge.net/
> HTTP/1.
On Mon, 9 Oct 2017 23:21:29 +0200, Klemens Nanni wrote:
> -HOMEPAGE=http://isync.sourceforge.net/
> +HOMEPAGE=https://isync.sourceforge.net/
It doesn't work here.
$ curl -I http://isync.sourceforge.net/
HTTP/1.1 200 OK
[...]
$ curl -I https://isync.sourceforge.net/
curl: (7) Failed to c
On Mon, Oct 09, 2017 at 09:21:29PM +, Klemens Nanni wrote:
> Simple version bump to the new feature release, including the following
> notable changes amongst other bug fixes:
>
> - Network timeout handling
> - Support for proper Maildir++ and a Maildir sub-folder naming style
> without extr
Simple version bump to the new feature release, including the following
notable changes amongst other bug fixes:
- Network timeout handling
- Support for proper Maildir++ and a Maildir sub-folder naming style
without extra dots
- Support for TLS client certificates
- Support for recovering from
On Thu, 10 Aug 2017 10:07:34 +0200, Klemens Nanni
wrote:
> Does anyone want to commit this?
Thanks, committed!
On Thu, Aug 10, 2017 at 5:33 AM, Daniel Jakots wrote:
> On Thu, 10 Aug 2017 02:53:59 +0200, Klemens Nanni
> wrote:
>
>> > I'm not entirely sure yet whether the introduced patch to get
>> > X509_OBJECT_get0_X509() and X509_STORE_get0_objects() working is the
>> > way to go, maybe someone more know
On Wed, Aug 09, 2017 at 11:33:09PM -0400, Daniel Jakots wrote:
> On Thu, 10 Aug 2017 02:53:59 +0200, Klemens Nanni
> wrote:
>
> > > I'm not entirely sure yet whether the introduced patch to get
> > > X509_OBJECT_get0_X509() and X509_STORE_get0_objects() working is the
> > > way to go, maybe someo
On Thu, 10 Aug 2017 02:53:59 +0200, Klemens Nanni
wrote:
> > I'm not entirely sure yet whether the introduced patch to get
> > X509_OBJECT_get0_X509() and X509_STORE_get0_objects() working is the
> > way to go, maybe someone more knowledgable about OpenSSL internals
> > can comment/fix this?
> +
On Thu, Aug 10, 2017 at 01:17:07AM +0200, Klemens Nanni wrote:
> On Wed, Aug 09, 2017 at 06:53:47PM -0400, Daniel Jakots wrote:
> > On Wed, 9 Aug 2017 23:58:33 +0200, Klemens Nanni wrote:
> >
> > > Other than that a trivial version bump suffices
> >
> > Then can you please send a diff rather tha
On Wed, Aug 09, 2017 at 06:53:47PM -0400, Daniel Jakots wrote:
> On Wed, 9 Aug 2017 23:58:33 +0200, Klemens Nanni wrote:
>
> > Other than that a trivial version bump suffices
>
> Then can you please send a diff rather than a .tgz?
I sent a tarball since the new patch wouldn't be included in the
On Wed, 9 Aug 2017 23:58:33 +0200, Klemens Nanni wrote:
> Other than that a trivial version bump suffices
Then can you please send a diff rather than a .tgz?
Cheers,
Daniel
1.2.1 is over two years old, 1.2.2 was released this week.
I'm not entirely sure yet whether the introduced patch to get
X509_OBJECT_get0_X509() and X509_STORE_get0_objects() working is the way
to go, maybe someone more knowledgable about OpenSSL internals can
comment/fix this?
Other than that a
Hi!
New version of isync was released earlier today. It features support
for SASL, changes in configuration file, "isync" deprecation and changes
in output.
Unfortunately, they use memcpy for overlapping regions, so patch is now
needed.
Comments? OKs?
--
Dmitrij D. Czarkoff
Index: Makefile
=
On 2015/04/01 17:39, Zé Loff wrote:
> On Wed, Apr 01, 2015 at 01:20:49PM -0300, Gleydson Soares wrote:
> > could you try to reproduce again?
> > isync doesn't segs here. (@amd64)
>
> mbsync (not this version though, the one on amd64 -current) segfaults
> every time it can't resolve the server name
Edd Barrett said:
> On Mon, Mar 30, 2015 at 12:55:33PM +0200, Dmitrij D. Czarkoff wrote:
> > Any test reports?
>
> I've been using this for a while (mbsync at least).
>
> I notice that the isync command segs. Not looked into it, but I have no
> .isyncrc file (only a .mbsyncrc), so that may be why
On Wed, Apr 01, 2015 at 01:20:49PM -0300, Gleydson Soares wrote:
> could you try to reproduce again?
> isync doesn't segs here. (@amd64)
mbsync (not this version though, the one on amd64 -current) segfaults
every time it can't resolve the server name, and has been doing so for a
while now. I've be
could you try to reproduce again?
isync doesn't segs here. (@amd64)
On Wed, Apr 1, 2015 at 12:59 PM, Edd Barrett wrote:
> On Mon, Mar 30, 2015 at 12:55:33PM +0200, Dmitrij D. Czarkoff wrote:
>> Any test reports?
>
> I've been using this for a while (mbsync at least).
>
> I notice that the isync c
On Mon, Mar 30, 2015 at 12:55:33PM +0200, Dmitrij D. Czarkoff wrote:
> Any test reports?
I've been using this for a while (mbsync at least).
I notice that the isync command segs. Not looked into it, but I have no
.isyncrc file (only a .mbsyncrc), so that may be why.
--
Best Regards
Edd Barrett
These days, MESSAGE is only displayed by pkg_add -u if it has changed from the
previous version (rather than for every update), so it seems a useful place for
information like this - not to intrusive and more likely to be seen by the
right people than a faq/current.html entry.
On 1 April 2015 0
Gleydson Soares said:
> >> +++ openbsd-wip/mail/isync/pkg/MESSAGE Mon Mar 9 14:25:35 2015
> >> @@ -0,0 +1,2 @@
> >> +Gmail users upgrading from isync-1.0.x, note: now mbsync recurses into
> >> "[Gmail]"
> >> +IMAP folder, so changes to mbsync configuration may be needed.
>
> convert to pkg-r
Dmitrij D. Czarkoff writes:
> Any test reports?
works here. sync fine with a large mailbox.
>> +++ openbsd-wip/mail/isync/pkg/MESSAGE Mon Mar 9 14:25:35 2015
>> @@ -0,0 +1,2 @@
>> +Gmail users upgrading from isync-1.0.x, note: now mbsync recurses into
>> "[Gmail]"
>> +IMAP folder, so c
Any test reports?
Dmitrij D. Czarkoff said:
> Hi!
>
> Below is an update for mail/isync (1.0.6 => 1.1.2).
>
> --
> Dmitrij D. Czarkoff
>
> diff -Nurx CVS mail/isync/Makefile openbsd-wip/mail/isync/Makefile
> --- mail/isync/Makefile Mon Mar 9 10:10:11 2015
> +++ openbsd-wip/mail/isync/Ma
Hi!
Below is an update for mail/isync (1.0.6 => 1.1.2).
--
Dmitrij D. Czarkoff
diff -Nurx CVS mail/isync/Makefile openbsd-wip/mail/isync/Makefile
--- mail/isync/Makefile Mon Mar 9 10:10:11 2015
+++ openbsd-wip/mail/isync/Makefile Mon Mar 9 14:25:35 2015
@@ -2,7 +2,7 @@
COMMENT= s
An update to isync / mbsync, a mail synchronizer similar offlineimap.
The version in ports (1.0.6) is now several releases behind the latest
(1.1.2).
Works well for me on amd64. Diff attached. This is my first ports
submission: I've made what I think are the minimal possible changes to
what's in
update mail/isync to 1.1.1
changelog:
http://sourceforge.net/projects/isync/files/isync/1.1.0/
http://sourceforge.net/projects/isync/files/isync/1.1.1/
works fine here.
OK?
Index: Makefile
===
RCS file: /cvs/ports/mail/isync
26 matches
Mail list logo
