Hi,
Dmitry Shachnev píše v So 12. 01. 2019 v 20:34 +0300:
> Looks like you were added to DPMT but not PAPT:
yes, sorry, my mistake. Fixed.
--
Ondřej Nový
vedoucí vývoje Zprávy/TV
tel: +420 777 963 207
On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote:
> > just drop the python-debianbts binary, without doing any kind of
> > strange migration, and keep the name python-debianbts for the
> > python3 package, as the Debian Python Policy states.
>
> I think there's an error in your
On Sat, Jan 12, 2019 at 06:14:51PM +0100, Geert Stappers wrote:
> Thanks
>
> Tried it today:
>
>
> $ git push --all
> Username for 'https://salsa.debian.org': stappers
> Password for 'https://stapp...@salsa.debian.org':
> remote: You are not allowed to push code to this project.
> fatal: unable
On Wed, Jan 09, 2019 at 02:13:00PM +0100, Ondrej Novy wrote:
> Hi,
>
> pá 4. 1. 2019 v 22:16 odesílatel Geert Stappers napsal:
>
> > Could you please add my account to PAPT and/or the python-team?
> >
>
> welcome :)
>
Thanks
Tried it today:
$ git push --all
Username for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 12.01.19 um 16:49 schrieb Andrey Rahmatullin:
> On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote:
The question is: if I drop Python2 support, what happens with
the package names? Should I simply provide the
On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote:
> >> The question is: if I drop Python2 support, what happens with the
> >> package names? Should I simply provide the python3-debianbts and
> >> drop python-debianbts, or shall I attempt some kind of migration
> >> to make the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Am 12.01.19 um 16:32 schrieb Mattia Rizzolo:
> On Sat, Jan 12, 2019 at 04:28:26PM +0100, Bastian Venthur wrote:
>> The question is: if I drop Python2 support, what happens with the
>> package names? Should I simply provide the python3-debianbts and
On Sat, Jan 12, 2019 at 04:28:26PM +0100, Bastian Venthur wrote:
> The question is: if I drop Python2 support, what
> happens with the package names? Should I simply provide the
> python3-debianbts and drop python-debianbts, or shall I attempt some
> kind of migration to make the python-debianbts
Hi,
I'm about to drop Python2 support for python-debianbts. Currenty the
source package produces two packages: python-debianbts and
python3-debianbts. The question is: if I drop Python2 support, what
happens with the package names? Should I simply provide the
python3-debianbts and drop
9 matches
Mail list logo