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

Re: Questions before RFS

Hi, Sergio,

On الأربعاء  7 تشرين الأول 2015 23:03, Sergio Durigan Junior wrote:
> Hello there,
> I am finishing packaging SleepyHead
> (<http://sleepyhead.sourceforge.net/wiki/>, ITP on Bug#780060), and
> Andreas kindly suggested that I put the package under the Debian Med
> umbrella (which I obviously accepted).  However, before proceeding with
> the Request for Sponsorship I would like to ask a few questions.

I can answer some of these, but not your zeroth question.

> 1) Since I am not a DD (yet), do I have to follow the procedures of
> debian-mentors for filing an RFS, or can I send the RFS directly to this
> list?

You can just email here asking for a sponsor. You don't need to go to
mentors or file an RFS bug.

> 2) I am also not a DM (yet, but I will apply very soon), but I will
> naturally be on the Uploaders section for this package.  Does this mean
> that every time I want to upload a new release I will have to ask here
> on the list for an sponsor?  Or do I have to ask on debian-mentors?

You can ask here.

> 3) I have read the policy
> <http://debian-med.alioth.debian.org/docs/policy.html>, but I could not
> find explicit instructions on how to request the creation of the git
> repository for my new package.  And then I just saw that there is a
> repository already created for it, so maybe there's no need to create
> anything new...  But I'll ask the question anyway: if I were to request
> a new repository for my new package, how should I have proceeded?

The directions are in the policy, but I just noticed that it's not under
an appropriately titled heading. See the section under "Git tips" titled
"Pushing to git.debian.org, creating a new bare repository on Alitoh"

Basically, there is a setup-repository script that you execute to create
your repository in Debian Med's git folder on Alioth. The actual
commands to do this are explained in the policy section I mentioned.

> 4) This one should probably go to debian-mentors, but I'll take my
> chances here.  SleepyHead is shipped with some bundled libraries, which
> I already removed from the compilation process in order to meet our
> policy.  However, their files are still in the tree (specifically a
> "jquery.js" file that is causing a lintian error)).  I tried using the
> "Files-Excluded:" directive on debian/copyright, without success.  I've
> seen that Andreas got involved in the discussions about implementing
> Files-Excluded, so I would like to know: what is the right thing to do
> in this case?  My current plan (not implemented yet) is to create a new
> repository with "gbp import-orig" while providing the "--filter="
> parameter to not import the bundles.  Any other suggestion?

The Files-Excluded field is taken into account by uscan when it is set
to repack the source (which is what happens if you set the repacksuffix
option in the debian/watch file-- see uscan(1) for details).

For a new package, I usually remove the offending files manually and
repack the tarball before doing gbp import-orig. I don't think it
matters how you do it. In future revisions of the package, when there's
a new release and if you have the watch file set up to repack, you can
just do `gbp import-orig --pristine-tar --uscan` and the Files-Excluded
will be honored.


Afif Elghraoui | عفيف الغراوي

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: