| View previous topic :: View next topic |
| Author |
Message |
cazort
Guru
Joined: 19 Sep 2004
Posts: 343
Location: Lancaster, PA
|
 Posted: Tue Dec 09, 2008 6:46 pm Post subject: |
 |
|
| Quote: | Do either of those files exist:
| Code: | ls -al /usr/bin/mktemp
ls -al /bin/mktemp |
They should both be there. Obviously one is a symlink to the oth
|
The actual executable was gone. I got it fixed...not sure how though...I re-emerged coreutils several times and maybe did something else, I forget, and it worked.
Annoying. This is the second time I've had a package that is SUPPOSED to install a certain file not install it...the last time was apache...didn't install /etc/apache2/httpd.conf.
_________________
Alex Zorach | Teacology | RateTea | Why This Way |
|
| Back to top |
|
 |
RLVampire
n00b
Joined: 25 Oct 2007
Posts: 9
|
| Posted: Mon Dec 22, 2008 5:48 am Post subject: |
|
|
This works as intended on my bleeding box and I did exactly as quoted and its fixed.  |
|
| Back to top |
|
|
hydrapolic
Tux's lil' helper
Joined: 07 Feb 2008
Posts: 126
|
| Posted: Tue Dec 30, 2008 6:41 am Post subject: |
|
|
Hello, I know this has been asked 100x times before, I've just seen more solutions so I ask. After updating portage today, it shows that:
[ebuild N ] sys-libs/e2fsprogs-libs-1.41.3 USE="nls"
[ebuild U ] sys-fs/e2fsprogs-1.41.3 [1.40.9]
[blocks b ] <sys-fs/e2fsprogs-1.41 ("<sys-fs/e2fsprogs-1.41" is blocking sys-libs/e2fsprogs-libs-1.41.3)
[uninstall ] sys-libs/com_err-1.40.9
[blocks b ] sys-libs/com_err ("sys-libs/com_err" is blocking sys-libs/e2fsprogs-libs-1.41.3)
[uninstall ] sys-libs/ss-1.40.9
[blocks b ] sys-libs/e2fsprogs-libs ("sys-libs/e2fsprogs-libs" is blocking sys-libs/ss-1.40.9, sys-libs/com_err-1.40.9)
[blocks b ] sys-libs/ss ("sys-libs/ss" is blocking sys-libs/e2fsprogs-libs-1.41.3)
If I do NOT have kerberos installed, neither the krb flag enabled in /etc/make.conf, is it safe to:
# emerge -f e2fsprogs e2fsprogs-libs
# emerge --unmerge ss com_err e2fsprogs
# emerge e2fsprogs e2fsprogs-libs
Thanks in advance. |
|
| Back to top |
|
|
richard.scott
Veteran
Joined: 19 May 2003
Posts: 1497
Location: Oxfordshire, UK
|
| Posted: Tue Dec 30, 2008 10:29 am Post subject: |
|
|
It used to be kerberos on my system that was pulling in the incorrect versions of com_err and ss etc instead of e2fsprogs.
Aslong as the rest of your system is up to date you should be ok with ignoring the kerberos part. |
|
| Back to top |
|
|
radio_flyer
Guru
Joined: 04 Nov 2004
Posts: 317
Location: Northern California
|
| Posted: Tue Dec 30, 2008 6:38 pm Post subject: |
|
|
Well, I have a question that is somewhat related to this thread (I think). I'm running x86, and I've had the kerberos USE flag disabled in make.conf for a long time (it never caused anything but trouble for me). Hence, I haven't had the com_err or ss package mess, and e2fsprogs-libs installed cleanly. So I've missed this whole imbroglio with the blockers, etc.
However, today, after my normal sequence of 'emerge --sync' 'emerge -UDpv world' 'emerge -uDf world' 'emerge -uDv world' 'emerge -uDNpv world' 'emerge -uDNv world' (yes, I've learned caution over the years with Gentoo), I now get this:
| Code: |
# emerge --depclean --pretend
* [snip blah blah]
Calculating dependencies... done!
>>> These are the packages that would be unmerged:
sys-fs/e2fsprogs
selected: 1.41.3
protected: none
omitted: none
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
Packages installed: 1231
Packages in world: 268
Packages in system: 50
Required packages: 1230
Number to remove: 1
|
I notice in /usr/lib/portage/base/profiles/packages that e2fsprogs has now been commented out (hence the reason for the --depclean output above.) Everything I've seen in portage so far has folks running 'emerge e2fsprogs' as part of the blockage fix, which obviously has the side effect of putting e2fsprogs in /var/lib/portage/world.
So, obviously, I'm not going to unmerge e2fsprogs until I sort out a few questions here:
- Is there a reason why e2fsprogs is no longer a base package?
- Is it safe to let it --unmerge because it's functionality is handled elsewhere, or is it necessary to run 'emerge --no-replace e2fsprogs' to lock this thing down?
If this is a different problem, or there's another thread discussing this issue, please point me to it. Thanks!
*UPDATE*: looks like this is a hot-off-the-press bug; see https://bugs.gentoo.org/show_bug.cgi?id=249663
I hope another round of dependency madness isn't about to begin... |
|
| Back to top |
|
|
Captain Newbie
Apprentice
Joined: 22 Dec 2006
Posts: 182
Location: Socal
|
| Posted: Tue Dec 30, 2008 8:30 pm Post subject: |
|
|
Oh brother, here we go 
If you happen to have genkernel installed (yeah, I'm lame, I know flames>/dev/null), you won't see this as Genkernel depends on e2fsprogs...for what that's worth.
At least as far as I can tell, e2fsprogs is necessary for boot, as it includes /sbin/fsck. I'm not willing to find out myself. Those who are unfortunate enough to blindly accept the actions of --depclean may render their systems unbootable.
_________________
/* Nobody will ever see this message  */
panic("Cannot initialize video hardware\n");
"As much as it pains me, we hope that developers know what they're doing." - wolf31o2 |
|
| Back to top |
|
|
richard.scott
Veteran
Joined: 19 May 2003
Posts: 1497
Location: Oxfordshire, UK
|
| Posted: Tue Dec 30, 2008 11:54 pm Post subject: |
|
|
I've just emerge --sync'd on the system that I started this thread about and I don't have genkernel installed as its a Xen guest OS.
I also don't have any dependency on e2fsprogs:
| Code: | # equery depends sys-fs/e2fsprogs
[ Searching for packages depending on sys-fs/e2fsprogs... ]
# |
yet I also don't have the emerge --depclean selecting e2fsprogs for removal? 
Is this something specific to the profile your using?
Oh, and I can't find /usr/lib/portage/base/profiles/packages either!  |
|
| Back to top |
|
|
hydrapolic
Tux's lil' helper
Joined: 07 Feb 2008
Posts: 126
|
| Posted: Wed Dec 31, 2008 11:22 am Post subject: |
|
|
@richard.scott
seems util-linux is also involved:
| Code: |
[ebuild NS ] sys-kernel/gentoo-sources-2.6.27-r7 [2.6.24-r8] USE="symlink -build"
[ebuild U ] sys-boot/grub-0.97-r6 [0.97-r5]
[ebuild U ] sys-kernel/genkernel-3.4.10-r2 [3.4.9] USE="bash-completion*"
[ebuild N ] sys-libs/e2fsprogs-libs-1.41.3-r1 USE="nls"
[ebuild U ] sys-fs/e2fsprogs-1.41.3 [1.40.9]
[blocks b ] <sys-fs/e2fsprogs-1.41 ("<sys-fs/e2fsprogs-1.41" is blocking sys-libs/e2fsprogs-libs-1.41.3-r1)
[ebuild U ] sys-apps/util-linux-2.14.1 [2.13.1.1] USE="(-uclibc)"
[uninstall ] sys-libs/com_err-1.40.9
[blocks b ] sys-libs/com_err ("sys-libs/com_err" is blocking sys-libs/e2fsprogs-libs-1.41.3-r1)
[uninstall ] sys-libs/ss-1.40.9
[blocks b ] sys-libs/e2fsprogs-libs ("sys-libs/e2fsprogs-libs" is blocking sys-libs/ss-1.40.9, sys-libs/com_err-1.40.9)
[blocks b ] sys-libs/ss ("sys-libs/ss" is blocking sys-libs/e2fsprogs-libs-1.41.3-r1)
|
I suppose I will wait a little bit more to sort the things out. Hopefully I will be able to fix it later. |
|
| Back to top |
|
|
richard.scott
Veteran
Joined: 19 May 2003
Posts: 1497
Location: Oxfordshire, UK
|
| Posted: Wed Dec 31, 2008 11:38 am Post subject: |
|
|
| hydrapolic wrote: | | seems util-linux is also involved... |
You need to upgrade util-linux first and then you can resolve the other blockers. |
|
| Back to top |
|
|
hydrapolic
Tux's lil' helper
Joined: 07 Feb 2008
Posts: 126
|
| Posted: Wed Dec 31, 2008 11:50 am Post subject: |
|
|
I would gladly, however...
| Code: |
# emerge -pv util-linux
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N ] sys-libs/e2fsprogs-libs-1.41.3-r1 USE="nls" 0 kB
[ebuild U ] sys-apps/util-linux-2.14.1 [2.13.1.1] USE="crypt nls unicode -loop-aes -old-linux (-selinux) -slang (-uclibc)" 0 kB
[blocks B ] sys-libs/com_err ("sys-libs/com_err" is blocking sys-libs/e2fsprogs-libs-1.41.3-r1)
[blocks B ] sys-libs/ss ("sys-libs/ss" is blocking sys-libs/e2fsprogs-libs-1.41.3-r1)
[blocks B ] <sys-fs/e2fsprogs-1.41 ("<sys-fs/e2fsprogs-1.41" is blocking sys-libs/e2fsprogs-libs-1.41.3-r1)
[blocks B ] sys-libs/e2fsprogs-libs ("sys-libs/e2fsprogs-libs" is blocking sys-libs/ss-1.40.9, sys-libs/com_err-1.40.9)
Total: 2 packages (1 upgrade, 1 new), Size of downloads: 0 kB
Conflict: 4 blocks (4 unsatisfied)
|
|
|
| Back to top |
|
|
richard.scott
Veteran
Joined: 19 May 2003
Posts: 1497
Location: Oxfordshire, UK
|
| Posted: Wed Dec 31, 2008 12:54 pm Post subject: |
|
|
In that case then you need to fix the e2fsprogs blockers first.
Waiting won't help as com_err and ss are no longer required anymore and need to be removed by resolving the blockers in the correct way.
This then replaces them with the e2fsprogs and e2fsprogs-libs.
You should then be able to upgrade other things after that. |
|
| Back to top |
|
|
hydrapolic
Tux's lil' helper
Joined: 07 Feb 2008
Posts: 126
|
| Posted: Wed Dec 31, 2008 4:21 pm Post subject: |
|
|
Is it possible to test the compilation process of e2fsprogs and libs ? I have seen people having trouble compiling it, tried:
ROOT="/tmp/efstest" emerge -p e2fsprogs
But I got the nasty warning about the blocking  |
|
| Back to top |
|
|
Captain Newbie
Apprentice
Joined: 22 Dec 2006
Posts: 182
Location: Socal
|
| Posted: Wed Dec 31, 2008 4:57 pm Post subject: |
|
|
| richard.scott wrote: | yet I also don't have the emerge --depclean selecting e2fsprogs for removal?
Is this something specific to the profile your using? |
It's possible that something's already been done to eliminate this problem...indeed, changes that were described in the bug have been synced to me this morning.
By the way, Portage 2.1.6.4 is very sexy, and outright removes the need for this thread.
_________________
/* Nobody will ever see this message */
panic("Cannot initialize video hardware\n");
"As much as it pains me, we hope that developers know what they're doing." - wolf31o2 |
|
| Back to top |
|
|
richard.scott
Veteran
Joined: 19 May 2003
Posts: 1497
Location: Oxfordshire, UK
|
| Posted: Wed Dec 31, 2008 5:07 pm Post subject: |
|
|
| hydrapolic wrote: | Is it possible to test the compilation process of e2fsprogs and libs ? I have seen people having trouble compiling it, tried:
ROOT="/tmp/efstest" emerge -p e2fsprogs
But I got the nasty warning about the blocking |
I don't think its possible to test the build. Just remember to "emerge -f" before you start.
From what I've seen most people who had trouble compiling it forgot to emerge -f the packages before building them.
If you forget this then wget breaks and you can't download anything to fix your system.
That's why the emerge -f line in my first post on this thread is so important!
Rich. |
|
| Back to top |
|
|
tp11235
n00b
Joined: 22 Aug 2006
Posts: 35
Location: England
|
| Posted: Thu Jan 01, 2009 11:31 am Post subject: Worked out of the box for me. |
|
|
| Thanks Richard.javascript:emoticon('') |
|
| Back to top |
|
|
chrisstankevitz
Guru
Joined: 14 Dec 2003
Posts: 472
Location: Santa Barbara, CA, USA
|
| Posted: Fri Jan 02, 2009 12:47 am Post subject: |
|
|
Question: Where do I go for the official gentoo method of dealing with the e2fsprogs block?
Answer:
a) go to http://www.gentoo.org/blockers/e2fsprogs.html
b) gentoo does not have an official method to deal with this block. Read this thread and come to your own conclusion
c) these sticky threads need to be made read-only so that there is one clear method for dealing with this.
d) [Your answer here]
Thanks,
Chris |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Fri Jan 02, 2009 3:23 am Post subject: |
|
|
| chrisstankevitz wrote: | | Question: Where do I go for the official gentoo method of dealing with the e2fsprogs block? |
Does there need to be an official method of working around every problem?
Potentially useful, but subject to scaling issues, both in breadth of coverage and in duration.
| chrisstankevitz wrote: | | b) gentoo does not have an official method to deal with this block. Read this thread and come to your own conclusion |
Not having a single official upgrade path designated is the common case for package blocks, while in this case there is a fairly simple solution that is not a feature of all, or even necessarily most, blocks.
| chrisstankevitz wrote: | | c) these sticky threads need to be made read-only so that there is one clear method for dealing with this. |
Unworkable due to the likelihood of there not being a single panacea for all possible variations.
| chrisstankevitz wrote: | | d) [Your answer here] |
Upgrade to the 2.1.6 or the, presently masked, 2.2 series of sys-apps/portage, let it resolve this block automatically. |
|
| Back to top |
|
|
chrisstankevitz
Guru
Joined: 14 Dec 2003
Posts: 472
Location: Santa Barbara, CA, USA
|
| Posted: Fri Jan 02, 2009 4:13 am Post subject: |
|
|
| . |
|
| Back to top |
|
|
Captain Newbie
Apprentice
Joined: 22 Dec 2006
Posts: 182
Location: Socal
|
| Posted: Fri Jan 02, 2009 4:32 am Post subject: |
|
|
| chrisstankevitz wrote: | | snip |
| Code: | emerge --oneshot --update portage
emerge --fetchonly --update --deep --newuse world
# The above is merely precautionary to ensure wget doesn't break
emerge --update --deep --newuse world |
_________________
/* Nobody will ever see this message */
panic("Cannot initialize video hardware\n");
"As much as it pains me, we hope that developers know what they're doing." - wolf31o2 |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Fri Jan 02, 2009 4:32 am Post subject: |
|
|
| chrisstankevitz wrote: | | Don't you think the current system is subject to scaling problems? Everyone logon to forums.gentoo.org ask for help. |
Ideally, everyone would search first. Bear in mind that in order to catch every block that any user would consider to be a major problem all blocks would need to be documented and there are multiple ways to resolve most blocks, ranging from obvious upgrade paths through to switching to different packages entirely, on the whole such things tend to be better handled through mechanisms such as the forums or mailing lists than trying to develop such documentation beforehand.
| chrisstankevitz wrote: | | Isn't that worth at least a mention in the gentoo newsletter or a simple guide. |
As ever, submissions to the newsletter are actively solicited, and the first post in this topic provides a simple, if not necessarily exhaustively documented, guide.
| chrisstankevitz wrote: | | I personally think it is -- but I'm not an OS developer, I'm just a dumb user who screwed his system up by following some idiot's instructions on forums.gentoo.org. |
At which point you should post describing how your system is behaving and requesting help fixing it, your experience can help other users, solutions even more so. |
|
| Back to top |
|
|
hydrapolic
Tux's lil' helper
Joined: 07 Feb 2008
Posts: 126
|
| Posted: Fri Jan 02, 2009 4:55 pm Post subject: |
|
|
| I managed to fix the problem by the steps provided in the topic head, special thanks to richard.scott for the help. |
|
| Back to top |
|
|
chrisstankevitz
Guru
Joined: 14 Dec 2003
Posts: 472
Location: Santa Barbara, CA, USA
|
| Posted: Fri Jan 02, 2009 11:59 pm Post subject: |
|
|
| desultory wrote: | | As ever, submissions to the newsletter are actively solicited |
Here's my submission:
| Quote: |
If you get a blocker on e2fsprogs, take these steps:
1. search forums.gentoo.org and read the 50 pages of posts about this problem.
2. If you still don't know how to fix it, ask on the forums.
3. When/if you solve the problem, post to the forums and let people know how you fixed it
4. If you hose your system following some bad advice, goto 1.
|
On a more serious note, what is the real reason the gentoo newsletter has been silent on this issue?
a) fix is obvious
b) no big deal if someone breaks wget
c) fix is complicated - impractical to post instructions
d) newsletter is not for wget-hosing-blockers
e) newsletter understaffed - e2fsprogs didn't make the cut
f) [your answer here]
And some good news on this issue: January 2, 2009 -- fix this problem by following these steps:
| Code: | emerge --sync
emerge portage
emerge -Dauv world |
Nowadays a simple portage update fixes the e2fsprogs blocker problem! Fantastic!
Chris |
|
| Back to top |
|
|
Captain Newbie
Apprentice
Joined: 22 Dec 2006
Posts: 182
Location: Socal
|
| Posted: Sat Jan 03, 2009 12:36 am Post subject: |
|
|
| chrisstankevitz wrote: | On a more serious note, what is the real reason the gentoo newsletter has been silent on this issue?
a) fix is obvious
b) no big deal if someone breaks wget
c) fix is complicated - impractical to post instructions
d) newsletter is not for wget-hosing-blockers
e) newsletter understaffed - e2fsprogs didn't make the cut
f) [your answer here] |
(f) Notifications for this sort of thing will probably be made through GLEP 42-like procedures in the future.
_________________
/* Nobody will ever see this message */
panic("Cannot initialize video hardware\n");
"As much as it pains me, we hope that developers know what they're doing." - wolf31o2 |
|
| Back to top |
|
|
desultory
Bodhisattva
Joined: 04 Nov 2005
Posts: 9410
|
| Posted: Sat Jan 03, 2009 12:52 am Post subject: |
|
|
| chrisstankevitz wrote: | | On a more serious note, what is the real reason the gentoo newsletter has been silent on this issue? |
As you did not specify the desired format, I will address this as multiple choice pick all that apply, with the last option being short form essay, I will give a brief explanation of my answer for each.
| chrisstankevitz wrote: | | a) the fix is obvious |
Yes. Especially given a current version of sys-apps/portage, including versions which have been available since before these blocks were put in place, even before that the fix was not difficult.
| chrisstankevitz wrote: | | b) no big deal if someone breaks wget |
No. Though avoiding that problem it not difficult.
| chrisstankevitz wrote: | | c) fix is different for everyone - impractical to post instructions |
No. Though there are at least theoretical cases were different solutions may be preferable.
| chrisstankevitz wrote: | | d) newsletter is not for system-hosing-blocker fixes |
No. The main problem here is that it is a monthly publication as such, in general, providing proactive documentation is more difficult and providing reactive documentation is less useful.
| chrisstankevitz wrote: | | e) newsletter understaffed - e2fsprogs didn't make the cut |
Yes. The newsletter could use more staff, though I have not found any indication that any guide regarding these blocks was submitted.
| chrisstankevitz wrote: | | f) [your answer here] |
With the stabilization of the 2.1.6 series GLEP 42 news items can now be used to document cases where manual intervention will be required by administrators while simultaneously reducing the incidence of such intervention. |
|
| Back to top |
|
|
hydrapolic
Tux's lil' helper
Joined: 07 Feb 2008
Posts: 126
|
| Posted: Sat Jan 03, 2009 10:46 am Post subject: |
|
|
| What about /usr/portage/UPDATING (as in FreeBSD) ? |
|
| Back to top |
|
|
|
Portage & Programming
