Github messages for voidlinux
 help / color / mirror / Atom feed
From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] xlint: homepage should not use variables on CI vs no error when locally ran
Date: Wed, 27 May 2020 18:48:04 +0200	[thread overview]
Message-ID: <20200527164804.a3Fpf_AYiKgNrPbnR1TOv8aiUC3H2iX78GNDPLR8hR4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22339@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 878 bytes --]

Closed issue by anjandev on void-packages repository

https://github.com/void-linux/void-packages/issues/22339

Description:
### System

* xuname:  
Void 5.6.14_1 x86_64 AuthenticAMD notuptodate rFFFFFFFF

* package:  
  * xtools-0.58_1

### Expected behavior
In my package template, I put the homepage as:
```
homepage="http://www.gnu.org/software/${pkgname}"
```

Running xlint on this file, I should get the same output as the build travis CI check on github.

### Actual behavior

xlint returns no errors. However, Travis returns the following error:
```
Linting srcpkgs/guile/template...
srcpkgs/guile/template:13: homepage should not use variables
```

### Steps to reproduce the behavior
Make a template with a homepage with variables in the homepage variable

Ie. xlint the guile template on your local machine vs. run the CI check on github.

      parent reply	other threads:[~2020-05-27 16:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27  2:07 [ISSUE] " anjandev
2020-05-27  2:13 ` ericonr
2020-05-27  2:13 ` ahesford
2020-05-27  2:17 ` anjandev
2020-05-27  2:18 ` ahesford
2020-05-27  2:22 ` anjandev
2020-05-27  2:49 ` ericonr
2020-05-27  2:49 ` ericonr
2020-05-27  3:29 ` anjandev
2020-05-27 15:05 ` leahneukirchen
2020-05-27 16:48 ` leahneukirchen
2020-05-27 16:48 ` leahneukirchen [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=20200527164804.a3Fpf_AYiKgNrPbnR1TOv8aiUC3H2iX78GNDPLR8hR4@z \
    --to=leahneukirchen@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).