From: "Stefan Mühlinghaus" <"master..."@googlemail.com>
To: voidlinux@googlegroups.com
Subject: Re: Problem building package
Date: Sun, 8 Mar 2015 10:14:47 -0700 (PDT) [thread overview]
Message-ID: <e2ebc7d1-3fe7-435b-a6fd-1d7b4bfca95c@googlegroups.com> (raw)
In-Reply-To: <234a9f9c-0fc2-49ea-b876-75bd2531d775@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 355 bytes --]
Alright, nevermind. I posted too quickly. Apparently my mistake was to call
the version "git". I'm using a date notation as version now and the package
is created without a problem.
I've also added the provided libraries to common/shlibs, completely
preventing the library dependency warnings. Is that OK? Or is that file
managed differently?
[-- Attachment #1.2: Type: text/html, Size: 388 bytes --]
next prev parent reply other threads:[~2015-03-08 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 16:39 Stefan Mühlinghaus
2015-03-08 17:14 ` Stefan Mühlinghaus [this message]
2015-03-10 6:43 ` Juan RP
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=e2ebc7d1-3fe7-435b-a6fd-1d7b4bfca95c@googlegroups.com \
--to="master..."@googlemail.com \
--cc=voidlinux@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).