Cannot install ebuilds in Sabayon 4 [Solved]

[exsencon]

I downloaded an installed Sn4.0 over the WE in place of Sn 3.4. It still looks good but I can't install an ebuild from bugs.gentoo that worked perfectly with Sn 3.4.

In order to get my scanner working (Canon Pixma MP520) I used an ebuild in Sn 3.4 from http://bugs.gentoo.org and it worked very well. Now in Sn 4.0 I just can't do it. I always get something like:

Code: Select all

localhost sane-pixma # emerge sane-pixma
WARNING: repository at /usr/local/portage is missing a repo_name entry
Calculating dependencies... done!

!!! All ebuilds that could satisfy "media-gfx/sane-pixma" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-gfx/sane-pixma-0.14.4 (masked by: corruption)

Now this thing worked perfectly in Sn 3.4. I did exactly the same procedure as I did in the old version of Sn but I am stuck with no clue. The file is not corrupted,it worked in 3.4.
The printer-end of MP520 works perfect with gutenprint-no problem there.
What does Sn 4.0 have that I don't understand?
Install went without any problems.

[Fitzcarraldo]

This is what I get with SL 4.0-r1 x86_64:

Code: Select all

acertm8215 fitzcarraldo # cd /usr/local/portage/media-gfx/sane-pixma/
acertm8215 sane-pixma # ls
sane-pixma-0.14.4.ebuild
acertm8215 sane-pixma # ebuild sane-pixma-0.14.4.ebuild manifest
>>> Creating Manifest for /usr/local/portage/media-gfx/sane-pixma
acertm8215 sane-pixma # ls
Manifest  sane-pixma-0.14.4.ebuild
acertm8215 sane-pixma # emerge -1v sane-pixma

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] media-gfx/sane-pixma-0.14.4  0 kB [1]

Total: 1 package (1 new), Size of downloads: 0 kB
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/local/portage


>>> Verifying ebuild manifests

>>> Emerging (1 of 1) media-gfx/sane-pixma-0.14.4 from unknown repo
 * mp150-0.14.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                  [ ok ]
 * checking ebuild checksums ;-) ...                                     [ ok ]
 * checking auxfile checksums ;-) ...                                    [ ok ]
 * checking miscfile checksums ;-) ...                                   [ ok ]
>>> Unpacking source...
>>> Unpacking mp150-0.14.4.tar.bz2 to /var/tmp/portage/media-gfx/sane-pixma-0.14.4/work
>>> Source unpacked in /var/tmp/portage/media-gfx/sane-pixma-0.14.4/work
>>> Compiling source in /var/tmp/portage/media-gfx/sane-pixma-0.14.4/work/sane-pixma-0.14.4 ...
make -s -j3
>>> Source compiled.
>>> Test phase [not enabled]: media-gfx/sane-pixma-0.14.4

>>> Install sane-pixma-0.14.4 into /var/tmp/portage/media-gfx/sane-pixma-0.14.4/image/ category media-gfx
>>> Completed installing sane-pixma-0.14.4 into /var/tmp/portage/media-gfx/sane-pixma-0.14.4/image/

strip: x86_64-pc-linux-gnu-strip --strip-unneeded -R .comment
   usr/lib/sane/libsane-pixma.so.1
   usr/local/bin/pixmascan

>>> Installing media-gfx/sane-pixma-0.14.4
 * checking 2 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). Once again, please do NOT file
 * a bug report unless you have completely understood the above message.
 *
 * package media-gfx/sane-pixma-0.14.4 NOT merged
 *
 * Detected file collision(s):
 *
 *      /usr/lib/sane/libsane-pixma.so.1
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * media-gfx/sane-backends-1.0.19-r2
 *      /usr/lib/sane/libsane-pixma.so.1
 *
 * Package 'media-gfx/sane-pixma-0.14.4' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.

>>> Failed to install media-gfx/sane-pixma-0.14.4, Log file:

>>>  '/var/lib/entropy/logs/media-gfx:sane-pixma-0.14.4:20090216-145114.log'
acertm8215 sane-pixma #

So no corruption. Try re-creating your manifest. That's what I try first if I get a 'masked by corruption' message. N.B. coming back to your earlier question in another thread about building outside the package manager, notice from the above message that Portage has protected me from overwriting an existing library file from media-gfx/sane-backends-1.0.19-r2. I have not investigated further, but it seems I already have Canon Pixma support in Sane. If I wanted to throw caution to the wind and overwrite the existing library, I could have entered the command FEATURES="-collision-protect" emerge -1v sane-pixma.

[exsencon]

I started all over again and I still don't get it.
I put PORTDIR_OVERLAY="/usr/local/portage" in /etc/make.conf
Then:

Code: Select all

localhost zeger # mkdir -p /usr/local/portage/media-gfx/sane-pixma
localhost zeger # cd /usr/local/portage/media-gfx/sane-pixma
localhost sane-pixma # wget -o sane-pixma-.0.14.4.ebuild http://bugs.gentoo.org/attachment.cgi?id=155647
localhost sane-pixma # ls
attachment.cgi?id=155647  sane-pixma-0.14.4.ebuild
localhost sane-pixma # ebuild sane-pixma-0.14.4.ebuild manifest
localhost sane-pixma # emerge -1v sane-pixma
WARNING: repository at /usr/local/portage is missing a repo_name entry

These are the packages that would be merged, in order:

Calculating dependencies... done!

!!! All ebuilds that could satisfy "media-gfx/sane-pixma" have been masked.
!!! One of the following masked packages is required to complete your request:
- media-gfx/sane-pixma-0.14.4 (masked by: corruption)

Now,as you can see, when I do ls I have two files: the sane-pixma-0.14.4.ebuild file which is just a download file and the attachment.cgi?id=155647 which is the real ebuild. Should I rename that as sane-pixma-0.14.4.ebuild? Whatever I just don't seem to be able to get a manifest. Also I allways get this warning about missing a repo entry.
I am at a loss.

[exsencon]

I just went into the portato gui and sane-pixma is there whit this error:

Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/portato/gui/windows/main.py", line 1247, in cb_pkg_list_selection
self.fill_version_list(self.selCP)
File "/usr/lib/python2.5/site-packages/portato/gui/windows/main.py", line 929, in fill_version_list
packages = system.sort_package_list(system.find_packages(cp, masked=True))
File "/usr/lib/python2.5/site-packages/portato/backend/portage/system.py", line 213, in find_packages
return self.geneticize_list(self._get_set(pkgSet).find(key, masked, with_version, only_cpv), only_cpv or not with_version)
File "/usr/lib/python2.5/site-packages/portato/backend/portage/system.py", line 169, in geneticize_list
return [self.new_package(x) for x in list_of_packages]
File "/usr/lib/python2.5/site-packages/portato/backend/portage/system_22.py", line 64, in new_package
return PortagePackage_22(cpv)
File "/usr/lib/python2.5/site-packages/portato/backend/portage/package.py", line 54, in __init__
self._init_settings(True)
File "/usr/lib/python2.5/site-packages/portato/backend/portage/package.py", line 79, in _init_settings
self._settings.settings.setcpv(self.get_cpv(), mydb = dbapi)
File "/usr/lib/portage/pym/portage/__init__.py", line 1968, in setcpv
for k, v in izip(aux_keys, mydb.aux_get(self.mycpv, aux_keys)):
File "/usr/lib/portage/pym/portage/dbapi/porttree.py", line 406, in aux_get
raise KeyError(mycpv)
KeyError: 'media-gfx/sane-pixma-0.14.4'

Portato version: 0.11.1
Python version: 2.5.2 (r252:60911, Nov 20 2008, 20:10:49)
[GCC 4.3.2]
Used backend: Portage 2.2_rc14
pygtk: 2.13.0 (using GTK+: 2.14.5)
pygobject: 2.15.4 (using GLib: 2.18.3)

Don't really know what it means

[Fitzcarraldo]

What's the file "attachment.cgi?id=155647" doing in your directory /usr/local/portage/media-gfx/sane-pixma/? Delete it. You need to have one text file only in that directory, and it should be called sane-pixma-0.14.4.ebuild and it should contain exactly what is stated on the Web page http://bugs.gentoo.org/attachment.cgi?id=155647

I would expect the message ">>> Creating Manifest for /usr/local/portage/media-gfx/sane-pixma" after I run the ebuild command, telling me that the manifest is created. You're not creating a manifest, which is why the merge is failing.

[exsencon]

Yes,well because I realised the attachment was the one that contained the real ebuild, the one that says sane-pixma-0.14.4.ebuild just contained a few lines and that's all,no ebuild. So I now copied-paste the real ebuild so I have sane-pixma-0.14.4.ebuild and it creates a manifest:

Code: Select all

localhost sane-pixma # ebuild sane-pixma-0.14.4.ebuild manifest
>>> Downloading 'http://213.186.33.38/gentoo-distfiles/distfiles/mp150-0.14.4.tar.bz2'
--2009-02-16 19:46:22--  http://213.186.33.38/gentoo-distfiles/distfiles/mp150-0.14.4.tar.bz2
Connecting to 213.186.33.38:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2009-02-16 19:46:22 ERROR 404: Not Found.

>>> Downloading 'http://gd.tuwien.ac.at/opsys/linux/gentoo/distfiles/mp150-0.14.4.tar.bz2'
--2009-02-16 19:46:22--  http://gd.tuwien.ac.at/opsys/linux/gentoo/distfiles/mp150-0.14.4.tar.bz2
Resolving gd.tuwien.ac.at... 192.35.244.50
Connecting to gd.tuwien.ac.at|192.35.244.50|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://gd.tuwien.ac.at/.admin/missing/server.php?name=GD.TUWIEN.AC.AT [following]
--2009-02-16 19:46:23--  http://gd.tuwien.ac.at/.admin/missing/server.php?name=GD.TUWIEN.AC.AT
Connecting to gd.tuwien.ac.at|192.35.244.50|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/usr/portage/distfiles/mp150-0.14.4.tar.bz2'

    [ <=>                                   ] 9,965       --.-K/s   in 0.05s

2009-02-16 19:46:23 (206 KB/s) - `/usr/portage/distfiles/mp150-0.14.4.tar.bz2' saved [9965]

>>> Creating Manifest for /usr/local/portage/media-gfx/sane-pixma


Then I do:

Code: Select all

localhost sane-pixma # ls
Manifest  sane-pixma-0.14.4.ebuild
localhost sane-pixma # emerge -1v sane-pixma

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] media-gfx/sane-pixma-0.14.4  0 kB [1]

Total: 1 package (1 new), Size of downloads: 0 kB
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/local/portage


>>> Verifying ebuild manifests

>>> Emerging (1 of 1) media-gfx/sane-pixma-0.14.4 from unknown repo
 * mp150-0.14.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                  [ ok ]
 * checking ebuild checksums ;-) ...                                     [ ok ]
 * checking auxfile checksums ;-) ...                                    [ ok ]
 * checking miscfile checksums ;-) ...                                   [ ok ]
>>> Unpacking source...
>>> Unpacking mp150-0.14.4.tar.bz2 to /var/tmp/portage/media-gfx/sane-pixma-0.14.4/work
bzip2: /var/tmp/portage/media-gfx/sane-pixma-0.14.4/distdir/mp150-0.14.4.tar.bz2 is not a bzip2 file.
tar: This does not look like a tar archive
tar: Error exit delayed from previous errors
 *
 * ERROR: media-gfx/sane-pixma-0.14.4 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 2439:  Called unpack 'mp150-0.14.4.tar.bz2'
 *               ebuild.sh, line  380:  Called die
 * The specific snippet of code:
 *                                      assert "$myfail"
 *  The die message:
 *   failure unpacking mp150-0.14.4.tar.bz2
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/lib/entropy/logs/media-gfx:sane-pixma-0.14.4:20090216-195102.log'.
 * The ebuild environment file is located at '/var/tmp/portage/media-gfx/sane-pixma-0.14.4/temp/environment'.
 * This ebuild is from an overlay: '/usr/local/portage/'
 *

>>> Failed to emerge media-gfx/sane-pixma-0.14.4, Log file:

>>>  '/var/lib/entropy/logs/media-gfx:sane-pixma-0.14.4:20090216-195102.log'
localhost sane-pixma #


So it failed apparently because it does not recognize it as a bzip2 file? Any thoughts? Should I use FEATURES="-collision-protect" emerge -1v sane-pixma?

[Fitzcarraldo]

Looks to me like you're having the same mirror trouble that forum member xipi had -- see the thread viewtopic.php?f=54&t=16132

Anyway, if you look through the console output you pasted, you can see that the file mp150-0.14.4.tar.bz2 has not been downloaded correctly. Just paste "mp150-0.14.4.tar.bz2" into Google's search box, search for the file and download it manually to e.g. your Desktop, then copy it to the directory /usr/portage/distfiles/. Then re-run the ebuild command to recreate the manifest. Then re-run the emerge command to merge the file.

[exsencon]

Allright,I did as you said and got a little farther down the road but now I have a package collision you mentioned earlier.

Code: Select all

localhost sane-pixma # emerge -1v sane-pixma

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] media-gfx/sane-pixma-0.14.4  0 kB [1]

Total: 1 package (1 new), Size of downloads: 0 kB
Portage tree and overlays:
 [0] /usr/portage
 [1] /usr/local/portage


>>> Verifying ebuild manifests

>>> Emerging (1 of 1) media-gfx/sane-pixma-0.14.4 from unknown repo
 * mp150-0.14.4.tar.bz2 RMD160 SHA1 SHA256 size ;-) ...                  [ ok ]
 * checking ebuild checksums ;-) ...                                     [ ok ]
 * checking auxfile checksums ;-) ...                                    [ ok ]
 * checking miscfile checksums ;-) ...                                   [ ok ]
>>> Unpacking source...
>>> Unpacking mp150-0.14.4.tar.bz2 to /var/tmp/portage/media-gfx/sane-pixma-0.14.4/work
>>> Source unpacked in /var/tmp/portage/media-gfx/sane-pixma-0.14.4/work
>>> Compiling source in /var/tmp/portage/media-gfx/sane-pixma-0.14.4/work/sane-pixma-0.14.4 ...
make -j2 -s
>>> Source compiled.
>>> Test phase [not enabled]: media-gfx/sane-pixma-0.14.4

>>> Install sane-pixma-0.14.4 into /var/tmp/portage/media-gfx/sane-pixma-0.14.4/image/ category media-gfx
>>> Completed installing sane-pixma-0.14.4 into /var/tmp/portage/media-gfx/sane-pixma-0.14.4/image/

strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment
   usr/local/bin/pixmascan
   usr/lib/sane/libsane-pixma.so.1

>>> Installing media-gfx/sane-pixma-0.14.4
 * checking 2 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at http://bugs.gentoo.org unless you report exactly which
 * two packages install the same file(s). Once again, please do NOT file
 * a bug report unless you have completely understood the above message.
 *
 * package media-gfx/sane-pixma-0.14.4 NOT merged
 *
 * Detected file collision(s):
 *
 *      /usr/lib/sane/libsane-pixma.so.1
 *
 * Searching all installed packages for file collisions...
 *
 * Press Ctrl-C to Stop
 *
 * media-gfx/sane-backends-1.0.19-r2
 *      /usr/lib/sane/libsane-pixma.so.1
 *
 * Package 'media-gfx/sane-pixma-0.14.4' NOT merged due to file
 * collisions. If necessary, refer to your elog messages for the whole
 * content of the above message.

>>> Failed to install media-gfx/sane-pixma-0.14.4, Log file:

>>>  '/var/lib/entropy/logs/media-gfx:sane-pixma-0.14.4:20090217-133125.log'
localhost sane-pixma #


What now? Should I do FEATURES="-collision-protect" emerge -1v sane-pixma ? I got the feeling I am almost there!

[Fitzcarraldo]

Try it and see. You'll probably be all right; just don't blame me if it breaks something!

[exsencon]

Well it didn't break anything I believe but it didn't work. I still get the same collision message and no install.