I like to use a graphical packager manager to get easy repo management - either immediate or sticky. In f25 and f26 yumex-dnf lets me examine things as non-root and then asks for permission before making changes.
I understand that the current recommendation in f26 is dnfdragora.
As non-root, the dnfdragora gui allows me to select or deselect repos - and the one I particularly want to control is rpmfusion updates - but this seems to have no effect on the packages found. Am I supposed to have 'kdesu dnfdragora' in the launcher?
I have kannolo-root-unlocker installed.
TIA,
John P
On 27/11/17 23:15, John Pilkington wrote:
I like to use a graphical packager manager to get easy repo management - either immediate or sticky. In f25 and f26 yumex-dnf lets me examine things as non-root and then asks for permission before making changes.
I understand that the current recommendation in f26 is dnfdragora.
As non-root, the dnfdragora gui allows me to select or deselect repos - and the one I particularly want to control is rpmfusion updates - but this seems to have no effect on the packages found. Am I supposed to have 'kdesu dnfdragora' in the launcher?
I have kannolo-root-unlocker installed.
I tried it with 'kdesu dnfdragora' and a newly-selected repo was still ignored.
Earlier, as non-root, fedora-updates showed 14 updates. I used the gui to enable rpmfusion-updates, but saw no more. After a 'divided by a common language' moment I guessed that 'Check all' meant 'Select all', supplied the root password, and the original 14 updates were installed.
When that had happened all the possible (and mostly unwanted) updates from rpmfusion were on offer. I quit.
I should explain that I'm running a local build of mythtv master that is seen as a downgrade from the version in rpmfusion, and I don't want it overwritten. I haven't yet found a good change to the specfile, which seems fine in other respects.
TIA,
John P
On 11/28/2017 12:40 PM, John Pilkington wrote:
On 27/11/17 23:15, John Pilkington wrote:
I like to use a graphical packager manager to get easy repo management
- either immediate or sticky. In f25 and f26 yumex-dnf lets me
examine things as non-root and then asks for permission before making changes.
I understand that the current recommendation in f26 is dnfdragora.
As non-root, the dnfdragora gui allows me to select or deselect repos
- and the one I particularly want to control is rpmfusion updates -
but this seems to have no effect on the packages found. Am I supposed to have 'kdesu dnfdragora' in the launcher?
I have kannolo-root-unlocker installed.
I tried it with 'kdesu dnfdragora' and a newly-selected repo was still ignored.
Earlier, as non-root, fedora-updates showed 14 updates. I used the gui to enable rpmfusion-updates, but saw no more. After a 'divided by a common language' moment I guessed that 'Check all' meant 'Select all', supplied the root password, and the original 14 updates were installed.
When that had happened all the possible (and mostly unwanted) updates from rpmfusion were on offer. I quit.
I should explain that I'm running a local build of mythtv master that is seen as a downgrade from the version in rpmfusion, and I don't want it overwritten. I haven't yet found a good change to the specfile, which seems fine in other respects.
Have you tried adding something like this to /etc/yum.repos.d/rpmfusion-free-updates.repo ?
exclude=myth*
TIA,
John P
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
On 28/11/17 17:21, Patrick Boutilier wrote:
On 11/28/2017 12:40 PM, John Pilkington wrote:
I should explain that I'm running a local build of mythtv master that is seen as a downgrade from the version in rpmfusion, and I don't want it overwritten. I haven't yet found a good change to the specfile, which seems fine in other respects.
Have you tried adding something like this to /etc/yum.repos.d/rpmfusion-free-updates.repo ?
exclude=myth*
No, but I probably will. It hasn't been required before, because yumex-dnf gave me sufficient control - although I did get caught out once by an auto-upgrade before I knew about the apparent-downgrade problem.
Now I use 'dnf install *64.rpm *arch.rpm --allowerasing' from a copy of the mock result folder, where most of the * will include 'myth'. Perhaps that wouldn't be 'excluded'.
But the Subject still looks like a bug.
Thanks,
John P
On 28.11.2017 17:40, John Pilkington wrote:
I should explain that I'm running a local build of mythtv master that is seen as a downgrade from the version in rpmfusion, and I don't want it overwritten. I haven't yet found a good change to the specfile, which seems fine in other respects.
You could increase the rpm Epoch of your local mythtv build, so it is seen as newer by yum. If you already have an Epoch set in your spec simply increase that. If you have not, set an epoch, add a line "Epoch: 1" (or what ever, I think even 0 is seen as higher as no epoch at all) where you set the version. And keep in mind that any sub-package-requirements now also have to be changed to "%{epoch}:%{version}-%{release}" instead of "%{version}-%{release}"
On 01/12/17 14:04, Lukas Middendorf wrote:
On 28.11.2017 17:40, John Pilkington wrote:
I should explain that I'm running a local build of mythtv master that is seen as a downgrade from the version in rpmfusion, and I don't want it overwritten. I haven't yet found a good change to the specfile, which seems fine in other respects.
You could increase the rpm Epoch of your local mythtv build, so it is seen as newer by yum. If you already have an Epoch set in your spec simply increase that. If you have not, set an epoch, add a line "Epoch: 1" (or what ever, I think even 0 is seen as higher as no epoch at all) where you set the version. And keep in mind that any sub-package-requirements now also have to be changed to "%{epoch}:%{version}-%{release}" instead of "%{version}-%{release}"
OK, thanks for that suggestion. ISTR 'epoch' being mentioned as a possibility before, but I hadn't experimented. You have given more details and I'll look at trying it for the next build.
That could fix my specific 'feature', but won't fix dnfdragora. I'll give it a bit longer, but then maybe a BZ?
On 12/01/2017 10:35 AM, John Pilkington wrote:
On 01/12/17 14:04, Lukas Middendorf wrote:
On 28.11.2017 17:40, John Pilkington wrote:
I should explain that I'm running a local build of mythtv master that is seen as a downgrade from the version in rpmfusion, and I don't want it overwritten. I haven't yet found a good change to the specfile, which seems fine in other respects.
You could increase the rpm Epoch of your local mythtv build, so it is seen as newer by yum. If you already have an Epoch set in your spec simply increase that. If you have not, set an epoch, add a line "Epoch: 1" (or what ever, I think even 0 is seen as higher as no epoch at all) where you set the version. And keep in mind that any sub-package-requirements now also have to be changed to "%{epoch}:%{version}-%{release}" instead of "%{version}-%{release}"
OK, thanks for that suggestion. ISTR 'epoch' being mentioned as a possibility before, but I hadn't experimented. You have given more details and I'll look at trying it for the next build.
That could fix my specific 'feature', but won't fix dnfdragora. I'll give it a bit longer, but then maybe a BZ?
Same thing in Fedora 27 with dnfdragora . Doesn't matter what you select for repositories, always shows the same updates available. Even when running as root.
kde mailing list -- kde@lists.fedoraproject.org To unsubscribe send an email to kde-leave@lists.fedoraproject.org
On 01/12/17 16:47, Patrick Boutilier wrote:
On 12/01/2017 10:35 AM, John Pilkington wrote:
On 01/12/17 14:04, Lukas Middendorf wrote:
On 28.11.2017 17:40, John Pilkington wrote:
I should explain that I'm running a local build of mythtv master that is seen as a downgrade from the version in rpmfusion, and I don't want it overwritten. I haven't yet found a good change to the specfile, which seems fine in other respects.
You could increase the rpm Epoch of your local mythtv build, so it is seen as newer by yum. If you already have an Epoch set in your spec simply increase that. If you have not, set an epoch, add a line "Epoch: 1" (or what ever, I think even 0 is seen as higher as no epoch at all) where you set the version. And keep in mind that any sub-package-requirements now also have to be changed to "%{epoch}:%{version}-%{release}" instead of "%{version}-%{release}"
OK, thanks for that suggestion. ISTR 'epoch' being mentioned as a possibility before, but I hadn't experimented. You have given more details and I'll look at trying it for the next build.
That could fix my specific 'feature', but won't fix dnfdragora. I'll give it a bit longer, but then maybe a BZ?
Same thing in Fedora 27 with dnfdragora . Doesn't matter what you select for repositories, always shows the same updates available. Even when running as root.
As an update: dnfdragora still does this (and had BZs aplenty when I looked), but software-updates and/or yumex-dnf seem ok for me.
I've now built mythtv-master for both el7 and fc26 with an 'Epoch' and don't see the pseudo-downgrades any more. The first attempt failed with two conflicts, apparently resolved by expanding plain "%{version}"s for a theme package as well. Thanks.
John P
-
John Pilkington -
Lukas Middendorf -
Patrick Boutilier