[Bug 211761] Review Request: dfu-programmer - USB DFU based programmer for Atmel chips

bugzilla at redhat.com bugzilla at redhat.com
Tue May 8 08:41:33 UTC 2007


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: dfu-programmer - USB DFU based programmer for Atmel chips


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





------- Additional Comments From bjohnson at symetrix.com  2007-05-08 04:41 EST -------
(In reply to comment #5)
> I think I've made the corrections to Issues 1 and 2.  So for 3 and 4, should I
> build the distro tarball, copy it over to my SOURCES dir, then rpmbuild the rpm
> and upload the tarball, rpm & srpm to SF?  Or did I not understand quite right?

Unless I'm misunderstanding you, you'll want to:
1) update your spec file in your version control to add a new changelog line
consistent with the version you are about to release (say 0.4.2-1)
2) make your tarball
3) make your rpm based off the spec you just updated

when you are done, you should be able to extract the tarball from your srpm (rpm
-ivh mypackage.src.rpm) and md5sum both that and the tarball that you you
started with and they will be the same.

As far as the timestamp, I'm assuming that sf.net respects preserving timestamps
on upload.  So then the tarball on your disk, in the srpm, and uploaded all have
the same timestamp.
 
> So from here, should I rev my project to 0.4.2 with the updates & re-post?  Are
> there any actions I should take beyond that?

If you follow what I'm talking about go ahead, else if you want me to look at
your spec file one more time, just post it here (go ahead an update with the
changelog you're going to use for the next release first so I can see how it's
going to be when you release it).  Just attach it on this bug report if you want.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the package-review mailing list