public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jesse Keating <jkeating@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/rpkg] 1.70-1: Fix mock-config (ticket #13) (jkeating)
Date: Mon, 10 Aug 2026 21:43:02 GMT	[thread overview]
Message-ID: <178639818248.1.16583842900214805235.rpms-rpkg-8b61b010e7a7@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/rpkg
            Branch : 1.70-1
            Commit : 8b61b010e7a78c06cfe7e2b3bab9ada93eaeecfc
            Author : Jesse Keating <jkeating@redhat.com>
            Date   : 2012-01-24T23:49:16-08:00
            Stats  : +9/-6 in 3 file(s)
            URL    : https://src.fedoraproject.org/rpms/rpkg/c/8b61b010e7a78c06cfe7e2b3bab9ada93eaeecfc?branch=1.70-1

            Log:
            Fix mock-config (ticket #13) (jkeating)
Make md5 a common build argument (jkeating)
Move arches to be a common build argument (ticket #3) (jkeating)
Find remote branch to track better (jkeating)

---
diff --git a/.gitignore b/.gitignore
index f49df6a..150104e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -9,3 +9,4 @@
 /rpkg-1.9.tar.gz
 /rpkg-1.10.tar.gz
 /rpkg-1.11.tar.gz
+/rpkg-1.12.tar.gz

diff --git a/rpkg.spec b/rpkg.spec
index a6eb9bb..070c39b 100644
--- a/rpkg.spec
+++ b/rpkg.spec
@@ -2,7 +2,7 @@
 %{!?python_sitelib: %global python_sitelib %(%{__python} -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())")}
 
 Name:           rpkg
-Version:        1.11
+Version:        1.12
 Release:        1%{?dist}
 Summary:        Utility for interacting with rpm+git packaging systems
 
@@ -19,11 +19,9 @@ BuildArch:      noarch
 BuildRequires:  python-devel, python-setuptools
 # We br these things for man page generation due to imports
 BuildRequires:  GitPython, koji, python-pycurl
-%if 0%{?rhel} < 7
 BuildRequires:  python-hashlib
 BuildRequires:  python-argparse
 BuildRequires:  python-kitchen
-%endif
 
 %description
 A tool for managing RPM package sources in a git repository.
@@ -35,10 +33,8 @@ Requires:       GitPython >= 0.2.0, python-argparse
 Requires:       python-pycurl, koji
 Requires:       rpm-build, rpm-python
 Requires:       rpmlint, mock, curl, openssh-clients, redhat-rpm-config
-%if 0%{?rhel} < 7
 Requires:       python-kitchen
 Requires:       python-hashlib
-%endif
 
 %description -n pyrpkg
 A python library for managing RPM package sources in a git repository.
@@ -78,6 +74,12 @@ rm -rf $RPM_BUILD_ROOT
 
 
 %changelog
+* Tue Jan 24 2012 Jesse Keating <jkeating@redhat.com> - 1.12-1
+- Fix mock-config (ticket #13) (jkeating)
+- Make md5 a common build argument (jkeating)
+- Move arches to be a common build argument (ticket #3) (jkeating)
+- Find remote branch to track better (jkeating)
+
 * Fri Jan 13 2012 Jesse Keating <jkeating@redhat.com> - 1.11-1
 - Change clog output to be more git-like (sochotnicky)
 - Fix mockconfig property (bochecha)

diff --git a/sources b/sources
index 4a430fe..e0790a0 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-d231c68ff93e28bae7572ea4b66fc41a  rpkg-1.11.tar.gz
+01cdd261e53300d7892ade768f4e3c05  rpkg-1.12.tar.gz

                 reply	other threads:[~2026-08-10 21:43 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=178639818248.1.16583842900214805235.rpms-rpkg-8b61b010e7a7@fedoraproject.org \
    --to=jkeating@redhat.com \
    --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