On Wed, Feb 13, 2019 at 11:11 AM Dimitri John Ledkov <x...@ubuntu.com> wrote: > > On Wed, 13 Feb 2019 at 13:42, Dan Streetman <dan.street...@canonical.com> > wrote: > > > > As far as I can tell, this hasn't been used by anyone in a long time, > > or at least only a small number of times. > > > > Can anyone who uses it let me know? > > > > I used to use it, but last few times I have tried to do it, it either > failed to open the bug report, or it was incomplete - as in, it didn't > copy the body of the bug as it used to. At the time, I did not have > time to dig into the import-bug-from-debian code to fix it up.
That's part of why I was asking - while changing u-d-t scripts to py3 i needed to adjust how it queried bts, and noticed the existing way did not correctly get the debian bug summary text. thanks for the feedback that it is (or would be, if it worked right) still useful. it's fixed in my u-d-t now: https://git.launchpad.net/~ddstreet/ubuntu-dev-tools/+git/ubuntu-dev-tools/commit/?id=e960ab737b61398f9ee2d5c0efc9e1426c32dd17 i didn't particularly like the hidden --dry-run param, nor that it still actually creates a lp bug (just in the staging area)...that's not really what "dry-run" means to me, so i changed that as well. > > I'd use it more, if it's known to work again. > > -- > Regards, > > Dimitri. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
