<RANT> So I went to request a new branch of an existing package only to find out fedrepo-req-branch, which hasn't been around that long is already depreceated and the facility brought into fedpkg... so:
$ fedpkg request-branch <branch> Could not execute request_branch: The "token" value must be set under the "fedpkg.pagure" section in your "fedpkg" user configuration
Ok, so where does that get stored?
$ man fedpkg (not in there...) $ vi /usr/share/doc/fedpkg/README (not in there...)
I figured out somewhere else that the default config is in /etc/rpkg/fedpkg.conf (In /etc/rpkg? That's intuitive!) but I didn't want to add my token to the site wide config so the search continues...
$ rpm -ql fedpkg (pokes around) $ vi /usr/lib/python2.7/site-packages/fedpkg/__main__.py ... def main(): default_user_config_path = os.path.join( os.path.expanduser('~'), '.config', 'rpkg', '%s.conf' % cli_name) ...
Found it!
Now which token do I need? The one from the src.fedoraproject.org pagure or pagure.io?
Oh and the tokens expire all the time and don't seem to have any helper scripts to automate updating of the tokens so I have to remember where they all are and manually edit them every time...
</RANT>
Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now.
Thanks, Richard
please see if helps [1] the meassage just have 5 days :) [1]https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproj ect.org/message/KS6QZQHNFCFEVJPJMFWITYWV3AHRSX5E/
On Sat, 2018-02-10 at 07:48 -0600, Richard Shaw wrote:
<RANT> So I went to request a new branch of an existing package only to find out fedrepo-req-branch, which hasn't been around that long is already depreceated and the facility brought into fedpkg... so: $ fedpkg request-branch <branch> Could not execute request_branch: The "token" value must be set under the "fedpkg.pagure" section in your "fedpkg" user configuration
Ok, so where does that get stored?
$ man fedpkg (not in there...) $ vi /usr/share/doc/fedpkg/README (not in there...)
I figured out somewhere else that the default config is in /etc/rpkg/fedpkg.conf (In /etc/rpkg? That's intuitive!) but I didn't want to add my token to the site wide config so the search continues...
$ rpm -ql fedpkg (pokes around) $ vi /usr/lib/python2.7/site-packages/fedpkg/__main__.py ... def main(): default_user_config_path = os.path.join( os.path.expanduser('~'), '.config', 'rpkg', '%s.conf' % cli_name) ...
Found it!
Now which token do I need? The one from the src.fedoraproject.org pagure or pagure.io?
Oh and the tokens expire all the time and don't seem to have any helper scripts to automate updating of the tokens so I have to remember where they all are and manually edit them every time...
</RANT>
Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now.
Thanks, Richard
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org
On samedi 10 février 2018 14:48:04 CET Richard Shaw wrote:
<RANT> So I went to request a new branch of an existing package only to find out fedrepo-req-branch, which hasn't been around that long is already depreceated and the facility brought into fedpkg... so:
$ fedpkg request-branch <branch> Could not execute request_branch: The "token" value must be set under the "fedpkg.pagure" section in your "fedpkg" user configuration
Ok, so where does that get stored?
$ man fedpkg (not in there...) $ vi /usr/share/doc/fedpkg/README (not in there...)
I figured out somewhere else that the default config is in /etc/rpkg/fedpkg.conf (In /etc/rpkg? That's intuitive!) but I didn't want to add my token to the site wide config so the search continues...
$ rpm -ql fedpkg (pokes around) $ vi /usr/lib/python2.7/site-packages/fedpkg/__main__.py ... def main(): default_user_config_path = os.path.join( os.path.expanduser('~'), '.config', 'rpkg', '%s.conf' % cli_name) ...
Found it!
Now which token do I need? The one from the src.fedoraproject.org pagure or pagure.io?
Oh and the tokens expire all the time and don't seem to have any helper scripts to automate updating of the tokens so I have to remember where they all are and manually edit them every time...
</RANT>
Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now.
Thanks, Richard
I wasn't even aware of this new use of fedpkg, but you could just have looked the help instead of searcghinq the source code:
$ fedpkg request-repo --help usage: fedpkg request-repo [-h] [--description DESCRIPTION] [--monitor {no-monitoring,monitoring,monitoring- with-scratch}] [--upstreamurl UPSTREAMURL] [--summary SUMMARY] [--exception] [bug]
Request a new dist-git repository
Before requesting a new dist-git repository for a new package, you need to generate a pagure.io API token at https://pagure.io/settings/token/new, and save it into your local user configuration located at ~/.config/rpkg/fedpkg.conf. For example:
[fedpkg.pagure] token = <api_key_here>
Below is a basic example of the command to request a dist-git repository for the package foo:
fedpkg --module-name foo request-repo 1234
positional arguments: bug Bugzilla bug ID of the package review request
optional arguments: -h, --help show this help message and exit --description DESCRIPTION, -d DESCRIPTION The repo's description in dist-git --monitor {no-monitoring,monitoring,monitoring-with-scratch}, -m {no- monitoring,monitoring,monitoring-with-scratch} The Koshei monitoring type for the repo --upstreamurl UPSTREAMURL, -u UPSTREAMURL The upstream URL of the project --summary SUMMARY, -s SUMMARY Override the package's summary from the Bugzilla bug --exception The package is an exception to the regular package review process (specifically, it does not require a Bugzilla bug)
On Sat, Feb 10, 2018 at 11:07 AM, Robert-André Mauchin zebob.m@gmail.com wrote:
I wasn't even aware of this new use of fedpkg, but you could just have looked the help instead of searcghinq the source code:
Always in the place you don't look... :)
Thanks, Richard
On Sat, 2018-02-10 at 18:07 +0100, Robert-André Mauchin wrote:
Before requesting a new dist-git repository for a new package, you need to generate a pagure.io API token at https://pagure.io/settings/token/new, and save it into your local user configuration located at ~/.config/rpkg/fedpkg.conf. For example:
[fedpkg.pagure] token =
It appears to be lying. It doesn't even open that file.
[dwoodhou@i7 master]$ sed s/token=.*/token=.../ ~/.config/rpkg/fedpkg.conf [fedpkg.pagure] token=... [dwoodhou@i7 master]$ strace -f -o foo -s 1024 fedpkg --user=dwmw2 --module-name pidgin-chime request-repo -u https://github.com/awslabs/pidgin-chime -s "Pidgin/libpurple protocol plugin for Amazon Chime" 1575008 Could not execute request_repo: The "token" value must be set under the "fedpkg.pagure" section in your "fedpkg" user configuration [dwoodhou@i7 master]$ grep fedpkg.conf foo 1236206 stat("/etc/rpkg/fedpkg.conf", {st_mode=S_IFREG|0644, st_size=1617, ...}) = 0 1236206 openat(AT_FDCWD, "/etc/rpkg/fedpkg.conf", O_RDONLY) = 3
Richard Shaw wrote:
$ fedpkg request-branch <branch> Could not execute request_branch: The "token" value must be set under the "fedpkg.pagure" section in your "fedpkg" user configuration
WTF?! So, instead of going to a web interface and making the change (old, now discontinued, pkgdb), we now have to: 1. go to the web interface 2. read the token there 3. locate a config file 4. edit the config file with a text editor 5. manually insert the token from step 2 there 6. use a CLI to make the change and that is an improvement, HOW?
Kevin Kofler
On 02/11/2018 08:40 AM, Kevin Kofler wrote:
Richard Shaw wrote:
$ fedpkg request-branch <branch> Could not execute request_branch: The "token" value must be set under the "fedpkg.pagure" section in your "fedpkg" user configuration
WTF?! So, instead of going to a web interface and making the change (old, now discontinued, pkgdb), we now have to:
- go to the web interface
- read the token there
- locate a config file
- edit the config file with a text editor
- manually insert the token from step 2 there
- use a CLI to make the change
and that is an improvement, HOW?
Been there, struggled with this and feeling really p***ed by it ;)
This pagureio stuff is a massive usability and a functional regression.
Ralf
On Sat, Feb 10, 2018 at 6:48 AM, Richard Shaw hobbes1069@gmail.com wrote:
Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now.
Thanks for speaking up about this. I'm having trouble following along with the latest changes too.
Pagure brings a ton of benefits to dist-git management, so I don't diss Pagure and all the hard work folks have put into making that a reality. I just miss the easy birds-eye-view that the pkgdb web UI provided.
- Ken
On 02/12/2018 10:14 AM, Ken Dreyer wrote:
On Sat, Feb 10, 2018 at 6:48 AM, Richard Shaw hobbes1069@gmail.com wrote:
Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now.
Thanks for speaking up about this. I'm having trouble following along with the latest changes too.
Pagure brings a ton of benefits to dist-git management, so I don't diss Pagure and all the hard work folks have put into making that a reality. I just miss the easy birds-eye-view that the pkgdb web UI provided.
I agree things are rough around the edges. Thats why I proposed the number one deliverable from our upcoming Infrastructure Hackfest ( https://fedoraproject.org/wiki/Infrastructure_Hackathon_2018 ) be cleaning up all our documentation and improving any workflows and scripts we can.
I hope we can fix some of these issues there...
kevin
On Mon, Feb 12, 2018 at 10:37:38AM -0800, Kevin Fenzi wrote:
On 02/12/2018 10:14 AM, Ken Dreyer wrote:
On Sat, Feb 10, 2018 at 6:48 AM, Richard Shaw hobbes1069@gmail.com wrote:
Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now.
Thanks for speaking up about this. I'm having trouble following along with the latest changes too.
Pagure brings a ton of benefits to dist-git management, so I don't diss Pagure and all the hard work folks have put into making that a reality. I just miss the easy birds-eye-view that the pkgdb web UI provided.
I agree things are rough around the edges. Thats why I proposed the number one deliverable from our upcoming Infrastructure Hackfest ( https://fedoraproject.org/wiki/Infrastructure_Hackathon_2018 ) be cleaning up all our documentation and improving any workflows and scripts we can.
I hope we can fix some of these issues there...
Along those lines, I would suggest collecting from this group the common workflows (if needed), document them on the wiki and advertise here for review. Then we could use that as a punch list to guide that work at the hackathon.
If someone wants to start the list of workflows, you can use this wiki section:
https://fedoraproject.org/w/index.php?title=Infrastructure_Hackathon_2018&am...
On Mon, Feb 12, 2018, at 7:37 PM, Kevin Fenzi wrote:
On 02/12/2018 10:14 AM, Ken Dreyer wrote:
On Sat, Feb 10, 2018 at 6:48 AM, Richard Shaw hobbes1069@gmail.com wrote:
Not coming from a programming background I found the learning curve pretty steep when I first tried to become a packager, I'm not sure I wouldn't have given up if I had to do it now.
Thanks for speaking up about this. I'm having trouble following along with the latest changes too.
Pagure brings a ton of benefits to dist-git management, so I don't diss Pagure and all the hard work folks have put into making that a reality. I just miss the easy birds-eye-view that the pkgdb web UI provided.
I agree things are rough around the edges. Thats why I proposed the number one deliverable from our upcoming Infrastructure Hackfest ( https://fedoraproject.org/wiki/Infrastructure_Hackathon_2018 ) be cleaning up all our documentation and improving any workflows and scripts we can.
I look forward to helping you publish this on docs.fedorproject.org ... which will be easier after the upcoming docs hackfest at the end of the month.
regards,
bex
I hope we can fix some of these issues there...
kevin
devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-leave@lists.fedoraproject.org Email had 1 attachment:
- signature.asc 1k (application/pgp-signature)
-
Brian Exelbierd -
David Woodhouse -
Ken Dreyer -
Kevin Fenzi -
Kevin Kofler -
Paul W. Frields -
Ralf Corsepius -
Richard Shaw -
Robert-André Mauchin -
Sérgio Basto