Hi Hannah,

Hannah Rittich <v...@rittich.net> writes:

> Hi,
>
> I have created a patch set which allows to specify a prefix for the
> files and directories that are installed into system directories. These
> patches have also been accepted by the upstream author. Thus, the
> packages cpputilities and qtutilities can be installed using a more
> specific naming.
>

Wow!  I'm sorry for holding you back, this is excellent work.

> I have updated the Debian packages for cpp-utilities, qtutilities, and
> Syncthing Tray to include the patches and renamed the source packages.
> The sources are on Salsa.
>
> How do we proceed now?
>

Have you read any of the New Maintainer Docs, and Debian Policy?  Are
you familiar with Lintian?  Expectations for all uploads are that
they're Policy-compliant, DFSG-free, and Lintian-clean.  It's also worth
reading the ftpmaster "Reject FAQ for Debian's NEW-Queue".

First, file ITP (Intent to Package) bug reports for the two dependencies
using their prefixed source package names.  You will close these bugs in
each package's first changelog entry.  This is required.  Yes, I was
lazy and didn't file ITPs for cpp-utilities, qtutilities--even though I
was working on them.  Yes, I should have filed them.

There is no need to file an RFS (Request for Sponsorship) for these
three packages, because I've committed to reviewing and sponsoring them.

You'll also need to do a formal copyright review which is (infamously)
not fun for most people.  I've already done the reviews on my copies, so
if you'd like to skip this for these three packages, I'm completely ok
with it and can just merge my work.  Formal copyright reviews are also
part of the basic skill-set for Debian packaging work.  Part of this
also requires identifying binary blobs, embedded copies, and assets of
questionable origin.

  https://www.debian.org/social_contract
  https://wiki.debian.org/DebianFreeSoftwareGuidelines
  https://wiki.debian.org/DFSGLicenses

Let me know if you prefer to do a copyright review on these packages, or
save it for another time.

Best,
Nicholas

Attachment: signature.asc
Description: PGP signature

Reply via email to