oxidecomputer / oxidecomputer/garbage-compactor
libxmlsec1 is a den of iniquity
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 12
- Forks
- 1
- Avg merge
- 1h 1m
- Merged PRs (30d)
- 2
Description
According to XML Security Library News, the XML Security Library 1.3.0 release includes the following changes (trimmed to point out the relevant criminal activity):
- core xmlsec and all xmlsec-crypto libraries:
- (ABI breaking change) ...
- (ABI breaking change) ...
- (API breaking change) ...
- (API breaking change) ...
- (API breaking change) ...
- (API/ABI breaking change) ...
- (ABI breaking change) ...
- (ABI breaking change) ...
- ...
- xmlsec-openssl library:
- ...
- (ABI breaking change) ...
- (ABI breaking change) ...
- ...
- xmlsec command line utility:
- (API breaking change) ...
- (API breaking change) ...
- ...
Literally no preparation for this has been made:
$ elfdump /usr/lib/libxmlsec1*so | grep SONAME
[13] SONAME 0x4ad2 libxmlsec1-openssl.so.1
[11] SONAME 0x6706 libxmlsec1.so.1
Sigh.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the repository's build scripts and checking the libxmlsec1 and libxmlsec1-openssl SONAME output with elfdump. Determine how the scripts handle the XML Security Library 1.3.0 API and ABI changes; done means the relevant build or packaging checks account for the changed library interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100