View previous topic :: View next topic |
Author |
Message |
znavko n00b
Joined: 09 Oct 2017 Posts: 14
|
Posted: Mon Oct 09, 2017 2:32 pm Post subject: [solved] mutagen is not downloading. How to install it? |
|
|
I use Funtoo. I need your support, cause I do not know how manually install package mutagen and complete my emerge task.
Code: | $ emerge gimp vlc exaile
...
...
>>> Emerging (1 of 44) media-libs/mutagen-1.36.2::media-kit
* Fetching files in the background.
* To view fetch progress, run in another terminal:
* tail -f /var/log/emerge-fetch.log
>>> Downloading 'http://distfiles.gentoo.org/distfiles/mutagen-1.36.2.tar.gz'
--2017-10-09 15:59:28-- http://distfiles.gentoo.org/distfiles/mutagen-1.36.2.tar.gz
Resolving distfiles.gentoo.org... 156.56.247.195, 140.211.166.134, 216.165.129.135, ...
Connecting to distfiles.gentoo.org|156.56.247.195|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-10-09 15:59:29 ERROR 404: Not Found.
>>> Downloading 'https://bitbucket.org/lazka/mutagen/downloads/mutagen-1.36.2.tar.gz'
--2017-10-09 15:59:29-- https://bitbucket.org/lazka/mutagen/downloads/mutagen-1.36.2.tar.gz
Resolving bitbucket.org... 104.192.143.3, 104.192.143.2, 104.192.143.1
Connecting to bitbucket.org|104.192.143.3|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-10-09 15:59:30 ERROR 404: Not Found.
!!! Couldn't download 'mutagen-1.36.2.tar.gz'. Aborting.
* Fetch failed for 'media-libs/mutagen-1.36.2', Log file:
* '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
>>> Failed to emerge media-libs/mutagen-1.36.2, Log file:
>>> '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
* Messages for package media-libs/mutagen-1.36.2:
* Fetch failed for 'media-libs/mutagen-1.36.2', Log file:
* '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
|
I try manually install:
Code: |
$ git clone https://github.com/quodlibet/mutagen
$ cd mutagen
$ python setup.py
$ python setup.py --help
$ python setup.py install
|
Installation finished. I run again:
Code: |
$ emerge gimp vlc exaile
...
!! Couldn't download 'mutagen-1.36.2.tar.gz'. Aborting.
* Fetch failed for 'media-libs/mutagen-1.36.2', Log file:
* '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
>>> Failed to emerge media-libs/mutagen-1.36.2, Log file:
>>> '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
* Messages for package media-libs/mutagen-1.36.2:
* Fetch failed for 'media-libs/mutagen-1.36.2', Log file:
* '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
|
What to do? Should I manually register mutagen in my system after manual installation?
Last edited by znavko on Tue Oct 10, 2017 9:21 am; edited 2 times in total |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30916 Location: here
|
|
Back to top |
|
|
znavko n00b
Joined: 09 Oct 2017 Posts: 14
|
Posted: Mon Oct 09, 2017 3:02 pm Post subject: |
|
|
With your advice I deleted manually installed mutagen
Code: | $ python setup.py -V
1.39.dev0
$ rm -R /usr/lib64/python2.7/site-packages/mutagen
|
I downloaded and installed required version 1.36:
Code: |
$ wget https://github.com/quodlibet/mutagen/releases/download/release-1.36.2/mutagen-1.36.2.tar.gz
$ tar xvf mutagen*
$ cd mutagen-1.36.2
$ python setup.py install
....
...
Writing /usr/lib64/python2.7/site-packages/mutagen-1.36.2-py2.7.egg-info
|
I only doubt if emerge needs mutagen for python3. I run again
Code: |
$ emerge gimp vlc exaile
....
>>> Failed to emerge media-libs/mutagen-1.36.2, Log file:
>>> '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
* Messages for package media-libs/mutagen-1.36.2:
* Fetch failed for 'media-libs/mutagen-1.36.2', Log file:
* '/var/tmp/portage/media-libs/mutagen-1.36.2/temp/build.log'
|
How to say system mutagen is installed??
Last edited by znavko on Mon Oct 09, 2017 3:18 pm; edited 1 time in total |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 30916 Location: here
|
Posted: Mon Oct 09, 2017 3:13 pm Post subject: |
|
|
The idea was that you download correct version and put archive in /usr/portage/distfiles, after that you can use emerge -1 mutagen command.
PS: you disabled BBCode on your message? _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
znavko n00b
Joined: 09 Oct 2017 Posts: 14
|
Posted: Mon Oct 09, 2017 3:40 pm Post subject: Solved |
|
|
Here described a method you mentioned: http://www.funtoo.org/Portage_Distfiles_Mirror
But for Funtoo I can put package archive into dir /var/cache/portage/distfiles without any other things.
Code: |
$ cd /var/cache/portage/distfiles
$ wget https://github.com/quodlibet/mutagen/releases/download/release-1.36.2/mutagen-1.36.2.tar.gz
$ emerge -1 mutagen
...
...
* Detected file collision(s):
*
* /usr/lib64/python2.7/site-packages/mutagen-1.36.2-py2.7.egg-info
* /usr/lib64/python2.7/site-packages/mutagen/flac.py
...
* /usr/bin/moggsplit
* /usr/bin/mid3iconv
* /usr/bin/mutagen-inspect
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
ctr + c
$ emerge gimp vlc exaile
.. the same message about collisions...
|
I found solution emerge collisions: https://forums.gentoo.org/viewtopic-t-718149.html
I added to make.conf
Code: |
$ nano /etc/portage/make.conf
FEATURES="-collision-detect -protect-owned" emerge =media-libs/mutagen-1.36.2
$ etc-update
...Nothing to do:)
$ emerge -1 mutagen
* Package 'media-libs/mutagen-1.36.2' merged despite file collisions. If
* necessary, refer to your elog messages for the whole content of the
* above message.
>>> Auto-cleaning packages...
>>> No outdated packages were found on your system.
* GNU info directory index is up-to-date.
$ emerge gimp vlc exaile
|
It's ok. Thank you, fedeliallalinea! |
|
Back to top |
|
|
pjp Administrator
Joined: 16 Apr 2002 Posts: 20067
|
Posted: Mon Oct 09, 2017 4:30 pm Post subject: |
|
|
Moved from Portage & Programming to Unsupported Software as this is Funtoo related. _________________ Quis separabit? Quo animo? |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21633
|
Posted: Tue Oct 10, 2017 12:58 am Post subject: |
|
|
Generally, you should not disable collision protection. In this case, you needed to do it (probably) because you did not remove all mutagen files installed outside control of Portage, so the Portage-managed install collided with those remnants. If you avoid installing software system-wide outside Portage, you will not need to disable collision protection. |
|
Back to top |
|
|
znavko n00b
Joined: 09 Oct 2017 Posts: 14
|
Posted: Tue Oct 10, 2017 9:20 am Post subject: |
|
|
I installed it system-wide to complete emerge command. But I have no sense how simply delete package installed system-wide outside Portage. |
|
Back to top |
|
|
Hu Moderator
Joined: 06 Mar 2007 Posts: 21633
|
Posted: Wed Oct 11, 2017 12:52 am Post subject: |
|
|
I think you misunderstand how to use the package manager. When you installed without using emerge, you were not completing a command. You were creating a mess that now must be fixed to avoid later problems. To remove a package installed outside Portage, you must remove every file that package installed. If you are very lucky, you have a record of which files those are and can remove them, either by hand or by running a package-specific uninstall tool. The lack of a standard way to find and remove files installed outside the package manager is one of the major reasons that we encourage people not to go outside the package manager. When Portage installs the files, it can easily uninstall them. When you install outside Portage, it is your responsibility to uninstall the files later. |
|
Back to top |
|
|
|