Ticket #1123 (closed requirement: fixed)
Please re-package CKAN packages as "noarch"
| Reported by: | nils.toedtmann | Owned by: | dread |
|---|---|---|---|
| Priority: | awaiting triage | Milestone: | |
| Component: | ckan | Keywords: | |
| Cc: | rgrp | Repository: | ckan |
| Theme: | none |
Description
... or, if the CKAN packages do contain architecture-specific binary code, build packages for i386 too.
Currently, http://apt-alpha.ckan.org/debian only offers packages for amd64, but e.g. "m1.small" EC2 instances are i386.
We would need this in order to migrate the community instances to a packaged based CKAN.
Rufus, pls prioritise.
Change History
comment:1 Changed 3 years ago by nils.toedtmann
- Owner changed from thejimmyg to dread
- Status changed from new to assigned
comment:2 Changed 3 years ago by dread
I'll change the architecture to "all" as per this article: http://linuxreviews.org/man/deb-control/
comment:3 Changed 3 years ago by thejimmyg
- Status changed from assigned to closed
- Resolution set to wontfix
This isn't necessarily a trivial thing. Let's get the build system for the packages stable before we start changing it all to support alternative architectures. Once the packaging is working well it would be trivial to switch those servers to amd64.
I'm sorry, but this isn't worth the investment in manpower at the moment.
comment:4 Changed 3 years ago by rgrp
You can't get small amazon instances as 64 bit and many people's own machines are 32 bit. How costly is packaging no-arch exactly (it must be more than a simple 'switch' in the build if you are saying this is costly :-) )
