Hi Tobias,
> This changelog entry does not really make sense / completly unclear.
> Please be more concise. For the breaks+replace:
> the changelog entry should answer the question "Why" not "what", it is
> completly unclear what you want to archieve.
I forgot to complement when I was testing and
Hi Felix,
> 'license-file-needs-no-entry-in-debian-copyright'. I will send you a
> Lintian merge request with a suggestion.
Thanks. I think it is often a sign of people just blindly grepping for
"Copyright". I've even seen some d/copyright with placeholder "Acme,
Inc", "Yoyodyne, Inc." or even "F
Hi Chris,
On Thu, Sep 12, 2019 at 12:19 AM Chris Lamb wrote:
>
> Did you spot the unused-file-paragraph-in-dep5-copyright Lintian
> warning?
I could not figure out where that message came from. I adjusted the
package, which is on Mentors.
> Indeed, remarking of the copyright of the copyright no
Package: sponsorship-requests
Severity: wishlist
Owner: Emmanuel Arias
X-Debbugs-CC: debian-pyt...@lists.debian.org
Dear mentors,
I am looking for a sponsor for my package "flask-jwt-simple"
* Package name: flask-jwt-simple
Version : 0.0.3-1
Upstream Author : Landon Gilbert-
First, please don't send HTML emails.
Second, you are mixing dh(1) with explicit targets and most likely breking
stuff in them. Please stick to dh(1) and overrides if needed.
--
WBR, wRAR
signature.asc
Description: PGP signature
Hello,
So I am creating my first Debian package from source and I am now stuck with
|dh_installdeb dpkg-genbuildinfo dpkg-genbuildinfo: error: binary build
with no binary artifacts found; .buildinfo is meaningless |
which I have difficulties finding information for.
But my recipe may be wrong s
Hello,
Upstream recently has released new version of the tool.
I have updated the salsa mirror for the project with the new release and
uploaded new packages to mentors.debian.net.
Here is the mentors link for the package:
https://mentors.debian.net/package/fossology
Alternatively, one can
Hi,
I dived into this more deeply and think my code snippet below was
misleading. The configure faulure is rather:
checking google/sparse_hash_set usability... no
checking google/sparse_hash_set presence... yes
configure: WARNING: google/sparse_hash_set: present but cannot be compiled
configure
Hi Felix,
> https://mentors.debian.net/debian/pool/main/w/wolfssl/wolfssl_4.1.0+dfsg-1.dsc
Did you spot the unused-file-paragraph-in-dep5-copyright Lintian
warning? Indeed, remarking of the copyright of the copyright notice
itself is really superfluous and just introduces noise into debian/
copyr
9 matches
Mail list logo
