bug tracking for non-RC architectures
Hi folks, For architectures that are not release candidates, we are going to need another way to track release critical bugs. The whole point of having architecture criteria is so the project can give higher priority to issues affecting release architectures (or all architectures) than to issues that are specific to an architecture that isn't meeting our standards for releasability; and we're not doing that very effectively if we leave such architecture-specific bugs at RC severity. OTOH, we don't want to lose sight of them by just downgrading the severities, as this would make it awkward to reintroduce the architecture as a release candidate without also silently reintroducing RC bugs. Usertags to the rescue! I've gone through the current list of release critical bugs at http://bugs.debian.org/release-critical/debian/all.html, identified the bugs that I believe are specific to one or more of arm, m68k, s390, and sparc, and have downgraded/usertagged them. The results for all archs can be seen here: http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-arm,rc-m68k,rc-s390,rc-sparcnam0=Statuspri0=pending:pending,forwarded,pending-fixed,fixed,donettl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU,Resolvednam1=Architecturepri1=tag:rc-arm,rc-m68k,rc-s390,rc-sparcttl1=arm,m68k,s390,sparcord1=0,1,2,3 Per-architecture views are also available: http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-arm http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-m68k http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-s390 http://bugs.debian.org/cgi-bin/pkgreport.cgi?which=tag[EMAIL PROTECTED]tag=rc-sparc This gives us convenient access to the bug lists relevant to each architecture, so that they can be upgraded again if/when the architecture meets the release criteria. I strongly encourage you to use this same usertag convention (rc-$arch usertag, under user debian-release@lists.debian.org) when filing new bugs about breakage specific to your architecture. Please refer to Anthony Towns' announcement[0] if you have questions about the use of usertags. Oh, and this also gives porters a handy list of bugs affecting their architecture that they can be working on in between getting things back in line with the release arch standards. As always, porter NMUs are encouraged -- you don't need an RC bug as an excuse to fix a package for your architecture! Wouldn't it be great to have zero bugs on that page two months from now? :) Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ [0] http://lists.debian.org/debian-devel-announce/2005/09/msg2.html signature.asc Description: Digital signature
Re: kdevelop3 FTBS on alpha/mipsel/s390 (should be Dep-Wait)
On Wed, Dec 07, 2005 at 11:10:56AM +, Jeremy Laine wrote: (second try, I got 2 out of 3 emails wrong the first time round) I am having problems getting kdevelop3 to build on alpha, mipsel and s390 due to unsatisfied Build-Depends: http://people.debian.org/~igloo/status.php?packages=kdevelop3 Is Dep-Wait supported by the corresponding buildd's or not yet? FWIW: Dep-Wait is a feature of wanna-build, not of the buildds. So is Auto-Dep-Wait, which is what I assume you're referring to; either way, it's supported for all architectures. But it's only automatic if w-b can figure out that one of your package's build-dependencies in *unavailable*, rather than *uninstallable*. A Dep-Wait has been set now for kdevelop3 on the affected archs. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Bug#306308: xearth: FTBFS: Missing Build-Depends on 'xutils'
On Mon, Apr 25, 2005 at 07:21:34PM +0200, Andreas Jochens wrote: Package: xearth Version: 1.1-10 Severity: serious Tags: sarge When building 'xearth' in a clean 'testing' chroot, I get the following error: dh_clean debian/rules build dh_testdir # Add here commands to configure the package. xmkmf make: xmkmf: Command not found make: *** [configure-stamp] Error 127 The new version in sid fixes this by adding the missing Build-Depends on xutils in debian/control. Non-free package, needs manual builds on ia64, m68k, s390 -- any volunteers? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
s390 binNMUs needed: emifreq-applet 0.17-2, ximian-connector 2.0.3-1
Hi folks, The emifreq-applet and ximian-connector packages have picked up a dependency on libhowl0 on s390, but not on any other architectures. Since libhowl0 is being moved out of main, these packages need to be rebuilt without libhowl0 -- which should only require a rebuild of the sources, now that none of the build-dependencies pull it in. Can someone do a recompile binNMU of these packages for s390, to spare the trouble of rebuilding on all architectures? Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Please requeue gpa for building on s390
Please requeue gpa for building on s390. According to the build logs, the last build (in November -- http://buildd.debian.org/fetch.php?pkg=gpaver=0.7.0-1arch=s390stamp=1069147811file=logas=raw) failed because of a missing build dep which is now available. Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Please re-queue uw-imap for building
Could someone re-queue uw-imap for building on arm, s390, and hppa? The first build attempt failed on these archs due to a now-fixed bug in po-debconf (214397). Thanks, -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
