First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 110308
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 118874
Assigned To: Portage team <dev-portage@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Anders Storsveen <wakko@generation.no>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 110308 depends on: Show dependency tree
Show dependency graph
Bug 110308 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2005-10-24 03:50 0000 
It would be great to make --skipfirst take a number like --skipfirst 20, thats
fantastic for resuming stuff like emerge world -e, when something b0rks, and you
have to re-emerge something else first... emerge --skipfirst 25 world -e would
resume on the 26th package on the emerge! ;)

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From SpanKY 2005-10-24 20:11:48 0000 ------- 
sounds like a good idea ... sometimes i hit two/three broken packages that i
want to skip in a big world update ...

------- Comment #2 From Jason Stubbs (RETIRED) 2005-10-25 23:41:13 0000 ------- 
Isn't bug #12768 essentially what is required?

------- Comment #3 From Anders Storsveen 2005-10-26 00:22:36 0000 ------- 
this is just adding a number to skipfirst, so instead of just first it skips
the
first 20 or something.. Very useful if you're repairing a broken system with
emerge -e world, and something breaks and you have to fix something else, hence
resume is not an option. Then you can do emerge - world --skipfirst 60 and
start
at the 60th pkg.

------- Comment #4 From Jason Stubbs (RETIRED) 2005-10-26 06:12:15 0000 ------- 
This could only ever be a short-term "fix" though. The package order which is 
gleaned from the tree which is currently being stored is going to be replaced 
by storing the tree itself. Hence, skipping x number of packages will no 
longer make sense. If fixing bug #12768 will solve your problem, it'd be 
better to wait for that than to add functionality which has a short life span.

------- Comment #5 From Simon Stelling (RETIRED) 2006-04-15 07:43:14 0000 ------- 
Think what is really wanted here is what is described in bug 118874:
--start-from=XXX. That way you don't have to count how many packages you want
to skip ;)

*** This bug has been marked as a duplicate of 118874 ***
First Last Prev Next    No search results available      Search page      Enter new bug