Bill Allombert [EMAIL PROTECTED] wrote:
This should be fixed by rebuilding af. However, since we are moving
to a new menu structure, the menu file will need to be updated[1], so
the packages will need a new sourceful upload anyway.
The footnote was missing, unfortunately: I'm really curious
On Mon, Jun 25, 2007 at 08:22:17AM +0200, Frank Küster wrote:
Bill Allombert [EMAIL PROTECTED] wrote:
This should be fixed by rebuilding af. However, since we are moving
to a new menu structure, the menu file will need to be updated[1], so
the packages will need a new sourceful upload
Bill Allombert [EMAIL PROTECTED] wrote:
On Mon, Jun 25, 2007 at 08:22:17AM +0200, Frank Küster wrote:
Bill Allombert [EMAIL PROTECTED] wrote:
This should be fixed by rebuilding af. However, since we are moving
to a new menu structure, the menu file will need to be updated[1], so
the
On 24/06/07 at 20:25 +0200, Steinar H. Gunderson wrote:
Steinar, do you want to merge your release goal with that one, or do you
prefer
me to file a seperate release goal? The main reason why I think they should
be
merged is that the way to detect issues is similar.
I'd prefer to
On Mon, Jun 25, 2007 at 12:34:30PM +0200, Frank Küster wrote:
Bill Allombert [EMAIL PROTECTED] wrote:
On Mon, Jun 25, 2007 at 08:22:17AM +0200, Frank Küster wrote:
Bill Allombert [EMAIL PROTECTED] wrote:
This should be fixed by rebuilding af. However, since we are moving
to a new
On Fri, Jun 22, 2007 at 09:23:16AM +0200, Lucas Nussbaum wrote:
However, with this setup, you only check that building packages in
non-clean environments doesn't significantly affect the package. It
would be interesting to check as well if the resulting package matches
what is in the archive,
Matthew Johnson wrote:
Also, you should consider build systems which switch using the
alternatives system. Debian Java policy says that debian/rules must
specify the build system to use explicitly, but there are a number of
packages which don't.
If you know of any such packages, please file
On Fri, Jun 22, 2007 at 11:25:44PM +0100, Enrico Zini wrote:
- compute a delicateness index of a package by summing the SAT
temperature of all packages that depend on it, and then give special
attention to the most delicate packages to see RC bugs, maintainer
activity and so on.
On Sat, Jun 23, 2007 at 09:35:25AM +0100, Enrico Zini wrote:
On Fri, Jun 22, 2007 at 11:25:44PM +0100, Enrico Zini wrote:
- compute a delicateness index of a package by summing the SAT
temperature of all packages that depend on it, and then give special
attention to the most
On Fri, Jun 22, 2007 at 09:37:39PM +0200, Lucas Nussbaum wrote:
af:
files list differ:
-./usr/lib/menu
-./usr/lib/menu/af
+./usr/share/menu
+./usr/share/menu/af
Non-ancient debhelper.
Still, what do we want to do about those?
This should be fixed by rebuilding af.
As discussed during DebConf, I'd like to propose a new release goal:
Packages should not only build in clean chroots, but also in non-clean
environments. Specifically, adding extra packages from the archive
into the build environment (that are not in Build-Conflicts) should
not affect the
On 22/06/07 at 01:49 +0200, Steinar H. Gunderson wrote:
As discussed during DebConf, I'd like to propose a new release goal: Packages
should not only build in clean chroots, but also in non-clean environments.
Specifically, adding extra packages from the archive into the build
environment
Lucas Nussbaum wrote:
acepack:
r-cran-acepack's depends differ:
-Depends: libc6 , libg2c0 , libgcc1 , r-base-core
+Depends: libc6 , libgcc1 , libgfortran1 , r-base-core
Caught by the BDFH.
alamin:
alamin-client's postinst differs:
if [ -x /etc/init.d/alamin-server ]; then
On 22/06/07 at 20:08 +0100, Joey Hess wrote:
Lucas Nussbaum wrote:
acepack:
r-cran-acepack's depends differ:
-Depends: libc6 , libg2c0 , libgcc1 , r-base-core
+Depends: libc6 , libgcc1 , libgfortran1 , r-base-core
Caught by the BDFH.
Ok, good to know.
alamin:
On Fri, Jun 22, 2007 at 01:49:25AM +0200, Steinar H. Gunderson wrote:
as it's stable.) The idea is to build a package both in a pbuilder and in
a really filled chroot -- it currently contains 18GB of packages, which is
most of the devel and libdevel sections. What is compared is:
This is
[Please keep discussion on -devel; -release is not a discussion list and
I'm not subscribed to -qa :-)]
Hi,
As discussed during DebConf, I'd like to propose a new release goal: Packages
should not only build in clean chroots, but also in non-clean environments.
Specifically, adding extra
Hi,
Steinar H. Gunderson schrieb:
To this end, I've set up the build daemon from Hell (BDFH) on my machine,
currently doing script testing.
Would it make sense to run the build under auto-apt, to see whether it
tries to access some file in another package? That would obviously not
be a
17 matches
Mail list logo
