e team policy[5]. I'm fine with creating a MR
> to be discussed rather in Salsa than this mailing list - whatever seems
> worthwhile to you.
I support this change to the team policy.
--
Arto Jantunen
Package: wnpp
Severity: wishlist
Owner: Arto Jantunen
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-python@lists.debian.org
* Package name: aiohttp-oauthlib
Version : 0.1.0
Upstream Contact: Hugo Osvaldo Barrera
* URL : https://git.sr.ht/~whynothugo/aiohttp
ader for it (I already maintain sqlacodegen, even though it appears
to have been abandoned upstream).
--
Arto Jantunen
Package: wnpp
Severity: wishlist
Owner: Arto Jantunen
* Package name: python-aioinflux
Version : 0.9.0
Upstream Author : Gustavo Bezerra
* URL : https://github.com/gusutabopb/aioinflux
* License : MIT
Programming Lang: Python
Description
sion 1.9.0 in 2011.
What is new is that pytrainer also directly uses sqlalchemy, instead of
just the transitive dependency of pytrainer -> migrate -> sqlalchemy.
--
Arto Jantunen
ghisv...@gmail.com writes:
> On Tue, 2018-10-16 at 11:45 +0300, Arto Jantunen wrote:
>> ghisv...@gmail.com writes:
>> > Don't get me wrong, I am all in favour for a modern stack,
>> > including
>> > Python 3.
>> >
>> > Howe
from a source package called python-numpy. In
my understanding the proposed change is to keep having the exact same
binary packages, just built from two different source packages
(python-numpy and python-numpy-legacy or whatever).
--
Arto Jantunen
Hi,
I'd like to join both the applications and modules teams, and have a
couple of existing packages I'd like to switch over to group
maintenance.
I have read and accept the team policy.
--
Arto Jantunen
signature.asc
Description: PGP signature
Barry Warsaw writes:
> On Feb 14, 2017, at 06:30 PM, Arto Jantunen wrote:
>>The patch-queue branch is based on the Debian branch, not upstream. Try
>>merging the new upstream version to your Debian branch, and then running
>>gbp pq rebase.
>
> This confuses me, or I
rt
> git rebase -i upstream
> (way way more commits to pick from than expected)
The patch-queue branch is based on the Debian branch, not upstream. Try
merging the new upstream version to your Debian branch, and then running
gbp pq rebase.
--
Arto Jantunen
h the gbp pq patches queue branch.
>
> I've never used it.
>
> Does that then result in one big undifferentiated mass of diff in the source
> package?
No, it results in separate patches with their headers intact in the
source package. I assume git-dpm (which I've never used) produces the
same end result.
The git repository is of course different, with gbp pq carrying the
patches as patches in the packaging branch, and git-dpm having separate
magical patch branches.
--
Arto Jantunen
Package: wnpp
Severity: wishlist
* Package name: python-inflect
Version : 0.2.5
Upstream Author : Paul Dyson
* URL : http://pypi.python.org/pypi/inflect
* License : AGPLv3
Programming Lang: Python
Description : Python library for correctly generating pl
this particular computer.
I've seen that as well. I assumed that it was caused by going from
wheezy + backports to jessie, the upgrade of dh-python there was broken
for some time.
--
Arto Jantunen
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "
ituation be OK ?
You could also finally solve this problem and start a "Debian Python Git
Packaging Team" (please invent and use a better name, however).
--
Arto Jantunen
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
reason).
If it really is impossible for the program to update it's configuration,
it should probably on startup show the user an error message containing
instructions on what to do.
--
Arto Jantunen
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of &
;
> What's the fourth one?
The original dh_python, I'd presume.
How about concentrating on getting rid of dh_python and python-central
for wheezy? My understanding is that consensus about those two being
deprecated and needing to be removed should be achievable without too
much flaming.
fine in
vim), but the VCS a person/team uses concerns a lot of people in a lot
of ways. Most VCS client tools can't deal with the repo formats used by
the other tools (and even in those cases where they can there are always
limitations). Nobody wants to waste time learning the quirks of every
sing the transition up in Debian by
making it default way too late.
It is sad that he has no intention of considering any opinions except
his own which is clouded by the fear of making the same mistake twice.
--
Arto Jantunen
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with
.
--
Arto Jantunen
19 matches
Mail list logo
