Since the last bugzilla update, the old batch-stabilize does not work anymore ( bug #488688 ). So, please make the new batch stabilize store the passwd. Afaik William sent you a patch.
I just told ago that I have been working with you on this and sending patches to convert you over to the new Bugzilla API. I haven't sent a patch for this particular feature.
I am working on a patch to do this using cookies in a way similar to how pybugz operates. I will be attaching a patch to this bug.
(In reply to William Hubbs from comment #2) > I am working on a patch to do this using cookies in a way similar to how > pybugz operates. I will be attaching a patch to this bug. Pybugz and bugzilla no longer use cookies. They were dropped by bugzilla because they had security issues, so this can't be done with cookies any longer. (In reply to Agostino Sarubbo from bug #532054#C26) > Atm I use batch-stabilize only for the interaction with cvs. Since the > interaction with the bugzilla is half broken ( bug 488848 ) I removed this > part and I use my own version in bash. So I have a wrapper called stabilize, > which calls first the batch-stabilize and then the script which writes on > the bugzilla. > In this manner I avoid to put everytime my passwd. I haven't seen your wrapper, so I don't know what you are doing, but you can't avoid entering your username and password. Since you are modifying a bug, you must log into Bugzilla. > I hope we can improve batch-stabilize in the future to have a single tool > that does everything. What do you mean by "everything"?
(In reply to William Hubbs from comment #3) > I haven't seen your wrapper, so I don't know what you are doing, but you > can't avoid entering your username and password. Since you are modifying a > bug, you must log into Bugzilla. I need to insert the password once. Then I have a .bugz_cookie. Atm I don't need to insert the passwd everytime. > > > I hope we can improve batch-stabilize in the future to have a single tool > > that does everything. > > What do you mean by "everything"? Everything I mean write on cvs and on the bugzilla.
(In reply to Agostino Sarubbo from comment #4) > (In reply to William Hubbs from comment #3) > > I haven't seen your wrapper, so I don't know what you are doing, but you > > can't avoid entering your username and password. Since you are modifying a > > bug, you must log into Bugzilla. > I need to insert the password once. Then I have a .bugz_cookie. Atm I don't > need to insert the passwd everytime. arch-tools and pybugz now share no code at all, and all of the arch-tools require a username and password whenever you run them. What I would have to do if you don't want to enter a username/password is figure out a way to let you save the token to a file so you can reuse it, but I would rather not share the same file as pybugz. > > > > > I hope we can improve batch-stabilize in the future to have a single tool > > > that does everything. > > > > What do you mean by "everything"? > > Everything I mean write on cvs and on the bugzilla. Batch-stabilize already does this once you sign in doesn't it?
(In reply to William Hubbs from comment #5) > arch-tools and pybugz now share no code at all, and all of the arch-tools > require a username and password whenever you run them. Well, since I'm using batch-stabilize to write in cvs, and pure pybugz via bash script to write on the bugzilla, since I did bugz login, I'm not entering a passwd since months... > Batch-stabilize already does this once you sign in doesn't it? Yes, but it is a pita insert user/pass for every stabilization.
(In reply to William Hubbs from comment #5) [...] > Batch-stabilize already does this once you sign in doesn't it? @Williamh, batch-stabilize still requests for password each time we invoke it :/
(reassigning to the first person on the ACL, CC-ing everybody else)
arch_tools is a project started by phajdan.jr which atm is a retired developer. I made an ebuild that is is my overlay but atm I have nothing to do with this project because I'm not using those scripts to commit. I asked mgorny to grant permission for all developers. If someone want to improve the project, it is on our git repo: https://gitweb.gentoo.org/proj/arch-tools.git/ For now, I'm closing it as WONTFIX
