Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #16927

Re: [src:backintime] Upload despite Hard Freeze (no response from maintainer/uploader)

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On Monday, June 16, 2025 6:22:44 AM Mountain Standard Time c.buhtz@posteo.jp 
wrote:
> Hello Carsten,
> thank you for the reply.
> 
> Am 16.06.2025 14:51 schrieb Carsten Schoenert:
> > You can't do anything on this except asking or find some DD who would
> > be willing to do this.
> 
> I see. And asking on that list was the best thing to do? Or is there
> another appropriate channel or medium I should use for asking?

To be more express, you only need a Debian Developer to sponsor the upload.  
If you are willing to do the packaging yourself, you can prepare everything 
and then file a RFS (Request For Sponsor) asking that a Debian Developer 
sponsor the upload.

Given that you are the upstream maintainer, that this bug has significant 
consequences for users, and that the changes are minimal, I think your chances 
of finding a sponsor for a prepared upload are pretty good (I would be willing 
to sponsor it).

There is information about the RFS procedure at:

https://mentors.debian.net/intro-maintainers/

If you are interested in going this route, I would recommend you fork the 
package on Salsa (you can request an account if you don’t already have one), 
prepare your changes in the fork, upload it to Mentors, and file an RFS.

This package uses gbp (Git-Buildpackage) with pristine-tar enabled.

https://wiki.debian.org/PackagingWithGit

You can choose to do an upgrade to your new upstream, which (once you have a 
working gbp setup), can be as easy as “gbp import-orig --uscan” and then 
editing debian/copyright and debian/changelog.

Or, you could backport your change using a patch, which means you don’t have 
to figure out how to use gbp, but you do need to figure out how to use quilt 
(if you don’t have any experience with it).

https://wiki.debian.org/UsingQuilt

If you are interested in going this route, feel free to email me directly with 
any questions.

-- 
Soren Stoutner
soren@debian.org

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

[src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) <c.buhtz@posteo.jp> - 2025-06-14 17:20 +0200
  Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Emmanuel Arias <eamanu@debian.org> - 2025-06-14 22:40 +0200
    Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) <c.buhtz@posteo.jp> - 2025-06-16 07:50 +0200
      Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) c.buhtz@posteo.jp - 2025-06-16 13:40 +0200
        Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Carsten Schoenert <c.schoenert@t-online.de> - 2025-06-16 15:10 +0200
          Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) c.buhtz@posteo.jp - 2025-06-16 15:30 +0200
              Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Soren Stoutner <soren@debian.org> - 2025-06-16 19:30 +0200
              Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) c.buhtz@posteo.jp - 2025-06-16 23:20 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Nicholas D Steeves <sten@debian.org> - 2025-06-16 23:50 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) c.buhtz@posteo.jp - 2025-06-17 09:00 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Nicholas D Steeves <sten@debian.org> - 2025-06-17 16:00 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Andrey Rakhmatullin <wrar@debian.org> - 2025-06-17 00:20 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) c.buhtz@posteo.jp - 2025-06-17 09:00 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Andrey Rakhmatullin <wrar@debian.org> - 2025-06-17 09:10 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Andrey Rakhmatullin <wrar@debian.org> - 2025-06-17 09:50 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) c.buhtz@posteo.jp - 2025-06-17 09:50 +0200
                  Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Soren Stoutner <soren@debian.org> - 2025-06-17 23:20 +0200
                Re: [src:backintime] Upload despite Hard Freeze (no response from maintainer/uploader) Nick Morrott <knowledgejunkie@gmail.com> - 2025-06-17 23:50 +0200
                  Re: [src:backintime] Upload despite Hard Freeze (no response from  maintainer/uploader) Soren Stoutner <soren@debian.org> - 2025-06-18 00:00 +0200

csiph-web