OoO En cette matinée pluvieuse du lundi 23 février 2009, vers 10:12,
Josselin Mouette j...@debian.org disait :
Do we need to upload a new version when there is a fix needed? In this
case, I suppose we should use python-support in unstable instead of the
one in experimental?
Yes, it is
Le lundi 02 mars 2009 à 15:48 +0100, Vincent Bernat a écrit :
I ask this because I have many packages that use unittests after the
build. I add /var/lib/python-support to PYTHONPATH and launch those
tests. Because the path has changed, this does not work any more.
You suggest to run
On Sun, Mar 1, 2009 at 4:14 PM, Tristan Seligmann
mithra...@mithrandi.net wrote:
* David Cournapeau courn...@gmail.com [2009-02-28 20:22:46 +0900]:
I have never used stacked branches, but are you sure you can only
branch the repository data related to a subset of the working tree
only ? My
* Josselin Mouette j...@debian.org [2009-03-02 16:21:20 +0100]:
Le lundi 02 mars 2009 à 15:48 +0100, Vincent Bernat a écrit :
I ask this because I have many packages that use unittests after the
build. I add /var/lib/python-support to PYTHONPATH and launch those
tests. Because the
* Ondrej Certik ond...@certik.cz [2009-03-02 11:07:25 -0500]:
If you don't want the project history, then you can use lightweight
checkouts, which are essentially equivalent to SVN checkouts (you get a
local working copy, but no local branch or repository).
Ah, so you basically only get
* Ondrej Certik [Mon, 02 Mar 2009 11:07:25 -0500]:
I have never used stacked branches, but are you sure you can only
branch the repository data related to a subset of the working tree
only ? My understanding is that bzr stacked branches are useful to
avoid downloading the whole history,
On Mon, 2009-02-03 at 17:37 +0100, Adeodato Simó wrote:
As far as I know, Git doesn't have a mechanism to create full-fledged
repositories with only part of the history, referencing other remote
repositories for missing data. With my Git user hat on, this is clearly
a technically inferiority
* Guy Hulbert [Mon, 02 Mar 2009 12:47:45 -0500]:
On Mon, 2009-02-03 at 17:37 +0100, Adeodato Simó wrote:
As far as I know, Git doesn't have a mechanism to create full-fledged
repositories with only part of the history, referencing other remote
repositories for missing data. With my Git
OoO Vers la fin de l'après-midi du lundi 02 mars 2009, vers 16:21,
Josselin Mouette j...@debian.org disait :
I ask this because I have many packages that use unittests after the
build. I add /var/lib/python-support to PYTHONPATH and launch those
tests. Because the path has
OoO Vers la fin de l'après-midi du lundi 02 mars 2009, vers 16:21,
Josselin Mouette j...@debian.org disait :
I ask this because I have many packages that use unittests after the
build. I add /var/lib/python-support to PYTHONPATH and launch those
tests. Because the path has
OoO Pendant le repas du lundi 02 mars 2009, vers 19:44, je disais:
I use this snippet then (with cdbs):
ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
common-install-indep::
PYTHONPATH='debian/$(cdbs_curpkg)/$(cdbs_python_support_path)/' \
python tests/runner.py
OoO Pendant le repas du lundi 02 mars 2009, vers 19:57, je disais:
Which can be shorten to:
ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
common-install-indep::
PYTHONPATH='debian/$(cdbs_curpkg)/$(cdbs_python_support_path)/' \
python tests/runner.py
endif
Which is
On Mon, Mar 02, 2009 at 12:47:45PM -0500, Guy Hulbert wrote:
On Mon, 2009-02-03 at 17:37 +0100, Adeodato Simó wrote:
As far as I know, Git doesn't have a mechanism to create full-fledged
repositories with only part of the history, referencing other remote
repositories for missing data. With
[Piotr Ożarowski, 2009-02-18]
[...] it's time however to decide which one will be my
winner - I'll decide that in next weeks (maybe months, but it
will happen sooner than later
Since nobody is interested in having the tools binary compatible[1]
(and, to be honest, I cared about opinion of two
Steve Langasek vor...@debian.org (02/03/2009):
My rebuttal is that if git is technical superior to bazaar because
bazaar has a mechanism to create repositories with only partial
history, then bazaar is technically superior to git because git has
rebasing as a first-class feature.
Oh my HEAD,
On Mon, Mar 2, 2009 at 11:27 AM, Tristan Seligmann
mithra...@mithrandi.net wrote:
* Ondrej Certik ond...@certik.cz [2009-03-02 11:07:25 -0500]:
If you don't want the project history, then you can use lightweight
checkouts, which are essentially equivalent to SVN checkouts (you get a
local
On Mon, Mar 2, 2009 at 4:17 PM, Piotr Ożarowski pi...@debian.org wrote:
[Piotr Ożarowski, 2009-02-18]
[...] it's time however to decide which one will be my
winner - I'll decide that in next weeks (maybe months, but it
will happen sooner than later
Since nobody is interested in having the
Hi Adeodato,
On Mon, Mar 2, 2009 at 11:37 AM, Adeodato Simó d...@net.com.org.es wrote:
* Ondrej Certik [Mon, 02 Mar 2009 11:07:25 -0500]:
I have never used stacked branches, but are you sure you can only
branch the repository data related to a subset of the working tree
only ? My
Piotr Ożarowski pi...@debian.org writes:
PS while converting [a package using python-central to use
python-support], remember to add to preinst something like these 3
lines:
| if [ $1 = upgrade ] dpkg --compare-versions $2 lt 1.2.3-4; then
| pycentral pkgremove python-foo
| fi
Why
[Ben Finney, 2009-03-02]
Piotr Ożarowski pi...@debian.org writes:
PS while converting [a package using python-central to use
python-support], remember to add to preinst something like these 3
lines:
| if [ $1 = upgrade ] dpkg --compare-versions $2 lt 1.2.3-4; then
| pycentral
[Piotr Ożarowski, 2009-03-02]
[Ben Finney, 2009-03-02]
Piotr Ożarowski pi...@debian.org writes:
PS while converting [a package using python-central to use
python-support], remember to add to preinst something like these 3
lines:
| if [ $1 = upgrade ] dpkg --compare-versions $2
On Mon, Mar 02, 2009 at 05:30:57PM -0500, Ondrej Certik wrote:
On Mon, Mar 2, 2009 at 3:44 PM, Steve Langasek vor...@debian.org wrote:
My rebuttal is that if git is technical superior to bazaar because bazaar
has a mechanism to create repositories with only partial history, then
bazaar is
[Ondrej Certik, 2009-03-03]
why is the decision unfair?
because *I* think it's unfair as both tools deserve to be the chosen
one
Ondrej: stop reading debian-devel, you see trolls everywhere already ;-P
--
-=[ Piotr Ożarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpaT3cZ1Nt8P.pgp
Hi
Dne Mon, 2 Mar 2009 22:17:52 +0100
Piotr Ożarowski pi...@debian.org napsal(a):
Since nobody is interested in having the tools binary compatible[1]
(and, to be honest, I cared about opinion of two guys only: Matthias
voted no by not agreeing to use /usr/lib/pyshared and Joss expressed
his
Piotr Ożarowski pi...@debian.org (03/03/2009):
[Cyril Brulebois, 2009-03-03]
Piotr Ożarowski pi...@debian.org (02/03/2009):
[Ben Finney, 2009-03-02]
Why does this not happen automatically when the package is upgraded
from a version that uses python-central?
how can
Ondrej Certik ond...@certik.cz writes:
why is the decision unfair?
You'll have to ask Piotr (the one making the decision, and also the
one who chose that subject field), not me.
--
\ “Pity the meek, for they shall inherit the earth.” —Donald |
`\
On Tue, Mar 03, 2009 at 12:39:48AM +0100, Cyril Brulebois wrote:
Piotr Ożarowski pi...@debian.org (03/03/2009):
[Cyril Brulebois, 2009-03-03]
Piotr Ożarowski pi...@debian.org (02/03/2009):
[Ben Finney, 2009-03-02]
Why does this not happen automatically when the package is upgraded
Cyril Brulebois k...@debian.org writes:
Piotr Ożarowski pi...@debian.org (03/03/2009):
[Cyril Brulebois, 2009-03-03]
Piotr Ożarowski pi...@debian.org (02/03/2009):
[Ben Finney, 2009-03-02]
Why does [removal of links created by ‘python-central’] not
happen automatically when
On Tue, Mar 3, 2009 at 1:37 AM, Adeodato Simó d...@net.com.org.es wrote:
3. Git
==
Git has shallow clones, created with the --depth option for git-clone.
This cut-offs the history of the project past a certain point, but the
result is lacking: mainly, you cannot push your changes back.
29 matches
Mail list logo
