This should now have been resolved in packaging.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 22 2019
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.
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.
The application can't address having run out of file descriptors.
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.