View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008188 | Taler | deployment and operations | public | 2024-01-22 14:33 | 2024-08-28 23:30 |
Reporter | dvn | Assigned To | dvn | ||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Target Version | 0.13 | Fixed in Version | 0.13 | ||
Summary | 0008188: ARM64 Debian Packages for Exchange | ||||
Description | We need arm64 debian packages for Exchange arm64 packages for GNUnet are a prerequisite | ||||
Tags | No tags attached. | ||||
|
Seems nullptrderef has address this largely, @dvn: can you confirm? |
|
https://buildbot.taler.net/#/builders/19/builds/820 - ARM builds are mostly addressed for exchange (likely large overlap for transplanting into merchant & co.) RISC-V is (/will, it hasn't yet (and might not if gnunet/1034 completes before it reaches risc-v)) fail due to GNUNet not having RISC-V builds yet. <- I added RISC-V builds (that, once we have gnunet nightly RISC-V, have no reason not to work) Documentation is still needed for this scripting - the 1xx scripts are generated, and further platform support can be evtl. added to them - however given I'm not familiar with how packaging is setup on whatever server hosts the debs, I'll likely need assistance for specifically distributing packages. The generation scripts, once also adapted to work in the GNUNet repository, should make it relatively easy to support other distributions (assuming the release server for those distros has been setup) and architectures - architectures usually just involve adding an item to the targets array (distro codenames are the same story for adding more) - and distributions just involve that + adapting the containerfile to the distro. |
|
Still missing for libeufin, merchant, challenger, wallet-core arm64 packages, so not time to close this unless we want to change it to a ticket just for exchange. Interesting approach with the generated scripts. A lot of repetition, but maybe we can cut down on that by migrating some of the ideas into the buildbot config itself. Anyway, that could be capture in a different ticket. |
|
libeufin and wallet-core should be packaged as arch-independent as far as I see it, as JVM/JavaScript code should be architecture-independent. So those are clearly a quite different story. As for merchant/challenger/sync/taler-mdb, we should probably just clone the exchange approach (which should be pretty quick), unless you first want to reduce the duplication. But with the *generation* I'm not sure that's too much of a problem, as we primarily care about duplicated source, not duplicated *generated* scripts, right? :-) |
|
> As for merchant/challenger/sync/taler-mdb, we should probably just clone the exchange approach (which should be pretty quick), unless you first want to reduce the duplication. But with the *generation* I'm not sure that's too much of a problem, as we primarily care about duplicated source, not duplicated *generated* scripts, right? :-) The generated scripts are already duplicated LOL > libeufin and wallet-core should be packaged as arch-independent as far as I see it, as JVM/JavaScript code should be architecture-independent. So those are clearly a quite different story. I'd have the question there of if the metadata is already set to be arch-independent, or if it's set to x86_64 for unknown reasons |
|
> Still missing for libeufin, merchant, challenger, wallet-core arm64 packages, so not time to close this unless we want to change it to a ticket just for exchange. My comment (& AFAIK C's aswell) were in regards to a large chunk of the work being done, not the entire ticket :) |
|
I've scoped this ticket to only Exchange. We can open new tickets for the others, as needed. GNUnet is done, and so is Exchange as of https://buildbot.taler.net/#/builders/19/builds/820 |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-01-22 14:33 | dvn | New Issue | |
2024-01-22 14:33 | dvn | Status | new => assigned |
2024-01-22 14:33 | dvn | Assigned To | => dvn |
2024-01-29 14:06 | Florian Dold | Target Version | => 0.11 |
2024-01-30 00:42 | Christian Grothoff | Severity | minor => feature |
2024-05-13 21:26 | Christian Grothoff | Target Version | 0.11 => 0.12 |
2024-06-16 18:34 | Christian Grothoff | Note Added: 0022628 | |
2024-06-16 18:39 | nullptrderef | Note Added: 0022629 | |
2024-06-16 18:44 | nullptrderef | Note Edited: 0022629 | |
2024-06-16 18:58 | nullptrderef | Note Edited: 0022629 | |
2024-06-16 18:59 | nullptrderef | Note Edited: 0022629 | |
2024-06-16 19:03 | nullptrderef | Note Edited: 0022629 | |
2024-06-16 19:03 | nullptrderef | Note Edited: 0022629 | |
2024-06-16 19:35 | nullptrderef | Note Edited: 0022629 | |
2024-06-16 21:06 | dvn | Note Added: 0022630 | |
2024-06-16 21:25 | Christian Grothoff | Note Added: 0022631 | |
2024-06-19 18:09 | Florian Dold | Target Version | 0.12 => 0.13 |
2024-06-23 18:52 | nullptrderef | Note Added: 0022712 | |
2024-06-23 18:53 | nullptrderef | Note Added: 0022713 | |
2024-06-24 02:44 | dvn | Summary | ARM64 Debian Packages => ARM64 Debian Packages for Exchange |
2024-06-24 02:44 | dvn | Description Updated | |
2024-06-24 02:45 | dvn | Status | assigned => resolved |
2024-06-24 02:45 | dvn | Resolution | open => fixed |
2024-06-24 02:45 | dvn | Note Added: 0022714 | |
2024-08-26 22:30 | Christian Grothoff | Fixed in Version | => 0.13 |
2024-08-28 23:30 | Christian Grothoff | Status | resolved => closed |