[Bug 448531] Review Request: pyrenamer - A mass file renamer written in PyGTK

bugzilla at redhat.com bugzilla at redhat.com
Wed May 28 15:00:05 UTC 2008


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: pyrenamer - A mass file renamer written in PyGTK


https://bugzilla.redhat.com/show_bug.cgi?id=448531


mtasaka at ioa.s.u-tokyo.ac.jp changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|nobody at fedoraproject.org    |mtasaka at ioa.s.u-tokyo.ac.jp
             Status|NEW                         |ASSIGNED
               Flag|                            |fedora-review?




------- Additional Comments From mtasaka at ioa.s.u-tokyo.ac.jp  2008-05-28 11:00 EST -------
For 0.5.0-2

* BuildRequires
  - "python-eyed3" seems needed also for BuildRequires.
  ! build.log shows (from following)
    http://koji.fedoraproject.org/koji/taskinfo?taskID=632906
--------------------------------------------------------
   177  checking for eyeD3 module... 
   178  no
   179  configure: WARNING: eyeD3 not found, rename music disabled!
--------------------------------------------------------
     This affects HAVE_EYED3 macro in configure{,.ac} then
     src/pyrenamer_globals.py.in. Actually the installed
     pyrenamer/pyrenamer_globals.py has:
--------------------------------------------------------
    26  have_eyed3=False
--------------------------------------------------------

* spec file convention
  - Please write in the order:
--------------------------------------------------------
%prep
%build
%install
%clean

%pre (%post, etc)

%files
--------------------------------------------------------
    i.e. Please don't write scriptlets between %prep and %build
         so that we can read your spec file easily.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the package-review mailing list