Overview
Request 648363 superseded
- Created by a_jaeger
- In state superseded
- Superseded by 649537
- Open review for legal-auto
- Open review for jengelh
- Open review for openSUSE:Factory:Staging:B
Request History
a_jaeger created request
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto added repo-checker as a reviewer
Please review build success
factory-auto accepted review
Check script succeeded
jengelh added jengelh as a reviewer
staging-bot set openSUSE:Factory:Staging:B as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:B"
staging-bot accepted review
Picked openSUSE:Factory:Staging:B
dimstar accepted review
Let's not block an SR based on a known, old issue in the service definitions used:
https://github.com/openSUSE/obs-service-tar_scm/issues/154
repo-checker accepted review
cycle and install check passed
dimstar_suse changed priority to moderate => important
raising priority for openSUSE:Factory:Staging:B
Please use real identities, not opensuse-packaging@opensuse.org (who is that, anyway?)
This is from "obs service run", feature: "*_scm" <param name="changesgenerate">enable</param> parameter. It would be a nice enhancement if the user is put there who run this service, instead the need of adjusting this everytime.
That sounds like you should set up a
~/.oscrc
if you don't have one yet. After all, the services only run manually (due tomode=disabled
) and in full conciousness (so I hope)..oscrc does not help. You can explicitly run this service locally (that is what it is for afaik and how I use it as well). You then get a new tarball and latest version set without manual download and fiddling. A nice feature would be to recognize the user from ~/.oscrc when issuing this locally.
if you call osc service locally to produce the changes entries, osc picks up the first 'email=' in .oscrc; so you can configure this to be your own email address instead of a mailing list (giving this as maintainer address means people might want to reach out there about issues - but by far not everybody is on the list and we'd not want that list to become a 'packaging bug list')