just curious, I'm not related to this RFS, should I still receive this
message?
2013/1/15 Arno Töll a...@debian.org
Sorry for the hijack of your RFS, I'm testing our new mail filter.
Please ignore me :)
--
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID:
The message has been sent to debian-mentors, so if you're subscribed to
the list that is probably why you are getting the e-mails like I am.
On Tue, Jan 15, 2013 at 02:18:48PM -0200, Carlos Jordão wrote:
just curious, I'm not related to this RFS, should I still receive this
message?
Scantailor, and
so
far during build the test suite fails (with an override the package builds
through).
The failure is that:
cut
make[1]: Entering directory
`/tmp/buildd/scantailor-0.9.11.1/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j1
Test project /tmp
Hi guys,
I'm working on packaging the scanned documents post processor Scantailor, and so
far during build the test suite fails (with an override the package builds
through).
The failure is that:
cut
make[1]: Entering directory
`/tmp/buildd/scantailor-0.9.11.1/obj-x86_64-linux-gnu'
Running
On Wed, Dec 12, 2012 at 11:35 AM, Daniel Stender
dan...@danielstender.com wrote:
test: cannot connect to X server :0
You do not have X11 on buildd. You need to use Xvfb during execution
of your test suite.
Eg.
https://lists.debian.org/debian-java/2012/11/msg6.html
HTH
--
To UNSUBSCRIBE
this is only a test
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1352692693.2676.9.camel@vulcan
Your message dated Sat, 25 Aug 2012 11:24:39 +
with message-id e1t5etn-00085a...@quantz.debian.org
and subject line closing RFS: bwctl/1.4-1 [ITP] -- bandwidth test controller
has caused the Debian Bug report #666221,
regarding RFS: bwctl/1.4-1 [ITP] -- bandwidth test controller
to be marked
changing to apache license in
upcoming release of bwctl
Then it should not go to main. See [1] how to change this in the source
package.
bwctl-client - bandwidth test controller (client)
bwctl-doc - documentation for bandwidth test controller
bwctl-server - bandwidth test
of bwctl
Section : net
It builds those binary packages:
bwctl-client - bandwidth test controller (client)
bwctl-doc - documentation for bandwidth test controller
bwctl-server - bandwidth test controller (server)
i2util-tools - internet2 utilities
libbwlib-dev - bandwidth test
I am not subscribed to this list.
Hi!
I suggest you not to put any more energy into it - in case you didn´t
already notice yourself.
From what I have seen from Carl-Valentin Schmitt - whether that is his
real name or not I do not know - on debian-user-german[1], kernel-testers
Am 2012-02-16 10:28, schrieb Michael van der Kolff:
But if you were serious, I'd say that this is where software that has
been written comes to get packaged - development is what you do on
github.com, gitorious.org, etc.
Cheers,
Michael
Hello Mike,
in github.com - there is M$ and fakebook
Neither github.com nor gitorious.org are owned by MS. Anyone may host
whatever they like, so long as it's in accordance with the law.
On 20/02/2012 11:45 PM, SchmiTTT cv.schm...@googlemail.com wrote:
Am 2012-02-16 10:28, schrieb Michael van der Kolff:
But if you were serious, I'd say that
It's a troll.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f426f54.4070...@gmail.com
Am 2012-02-20 17:05, schrieb Igor Pashev:
It's a troll.
sorry no !
I am a misunderstood autistic penguin !
Regards.
Val.
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Hello dear mentors,
this code is, when I am not wrong, revolutionary. It is a new program,
to resolve
bugs in some programs and configuration-errors in conf-files
This program is ironing the wrinkles of Linux away.
Before I make a debian-package of it, I want you to test this code.
I had
programs and configuration-errors in conf-files
This program is ironing the wrinkles of Linux away.
Before I make a debian-package of it, I want you to test this code.
I had only the problem with a too dark screen on my notebook (intel core
duo with 2 BIOS-chips).
The dark screen is still
On 01/03/2012 11:38 AM, fre...@free.fr wrote:
What's the way to take, to test the presence of a list of packages
and to install one package or more in case where none are already
installed ?
This is handled by declaring package relationships via Depends:,
Recommends:, etc.
http
- Mail original -
De: Michael Shuler mich...@pbandjelly.org
À: debian-mentors@lists.debian.org
Envoyé: Mardi 3 Janvier 2012 18:44:42
Objet: Re: How to test the presence of packages ?
On 01/03/2012 11:38 AM, fre...@free.fr wrote:
What's the way to take, to test the presence of a list
Il giorno mar, 03/01/2012 alle 18.56 +0100, fre...@free.fr ha scritto:
- Mail original -
De: Michael Shuler mich...@pbandjelly.org
À: debian-mentors@lists.debian.org
Envoyé: Mardi 3 Janvier 2012 18:44:42
Objet: Re: How to test the presence of packages ?
On 01/03/2012 11:38 AM
On 03/01/12 13:08, fre...@free.fr wrote:
Hello,
What's the way to take, to test the presence of a list of packages and to
install one package or more in case where none are already installed ?
Regards,
Fred.
You mean like, in a package or a script?
--
Luis Alejandro Martínez
- Mail original -
De: Luis Alejandro Martínez Faneyth l...@huntingbears.com.ve
À: debian-mentors@lists.debian.org
Envoyé: Mardi 3 Janvier 2012 18:52:02
Objet: Re: How to test the presence of packages ?
You mean like, in a package or a script?
Thats the question, how to do
${PACKAGE}
fi
done
==8==8==
Now, if you need this at package level, you should listen to Pietro's
advices.
On 03/01/12 13:08, fre...@free.fr wrote:
Hello,
What's the way to take, to test the presence of a list of packages and to
install one
Replacing If none is installed then install package2 and package3 with
If none is installed then isntall package2, then the solution is:
Depends: package2 | package1 | package3 | package4
OK.
Replacing If one of this list is already installed with If at least
two out of this list are
Am Dienstag, den 03.01.2012, 14:29 -0430 schrieb Luis Alejandro Martínez
Faneyth:
If you need a simple script logic, you could use bash like this:
==8==8==
#!/bin/bash
PACKAGES=package1 package2 package3
for PACKAGE in ${PACKAGES}; do
better.
Sure!
The summary page is
http://earth.esa.int/services/sample_products/
the url of the product to be downloaded for test is
http://earth.esa.int/services/sample_products/meris/LRC/L2/MER_LRC_2PTGMV2620_104318_0104X000_0_0_0001.N1.gz
Although data are available for free
Le Sun, Aug 14, 2011 at 10:26:04AM +0200, Antonio Valentino a écrit :
Uhm, how much is it important to test the package at build time?
Dear Antonio,
I have experience distributing a completely broken package for weeks or monthes
without anybody noticing, so I would recommend to run
Antonio Valentino antonio.valent...@tiscali.it writes:
the url of the product to be downloaded for test is
http://earth.esa.int/services/sample_products/meris/LRC/L2/MER_LRC_2PTGMV2620_104318_0104X000_0_0_0001.N1.gz
Thanks.
Uhm, how much is it important to test the package
On Sun, Aug 14, 2011 at 11:35 AM, Ben Finney ben+deb...@benfinney.id.au wrote:
Don't be. That's not a reason to avoid distributing it in Debian, if
it's useful overall to Debian recipients to do so.
The question remains about getting a free-software license to do so, but
you're aware of
Hi mentors,
I have a package (pyepr) that provides a small python extension written
in cython.
The upstream source includes a test suite that needs some data to be
downloaded from the internet (398K) using wget.
Note that data are only used for testing, they are not installed.
My question
On Sat, 13 Aug 2011 13:09:57 +0200, Antonio Valentino wrote:
My question is: is it sane to download data at package build time?
It's not possible, buildds don't have network access.
Kindly,
David
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216
Il 13/08/2011 13:24, David Paleino ha scritto:
On Sat, 13 Aug 2011 13:09:57 +0200, Antonio Valentino wrote:
My question is: is it sane to download data at package build time?
It's not possible, buildds don't have network access.
Kindly,
David
OK, thanks David
--
Antonio Valentino
Excerpts from Antonio Valentino's message of Sat Aug 13 07:09:57 -0400 2011:
Hi mentors,
I have a package (pyepr) that provides a small python extension written
in cython.
The upstream source includes a test suite that needs some data to be
downloaded from the internet (398K) using wget
Antonio Valentino antonio.valent...@tiscali.it writes:
The upstream source includes a test suite that needs some data to be
downloaded from the internet (398K) using wget. Note that data are
only used for testing, they are not installed.
Downloading data to run automated code tests
Asheesh Laroia li...@asheesh.org writes:
Excerpts from Antonio Valentino's message of Sat Aug 13 07:09:57 -0400 2011:
Hi mentors,
I have a package (pyepr) that provides a small python extension written
in cython.
The upstream source includes a test suite that needs some data
Hi guys,
thank you for all your answers
Il 13/08/2011 13:09, Antonio Valentino ha scritto:
Hi mentors,
I have a package (pyepr) that provides a small python extension written
in cython.
The upstream source includes a test suite that needs some data to be
downloaded from the internet (398K
: LGPL-2+
Section : devel
It builds these binary packages:
failmalloc - Memory allocation failure crash-test tool
The package appears to be lintian clean.
The upload would fix these bugs: 462792 (ITP)
My motivation for maintaining this package is: I have found this tool
...@enbug.org
* URL : http://www.nongnu.org/failmalloc
* License : LGPL-2+
Section : devel
It builds these binary packages:
failmalloc - Memory allocation failure crash-test tool
The package appears to be lintian clean.
The upload would fix these bugs
Alessandro Ghedini al3x...@gmail.com writes:
Is anyone interested in uploading this package?
I'm interested; it's a potentially very useful piece of software. I did
a quick look at your package, and found the following issues:
- You seem to have repacked the upstream source:
% cmp
On Fri, Jan 14, 2011 at 05:04:11PM +0100, Andreas Rottmann wrote:
Alessandro Ghedini al3x...@gmail.com writes:
Is anyone interested in uploading this package?
I'm interested; it's a potentially very useful piece of software. I did
a quick look at your package, and found the following
It builds these binary packages:
failmalloc - Memory allocation failure crash-test tool
The package appears to be lintian clean.
The upload would fix these bugs: 462792 (ITP)
My motivation for maintaining this package is: I have found this tool
very helpful. I packaged it for myself, and I
It builds these binary packages:
failmalloc - Memory allocation failure crash-test tool
libfailmalloc0 - Memory allocation failure crash-test tool (library)
The package appears to be lintian clean.
The upload would fix these bugs: 462792 (ITP)
My motivation for maintaining this package is: I have found
utilities according to [1].
It builds these binary packages:
failmalloc - Memory allocation failure crash-test tool
libfailmalloc0 - Memory allocation failure crash-test tool (library)
The package appears to be lintian clean.
The upload would fix these bugs: 462792 (ITP)
[...]
I would
On Tue, Jan 04, 2011 at 02:21:16PM +0100, Niels Thykier wrote:
I thinking that devel might be a better section than utils. Particularly
the devel section covers Development utilities according to [1].
Agreed.
Any particular reason for Build-Depending on autotools-dev? It does not
appear to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2011-01-04 16:40, Alessandro Ghedini wrote:
On Tue, Jan 04, 2011 at 02:21:16PM +0100, Niels Thykier wrote:
I thinking that devel might be a better section than utils. Particularly
the devel section covers Development utilities according to
On Tue, Jan 04, 2011 at 05:31:54PM +0100, Niels Thykier wrote:
Not quite correct. Lintian allows you to B-D on autotools-dev (among
others) to suppress this warning. Adding it to B-D makes lintian skip
the check entirely (yupe, I did look it up in the lintain source[1]). As
I recall you can do
On Tue, Jan 04, 2011 at 08:09:11PM +0100, Alessandro Ghedini wrote:
On Tue, Jan 04, 2011 at 05:31:54PM +0100, Niels Thykier wrote:
Not quite correct. Lintian allows you to B-D on autotools-dev (among
others) to suppress this warning. Adding it to B-D makes lintian skip
the check entirely
package: piuparts
severity: important
x-debbugs-cc: debian-mentors@lists.debian.org, mats.anders...@gisladisker.se,
566...@bugs.debian.org
Hi Mats,
On Donnerstag, 4. November 2010, Mats Erik Andersson wrote:
I am reading that last logging report, and I must draw this conclusion:
* There
itself, but are part of its regression tests.
Should I repackage a dfsg version of the source without these
files? (I think so, but would welcome a confirmation).
If so, how should I handle the tests? Should I automate the
download (I would use svn export) of the test data bank?
If sso, when
/Resources
If so, how should I handle the tests? Should I automate the
download (I would use svn export) of the test data bank?
If sso, when? At libcolladadom-dev install? Within the
dh_override_auto_test target?
If the material required for the tests are not in the orig.tar.gz then
you
Many thanks to everybody for their interesting answers. Here is a short
summary, and examples for a manpage called manpage.1.gz, in the current
directory.
Have a nice week-end,
-- Charles
How to test a local manpage.
Some manual pages are using helpers, usually ‘tbl’, ‘eqn’ or ‘pic
On Wed, Jul 14, 2010 at 10:07:37PM +0200, Daniel Leidert wrote:
I don't know if this would help you, but the canonical (lintian) way to
check that everything is OK is like this:
LANG=en_US.UTF-8 MANWIDTH=80 man --warnings -E UTF-8 -l file /dev/null
You'll of course see the warnings
Il 14/07/2010 6.50, Charles Plessy ha scritto:
Does anybody know how a more convenient to display a
manpage the same way as users will get it by using ‘man’ ?
groff -T ascii -man manpage
zcat /usr/share/man/manX/XXX | groff -T ascii -m man
--
.''`.
: :' : Luca Falavigna
14.07.2010 09:01, Russ Allbery wrote:
[]
You can just run man directly on the *roff file, but if you want to stick
with the zcat pipeline, just add the -t flag to nroff to say to run the
output through the tbl preprocessor first.
This is the most close of all suggestions. But even closer is:
On Wed, Jul 14, 2010 at 08:57:12AM +0200, Luca Falavigna wrote:
Il 14/07/2010 6.50, Charles Plessy ha scritto:
Does anybody know how a more convenient to display a
manpage the same way as users will get it by using ‘man’ ?
groff -T ascii -man manpage
zcat /usr/share/man/manX/XXX | groff
14.07.2010 13:14, Roger Leigh wrote:
On Wed, Jul 14, 2010 at 08:57:12AM +0200, Luca Falavigna wrote:
Il 14/07/2010 6.50, Charles Plessy ha scritto:
Does anybody know how a more convenient to display a
manpage the same way as users will get it by using ‘man’ ?
groff -T ascii -man manpage
Hi Charles,
On Wednesday 14 July 2010 06:50:57 Charles Plessy wrote:
Dear all,
before updating a package, I wanted to look at the new upstream manpage,
but realised that ‘nroff -man’ does not produce the same output as ‘man’
itself. Let's take the example of samtools(1) from the samtools
Am Mittwoch, den 14.07.2010, 15:48 +0200 schrieb Manuel A. Fernandez
Montecelo:
On Wednesday 14 July 2010 06:50:57 Charles Plessy wrote:
[..]
The workaround I found was to copy the new manpage in /tmp/man/man1, and
call ‘man -M /tmp/man samtools’. Does anybody know how a more convenient
to
Dear all,
before updating a package, I wanted to look at the new upstream manpage, but
realised that ‘nroff -man’ does not produce the same output as ‘man’ itself.
Let's take the example of samtools(1) from the samtools package.
With ‘man samtools’, users can see tables like the following one in
2010/7/14 Charles Plessy ple...@debian.org:
Dear all,
before updating a package, I wanted to look at the new upstream manpage, but
realised that 'nroff -man' does not produce the same output as 'man' itself.
Let's take the example of samtools(1) from the samtools package.
With 'man
Charles Plessy ple...@debian.org writes:
before updating a package, I wanted to look at the new upstream manpage,
but realised that ‘nroff -man’ does not produce the same output as ‘man’
itself. Let's take the example of samtools(1) from the samtools
package.
With ‘man samtools’, users can
:
Hi mentors,
On my package, dhcp-probe, i have a problem on 64 bits architectures (amd64
for the bug report).
I built a patch with help of Ilkka Virta and i have not any 64 bits host to
test the patch.
How to test a package 64 bits on a 32 bits host ?
If it is impossible, where can
On Saturday 12,September,2009 03:35 PM, Pietro Battiston wrote:
Il giorno ven, 11/09/2009 alle 21.31 +0200, Jérémy Lal ha scritto:
VirtualBox supports 64 bits guests on 32 bits hosts,
provided you have a cpu that supports virtualization.
Are there any 32 bit cpus around which support
On Sat, 12 Sep 2009 09:35:39 +0200, Pietro Battiston wrote:
Il giorno ven, 11/09/2009 alle 21.31 +0200, Jérémy Lal ha scritto:
VirtualBox supports 64 bits guests on 32 bits hosts,
provided you have a cpu that supports virtualization.
Are there any 32 bit cpus around which support
Il giorno sab, 12/09/2009 alle 13.33 +0200, Laurent Guignard ha scritto:
On Sat, 12 Sep 2009 09:35:39 +0200, Pietro Battiston wrote:
Il giorno ven, 11/09/2009 alle 21.31 +0200, Jérémy Lal ha scritto:
VirtualBox supports 64 bits guests on 32 bits hosts,
provided you have a cpu that
Le Saturday 12 September 2009 13:57:49 Pietro Battiston, vous avez écrit :
Il giorno sab, 12/09/2009 alle 13.33 +0200, Laurent Guignard ha scritto:
On Sat, 12 Sep 2009 09:35:39 +0200, Pietro Battiston wrote:
Il giorno ven, 11/09/2009 alle 21.31 +0200, Jérémy Lal ha scritto:
VirtualBox
On 12/09/2009 13:57, Pietro Battiston wrote:
Il giorno sab, 12/09/2009 alle 13.33 +0200, Laurent Guignard ha scritto:
On Sat, 12 Sep 2009 09:35:39 +0200, Pietro Battiston wrote:
Il giorno ven, 11/09/2009 alle 21.31 +0200, Jérémy Lal ha scritto:
VirtualBox supports 64 bits guests on 32 bits
Benoit Mortier wrote:
Hello,
You can run 64bit system on virtualbox on a 32bit cpu. I'am doing it to
compile stuff for amd64. For this to work you have to have vt extensions
on your cpu and virtualbox 2.2.0.
see:
model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz
just
Hi mentors,
On my package, dhcp-probe, i have a problem on 64 bits architectures (amd64
for the bug report).
I built a patch with help of Ilkka Virta and i have not any 64 bits host to
test the patch.
How to test a package 64 bits on a 32 bits host ?
If it is impossible, where can i test my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/11/09 20:17, Laurent Guignard wrote:
Hi mentors,
On my package, dhcp-probe, i have a problem on 64 bits architectures (amd64
for the bug report).
I built a patch with help of Ilkka Virta and i have not any 64 bits host to
test the patch
of Ilkka Virta and i have not any 64 bits host to
test the patch.
How to test a package 64 bits on a 32 bits host ?
If it is impossible, where can i test my package before submit it for upload ?
Is there any machine where i can logon freely and test my package (i am not
Debian Developer nor Debian
Laurent Guignard wrote:
Hi mentors,
On my package, dhcp-probe, i have a problem on 64 bits architectures
(amd64 for the bug report).
I built a patch with help of Ilkka Virta and i have not any 64 bits host
to test the patch.
How to test a package 64 bits on a 32 bits host
packages for Debian
using their own system resources?
That is, if I'm maintaining packages for Debian and want to build and
test them in an easy and automated manner, what tools are available
(‘pbuilder’, ‘sbuild’, ‘cowbuilder’, …) and for each of them why would I
choose that one?
--
\ “If you
In 87bpmvsux5.fsf...@benfinney.id.au, Ben Finney wrote:
That is, if I'm maintaining packages for Debian and want to build and
test them in an easy and automated manner, what tools are available
(‘pbuilder’, ‘sbuild’, ‘cowbuilder’, …) and for each of them why would I
choose that one?
There's
On Tue, Aug 04, 2009 at 09:57:49AM -0500, Boyd Stephen Smith Jr. wrote:
There's really only two that I know of. pbuilder (and variants:
qemubuilder, cowbuilder, etc.) and sbuild. ISTR, sbuild is used on the
buildds, but all my experience is with pbuilder. I find it incredibly
flexible
Hello,
At preparing zope2.11.3 packages, I found several python (test-)modules
that do have python2.5/python2.6 code. This code is mostly for checking
python2.5/python2.6 support, and thus isn't relevant for the
functionality of zope itself.
Zope2.11.3 still requires python2.4, so when
[Jonas Meurer, 2009-07-02]
At preparing zope2.11.3 packages, I found several python (test-)modules
that do have python2.5/python2.6 code. This code is mostly for checking
python2.5/python2.6 support, and thus isn't relevant for the
functionality of zope itself.
Zope2.11.3 still requires
Hello,
On 02/07/2009 Piotr Ożarowski wrote:
[Jonas Meurer, 2009-07-02]
At preparing zope2.11.3 packages, I found several python (test-)modules
that do have python2.5/python2.6 code. This code is mostly for checking
python2.5/python2.6 support, and thus isn't relevant
Jonas Meurer jo...@freesources.org writes:
On 02/07/2009 Piotr Ożarowski wrote:
PS consider switching to python-support or we'll force you to do
this in few months ;-)
thanks for the last suggestion. I finally noticed that python-support
already supports to exclude python files from
Hi,
On Donnerstag, 2. April 2009, Ben Finney wrote:
Yes. My question is, though, is it a good idea to run the one within
the other? As I understand it, ‘piuparts’ does its work inside a
chroot; is it advisable for that to happen while already inside
‘pbuilder’s existing chroot?
not really,
Howdy all,
I'm trying to make more use of ‘pbuilder’ hooks for automating the
testing of my packages.
Does it make sense to use a hook to install and remove the package
after it is built? The plus side is this would test that the
{pre,post}{inst,rm} programs run successfully. What
Ben Finney ben+deb...@benfinney.id.au writes:
Does it make sense to use a hook to install and remove the package
[in a ‘pbuilder’ chroot] after it is built? The plus side is this
would test that the {pre,post}{inst,rm} programs run successfully.
What are the negatives of this approach?
I've
On Thu, 2009-04-02 at 11:32 +1100, Ben Finney wrote:
I've been made aware of ‘piuparts’. Would it make sense to have a hook
to run this command, on the newly-built package, inside the ‘pbuilder’
chroot? How would such a hook program get access to the file name of
the binary package?
I think
Chow Loong Jin hyper...@gmail.com writes:
I think you should look at the lintian hook example in
/usr/share/doc/pbuilder/examples. That could possibly be copied and
modified to use piuparts.
Yes. My question is, though, is it a good idea to run the one within
the other? As I understand it,
Hi,
I'd like to sponsor a package that have problems in building on some
architectures. After fixing I need to build this package (at least)
on problematic architectures.
Is there any buildd network for test builds available?
If not, I think I have to use some Debian Machines. Is there any
On Wed, 25 Mar 2009 22:20:31 +0100
Erik Schanze schan...@gmx.de wrote:
Hi,
I'd like to sponsor a package that have problems in building on some
architectures. After fixing I need to build this package (at least)
on problematic architectures.
Is there any buildd network for test builds
On Mon, Feb 16, 2009 at 5:34 PM, Jens Peter Secher jpsec...@diku.dk wrote:
The package looks good, except for a few things:
Thanks for you review.
Now, please see my comments below:
- The Depends for libjabberd2-dev should be
libjabberd2 (= ${binary:Version}).
Solved.
- /var/spool/jabberd
On Thu, Nov 13, 2008 at 08:19:38PM -0600, Kumar Appaiah wrote:
Dear Debian Mentors,
*SKIP*
1. Is there a way to set an arbitrary environment variable while
running pbuilder (in my case, LD_LIBRARY_PATH).
Try adding Cexport LD_LIBRARY_PATH=/path/to/lib/in/chroot in
pbuilderrc (whatever is
On Thu, Nov 13, 2008 at 08:19:38PM -0600, Kumar Appaiah wrote:
I was wondering if you could suggest a nice way to use pbuilder to
test package builds with gcc-snapshot.
Just a note to point out that sbuild supports the use of gcc-snapshot without
any special configuration. Just add the --use
On Fri, Nov 14, 2008 at 12:25:16PM +, Roger Leigh wrote:
On Thu, Nov 13, 2008 at 08:19:38PM -0600, Kumar Appaiah wrote:
I was wondering if you could suggest a nice way to use pbuilder to
test package builds with gcc-snapshot.
Just a note to point out that sbuild supports the use of gcc
Dear Debian Mentors,
I was wondering if you could suggest a nice way to use pbuilder to
test package builds with gcc-snapshot. Currently, I've got a way
(albeit crude way) to get that working, and I have listed it here:
Bottom part of: http://wiki.debian.org/PbuilderTricks
However, one of my
On Fri, Nov 14, 2008 at 11:19 AM, Kumar Appaiah
[EMAIL PROTECTED] wrote:
1. Is there a way to set an arbitrary environment variable while
running pbuilder (in my case, LD_LIBRARY_PATH).
grep export ~/.pbuilderrc
export CCACHE_DIR=/var/cache/pbuilder/ccache
export PATH=/usr/lib/ccache:${PATH}
On Fri, Nov 14, 2008 at 11:34:31AM +0900, Paul Wise wrote:
1. Is there a way to set an arbitrary environment variable while
running pbuilder (in my case, LD_LIBRARY_PATH).
grep export ~/.pbuilderrc
export CCACHE_DIR=/var/cache/pbuilder/ccache
export PATH=/usr/lib/ccache:${PATH}
export
Paul Wise wrote:
On Fri, Nov 14, 2008 at 11:19 AM, Kumar Appaiah
[EMAIL PROTECTED] wrote:
1. Is there a way to set an arbitrary environment variable while
running pbuilder (in my case, LD_LIBRARY_PATH).
grep export ~/.pbuilderrc
export CCACHE_DIR=/var/cache/pbuilder/ccache
export
Howdy mentors,
Why does 'dh build' attempt to run the package's test suite, but
doesn't satisfy the run-time dependencies before doing so? How can
this be made to work within a pbuilder environment?
I'm packaging a Python application that has a unit test suite. This
unit test suite, naturally
You can tell pbuilder to include extra packages in the environment by
setting the EXTRAPACKAGES variable. In my .pbuilderrc I have something like:
PBUILDERSATISFYDEPENDSCMD=/usr/lib/pbuilder/pbuilder-satisfydepends-gdebi
case $TEST in
ffmpeg) # For testing of WinFF
EXTRAPACKAGES
Paul Gevers [EMAIL PROTECTED] writes:
You can tell pbuilder to include extra packages in the environment by
setting the EXTRAPACKAGES variable.
That doesn't scale. I can't expect everyone who might be building this
package (e.g. a sponsor, or the buildd hosts) to install packages
without
, or
perhaps both, need readjusting.
Hi,
some consider it good behavior to run the test suites at build time,
because it will help you detect bugs that happen on other
architectures than your own. And you can only fix bugs that you have
detected. This way you are certain that the packages you build
test
--
Anthony BERGER
Administrateur / Ingénieur Système
Infogérance CEA Cadarache
Tel : 04 42 25 78 46
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Neil Williams wrote:
On Sun, 2008-04-20 at 14:58 +0200, Martin Fuzzey wrote:
Hi mentors,
A little question regarding automatic test suites :
When a package provides such a suite should the normal package build process
:
1) Always run the test suite (for example to catch bugs that may
On Mon, 2008-04-21 at 10:14 -0700, Kevin B. McCarty wrote:
Neil Williams wrote:
1) Always run the test suite (for example to catch bugs that may not
occur on the developper's architecture)
Yes. (That is the main point of having a test suite.)
I agree with this (of course
201 - 300 of 501 matches
Mail list logo
