[sr #106712] accepting follow-ups by email

[Ineiev]

Update of sr #106712 (group administration):

  Depends on: => support #06


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature

[sr #111106] Need a way to disable email replies to savannah trackers mails, on a per-project basis

[Ineiev]

Follow-up Comment #1, sr #06 (group administration):

On Wed, Aug 14, 2024 at 01:59:25PM -0400, Bruno Haible wrote:
> Now, for two weeks (more precisely, since
>
https://git.savannah.gnu.org/gitweb/?p=administration/savane.git;a=commitdiff;h=940893361e4e6d9ce2b5c010613595b83c80529f
> ), the sent mail contains
> 1) a line "Include the next line when replying by email."
> 2) a CC such as 362990-bugs-savannah 
> which makes the recipient think that they can / should reply by mail.

If they think so, they are correct at least partially: they
can comment on the tracker through email.

> Please provide a way to turn this off on a per-project/package basis.

The feature offers users an option to post on trackers using
GnuPG-authenticated email. it's up to the user who submits comments
what way to use, handling that on per-package basis is pointless.

What I can think of instead is,

* improving the comment "Include the next line when replying by email.";
* changing the Reply-To: header to avoid the mailing lists;
* adding a user preference to include that data, disabled by default.



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/


signature.asc
Description: PGP signature

[sr #111106] Need a way to disable email replies to savannah trackers mails, on a per-project basis

[Ineiev]

Update of sr #06 (group administration):

  Status:None => In Progress
 Assigned to:None => ineiev 


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature

[sr #111023] My account is in some weird half-existent state

[Ineiev]

Update of sr #111023 (group administration):

  Status:   Need Info => Done   
 Open/Closed:Open => Closed 


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature

[sr #111106] Need a way to disable email replies to savannah trackers mails, on a per-project basis

[Bruno Haible]

Follow-up Comment #2, sr #06 (group administration):


> they are correct at least partially: they can comment on the tracker through
email.

I would have nothing against that, if it was guaranteed that the reply ends up
in the tracker, at that ticket.

> The feature offers users an option to post on trackers using
GnuPG-authenticated email.

Ah, that explains why the reply ended up on the mailing list, not on the
tracker. In order to prevent that, please add some text to the reply, to
explain the feature and its limitations. Either


DO NOT REPLY BY MAIL unless you are using GnuPG-authenticated email.


or, with some more verbosity:


To reply to this notification, you have two options:
* Reply in the tracker at https://savannah.gnu.org/bugs/ after logging
in, or
* By email, IF AND ONLY IF you are using GnuPG-authenticated email AND you
include the following line in the reply:
{savane: user = 1871; tracker = support; item = 06}


Rationale: 99% of the people I know use email without GnuPG-authentication. It
is therefore essential to remind people that this is a requirement for not
creating a communication mess.

> changing the Reply-To: header to avoid the mailing lists

This would be even worse, because it would turn the discussion into a private
email discussion. It is essential for the community that discussions happen in
public.

> adding a user preference to include that data, disabled by default.

That is also a possibility; if so, please include the notice about
GnuPG-authentication here as well.



___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.nongnu.org/


signature.asc
Description: PGP signature

[sr #111106] Need a way to disable email replies to savannah trackers mails, on a per-project basis

[Ineiev]

Follow-up Comment #3, sr #06 (group administration):


> > The feature offers users an option to post on trackers using
> GnuPG-authenticated email.
>
> Ah, that explains why the reply ended up on the mailing list, not on the
> tracker.

/Just explaining this to myself:/ That explains why the reply ended up
_only_ on the mailing list but not on the tracker.  the Reply-To:
header contained both addresses, and I believe the poster sent
the message to all.  GnuPG signature by itself doesn't direct
it to savannah-trackers@ rather than to the mailing list.

> In order to prevent that, please add some text to the reply, to
> explain the feature and its limitations.
...
> To reply to this notification, you have two options:
> * Reply in the tracker at https://savannah.gnu.org/bugs/ after
logging
> in, or
> * By email, IF AND ONLY IF you are using GnuPG-authenticated email AND you
> include the following line in the reply:


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/


signature.asc
Description: PGP signature

[sr #111106] Need a way to disable email replies to savannah trackers mails, on a per-project basis

[Ineiev]

Follow-up Comment #4, sr #06 (group administration):


> > The feature offers users an option to post on trackers using
> GnuPG-authenticated email.
>
> Ah, that explains why the reply ended up on the mailing list, not on the
> tracker.

/Just explaining this to myself:/ That explains why the reply ended up
_only_ on the mailing list but not on the tracker.  the Reply-To:
header contained both addresses, and I believe the poster sent
the message to all.  GnuPG signature by itself doesn't direct
it to savannah-trackers@ rather than to the mailing list.

> In order to prevent that, please add some text to the reply, to
> explain the feature and its limitations.
...
> To reply to this notification, you have two options:
> * Reply in the tracker at https://savannah.gnu.org/bugs/ after
logging
> in, or
> * By email, IF AND ONLY IF you are using GnuPG-authenticated email AND you
> include the following line in the reply:
> {sa+nomarkup+vane:-nomarkup- user = 1871; tracker = support; item = 06}

Thank you, I shall.

> > changing the Reply-To: header to avoid the mailing lists
>
> This would be even worse, because it would turn the discussion into a
private
> email discussion. It is essential for the community that discussions happen
in
> public.

I see.

>> adding a user preference to include that data, disabled by default.
>
> That is also a possibility; if so, please include the notice about
> GnuPG-authentication here as well.

I'll bear this in mind if I implement this.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/


signature.asc
Description: PGP signature

Re: remote unpack failed (Savannah git repository of Gnulib)

[Paul Eggert]

On 2024-07-15 15:44, Bob Proulx wrote:

Bruno Haible was the first to report the problem yesterday and got me
on the task.  I admit that it took me some hair pulling before I
realized the error and corrected it.


Thanks, but unfortunately I'm seeing similar failures now, trying to 
commit to GNU cpio:


$ git push
Enumerating objects: 23, done.
Counting objects: 100% (23/23), done.
Delta compression using up to 12 threads
Compressing objects: 100% (11/11), done.
Writing objects: 100% (12/12), 9.69 KiB | 1.38 MiB/s, done.
Total 12 (delta 9), reused 0 (delta 0), pack-reused 0
error: remote unpack failed: unable to create temporary object directory
To git.sv.gnu.org:/srv/git/cpio.git
 ! [remote rejected] master -> master (unpacker error)
error: failed to push some refs to 'git.sv.gnu.org:/srv/git/cpio.git'


I waited a bit and tried again, but still had the same symptoms.

Hmm July 15, then August 15 - is this some phase-of-the-moon thing?

Re: remote unpack failed (Savannah git repository of Gnulib)

[Bob Proulx]

Hi Paul,

Paul Eggert wrote:
> Thanks, but unfortunately I'm seeing similar failures now, trying to commit
> to GNU cpio:
>
> $ git push
> Enumerating objects: 23, done.
> Counting objects: 100% (23/23), done.
> Delta compression using up to 12 threads
> Compressing objects: 100% (11/11), done.
> Writing objects: 100% (12/12), 9.69 KiB | 1.38 MiB/s, done.
> Total 12 (delta 9), reused 0 (delta 0), pack-reused 0
> error: remote unpack failed: unable to create temporary object directory
> To git.sv.gnu.org:/srv/git/cpio.git
>  ! [remote rejected] master -> master (unpacker error)
> error: failed to push some refs to 'git.sv.gnu.org:/srv/git/cpio.git'

Whatever the current problem is the problem is a different problem
from before.  And I can git-push okay on my test repository.

> I waited a bit and tried again, but still had the same symptoms.

I am looking in and poking around and looking for something that might
be the problem.

> Hmm July 15, then August 15 - is this some phase-of-the-moon thing?

Hopefully that's just coincidental!

Bob

Re: remote unpack failed (Savannah git repository of Gnulib)

[Bob Proulx]

Bob Proulx wrote:
> Paul Eggert wrote:
> > error: remote unpack failed: unable to create temporary object directory

For the list this was a permission problem.  We have things understood
now.  It wasn't something that would affect others globally.

> > Hmm July 15, then August 15 - is this some phase-of-the-moon thing?
>
> Hopefully that's just coincidental!

And thankfully it was!  Whew! :-)

Bob