Re: Re add my account?

2019-02-11 Thread Nicholas D Steeves
Hi Andreas,

On Fri, Feb 08, 2019 at 11:52:55AM +0100, Andreas Noteng wrote:
>Hello, I am a DM who have not been active for a few years, but I can still
>se my name in the list of DMs. Now coming back I see that quite a few
>things have changed. Most noteably our packages has moved to GIT it seems.
>Looks like I don't have access to this new host. How would I proceed to
>gain access and update my long neglected packages?
>My alioth username was anoteng-guest
>--
>Andreas Noteng

I'm a *very* recent member to the team, but:

Off the topic of my head, you'll need to check that your unexpired gpg
key is still on the DM keyring, register for a salsa account
(presumably anoteng-guest), read and accept both
https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
and also read & accept relevant pages on the wiki such as
https://wiki.debian.org/Python/LibraryStyleGuide#Style_Guide_for_Packaging_Python_Libraries.

Then send an email to this list with your salsa account name, the list
of your team-maintained packages, mention you confirmed your GPG key
is up-to-date on the DM keyring, and say that you read accepted those
articles on team standards.  Oh, that email is to request that
anoteng-guest be added to the salsa team.

P.S. Everyone is super busy right now, so I would anticipate a long
delay for a reply...but maybe not :-)

Cheers,
Nicholas


signature.asc
Description: PGP signature


Remove python-social-auth?

2019-02-11 Thread W. Martin Borgert

Hi,

I like to make python-social-auth a transitional package which
installs social-auth-core and social-auth-app-django. Which is
practically the new project by upstream. Or just remove it?
We don't want python-social-auth in buster, do we?

TIA & Cheers



Re: upstream release of unreleased package

2019-02-11 Thread daniel

On 10/2/19 21:37, Brian May wrote:

This is your first error. Changes to debian/* files belong to the
debian/master branch, not the patch-queue/debian/master branch.

So you should be finalise the changes to the patch-queue first, then run
something like "gbp pq export" which will switch back the the
debian/master branch, then you can make changes to the debian/* files.

Sorry, I don't have time to try to explain how to fix this right now :-(


Thanks for the information. Now I understand better the problem.