Re: DNF not Installing all Updates?
On 2021-06-27 8:09 p.m., Stephen Morris wrote: I usually ignore the "nothing to do" situation as well and just issue the command again the next time I'm ready to put on updates again. It is a bit disconcerting though when Discover reports there being, in my case 638MB of Fedora System Updates as opposed to application updates, right from the first boot of F34 after a fresh install, and that calculation of how many updates are available never changes irrespective of how many updates are applied by dnf and how often. I've had F34 installed in the vm for probably around 6 months, and Discover has never stopped reporting 638MB of System Updates until I actually put them on. That is very strange and doesn't make sense. If you're doing a workstation install, then yes, there will be a large amount of updates to do because it starts with a fixed image and doesn't use updates. But dnf should do them and it would be interesting to see what updates Discover thinks should be done. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 2021-06-27 7:59 p.m., Stephen Morris wrote: On 28/6/21 10:12, Samuel Sieb wrote: On 2021-06-27 4:12 p.m., Stephen Morris wrote: On 27/6/21 22:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. I thought that might be the case. Because I was updating a large number of packages I was seeing this message around a dozen times on various packages. I am assuming that if dnf gets to the situation where it can't find the package in any mirror, that it will suspend that update and any associated updates but continue on with the rest of the updates that are available and check again with the next update to see if it can then find the "missing" package? If dnf can't find a package on any mirror, it will immediately abort the entire transaction. Otherwise, it would have go through the whole dependency resolution process again. So does that then mean that we have to keep issuing the dnf upgrade statement until the issue is resolved, which may or may not be a quick fix depending on what the issue is? A 404 means that a sync is ongoing and not completed yet. It's extremely unlikely that a file will be missing on all mirrors unless you're very unlucky. :-) In any case, you shouldn't have to wait very long. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/6/21 10:18, Ed Greshko wrote: On 28/06/2021 08:11, Samuel Sieb wrote: On 2021-06-27 4:27 p.m., Stephen Morris wrote: On 28/6/21 04:59, Samuel Sieb wrote: On 2021-06-27 5:34 a.m., Stephen Morris wrote: On 27/6/21 22:23, Ed Greshko wrote: I have not had a situation where an update was performed and immediately followed by a need for another update. I do my updates with "dnf --refresh update". The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available. I attribute that to packageKit using different mirrors than dnf. I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? It's not that they use different mirrors. The mirror manager provides somewhat randomized mirrors when asked, so at different times, you can end up looking at different mirrors. And it's possible, if you check during the syncing time, that different mirrors have different available updates. I thought dnf had a list of mirrors and the first time dnf was run it used the first mirror in the list, and kept using that mirror until it got a 404 situation on a package whereby it would go to the next mirror and if the package was obtained from that mirror, it would continue using that mirror for all updates until that produced a 404 situation, in which case it would move to the next mirror and so on. I've been finding it nothing unusual for Discover monitoring process to tell me there were updates available, even after using dnf to put on all updates it can see, and go and issue a dnf upgrade and have dnf tell me there was nothing to do. The default repo configuration is to use the mirror manager. So dnf asks the mirror manager for a list of mirrors and it starts with the first one. I'm not sure if it completely abandons a certain mirror on the first 404, but it does go to another one for at least that file. I don't understand why Discover will tell you that there are more updates available. dnf does cache the current state for a while, so you could try adding "--refresh" to the dnf command to force it to check. But Packagekit uses the same configuration as dnf and I think it even uses the same underlying libraries. As I mentioned somewhere, I still have both packageKit and dnfdragora installed. There are times when the packageKit updates icon appears on my systray telling me a number of updates are available. But, when I run "dnf --refresh upgrade" I am told "Nothing to do". I just try again later in the day. I usually ignore the "nothing to do" situation as well and just issue the command again the next time I'm ready to put on updates again. It is a bit disconcerting though when Discover reports there being, in my case 638MB of Fedora System Updates as opposed to application updates, right from the first boot of F34 after a fresh install, and that calculation of how many updates are available never changes irrespective of how many updates are applied by dnf and how often. I've had F34 installed in the vm for probably around 6 months, and Discover has never stopped reporting 638MB of System Updates until I actually put them on. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
PackageKit uses libdnf. libdnf is the core library for dnf,PackageKit and rpm-ostree. You should generally get the same results using either dnf or PackageKit. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/6/21 10:12, Samuel Sieb wrote: On 2021-06-27 4:12 p.m., Stephen Morris wrote: On 27/6/21 22:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. I thought that might be the case. Because I was updating a large number of packages I was seeing this message around a dozen times on various packages. I am assuming that if dnf gets to the situation where it can't find the package in any mirror, that it will suspend that update and any associated updates but continue on with the rest of the updates that are available and check again with the next update to see if it can then find the "missing" package? If dnf can't find a package on any mirror, it will immediately abort the entire transaction. Otherwise, it would have go through the whole dependency resolution process again. So does that then mean that we have to keep issuing the dnf upgrade statement until the issue is resolved, which may or may not be a quick fix depending on what the issue is? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/6/21 09:43, Ed Greshko wrote: On 28/06/2021 07:06, Stephen Morris wrote: On 28/6/21 05:01, Samuel Sieb wrote: On 2021-06-27 4:28 a.m., Ed Greshko wrote: On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. system-update uses all the repos you have enabled, including the updates repo. After system-update, you should be fully up-to-date. What is system-update, is that functionality provided by another dnf plugin? That would be the command you'd use when upgrading to the next version Fedora when it becomes available. That's okay, I've used that before, I just thought Samuel might have been referring to something different, its all good. regards, Steve Yes, it is a dnf plugin. "sudo dnf install dnf-plugin-system-upgrade" https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ may be helpful when time to upgrade. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 28/06/2021 10:26, ToddAndMargo via users wrote: On 6/27/21 7:13 PM, Ed Greshko wrote: On 28/06/2021 10:07, ToddAndMargo via users wrote: On 6/27/21 6:47 PM, Ed Greshko wrote: On 28/06/2021 09:44, Ed Greshko wrote: and [root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named/slaves/ /var/named/chroot/var/named/slaves/: 2415417 greshko.com.zone /var/named/slaves/: 2415417 greshko.com.zone Can I talk you out of a? # stat /var/named/slaves/ | grep Inode # stat /var/named/chroot/var/named/slaves/ | grep Inode [root@f33k ~]# stat /var/named/slaves/ | grep Inode Device: 20h/32d Inode: 1937752 Links: 1 [root@f33k ~]# stat /var/named/chroot/var/named/slaves/ | grep Inode Device: 20h/32d Inode: 1937752 Links: 1 Awesome! Even more awesome when your issue is resolved. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 6/27/21 7:13 PM, Ed Greshko wrote: On 28/06/2021 10:07, ToddAndMargo via users wrote: On 6/27/21 6:47 PM, Ed Greshko wrote: On 28/06/2021 09:44, Ed Greshko wrote: and [root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named/slaves/ /var/named/chroot/var/named/slaves/: 2415417 greshko.com.zone /var/named/slaves/: 2415417 greshko.com.zone Can I talk you out of a? # stat /var/named/slaves/ | grep Inode # stat /var/named/chroot/var/named/slaves/ | grep Inode [root@f33k ~]# stat /var/named/slaves/ | grep Inode Device: 20h/32d Inode: 1937752 Links: 1 [root@f33k ~]# stat /var/named/chroot/var/named/slaves/ | grep Inode Device: 20h/32d Inode: 1937752 Links: 1 Awesome! ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 28/06/2021 10:07, ToddAndMargo via users wrote: On 6/27/21 6:47 PM, Ed Greshko wrote: On 28/06/2021 09:44, Ed Greshko wrote: and [root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named/slaves/ /var/named/chroot/var/named/slaves/: 2415417 greshko.com.zone /var/named/slaves/: 2415417 greshko.com.zone Can I talk you out of a? # stat /var/named/slaves/ | grep Inode # stat /var/named/chroot/var/named/slaves/ | grep Inode [root@f33k ~]# stat /var/named/slaves/ | grep Inode Device: 20h/32d Inode: 1937752 Links: 1 [root@f33k ~]# stat /var/named/chroot/var/named/slaves/ | grep Inode Device: 20h/32d Inode: 1937752 Links: 1 -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 6/27/21 6:47 PM, Ed Greshko wrote:
On 28/06/2021 09:44, Ed Greshko wrote:
On 28/06/2021 09:39, ToddAndMargo via users wrote:
On 6/27/21 5:34 PM, Ed Greshko wrote:
On 28/06/2021 06:40, ToddAndMargo via users wrote:
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
named.root.key:
Hang on... If you're wanting it to bring things from outside of the
chroot into it, what's the point of chrooting? You're breaking the
jail by doing that.
The old approach was you created all the files in the chroot, where
bind-chroot makes use of them. And, you have a link outside of the
chroot into it, so that *you* can edit /etc/named.something without
thinking about it. But, ultimately, you shouldn't need any files
outside of the chroot, at all. And there's probably some
advantage in
just having one set (less confusing for you, at the very least).
Hi Tim,
Bing-chroot uses "mount --bind". It is not occurring
on my zone files.
For a good explanation, see
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
-T
I have moved my zone fines to /var/named
Mount bind still does not get them. I had to
manually copy them over.
zone "abc.local" {
type master;
# file "/var/named/chroot/var/named/abc.hosts";
file "abc.hosts";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
zone "255.168.192.in-addr.arpa" {
type master;
# file "/var/named/chroot/var/named/abc.hosts.rev";
file "abc.hosts.rev";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
You may want to start "clean".
First stop named-chroot and start the named server to make sure it
doesn't produced erros.
If that check ok, then stop named.
Then do
rpm -e --nodeps bind-chroot
rm -rf /var/named/chroot
dnf install bind-chroot
Then, without moving any files or doing anything, start named-chroot
FYI, I just did the above procedure on my test system without trouble.
Did it do a mount --bind on your zone files?
Of course..
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named/slaves/
/var/named/chroot/var/named/slaves/:
2415417 greshko.com.zone
/var/named/slaves/:
2415417 greshko.com.zone
Can I talk you out of a?
# stat /var/named/slaves/ | grep Inode
# stat /var/named/chroot/var/named/slaves/ | grep Inode
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 28/06/2021 09:44, Ed Greshko wrote:
On 28/06/2021 09:39, ToddAndMargo via users wrote:
On 6/27/21 5:34 PM, Ed Greshko wrote:
On 28/06/2021 06:40, ToddAndMargo via users wrote:
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
named.root.key:
Hang on... If you're wanting it to bring things from outside of the
chroot into it, what's the point of chrooting? You're breaking the
jail by doing that.
The old approach was you created all the files in the chroot, where
bind-chroot makes use of them. And, you have a link outside of the
chroot into it, so that *you* can edit /etc/named.something without
thinking about it. But, ultimately, you shouldn't need any files
outside of the chroot, at all. And there's probably some advantage in
just having one set (less confusing for you, at the very least).
Hi Tim,
Bing-chroot uses "mount --bind". It is not occurring
on my zone files.
For a good explanation, see
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
-T
I have moved my zone fines to /var/named
Mount bind still does not get them. I had to
manually copy them over.
zone "abc.local" {
type master;
# file "/var/named/chroot/var/named/abc.hosts";
file "abc.hosts";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
zone "255.168.192.in-addr.arpa" {
type master;
# file "/var/named/chroot/var/named/abc.hosts.rev";
file "abc.hosts.rev";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
You may want to start "clean".
First stop named-chroot and start the named server to make sure it doesn't
produced erros.
If that check ok, then stop named.
Then do
rpm -e --nodeps bind-chroot
rm -rf /var/named/chroot
dnf install bind-chroot
Then, without moving any files or doing anything, start named-chroot
FYI, I just did the above procedure on my test system without trouble.
Did it do a mount --bind on your zone files?
Of course..
and
[root@f33k ~]# ls -i /var/named/chroot/var/named/slaves/ /var/named/slaves/
/var/named/chroot/var/named/slaves/:
2415417 greshko.com.zone
/var/named/slaves/:
2415417 greshko.com.zone
--
Remind me to ignore comments which aren't germane to the thread.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 28/06/2021 09:39, ToddAndMargo via users wrote:
On 6/27/21 5:34 PM, Ed Greshko wrote:
On 28/06/2021 06:40, ToddAndMargo via users wrote:
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
named.root.key:
Hang on... If you're wanting it to bring things from outside of the
chroot into it, what's the point of chrooting? You're breaking the
jail by doing that.
The old approach was you created all the files in the chroot, where
bind-chroot makes use of them. And, you have a link outside of the
chroot into it, so that *you* can edit /etc/named.something without
thinking about it. But, ultimately, you shouldn't need any files
outside of the chroot, at all. And there's probably some advantage in
just having one set (less confusing for you, at the very least).
Hi Tim,
Bing-chroot uses "mount --bind". It is not occurring
on my zone files.
For a good explanation, see
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
-T
I have moved my zone fines to /var/named
Mount bind still does not get them. I had to
manually copy them over.
zone "abc.local" {
type master;
# file "/var/named/chroot/var/named/abc.hosts";
file "abc.hosts";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
zone "255.168.192.in-addr.arpa" {
type master;
# file "/var/named/chroot/var/named/abc.hosts.rev";
file "abc.hosts.rev";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
You may want to start "clean".
First stop named-chroot and start the named server to make sure it doesn't
produced erros.
If that check ok, then stop named.
Then do
rpm -e --nodeps bind-chroot
rm -rf /var/named/chroot
dnf install bind-chroot
Then, without moving any files or doing anything, start named-chroot
FYI, I just did the above procedure on my test system without trouble.
Did it do a mount --bind on your zone files?
Of course..
● named-chroot.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named-chroot.service; disabled;
vendor preset: disabled)
Active: active (running) since Mon 2021-06-28 08:27:44 CST; 1h 15min ago
Process: 6305 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then
/usr/sbin/named-checkconf -t /var/named/chroot -z "$NAMEDCONF"; else echo "Checking of zone >
Process: 6307 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} -t
/var/named/chroot $OPTIONS (code=exited, status=0/SUCCESS)
Main PID: 6308 (named)
Tasks: 4 (limit: 2504)
Memory: 57.8M
CPU: 170ms
CGroup: /system.slice/named-chroot.service
└─6308 /usr/sbin/named -u named -c /etc/named.conf -t
/var/named/chroot
Jun 28 08:27:44 f33k.greshko.com named[6308]: all zones loaded
Jun 28 08:27:44 f33k.greshko.com named[6308]: running
Jun 28 08:27:44 f33k.greshko.com named[6308]: zone greshko.com/IN: sending
notifies (serial 1623223423)
Jun 28 08:27:45 f33k.greshko.com named[6308]: managed-keys-zone: Key 20326 for
zone . acceptance timer complete: key now trusted
Jun 28 08:27:45 f33k.greshko.com named[6308]: resolver priming query complete
--
Remind me to ignore comments which aren't germane to the thread.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 6/27/21 5:34 PM, Ed Greshko wrote:
On 28/06/2021 06:40, ToddAndMargo via users wrote:
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
named.root.key:
Hang on... If you're wanting it to bring things from outside of the
chroot into it, what's the point of chrooting? You're breaking the
jail by doing that.
The old approach was you created all the files in the chroot, where
bind-chroot makes use of them. And, you have a link outside of the
chroot into it, so that *you* can edit /etc/named.something without
thinking about it. But, ultimately, you shouldn't need any files
outside of the chroot, at all. And there's probably some advantage in
just having one set (less confusing for you, at the very least).
Hi Tim,
Bing-chroot uses "mount --bind". It is not occurring
on my zone files.
For a good explanation, see
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
-T
I have moved my zone fines to /var/named
Mount bind still does not get them. I had to
manually copy them over.
zone "abc.local" {
type master;
# file "/var/named/chroot/var/named/abc.hosts";
file "abc.hosts";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
zone "255.168.192.in-addr.arpa" {
type master;
# file "/var/named/chroot/var/named/abc.hosts.rev";
file "abc.hosts.rev";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
You may want to start "clean".
First stop named-chroot and start the named server to make sure it
doesn't produced erros.
If that check ok, then stop named.
Then do
rpm -e --nodeps bind-chroot
rm -rf /var/named/chroot
dnf install bind-chroot
Then, without moving any files or doing anything, start named-chroot
FYI, I just did the above procedure on my test system without trouble.
Did it do a mount --bind on your zone files?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
conflict between mythtv and rtl-sdr
After a recent update which installed rtl-sdr-0.6.0-9.fc34.x86_64 mythbackend failed to see the tuners. This was caused by these permissions: crw-rw+ 1 root rtlsdr 212, 3 Jun 20 23:10 /dev/dvb/adapter0/frontend0 set by /usr/lib/udev/rules.d/10-rtl-sdr.rules and mythbackend is not a member of rtlsdr group. There seems to be a conflict between mythtv-backend and rtl-sdr. How should this be resolved? Is it proper for one package (rtl-sdr) to take ownership of these devices? ATM I just change the permissions of dvb tuners from rc.local but this is not ideal. Or I could add mythtv user to rtlsdr group. TIA -- Eyal Lebedinsky (fed...@eyal.emu.id.au) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 28/06/2021 06:40, ToddAndMargo via users wrote:
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
named.root.key:
Hang on... If you're wanting it to bring things from outside of the
chroot into it, what's the point of chrooting? You're breaking the
jail by doing that.
The old approach was you created all the files in the chroot, where
bind-chroot makes use of them. And, you have a link outside of the
chroot into it, so that *you* can edit /etc/named.something without
thinking about it. But, ultimately, you shouldn't need any files
outside of the chroot, at all. And there's probably some advantage in
just having one set (less confusing for you, at the very least).
Hi Tim,
Bing-chroot uses "mount --bind". It is not occurring
on my zone files.
For a good explanation, see
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
-T
I have moved my zone fines to /var/named
Mount bind still does not get them. I had to
manually copy them over.
zone "abc.local" {
type master;
# file "/var/named/chroot/var/named/abc.hosts";
file "abc.hosts";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
zone "255.168.192.in-addr.arpa" {
type master;
# file "/var/named/chroot/var/named/abc.hosts.rev";
file "abc.hosts.rev";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
You may want to start "clean".
First stop named-chroot and start the named server to make sure it doesn't
produced erros.
If that check ok, then stop named.
Then do
rpm -e --nodeps bind-chroot
rm -rf /var/named/chroot
dnf install bind-chroot
Then, without moving any files or doing anything, start named-chroot
FYI, I just did the above procedure on my test system without trouble.
--
Remind me to ignore comments which aren't germane to the thread.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/06/2021 08:11, Samuel Sieb wrote: On 2021-06-27 4:27 p.m., Stephen Morris wrote: On 28/6/21 04:59, Samuel Sieb wrote: On 2021-06-27 5:34 a.m., Stephen Morris wrote: On 27/6/21 22:23, Ed Greshko wrote: I have not had a situation where an update was performed and immediately followed by a need for another update. I do my updates with "dnf --refresh update". The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available. I attribute that to packageKit using different mirrors than dnf. I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? It's not that they use different mirrors. The mirror manager provides somewhat randomized mirrors when asked, so at different times, you can end up looking at different mirrors. And it's possible, if you check during the syncing time, that different mirrors have different available updates. I thought dnf had a list of mirrors and the first time dnf was run it used the first mirror in the list, and kept using that mirror until it got a 404 situation on a package whereby it would go to the next mirror and if the package was obtained from that mirror, it would continue using that mirror for all updates until that produced a 404 situation, in which case it would move to the next mirror and so on. I've been finding it nothing unusual for Discover monitoring process to tell me there were updates available, even after using dnf to put on all updates it can see, and go and issue a dnf upgrade and have dnf tell me there was nothing to do. The default repo configuration is to use the mirror manager. So dnf asks the mirror manager for a list of mirrors and it starts with the first one. I'm not sure if it completely abandons a certain mirror on the first 404, but it does go to another one for at least that file. I don't understand why Discover will tell you that there are more updates available. dnf does cache the current state for a while, so you could try adding "--refresh" to the dnf command to force it to check. But Packagekit uses the same configuration as dnf and I think it even uses the same underlying libraries. As I mentioned somewhere, I still have both packageKit and dnfdragora installed. There are times when the packageKit updates icon appears on my systray telling me a number of updates are available. But, when I run "dnf --refresh upgrade" I am told "Nothing to do". I just try again later in the day. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 2021-06-27 4:12 p.m., Stephen Morris wrote: On 27/6/21 22:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. I thought that might be the case. Because I was updating a large number of packages I was seeing this message around a dozen times on various packages. I am assuming that if dnf gets to the situation where it can't find the package in any mirror, that it will suspend that update and any associated updates but continue on with the rest of the updates that are available and check again with the next update to see if it can then find the "missing" package? If dnf can't find a package on any mirror, it will immediately abort the entire transaction. Otherwise, it would have go through the whole dependency resolution process again. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 2021-06-27 4:27 p.m., Stephen Morris wrote: On 28/6/21 04:59, Samuel Sieb wrote: On 2021-06-27 5:34 a.m., Stephen Morris wrote: On 27/6/21 22:23, Ed Greshko wrote: I have not had a situation where an update was performed and immediately followed by a need for another update. I do my updates with "dnf --refresh update". The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available. I attribute that to packageKit using different mirrors than dnf. I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? It's not that they use different mirrors. The mirror manager provides somewhat randomized mirrors when asked, so at different times, you can end up looking at different mirrors. And it's possible, if you check during the syncing time, that different mirrors have different available updates. I thought dnf had a list of mirrors and the first time dnf was run it used the first mirror in the list, and kept using that mirror until it got a 404 situation on a package whereby it would go to the next mirror and if the package was obtained from that mirror, it would continue using that mirror for all updates until that produced a 404 situation, in which case it would move to the next mirror and so on. I've been finding it nothing unusual for Discover monitoring process to tell me there were updates available, even after using dnf to put on all updates it can see, and go and issue a dnf upgrade and have dnf tell me there was nothing to do. The default repo configuration is to use the mirror manager. So dnf asks the mirror manager for a list of mirrors and it starts with the first one. I'm not sure if it completely abandons a certain mirror on the first 404, but it does go to another one for at least that file. I don't understand why Discover will tell you that there are more updates available. dnf does cache the current state for a while, so you could try adding "--refresh" to the dnf command to force it to check. But Packagekit uses the same configuration as dnf and I think it even uses the same underlying libraries. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/06/2021 07:12, Stephen Morris wrote: On 27/6/21 22:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? Oh, dnf will "catch up" as more mirrors are synced. You'll never have a case where an update is available via PK but never becomes available when using dnf. Thanks Ed, I thought that was the case but I was just checking. While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. I thought that might be the case. Because I was updating a large number of packages I was seeing this message around a dozen times on various packages. I am assuming that if dnf gets to the situation where it can't find the package in any mirror, that it will suspend that update and any associated updates but continue on with the rest of the updates that are available and check again with the next update to see if it can then find the "missing" package? It hasn't happened to me in a while, so I can't be certain. I think (grain of salt) if none of the downloaded package updates depend on packages not downloaded it will update those. Either way, it is harmless and will be sorted out in time. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/06/2021 07:06, Stephen Morris wrote: On 28/6/21 05:01, Samuel Sieb wrote: On 2021-06-27 4:28 a.m., Ed Greshko wrote: On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. system-update uses all the repos you have enabled, including the updates repo. After system-update, you should be fully up-to-date. What is system-update, is that functionality provided by another dnf plugin? That would be the command you'd use when upgrading to the next version Fedora when it becomes available. Yes, it is a dnf plugin. "sudo dnf install dnf-plugin-system-upgrade" https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ may be helpful when time to upgrade. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/6/21 04:59, Samuel Sieb wrote: On 2021-06-27 5:34 a.m., Stephen Morris wrote: On 27/6/21 22:23, Ed Greshko wrote: I have not had a situation where an update was performed and immediately followed by a need for another update. I do my updates with "dnf --refresh update". The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available. I attribute that to packageKit using different mirrors than dnf. I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? It's not that they use different mirrors. The mirror manager provides somewhat randomized mirrors when asked, so at different times, you can end up looking at different mirrors. And it's possible, if you check during the syncing time, that different mirrors have different available updates. I thought dnf had a list of mirrors and the first time dnf was run it used the first mirror in the list, and kept using that mirror until it got a 404 situation on a package whereby it would go to the next mirror and if the package was obtained from that mirror, it would continue using that mirror for all updates until that produced a 404 situation, in which case it would move to the next mirror and so on. I've been finding it nothing unusual for Discover monitoring process to tell me there were updates available, even after using dnf to put on all updates it can see, and go and issue a dnf upgrade and have dnf tell me there was nothing to do. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/6/21 22:52, Ed Greshko wrote: On 27/06/2021 20:45, Ed Greshko wrote: On 27/06/2021 20:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? Oh, dnf will "catch up" as more mirrors are synced. You'll never have a case where an update is available via PK but never becomes available when using dnf. While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. Hit send before I completed my thought. I think it "wise" to do as poc has done. Get rid of packageKit and plasma-discover. Running 2 update utilities can lead to confusion. Again with the fast finger. I always install dnfdragora-updater and use that for notifications of when package updates are available. But, I use dnf from the command line to do the actual update as I have an alias to do the update via dnf and that is easier than clicking on things and I like to see what is going on. I normally use dnf to apply updates and use dnfdragora to browse the repositories to see what is available and what might be useful to me. I haven't installed dnfdragora-updater (I had forgotten that was available) as yet, but I should as discover is notifying of updates. The only reason I went to Discover to check updates after putting on the updates that dnf provided, was I was once in a situation where I was trying to use a product that wasn't installed and I was given installation instructions to install it via Discover, but I couldn't find it in Discover nor dnf so I installed it via a flatpak (unfortunately I don't remember what the product was). regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/6/21 22:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? Oh, dnf will "catch up" as more mirrors are synced. You'll never have a case where an update is available via PK but never becomes available when using dnf. Thanks Ed, I thought that was the case but I was just checking. While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. I thought that might be the case. Because I was updating a large number of packages I was seeing this message around a dozen times on various packages. I am assuming that if dnf gets to the situation where it can't find the package in any mirror, that it will suspend that update and any associated updates but continue on with the rest of the updates that are available and check again with the next update to see if it can then find the "missing" package? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 28/6/21 05:01, Samuel Sieb wrote: On 2021-06-27 4:28 a.m., Ed Greshko wrote: On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. system-update uses all the repos you have enabled, including the updates repo. After system-update, you should be fully up-to-date. What is system-update, is that functionality provided by another dnf plugin? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: bind-chroot not duplicating my forward and reverse tables
On 6/26/21 7:27 PM, ToddAndMargo via users wrote:
On 6/25/21 12:24 AM, Tim via users wrote:
On Thu, 2021-06-24 at 21:04 -0700, ToddAndMargo via users wrote:
I am trying to clean up my bind-chroot forward and reverse files.
The goal is to have bind-chroot do its thing by duplicating
these two files over into
/var/named/chroot/var/named/slaves/
with the identical inodes like it does with named.root and
named.root.key:
Hang on... If you're wanting it to bring things from outside of the
chroot into it, what's the point of chrooting? You're breaking the
jail by doing that.
The old approach was you created all the files in the chroot, where
bind-chroot makes use of them. And, you have a link outside of the
chroot into it, so that *you* can edit /etc/named.something without
thinking about it. But, ultimately, you shouldn't need any files
outside of the chroot, at all. And there's probably some advantage in
just having one set (less confusing for you, at the very least).
Hi Tim,
Bing-chroot uses "mount --bind". It is not occurring
on my zone files.
For a good explanation, see
https://bugzilla.redhat.com/show_bug.cgi?id=1972022#c3
-T
I have moved my zone fines to /var/named
Mount bind still does not get them. I had to
manually copy them over.
zone "abc.local" {
type master;
# file "/var/named/chroot/var/named/abc.hosts";
file "abc.hosts";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
zone "255.168.192.in-addr.arpa" {
type master;
# file "/var/named/chroot/var/named/abc.hosts.rev";
file "abc.hosts.rev";
allow-update { key DHCP_UPDATER; };
# allow-update { 127.0.0.1; };
};
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: scilab
> On Jun 27, 2021, at 17:16, Patrick Dupre wrote: > > echo $LD_LIBRARY_PATH > /usr/lib64/gtk-3.0/modules > > but still > /usr/local/scilab-6.1.0/bin/scilab > Gtk-Message: 23:13:39.716: Failed to load module "pk-gtk-module" > > also: > /usr/local/scilab-6.1.0/bin/scilab-bin > > error while loading shared libraries: libscilab-cli.so.6: cannot open shared > object file: No such file or directory If you are building your own software outside of standard paths, you’ll either need to link with —rpath or set up your own LD_LIBRARY_PATH for wherever you installed your scilab libraries. Probably the same path as the executables, only in …/lib. This is a general Linux issue, not really a “Fedora” issue, per se. I use Lmod for environment modules for stuff like this, if I’m not packaging the software. — Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: packagekitd Hogging CPU
On Sun, 2021-06-27 at 12:33 -0600, Chris Murphy wrote: > On Wed, Jun 23, 2021, 3:44 AM Patrick O'Callaghan > > wrote: > > > > > > > Interesting. That sounds superficially similar to Android's A/B > > system > > update method. Is there work being done on getting this into > > Fedora? > > > > Folks are looking at multiple ways of doing it. All options imply > some kind > of layout change, and we need to consider upgrades. It has to work > for dnf > and PackageKit, etc. Thanks. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: scilab
echo $LD_LIBRARY_PATH /usr/lib64/gtk-3.0/modules but still /usr/local/scilab-6.1.0/bin/scilab Gtk-Message: 23:13:39.716: Failed to load module "pk-gtk-module" also: /usr/local/scilab-6.1.0/bin/scilab-bin error while loading shared libraries: libscilab-cli.so.6: cannot open shared object file: No such file or directory > Sent: Sunday, June 27, 2021 at 10:51 PM > From: "Samuel Sieb" > To: users@lists.fedoraproject.org > Subject: Re: scilab > > On 6/27/21 1:49 PM, John Mellor wrote: > > On 2021-06-27 9:18 a.m., Patrick Dupre wrote: > >> Hello, > >> > >> Trying to run scilab under fedora34 > >> '/usr/local/scilab-6.1.0/bin/scilab) from the files available on the > >> scilab > >> web site, I get > >> Gtk-Message: 15:06:56.350: Failed to load module "pk-gtk-module" > >> > >> dnf repoquery --whatprovides 'pk-gtk-module' > >> does not provide any information > >> > >> rpmfind provides > >> PackageKit-gtk3-module > >> (/usr/lib64/gnome-settings-daemon-3.0/gtk-modules/pk-gtk-module.desktop > >> /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so) > >> > >> Package PackageKit-gtk3-module-1.2.3-1.fc34.x86_64 is already installed > >> > >> I am not sure about what I should do > > > > That sounds like /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so is not > > in LD_LIBRARY_PATH. > > Or else the application included its own copy that isn't linking to > something else. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: background application
su, 2021-06-27 kello 12:58 -0700, Samuel Sieb kirjoitti: > > How do I manage these extensions? > > [...] In F34, there's a new Extensions app. Which is in the gnome-extensions-app package. As for what could be causing the issue with the Nextcloud client, one other thing I thought of is that there is a separate Nextcloud plugin for Nautilus in the nextcloud-client-nautilus package. Might be worth giving that a go if it isn't already installed. -- Terveisin / Regards, Matti Pulkkinen ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: scilab
On 6/27/21 1:49 PM, John Mellor wrote: On 2021-06-27 9:18 a.m., Patrick Dupre wrote: Hello, Trying to run scilab under fedora34 '/usr/local/scilab-6.1.0/bin/scilab) from the files available on the scilab web site, I get Gtk-Message: 15:06:56.350: Failed to load module "pk-gtk-module" dnf repoquery --whatprovides 'pk-gtk-module' does not provide any information rpmfind provides PackageKit-gtk3-module (/usr/lib64/gnome-settings-daemon-3.0/gtk-modules/pk-gtk-module.desktop /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so) Package PackageKit-gtk3-module-1.2.3-1.fc34.x86_64 is already installed I am not sure about what I should do That sounds like /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so is not in LD_LIBRARY_PATH. Or else the application included its own copy that isn't linking to something else. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: scilab
On 2021-06-27 9:18 a.m., Patrick Dupre wrote: Hello, Trying to run scilab under fedora34 '/usr/local/scilab-6.1.0/bin/scilab) from the files available on the scilab web site, I get Gtk-Message: 15:06:56.350: Failed to load module "pk-gtk-module" dnf repoquery --whatprovides 'pk-gtk-module' does not provide any information rpmfind provides PackageKit-gtk3-module (/usr/lib64/gnome-settings-daemon-3.0/gtk-modules/pk-gtk-module.desktop /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so) Package PackageKit-gtk3-module-1.2.3-1.fc34.x86_64 is already installed I am not sure about what I should do That sounds like /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so is not in LD_LIBRARY_PATH. Add it on the command line and run scilab from command line with it added. Let's see if that resolves the issue. -- John Mellor ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
slow startup process and dmesg times
hello, I am looking at output from dmesg on my laptop and there appears to be a time when a process takes longer than what might be expected and I think this may be reducing my startup speed. My question is, is it normal for there to be a jump in time (timestamp) from 7 seconds to 18 seconds. And then from 21 seconds to 30 seconds? Are these processes slowing down my startup? dmesg output: https://pastebin.com/HhDyURjd thank you. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: background application
On 2021-06-27 12:50 p.m., Patrick Dupre wrote: This is exactly right. I am using gnome. Now, I installed gnome-shell-extension-appindicator but I do not see any difference concerning nextcloud. How do I manage these extensions? In F33, use gnome-tweaks. In F34, there's a new Extensions app. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: background application
This is exactly right. I am using gnome. Now, I installed gnome-shell-extension-appindicator but I do not see any difference concerning nextcloud. How do I manage these extensions? > On 2021-06-27 7:40 a.m., Matti Pulkkinen wrote: > > su, 2021-06-27 kello 09:23 +0200, Patrick Dupre kirjoitti: > >> Thanks for the suggestions. > >> > >> Indeed, the behavior of nextcloud is a bit strange > >> I was wrong it is not launched when the machine is turned on. > >> The user launches it, but the interface disappear as soon as the mouse > >> is moved > >> away, but the application still run. It make difficult to interact with > >> the application. > >> Another call is necessary, and I get > >> nextcloud.gui.application: Already running, exiting... > >> > > > > Are you using Gnome? If so, do you have the appindicator extension[1] > > or something like it installed? I vaguely remember the Nextcloud client > > just opening its little drop-down menu if the program is started with > > no system tray available. When that window closes, the program is left > > running in the background with no way for the user to get at it > > graphically. After installing a system tray extension, the client > > started working properly again. Things may have changed as the client > > seems to be better integrated into Gnome now, but installing the > > extension might be worth a shot anyway. > > > > [1] https://github.com/ubuntu/gnome-shell-extension-appindicator > > I use gnome-shell-extension-topicons-plus which is packaged in Fedora. > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: background application
On 2021-06-27 7:40 a.m., Matti Pulkkinen wrote: su, 2021-06-27 kello 09:23 +0200, Patrick Dupre kirjoitti: Thanks for the suggestions. Indeed, the behavior of nextcloud is a bit strange I was wrong it is not launched when the machine is turned on. The user launches it, but the interface disappear as soon as the mouse is moved away, but the application still run. It make difficult to interact with the application. Another call is necessary, and I get nextcloud.gui.application: Already running, exiting... Are you using Gnome? If so, do you have the appindicator extension[1] or something like it installed? I vaguely remember the Nextcloud client just opening its little drop-down menu if the program is started with no system tray available. When that window closes, the program is left running in the background with no way for the user to get at it graphically. After installing a system tray extension, the client started working properly again. Things may have changed as the client seems to be better integrated into Gnome now, but installing the extension might be worth a shot anyway. [1] https://github.com/ubuntu/gnome-shell-extension-appindicator I use gnome-shell-extension-topicons-plus which is packaged in Fedora. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 2021-06-27 4:28 a.m., Ed Greshko wrote: On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. system-update uses all the repos you have enabled, including the updates repo. After system-update, you should be fully up-to-date. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 2021-06-27 5:34 a.m., Stephen Morris wrote: On 27/6/21 22:23, Ed Greshko wrote: I have not had a situation where an update was performed and immediately followed by a need for another update. I do my updates with "dnf --refresh update". The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available. I attribute that to packageKit using different mirrors than dnf. I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? It's not that they use different mirrors. The mirror manager provides somewhat randomized mirrors when asked, so at different times, you can end up looking at different mirrors. And it's possible, if you check during the syncing time, that different mirrors have different available updates. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: packagekitd Hogging CPU
On Wed, Jun 23, 2021, 3:44 AM Patrick O'Callaghan wrote: > > > Interesting. That sounds superficially similar to Android's A/B system > update method. Is there work being done on getting this into Fedora? > Folks are looking at multiple ways of doing it. All options imply some kind of layout change, and we need to consider upgrades. It has to work for dnf and PackageKit, etc. -- Chris Murphy > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: background application
su, 2021-06-27 kello 09:23 +0200, Patrick Dupre kirjoitti: > Thanks for the suggestions. > > Indeed, the behavior of nextcloud is a bit strange > I was wrong it is not launched when the machine is turned on. > The user launches it, but the interface disappear as soon as the mouse > is moved > away, but the application still run. It make difficult to interact with > the application. > Another call is necessary, and I get > nextcloud.gui.application: Already running, exiting... > Are you using Gnome? If so, do you have the appindicator extension[1] or something like it installed? I vaguely remember the Nextcloud client just opening its little drop-down menu if the program is started with no system tray available. When that window closes, the program is left running in the background with no way for the user to get at it graphically. After installing a system tray extension, the client started working properly again. Things may have changed as the client seems to be better integrated into Gnome now, but installing the extension might be worth a shot anyway. [1] https://github.com/ubuntu/gnome-shell-extension-appindicator -- Terveisin / Regards, Matti Pulkkinen ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
scilab
Hello, Trying to run scilab under fedora34 '/usr/local/scilab-6.1.0/bin/scilab) from the files available on the scilab web site, I get Gtk-Message: 15:06:56.350: Failed to load module "pk-gtk-module" dnf repoquery --whatprovides 'pk-gtk-module' does not provide any information rpmfind provides PackageKit-gtk3-module (/usr/lib64/gnome-settings-daemon-3.0/gtk-modules/pk-gtk-module.desktop /usr/lib64/gtk-3.0/modules/libpk-gtk-module.so) Package PackageKit-gtk3-module-1.2.3-1.fc34.x86_64 is already installed I am not sure about what I should do === Patrick DUPRÉ | | email: pdu...@gmx.com Laboratoire interdisciplinaire Carnot de Bourgogne 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE Tel: +33 (0)380395988| | Room# D114A === ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/06/2021 20:45, Ed Greshko wrote: On 27/06/2021 20:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? Oh, dnf will "catch up" as more mirrors are synced. You'll never have a case where an update is available via PK but never becomes available when using dnf. While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. Hit send before I completed my thought. I think it "wise" to do as poc has done. Get rid of packageKit and plasma-discover. Running 2 update utilities can lead to confusion. Again with the fast finger. I always install dnfdragora-updater and use that for notifications of when package updates are available. But, I use dnf from the command line to do the actual update as I have an alias to do the update via dnf and that is easier than clicking on things and I like to see what is going on. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/06/2021 20:43, Ed Greshko wrote: On 27/06/2021 20:34, Stephen Morris wrote: I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? Oh, dnf will "catch up" as more mirrors are synced. You'll never have a case where an update is available via PK but never becomes available when using dnf. While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. Hit send before I completed my thought. I think it "wise" to do as poc has done. Get rid of packageKit and plasma-discover. Running 2 update utilities can lead to confusion. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/06/2021 20:34, Stephen Morris wrote: I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? Oh, dnf will "catch up" as more mirrors are synced. You'll never have a case where an update is available via PK but never becomes available when using dnf. While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? It gets the 404 error since it uses curl to download. I see no way to avoid what you've seen. It happens only occasionally so I never thought about it. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/6/21 22:30, Ed Greshko wrote: On 27/06/2021 20:24, Stephen Morris wrote: On 27/6/21 21:28, Ed Greshko wrote: On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. So, it would be a much simpler process to upgrade from the released repo and then do normal updates later. I have always used dnf upgrade for normal updates. From what I've found dnf update and dnf upgrade do the same thing and apply updates/installs from all active repositories, or is there a difference between the two? No, they do the same thing. I misunderstood your original post. Mostly because that upgrade/update are used interchangeably. I thought you were speaking of "dnf system-upgrade" No problems, it's all good. regards, Steve I only looked at discover because I was looking at trying to use a package that wasn't installed, and I was told to use Discover to install it (I don't remember which package is was and I couldn't find how to install it from Discover, so I finished up using flatpak). OK. Well in that case nothing can be speculated. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/6/21 22:23, Ed Greshko wrote: On 27/06/2021 20:00, Patrick O'Callaghan wrote: On Sun, 2021-06-27 at 18:31 +1000, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all done to alleviate this that is not done in an "out of the box" install, should be using Discovery instead? I think plasma-discover uses PackageKit. As has been noted several times here, mixing dnf and PK often leads to confusion. Better pick one and stick with it. Personally, I erased PK and don't use plasma-discover, and I don't see these kinds of problem. I probably misunderstood the OP. I haven't (yet) banished packageKit from my system. I have not had a situation where an update was performed and immediately followed by a need for another update. I do my updates with "dnf --refresh update". The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available. I attribute that to packageKit using different mirrors than dnf. I hadn't realised Discover was using Packagekit. If it is using different mirrors to dnf and they indicate they have updates over and above what dnf has applied, does that mean dnf will catch up, or are they updates that dnf will never put on because it never sees them? While we are on the topic of updates with dnf, I have noticed that when dnf goes to a mirror to find an update, if it can't find the package it produces a 404 error, and keeps producing that error when it goes to the next mirror, etc. Is there any way to get dnf to only produce the 404 error if the required package can't be found in any mirror? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/06/2021 20:24, Stephen Morris wrote: On 27/6/21 21:28, Ed Greshko wrote: On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. So, it would be a much simpler process to upgrade from the released repo and then do normal updates later. I have always used dnf upgrade for normal updates. From what I've found dnf update and dnf upgrade do the same thing and apply updates/installs from all active repositories, or is there a difference between the two? No, they do the same thing. I misunderstood your original post. Mostly because that upgrade/update are used interchangeably. I thought you were speaking of "dnf system-upgrade" I only looked at discover because I was looking at trying to use a package that wasn't installed, and I was told to use Discover to install it (I don't remember which package is was and I couldn't find how to install it from Discover, so I finished up using flatpak). OK. Well in that case nothing can be speculated. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/6/21 21:28, Ed Greshko wrote: On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. So, it would be a much simpler process to upgrade from the released repo and then do normal updates later. I have always used dnf upgrade for normal updates. From what I've found dnf update and dnf upgrade do the same thing and apply updates/installs from all active repositories, or is there a difference between the two? I only looked at discover because I was looking at trying to use a package that wasn't installed, and I was told to use Discover to install it (I don't remember which package is was and I couldn't find how to install it from Discover, so I finished up using flatpak). regards, Steve Hey, at least it isn't like Windows. I have a Windows 10 VM that I rarely use. When I do use it, and updates are applied, it is a constant cycle of "Download updates, apply updates, reboot" and rinse/repeat ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/06/2021 20:00, Patrick O'Callaghan wrote: On Sun, 2021-06-27 at 18:31 +1000, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all done to alleviate this that is not done in an "out of the box" install, should be using Discovery instead? I think plasma-discover uses PackageKit. As has been noted several times here, mixing dnf and PK often leads to confusion. Better pick one and stick with it. Personally, I erased PK and don't use plasma-discover, and I don't see these kinds of problem. I probably misunderstood the OP. I haven't (yet) banished packageKit from my system. I have not had a situation where an update was performed and immediately followed by a need for another update. I do my updates with "dnf --refresh update". The only thing I've seen is when packageKit is telling me there are updates but when dnf runs it says no updates are available. I attribute that to packageKit using different mirrors than dnf. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On Sun, 2021-06-27 at 18:31 +1000, Stephen Morris wrote: > Hi, > I have just done a sudo dnf upgrade on F34 which I think > upgraded > 1311 packages. After the update finished I rebooted F34 and then ran > discovery and it was still telling me there was 628 MB of F34 > Platform > updates to put on, which I did put on. Why is dnf not installing all > done to alleviate this that is not done in an "out of the box" > install, > should be using Discovery instead? I think plasma-discover uses PackageKit. As has been noted several times here, mixing dnf and PK often leads to confusion. Better pick one and stick with it. Personally, I erased PK and don't use plasma-discover, and I don't see these kinds of problem. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/06/2021 16:31, Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? I've not looked at what goes on during the upgrade process. That is going from a previous release of Fedora to a later version of Fedora. I suspect that the upgrade process just compares what you have on your system with what packages are available in the fedora.repo (which doesn't change) and doesn't look at the fedora-updates.repo since looking in both places and keeping track of what package should be upgraded from which repo would be much more work. Especially in the case of where an update of some packages may change dependencies or pull in packages not used previously. So, it would be a much simpler process to upgrade from the released repo and then do normal updates later. Hey, at least it isn't like Windows. I have a Windows 10 VM that I rarely use. When I do use it, and updates are applied, it is a constant cycle of "Download updates, apply updates, reboot" and rinse/repeat -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 27/06/2021 16:53, Samuel Sieb wrote: On 2021-06-27 1:31 a.m., Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? What is "Discovery"? It is actually "discover". But it is launched as plasma-discover. And is Description : KDE and Plasma resources management GUI a.k.a. "Software Center" I never use it. -- Remind me to ignore comments which aren't germane to the thread. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
rpmbuild
Hello,
I am trying to generate a rpm package from the sources of
perl-PDL-Graphics-PLplot-0.72
I run cpanspec to generate the .spec file (see below) and I get.
setting SOURCE_DATE_EPOCH=1624752000
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.iQt9av
+ umask 022
+ cd /home/pdupre/rpmbuild/BUILD
+ cd /home/pdupre/rpmbuild/BUILD
+ rm -rf PDL-Graphics-PLplot-0.72
+ /usr/bin/gzip -dc
/home/pdupre/rpmbuild/SOURCES/PDL-Graphics-PLplot-0.72.tar.gz
+ /usr/bin/tar -xof -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd PDL-Graphics-PLplot-0.72
+ /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.ADwt9P
+ umask 022
+ cd /home/pdupre/rpmbuild/BUILD
+ cd PDL-Graphics-PLplot-0.72
+ /usr/bin/perl Makefile.PL INSTALLDIRS=vendor 'OPTIMIZE=-O2 -flto=auto
-ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall
-Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
PDL is installed
Bad value support required! (Turn on WITH_BADVAL in perldl.conf)
Not building PDL::Graphics::PLplot
Bad value support required! (Turn on WITH_BADVAL in perldl.conf) Not
building PDL::Graphics::PLplot
Checking if your kit is complete...
Looks good
+ make -j4
make: Nothing to be done for 'all'.
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.VQPCoW
+ umask 022
+ cd /home/pdupre/rpmbuild/BUILD
+ '['
/home/pdupre/rpmbuild/BUILDROOT/perl-PDL-Graphics-PLplot-0.72-1.fc34.x86_64
'!=' / ']'
+ rm -rf
/home/pdupre/rpmbuild/BUILDROOT/perl-PDL-Graphics-PLplot-0.72-1.fc34.x86_64
++ dirname
/home/pdupre/rpmbuild/BUILDROOT/perl-PDL-Graphics-PLplot-0.72-1.fc34.x86_64
+ mkdir -p /home/pdupre/rpmbuild/BUILDROOT
+ mkdir
/home/pdupre/rpmbuild/BUILDROOT/perl-PDL-Graphics-PLplot-0.72-1.fc34.x86_64
+ cd PDL-Graphics-PLplot-0.72
+ rm -rf
/home/pdupre/rpmbuild/BUILDROOT/perl-PDL-Graphics-PLplot-0.72-1.fc34.x86_64
+ make pure_install
PERL_INSTALL_ROOT=/home/pdupre/rpmbuild/BUILDROOT/perl-PDL-Graphics-PLplot-0.72-1.fc34.x86_64
make: *** No rule to make target 'pure_install'. Stop.
error: Bad exit status from /var/tmp/rpm-tmp.VQPCoW (%install)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.VQPCoW (%install)
any idea?
spec file
Name: perl-PDL-Graphics-PLplot
Version:0.72
Release:1%{?dist}
Summary:PDL::Graphics::PLplot Perl module
License:CHECK(Distributable)
Group: Development/Libraries
URL:http://search.cpan.org/dist/PDL-Graphics-PLplot/
Source0:
http://www.cpan.org/modules/by-module/PDL/PDL-Graphics-PLplot-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
BuildRequires: perl(ExtUtils::MakeMaker)
Requires: perl(:MODULE_COMPAT_%(eval "`%{__perl} -V:version`"; echo
$version))
%description
The interface consists of two levels. A low level interface which maps
closely to the PLplot C interface, and a high level, object-oriented
interface which is easier to use.
%prep
%setup -q -n PDL-Graphics-PLplot-%{version}
%build
%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE="$RPM_OPT_FLAGS"
make %{?_smp_mflags}
%install
rm -rf $RPM_BUILD_ROOT
make pure_install PERL_INSTALL_ROOT=$RPM_BUILD_ROOT
find $RPM_BUILD_ROOT -type f -name .packlist -exec rm -f {} \;
find $RPM_BUILD_ROOT -type f -name '*.bs' -size 0 -exec rm -f {} \;
find $RPM_BUILD_ROOT -depth -type d -exec rmdir {} 2>/dev/null \;
%{_fixperms} $RPM_BUILD_ROOT/*
%check
make test
%clean
rm -rf $RPM_BUILD_ROOT
%files
%defattr(-,root,root,-)
%doc Changes META.json plplot.pd README
%{perl_vendorarch}/auto/*
%{perl_vendorarch}/PDL*
%{_mandir}/man3/*
%changelog
* Sun Jun 27 2021 Patrick Dupre 0.72-1
- Specfile autogenerated by cpanspec 1.78.
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988| | Room# D114A
===
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: DNF not Installing all Updates?
On 2021-06-27 1:31 a.m., Stephen Morris wrote: Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? What is "Discovery"? ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
DNF not Installing all Updates?
Hi, I have just done a sudo dnf upgrade on F34 which I think upgraded 1311 packages. After the update finished I rebooted F34 and then ran discovery and it was still telling me there was 628 MB of F34 Platform updates to put on, which I did put on. Why is dnf not installing all updates that are available? Is there a configuration that needs to be done to alleviate this that is not done in an "out of the box" install, or, is this telling me that we shouldn't be doing updates with dnf we should be using Discovery instead? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: background application
Thanks for the suggestions. Indeed, the behavior of nextcloud is a bit strange I was wrong it is not launched when the machine is turned on. The user launches it, but the interface disappear as soon as the mouse is moved away, but the application still run. It make difficult to interact with the application. Another call is necessary, and I get nextcloud.gui.application: Already running, exiting... === Patrick DUPRÉ | | email: pdu...@gmx.com === > > > Actually, this is exactly what I did. But this application is not listed. > > May be a systemd "user" service. Take a look at > > systemctl --user list-unit-files > > and see if something like nextcloud is listed (you can disable it > with systemctl --user disable ...). > > Some other possibilities are covered in my web page at: > > https://tomhorsley.com/game/punch.html > > The find-xdg script is useful (for me, anyway). > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
