View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008903 | Taler | deployment and operations | public | 2024-06-06 07:15 | 2024-08-28 21:31 |
| Reporter | javier.sepulveda | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Target Version | 0.13 | Fixed in Version | 0.13 | ||
| Summary | 0008903: Upgrade issue - Some packages kept back | ||||
| Description | When trying to UPGRADE the taler-ops server, some packages are kept without an upgrade, probably due of dependencies. ### The following packages have been kept back: libsemanage-common libtalerexchange libtalermerchant passwd taler-exchange taler-exchange-database taler-exchange-offline taler-merchant | ||||
| Tags | No tags attached. | ||||
| I've investigated it (apt-cache showpkg, apt-cache rdepends, apt-cache policy) and cannot fathom where the issue comes from. I've resolved the stuck 'passwd' package, so we're now ONLY on the taler-specific packages. Sure, apt dist-upgrade would happily do the upgrade (please don't run that!), but I'd like to understand why 'apt upgrade' refuses to do the upgrade! | |
| Debian reported a policy violation for taler-merchant/taler-exchange. What's odd is that a new version of taler-terms-generator was already installed, while all other components were at an older version. Curiously, removing taler-terms-generator lead to a resolution of the previous install policy issue. IMO it's not worth to dig deeper into this, seems more like a Debian issue of plain "apt-get upgrade" being too conservative. The problem is easily resolved with "dist-upgrade". We should probably recommend just using "dist-upgrade" in general. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-06-06 07:15 | javier.sepulveda | New Issue | |
| 2024-06-06 07:15 | javier.sepulveda | Status | new => assigned |
| 2024-06-06 07:15 | javier.sepulveda | Assigned To | => javier.sepulveda |
| 2024-06-06 07:16 | javier.sepulveda | Assigned To | javier.sepulveda => |
| 2024-06-06 07:17 | javier.sepulveda | Assigned To | => Christian Grothoff |
| 2024-06-06 09:28 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2024-06-06 09:29 | Christian Grothoff | Note Added: 0022523 | |
| 2024-06-10 13:54 | Florian Dold | Note Added: 0022566 | |
| 2024-06-10 13:54 | Florian Dold | Status | assigned => informing |
| 2024-06-10 13:54 | Florian Dold | Resolution | open => no change required |
| 2024-08-26 20:29 | Christian Grothoff | Target Version | => 0.13 |
| 2024-08-26 20:29 | Christian Grothoff | Fixed in Version | => 0.13 |
| 2024-08-28 21:31 | Christian Grothoff | Status | informing => closed |