public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ramakrishna Reddy <ramkrsna@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/python-bitarray] epel10: - Initial RPM release
Date: Sun, 09 Aug 2026 01:30:06 GMT	[thread overview]
Message-ID: <178623900641.1.17111090315148558021.rpms-python-bitarray-1f2f4a755e76@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-bitarray
Branch : epel10
Commit : 1f2f4a755e760473150b244476ff675a4e927e4b
Author : Ramakrishna Reddy <ramkrsna@fedoraproject.org>
Date   : 2009-04-23T09:36:40+00:00
Stats  : +59/-0 in 4 file(s)
URL    : https://src.fedoraproject.org/rpms/python-bitarray/c/1f2f4a755e760473150b244476ff675a4e927e4b?branch=epel10

Log:
- Initial RPM release

---
diff --git a/.cvsignore b/.cvsignore
index e69de29..a65fcfc 100644
--- a/.cvsignore
+++ b/.cvsignore
@@ -0,0 +1 @@
+bitarray-0.3.5.tar.gz

diff --git a/import.log b/import.log
new file mode 100644
index 0000000..d3b2e40
--- /dev/null
+++ b/import.log
@@ -0,0 +1 @@
+python-bitarray-0_3_5-1_fc10:HEAD:python-bitarray-0.3.5-1.fc10.src.rpm:1240479334

diff --git a/python-bitarray.spec b/python-bitarray.spec
new file mode 100644
index 0000000..7512b97
--- /dev/null
+++ b/python-bitarray.spec
@@ -0,0 +1,56 @@
+%{!?python_sitearch: %define python_sitearch %(%{__python} -c "from distutils.sysconfig import get_python_lib; print get_python_lib(1)")}
+ 
+
+Name:   python-bitarray          
+Version:     0.3.5   
+Release:        1%{?dist}
+Summary:        Efficient Array of Booleans --C Extensions
+
+Group:          Development/Languages
+License:        Python
+URL:            http://pypi.python.org/pypi/bitarray/
+Source0:        http://pypi.python.org/packages/source/b/bitarray/bitarray-%{version}.tar.gz
+BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
+BuildRequires:  python-devel python-setuptools
+
+%description
+Bitarrays are sequence types and behave very much like usual lists.
+Eight bits are represented by one byte in contiguous block of memory.
+The user can select between two representations; little-endian and big-endian.
+Most of the functionality is implemented in C.Methods for accessing the machine
+representation are provided. This can be useful when bit level access to binary
+files is required, such as portable bitmap image files (.pbm). Also, when 
+dealing with compressed data which uses variable bit length encoding
+you may find this module useful.
+
+%prep
+%setup -q -n bitarray-%{version}
+
+
+%build
+CFLAGS="$RPM_OPT_FLAGS" %{__python} setup.py build
+
+
+%install
+rm -rf $RPM_BUILD_ROOT
+%{__python} setup.py install -O1 --skip-build --root $RPM_BUILD_ROOT
+
+ 
+%clean
+rm -rf $RPM_BUILD_ROOT
+
+
+%files
+%defattr(-,root,root,-)
+%doc LICENSE 
+
+%{python_sitearch}/*
+ 
+
+
+%changelog
+* Wed Apr 08 2009 Ramakrishna Reddy Yekulla <ramkrsna@fedoraproject.org> 0.3.5-1
+- Initial RPM release
+
+
+

diff --git a/sources b/sources
index e69de29..d8e38b0 100644
--- a/sources
+++ b/sources
@@ -0,0 +1 @@
+322a25e04e7aece5e028e5b068329291  bitarray-0.3.5.tar.gz

                 reply	other threads:[~2026-08-09  1:30 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=178623900641.1.17111090315148558021.rpms-python-bitarray-1f2f4a755e76@fedoraproject.org \
    --to=ramkrsna@fedoraproject.org \
    --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