*ping* *ping*
On Tue, 16 Apr 2024 11:21:51 +0200
Jeroen Ploemen wrote:
> *ping*
>
>
> On Tue, 19 Mar 2024 13:41:04 +0100
> Jeroen Ploemen wrote:
>
> > Dear team admins,
> >
> > please delete the following packages from the DPT namespace on
> >
*ping*
On Tue, 19 Mar 2024 13:41:04 +0100
Jeroen Ploemen wrote:
> Dear team admins,
>
> please delete the following packages from the DPT namespace on
> salsa:
>
> cheetah
> jaraco.classes
> jaraco.collections
> jaraco.context
> jaraco.text
> nfoview
>
On Wed, 27 Mar 2024 00:33:15 +0100
Thomas Goirand wrote:
> On 3/19/24 13:41, Jeroen Ploemen wrote:
> > Dear team admins,
> >
> > please delete the following packages from the DPT namespace on
> > salsa:
> >
> > cheetah
> > jaraco.clas
Dear team admins,
please delete the following packages from the DPT namespace on salsa:
cheetah
jaraco.classes
jaraco.collections
jaraco.context
jaraco.text
nfoview
ply
puremagic
python-autocommand
python-jaraco.functools
python-portend
python-rarfile
python-tempora
python-yenc
sabctools
On Fri, 1 Mar 2024 07:21:57 +
Julian Gilbey wrote:
> These are really interesting points. Under the proposed system, I
> presume that one could leave "privately maintained" packages within
> the python-team area of salsa and still benefit from these automatic
> changes without giving
On Tue, 27 Feb 2024 18:32:54 +
Scott Kitterman wrote:
> While I do take advantage of this for a few packages, I don't
> personally care much either way. I suspect that packages will be
> removed from team maintenance as a result though and I think that's
> a bad idea.
>
> I'd prefer the
hi Ileana,
I took a look at the python-leather package up for sponsorship in the
Python team. Some issues came up during review:
* possible unused build-deps on python3-six, -doc, dpkg-dev;
* build-dep on furo could be marked !nodoc;
* build-dep on sphinx-common is redundant, already a
hi Lance,
I took a look at the python-ciso8601 package, put up for sponsorship
in the Python team. Just missed you on IRC, so sending comments by
email instead:
* copyright:
+ incorrect info for upstream (license file in sources states 2014,
does not mention a "tomst");
+ missing info
hi Bo,
I took a look at the riscemu package, put up for sponsorship in the
Python team. Some (mostly minor) issues came up:
* copyright:
+ upstream years are incorrect (license file, sources have 2021-2022
resp. 2023).
+ leftover boilerplate comments.
+ empty line (dot) at the start of
hi Ileana,
I took a look at the astral package put up for sponsorship in the
Python team. Some minor issues came up:
* unused build-deps on requests, tz;
* outdated copyright years for upstream, see src/astral/__init__.py;
* entire paragraph for apache-2.0 license is only a filepath.
Also
Hi,
I took a look at lazy-loader, up for sponsorship in the Python Team:
* copyright: years outdated;
* control: long description would benefit from some more details
explaining what lazy loader is and does, e.g. a summary of [1];
* control: standards-version is slightly out-of-date;
* watch:
hi Matthias,
the package looks mostly fine on the technical side, with only some
minor issues and suggestions for improvement of d/control and d/rules.
The copyright file does need attention though, also in light of
recent upstream commits that made significant changes. A fresh
upstream release
On Wed, 18 Jan 2023 14:45:41 -1000
Chiara Marmo wrote:
> Dear list,
>
> A new upstream version of sphinxext-opengraph is available on salsa.
Uploaded, thanks.
pgpNhgurjV0RY.pgp
Description: OpenPGP digital signature
On Thu, 5 Jan 2023 01:17:40 -0800
Vincent Cheng wrote:
> to the packaging, but otherwise I think this is ready for upload;
> if Jeroen isn't planning on uploading kivy in the next day or so,
My system has been resurrected, and I'm fine with the current state of
the kivy packaging as well. I do
hi Dean,
thanks for making all those improvements. Only a couple of things
remaining:
* Copyright: try using standard license shortnames [1] where
possible: Easing appears identical to BSD-3-clause; Khronos looks
a lot like Expat.
* Rules, lintian: are the files in
hi Ileana,
I took a look at pytest-fail-slow, up for sponsorship in the Python
team.
Some repo issues:
* It appears tags were not pushed, as there's no tags at all in the
repo - not even for the imported upstream release - although the
typical gbp workflow would handle that.
* The upstream
hi Bo,
my comments for the pygubu package up for sponsorship in the Python
team:
* changelog: only a single entry is needed for an initial debian
release.
* copyright:
+ please remove the copyright statement at the start of the MIT
license paragraph so that it contains only the license
hi Dean,
I reviewed the kivy package up for sponsorship in the Python team:
* There's quite a few lintian hits [1], and most of those look legit.
Please fix the correctly identified issues, and add overrides for
any false positives.
* In the changelog, you should mention this is a team
On Thu, 8 Dec 2022 17:14:31 +0530
Nilesh Patra wrote:
> > > SystemError: initialization of CorePyWrap raised unreported
> > > exception autopkgtest [17:14:04]: test autodep8-python3
> Similar report is also filed for tagpy (Bug#1025201) -- could
> someone please help in fixing these?
Looks
hi Ileana,
took a look a the weresync package you put up for sponsopship in the
Python team:
* weird, probably unnecessary d/source/include-binaries that lists
the upstream signing key;
* autopkgtest:
+ runs in extracted source dir, might not test installed package;
+ only tests with the
hi Claudius,
took a look at the pystray package up for sponsorship in the Python
team. Overall it's in really good shape, still a few comments left
though:
* control: the long description is really short and mentions neither
supported environment nor any other pystray features.
* tests:
+
On Fri, 4 Nov 2022 16:07:56 +0100
François Mazen wrote:
Thank you for making all those improvements.
> > * copyright:
> > + public domain without explanation detailing exactly what
> > exemption the files in question have from default copyright
> > restrictions.
>
> I don't know what do you
On Tue, 1 Nov 2022 12:33:59 -1000
Chiara Marmo wrote:
> Dear list,
> I have committed to salsa the new version of sphinxext-opengraph
> [1]. If someone could have a look, that would be great.
> Thanks!
Looks like there's a newer upstream release, fixing bugs in 0.7.0?
pgp8WgYblHIhF.pgp
hi Francois,
I took a look at the gtg package put up for sponsorship in the Python
team:
* changelog:
+ multiple entries for revisions that did enter the archive (0.3.1-2
through 4) appear to have gone missing?
+ there's about a dozen open bugs against the old package, yet only
a single
On Fri, 28 Oct 2022 16:46:51 +0300
Ileana Dumitrescu wrote:
> > I did just notice the upstream release contains several other
> > files worth considering for removal: a bunch of windows
> > executables [1].
>
> I agree and can remove those from the source tarball too. To do that
> with the
On Wed, 26 Oct 2022 17:29:59 +0300
Ileana Dumitrescu wrote:
> Thank you for the feedback! I made changes as you suggested. There
> is a new upstream version that I also included in the new package.
Great! The copyright stuff is a chore on packages like this, so
thanks alot for seeing that
hi Ileana,
I took a look at the package update you prepared and put up for
sponsorship in the Python team:
* leftover boilerplate comments and examples remain throughout the
packaging (control, rules, watch), please remove when unused.
* changelog: isn't #941447 also fixed by the new release?
On Mon, 3 Oct 2022 11:56:30 -0400
Ben Westover wrote:
> Thanks, I didn't catch that since I use sbuild instead of pbuilder.
> I have set the environment variable CI = true which should disable
> those tests.
Unfortunately, it doesn't.
The change suggested below does make 'CI=true' take effect,
Hi Ben,
* control: missing build-dep on python3-all? Needed to run the
testsuite against all supported Python version rather than just the
default one.
* watch: regex "(\d\.\d.\d)" is overly specific, could easily miss
upstream versions such as a hypothetical "1.5" or "1.4.10".
Package
On Thu, 22 Sep 2022 12:35:12 -0400
Antoine Beaupré wrote:
> I think the simplest solution is not to rewrite the launcher, but to
> rename it. So in debian/rules, you would simply do:
>
> override_dh_auto_install:
> dh_auto_install
> mv
On Sat, 3 Sep 2022 15:33:04 -1000
Chiara Marmo wrote:
> I have opened merge requests on salsa for numpydoc [1] in order to
> update to the last available upstream version 1.4.0
Any reason why you're no longer closing #1013376 when building your
updated package against experimental seems to work
On Fri, 11 Mar 2022 12:42:48 -1000
Chiara Marmo wrote:
> Dear list,
>
> a new version of sphinxext-opengraph (0.6.2) is available for
> upload on salsa.
Uploaded, thanks!
pgph9YZjSJH6I.pgp
Description: OpenPGP digital signature
On Thu, 24 Feb 2022 14:35:05 -1000
Chiara Marmo wrote:
> Dear list,
>
> a new version (0.6.1) of sphinxext-opengraph is ready for upload on
> salsa [1].
Uploaded, thanks!
pgpFolYaSjWEi.pgp
Description: OpenPGP digital signature
On Sun, 2 Jan 2022 15:26:30 -1000
Chiara Marmo wrote:
> Ready for upload?
Uploaded with some minor changes. Thanks for your contribution.
pgpSQMyHTArPC.pgp
Description: OpenPGP digital signature
On Fri, 31 Dec 2021 17:25:34 -1000
Chiara Marmo wrote:
> I think the configuration is better now, as the CI passed too.
Using @builddeps@ may seem attractive at first, but is best reserved
for autopkgtests that actually do a full build. In most other cases
redundant extra stuff gets installed
On Thu, 30 Dec 2021 14:27:09 -1000
Chiara Marmo wrote:
> Dear list, Sandro,
>
> I have uploaded on salsa a new upstream version of
> sphinxext-opengraph:
> https://salsa.debian.org/python-team/packages/sphinxext-opengraph/
>
> I have also modified the way how tests are run... but I'm still in
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: debian-python@lists.debian.org
Dear mentors,
Note that this update has been approved by the stable release managers,
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984604
I am looking for a sponsor for my package "sabnzbdplus":
37 matches
Mail list logo
