[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1091185: marked as done (RFS: racket-mode/20241217~git.3dc8c17-1 -- emacs support for editing and running racket code)

Your message dated Fri, 27 Dec 2024 13:28:39 +0000
with message-id <875xn5p854.fsf@zephyr.silentflame.com>
and subject line Re: Bug#1091185: RFS: racket-mode/20241217~git.3dc8c17-1 -- emacs support for editing and running racket code
has caused the Debian Bug report #1091185,
regarding RFS: racket-mode/20241217~git.3dc8c17-1 -- emacs support for editing and running racket code
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1091185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091185
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "racket-mode":

 * Package name     : racket-mode
   Version          : 20241217~git.3dc8c17-1
   Upstream contact : Greg Hendershott <git@greghendershott.com>
 * URL              : https://github.com/greghendershott/racket-mode
 * License          : GPL-3+
 * Vcs              : https://salsa.debian.org/emacsen-team/racket-mode
   Section          : editors

The source builds the following binary packages:

  elpa-racket-mode - emacs support for editing and running racket code

To access further information about this package, please visit the following URL:

  https://mentors.debian.net/package/racket-mode/

Alternatively, you can download the package with 'dget' using this command:

  dget -x https://mentors.debian.net/debian/pool/main/r/racket-mode/racket-mode_20241217~git.3dc8c17-1.dsc

Changes since the last upload:

 racket-mode (20241217~git.3dc8c17-1) experimental; urgency=medium
 .
   * Update to new upstream version 20241217~git.3dc8c17
   * Update d/watch scheme to include commit hash
   * Bump debhelper from old 12 to 13
   * Set upstream metadata fields: Bug-Database, Bug-Submit,
     Repository-Browse
   * Use canonical URL in Vcs-Browser
   * Update standards version to 4.7.0, no changes needed
   * Drop oldoldstable emacs version in Recommends in d/control
   * Add "Rules-Requires-Root: no" to d/control
   * Update build-depends required for tests in d/control
   * Change section from lisp to editors in d/control
   * Set user-emacs-directory to a temp path required by tests in
     d/elpa-test
   * Enable elpa test in d/rules
   * Add Upstream-Contact in d/copyright
   * Update license from GPL-2+ to GPL-3+ as per upstream in d/copyright
     - Upstream updated the license from version 2 and later to version 3
       and later in 2022.
   * Add copyright clause for debian directory in d/copyright (Closes:
     #1091177)
     - Copyright holder is David Bremner based on history and granted by
       David.
     - Also add comments stating that the license of "debian/*" should
       follow upstream as granted by David.
     - Add David's email at Bug#1091177 as reference for clarification.
   * Add d/gbp.conf matching the current practice
   * Add d/README.Debian to document the dgit-maint-debrebase workflow
   * Add myself to Uploaders in d/control


-- 
Regards,
Xiyue Deng

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hello,

On Fri 27 Dec 2024 at 01:29am -08, Xiyue Deng wrote:

> Hi Sean,
>
> Sean Whitton <spwhitton@spwhitton.name> writes:
>
>> Hello Xiyue,
>>
>> This is a git-debrebase package; are you aware of that?
>>
>> It's important that you know the workflow in use before adding you to
>> Uploaders.
>>
>
> Yes, I am aware.  I took some time to read git-debrebase(5) to
> re-enforce my understanding of the concepts of the branches, merges, and
> states.  I made sure that it was stitched since commit 1b96c5fa before
> making Debian specific changes so that it stayed stitched, and also
> documented this workflow in README.source in 26b94c87.  I also worked on
> js2-mode which also uses the git-debrebase flow.

Coolio, thanks.

It looks like you put it in README.Debian by mistake, btw.
README.source would be the correct place.  I'll fix it.

Also, it looks like you might not have seen 97dc4ef?
I'll restore the <!nocheck>.
To let you know how I got there: I was verifying that the merge in of my
NMU was correct.  I started by typing 'git debrebase' (since I knew I
was going to restitch; see below) and then used
'git diff dgit/dgit/sid..46478be'.  This led me to find a series of
commits by David.

Thanks for fixing the tests, btw.

> Hopefully I'm doing the right thing here.  But please do correct me if
> anything doesn't look right.

If I'm reading the history correctly, I believe that it would be more
usual to stitch after making all your changes, not only after importing
the upstream changes.

The thing about not touching the upstream source before making
Debian-specific changes is only when a package is first converted to use
git-debrebase.  After that you're fine.

If you can identify what it is in the git-debrebase docs that confused
you here, please consider proposing a patch.

In the meantime, I'll do a debrebase myself before uploading in order
that there's a more usual history.

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: