macaroni-os / macaroni-os/mark-issues
[net-kit] www-apps/gitea-1.26.1 doesn't emerge
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
```
github.com/markbates/goth/providers/twitter
# github.com/msteinert/pam/v2
../go-mod/github.com/msteinert/pam/v2@v2.1.0/transaction.go:409:55: could not determine what C.RTLD_NEXT refers to
golang.org/x/crypto/ripemd160
github.com/markbates/goth/providers/google
github.com/aws/aws-sdk-go-v2/internal/rand
github.com/aws/aws-sdk-go-v2/internal/sdk
github.com/aws/aws-sdk-go-v2/internal/sync/singleflight
github.com/aws/smithy-go/logging
github.com/aws/smithy-go/context
github.com/aws/smithy-go/time
github.com/aws/smithy-go/internal/sync/singleflight
github.com/go-fed/httpsig
github.com/aws/smithy-go
github.com/aws/smithy-go/transport/http/internal/io
```
It seems related to `pam` module. If `pam` is disabled the compilation goes ahead.
Probably, we need to upgrade `pam` package.
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 with the reported failure in github.com/msteinert/pam/v2/transaction.go and inspect the gitea-1.26.1 package build configuration to see how the pam module is selected. Verify whether upgrading pam resolves the C.RTLD_NEXT error, then confirm that gitea emerges successfully with pam enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100