Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I want to install texlive on my fedora 16 laptop with the following procedure:

# yum remove tex-* texlive-*
# cat > /etc/yum.repos.d/texlive.repo <<EOF
[texlive]
name=texlive
baseurl=http://jnovy.fedorapeople.org/texlive/2012/packages.f17/
enabled=1
gpgcheck=0
EOF
# yum update; 
# yum install texlive

after yum update, I notice that my laptop is fedora 16, while I used 2012/packages.fc17/

so I modify /etc/yum.repos.d/texlive.repo to use 2011/packages.fc16

and do yum update again however, there are many errors

    [root@kitty esolve]# yum update
    Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
    http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-16/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-16/x86_64/repodata/repomd.xml
    Trying other mirror.
    Setting up Update Process
    Resolving Dependencies
    --> Running transaction check
    ---> Package dvipng.x86_64 0:1.14-1.fc15 will be obsoleted
    ---> Package kpathsea.x86_64 0:2007-66.fc16 will be obsoleted
    --> Processing Dependency: libkpathsea.so.4()(64bit) for package: evince-dvi-3.2.1-2.fc16.x86_64
    ---> Package mkvtoolnix.x86_64 0:5.8.0-1 will be updated
    ---> Package mkvtoolnix.x86_64 0:6.3.0-1 will be an update
    ---> Package nautilus-dropbox.x86_64 0:1.4.0-1.fc10 will be updated
    ---> Package nautilus-dropbox.x86_64 0:1.6.0-1.fc10 will be an update
    ---> Package texlive-dvipng-bin.x86_64 2:svn26509.0-19.20130317_r29408.fc17 will be obsoleting
    --> Processing Dependency: texlive-kpathsea-lib = 2:2012-19.20130317_r29408.fc17 for package: 2:texlive-dvipng-bin-svn26509.0-19.20130317_r29408.fc17.x86_64
    --> Processing Dependency: texlive-base for package: 2:texlive-dvipng-bin-svn26509.0-19.20130317_r29408.fc17.x86_64
    --> Processing Dependency: tex-dvipng for package: 2:texlive-dvipng-bin-svn26509.0-19.20130317_r29408.fc17.x86_64
    --> Processing Dependency: libpng15.so.15()(64bit) for package: 2:texlive-dvipng-bin-svn26509.0-19.20130317_r29408.fc17.x86_64
    --> Processing Dependency: libkpathsea.so.6()(64bit) for package: 2:texlive-dvipng-bin-svn26509.0-19.20130317_r29408.fc17.x86_64
    ---> Package texlive-kpathsea.noarch 2:svn28792.0-19.fc17 will be obsoleting
    --> Processing Dependency: texlive-kpathsea-bin for package: 2:texlive-kpathsea-svn28792.0-19.fc17.noarch
    --> Running transaction check
    ---> Package kpathsea.x86_64 0:2007-66.fc16 will be obsoleted
    --> Processing Dependency: libkpathsea.so.4()(64bit) for package: evince-dvi-3.2.1-2.fc16.x86_64
    ---> Package texlive-base.noarch 2:2012-19.20130317_r29408.fc17 will be installed
    ---> Package texlive-dvipng.noarch 2:svn26689.1.14-19.fc17 will be installed
    ---> Package texlive-dvipng-bin.x86_64 2:svn26509.0-19.20130317_r29408.fc17 will be obsoleting
    --> Processing Dependency: libpng15.so.15()(64bit) for package: 2:texlive-dvipng-bin-svn26509.0-19.20130317_r29408.fc17.x86_64
    ---> Package texlive-kpathsea-bin.x86_64 2:svn27347.0-19.20130317_r29408.fc17 will be installed
    ---> Package texlive-kpathsea-lib.x86_64 2:2012-19.20130317_r29408.fc17 will be installed
    --> Finished Dependency Resolution
    Error: Package: evince-dvi-3.2.1-2.fc16.x86_64 (@fedora)
               Requires: libkpathsea.so.4()(64bit)
               Removing: kpathsea-2007-66.fc16.x86_64 (@so-updates)
                   libkpathsea.so.4()(64bit)
               Obsoleted By: 2:texlive-kpathsea-svn28792.0-19.fc17.noarch (texlive)
                   Not found
    Error: Package: 2:texlive-dvipng-bin-svn26509.0-19.20130317_r29408.fc17.x86_64 (texlive)
               Requires: libpng15.so.15()(64bit)
     You could try using --skip-broken to work around the problem
     You could try running: rpm -Va --nofiles --nodigest

and when I do yum install texlive, it simply tries to install the f17 version, which failed.

what Can I do to install f16 version? how can I undo yum update with 2012/packages.f17/

I tried yum history, and for today's history, I only have

    Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
    ID     | Login user               | Date and time    | Action(s)      | Altered
    -------------------------------------------------------------------------------
       124 | esolve ... <esolve>      | 2013-09-12 18:35 | Erase          |   24
       123 | root <root>              | 2013-08-23 11:08 | Update         |    1   
       122 | root <root>              | 2013-08-21 14:13 | Update         |    1  <
       121 | esolve ... <esolve>      | 2013-05-31 15:36 | Install        |    1 > 
       120 | root <root>              | 2013-05-29 15:13 | Install        |    1  <
       119 | root <root>              | 2013-04-18 13:13 | Update         |    1 ><

which seems not related to yum update

the history results:

     1003  yum update
     1004  vim
     1005  vim /etc/yum.repos.d/texlive.repo
     1006  yum update
     1007  yum install texlive
     1008  vim /etc/yum.repos.d/texlive.repo
     1009  clear
     1010  yum history
     1011  yum history list
     1012  vim
     1013  vim /etc/yum.repos.d/texlive.repo
     1014  yum history list
     1015  history

also I tried

yum history undo 124 

but it failed!

    [root@kitty esolve]# yum history undo 124
    Loaded plugins: auto-update-debuginfo, langpacks, presto, refresh-packagekit
    http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-16/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found : http://repos.fedorapeople.org/repos/leigh123linux/cinnamon/fedora-16/x86_64/repodata/repomd.xml
    Trying other mirror.
    Undoing transaction 124, from Thu Sep 12 18:35:31 2013
        Erase R-2.14.1-1.fc16.x86_64                  ?
        Erase R-core-2.14.1-1.fc16.x86_64             ?
        Erase R-devel-2.14.1-1.fc16.x86_64            ?
        Erase a2ps-4.14-12.fc15.x86_64                ?
        Erase docbook-utils-pdf-0.6.14-29.fc16.noarch ?
        Erase html2ps-1.0-0.7.b7.fc15.noarch          ?
        Erase jadetex-3.13-10.fc15.noarch             ?
        Erase kile-2.1.1-1.fc16.x86_64                ?
        Erase linuxdoc-tools-0.9.66-9.fc15.x86_64     ?
        Erase tetex-dvipost-1.1-12.fc15.x86_64        ?
        Erase tex-cm-lgc-0.5-18.fc15.noarch           ?
        Erase tex-preview-11.86-6.fc16.noarch         ?
        Erase texinfo-tex-4.13a-15.fc15.x86_64        ?
        Erase texlive-2007-66.fc16.x86_64             ?
        Erase texlive-dvips-2007-66.fc16.x86_64       ?
        Erase texlive-latex-2007-66.fc16.x86_64       ?
        Erase texlive-texmf-2007-40.fc16.noarch       ?
        Erase texlive-texmf-dvips-2007-40.fc16.noarch ?
        Erase texlive-texmf-fonts-2007-40.fc16.noarch ?
        Erase texlive-texmf-latex-2007-40.fc16.noarch ?
        Erase texlive-utils-2007-66.fc16.x86_64       ?
        Erase texmaker-1:3.2.2-1.fc16.x86_64          ?
        Erase texmf-RR-Inria-4.11-inria.0.noarch      ?
        Erase xdvik-22.84.14-9.fc15.x86_64            ?
        Error: No package(s) available to install
share|improve this question

1 Answer 1

Well, I think the url you use for F16 is wrong. The correct one is:

http://jnovy.fedorapeople.org/texlive/2011/packages.fc16/

Otherwise you can undo yum actions with yum history and the option undo or rollback For more details you can refer to the man page and here:

Yum History

Working with transactions - Red Hat 6 docs

share|improve this answer
    
it is a typo. I used the right url –  misteryes Sep 12 '13 at 17:03
    
I tried to list the history, and I can't find any corresponding action in the list,pls the update, thx –  misteryes Sep 12 '13 at 17:07
    
Is what you used yum history list ? Please also paste the commands that led to the output. –  Vasil Valchev Sep 12 '13 at 17:40
    
I have updated, pls see the question, thx –  misteryes Sep 12 '13 at 19:56

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.