Mailinglist Archive: opensuse (1558 mails)

< Previous Next >
Re: [opensuse] positive progression of a bugzilla
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
  • Date: Thu, 27 Aug 2009 16:11:14 -0400
  • Message-id: <87f94c370908271311s256891fen513da3c8cd8ed84c@xxxxxxxxxxxxxx>
On Thu, Aug 27, 2009 at 1:29 PM, Marcus Meissner<meissner@xxxxxxx> wrote:
On Thu, Aug 27, 2009 at 01:24:43PM -0400, Greg Freemyer wrote:
All,

We keep reading about bugzillas that are ignored etc.

I was astounded to see one of my bugzillas was tagged "SHIP_STOPPER"
this morning.

https://bugzilla.novell.com/show_bug.cgi?id=529525

It relates to zypper dup just blindly using the configured
repositories and not ensuring the repositories are set appropriately
to do a "distribution upgrade".

The last Novel comment was from Stephen Kulow:
==
not to read any howto how to update distributions? Very possible, but not
exactly a bug ;(
==

To which I replied:
==
I guess I am of the minority and asinine opinion that a tool that accepts the
argument --distribution-upgrade should actually do a distribution upgrade.

Maybe the option should be renamed to "--distribution-upgrade-final-step"
with
shortform -dup_f.

Even better I think --distribution-upgrade should accept an argument that
defines the target distribution being upgraded to and performs the necessary
repository management.  After all, zypper is the main CLI tool for repository
management, so that is not outside the scope of what a normal user might
expect.

Clearly anyone considering zypper -dup has Internet access, so it could be
updated as needed to work with the new repositories at each distro release.
==

I must say, I expected the bugzilla to be closed as not a bug, etc.

Instead, Stephen promoted this to "SHIP_STOPPER" this morning.

Call me shocked!

Actually SHIP_STOPPER- means: "Not a shipstopper".

http://en.opensuse.org/Bugs/Definitions#Ship_Stopper_Bugs

Ciao, Marcus

you just punctured my bubble. (crocodile tiers)

at least is hasn't been closed (yet) as being a new feature request
and more appropriate to openfate.

fyi: I have also made comments about overall repository management as
part of the zypper dup process in the big openfate discussion. I'm
hoping one of the two causes a process/tool/solution to be
implemented.

The current instructions simply say: "adapt repository list"

I don't think that is acceptable at all if zypper dup is supposed to
be a typical end-user upgrade path.

Greg
--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
Preservation and Forensic processing of Exchange Repositories White Paper -
<http://www.norcrossgroup.com/forms/whitepapers/tng_whitepaper_fpe.html>

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >