Linux DTrace development list
 help / color / mirror / Atom feed
From: Kris Van Hees <noreply@github.com>
To: dtrace@lists.linux.dev
Subject: [oracle/dtrace] 729657: test: Fix path to sed
Date: Wed, 30 Sep 2026 11:40:57 -0700	[thread overview]
Message-ID: <oracle/dtrace/push/refs/heads/dev-queue/02f587-a0a173@github.com> (raw)

  Branch: refs/heads/dev-queue
  Home:   https://github.com/oracle/dtrace
  Commit: 729657e904d4e949b1ad9d52211f5d0702edfded
      https://github.com/oracle/dtrace/commit/729657e904d4e949b1ad9d52211f5d0702edfded
  Author: Kris Van Hees <kris.van.hees@oracle.com>
  Date:   2026-09-29 (Tue, 29 Sep 2026)

  Changed paths:
    M test/internals/libproc/err.bad_sh_link.r.p

  Log Message:
  -----------
  test: Fix path to sed

Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Elena Zannoni <elena.zannoni@oracle.com>


  Commit: e31cc91ab28d5f9e16465872f160ad60d68c92fe
      https://github.com/oracle/dtrace/commit/e31cc91ab28d5f9e16465872f160ad60d68c92fe
  Author: Kris Van Hees <kris.van.hees@oracle.com>
  Date:   2026-09-29 (Tue, 29 Sep 2026)

  Changed paths:
    M libdtrace/dt_link.c

  Log Message:
  -----------
  link: no longer add utsname in USDT ELF notes

USDT ELF notes used to contain utsname information for debugging, but
this has proven to be troublesome for distributions that expect to be
able to regenerate build objects with identical data.  Since the
utsname data contains the system name, the USDT ELF notes were causing
comparisons between generates and regenerated objects to fail.

Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Elena Zannoni <elena.zannoni@oracle.com>


  Commit: f49e2063d6c13d6c97dd61807589a9e5fb193b65
      https://github.com/oracle/dtrace/commit/f49e2063d6c13d6c97dd61807589a9e5fb193b65
  Author: Kris Van Hees <kris.van.hees@oracle.com>
  Date:   2026-09-29 (Tue, 29 Sep 2026)

  Changed paths:
    M libdtrace/dt_impl.h
    M libdtrace/dt_module.c
    M libdtrace/dt_open.c

  Log Message:
  -----------
  ctf: introduce dt_ctfa_open to support ctf-nobfd

If DTrace is statically linked with the libctf-nobfd library, there is
no ctf_arc_open() function (for unknown reasons).  We therefore add a
dt_ctfa_open() function that works both for libctf and libctf-nobfd.

Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Elena Zannoni <elena.zannoni@oracle.com>


  Commit: a0a173ff1ec490c5b9823654665cff62ccf27ff3
      https://github.com/oracle/dtrace/commit/a0a173ff1ec490c5b9823654665cff62ccf27ff3
  Author: Kris Van Hees <kris.van.hees@oracle.com>
  Date:   2026-09-29 (Tue, 29 Sep 2026)

  Changed paths:
    A dists/Build
    A dists/debian/changelog
    A dists/debian/control
    A dists/debian/copyright
    A dists/debian/dtrace-tests.install
    A dists/debian/dtrace-tests.lintian-overrides
    A dists/debian/dtrace.docs
    A dists/debian/dtrace.install
    A dists/debian/dtrace.lintian-overrides
    A dists/debian/dtrace.manpages
    A dists/debian/libdtrace2-dev.install
    A dists/debian/libdtrace2.install
    A dists/debian/libdtrace2.lintian-overrides
    A dists/debian/libdtrace2.manpages
    A dists/debian/mkChangelog
    A dists/debian/patches/debian-configure.patch
    A dists/debian/patches/debian-static-linking.patch
    A dists/debian/patches/series
    A dists/debian/rules
    A dists/debian/source/format

  Log Message:
  -----------
  Add packaging configuration for Debian

Packaging configuration files for Debian are provided in dists/debian.

Sample steps to build DEB packages:

 - make dist
 - cp dtrace-x.y.z.tar.bz2 $D/dtrace_x.y.z.orig.tar.bz2
 - cd $D
 - tar -jxpSf dtrace_x.y.z.orig.tar.bz2
 - cd dtrace-x.y.z
 - make prep-debian
 - debuild

Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Reviewed-by: Elena Zannoni <elena.zannoni@oracle.com>


Compare: https://github.com/oracle/dtrace/compare/02f587384320...a0a173ff1ec4

To unsubscribe from these emails, change your notification settings at https://github.com/oracle/dtrace/settings/notifications

                 reply	other threads:[~2026-09-30 18:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=oracle/dtrace/push/refs/heads/dev-queue/02f587-a0a173@github.com \
    --to=noreply@github.com \
    --cc=dtrace@lists.linux.dev \
    /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