taskdeb-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[pkg-tasktools] Bug#907603: marked as done (taskwarrior: Task sync fails


From: Debian Bug Tracking System
Subject: [pkg-tasktools] Bug#907603: marked as done (taskwarrior: Task sync fails with "Aborted")
Date: Wed, 05 Sep 2018 17:48:03 +0000

Your message dated Wed, 5 Sep 2018 19:44:20 +0200
with message-id <address@hidden>
and subject line Re: [pkg-tasktools] Bug#907603: Problem has resolved
has caused the Debian Bug report #907603,
regarding taskwarrior: Task sync fails with "Aborted"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
907603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907603
Debian Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: taskwarrior: Task sync fails with "Aborted" Date: Wed, 29 Aug 2018 19:51:00 -0700
Package: taskwarrior
Version: 2.5.1+dfsg-6
Severity: important

Dear Maintainer,

   * What led up to the situation?

A long-functioning taskwarrior installation fails to sync and crashes, perhaps 
after a recent update.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Ran 'task sync'. Running 'task list' works as usual.

   * What was the outcome of this action?

$ task sync
Aborted
$

Or, with debugging output turned on: 

$ task rc.debug=1 rc.debug.tls=3 sync
c: INFO Server certificate will be verified but hostname ignored.
c: 3 ASSERT: extensions.c[_gnutls_get_extension]:65
c: 3 ASSERT: extensions.c[_gnutls_get_extension]:65
c: 3 ASSERT: mpi.c[_gnutls_x509_read_uint]:246
c: 3 ASSERT: extensions.c[_gnutls_get_extension]:65
c: 3 ASSERT: extensions.c[_gnutls_get_extension]:65
c: 3 ASSERT: x509_ext.c[gnutls_subject_alt_names_get]:110
c: 3 ASSERT: x509.c[get_alt_name]:1701
c: 3 ASSERT: extensions.c[_gnutls_get_extension]:65
c: 3 ASSERT: constate.c[_gnutls_epoch_get]:600
c: 3 ASSERT: system/threads.c[gnutls_system_mutex_lock]:120
Aborted
$


   * What outcome did you expect instead?

Proper syncing with the taskserver, as usual.  The taskserver (inthe.am) is 
fine,
as my Debian jessie box and Android clients sync correctly.

As part of debugging this anomaly, I have tried cloning and compiling 
taskwarrior
from the upstream source, using Debian's libgnutls, with the same error. 

Thank you for your time! Taskwarrior makes my life better :)!

Charlie


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (200, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages taskwarrior depends on:
ii  libc6        2.27-5
ii  libgcc1      1:8.2.0-4
ii  libgnutls30  3.5.19-1
ii  libstdc++6   8.2.0-4
ii  libuuid1     2.32.1-0.1

taskwarrior recommends no packages.

taskwarrior suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- Subject: Re: [pkg-tasktools] Bug#907603: Problem has resolved Date: Wed, 5 Sep 2018 19:44:20 +0200
Alright, thank you for the update, closing then!

Ftr, the error message you reported felt somewhat related to the latest openssl update, if not that task* use gnutls..

On Wed, 5 Sep 2018, 7:32 p.m. Charlie Hagedorn, <address@hidden> wrote:
The problem appears to have resolved itself. The computer was restarted at least once, and has been updated at least once. A check of the dependencies with reportbug suggests that no change in taskwarrior's dependencies occurred.

Please close this bug at this time -- I will reply back if it recurs.

Thank you!


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]