Please do consider taking this to whatever the appropriate priority actually is, or however else you keep it off my radar until such time there's some meaningful involvement on my part ;-)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 27 2019
I'm sorry, this is an incomplete set of steps to reproduce on an by-now-out-dated version of pykolab/wallace.
This ticket is both old, as well as appears to be out-dated, in the sense that further updates to guam have been made available that also, supposedly, work, and was originally reported by an employee for another one of our then-employees to address.
While OwnCloud nor NextCloud WebDAV currently establish a priority for us, WebDAV more generally would.
Inconvenient at best for the moment, but certainly a risk going forward.
Viewing "details" and perhaps even the mail headers, is there a Date header that you see in the sources of the email?
Mar 25 2019
It'll resolve itself once a package is built in Winterfell.
Mar 23 2019
Such would be a request for enhancement we're unlikely to entertain.
Mar 22 2019
That's like reading the PIN off of the ATM card.
This should now have been resolved in packaging.
This should be resolved in packaging.
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
Correcting the priority from 60/40 to Normal
It doesn't seem like there's any actual errors in reality.
Should be fixed by removing pytz from our repositories.
this should now be fixed in 3.4.3.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This ticket is no longer relevant.
This seems like low-priority aesthetics to me more so than an actual problem.
No longer relevant.
No longer relevant.
We do not actively support the database backend driver, so please bear in mind this has a very low priority for us.
This ticket is no longer relevant.