Github messages for voidlinux
 help / color / mirror / Atom feed
From: yopito <yopito@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] burp2-serveur: fix unstable release detection
Date: Sun, 20 Jun 2021 22:28:34 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31590@inbox.vuxu.org> (raw)

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

There is a new pull request by yopito against master on the void-packages repository

https://github.com/yopito/void-packages burp2-server.fix.update.check
https://github.com/void-linux/void-packages/pull/31590

burp2-serveur: fix unstable release detection
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/31590.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-burp2-server.fix.update.check-31590.patch --]
[-- Type: text/x-diff, Size: 619 bytes --]

From 4e80b76b3ead43c141dbb568f01171e4307a489c Mon Sep 17 00:00:00 2001
From: yopito <pierre.bourgin@free.fr>
Date: Sun, 20 Jun 2021 22:27:35 +0200
Subject: [PATCH] burp2-serveur: fix unstable release detection

---
 srcpkgs/burp2-server/update | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/burp2-server/update b/srcpkgs/burp2-server/update
index a07b270a9807..1564ce41cb88 100644
--- a/srcpkgs/burp2-server/update
+++ b/srcpkgs/burp2-server/update
@@ -1,3 +1,3 @@
 pkgname=burp
-# 2019-02: 2.3.x are latest releases (unstable)
-ignore="2.3.*"
+# unstable releases
+ignore="?.[3579].*"

             reply	other threads:[~2021-06-20 20:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20 20:28 yopito [this message]
2021-06-21  8:57 ` Johnnynator
2021-06-21 11:37 ` [PR PATCH] [Updated] " yopito
2021-06-21 11:37 ` burp2-server: " yopito
2021-06-21 11:44 ` [PR PATCH] [Merged]: " Johnnynator

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31590@inbox.vuxu.org \
    --to=yopito@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).