it would be great, if RadioTray will get back into the official
Debian repository.
I have already written a mail to the old Debian maintainer Elías
Alejandro Año Mendoza, but did not get an answer.
Is here someone, who is willing to sponsor RadioTray?
Regards,
Matthias
no longer part of Debian.
Regards Matthias
Am 05.01.22 um 05:15 schrieb Paul Wise:
> On Tue, 2021-12-28 at 18:37 +0100, Matthias wrote:
>
>> but it would be great, if RadioTray will get back into the official
>> Debian repository.
>
> Please note the extra steps required when
) not being binary
> compatible, but this is a rare case, and the Stackless people are
> interested in resolving the bug if it can be reproduced.
long time ago, stackless was distributed as a patch to python. is this
still the case?
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
bapache2-python), vim, and maybe other packages.
> 4.1.1. rtupdate script invocation
>
> 1. in the pre-installation phase of the python package, the package
>supplied scripts are called with the parameter: pre-rtupdate runtime>
>
> A failure in any script results in the failure of the
>pre-installation script of the python package.
>
>[42]Note Whether or not all scripts are run, or the process aborts
> at the first failure, is still under flux
>
>Since such a failure of a script would leave all packages whose
>pre-rtupdate has been run in a dangling state, a bug in a pre-rtupdate
>will always be a critical bug. Be very very careful when working on a
>pre-rtupdate script.
I'm adding a "failed-pre-rtupdate" hook for the next upload, which is
run, if the pre-rtupdate hook fails (to allow the package to go to a
sane state again).
I do have a different view on raising build and support information to
the Packages/Sources files; in other cases the document clarifies
things well. IMO the current section 3.6 makes things more confusing
than they are (at least for me). Would it be helpful to add
paragraphs starting with "Example:" in sections where they are useful?
I.e. most package maintainers won't need the rtupdate scripts, and
therefore could skip reading when they don't need these scripts.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ou know that the package can be
binNMU'ed (i.e. no too strict dependencies between arch/indep
packages), please send a mail to -release. We should file binNMU
requests for other packages as well.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe&quo
ython ./
If more packages are needed for testing the removal of python2.3,
I'll add these to this archive.
- rebuild extension packages to drop 2.3 extensions.
2 and 3 can be done now and would be a prerequisite for the python2.3
removal.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL
tiple python versions is not meant at
all as an excuse for lazy debian maintainers depending on python for
not following upstream python development.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
eam versions where necessary. Once done,
propose the versions in this repository to the release team, but I
doubt it will be allowed into etch.
Mixed feeling yes, but IMO unavoidable with our release schedule for
etch.
Matthias
Loïc Minier writes:
> On Tue, Jan 02, 2007, Pierre Habouzit wrote:
> > or do that "the clean way": edit /usr/share/python/debian_defaults
>
> This is slightly better indeed. My personal taste wouldn't allow me to
> edit a file under /usr, but I suppose a diversion would achieve a
> similar j
built for Ubuntu feisty to support the debug interpreter
build. A short build description and a list of packages can be found
at [1]. I will file wishlist bug reports to package these for Debian
as well.
Matthias
[1] https://wiki.ubuntu.com/PyDbgBuilds
--
To UNSUBSCRIBE, email to [EMAIL PROT
Ondrej Certik writes:
> On Dec 5, 2007 8:10 PM, Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
> > On 05/12/07 at 13:37 +0100, Bernd Zeimetz wrote:
> > > >> 1. Why is there the build-conflict in the first place? This is the
> > > >> question to original
Sanghyeon Seo writes:
> 2007/12/17, Tshepang Lekhonkhobe <[EMAIL PROTECTED]>:
> > > > Hi,
> > > > I was surprised to find python2.{4,5}-doc in contrib and wondered why?
> > > it needs latex2html to build.
> > Are there any free near-equivalents?
>
> There are, like hevea and tth, but as Python d
I'll try to address these, but please don't expect those to be done
before Feb 23/24.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Marc 'HE' Brockschmidt writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
> > Yes. If outstanding issues are solved; people want make you believe
> > that NMUs are enough to complete the transition. What needs to be
> > done:
> >
> > - Look for
- add another path (e.g. /usr/local/python/lib2.x/site-packages),
and remove the /usr/local/lib/python2.x/site-packages path after
the next release. Does provide an upgrade path, but doesn't solve
the probem immediately.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
out
packaging of eggs, not Python packaging in general. You can find a
more complete thread on the python-dev ML, and a summary of the BoF
discussion in the python.org wiki.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Raphael Hertzog writes:
> On Tue, 15 Apr 2008, Adeodato Sim
Ondrej Certik writes:
> On Mon, Jul 7, 2008 at 2:12 PM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> > Package: python-numpy
> > Version: 1:1.1.0-2
> > Severity: serious
> >
> > python-numpy now has an unconditional dependency on libatlas3gf-base,
> > n
[EMAIL PROTECTED] writes:
> On Mon, Jul 7, 2008 at 2:12 PM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> > Package: python-numpy
> > Version: 1:1.1.0-2
> > Severity: serious
> >
> > python-numpy now has an unconditional dependency on libatlas3gf-base,
> &
> I'd be interested to know people's experiences with trying it out for
> packaging Python distributions for Debian.
how would it help? a Python distribution is a set of source/binary
packages which we do package separately.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
rthanx.com
I only trust my own comparsion without any date and version numbers.
And honestly I don't care about a checkin of the usual 2-5 files
taking half a second longer. What annoys me most with git is the
steep learning curve and the non-intuitive UI, therefore I do prefer
bzr over hg over
Ondrej Certik schrieb:
> Hi,
>
> I finally packaged the newest uptream and committed all fixes into our
> svn repo for numpy. Kumar (or others), do you think you could please
> test the package?
numpy becomes big. see https://launchpad.net/bugs/309215. In the past the parts
depending on external
extension in a subpackage seems to be worse than
having it as a toplevel module or in its own namespace.
Background in https://bugs.launchpad.net/bugs/309215
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> python-central should implement the same behaviour, IMHO
As I did write above, the support for namespace packages should be implemented
using diversions. It's ok to generate these by a packaging helper.
> Just one more issue: what about "current" issue? Although I prote
Ondrej Certik schrieb:
> Hi Matthias,
>
> thanks for all the work you do. I have one question:
>
>> - 3.0/3.1: I do not plan to upload 3.0 to unstable or experimental,
>> but will prepare 3.1 packages for experimental and upload those
>> to unstable with the f
On 25.07.2009 05:47, Matthew Johnson wrote:
On Sat Jul 25 11:28, Mathieu Malaterre wrote:
On Fri, Jul 24, 2009 at 7:45 PM, Max Bowsher wrote:
...
It would be extremely nice too if all wrap language would adopt the
same convention. So that toolkit such as VTK/ITK/GDCM wrapping their
interface i
use
>different helper tool,
> * Python modules available out of the box (think about daemons),
I appreciate these goals and I'm fine to provide a wrapper for dh_pycentral if
the new dh_python implements these goals.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
t time without zope2.x in unstable is ok, while having three
python2.x versions is too much. But it looks like zope2.12 based on python2.5 or
python2.6 is doable for squeeze.
Matthias
[1]
https://edge.launchpad.net/~schooltool-owners/+archive/ppa/+index?field.series_filter=jaunty&batch=20
was the last package
absolutely needing python2.4.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Fyi, I replaced your NMU with my merge from Ubuntu, which already had these
changes. I may have missed the "indentation problems", please file separate bug
reports for these.
Matthias
On 03.11.2009 16:07, Piotr Ożarowski wrote:
Hi Matthias,
You uploaded new python-central pa
e the best to have a
separate binary package python3-* (which could be built from the same source
package).
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
,
directories without __init__.py file will be skipped),
IOW, you want to skip modules that are not a part of a package? Why?
which files would that be?
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Conta
ntral/dh_python replacement.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 28.01.2010 12:50, Cyril Brulebois wrote:
Scott Kitterman (17/12/2009):
I believe that we are getting close to uploading Python 2.6 to
Unstable and dropping Python 2.4 as a supported Python version. If
we finish preparations in the next week, are there any ongoing
transitions a python2.6/pyt
build for many packages.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ba94202.7020...@debian.org
support it. python3.2 3.2~a2 is not
proposed for squeeze and only available in experimental to demonstrate
the coexistence of different python3 versions.
Scott Kitterman
Piotr Ożarowski
Barry Warsaw
Matthias Klose
[1] http://python.org/dev/peps/pep-3147/
[2] http://python.org/dev/peps
ludes packages from experimental too. I'll file
bug reports next week. The easier solution would be to remove python2.5 from
the list of supported python versions and rebuild.
(Sending email to the maintainers mentioned below)
Matthias
grass 6.4.0~rc6+42329-2
kaa-imlib2 0.2.3
3
Yes, this is still the upstream plan, and there was no use case for a python2
executable.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cc5b419.2010...@debian.org
On 11/28/2011 09:25 PM, Stefano Rivera wrote:
> Of course, it would have to be packaged as a separate Python stack,
> again. Although it would be interesting to allow modules to be built for
> alternate Python implementations, but that's not a trivial project...
maybe for binary packages, but ther
les in 2.x).
Not sure if backporting pep 3147 would be worth it.
> However some packages have different
> installation process for pypy and not pypy build (for example building
> optional C extensions or not).
that should be handled in the packaging.
Matthias
--
To UNSUBSCRIBE,
n/pkgreport.cgi?tag=python2.6-removal;users=debian-python@lists.debian.org,
the only blocker is packaging of zope2.13. feedback from the zope2 packagers is
outstanding.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
t next week, re-adding myself as an uploader,
apparently silently removed.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f6333db.6080...@debian.org
On 16.03.2012 14:29, Jakub Wilk wrote:
* Matthias Klose , 2012-03-16, 13:36:
re-adding myself as an uploader, apparently silently removed.
Well, from my IRC log (2011-08-27):
22:43 < jwilk> morph_: Out of interest, did you ask the former Numpy
co-maintainers if they are ok with removin
Package: wnpp
Severity: wishlist
Owner: "Matthias Kümmerer"
* Package name: alembic
Version : 0.3.1
Upstream Author : Mike Bayer
* URL : https://bitbucket.org/zzzeek/alembic
* License : MIT
Programming Lang: Python
Description : lightweigh
ng updates. The list of packages
and maintainers is attached below. I'll file bug reports later (user:
d...@debian.org, tag: pillow).
Please report any other issues to the python-imaging packages.
Matthias
A Mennucc1
freevo (U)
Agustin Henze
nikola
Alberto Garcia
ocrfeeder (U
es do provide the pillow names). I'll stick to the original names
for now.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51195f44.1080...@debian.org
ging:
> http://wiki.debian.org/Games/VCS
Now you did point out one discrepancy, which hinders newcomers, and you do want
to introduce another one?
Matthias
[1]
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pycentral-deprecation;users=debian-python@lists.debian.org
[2] https://lists.debian.
mfortable with how a git-based team repository would
>> work, I suspect you'll find more consensus to switch.
>
> +1
can we limit the packages in this ppa to those using dh_python[23] and those
supporting python3?
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/512416b2.5030...@debian.org
more complex than this).
So there would be no way anymore to build using upstream tarballs? This doesn't
sound appropriate to force on a whole team.
I don't think that many of the people that voted are aware of your implicit
changes (no release tarballs, including upstream source in th
a
> proper layout? I've investigated some other python3 packages, they all
> put everything in /usr/lib/python3/.
This is correct.
> However, this seems to contradict the FHS? What is the way to go here?
No, the FHS doesn't make any statement about code in /usr/share.
Mat
ld failures are uploaded to the archive. So do you
volunteer doing that?
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5187ef78.4020...@debian.org
ages as well, as long as some essential packages like
coreutils and perl are rebuilt against the new libc6.
Afaicr, adding trigger support in some helpers did introduce its own set of
upgrade issues, but this might be safe, if no helpers use triggers to generate
and update symlink farms.
I don'
Am 11.06.2013 08:18, schrieb Arnaud Fontaine:
> Hello,
>
> No reply so I guess it should be ok. Therefore, I will request the
> removal of python from experimental.
please wait until the upload in NEW reaches unstable, and then it will be
removed automatically.
--
To UNSUBSCRIBE, email
On 06/29/13 16:53, Thomas Kluyver wrote:
> On 22 May 2013 16:28, Barry Warsaw wrote:
>
>> I think we should consider switching back to setuptools once 0.7 is
>> released
>> (defined as "available on PyPI), since this will clearly be the future of
>> this
>> component. We may have some fallout to
n it doesn't match the module name, so that it can be found by apt-cache -n
search. But again, no need for a policy here.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51dd84a6.8020...@debian.org
it, but also points to the hint
given by the command-not-found handler which package to install if the command
cannot be found.
Also the platform package manager should be the preferred way to install
packages, not pip, so even a Recommends is a bit strange.
Matthias
--
To UNSUBSCRIBE, emai
tion is
built up on the Debian side, and I currently cannot see why exactly. pip
installs (when using the system python) should go to /usr/local, if not then pip
should be patched. Maybe give a warning, or require an extra option to run as
--yes-run-as-root, or maybe give a hint installing the deb package.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/523a32fa.7000...@debian.org
oth.debian.org
>
> The only reason they are maintained within the OpenStack team is because
> I don't want to be forced to use SVN, and I think it's safer than in
> collab-maint where so many people have commit access (which means they
> can rm -rf...).
apparently these
supported python version.
Plus dh-python should be updated before 3.4 becomes a supported version.
The 3.4 release is planned for March 16, so it shouldn't be too much of a
surprise to make 3.4 the default for the next Debian release, and hopefully be
able to drop 3.3.
Matthias
-
Am 27.01.2014 00:14, schrieb Nicolas Dandrimont:
> - Adding Python 3 support when upstream has it
I think this should make it into the python policy.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
Am 26.01.2014 19:59, schrieb Matthias Klose:
> Python 3.4 beta2 is in testing, the python3-setuptools package is able to
> handle
> 3.4 builds. I am planning to go on with 3.4 as a supported Python 3 version
> some time in February (targeting not later than Feb 9, release date of
nments created by venv or virtualenv. Some
package builds use virtual environments, but the population of these
has to be satisfied by package build dependencies anyway.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
Hi everyone,
i prepared an update to the package python-pisa [1] and would like to
join the DPMT to commit the changes to the subversion. At the moment i
use a temporary git repository at alioth[2]. My alioth account name is
matthias-guest.
best wishes,
Matthias
[1] http
ug filing
> asking to convert to dh_python{2,3}?
that would be good. However before we start this, I'd like to make sure that we
get rid of /usr/share/pyshared as well. With PEP 404 [1] reconfirmed this year
at PyCon we can safely remove the symlink farm.
Matthias
http://legacy
e needed to make the pyvenv command work. so we have to
construct these out of the debian supplied packages, and best in a form that
these cannot be broken by updates in the venv, i.e. re-vendorized.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/536a0912.4020...@debian.org
Am 07.05.2014 12:17, schrieb Piotr Ożarowski:
> dh_python2 ignores python3-* packages, dh_python3 ignores python-*
> packages, but in all other packages both of them will try to handle .py
> files. To avoid possible unnecessary dependencies or shebang rewrites,
> debhelper's -N (--no-package) or -p
er as a surprise.
Matthias
=== modified file 'debian/python-policy.sgml'
--- debian/python-policy.sgml 2013-05-22 02:12:02 +
+++ debian/python-policy.sgml 2014-05-07 14:34:24 +
@@ -32,7 +32,7 @@
Scott Kitterman
sc...@kitterman.com
-
Am 07.05.2014 17:27, schrieb Barry Warsaw:
>> +
>> +
>> +
>> + Applications should use Python3, and should not be
>> + packaged for Python2 as well.
>> +
>
> Maybe also that system scripts written in Python should be Python 3 and not
> Python 2. I'd add
Am 07.05.2014 23:01, schrieb Steve Langasek:
> On Wed, May 07, 2014 at 10:15:37PM +0200, Matthias Klose wrote:
>> Am 07.05.2014 17:27, schrieb Barry Warsaw:
>>>> + ++ + Applications
>>>> should use
>>>> Python3, and should
Am 07.05.2014 16:45, schrieb Matthias Klose:
> Attached is a proposed change to the Debian Python policy to focus on Python3
> within the distribution. The intent is to document and start a large journey
> towards one Python stack in Debian. This is unlikely to happen for jessie+1,
&
an initial list of packages where to start from?
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/537231e0.50...@debian.org
updates yet.
I would like to start pinging maintainers frist, then filing bug reports once
the final python3 version is in testing and a few of these issues are already
resolved in the archive.
Proposing to usertag issues with debian-python@lists.debian.org/pyshared-removal
Matthias
--
sr/share/python/wheels, and/or /usr/share/python3/wheels?
- naming of wheel packages. It's good to see wheels packaged
in a separate binary package. However there is no proposal
how to name these packages.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
ges
could break for some time when these packages are updated to new versions.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/537939dc.2010...@debian.org
Am 16.05.2014 00:32, schrieb Barry Warsaw:
> My thoughts...
>
> On May 16, 2014, at 12:07 AM, Matthias Klose wrote:
>
>> - should we add wheels everywhere? I don't think we should,
>> but I'd like to state this somewhere, like in the python policy.
>
Am 19.05.2014 12:19, schrieb Piotr Ożarowski:
> please at least unpack these wls files so that admins don't have to
> figure out what to do with them if they want to apply a patch from
> upstream
no, you don't gain anything by this. we don't unpack jar files eith
Am 19.05.2014 13:19, schrieb Jakub Wilk:
> * Matthias Klose , 2014-05-19, 12:44:
>> we don't unpack jar files either.
>
> Fortunately, we don't have to mimic all the Java misfeatures.
fine, then please come back after changing the policy to ship unpacked .a files.
Call
aunchpad.net/ubuntu/+source/twisted-py3. If this is
good enough for pika, I'll upload that to unstable as well.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archi
bin/sh
# -*- coding: utf-8 -*-
shell_code=''' '
echo This is Shell
exec python $0
python_code='''
## ONLY use DOUBLE quotes ‹"› after this line
print("This is Python")
# End of Python code. Do not modify this line. #'
This way, "d
't yet ported to 3.0?
> This should be a "smooth transition", as the packages for wxpython 2.8 and
> 3.0 are co-installable.
Maybe I misunderstand something but I wouldn't call this "smooth".
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.deb
Am 23.07.2014 15:07, schrieb Olly Betts:
> On Wed, Jul 23, 2014 at 02:10:19PM +0200, Matthias Klose wrote:
>> Am 23.07.2014 03:38, schrieb Olly Betts:
>>> The intention is to eliminate wxwidgets2.8 (and hence wxpython 2.8) before
>>> releasing jessie - the last upstream
Am 28.07.2014 um 14:00 schrieb Debian FTP Masters:
>
>
> Accepted:
>
> Format: 1.8
> Date: Mon, 30 Jun 2014 10:04:06 +0200
> Source: python-pandocfilters
> Binary: python-pandocfilters python3-pandocfilters
> Architecture: source all
> Version: 1.2.1-1
> Distribution: unstable
> Urgency: low
> M
> (non-PEP 8 compliant) names.
>
Agreed. In fact I'd recommend that bs3's reverse dependencies get converted
to bs4 before the release (and then drop bs3 from the archive) if possible.
--
-- Matthias Urlichs
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
w
Am 07.08.2014 um 23:48 schrieb Raphael Hertzog:
> Hi,
>
> I rebuilt all reverse deps of python-django and I tagged confirmed all the
> associated bugs where the package failed to build with python-django 1.7
> and I sent the relevant extract of the build log...
a lot of django packages are still
Seen this in pycurl (#757694), but if this is something which occurs more often,
then I think we should prepare for a policy update and/or a lintian warning.
Maybe it is not yet possible to avoid one stack entirely, but we should not
create artificial dependencies.
Matthias
--
To
er wait
for the fixes from upstream (and maybe new bugs), then I think it's better to
drop the autopkg tests.
And replying to the bug report without replying to the maintainer is at least
odd.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject
Am 20.08.2014 um 06:52 schrieb Nikolaus Rath:
> If someone cares deeply about this, the necessary patch is at
> https://bitbucket.org/nikratio/s3ql/commits/9a8c0ebbff390555e63b7e203b999b89aabbb86e/raw/.
>
>
> I did not add it to the debian package yet because I considered it a
> minor issue tha
ACKAGENAME" database, and make the mysql credentials overrideable
(via environment or whatever).
Requiring (a) root (b) without a password (c) on localhost (presumably) is
a bad idea on all three counts.
--
-- Matthias Urlichs
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.de
Am 11.09.2014 um 10:30 schrieb Piotr Ożarowski:
> [Andreas Tille, 2014-09-11]
>> pkg_resources.DistributionNotFound: pil>=1.1.7
>
> python{,3}-pil provides Pillow egg-info
> Matthias: should python-imaging provide pil.egg.info file (for older
> libraries/applications l
;&2 ; exit 1; fi
git config commitmail.$BRANCH.last $HEAD
if [ "$LAST" = "$HEAD ] ; then echo "Nothing changed, exiting">&2 ; exit ; fi
git log $LOG_OPTS $LAST..$HEAD | mail -s "Changes on $BRANCH until $(date)"
$DEST
#echo "mailed log of $(git
Hi,
Charles Plessy:
> https://github.com/mhagger/git-multimail/
>
Looking at that code, IMHO it should be sufficient to add the arguments
'--' and 'debian' to all calls of "git revlist".
--
-- Matthias Urlichs
--
To UNSUBSCRIBE, email to debian-py
Am 17.10.2014 um 17:03 schrieb Barry Warsaw:
> Hi Florent,
>
> On Oct 17, 2014, at 04:17 PM, Florent Rougon wrote:
>
>> As the upstream maintainer of pythondialog, I feel a bit concerned about
>> its status in Debian, in particular about what is going to go into
>> jessie. In short, I'd rather se
you happen to use a
different version of tar than the one used to prepare the pristine-tar
entry.
I'd rather record the .orig.tar.?z's exact size and hash(es).
--
-- Matthias Urlichs
signature.asc
Description: Digital signature
Hi,
Daniele Tricoli:
> Due to #753578 I added a stub (technically I just used a symlink) to make
> import requests.packages.urllib3 works.
I'd add a stub _file_ which just contains "from urllib3 import *".
--
-- Matthias Urlichs
signature.asc
Description: Digital signature
On 11/19/2014 12:45 AM, Yannick Roehlly wrote:
Hi,
The building of Python 2 without SSLv3 support breaks requests:
import requests
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 68, in
_attach_namespace(ur
switch to the
Debian/Ubuntu version of debian/*?
--
-- Matthias Urlichs
signature.asc
Description: Digital signature
Hi, I won't have the time to do that, CCing debian-python. You may want to ask
for a sponsor there, or even join the python-modules team.
Matthias
On 02/06/2015 06:23 AM, Riley Baird wrote:
> Hi Matthias,
>
> A couple of years ago, you orphaned the "slides" package. I&#
On 02/11/2015 04:04 PM, Michael Crusoe wrote:
> Hello,
>
> I'm working on the packaging of the khmer project[0] with the debian-med
> team[1] and we've run into an odd problem: dh_python2 renames the Python
> extension shared library from `_khmermodule.so` to a version with a
> mutliarch triplet:
cause of their removal, we'll have
> plenty of time to fix them.
well, they are needed at least in Debian, because some python packaging helper
introduced a separate site directory. Let's remove that helper first.
Matthias
--
To UNSUBSCRIBE, email to debian-python-requ...@
On 04/13/2015 11:07 PM, Donald Stufft wrote:
>
>> On Apr 13, 2015, at 4:17 PM, Stefano Rivera wrote:
>>
>> Matthias and I are planning to have a Debian Python BoF at PyCon,
>> tomorrow afternoon. I think lunch is 2pm, so 3pm?
>>
>> Meet outside the cPyth
1 - 100 of 564 matches
Mail list logo
