Re: How to report bugs with the new git repo?

[Pavlo Solntsev]

Thank you All for the discussion. It looks like official part, e.g. bug
registration, should be done as usually, while technical work may be done
using git lab.

-Pavlo Solntsev
-

*Please avoid sending me Word or PowerPoint attachments.See
http://www.gnu.org/philosophy/no-word-attachments.html
*

On Thu, Feb 15, 2018 at 6:33 PM, Sean Whitton 
wrote:

> Hello Pavlo,
>
> On Thu, Feb 15 2018, Pavlo Solntsev wrote:
>
> > I am very excited to see that Debian has moved to GitLab (
> > https://salsa.debian.org). With this change, I am wondering how bug
> > report process should look like? Now, I want to submit patches to
> > packages, e.g.  libgdamm. What would be the best process: submit a
> > patch via push request in the Debian repo, or push patches to
> > upstream?
>
> Your choices are basically:
>
> - send a patch to the bug as before, ideally adding the patch tag, with
>   patch attached
>
> - send an e-mail to the bug, ideally adding the patch tag, including a
>   URI to your merge request.
>
> --
> Sean Whitton
>

Re: How to report bugs with the new git repo?

[Sean Whitton]

Hello Pavlo,

On Thu, Feb 15 2018, Pavlo Solntsev wrote:

> I am very excited to see that Debian has moved to GitLab (
> https://salsa.debian.org). With this change, I am wondering how bug
> report process should look like? Now, I want to submit patches to
> packages, e.g.  libgdamm. What would be the best process: submit a
> patch via push request in the Debian repo, or push patches to
> upstream?

Your choices are basically:

- send a patch to the bug as before, ideally adding the patch tag, with
  patch attached

- send an e-mail to the bug, ideally adding the patch tag, including a
  URI to your merge request.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: How to report bugs with the new git repo?

[Pavlo Solntsev]

OK,
it looks like it is clear. Thanks.


-Pavlo Solntsev

-

*Please avoid sending me Word or PowerPoint attachments.See
http://www.gnu.org/philosophy/no-word-attachments.html
*

On Thu, Feb 15, 2018 at 11:35 AM, Mattia Rizzolo  wrote:

> On Thu, Feb 15, 2018 at 08:24:21PM +0500, Andrey Rahmatullin wrote:
> > If the question is "how should I send a patch to the maintainer" then a
> > pull request is just one of the available ways, and the best one was
> > always opening a bug report in the BTS, sending the changes in some other
> > way directly to the maintainer was always possible too.
>
> On this note, consider that I'm not sure people have realized they need
> to subscribe ("watch") the gitlab project to receive notifications about
> new MRs.
>
> At least I already encountered two maintainers who didn't and miss some
> MRs until poked elsewhere.
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>

Re: How to report bugs with the new git repo?

[Mattia Rizzolo]

On Thu, Feb 15, 2018 at 08:24:21PM +0500, Andrey Rahmatullin wrote:
> If the question is "how should I send a patch to the maintainer" then a
> pull request is just one of the available ways, and the best one was
> always opening a bug report in the BTS, sending the changes in some other
> way directly to the maintainer was always possible too.

On this note, consider that I'm not sure people have realized they need
to subscribe ("watch") the gitlab project to receive notifications about
new MRs.

At least I already encountered two maintainers who didn't and miss some
MRs until poked elsewhere.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Re: How to report bugs with the new git repo?

[Ole Streicher]

"W. Martin Borgert"  writes:
> If it is (probably) a Debian bug, submit bug (and patch) to the
> Debian BTS. Ideally, using the "reportbug" command.

I would prefer a merge request over a bug with an attached patch: the
gitlab workflow is quite effective, especially when compared to a
(randomly formatted) patch file. And I also like that the patch author
is automatically attributed when the patch is accepted.

Is it possible to setup a gitlab hook that automatically generates a
"patch" tagged bug report when a merge request is created?

Cheers

Ole

Re: How to report bugs with the new git repo?

[Andrey Rahmatullin]

On Thu, Feb 15, 2018 at 09:00:28AM -0600, Pavlo Solntsev wrote:
> I am very excited to see that Debian has moved to GitLab (
> https://salsa.debian.org). With this change, I am wondering how bug report
> process should look like? 
I don't think anything has changed.

>  Now, I want to submit patches to packages, e.g.
> libgdamm. What would be the best process: submit a patch via push request
> in the Debian repo, or push patches to upstream?
If the question is "whether I should send the changes to the upstream
authors or to the maintainer" then nothing has changed.
If the question is "how should I send a patch to the maintainer" then a
pull request is just one of the available ways, and the best one was
always opening a bug report in the BTS, sending the changes in some other
way directly to the maintainer was always possible too.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: How to report bugs with the new git repo?

[W. Martin Borgert]

Quoting Pavlo Solntsev :

Now, I want to submit patches to packages, e.g.
libgdamm. What would be the best process: submit a patch via push request
in the Debian repo, or push patches to upstream?


If it is (probably) a Debian bug, submit bug (and patch) to the
Debian BTS. Ideally, using the "reportbug" command.

If it is (probably) an upstream bug, submit the bug to upstream
in the form prefered by upstream.

Cheers

How to report bugs with the new git repo?

[Pavlo Solntsev]

Hello,

I am very excited to see that Debian has moved to GitLab (
https://salsa.debian.org). With this change, I am wondering how bug report
process should look like? Now, I want to submit patches to packages, e.g.
libgdamm. What would be the best process: submit a patch via push request
in the Debian repo, or push patches to upstream?

Thanks,

-Pavlo Solntsev
-

*Please avoid sending me Word or PowerPoint attachments.See
http://www.gnu.org/philosophy/no-word-attachments.html
*