Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 61196 - two different builds of same ethereal srpm
two different builds of same ethereal srpm
Product: Red Hat Linux
Classification: Retired
Component: ethereal (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Phil Knirsch
Depends On:
Blocks: 61590
  Show dependency treegraph
Reported: 2002-03-15 00:27 EST by Chris Ricker
Modified: 2015-03-04 20:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-03-26 07:17:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Ricker 2002-03-15 00:27:21 EST
The ethereal-0.9.0-2 and ethereal-gnome-0.9.0-2 rpms in rawhide and in beta2 are
different from each other
Comment 1 Phil Knirsch 2002-03-18 10:50:36 EST
Yes, and? Whats your point? Rawhide is know to break things and no version
number guarantees for betas were ever given, only for final official products.

Read ya, Phil
Comment 2 Chris Ricker 2002-03-18 12:21:08 EST
the point is that you've now thrown out all ability to track bug reports by
package version, since there are two packages being distributed with different
bugs and the exact same package version....

see the discussion about all this on the testers-list on the 15th
Comment 3 Phil Knirsch 2002-03-26 08:01:59 EST
OK, will be fixed in rawhide and betas real soon now (just rebuilding it with a
new release number).

Read ya, Phil
Comment 4 Jay Turner 2002-03-26 08:54:38 EST
0.9.0-3 is currently in 7.3-HEAD, so just waiting for it to get into a Hampton
Comment 5 Phil Knirsch 2002-03-26 08:59:51 EST
Errh, who built that?!? Luckily i am building a new one with -4 right now with
another fix, so we should be fine as well.

Read ya, Phil

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