Re: [gentoo-dev] Re: Re: Masking practics

2006-08-07 Thread Enrico Weigelt

big_snip /

My problem still seems unsolved (or did I miss something) ?

Lets say, if I've, installed foo-1.1, and it gets masked due
some bug(s), but 1.0 isn't, I want to get informed with an big
fat warning, *before* anything actually done, ie. 

[...]
# WARNING: installed package foo-1.1 has been masked and would
# be downgraded:
# masking comment ...
[...]

An fully-automatic downgrade should *never* downgrade anything. 
This is too dangerous, because essential features can get lost.
Again, my bugzilla example: assuming 2.22 will be unmasked some
day and I installed it w/ postgres support. Now there are some 
bugs found, but not fixed fast enough, so it gets masked. 
I run an update w/o knowing that it downgrades, and my whole
bugzilla hosting is suddenly broken.

Do you consider this as stability, seriously ?!


cu
-- 
-
 Enrico Weigelt==   metux IT service - http://www.metux.de/
-
 Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
-
-- 
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] Re: Re: Masking practics

2006-08-07 Thread Edward Catmur
On Mon, 2006-08-07 at 15:01 +0200, Enrico Weigelt wrote:
 Lets say, if I've, installed foo-1.1, and it gets masked due
 some bug(s), but 1.0 isn't, I want to get informed with an big
 fat warning, *before* anything actually done, ie. 
 
 [...]
 # WARNING: installed package foo-1.1 has been masked and would
 # be downgraded:
 # masking comment ...
 [...]
 
 An fully-automatic downgrade should *never* downgrade anything. 
 This is too dangerous, because essential features can get lost.
 Again, my bugzilla example: assuming 2.22 will be unmasked some
 day and I installed it w/ postgres support. Now there are some 
 bugs found, but not fixed fast enough, so it gets masked. 
 I run an update w/o knowing that it downgrades, and my whole
 bugzilla hosting is suddenly broken.

That would not happen. bugzilla is a webapp and as such is fully
SLOTted. Upgrades (and downgrades) are manual.

Ed

-- 
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] Re: Re: Masking practics

2006-08-07 Thread Simon Stelling

Enrico Weigelt wrote:

big_snip /

My problem still seems unsolved (or did I miss something) ?

Lets say, if I've, installed foo-1.1, and it gets masked due
some bug(s), but 1.0 isn't, I want to get informed with an big
fat warning, *before* anything actually done, ie. 


[...]
# WARNING: installed package foo-1.1 has been masked and would
# be downgraded:
# masking comment ...
[...]

An fully-automatic downgrade should *never* downgrade anything. 
This is too dangerous, because essential features can get lost.

Again, my bugzilla example: assuming 2.22 will be unmasked some
day and I installed it w/ postgres support. Now there are some 
bugs found, but not fixed fast enough, so it gets masked. 
I run an update w/o knowing that it downgrades, and my whole

bugzilla hosting is suddenly broken.

Do you consider this as stability, seriously ?!


If your bugzilla hosting breaks with lower versions, then the ebuild contains a 
RDEPEND=postgres? ( =dev-db/postgresql-2.22 ). Now if =postgresql-2.22 gets 
masked, portage will bail out with an error because it can't find a valid 
dependency tree. This will cause the comment above the masking line in p.mask to 
be shown. You can then decide whether the breakage affects you or not and 
depending on that unmask it locally or remove your bugzilla installation.


If there is a bugzilla-ebuild which works with postgresql-2.22, it will be 
downgraded too, leaving you with a working bugzilla.


I can't quite see the massive problem.

--
Kind Regards,

Simon Stelling
Gentoo/AMD64 Developer
--
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] Re: Re: Masking practics

2006-08-07 Thread Alec Warner
Enrico Weigelt wrote:
 big_snip /
 
 My problem still seems unsolved (or did I miss something) ?
 
 Lets say, if I've, installed foo-1.1, and it gets masked due
 some bug(s), but 1.0 isn't, I want to get informed with an big
 fat warning, *before* anything actually done, ie. 
 
 [...]
 # WARNING: installed package foo-1.1 has been masked and would
 # be downgraded:
 # masking comment ...
 [...]
 
 An fully-automatic downgrade should *never* downgrade anything. 
 This is too dangerous, because essential features can get lost.
 Again, my bugzilla example: assuming 2.22 will be unmasked some
 day and I installed it w/ postgres support. Now there are some 
 bugs found, but not fixed fast enough, so it gets masked. 
 I run an update w/o knowing that it downgrades, and my whole
 bugzilla hosting is suddenly broken.
 
 Do you consider this as stability, seriously ?!
 

I would call you a horrible administrator since this:
I run an update w/o knowing that it downgrades
should NEVER happen.

emerge -pv foo
[ebuild UD] cat/foo-currentversion [downgraded-version] stuff

-- 
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] Re: Re: Masking practics

2006-08-07 Thread Enrico Weigelt
* Alec Warner [EMAIL PROTECTED] schrieb:

snip

 I would call you a horrible administrator since this:
 I run an update w/o knowing that it downgrades
 should NEVER happen.
 
 emerge -pv foo
 [ebuild UD] cat/foo-currentversion [downgraded-version] stuff

Great. I have to explicitly compare the versions on each package.

Not actually an great help.


cu
-- 
-
 Enrico Weigelt==   metux IT service - http://www.metux.de/
-
 Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
 Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
-
-- 
gentoo-dev@gentoo.org mailing list



Re: [gentoo-dev] Re: Re: Masking practics

2006-08-07 Thread Alexandre Buisse
On Mon, Aug  7, 2006 at 22:18:35 +0200, Enrico Weigelt wrote:

 * Alec Warner [EMAIL PROTECTED] schrieb:
 
 snip
 
  I would call you a horrible administrator since this:
  I run an update w/o knowing that it downgrades
  should NEVER happen.
  
  emerge -pv foo
  [ebuild UD] cat/foo-currentversion [downgraded-version] stuff
 
 Great. I have to explicitly compare the versions on each package.

And what about the big blue 'D'?

/Alexandre
-- 
Hi, I'm a .signature virus! Please copy me in your ~/.signature.


pgpgSBn4Uv7SJ.pgp
Description: PGP signature


[gentoo-dev] Re: Re: Masking practics

2006-08-04 Thread Duncan
Jakub Moc [EMAIL PROTECTED] posted [EMAIL PROTECTED], excerpted
below, on  Thu, 03 Aug 2006 22:32:57 +0200:

 Alec Warner wrote:
 Enrico Weigelt wrote:
 * Duncan schrieb:

 How can it be too late?  You sync during that 30 days it's masked, do
 an emerge --pretend --update world, and see that it's going to
 downgrade.
 How do I see it (without actually having the version numbers in mind?)

 Why I need is simply an command line, which just tells me, which
 packages are now re-masked and which ones are scheduled for removal.
 
 Erm, am I missing something?
 
 # emerge -uDpv world
 
 !!! Ebuilds for the following packages are either all !!! masked or don't
 exist:
 media-libs/tunepimp

Exactly, altho I did make the slight mistake of saying downgrade, when we
are talking removing from the tree so it would be (as above) all masked,
not just a downgrade.  With all versions masked, the warning is more
verbose than simply a downgrade, including a mention of why (in this case
package.mask, with the package.mask entry and associated comment, with
portage 2.1.1-preX anyway).

quote
!!! All ebuilds that could satisfy tunepimp have been masked.
!!! One of the following masked packages is required to complete your request:
- media-libs/tunepimp-0.4.2 (masked by: package.mask)
# Diego Pettenò [EMAIL PROTECTED] (24 Jul 2006)
# TunePimp has security problems (#140184) and isn't API stable yet
# scheduled for removal.

- media-libs/tunepimp-0.3.0 (masked by: package.mask)
- media-libs/tunepimp-0.4.0 (masked by: package.mask)
- media-libs/tunepimp-0.3.0-r1 (masked by: package.mask)

For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.
/quote

So it tells you exactly which packages are available but masked, that
they're masked and by what (package.mask), and what the comment masking
them is -- scheduled for removal due to security bugs, with a bug number.

That seems like all the necessary info to me, including a bug to look up
for more information, if desired.  The scheduled for removal certainly
suggests to me that if I want to keep it, I better put it in my overlay
/now/.

-- 
Duncan - List replies preferred.   No HTML msgs.
Every nonfree program has a lord, a master --
and if you use the program, he is your master.  Richard Stallman

-- 
gentoo-dev@gentoo.org mailing list