Bug 225298 - Merge Review: automake14
Merge Review: automake14
Product: Fedora
Classification: Fedora
Component: Package Review (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Patrice Dumas
Fedora Package Reviews List
Depends On:
  Show dependency treegraph
Reported: 2007-01-29 16:08 EST by Nobody's working on this, feel free to take it
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-03-13 11:40:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
pertusus: fedora‑review+

Attachments (Terms of Use)

  None (edit)
Description Nobody's working on this, feel free to take it 2007-01-29 16:08:45 EST
Fedora Merge Review: automake14

Comment 1 Patrice Dumas 2007-02-16 02:15:33 EST
* I think that autoconf isn't needed as BR

* What is the point of
mkdir -p info
mv automake14.info* info

* The Requires: perl is automatically found, so you can omit it
  if you like
Comment 2 Karsten Hopp 2007-02-19 06:56:36 EST
verified that it builds fine in mock without the autoconf BR, dropped perl
requirement in -15
Comment 3 Patrice Dumas 2007-02-23 17:15:31 EST
I don't see any other issue, it is approved.
Comment 4 Patrice Dumas 2007-02-24 07:53:10 EST
I have checked that source match upstream, however the tarball
timestamp isn't the same, this should be fixed. I am not sure
that it can be easily done now that the tarball is in the look-aside
cache, though.
Comment 5 Karsten Hopp 2007-02-26 05:51:17 EST
I can't fix this, our scripts check the md5sum and won't allow a me to replace
the file with just a different timestamp. 
Comment 6 Patrice Dumas 2007-02-26 18:03:34 EST
No problem, it is not a big deal, just try to do it next time.
Comment 7 Karsten Hopp 2007-03-13 11:40:39 EDT
Closing as suggested by Warren in his mail to fedora-maintainers 'Review with
Flags (Version 6)'

Note You need to log in before you can comment on or make changes to this bug.