Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 154248 - Satellite should handle .nosrc.rpm packages
Satellite should handle .nosrc.rpm packages
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Wregglesworth
David Lutterkort
Depends On: 155374
Blocks: 147875 161444 165746
  Show dependency treegraph
Reported: 2005-04-08 14:16 EDT by Steve Conklin
Modified: 2013-04-30 19:39 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHN 4.0.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-31 22:39:36 EDT
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 Steve Conklin 2005-04-08 14:16:42 EDT
Description of problem:

rhnpush fails for .nosrc.rpm packages. .nosrc.rpm is an accepted package file
extension, and should be valid for use with the satellite.

For more information, see IT#68302.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Mihai Ibanescu 2005-04-14 18:26:38 EDT
did you try to use --source? Source rpms are "special".
Comment 2 Mihai Ibanescu 2005-04-14 18:27:18 EDT
Oh, sorry, misread the bug report - .nosrc.rpm are not exactly supported by os
Comment 3 Mihai Ibanescu 2005-04-14 18:28:42 EDT
John, can you please try to reproduce the error? We can try to patch it to work
with those packages, but AFAIR it's really difficult to know it's a nosrc.rpm -
nothing in the rpm header tells you that.
Comment 4 John Wregglesworth 2005-04-15 10:52:40 EDT
I tried uploading a nosrc rpm without --source and got this traceback:
Traceback (most recent call last):
  File "rhnpush.py", line 413, in ?
    sys.exit(main() or 0)
  File "rhnpush.py", line 133, in main
  File "rhnpush.py", line 276, in packages
    ret = self.package(p)
  File "rhnpush.py", line 301, in package
    h = uploadLib2.get_header(package, source=self.options.source)
  File "uploadLib2.py", line 598, in get_header
    raise UploadError("Unexpected RPM package type")
uploadLib2.UploadError: Unexpected RPM package type

When I tried uploading the package using --source it supposedly uploads the
package to the channel (gets a 200 result code), but I can't find it anywhere
through the web interface. It looks like rhnpush treats nosrc packages the same
way it treats src packages.
Comment 5 John Wregglesworth 2005-05-25 12:32:18 EDT
Test Plan:

o Find a nosrc rpm and a binary version of the nosrc rpm.

o Using rhnpush, push the binary version of the nosrc rpm into a channel.

  rhnpush --server=servername/APP --channel=channel_name file.rpm

o Using rhnpush, push the nosrc rpm using the --source option. Doesn't have to
be into a channel.

  rhnpush --server=servername/APP --source ~/file.nosrc.rpm

o Through the web interface, go to Channels->Manage Software Channels->Manage
Software Packages and click on the name of the binary rpm that you pushed earlier.

o The Source RPM field should list the nosrc version of the rpm that you pushed

o The Download section at the bottom of the screen should list the nosrc rpm as
being available for download.

o Download the nosrc rpm and ensure that the filename is correct.
Comment 12 David Lutterkort 2005-08-03 19:41:11 EDT
Excellent ! Works with rhnpush-4.0.0-156.rhel4 from

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