From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] cgdb: update to 0.7.1
Date: Wed, 30 Oct 2019 01:23:35 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15917@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 345 bytes --]
There is a new pull request by ndowens against master on the void-packages repository
https://github.com/ndowens/void-packages cgdb
https://github.com/void-linux/void-packages/pull/15917
cgdb: update to 0.7.1
Removed patch, is now part of this release
A patch file from https://github.com/void-linux/void-packages/pull/15917.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-cgdb-15917.patch --]
[-- Type: text/x-diff, Size: 2502 bytes --]
From a50542e1ce6478a6a043ca4d4efdd51d91c73428 Mon Sep 17 00:00:00 2001
From: Nathan Owens <ndowens04@gmail.com>
Date: Tue, 29 Oct 2019 18:17:52 -0500
Subject: [PATCH] cgdb: update to 0.7.1
Removed patch, is now part of this release
---
srcpkgs/cgdb/patches/fix-memory-leak.patch | 18 ------------------
srcpkgs/cgdb/template | 10 ++++------
2 files changed, 4 insertions(+), 24 deletions(-)
delete mode 100644 srcpkgs/cgdb/patches/fix-memory-leak.patch
diff --git a/srcpkgs/cgdb/patches/fix-memory-leak.patch b/srcpkgs/cgdb/patches/fix-memory-leak.patch
deleted file mode 100644
index 77a3be08922..00000000000
--- a/srcpkgs/cgdb/patches/fix-memory-leak.patch
+++ /dev/null
@@ -1,18 +0,0 @@
---- lib/tgdb/tgdb.cpp.orig 2018-12-30 13:23:23.260656690 -0600
-+++ lib/tgdb/tgdb.cpp 2018-12-30 13:24:33.484655276 -0600
-@@ -1039,11 +1039,14 @@
- request->choice.debugger_command.c);
- break;
- case TGDB_REQUEST_MODIFY_BREAKPOINT:
-- command = tgdb_client_modify_breakpoint_call(tgdb,
-+ str = tgdb_client_modify_breakpoint_call(tgdb,
- request->choice.modify_breakpoint.file,
- request->choice.modify_breakpoint.line,
- request->choice.modify_breakpoint.addr,
- request->choice.modify_breakpoint.b);
-+ command = str;
-+ free(str);
-+ str = NULL;
- break;
- case TGDB_REQUEST_COMPLETE:
- str = sys_aprintf("server interpreter-exec mi"
diff --git a/srcpkgs/cgdb/template b/srcpkgs/cgdb/template
index 8843f6d8f75..dcdd7a97a3e 100644
--- a/srcpkgs/cgdb/template
+++ b/srcpkgs/cgdb/template
@@ -1,7 +1,7 @@
# Template file for 'cgdb'
pkgname=cgdb
-version=0.7.0
-revision=3
+version=0.7.1
+revision=1
build_style=gnu-configure
configure_args="ac_cv_rl_version=6.3
ac_cv_file__proc_self_status=yes"
@@ -10,9 +10,7 @@ makedepends="ncurses-devel readline-devel"
depends="gdb"
short_desc="Curses-based interface to the GNU Debugger"
maintainer="Orphaned <orphan@voidlinux.org>"
-license="GPL-2"
+license="GPL-2.0-only"
homepage="http://cgdb.sourceforge.net"
distfiles="http://cgdb.me/files/cgdb-${version}.tar.gz"
-checksum=bf7a9264668db3f9342591b08b2cc3bbb08e235ba2372877b4650b70c6fb5423
-
-nocross="checking Checking attribute printf support... cannot run test program while cross compiling"
+checksum=bb723be58ec68cb59a598b8e24a31d10ef31e0e9c277a4de07b2f457fe7de198
next reply other threads:[~2019-10-30 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 0:23 voidlinux-github [this message]
2019-10-30 15:01 ` [PR PATCH] [Merged]: " voidlinux-github
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-15917@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).