These are the channel logs matching your query vdirsyncer
| 2023-01-10 | [15:09:09] <elb> this machine has installed emacs, emacs-guix, guile, khal, vdirsyncer, mutt, profanity, go, sbcl, nss-certs, and glibc-locales, and has a /gnu of 5.6 GB |
| 2023-01-10 | [15:12:26] <nckx> For context, ‘guix size emacs emacs-guix guile khal vdirsyncer mutt profanity go sbcl nss-certs glibc-locales’ → 3114.8 MiB — not saying that's great or can't be improved by motivated packagers but it's not an order of magnitude from 5.6 GiB. |
| 2022-01-18 | [04:43:24] <lfam> At least, vdirsyncer builds when you simply relax the requirement in black's setup.py. I'm now building up to gqrx, which was my other broken package |
| 2022-01-17 | [16:29:41] <johnhamelink> Hey there :) I'm currently an Arch user who's looking to migrate to GNU Guix! My plan is to start by moving all my Emacs & its dependencies and peripheral applications (Emacs packages, mu, isync/mbsync, vdirsyncer, etc) inside a guix foreign install, and then work my way from there. I was using setup.el + straight, so after installing the emacs packages with guix install, and then removing the |
| 2020-11-30 | [23:29:57] <lfam> jonsger: No, I'm not using radicale. It was a test-suite dependency of vdirsyncer, which I am using. IIRC the vdirsyncer author was not very happy with the correctness of radicale, or of dav implementations in general |
| 2020-11-30 | [23:31:08] <lfam> sneek: later tell jonsger: No, I'm not using radicale. It was a test-suite dependency of vdirsyncer, which I am using. IIRC the vdirsyncer author was not very happy with the correctness of radicale, or of dav implementations in general |
| 2020-04-29 | [09:34:26] <efraim> it also came up in vdirsyncer on core-updates and I'm guessing on other python packages we haven't caught yet |
| 2020-04-26 | [19:01:23] <efraim> vdirsyncer failing on core-updates |
| 2020-04-26 | [21:54:45] <efraim> hmm, the copyright in the man page for vdirsyncer says 2014-1970 |
| 2019-10-04 | [11:12:47] <efraim> I think I'm going to skip the tests on vdirsyncer, the test suite has never been reliable on that package |
| 2017-08-08 | [20:26:24] <efraim> perhaps it is inherited, but I'm pretty sure its a python specific thing, like how until just recently we had vdirsyncer propagated by khal |
| 2017-08-08 | [20:28:56] <lfam> The propagation of vdirsyncer by khal was... a mistake :) |
| 2016-09-05 | [22:04:01] <lfam> Right now, the man page for vdirsyncer is not generated due to an issue with our old version of Sphinx |
| 2016-06-17 | [23:15:47] <sankey> the package is "vdirsyncer", and i see it right here: |
| 2016-06-17 | [23:16:44] <bavier> sankey: try `guix package --show=vdirsyncer` |
| 2016-06-17 | [23:24:42] <alezost> sankey: it's better to run "guix pull" more often :-) vdirsyncer was added 6 months ago: http://git.savannah.gnu.org/cgit/guix.git/commit/?id=a2f6a3d502768e58b12a64943994dd2102b6ff91 |
| 2016-03-02 | [03:09:05] <lfam> I've been working pretty closely with this upstream. Interesting discussion to join: https://github.com/untitaker/vdirsyncer/issues/352 |
| 2016-03-02 | [04:20:13] <lfam> Can somebody proofread my response to this: https://github.com/untitaker/vdirsyncer/issues/352 |
| 2016-03-02 | [04:37:04] <Jookia> "In other words, it's not just for finding bugs in vdirsyncer, but also elsewhere. Why would vdirsyncer-packagers care if a server introduced a bug that makes the tests fail?" <- again, aren't the tests meant to show issues |
| 2016-03-02 | [04:39:04] <Jookia> "a simple vdirsyncer --help catches 80% of errors" how broken can your code be |
| 2016-01-24 | [22:41:00] <lfam> So the `khal` package installs an executable Python wrapper to the `vdirsyncer` package's main executable. What in the world? |
| 2016-01-24 | [22:45:28] <lfam> I don't even think you can run vdirsyncer from within khal so it makes no sense for khal to even know about it |
| 2015-12-10 | [00:10:51] <lfam> All that and vdirsyncer doesn't even build a proper manpage. It doesn't even mention the comand-line options. |
| 2015-12-09 | [22:39:51] <lfam> https://github.com/untitaker/vdirsyncer/issues/135 |
| 2023-02-25 | [03:03:54] <fruit-loops> "#61557 - vdirsyncer fails to verify certificates - GNU bug report logs" https://debbugs.gnu.org/cgi/bugreport.cgi?bug=61557 |
| 2023-02-25 | [03:08:01] <fruit-loops> "vdirsyncer fails to verify certificates" https://issues.guix.gnu.org/61557 |
| 2023-02-25 | [03:09:41] <elb> nckx: hmmm when I searched mobile earlier today there were only two open vdirsyncer bugs, and that wasn't one of them |
| 2023-02-25 | [03:10:49] <elb> ok yeah, it's just not tagged or something? if I search vdirsyncer on issues.guix.gnu.org, I don't see it |
| 2023-02-25 | [03:36:53] <fruit-loops> "vdirsyncer fails to verify certificates" https://issues.guix.gnu.org/61557 |
| 2023-02-25 | [03:38:16] <elb> lechner: no, against vdirsyncer |
| 2023-02-25 | [03:46:06] <fruit-loops> "vdirsyncer fails to verify certificates" https://issues.guix.gnu.org/61557 |