Re: numpy 1.2.1, switching to git?
[Piotr Ożarowski, 2008-12-23 13:37] > unfortunately I use Git only outside Debian, so I don't know about > issues git-buildpackage might have. I know it doesn't have > mergeWithUpstream but it's written in Python, so we can implement this. > The problem is (FWIK) that it's better to use Git with upstream sources > (with tools like pristine-tar)... anyway, I vote for Git, but I'm open > to alternative suggestions. update: I vote for status quo (svn, svn-buildpackage, mergeWithUpstream) for now - at least until all top contributors will have decent internet connection or we'll work out some kind of remote upstream branches schema so that one could choose what to download (and a script to download all repositories (packages) within the team) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: numpy 1.2.1, switching to git?
On Fri, Dec 26, 2008 at 12:54 AM, Piotr Ożarowski wrote: > [Piotr Ożarowski, 2008-12-23 13:37] >> unfortunately I use Git only outside Debian, so I don't know about >> issues git-buildpackage might have. I know it doesn't have >> mergeWithUpstream but it's written in Python, so we can implement this. >> The problem is (FWIK) that it's better to use Git with upstream sources >> (with tools like pristine-tar)... anyway, I vote for Git, but I'm open >> to alternative suggestions. > > update: I vote for status quo (svn, svn-buildpackage, mergeWithUpstream) > for now - at least until all top contributors will have decent internet > connection or we'll work out some kind of remote upstream branches > schema so that one could choose what to download (and a script to > download all repositories (packages) within the team) Agree. We talked with Sandro on IRC, the problem is in a bad internet connection --- it takes ~40min to download 10MB -- then of course every MB matters. For me it takes just couple seconds, so it doesn't really matter if I am downloading tarball+debian dir separately, or together in a git repo. I just assumed that everyone has a decent internet connection these days, and I was wrong. :) Ondrej
Re: numpy 1.2.1, switching to git?
On Thu, Dec 25, 2008 at 15:54, Ondrej Certik wrote:
...
Last reply on this thread, just to recap what Ondrej and me discussed
on irc this evening.
I didn't realize I ain't made clear what's my network situation: I'm
still at 56k, so many of the think you broadband users consider
normal, trivial, or chip, for me they're not. I have to minimize the
stuff I download at home and maximize the effort, and svn
(+downloading the tarball at work, if they are big) allows me to
achieve this balance.
But even if I had an adsl or so, I would say that that git is not the
right choice for our team (but I would have made a lot less problems
migrating to it). I think that, being things are they are now, svn is
the right choice and keep being. What we really need is to migrate a
svn layout-2 repository (one composed by
{trunk,tags,branches,...}/package).
Anyhow, to be short: I count as 1, and we are in democracy; whatever
the team will come up, I'll stick to it eventually changing/reducing
the way I contribute to it.
Cheers and Happy Holidays,
--
Sandro Tosi (aka morph, Morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: numpy 1.2.1, switching to git?
Ondrej Certik wrote: > Agree. We talked with Sandro on IRC, the problem is in a bad internet > connection --- it takes ~40min to download 10MB -- then of course > every MB matters. For me it takes just couple seconds, so it doesn't > really matter if I am downloading tarball+debian dir separately, or > together in a git repo. but then if you need the original sources to build a package - it doesn't matter much if you get the tarball or clone a git repository. > I just assumed that everyone has a decent internet connection these > days, and I was wrong. :) unfortunately not... Cheers, Bernd -- Bernd Zeimetz Debian GNU/Linux Developer GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#509697: Python 2.5, ctypes, and binutils
Regarding #509697 (python 2.5 providing ctypes, and ctypes using objdump), I don't think it's reasonable to make python2.5 depend on binutils, just for the purpose of one of the modules in the standard library. One option would be to add binutils to Recommends or Suggest, but that does not ensure packages that Depend: python-ctypes will work. Maybe "python" should stop Providing: python-ctypes, and python-ctypes should depend on "python (>= 2.5) | python2.4" instead of just "python2.4" (plus the recently added a dependency on binutils). This way binutils will get pulled only when a package that depends on python-ctypes is installed. (This does not solve, however, packages that are being smart and are depending on "python (>= 2.5) | python-ctypes". But maybe those packages should stop doing that.) If this is the way to go, then for squeeze it means that, if the ctypes source package is to disappear, it should be created as a dummy package (from python-defaults instead?), if only to contain the binutils depends/recommends. Comments welcome. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org When all is summed up, a man never speaks of himself without loss; his accusations of himself are always believed; his praises never. -- Michel de Montaigne -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-pytc
On Thu, Dec 18, 2008 at 09:43:48PM +0100, Piotr O??arowski wrote: * why not Priority: optional? * please build -dbg package * consider using debhelper7's command sequencer (man dh) instead of CDBS, it will be easier to build -dbg package without CDBS, IMHO * add Vcs-Svn and Vcs-Browser fields I've just committed (r7192) the above suggestions (except for switching to dh). * did you send patches upstream? Will do. Happy holidays! Vernon signature.asc Description: Digital signature
Re: RFS: python-pytc
I cannot build it as I have currently access to i386 arch. only (and libtokyocabinet-dev is available for amd64 only), Please ping me (in private) when libtokyocabinet will be available for i386 or next week (I will be back home then)... unless someone else will pick it up in the meantime :-) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-pytc
* Piotr Ożarowski [Fri, 26 Dec 2008 22:12:37 +0100]: > Please ping me (in private) when libtokyocabinet will be available for > i386 #505317. -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org If you want the holes in your knowledge showing up try teaching someone. -- Alan Cox -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-pytc
On Fri, Dec 26, 2008 at 22:12, Piotr Ożarowski wrote: > I cannot build it as I have currently access to i386 arch. only > (and libtokyocabinet-dev is available for amd64 only), > > Please ping me (in private) when libtokyocabinet will be available for > i386 or next week (I will be back home then)... unless someone else will > pick it up in the meantime :-) Built on amd64 and it builds fine, even package contents it's ok; my only concern is about depending on python-all-dbg for -dbg package. Cheers, -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi
