Bug 715366
Summary: | gnome-shell-extensions doesn't have complete SourceURL (comment) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Toshio Ernie Kuratomi <a.badger> |
Component: | gnome-shell-extensions | Assignee: | Rahul Sundaram <metherid> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | elad, metherid, michel, pikachu.2014, timur.kristof |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-09-12 10:44:22 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Toshio Ernie Kuratomi
2011-06-22 16:28:49 UTC
The information you are requesting is already documented in the .spec file. In case that is not enough for you, please look at https://bugzilla.redhat.com/show_bug.cgi?id=708230#c17 (last comment). Timur, simply add git clone git://git.gnome.org/gnome-shell-extensions to the comment, so that people who search for the repo wouldn't need to find it in bug reports. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers (In reply to comment #2) > Timur, simply add git clone git://git.gnome.org/gnome-shell-extensions to the > comment, so that people who search for the repo wouldn't need to find it in bug > reports. > That and the revision information is exactly what's needed. So adding a comment like this: # git clone -r %{commit} git://git.gnome.org/gnome-shell-extensions Reading the other bug you linked to, I also noticed that the release string is supposed to have the date followed by "git" optionally followed by the checkout hash like this: Release: 1.20110528gitg63dd27c and a subsequent update might look like: Release: 2.20110627git9de42ac4 The main reason is that the Release string provides information to two audiences: * other packagers/people who are interested in the code. Those people will be interested in the git hash. * end users who just want to know how current the package is compared to the latest tarball they saw announced on upstream's website/Debian's repositories, etc. A less major reason is that upstream may switch version control systems in which case the dates portably establish the relative age of the packages' source tarballs across the transition whereas the hashes and revision numbers do not. ie: It's clear which checkout was more recent in the following: 20110528git 20110627hg It's not clear which checkout was more recent without the dates: g63dd27cgit 1ab733be9b6ehg https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Snapshot_packages Fixed in the rawhide / F-16 branch as of 3.1.91-1 gnome-shell-extensions-3.1.91-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gnome-shell-extensions-3.1.91-1.fc16 gnome-shell-extensions-3.1.91-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gnome-shell-extensions-3.1.91-2.fc16 gnome-shell-extensions-3.1.91-3.20111001gite102c0c6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gnome-shell-extensions-3.1.91-3.20111001gite102c0c6.fc16 gnome-shell-extensions-3.2.0-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gnome-shell-extensions-3.2.0-1.fc16 |