bug tracking for non-RC architectures

[Steve Langasek]

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
, 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-sparc&nam0=Status&pri0=pending:pending,forwarded,pending-fixed,fixed,done&ttl0=Outstanding,Forwarded,Pending%20Upload,Fixed%20in%20NMU,Resolved&nam1=Architecture&pri1=tag:rc-arm,rc-m68k,rc-s390,rc-sparc&ttl1=arm,m68k,s390,sparc&ord1=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

HELP!

[C. Lawrence Perkins]

I'm trying to install Debian GNU/Linux under 
z/VM.  I can't get the installer to successfully reach any mirror 
sites.  I know I'm getting to the site, but it says the "mirror site is not 
available [ I know it IS, I can FTP to it from another CMS UserID ] or doesn't 
have a valid Release file" but I can see a file called "Release" in two places 
on the directory tree and pointing the installer to them doesn't seem to 
help.
 
Can you put me in contact with ANYONE who has done 
a successful S390 Debian install on z/VM?
 
Thank you .
 
Larry Perkins
214.478.9193
or reply this e-mail address
 

Re: Kernel 2.6

[Bastian Blank]

On Wed, Dec 21, 2005 at 02:53:54PM -0300, Jerônimo Bezerra wrote:
> I am Jeronimo and I work at one University in Brazil and here we have a
> S/390. We installed the Debian Woody 3.0 some time ago, and now we have
> make a another installation with Sarge 3.1, and if possible, using a
> kernel 2.6. Is it possible? 

You can't install sarge with 2.6 kernel, but you can install it
after the installation succedes, but there exists no hardware
configuration. This means, you have to manualy populate /etc/modutils
with the correct command line for the dasd modules (dasd is not longer
compiled in) and the network device configuarion in the sysfs.

> I downloaded the images from
> ftp.debian.org/debian/dists/sarge/main/installer-s390/current/images/generic 
> and when I start the Profile, appers kernel 2.4.27. The installer recognize 
> my NIC LCS, but it doesn't work, I don't know how yet, but in console, I 
> write "ifconfig eth0" and receive a error that says "Device not found" and 
> assing the IP Address to interface sit0.

We never had the chance to test a LCS NIC as all new machines have qeth.

Bastian

-- 
Another dream that failed.  There's nothing sadder.
-- Kirk, "This side of Paradise", stardate 3417.3


signature.asc
Description: Digital signature

Re: Mail Delivery (failure regis...@edonkey2000.com)

[register]

From: [EMAIL PROTECTED]
Subject: Doesn't accept mail

No one reads this address. If you need customer support please send mail to 
[EMAIL PROTECTED]
Thanks,
Jed.
 Original Message 




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]