public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/rust-drop-tracker] f43: Update to version 0.2.0; Fixes RHBZ#2493343
Date: Fri, 26 Jun 2026 09:12:47 GMT	[thread overview]
Message-ID: <178246516735.1.3512365346169524008.rpms-rust-drop-tracker-f9ce4f5b14cf@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/rust-drop-tracker
Branch : f43
Commit : f9ce4f5b14cf4651acc692e4ca90590021dd6072
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-06-26T10:02:48+01:00
Stats  : +4/-3 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/rust-drop-tracker/c/f9ce4f5b14cf4651acc692e4ca90590021dd6072?branch=f43

Log:
Update to version 0.2.0; Fixes RHBZ#2493343

---
diff --git a/.gitignore b/.gitignore
index 5928998..a8ce57a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
 /drop-tracker-0.1.3.crate
+/drop-tracker-0.2.0.crate

diff --git a/rust-drop-tracker.spec b/rust-drop-tracker.spec
index e6a4361..dd08e84 100644
--- a/rust-drop-tracker.spec
+++ b/rust-drop-tracker.spec
@@ -1,11 +1,11 @@
-# Generated by rust2rpm 27
+# Generated by rust2rpm 28
 %bcond check 1
 %global debug_package %{nil}
 
 %global crate drop-tracker
 
 Name:           rust-drop-tracker
-Version:        0.1.3
+Version:        0.2.0
 Release:        %autorelease
 Summary:        To check when a variable gets dropped
 

diff --git a/sources b/sources
index affe7e0..85181eb 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (drop-tracker-0.1.3.crate) = 6a05064764b2274730c93a3b42d32bf065129ca6c434c2a38ba51b9a8b8a573ea9ee34552addbff076d7daad4ca0de90abe3c7926018561fd2ed58823bf2449d
+SHA512 (drop-tracker-0.2.0.crate) = 360878a76542f9f3a1afc4f73faaeae4c3f391eed0e6e914ef8bd795fe74767d71479e3ed0b4368f854a57ab2fc5714a8efa6ef378aaa54243863f3dea7c9e53

                 reply	other threads:[~2026-06-26  9:12 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=178246516735.1.3512365346169524008.rpms-rust-drop-tracker-f9ce4f5b14cf@fedoraproject.org \
    --to=code@musicinmybrain.net \
    --cc=git-commits@fedoraproject.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