Re: [gentoo-user] USB crucial file recovery
On Monday 29 Aug 2016 17:51:19 Grant wrote: > > I have a USB stick with a crucial file on it (and only an old backup > > elsewhere). It's formatted NTFS because I wanted to be able to open > > the file on various Gentoo systems and my research indicated that > >>> > >>>NTFS > >>> > > was the best solution. > > > > I decided to copy a 10GB file from a USB hard disk directly to the > >>> > >>>USB > >>> > > stick this morning and I ran into errors so I canceled the operation > > and now the file manager (thunar) has been stuck for well over an > >>> > >>>hour > >>> > > and I'm getting errors like these over and over: > > > > [ 2794.535814] Buffer I/O error on dev sdc1, logical block 2134893, > > lost async page write > > [ 2794.535819] Buffer I/O error on dev sdc1, logical block 2134894, > > lost async page write > > [ 2794.535822] Buffer I/O error on dev sdc1, logical block 2134895, > > lost async page write > > [ 2794.535824] Buffer I/O error on dev sdc1, logical block 2134896, > > lost async page write > > [ 2794.535826] Buffer I/O error on dev sdc1, logical block 2134897, > > lost async page write > > [ 2794.535828] Buffer I/O error on dev sdc1, logical block 2134898, > > lost async page write > > [ 2794.535830] Buffer I/O error on dev sdc1, logical block 2134899, > > lost async page write > > [ 2794.535832] Buffer I/O error on dev sdc1, logical block 2134900, > > lost async page write > > [ 2794.535835] Buffer I/O error on dev sdc1, logical block 2134901, > > lost async page write > > [ 2794.535837] Buffer I/O error on dev sdc1, logical block 2134902, > > lost async page write > > [ 2842.568843] sd 9:0:0:0: [sdc] tag#0 FAILED Result: > > hostbyte=DID_ERROR driverbyte=DRIVER_SENSE > > [ 2842.568849] sd 9:0:0:0: [sdc] tag#0 Sense Key : Hardware Error > >>> > >>>[current] > >>> > > [ 2842.568852] sd 9:0:0:0: [sdc] tag#0 Add. Sense: No additional > >>> > >>>sense > >>> > > information > > [ 2842.568857] sd 9:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 04 a4 > > 58 00 00 f0 00 > > [ 2842.568859] blk_update_request: I/O error, dev sdc, sector > >>> > >>>17081432 > >>> > > [ 2842.568862] buffer_io_error: 20 callbacks suppressed > > > > nmon says sdc is 100% busy but doesn't show any reading or writing. > >>> > >>>I > >>> > > once pulled the USB stick in a situation like this and I ended up > > having to reformat it which I need to avoid this time since the file > > is crucial. What should I do? > > > > - Grant > > Whatever you do, do NOT try to unplug the USB you were writing to > >>> > >>>unless you > >>> > first manage to successfully unmount it. If you do pull the USB > >>> > >>>stick > >>> > regardless of its current I/O state you will likely corrupt whatever > >>> > >>>file you > >>> > were writing onto, or potentially more. > > You could well have a hardware failure here, which manifested itself > >>> > >>>during > >>> > your copying operation. Things you could try: > > Run lsof to find out which process is trying to access the USB fs and > >>> > >>>kill it. > >>> > Then see if you can remount it read-only. > > Run dd, dcfldd, ddrescue to make an image of the complete USB stick > >>> > >>>on your > >>> > hard drive and then try to recover any lost files with testdisk. > > Use any low level recovery tools the manufacturer may offer - they > >>> > >>>will likely > >>> > require MSWindows. > > Shut down your OS and disconnect the USB stick, then reboot and try > >>> > >>>again to > >>> > access it, although I would first create an image of the device using > >>> > >>>any of > >>> > the above tools. > >>> > >>>dd errored and lsof returned no output at all so I tried to reboot but > >>>even that hung after the first 2 lines of output so I did a hard reset > >>>after waiting an hour or so. Once it came back up I tried to do 'dd > >>>if=/dev/sdb1 of=usbstick' but I got this after awhile: > >>> > >>>dd: error reading ‘/dev/sdb1’: Input/output error > >>>16937216+0 records in > >>>16937216+0 records out > >>>8671854592 bytes (8.7 GB) copied, 230.107 s, 37.7 MB/s > >>> > >>>It's a 64GB USB stick. dmesg says: > >>> > >>>[ 744.729873] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK > >>>driverbyte=DRIVER_SENSE > >>>[ 744.729879] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error > >>>[current] > >>>[ 744.729883] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read > >>>error > >>>[ 744.729886] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 78 e0 > >>>00 00 f0 00 > >>>[ 744.729889] blk_update_request: critical medium error, dev sdb, > >>>sector 16939232 > >>>[ 744.763468] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK > >>>driverbyte=DRIVER_SENSE > >>>[ 744.763472] sd 8:0:0:0: [sdb] tag#0 Sense
Re: [gentoo-user] Shutter alternatives
meino.cra...@gmx.de wrote: > Jean-Christophe Bach[16-08-27 12:00]: >> Hello, >> >>> I am looking for an alternative for shutter, which has been >>> removed from portage which is not shutterbug (see me initial posting). >>> >>> So neither shutter nor shutterbug is an alternative to shutter. >>> >>> What else can I use instead. >> >> I am using media-gfx/scrot, a very simple screenshot program. >> >> JC > > Hi Bill, hi Jean-Christophe, > > GREAT! Thanks for the input...will take scrot but only for that > reason, that I have no XFCE installed and dont want install > the dependencies. > If dumping a single X window is sufficient there is also x11-apps/xwd, which I use together with convert from imagemagik: $ /usr/bin/xwd | convert - screenshot.png raffaele
Re: [gentoo-user] USB crucial file recovery
2016-08-30 5:51 GMT+05:00 Grant: > Ah, I got it, I just needed to specify the offset when mounting. > Thank you so much everyone. Many hours of work went into the file I > just recovered. > > So I'm done with NTFS forever. Will ext2 somehow allow me to use the > USB stick across Gentoo systems without permission/ownership problems? > > - Grant > > I would recommend to use F2FS filesystem, since you have only Linux systems. -- >From Siberia with Love!
Re: [gentoo-user] guvcview update produces an executable with missing lib...
Daniel Frey[16-08-30 03:48]: > On 08/29/2016 11:11 AM, waltd...@waltdnes.org wrote: > > On Mon, Aug 29, 2016 at 06:29:50PM +0200, meino.cra...@gmx.de wrote > >> Hi, > >> > >> after updateing my system, beside others guvcview was updated: > >> > >> from qlop > >> Mon Aug 29 17:44:08 2016 >>> media-video/guvcview-2.0.4 > >> > >> After ldconfig as root and rehash (zsh) as user I got: > >> > >> /home/user>guvcview > >> guvcview: error while loading shared libraries: libgviewv4l2core-1.0.so.1: > >> cannot open shared object file: No such file or directory > >> [1]23848 exit 127 guvcview > >> > >> > >> ...h. > >> > >> What did I wrong? > >> > >> Best regards, > >> mcc > > > > The first suggestion in a case like this is to run revdep-rebuild. As > > a matter of fact, it probably wouldn't hurt to run revdep-rebuild after > > every update. > > > > Yes, I do. Portage occasionally misses a rebuild. It's a lot better now > at catching them but it still misses them. > > > > Dan > Ok, we now know that depclean and redep rebuild are needed after each update. It is someting, which I put together into one script which I run after each update. And we know that portage seems to be guilty. And that it should not be guilty. And that it does better in this cases. One thing remains: How can I get that guvcview up and running? Best regards, Meino
Re: [gentoo-user] USB crucial file recovery
> I have a USB stick with a crucial file on it (and only an old backup > elsewhere). It's formatted NTFS because I wanted to be able to open > the file on various Gentoo systems and my research indicated that >>>NTFS > was the best solution. > > I decided to copy a 10GB file from a USB hard disk directly to the >>>USB > stick this morning and I ran into errors so I canceled the operation > and now the file manager (thunar) has been stuck for well over an >>>hour > and I'm getting errors like these over and over: > > [ 2794.535814] Buffer I/O error on dev sdc1, logical block 2134893, > lost async page write > [ 2794.535819] Buffer I/O error on dev sdc1, logical block 2134894, > lost async page write > [ 2794.535822] Buffer I/O error on dev sdc1, logical block 2134895, > lost async page write > [ 2794.535824] Buffer I/O error on dev sdc1, logical block 2134896, > lost async page write > [ 2794.535826] Buffer I/O error on dev sdc1, logical block 2134897, > lost async page write > [ 2794.535828] Buffer I/O error on dev sdc1, logical block 2134898, > lost async page write > [ 2794.535830] Buffer I/O error on dev sdc1, logical block 2134899, > lost async page write > [ 2794.535832] Buffer I/O error on dev sdc1, logical block 2134900, > lost async page write > [ 2794.535835] Buffer I/O error on dev sdc1, logical block 2134901, > lost async page write > [ 2794.535837] Buffer I/O error on dev sdc1, logical block 2134902, > lost async page write > [ 2842.568843] sd 9:0:0:0: [sdc] tag#0 FAILED Result: > hostbyte=DID_ERROR driverbyte=DRIVER_SENSE > [ 2842.568849] sd 9:0:0:0: [sdc] tag#0 Sense Key : Hardware Error >>>[current] > [ 2842.568852] sd 9:0:0:0: [sdc] tag#0 Add. Sense: No additional >>>sense > information > [ 2842.568857] sd 9:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 04 a4 > 58 00 00 f0 00 > [ 2842.568859] blk_update_request: I/O error, dev sdc, sector >>>17081432 > [ 2842.568862] buffer_io_error: 20 callbacks suppressed > > nmon says sdc is 100% busy but doesn't show any reading or writing. >>>I > once pulled the USB stick in a situation like this and I ended up > having to reformat it which I need to avoid this time since the file > is crucial. What should I do? > > - Grant Whatever you do, do NOT try to unplug the USB you were writing to >>>unless you first manage to successfully unmount it. If you do pull the USB >>>stick regardless of its current I/O state you will likely corrupt whatever >>>file you were writing onto, or potentially more. You could well have a hardware failure here, which manifested itself >>>during your copying operation. Things you could try: Run lsof to find out which process is trying to access the USB fs and >>>kill it. Then see if you can remount it read-only. Run dd, dcfldd, ddrescue to make an image of the complete USB stick >>>on your hard drive and then try to recover any lost files with testdisk. Use any low level recovery tools the manufacturer may offer - they >>>will likely require MSWindows. Shut down your OS and disconnect the USB stick, then reboot and try >>>again to access it, although I would first create an image of the device using >>>any of the above tools. >>> >>> >>>dd errored and lsof returned no output at all so I tried to reboot but >>>even that hung after the first 2 lines of output so I did a hard reset >>>after waiting an hour or so. Once it came back up I tried to do 'dd >>>if=/dev/sdb1 of=usbstick' but I got this after awhile: >>> >>>dd: error reading ‘/dev/sdb1’: Input/output error >>>16937216+0 records in >>>16937216+0 records out >>>8671854592 bytes (8.7 GB) copied, 230.107 s, 37.7 MB/s >>> >>>It's a 64GB USB stick. dmesg says: >>> >>>[ 744.729873] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK >>>driverbyte=DRIVER_SENSE >>>[ 744.729879] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error >>>[current] >>>[ 744.729883] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read >>>error >>>[ 744.729886] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 78 e0 >>>00 00 f0 00 >>>[ 744.729889] blk_update_request: critical medium error, dev sdb, >>>sector 16939232 >>>[ 744.763468] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK >>>driverbyte=DRIVER_SENSE >>>[ 744.763472] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error >>>[current] >>>[ 744.763474] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read >>>error >>>[ 744.763478] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 79 00 >>>00 00 04 00 >>>[ 744.763480] blk_update_request: critical medium error, dev sdb, >>>sector 16939264 >>>[ 744.763482] Buffer I/O error on dev sdb1, logical block 4234304, >>>async page read >>>[ 744.786743] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK
Re: [gentoo-user] USB crucial file recovery
I have a USB stick with a crucial file on it (and only an old backup elsewhere). It's formatted NTFS because I wanted to be able to open the file on various Gentoo systems and my research indicated that >>NTFS was the best solution. I decided to copy a 10GB file from a USB hard disk directly to the >>USB stick this morning and I ran into errors so I canceled the operation and now the file manager (thunar) has been stuck for well over an >>hour and I'm getting errors like these over and over: [ 2794.535814] Buffer I/O error on dev sdc1, logical block 2134893, lost async page write [ 2794.535819] Buffer I/O error on dev sdc1, logical block 2134894, lost async page write [ 2794.535822] Buffer I/O error on dev sdc1, logical block 2134895, lost async page write [ 2794.535824] Buffer I/O error on dev sdc1, logical block 2134896, lost async page write [ 2794.535826] Buffer I/O error on dev sdc1, logical block 2134897, lost async page write [ 2794.535828] Buffer I/O error on dev sdc1, logical block 2134898, lost async page write [ 2794.535830] Buffer I/O error on dev sdc1, logical block 2134899, lost async page write [ 2794.535832] Buffer I/O error on dev sdc1, logical block 2134900, lost async page write [ 2794.535835] Buffer I/O error on dev sdc1, logical block 2134901, lost async page write [ 2794.535837] Buffer I/O error on dev sdc1, logical block 2134902, lost async page write [ 2842.568843] sd 9:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE [ 2842.568849] sd 9:0:0:0: [sdc] tag#0 Sense Key : Hardware Error >>[current] [ 2842.568852] sd 9:0:0:0: [sdc] tag#0 Add. Sense: No additional >>sense information [ 2842.568857] sd 9:0:0:0: [sdc] tag#0 CDB: Write(10) 2a 00 01 04 a4 58 00 00 f0 00 [ 2842.568859] blk_update_request: I/O error, dev sdc, sector >>17081432 [ 2842.568862] buffer_io_error: 20 callbacks suppressed nmon says sdc is 100% busy but doesn't show any reading or writing. >>I once pulled the USB stick in a situation like this and I ended up having to reformat it which I need to avoid this time since the file is crucial. What should I do? - Grant >>> >>> Whatever you do, do NOT try to unplug the USB you were writing to >>unless you >>> first manage to successfully unmount it. If you do pull the USB >>stick >>> regardless of its current I/O state you will likely corrupt whatever >>file you >>> were writing onto, or potentially more. >>> >>> You could well have a hardware failure here, which manifested itself >>during >>> your copying operation. Things you could try: >>> >>> Run lsof to find out which process is trying to access the USB fs and >>kill it. >>> Then see if you can remount it read-only. >>> >>> Run dd, dcfldd, ddrescue to make an image of the complete USB stick >>on your >>> hard drive and then try to recover any lost files with testdisk. >>> >>> Use any low level recovery tools the manufacturer may offer - they >>will likely >>> require MSWindows. >>> >>> Shut down your OS and disconnect the USB stick, then reboot and try >>again to >>> access it, although I would first create an image of the device using >>any of >>> the above tools. >> >> >>dd errored and lsof returned no output at all so I tried to reboot but >>even that hung after the first 2 lines of output so I did a hard reset >>after waiting an hour or so. Once it came back up I tried to do 'dd >>if=/dev/sdb1 of=usbstick' but I got this after awhile: >> >>dd: error reading ‘/dev/sdb1’: Input/output error >>16937216+0 records in >>16937216+0 records out >>8671854592 bytes (8.7 GB) copied, 230.107 s, 37.7 MB/s >> >>It's a 64GB USB stick. dmesg says: >> >>[ 744.729873] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK >>driverbyte=DRIVER_SENSE >>[ 744.729879] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error >>[current] >>[ 744.729883] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read >>error >>[ 744.729886] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 78 e0 >>00 00 f0 00 >>[ 744.729889] blk_update_request: critical medium error, dev sdb, >>sector 16939232 >>[ 744.763468] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK >>driverbyte=DRIVER_SENSE >>[ 744.763472] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error >>[current] >>[ 744.763474] sd 8:0:0:0: [sdb] tag#0 Add. Sense: Unrecovered read >>error >>[ 744.763478] sd 8:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 01 02 79 00 >>00 00 04 00 >>[ 744.763480] blk_update_request: critical medium error, dev sdb, >>sector 16939264 >>[ 744.763482] Buffer I/O error on dev sdb1, logical block 4234304, >>async page read >>[ 744.786743] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK >>driverbyte=DRIVER_SENSE >>[ 744.786747] sd 8:0:0:0: [sdb] tag#0 Sense Key : Medium Error >>[current] >>[ 744.786750] sd
Re: [gentoo-user] python-updater: depclean removes it?
On 08/29/2016 03:39 PM, Michael Orlitzky wrote: > On 08/29/2016 06:10 PM, Alan McKinnon wrote: >> >> What replaces it's functionality, or what is now in the codebase that >> guarantees the problems python-updater fixed can't happen anymore? >> > > *shrug* > > mgorny says: > > It's obsolete for a long time (pretty much since PYTHON_TARGETS > become widespread), full of bugs and pretty much useless these days. > It will be masked for removal soon. However, we are giving people a > few more weeks to get it cleaned out of their systems to avoid any > potential issues. > > https://bugs.gentoo.org/show_bug.cgi?id=590120 > > Ah, that's why I didn't find a bug, it was closed already. Dan
Re: [gentoo-user] python-updater: depclean removes it?
On 08/29/2016 06:10 PM, Alan McKinnon wrote: > > What replaces it's functionality, or what is now in the codebase that > guarantees the problems python-updater fixed can't happen anymore? > *shrug* mgorny says: It's obsolete for a long time (pretty much since PYTHON_TARGETS become widespread), full of bugs and pretty much useless these days. It will be masked for removal soon. However, we are giving people a few more weeks to get it cleaned out of their systems to avoid any potential issues. https://bugs.gentoo.org/show_bug.cgi?id=590120
Re: [gentoo-user] python-updater: depclean removes it?
On 29/08/2016 21:29, Michael Orlitzky wrote: On 08/29/2016 03:08 PM, Daniel Frey wrote: Did something change recently? I was doing some updates and noticed app-admin/python-updater was removed. It's still in the tree but the system decided it was no longer needed - was it removed from @system? It's no longer needed, its removal is intentional. What replaces it's functionality, or what is now in the codebase that guarantees the problems python-updater fixed can't happen anymore? Now and again I run it just for fun and sometimes python-updater finds something to rebuild. Which implies that it's either still needed or finding false positives. I'd like to know which is true :-)
Re: [gentoo-user] emerge @system
On 29/08/2016 21:08, Neil Bothwick wrote: On Mon, 29 Aug 2016 17:04:08 +0100, Peter Humphrey wrote: I remember someone (Dale?) some time ago being dismayed at the large number of packages that would be installed by emerge @system. Now I see what he meant: on this box 401 of the 1103 installed packages. I'd like to construct a set that would create a reliable basis for building the rest of @system and @world. I have a small rescue system on the same disk, also ~amd64, which doesn't have X or any desktop programs but otherwise is configured for the same setup. Would it be sensible to use the 44 packages in that @system as a new set @sysbase on the main system, or would I miss something important? Surely the addition of X, and maybe kde or gnome, to your USE flags is what is causing so many packages to be pulled in by @system. I found something similar when building a new system recently, @system pulled in X and a shedload of dependencies. Switching to a non-desktop profile meant far fewer packages were needed to get a basic system. Don't forget that @system only lives in a context, and the context is a real computer. Out of context it's just a list of strings. In context, it's strings that means packages, with deps and everything else that needs to be built for @system to mean anything on the machine it's added to. One never needs to define @system, that is already done in a profile so it's not something that means sense to migrate or re-use elsewhere. Don't worry about @system, worry about USE and get that right. Emerge will deal with what it takes to give the user the @system he's really asking for. Or maybe I don't completely understand yet Peter's actual question. Alan
Re: [gentoo-user] python-updater: depclean removes it?
On 08/29/2016 03:08 PM, Daniel Frey wrote: > Did something change recently? > > I was doing some updates and noticed app-admin/python-updater was > removed. It's still in the tree but the system decided it was no longer > needed - was it removed from @system? > It's no longer needed, its removal is intentional.
Re: [gentoo-user] emerge @system
On Mon, 29 Aug 2016 17:04:08 +0100, Peter Humphrey wrote: > I remember someone (Dale?) some time ago being dismayed at the large > number of packages that would be installed by emerge @system. > > Now I see what he meant: on this box 401 of the 1103 installed > packages. I'd like to construct a set that would create a reliable > basis for building the rest of @system and @world. > > I have a small rescue system on the same disk, also ~amd64, which > doesn't have X or any desktop programs but otherwise is configured for > the same setup. Would it be sensible to use the 44 packages in that > @system as a new set @sysbase on the main system, or would I miss > something important? Surely the addition of X, and maybe kde or gnome, to your USE flags is what is causing so many packages to be pulled in by @system. I found something similar when building a new system recently, @system pulled in X and a shedload of dependencies. Switching to a non-desktop profile meant far fewer packages were needed to get a basic system. -- Neil Bothwick Walk softly and carry a fully charged phazer. pgpFtOmmLMPfI.pgp Description: OpenPGP digital signature
[gentoo-user] python-updater: depclean removes it?
Did something change recently? I was doing some updates and noticed app-admin/python-updater was removed. It's still in the tree but the system decided it was no longer needed - was it removed from @system? After an update I typically run perl-cleaner, python-updater, and revdep-rebuild to catch packages portage misses. So I was a little surprised when it popped up in the --depclean list. Dan
Re: [gentoo-user] guvcview update produces an executable with missing lib...
On 08/29/2016 11:11 AM, waltd...@waltdnes.org wrote: > On Mon, Aug 29, 2016 at 06:29:50PM +0200, meino.cra...@gmx.de wrote >> Hi, >> >> after updateing my system, beside others guvcview was updated: >> >> from qlop >> Mon Aug 29 17:44:08 2016 >>> media-video/guvcview-2.0.4 >> >> After ldconfig as root and rehash (zsh) as user I got: >> >> /home/user>guvcview >> guvcview: error while loading shared libraries: libgviewv4l2core-1.0.so.1: >> cannot open shared object file: No such file or directory >> [1]23848 exit 127 guvcview >> >> >> ...h. >> >> What did I wrong? >> >> Best regards, >> mcc > > The first suggestion in a case like this is to run revdep-rebuild. As > a matter of fact, it probably wouldn't hurt to run revdep-rebuild after > every update. > Yes, I do. Portage occasionally misses a rebuild. It's a lot better now at catching them but it still misses them. Dan
Re: [gentoo-user] guvcview update produces an executable with missing lib...
On Mon, Aug 29, 2016 at 06:29:50PM +0200, meino.cra...@gmx.de wrote > Hi, > > after updateing my system, beside others guvcview was updated: > > from qlop > Mon Aug 29 17:44:08 2016 >>> media-video/guvcview-2.0.4 > > After ldconfig as root and rehash (zsh) as user I got: > > /home/user>guvcview > guvcview: error while loading shared libraries: libgviewv4l2core-1.0.so.1: > cannot open shared object file: No such file or directory > [1]23848 exit 127 guvcview > > > ...h. > > What did I wrong? > > Best regards, > mcc The first suggestion in a case like this is to run revdep-rebuild. As a matter of fact, it probably wouldn't hurt to run revdep-rebuild after every update. -- Walter DnesI don't run "desktop environments"; I run useful applications
[gentoo-user] guvcview update produces an executable with missing lib...
Hi, after updateing my system, beside others guvcview was updated: from qlop Mon Aug 29 17:44:08 2016 >>> media-video/guvcview-2.0.4 After ldconfig as root and rehash (zsh) as user I got: /home/user>guvcview guvcview: error while loading shared libraries: libgviewv4l2core-1.0.so.1: cannot open shared object file: No such file or directory [1]23848 exit 127 guvcview ...h. What did I wrong? Best regards, mcc
[gentoo-user] emerge @system
Hello list, I remember someone (Dale?) some time ago being dismayed at the large number of packages that would be installed by emerge @system. Now I see what he meant: on this box 401 of the 1103 installed packages. I'd like to construct a set that would create a reliable basis for building the rest of @system and @world. I have a small rescue system on the same disk, also ~amd64, which doesn't have X or any desktop programs but otherwise is configured for the same setup. Would it be sensible to use the 44 packages in that @system as a new set @sysbase on the main system, or would I miss something important? The set is attached. -- Rgds Peter app-arch/bzip2 app-arch/gzip app-arch/tar app-arch/xz-utils app-shells/bash:0 net-misc/iputils net-misc/rsync net-misc/wget sys-apps/baselayout sys-apps/busybox sys-apps/coreutils sys-apps/diffutils sys-apps/file sys-apps/findutils sys-apps/gawk sys-apps/grep sys-apps/iproute2 sys-apps/kbd sys-apps/less sys-apps/man-pages sys-apps/net-tools sys-apps/openrc sys-apps/sed sys-apps/util-linux sys-apps/which sys-devel/binutils sys-devel/gcc sys-devel/gnuconfig sys-devel/make sys-devel/patch sys-fs/e2fsprogs sys-process/procps sys-process/psmisc virtual/dev-manager virtual/editor virtual/libc virtual/man virtual/modutils virtual/os-headers virtual/package-manager virtual/pager virtual/service-manager virtual/shadow virtual/ssh
Re: [gentoo-user] removal of bopm before hopm is in tree
On Thursday, August 25, 2016 07:29:35 PM Raymond Jennings wrote: > I still use bopm, and it built fine last time I emerged it. > > If hopm isn't in the tree yet, why was bopm still pmasked for removal? > > Reason for asking is I'm curious about removal procedures. I was under the > impression that replacement packages get added to the tree before their > obsolete predecessors get pmasked for booting out. > > And if that's not the case, should it be? https://bugs.gentoo.org/show_bug.cgi?id=473754 has a bug noting why bopm is being removed. It was mentioned in there that hopm isn't in tree, sure. It's also mentioned that bopm's default configuration doesn't really do anything, as it depends on a service that was shuttered back in 2013. (If I read the bug report correctly.) However, note that in that bug, bopm is listed has not having a maintainer in Gentoo...no dev (or volunteer) is maintaining it. Without a maintainer, there's nobody with access who's motivated to add hopm. If you'd like to see hopm in the tree, you care more about it than any of the current devs. Which means you should probably look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers and see about becoming a proxy maintainer for it. -- :wq signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Is there a reason why LLVM/Clang ebuilds don't support "mutislot"?
On Sun, Aug 28, 2016 at 11:58:03PM -0400, P Levine wrote: > Other distros like Ubuntu support the installation of multiple versions of > LLVM/Clang side by side. One of the things Clang is really good at is > support for the most recently approved upcoming features of the C++17 > standard. The best support for testing such features is with the latest > sys-devel/llvm-. However if I want to compile Mesa against a stable > version LLVM/Clang as well, I don't get that option. I'm not sure such a configuration is fully supported upstream, but the way ubuntu (and debian) does this is (was?) painfully broken. If I recall correctly they first build it in one location and then move it around and try to partially solve things through symlinks. This totally destroys llvm-config and LLVM's cmake find_package module meaning those things have hard-coded paths that have nothing to do with where the things are installed on the system. Simple example, the following CMakeLists.txt cmake_minimum_required(VERSION 3.4) project(llvm-test) find_package(LLVM) errors out on ubuntu with: CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:178 (include): include could not find load file: /usr/share/llvm/cmake/LLVMExports.cmake Call Stack (most recent call first): CMakeLists.txt:4 (find_package) CMake Error at /usr/share/llvm-3.8/cmake/LLVMConfig.cmake:181 (include): include could not find load file: /usr/share/llvm/cmake/LLVM-Config.cmake Call Stack (most recent call first): CMakeLists.txt:4 (find_package) -- Configuring incomplete, errors occurred! Fixing this one path leads to more suffering further down the road. The way gentoo maintainers package LLVM is much saner and developer friendly.