| Summary: | Cannot install tigervnc-server due to conflict with vnc-server common | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Andy Liebman <AndrewL733> |
| Component: | RPM Packages | Assignee: | D Morgan <dmorganec> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | alexatkin, aozeritsky, dmorganec, ennael1, fundawang, jquelin, mageia, matteo.pasotti, misc, pterjan |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | tigervnc and vnc-server-common-1.0-2.mga1 | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 3342 | ||
|
Description
Andy Liebman
2012-03-02 23:31:34 CET
Hi can you paste the output of: urpmi --debug tigervnc-server Here you go: [root@localhost init.d]# urpmi --debug tigervnc-server getting lock on urpmi parsing: /etc/urpmi/mediacfg.d/Devel-1-x86_64 parsing: /etc/urpmi/mediacfg.d/Devel-2-beta1-x86_64 loading mirrors cache using mirror ftp://distro.ibiblio.org/pub/linux/distributions/mageia/distrib/cauldron/x86_64 using mirror ftp://distro.ibiblio.org/pub/linux/distributions/mageia/distrib/cauldron/x86_64 using mirror ftp://distro.ibiblio.org/pub/linux/distributions/mageia/distrib/cauldron/x86_64 using mirror ftp://distro.ibiblio.org/pub/linux/distributions/mageia/distrib/cauldron/x86_64 using mirror ftp://distro.ibiblio.org/pub/linux/distributions/mageia/distrib/cauldron/x86_64 using mirror ftp://distro.ibiblio.org/pub/linux/distributions/mageia/distrib/cauldron/x86_64 examining synthesis file [/var/lib/urpmi/Core Release (distrib1)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Core Updates (distrib3)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Nonfree Release (distrib11)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Nonfree Updates (distrib13)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Core 32bit Release (distrib31)/synthesis.hdlist.cz] examining synthesis file [/var/lib/urpmi/Core 32bit Updates (distrib33)/synthesis.hdlist.cz] getting exclusive lock on rpm search_packages: found tigervnc-server-1.1.0-1.mga2.x86_64 matching tigervnc-server found package(s): tigervnc-server-1.1.0-1.mga2.x86_64 opening rpmdb (root=, write=) selecting tigervnc-server-1.1.0-1.mga2.x86_64 requiring vnc-server-common for tigervnc-server-1.1.0-1.mga2.x86_64 selecting vnc-server-common-1.0-2.mga1.noarch tigervnc-server is not in potential orphans To satisfy dependencies, the following packages are going to be installed: Package Version Release Arch (medium "Core Release (distrib1)") tigervnc-server 1.1.0 1.mga2 x86_64 vnc-server-common 1.0 2.mga1 noarch 2.8MB of additional disk space will be used. 939KB of packages will be retrieved. Proceed with the installation of the 2 packages? (Y/n) y opening rpmdb (root=, write=) getting graph of dependencies for sorting sorting graph of dependencies rpms sorted by dependencies: vnc-server-common tigervnc-server selecting vnc-server-common-1.0-2.mga1.noarch selecting tigervnc-server-1.1.0-1.mga2.x86_64 transaction valid: remove= update=vnc-server-common,tigervnc-server scheduled sets of transactions: remove=0= update=2=vnc-server-common,tigervnc-server verifying signature of /var/cache/urpmi/rpms/vnc-server-common-1.0-2.mga1.noarch.rpm verifying signature of /var/cache/urpmi/rpms/tigervnc-server-1.1.0-1.mga2.x86_64.rpm installing vnc-server-common-1.0-2.mga1.noarch.rpm tigervnc-server-1.1.0-1.mga2.x86_64.rpm from /var/cache/urpmi/rpms starting installing packages opening rpmdb (root=, write=1) created transaction for installing on / (remove=0, install=0, upgrade=2) trans: scheduling update of vnc-server-common-1.0-2.mga1.noarch (id=6729, file=/var/cache/urpmi/rpms/vnc-server-common-1.0-2.mga1.noarch.rpm) trans: scheduling update of tigervnc-server-1.1.0-1.mga2.x86_64 (id=12812, file=/var/cache/urpmi/rpms/tigervnc-server-1.1.0-1.mga2.x86_64.rpm) Preparing... ###################################################################################### Installation failed: file /etc/sysconfig/vncservers conflicts between attempted installs of tigervnc-server-1.1.0-1.mga2.x86_64 and vnc-server-common-1.0-2.mga1.noarch Installation failed: file /etc/sysconfig/vncservers conflicts between attempted installs of tigervnc-server-1.1.0-1.mga2.x86_64 and vnc-server-common-1.0-2.mga1.noarch unlocking urpmi database unlocking rpm database EXITING (pid=17311) Ok thanks. In mga the file /etc/sysconfig/vncservers is only in vnc-server-common. As there is no maintainer for this package I added the committers in CC. (Please set the status to 'assigned' if you are working on it) CC:
(none) =>
dmorganec, fundawang, misc I sort of got around this by installing vnc-server-common first, then installing tigervnc-server and ignoring the conflicts. I have tigervnc server working, but this would definitely cause issues for a novice Linux user.
Jerome Quelin
2012-04-12 19:58:37 CEST
CC:
(none) =>
jquelin
Alexey Ozeritsky
2012-05-06 22:24:29 CEST
CC:
(none) =>
aozeritsky I can't believe you haven't fixed this yet in RC 1. Why bother reporting bugs??? This is pretty fundamental stuff, running VNC Server!!
claire robinson
2012-05-12 17:53:51 CEST
CC:
(none) =>
ennael1 It looks like this will affect upgrade from mga1 so adding to the tracker. I will confirm on Monday. Blocks:
(none) =>
3342 Yes someone updated tigervnc to the fedora package switching to systemd and replacing the configuration file with one saying "# THIS FILE HAS BEEN REPLACED BY /lib/systemd/system/vncserver@.service" which is not very helpful... It seems you can no longer have a configuration file, you are supposed to manually copy the service file and edit it... CC:
(none) =>
pterjan http://svnweb.mageia.org/packages/cauldron/tigervnc/current/SOURCES/vncserver.sysconfig?revision=180030&view=markup - i think this file should be removed and info that it cointains should be added into urpmi's readme. This should fix the conflict. CC:
(none) =>
sander.lepik I would vote to remove the untested systemd stuff which makes the package harder to use (and will leave system in bad state if you uninstall the package). I committed it in svn. Package was now uploaded Status:
NEW =>
RESOLVED |