On Tue, Oct 06, 2015 at 04:03:54PM +0200, Thomas Goirand wrote:
> On 10/06/2015 01:02 PM, Mattia Rizzolo wrote:
> > On Tue, Oct 06, 2015 at 08:39:48AM +, Brian May wrote:
> >> On Tue, 6 Oct 2015 at 18:46 Thomas Goirand <z...@debian.org> wrote:
> >>
> >
ebian.org arch.debian.org anonscm.debian.org
HostName alioth.debian.org
User mapreri-guest
so you avoid fiddling with every git remote.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapr
n before
> > having them committed to our git.
> >
>
> Sounds like an interesting thing to discuss/test after we move to git...
Moreover, jenkins.debian.org is happening right about now, guess it
would help quite something (and I'd be happy to host such tests there).
--
regards,
ve you might not be aware of.
Isn't this the whole point of unstable→testing?
Ok, the debian testing migration might do really few checks compared to
ubuntu's, but still it's the same thing, and I believe RT would like to
add more checks (at lest dep-8 tests) someday.
--
regards,
On Mon, Oct 05, 2015 at 05:26:38PM -0400, Barry Warsaw wrote:
> On Oct 05, 2015, at 09:16 PM, Mattia Rizzolo wrote:
>
> >Isn't this the whole point of unstable→testing?
>
> I guess, although it seems a lot of people run unstable so breakages affect
> more people. I run u
On Mon, Dec 14, 2015 at 02:41:09PM +0100, Piotr Ożarowski wrote:
> [Mattia Rizzolo, 2015-12-14]
> > Given that looks like nobody is interested in it, shall I do a QA upload
> > of the package kicking it out of the team?
>
> yes please (and thanks)
OK, uploade
ask for RM: RoQA for a couple
of packages without feeling too guilty...
PS: let me guess, should this bug be reassigned to ftp-master for RM?
since you already stated -release is not the right place for this, and a
transition tracker is not really needed in this case.
--
regards,
ore uploading.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: ht
, but didn't upload, so I'm just holding off a dput.
Please tell me what I should do with this :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org
On Mon, Dec 14, 2015 at 08:30:09PM +0100, Luca Falavigna wrote:
> 2015-12-14 19:17 GMT+01:00 Mattia Rizzolo <mat...@debian.org>:
> > Turned out Luca already did the pysupport→dh-python migration back the
> > time we were on svn, but didn't upload, so I'm just holding off a
don't need to feel bound to a package. Anyway, this
lead to a package rejection back this summer for some package of the X
team, where there are a lot of packages with this "issue" (even if
actively maintained).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF
Uploaders was removed in the
> first place?!)
dunno, I just noticed it while doing my shift for removing pysupport.
If you guys tell me so I'm happy to send an O bug, move the repo to
collab-maint and doing a QA upload orphanizing it.
--
regards,
Mattia Rizzolo
GPG
on keybase)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.
it, and the md5sum
> coincided
>
> thanks! I learned something today :)
cool, uploaded.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad
.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https
control: tag -1 moreinfo
On Wed, Jan 20, 2016 at 07:00:01PM +, Mattia Rizzolo wrote:
> Package: ftp.debian.org
> X-Debbugs-Cc: debian-python@lists.debian.org
>
> The maintainer (jenner) seems MIA (even if not declered officially by
> the mia team), nobody in the DPMT stepped
the parties involved :D
(especially to the maintainers who switched promptly and didn't wait
for the last time, and to the maintainers who actually maintain their
packages avoiding more work from QA guys who had to NMU them :P)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A
e any packages that require nose2, which I find somewhat
> confusing. So probably will upload anyway.
Hopefully I cleared some.
FYI, I don't know of a nice way to build a dependency graph, like
sometimes I see somewhere, with graphiz
--
regards,
Mattia Rizzolo
GPG Ke
ntained in the python teams somebody could have gone through them and
fixing them in little time).
But be assured, if you don't do that yourself somebody else will do them
in one of the several efforts/projects that involves rebuilding
packages and checking they don't FTBFS :)
--
regards,
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/develop
such a mail
already next week, much less in some months.
> Btw, the docs on the wiki documents how to be added/contribue, but not
> really how to stop ;-)
A person usually just remove himself from the Uploaders field, from my
experience.
--
regards,
Mattia Rizzolo
.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https
nk it would make sense to
include in the binaries, as it provides quick documentation (I think)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad u
On Fri, Aug 19, 2016 at 10:47:37PM +0200, Elena ``of Valhalla'' wrote:
> On 2016-08-18 at 22:27:42 +0000, Mattia Rizzolo wrote:
> > * Files-Excluded in d/copyright doesn't list all the files that are
> > removed (at least according to `git diff --stat
> > upstream/
uld be a plain waste of time.
I'm curious: what triggered this email of yours?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad u
; packages, though. I'd not encourage people to do so but also not
> forbid it,
Thanks for having some trust in your fellow package maintainers...
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http
accept the email, and discard it.
Mattia,
whom suffers from this for the debian-science-maintainers ML.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :'
list, which appears
to be jwilk. I find that particularly interesting, given that afaik he
left the team some time ago.
I don't know whether anybody else knows the administration password
other than him.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B
ou sure
that's not under a different copyright/license? (if so upstream might
be at fault here, and this package might not be redistributable)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''
under another license
* I: python-patch: new-package-should-not-package-python2-module python-patch
+ right, I was about to forget about this...
* I: python-patch source: binary-control-field-duplicates-source field
"section" in package python-patch
--
regards,
Hey Paolo, any news of this package?
(explicitly CCing you to be extra sure it'll reach you)
(And this is why I prefer RFS bugs, btw, saving me from digging in my
mail archive to find this one…)
On Thu, Dec 29, 2016 at 06:17:40PM +0100, Mattia Rizzolo wrote:
> On Tue, Nov 29, 2016 at 08
her python-sphnix nor python3-sphinx ship anything in /usr/bin, so
bad example.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user
or now).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page:
who would consider moving the file back to
python3-cpuinfo a step backward…
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: ht
remove the old repository from collab-mainnt
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri
ot any response yet.
JFTR python-modules-commits-owner@ currently goes to
stratus at users.alioth.debian.org, piotr at users.alioth.debian.org,
bzed at users.alioth.debian.org, kitterman at users.alioth.debian.org,
barry at users.alioth.debian.org
--
regards,
Mattia Rizzolo
ral, it pushes branches
> available on both sides and tags.
I have recently discovered the config push.followTags=true, which pushes
all tags which reference objects that are being pushed.
That should save the '--tags' flag :)
--
regards,
lways quit patches. Sure
if somebody uses pq and somebody else doesn't it would end up with some
diff noise due to the import/export, but imho nothing worth concerning
about.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540
ted lines after).
I think you should try and see whether pybuild's autodetection works
fine, as it usually does.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://ma
member to sponsor it.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: h
YES, please.
On Fri, Feb 23, 2018 at 10:46 PM Stefano Rivera wrote:
> Hi Scott (2018.02.23_12:09:20_+0200)
> > Yes. I was planning on running the old scripts again. I'll do that
> > today.
>
> OK, I think I've got something that's ready.
>
> I think I'll just push them
r one to me.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debia
lintian suggests.
>
> Lintian should not tell us to remove fields that then cause warnings in build
> tools. Or those tools should be fixed.
CCing the dh-python maintainers, as it's dh_python{2,3} that deals with
those fields...
--
regards,
Mattia Rizzolo
GPG K
eral people in
a later moment…
For sure it's not just "fix your bugs" but more like "fix your bugs AND
all your rdeps", in fact you'd expect the maintainer of the package
breaking everything to be a tad more proactive, but in many cases like
this, it's not.
--
regards
n3-astropy from unstable as the broken
version from testing would not be installable using the numpy from
unstable.
> So, how to handle this?
No action needed once both astropy and numpy are "fixed". :)
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52
s should not hinder
> numpy to migrate.
I don't understand this, I don't see any python2-related issue right
now. Could you please expand?
--
regards,
Mattia Rizzolo
GPG Key: 4096R/B9444540 http://goo.gl/I8TMB
more about me: http://mapreri.org
Launchpad User: https://launchpad.net/~mapr
s that regularly (Except these last few weeks
when it was on vaction). I think he said complete automation would miss
too many things that he is filtering out by hand for now.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about
uild to be
retried.
However there is after that a different RC bug (that I can fix once the
build is confirmed to be fixed as well).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more abo
3
* drop the py2 package
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA pa
'll upload web.py without Python 2 support then.
> If someone has strong interest in rebuildd, they has to make a
> Python 3 version anyway. If the package is not in buster, there
> can still be a backport.
>
> Thanks for your input, Julien, Julien, and Mattia!
--
regards,
Mattia
em to migrate their codebases.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian Q
Go for it!
(I just hope that you check for any conflicting d/tests/control before
moving that file over)
On Mon, 7 Jan 2019, 9:42 p.m. Ondrej Novy Hi,
>
> because of:
>
>- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908272
>-
>
>
nbts binary, without doing any kind of
strange migration, and keep the name python3-debianbts for the
python3 package, as the Debian Python Policy states.
As Andrey wrote, don't touch the source package name either.
Sorry if I spread confusion accidentally…
--
regards,
on-debianbts the new default package
> name for Python3?
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.
--
regards,
Mattia Rizzolo
GPG
from testing without the maintainer saying
anything, open an RM bug for the rdep.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad
Considering that this is bzr we are talking about, a package that is
already entering the graveyard, I think it would be easiest to just disable
the test suite and move on.
But I would be happier it Thomas at least checked the rdeps before dropping
packages, at least evaluating if breaking things
Hi,
On Mon, 16 Sep 2019, 1:59 am Louis-Philippe Véronneau,
wrote:
> What is the process to update the DPMT and PAPT policies? I feel the
> DPMT policy is pretty good and I feel the PAPT policy could copy a bunch
> of stuff from there.
>
I wonder, I think the historical reasons for papt and
oaded!
Just, please do not push debian/ tags unless you are completely sure
that's what is going to be uploaded.
In this case I would have liked to run wrap-and-sort, and add a R³
header, but hold back just for that.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA1
ed any upload since ~11:20 AM UTC today.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~m
On Mon, Jul 22, 2019 at 12:53:23PM +0200, Andreas Tille wrote:
> I wonder whether this is safe for backports and backports-sloppy.
Yes, stretch-backports already supported it, so clearly buster-bpo and
stretch-bpo-sl support it.
--
regards,
Mattia Rizzolo
GPG Key: 6
151542154628352=2
uh. meh.
I haven't looked at the code, but if you made the effort, how improbable
would it be for you to just keep the patches for py3 support yourself in
the packaging for the time being?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52
On Mon, 2 Dec 2019, 10:25 pm Paul Gevers, wrote:
> Hi,
>
> On 02-12-2019 22:15, Sandro Tosi wrote:
> > the blocks are only between py2removal packages, so if a package
> > un-related to the py2removal effort
> > depend/recomments/b-deps/autotest-triggers a py2removal *application*,
> that
> > is
Debian, if noone disagrees I will likely convert this bug to a
> removal request in the not too distant future.
Sure, let's do this already!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://ma
ils dropped its python2.
calibre from unstble is not migrating because of missing builds in arm64
and mipsel.
I reckon the way forward is to fix those two FTBFS in calibre.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`
s also removing calibre. At the same time,
bothering the release team for such minor matters feels somewhat
exaggerated.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: http
binary package makes sense for almost all
cases I can think of packages shipping executables under /usr/bin/.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org :
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?log
frowingly* accept, is force-pushing a tag
because you are doing it again. Having said that, I usually just append
a number if I need to re-repack again an upstream tarball (+dfsg1,
+dfsg2, etc). But you mentioned only pristine-tar, so I suppose that's
not your case.
--
regards,
On Tue, 31 Dec 2019, 7:42 pm Daniele Tricoli, wrote:
> Hello Fabrice,
> thanks for pinging I did not notice the MR :(
> Please next time can you assign it to me? I should reveive some sort of
> notification I hope! :)
>
I recommend you enable notifications for all packages in you are interested
There was a temporary bug in piuparts (after a migration from py2 to py3).
The bug has been fixed yesterday, and failed tests will be retried
automatically after a time.
There are probably hundreds of failed tests like that.
On Mon, 30 Dec 2019, 4:15 am Chow Loong Jin, wrote:
> On Mon, Dec 30,
> updating all its rdeps and not run unittests for the python2 binary
> > > (so dropping pytest and the other b-d* only used for tests).
> >
> > Go for it.
>
> +1 from me too.
Yeah, +1!
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F5
ot always!), if it's a small packages it is processed quite
quickly, but poking the ftp team before not even a month has passed
without a good reason (for example, it's blocking an RC bug fix) is just
inappropriate.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18
it makes sense to converge on a single
solution for the whole team, and honestly I don't have much of a strong
preference towards either one.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More abo
the freeze policy.
> Is this something the Debian Python Team could take over?
I'll keep a tab open to review and sponsor the nmu (but anybody feel
free to beat me).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3
think there is any gain whatsoever in rolling back to 0.11.0 at
this point.
Lastly, I'll ask the salsa admins to remove the repository you created
in the /debian/ space.
If you are interested in this package I recommend you join the DPT then
:)
--
regards,
Mattia Rizzolo
er autopkgtest breaks before said breaking upload.
https://release.debian.org/britney/pseudo-excuses-experimental.html
That ought to prevent plenty of headaches we would otheriwse have.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540
to do?
I suppose in this case it's easier to just wait for gevent's maintainer
to fix it.
I don't think you need to worry of this not happening in time for the
bookworm release.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .
that:
https://tracker.debian.org/pkg/python-debian
The first one (python-team) is probably the one you are looking for.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: http
78 matches
Mail list logo