-bag errors ;-).
That too :-) But I mostly value them for avoiding the introduction of
ABI changes or otherwise changed behaviour which break existing
packages. E. g. if we upload a new pygobject which breaks our
graphical installer (ubiquity), we'd hold pygobject instead of
noticing the break
ed features, but it could perhaps look like
Tests: foo
Features: build-target=testonly
Which would then expect a "testonly" debian/rules target.
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
-
.
It kind of does by rejecting packages which don't build on all
platforms, i. e. if tests during build fail on a particular arch.
> Would it be worth running them as autopkgtest tests *as well* for
> this use case?
If you can, sure. Otherwise a quick smoke test
compromise?
>
> It does indeed, with Jakub's idea of copying only the required code to
> $ADTTMP too.
Done now:
http://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=commitdiff;h=9b4ffe65ce
Language/grammar/style corrections appreciated :)
Martin
--
Martin Pitt
I wouldn't want to drop build-needed, as it only complicates things
for the cases where people want it. But I'm happy to add a stanza to
its documentation to avoid it for packages which take a nontrivial
amount of time to build; does that sound like an acceptable
compromise?
ules build-tests" (or whichever target you have) in
debian/tests/mytest.
autopkgtest calls dpkg-buildpackage to do the actual package build, so
for adding this to autopkgtest explicitly, we could add a flag for
that and call dpkg-buildpackage --target.
Martin
--
Martin Pitt
n specific in libpq-dev.
Thus you should do
> -PGXS := $(shell pg_config --pgxs)
> +PGXS := $(shell /usr/lib/postgresql/8.2/bin/pg_config --pgxs)
Martin
--
Martin Pitthttp://www.piware.de
Ubuntu Developer http://www.ubuntu.com
Debian Developer http://www.debian.org
signature.asc
Description: Digital signature
s0
> a warning.
No need to, both packages that depend on it come from the same source
package as libsysfs0 itself (from sysfsutils, which I maintain) :-)
Thanks again and have a nice day!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED]
s0
> a warning.
No need to, both packages that depend on it come from the same source
package as libsysfs0 itself (from sysfsutils, which I maintain) :-)
Thanks again and have a nice day!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED]
testing)? Or
do the archive scripts recognize this automatically and drop the
package as soon as no other package is depending on it any more?
Thank you in advance!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED] [EMAIL PROTECTED]
http
testing)? Or
do the archive scripts recognize this automatically and drop the
package as soon as no other package is depending on it any more?
Thank you in advance!
Martin
--
Martin Pitt Debian GNU/Linux Developer
[EMAIL PROTECTED] [EMAIL PROTECTED]
http
beta
releases and the 1.1 so that the bugs are explicitly closed by the
unstable upload?
Thanks for enlightenment and have a nice day!
Martin
(Please keep me CC'ed, I'm not subscribed)
--
Martin Pitt
home: www.piware.de
eMail: [EMAIL PROTECTED]
beta
releases and the 1.1 so that the bugs are explicitly closed by the
unstable upload?
Thanks for enlightenment and have a nice day!
Martin
(Please keep me CC'ed, I'm not subscribed)
--
Martin Pitt
home: www.piware.de
eMail: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL
13 matches
Mail list logo
