From: whiteman808 <whiteman808@paraboletancza.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] src_install: dobin failed while merging ebuild
Date: Sun, 17 Nov 2024 19:29:17 +0100 [thread overview]
Message-ID: <42nze2a5md6xk6wdwbs37dlpnlsaubvte43s52mqhkzrlvpyjj@lk3g43oi4fwg> (raw)
In-Reply-To: <8495056.NyiUUSuA9g@rogueboard>
[-- Attachment #1: Type: text/plain, Size: 2188 bytes --]
Hey,
On 17 Nov 2024, 15:12:57, Michael wrote:
> On Sunday 17 November 2024 14:37:53 GMT whiteman808 wrote:
> > Hello,
> >
> > On 17 Nov 2024, 17:55:38, Matt Jolly wrote:
> > > Hi,
> > >
> > > On 17/11/24 17:22, whiteman808 wrote:
> > > > I need help with writing ebuild. Ebuild fails to merge.
> > > > Necessary information is located in attachments.
> > >
> > > I haven't actually built this, but if dobin is failing after this step:
> > > > cp $WORK/b001/exe/a.out goimapnotify
> > >
> > > Where is goimapnotify actually being copied to? If you run
> > > `ebuild foo-1.2.3.ebuild compile` and inspect ${S} (the workdir)
> > > where is this file?
> > >
> > > dobin is relative to ${S}; you probably just need to adjust that path.
> > >
> > > Let me know how you go with those hints.
> > >
> > > Cheers,
> > >
> > > Matt
> >
> > Merging as non-root user with FEATURES="fakeroot" works. But sudo emerge
> > goimapnotify fails with:
> >
> > ^[[32m * ^[[39;49;00mPackage: net-mail/goimapnotify-2.4:0
> > ^[[32m * ^[[39;49;00mRepository: whiteman808
> > ^[[32m * ^[[39;49;00mMaintainer: whiteman808@paraboletancza.org
> > ^[[32m * ^[[39;49;00mUSE: abi_x86_64 amd64 elibc_glibc kernel_linux
> > systemd ^[[32m * ^[[39;49;00mFEATURES: network-sandbox preserve-libs
> > sandbox userpriv usersandbox
> > >>> Unpacking source...
> > >>> Unpacking goimapnotify-2.4.tar.bz2 to
> > >>> /var/tmp/portage/net-mail/goimapnotify-2.4/work
> > go mod verify
> > go: github.com/emersion/go-imap@v1.2.1: Get
> > "https://proxy.golang.org/github.com/emersion/go-imap/@v/v1.2.1.mod": dial
> > tcp: lookup proxy.golang.org on [2a00:f41:5812:9793::ba]:53: dial udp
> > [2a00:f41:5812:9793::ba]:53: connect: network is unreachable
>
> It looks like you have a network problem and in particular DNS resolution (UDP
> port 53).
>
I have a working ebuild after spending hours on learning Gentoo ebuild-specific syntax.
Not sure if it is normal if I haven't yet written any ebuilds from scratch. This is my
first ebuild that I wrote by hand.
I will be thankful for a code review of the my ebuild in the attachment.
Thank you,
whiteman808.
[-- Attachment #2: goimapnotify-2.4.ebuild --]
[-- Type: application/vnd.gentoo.ebuild, Size: 1050 bytes --]
[-- Attachment #3: goimapnotify-9999.ebuild --]
[-- Type: application/vnd.gentoo.ebuild, Size: 1050 bytes --]
[-- Attachment #4: metadata.xml --]
[-- Type: text/xml, Size: 343 bytes --]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
<maintainer type="person">
<email>whiteman808@paraboletancza.org</email>
<name>whiteman808</name>
</maintainer>
<upstream>
<remote-id type="gitlab">shackra/goimapnotify</remote-id>
</upstream>
</pkgmetadata>
prev parent reply other threads:[~2024-11-17 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 7:22 [gentoo-user] src_install: dobin failed while merging ebuild whiteman808
2024-11-17 7:55 ` Matt Jolly
2024-11-17 14:37 ` whiteman808
2024-11-17 15:12 ` Michael
2024-11-17 18:29 ` whiteman808 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42nze2a5md6xk6wdwbs37dlpnlsaubvte43s52mqhkzrlvpyjj@lk3g43oi4fwg \
--to=whiteman808@paraboletancza.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox