Mailinglist Archive: zypp-devel (59 mails)

[Jan Kupec <jkupec@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stanislav Visnovsky wrote:
> On Monday 24 November 2008 11:53:33 Jan Kupec wrote:
> > Michael Andres wrote:
> > > On Monday 24 November 2008 09:55:11 Jan Kupec wrote:
> > > > bugzilla_noreply@xxxxxxxxxx wrote:
> > > > > --- Comment #2 from Michael Andres <ma@xxxxxxxxxx>  2008-11-21 11:48:55
> > > > > MST ---
> > > > >
> > > > > The second one is not necessarily a bug, because the solver uses
> > > > > different policies in 'dup' and 'up'. I suppose this will confuse
> > > > > several people, as they don't know what's the command they want to use.
> > > > > And as the zypper output is not very versbose, it's not that obvious
> > > > > why those packages were not considered in 'dup'.
> > > > The question is what should zypper show to make it obvious. It would
> > > > need some additional info from the solver, currently it just gets which
> > > > packages are going to be installed and which removed - no hit why. Or is
> > > > there something more?
> > > No, it's about zypper displaying just the package names. It might become
> > > more obvious, if one sees more details about the packages changes.
> > sure, this is planned. I thought you have something else in mind - some
> > sort of explanations why some packages have or haven't been selected,
> > etc...
> >
> > >     foo (upgrade   2.1 -> 2.2)
> > >     baa (downgrade 1.1 -> 0.9, arch i386 -> x_86_64)
> > >     reh (reinstall 1.1 -> 1.1, vendor packman -> openSUSE)
> > >
> > > It might also be helpfull to display an abstract of the solver policies,
> > > so one recognizes the different rules active for 'up' and 'dup'
> > >
> > >     allowdowngrade    = 1
> > >     allowarchchange   = 1
> > >     allowvendorchange = 1
> > >     allowuninstall    = 0
> > >     ..
> > >
> > >
> > > If you now don't see 'reh' in 'zypper up', but see
> > >
> > >     allowvendorchange = 0
> > >
> > > you know why it's not there without need to file a bugreport.
> > Yes, this is a good idea.
>
> I think this will not work, because
>
> 1) nobody will notice the summary
> 2) those who notice will be confused what is the exact meaning
>
> Anyway, in verbose mode that might be helpful.

Of course, this is nothing for default output, but on demand.

- --
cheers,
jano


 Ján Kupec
 YaST team
- ---------------------------------------------------------(PGP)---
 Key ID: 637EE901
 Fingerprint: 93B9 C79B 2D20 51C3 800B  E09B 8048 46A6 637E E901
- -----------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkkqpfMACgkQgEhGpmN+6QHUXwCeLczMAoKTjxKSPjvLZOI6U2II
MA4AmwUmZgidMoQlJozAMveKBI0Z9IaN
=vOeK
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx