Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upFind a way to prevent installation of fc13 rpms on f14 and vice vers #197
Comments
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the Release 1 Beta 1 milestone
Mar 8, 2015
marmarek
added
bug
C: core
P: major
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by joanna on 5 Apr 2011 22:23 UTC
One might think that if we provided both .fc14 and .fc14 versions of the same packet (i.e. with the same version/rel), then yum would intelligently choose the proper packet (if running on F13 would chose .fc13, etc). But this is not how it works -- yum always greedily chooses the hightest numbered packet, so in that case the .fc14 will always be chosen on both F14 as well as on F13.
Any ideas better than having to maintain two different repos?
|
Comment by joanna on 5 Apr 2011 22:23 UTC Any ideas better than having to maintain two different repos? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by joanna on 6 Apr 2011 07:50 UTC
Ok, I'm pretty determined to split the VM repo into two:
.../current/vm/f13
.../current/vm/f14
.../unstable/vm/f13
.../unstable/vm/f14
Will also require changes to core-commonvm rpm, and to some Makefiles to automatically copy rpms to appropriate repo based on the suffic.
|
Comment by joanna on 6 Apr 2011 07:50 UTC .../current/vm/f13 Will also require changes to core-commonvm rpm, and to some Makefiles to automatically copy rpms to appropriate repo based on the suffic. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 6 Apr 2011 10:52 UTC |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Comment by joanna on 6 Apr 2011 12:39 UTC |
marmarek commentedMar 8, 2015
Reported by joanna on 5 Apr 2011 22:03 UTC
I have just upload new gui-vm package compiled on F13 (so it has .fc13 extension) to our vm unstable repo. When I launched the yum update in VM based on F14 the packet was happily picked and installed. As a result the gui stopped working :/
I think we would like to maintain VM packages for both F13 and F14, and this behaviour is very problematic for us...
Migrated-From: https://wiki.qubes-os.org/ticket/197