Re: rawhide and f41 build errors.

Never mind... export LC_ALL="C.UTF-8" took care of the failure... steved. On 11/11/24 1:02 PM, Steve Dickson wrote: On 11/10/24 11:56 AM, Kevin Fenzi wrote: On Sat, Nov 09, 2024 at 12:07:09PM -0600, Steve Dickson wrote: Hello, Out of the blue rawhide scratch builds [1] are n

Re: rawhide and f41 build errors.

On 11/10/24 11:56 AM, Kevin Fenzi wrote: On Sat, Nov 09, 2024 at 12:07:09PM -0600, Steve Dickson wrote: Hello, Out of the blue rawhide scratch builds [1] are now failing and f41 builds [2] are failing but f40 builds [3] are succeeding and they are all the same code! Late Oct I made a

rawhide and f41 build errors.

Hello, Out of the blue rawhide scratch builds [1] are now failing and f41 builds [2] are failing but f40 builds [3] are succeeding and they are all the same code! Late Oct I made a release so their repo heads are all the same. Does anybody know what has changed in the building process? Or bette

Re: RPM build warning

On 7/23/24 5:04 PM, Elliott Sales de Andrade wrote: On Tue, Jul 23, 2024 at 4:56 PM Steve Dickson wrote: On 7/23/24 4:36 PM, Zbigniew Jędrzejewski-Szmek wrote: On Tue, Jul 23, 2024 at 04:31:31PM -0400, Steve Dickson wrote: Hello I've got the following warning RPM build war

Re: RPM build warning

On 7/23/24 4:36 PM, Zbigniew Jędrzejewski-Szmek wrote: On Tue, Jul 23, 2024 at 04:31:31PM -0400, Steve Dickson wrote: Hello I've got the following warning RPM build warnings: source_date_epoch_from_changelog set but %changelog is missing The spec file definitely has a %chan

RPM build warning

Hello I've got the following warning RPM build warnings: source_date_epoch_from_changelog set but %changelog is missing The spec file definitely has a %changelog section. What is it the warning about? tia, steved. -- ___ devel mailing list -- d

Re: scratch build error.

avoid the need to call pkg-config. See the pkg-config man page for more details. error: Bad exit status from /var/tmp/rpm-tmp.ercgmY (%build)     Bad exit status from /var/tmp/rpm-tmp.ercgmY (%build) RPM build errors: Child return code was: 1 On 6/29/24 19:48, Steve Dickson wrote: Hello, My

scratch build error.

Hello, My apologies if this has been already discussed, I don't follow this email list as closely as I should so please point to the previous discussion, if there is one. I'm getting the following rawhide scratch build error [1] which appears to be a mock build error [2] that is not part of the

Re: Lost KDC for FEDORAPROJECT.ORG realm

On 1/23/24 10:13 AM, Miro Hrončok wrote: On 23. 01. 24 16:08, Steve Dickson wrote: Hello, I had to change my /etc/krb5.conf do to some realm changes... and now when I to a kinit to FEDORAPROJECT.ORG  it hangs for a while then errors with kinit: Cannot contact any KDC for realm

Re: Lost KDC for FEDORAPROJECT.ORG realm

On 1/23/24 10:08 AM, Steve Dickson wrote: Hello, I had to change my /etc/krb5.conf do to some realm changes... and now when I to a kinit to FEDORAPROJECT.ORG  it hangs for a while then errors with kinit: Cannot contact any KDC for realm 'FEDORAPROJECT.ORG' while getting initial c

Lost KDC for FEDORAPROJECT.ORG realm

Hello, I had to change my /etc/krb5.conf do to some realm changes... and now when I to a kinit to FEDORAPROJECT.ORG it hangs for a while then errors with kinit: Cannot contact any KDC for realm 'FEDORAPROJECT.ORG' while getting initial credentials My question is, what has to be in the /etc/k

Re: xmlParseMemory() and xmlParseMemory gone rawhide?

On 11/18/23 12:39 PM, Dan Horák wrote: On Sat, 18 Nov 2023 12:30:04 -0500 Steve Dickson wrote: Hello, When building an nfs-utils rpm in rawhide I get the following errors: xml.c: In function ‘junction_parse_xml_buf’: xml.c:293:15: error: implicit declaration of function ‘xmlParseMemory

xmlParseMemory() and xmlParseMemory gone rawhide?

Hello, When building an nfs-utils rpm in rawhide I get the following errors: xml.c: In function ‘junction_parse_xml_buf’: xml.c:293:15: error: implicit declaration of function ‘xmlParseMemory’ [-Werror=implicit-function-declaration] 293 | tmp = xmlParseMemory(buf, (int)len); |

Re: FEDORA-2023-ed0c57b4ba — unspecified update for libtirpc — Fedora Updates System

On 10/25/23 12:20 PM, Adam Williamson wrote: On Wed, 2023-10-25 at 12:03 -0400, Steve Dickson wrote: Hello, This update failed [1] due to a system timeout [2] not a test failure... Is there some way to override or wave the failure. Failed tests are automatically retried one time. However

FEDORA-2023-ed0c57b4ba — unspecified update for libtirpc — Fedora Updates System

Hello, This update failed [1] due to a system timeout [2] not a test failure... Is there some way to override or wave the failure. tia, steved. [1] https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed0c57b4ba [2] https://openqa.fedoraproject.org/tests/2225991# __

Re: python3 build failure

On 7/20/23 2:09 PM, Yaakov Selkowitz wrote: On Thu, 2023-07-20 at 13:59 -0400, Steve Dickson wrote: This bz[1] was opened on one of my packages not building on f39. I did a quick rawhide scratch build and sure enough the build fails with [2] The important part is earlier in the log

python3 build failure

Hello, This bz[1] was opened on one of my packages not building on f39. I did a quick rawhide scratch build and sure enough the build fails with [2] Traceback (most recent call last): File "/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py", line 93, in trace result = func(

strange python3 mock error

Hello, I'm getting a very strange mock error [1] on a package [2] that was recently ported to python 3. The package builds fine locally... only fails in a scratch build... and that function that the error is c complaining about does not exist in the package... Not clear what to do... tia! stev

What happen kup in Fedora 37

Hello, I'm trying to access kernel.org with kup script but it does not seem to be in Fedora 37. The only rpm I can find is kup-0.3.6-11.fc36.rpm. What am I missing?? steved. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send

Re: Strange RPM build warning

On 2/28/23 12:37 PM, Chuck Anderson wrote: February is abbreviated as "Fed" in the first changelog entry: * Tue Fed 28 2023 Steve Dickson 1.2.6-4.rc2 - Updated to latest upstream RC release: rpcbind-1_2_7-rc2 Yup! That was the problem... Thank you for your time!!! steved. On T

Re: Strange RPM build warning

On 2/28/23 12:37 PM, Miro Hrončok wrote: On 28. 02. 23 18:33, Steve Dickson wrote: On 2/28/23 12:12 PM, Miro Hrončok wrote: On 28. 02. 23 17:43, Steve Dickson wrote: Hello, I'm getting this warning RPM build warnings: source_date_epoch_from_changelog set but %changelog is mi

Re: Strange RPM build warning

On 2/28/23 12:12 PM, Miro Hrončok wrote: On 28. 02. 23 17:43, Steve Dickson wrote: Hello, I'm getting this warning RPM build warnings: source_date_epoch_from_changelog set but %changelog is missing But the %changelog is not missing... Any ideas? Could you please share the spec

Strange RPM build warning

Hello, I'm getting this warning RPM build warnings: source_date_epoch_from_changelog set but %changelog is missing But the %changelog is not missing... Any ideas? tia, steved. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscri

gaps test failed

Hello, My update [1] failed because the gaps test failed sbin/mount.nfs: gap: (0x5590..0x55a0 probable component: __printf_chk) in annobin notes. /sbin/mount.nfs: gap: (0x11760..0x11770 probable component: __printf_chk) in annobin notes. /sbin/mount.nfs: FAIL: gaps test because gaps were det

Re: PSA: koji armv7hl builders locking up

On 8/7/22 3:49 PM, Kevin Fenzi wrote: Or just wait... I have been checking them a few times a day and rebooting any that are locked up. How long do we have to wait? [1] has been stuck since Mon, 08 Aug 2022 14:17:44 UTC steved. [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=90612742

nfs4-acl-tools

Hello, I just took over the maintership of nfs4-acl-tools and it appears the command has not been part of Fedora since f32. Granted there has not been any upstream activity until now, but is there a way to get back into, at least, rawhide? tia, steved. _

Maintainer Change

Hello, I'm taking over the maintainership of a package. In the past I would access the pkgdb via a link similar to [1] to change ACLs that link no longer exists How is this done these days? tia, steved. [1] https://admin.fedoraproject.org/pkgdb/acls/name/

Re: sign_and_send_pubkey: signing failed for RSA

FAULT on both machines. Cheers, Chris On Wed, 27 Oct 2021 at 12:11, Petr Pisar <mailto:ppi...@redhat.com>> wrote: V Tue, Oct 26, 2021 at 01:31:31PM -0400, Steve Dickson napsal(a): > A very strange problem... on one of my fedora > build machine I'm get

sign_and_send_pubkey: signing failed for RSA

Hello, A very strange problem... on one of my fedora build machine I'm getting the following error when I do a git pull $ git pull sign_and_send_pubkey: signing failed for RSA "/home/steved/.ssh/id_rsa" from agent: agent refused operation ste...@pkgs.fedoraproject.org: Permission denied (publi

1974358 – Review Request: fdr - Flight Data Recorder

Hello, Anybody interested in doing a "review swap" or just a review?? Here is my review request [1]. I would like to get this into f35. tia, steved. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1974358 ___ devel mailing list -- devel@lists.fedorap

Re: git push on master branch rejected.

On 2/22/21 9:31 AM, Steve Dickson wrote: > > > On 2/22/21 9:28 AM, Steve Dickson wrote: >> >> >> On 2/22/21 2:39 AM, Pierre-Yves Chibon wrote: >>> On Sun, Feb 21, 2021 at 05:21:33PM -0500, Steve Dickson wrote: >>>> >>>> Thanks you

Re: git push on master branch rejected.

On 2/22/21 9:28 AM, Steve Dickson wrote: > > > On 2/22/21 2:39 AM, Pierre-Yves Chibon wrote: >> On Sun, Feb 21, 2021 at 05:21:33PM -0500, Steve Dickson wrote: >>> >>> Thanks you for your rapid reply! >>> >>> On 2/21/21 4:57 PM, Michael Y

Re: git push on master branch rejected.

On 2/22/21 2:39 AM, Pierre-Yves Chibon wrote: > On Sun, Feb 21, 2021 at 05:21:33PM -0500, Steve Dickson wrote: >> >> Thanks you for your rapid reply! >> >> On 2/21/21 4:57 PM, Michael Young wrote: >>> On Sun, 21 Feb 2021, Steve Dickson wrote: >>>

Re: git push on master branch rejected.

Thanks you for your rapid reply! On 2/21/21 4:57 PM, Michael Young wrote: > On Sun, 21 Feb 2021, Steve Dickson wrote: > >> I apologies if I missed something... If there is a >> thread that talks about this please point me at it >> but... >> >> when I do a

git push on master branch rejected.

Hello, I apologies if I missed something... If there is a thread that talks about this please point me at it but... when I do a git push on the master branch I get: $ git push Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 12 threads Compressing

Re: Don't update to the latest f33!

On 2/17/21 6:55 PM, Ed Greshko wrote: > On 18/02/2021 05:11, Steve Dickson wrote: >> I agree... ignoring syntax error or parsing error just does not seem >> like the appropriate thing to do... Error out! Tell me what is broken >> so I can fix it!! > > Replace th

Re: Don't update to the latest f33!

On 2/16/21 9:03 AM, Ed Greshko wrote: > On 16/02/2021 21:37, Steve Dickson wrote: >> >> On 2/15/21 9:16 PM, Dominique Martinet wrote: >>> Steve Dickson wrote on Mon, Feb 15, 2021 at 09:04:52PM -0500: >>>>> I think if no IP was successfully parsed the fal

Re: Don't update to the latest f33!

On 2/16/21 9:02 AM, Troy Curtis Jr wrote: > > > On Mon, Feb 15, 2021 at 10:02 PM Dominique Martinet > wrote: > > Michael Catanzaro wrote on Mon, Feb 15, 2021 at 08:46:57PM -0600: > > We removed the fallbacks due to complaints from users who didn't want

Re: Don't update to the latest f33!

On 2/16/21 6:05 AM, David Both wrote: > This situation is due to the change from the old resolver to the new > systemd-resolved. > > I have a page on my technical web site that describes the problem and the > circumvention. > > http://www.linux-databook.info/?page_id=5951 > > This does not,

Re: Don't update to the latest f33!

On 2/15/21 9:16 PM, Dominique Martinet wrote: > Steve Dickson wrote on Mon, Feb 15, 2021 at 09:04:52PM -0500: >>> I think if no IP was successfully parsed the fallback ought to kick in, >>> so it's a systemd-resolved bug -- do you want to report this upstream or >&

Re: Don't update to the latest f33!

On 2/15/21 8:53 PM, Dominique Martinet wrote: > Hi Steve, > > Steve Dickson wrote on Mon, Feb 15, 2021 at 08:40:17PM -0500: >> When I have DNS=67.207.67.3,67.207.67.2 I get > > FWIW the man page states it is a space-separated list of IPs, you might > want to try DNS=

Re: Don't update to the latest f33!

On 2/15/21 8:16 PM, Ed Greshko wrote: > On 16/02/2021 09:10, Steve Dickson wrote: >> On 2/15/21 7:55 PM, Ed Greshko wrote: >>> On 16/02/2021 08:50, Steve Dickson wrote: >>>> But I think this is the problem... >>>> >>>> systemctl start

Re: Don't update to the latest f33!

On 2/15/21 7:55 PM, Ed Greshko wrote: > On 16/02/2021 08:50, Steve Dickson wrote: >> But I think this is the problem... >> >> systemctl start systemd-resolved >> systemctl -o cat status systemd-resolved >> Starting Network Name Resolution... >> Posit

Re: Don't update to the latest f33!

On 2/15/21 7:31 PM, Ed Greshko wrote: > I think I may have sent this off-list > > On 16/02/2021 08:17, Steve Dickson wrote: >> On 2/15/21 7:12 PM, Ed Greshko wrote: >>> On 16/02/2021 06:40, Steve Dickson wrote: >>>> I just updated to latest Fedora 33 an

Re: Don't update to the latest f33!

On 2/15/21 7:25 PM, Sam Varshavchik wrote: >> # cat /run/NetworkManager/no-stub-resolv.conf >> cat: /run/NetworkManager/no-stub-resolv.conf: No such file or directory >> >> Who is suppose to create that? It is on /run so it be created on every >> reboot... > > NetworkManager. Maybe you have /ru

Re: Don't update to the latest f33!

On 2/15/21 7:24 PM, Ed Greshko wrote: > On 16/02/2021 08:17, Steve Dickson wrote: >> On 2/15/21 7:12 PM, Ed Greshko wrote: >>> On 16/02/2021 06:40, Steve Dickson wrote: >>>> I just updated to latest Fedora 33 and >>>> I no longer have any DNS na

Re: Don't update to the latest f33!

On 2/15/21 7:12 PM, Ed Greshko wrote: > On 16/02/2021 06:40, Steve Dickson wrote: >> I just updated to latest Fedora 33 and >> I no longer have any DNS name solution. >> The network is up... but... >> >> $ pingwww.yahoo.com >> ping:www.yahoo.com: Name or se

Re: Don't update to the latest f33!

On 2/15/21 6:19 PM, Sam Varshavchik wrote: > Steve Dickson writes: > >> Hello, >> >> I just updated to latest Fedora 33 and >> I no longer have any DNS name solution. >> The network is up... but... >> >> $ ping www.yahoo.com >> ping: ww

Re: Don't update to the latest f33!

On 2/15/21 6:00 PM, Stephen John Smoogen wrote: > > > On Mon, 15 Feb 2021 at 17:39, Steve Dickson <mailto:ste...@redhat.com>> wrote: > > Hello, > > I just updated to latest Fedora 33 and > I no longer have any DNS name solution. > The net

Don't update to the latest f33!

Hello, I just updated to latest Fedora 33 and I no longer have any DNS name solution. The network is up... but... $ ping www.yahoo.com ping: www.yahoo.com: Name or service not known I changed nothing! How would be the bet way to debug this??? steved. ___

Re: Serial Console with Fedora 33

Hello On 12/13/20 7:35 PM, Sérgio Basto wrote: > ~]# grubby --remove-args="rhgb quiet" --args=console=ttyS0,115200 -- > update-kernel /boot/vmlinuz-4.2.0-1.fc23.x86_64 This worked... thanks! > > > This command removes the Red Hat graphical boot argument, enables > boot message to be seen, and

Serial Console with Fedora 33

Hello, How does one set up a serial console with F33? In the past I would edit kernelopts with grub2-editenv and set "console=tty0 console=ttyS0,115200n8". As well as set the following in /etc/grub2.conf terminal_output console #set timeout=5 serial --unit=0 --speed=115200 --word=8 --parity=no -

Re: Failed to pair: org.bluez.Error.AuthenticationFailed

On 12/8/20 2:39 PM, Steve Dickson wrote: > > > On 12/8/20 8:11 AM, Steve Dickson wrote: >> Hello, >> >> I realize this is probably not the most appropriate list >> to ask this question... but >> >> I have a pair of Jabra Elite 45h headphones that

Re: Failed to pair: org.bluez.Error.AuthenticationFailed

On 12/8/20 10:28 AM, José Abílio Matos wrote: > But is it a problem of the kernel or the daemon? > Its a kernel problem... On the 5-9 kernel I tried bluez-5.53, bluez-5.54, bluez-5.5 all failed with Connection refused (111) Then I tried bluez-5.5 on the last 5.8 kernel (5.8.18-300.fc33)... ever

Re: Failed to pair: org.bluez.Error.AuthenticationFailed

On 12/8/20 8:11 AM, Steve Dickson wrote: > Hello, > > I realize this is probably not the most appropriate list > to ask this question... but > > I have a pair of Jabra Elite 45h headphones that > was working just fine until I updated to Fedora 33. > > When I try

Re: Failed to pair: org.bluez.Error.AuthenticationFailed

On 12/8/20 10:28 AM, José Abílio Matos wrote: > Clearly I am stealing the thread but I also have a problem with bluetooth in > Fedora 33 and I unable to point what is the problem. > > > I have followed the instruction at > > https://fedoraproject.org/wiki/How_to_debug_Bluetooth_problems Using

Re: Failed to pair: org.bluez.Error.AuthenticationFailed

On 12/8/20 8:31 AM, Peter Robinson wrote: > On Tue, Dec 8, 2020 at 1:10 PM Steve Dickson wrote: >> >> Hello, >> >> I realize this is probably not the most appropriate list >> to ask this question... but >> >> I have a pair of Jabra Elite 45h hea

Failed to pair: org.bluez.Error.AuthenticationFailed

Hello, I realize this is probably not the most appropriate list to ask this question... but I have a pair of Jabra Elite 45h headphones that was working just fine until I updated to Fedora 33. When I try to pair via bluetoothctl I get the following error [bluetooth]# pair 70:BF:92:D6:51:CB Att

Re: nfs-utils: compiler error tracking strlen on Rawhide armv7hl and i686

On 11/8/20 11:21 PM, John Reiser wrote: > Let's handle some preliminary errors in this thread on building nfs-utils, > before they spread even more. > > 1. Be specific.  State the package name in both the Subject and the first > line of the body. > This provides context which aids the scanning

Rawhide build failure on strange archs

Hello, I'm getting a build failure on the armv7hl arch and the i686 arch, which do not make much sense. The build is [1] and only those arche are complaining about an sprintf() statement. The rest of the arches are fine with the statment... %99.9 of the arches that are used today... I didn't ev

Re: Removing unsupported AUTH_DES interfaces in libtirpc.

Hey... Thanks for all the input! On 10/19/20 1:21 PM, Steve Dickson wrote: > Hello, > > About a year ago I stub out the interfaces > and had them return an error if called. > No one has complained... > > This time I would like to remove interfaces > so there will be

Removing unsupported AUTH_DES interfaces in libtirpc.

Hello, About a year ago I stub out the interfaces and had them return an error if called. No one has complained... This time I would like to remove interfaces so there will be no support whatsoever to pass some upcoming audits... This means I will need to change the SONAME for libtirpc whic

Re: Kerberos authentication fails: unable to obtain a session

On 3/10/20 1:55 PM, Kevin Fenzi wrote: > On Tue, Mar 10, 2020 at 10:42:09AM -0400, Steve Dickson wrote: >> Hello, >> >> I'm trying to do a scratch build >> $ fedpkg scratch-build --arches x86_64 --srpm >> >> and I'm getting the $SUBJECT error. I

Re: Kerberos authentication fails: unable to obtain a session

On 3/10/20 10:42 AM, Steve Dickson wrote: > Hello, > > I'm trying to do a scratch build > $ fedpkg scratch-build --arches x86_64 --srpm > > and I'm getting the $SUBJECT error. I know I have > a Kerberos ticket: > > $ klist > Ticket cache: KEY

Kerberos authentication fails: unable to obtain a session

Hello, I'm trying to do a scratch build $ fedpkg scratch-build --arches x86_64 --srpm and I'm getting the $SUBJECT error. I know I have a Kerberos ticket: $ klist Ticket cache: KEYRING:persistent:24013:krb_ccache_zynJSfJ Default principal: ste...@fedoraproject.org Valid starting Expire

Re: Fedora 31 Network Strangeness

On 1/31/20 10:31 AM, Tom Hughes wrote: > On 31/01/2020 15:29, Tom Hughes wrote: >> On 31/01/2020 15:23, Steve Dickson wrote: >> >>>> I know there was a change with systemd-networkd in a recent release so >>>> that it now creates a unique but persiste

Re: Fedora 31 Network Strangeness

On 1/31/20 9:55 AM, Tom Hughes wrote: > On 31/01/2020 14:28, Steve Dickson wrote: > >> I've recently updated my laptop to F31. Then I was no longer >> able to ssh into it. After a little debugging... it turns >> out my laptop was not getting the expected ip address

Fedora 31 Network Strangeness

Hello, I've recently updated my laptop to F31. Then I was no longer able to ssh into it. After a little debugging... it turns out my laptop was not getting the expected ip address from DHCP. The reason for that was the MAC address it was sending to dhcpd had change!!! Looking at the interfaces

1794117 – Disabling support for UDP for NFSv3

FYI... NFS over UDP will be deprecated in the 5.6 kernel. https://bugzilla.redhat.com/show_bug.cgi?id=1794117 Its not clear what or if any havoc this could cause but the commit (f745bfdc) has been accepted upstream. Just letting the community know... If by chance a bz is opened, please feel

New Package Process

Hello, I have a new contributor who wants to get a package into Fedora. The package is called "Flight Data Recorder" https://github.com/oracle/fdr It manages ftraces to record kernel data in way, when there is a kernel crash, one can go back and "see" what happen... It sounds very pro

Re: Question about libtirpc CNAME Change.

Hello, On 11/18/19 10:44 AM, Florian Weimer wrote: > * Steve Dickson: > >> In a recent upstream commit, the outdated, unsupported >> AUTH_DES authentication is now compiled out by default. >> >> This does effect the API, but does it really need a CNAME chang

Question about libtirpc CNAME Change.

Hello, In a recent upstream commit, the outdated, unsupported AUTH_DES authentication is now compiled out by default. This does effect the API, but does it really need a CNAME change since it interface can be recompiled back in? The reason I ask, change libtirpc's CNAME will require a large num

Changing the maintainer on a couple packages

Hello, I would like to change the maintership of nfsometer and nfstest now that they have been re-write in python 3. How do I do that? tia, steved. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@

Re: sign_and_send_pubkey: signing failed: agent refused operation

On 5/16/19 5:11 AM, Jakub Jelen wrote: > On Wed, 2019-05-15 at 17:09 -0400, Steve Dickson wrote: >> Hello, >> >> I'm getting the following error when I'm access the fedora git trees. >> >> sign_and_send_pubkey: signing failed: agent refused operation &

sign_and_send_pubkey: signing failed: agent refused operation

Hello, I'm getting the following error when I'm access the fedora git trees. sign_and_send_pubkey: signing failed: agent refused operation ste...@pkgs.fedoraproject.org: Permission denied (publickey). fatal: Could not read from remote repository. Please make sure you have the correct access righ

Re: Did the XML API change?

s.c:1386: > undefined reference to `xmlXPathNewContext' > > libjunction.la is not linked against libxml2 and later when you > construct nfsref, it is failing with undefined symbols. Got it... thanks!!! steved. > On Tue, Dec 11, 2018 at 5:55 PM Steve Dickson wrote: >> >

Re: Did the XML API change?

On 12/11/18 11:59 AM, Tom Hughes wrote: > On 11/12/2018 16:46, Steve Dickson wrote: > >> I'm getting a bunch of xml routines undefined >> >> https://koji.fedoraproject.org/koji/getfile?taskID=31408933&volume=DEFAULT&name=build.log&offset=-4000 >> &

Did the XML API change?

Hello, I'm getting a bunch of xml routines undefined https://koji.fedoraproject.org/koji/getfile?taskID=31408933&volume=DEFAULT&name=build.log&offset=-4000 on my rawhide build... everything builds just fine on f29... and I have BuildRequires: libxml2-devel Is there something more I have Build

Re: Fedora 30: Deprecating /etc/sysconf/nfs

On 10/12/18 2:54 PM, Stephen Gallagher wrote: > On Fri, Oct 12, 2018 at 2:48 PM Steve Dickson wrote: >> >> Hello, >> >> A few years back there was a movement the NFS community >> to consulate all nfs configuration into one file >> call /etc/nfs.conf... See

Fedora 30: Deprecating /etc/sysconf/nfs

Hello, A few years back there was a movement the NFS community to consulate all nfs configuration into one file call /etc/nfs.conf... See nfs.conf(5) Maybe stupidly, I've maintain backwards compatibility for that last couple Fedora releases. I think it is time to go to the single file configurat

Re: The update system has the wrong package

On 05/31/2018 12:02 PM, Randy Barlow wrote: > On 05/30/2018 02:23 PM, Steve Dickson wrote: >> You are right... I only did a rawhide build... but that is no longer the case >> https://koji.fedoraproject.org/koji/taskinfo?taskID=27299567 >> >> And I'm still having

Re: The update system has the wrong package

On 05/29/2018 05:00 PM, Adam Williamson wrote: > On Tue, 2018-05-29 at 16:54 -0400, Steve Dickson wrote: >> Hello, >> >> I'm trying to update the rpcsvc-proto package. >> When I try to create a new update, the system >> only gives me rpcsvc-proto

Re: The update system has the wrong package

On 05/29/2018 06:40 PM, Michael Schwendt wrote: > On Tue, 29 May 2018 16:54:00 -0400, Steve Dickson wrote: > >> Hello, >> >> I'm trying to update the rpcsvc-proto package. >> When I try to create a new update, the system >> only gives me rpcsvc-pr

The update system has the wrong package

Hello, I'm trying to update the rpcsvc-proto package. When I try to create a new update, the system only gives me rpcsvc-proto-devel as a choice not rpcsvc-proto. Where do I open up a ticket to get this taken care of? steved. ___ devel mailing list

Problem: package fwupdate-libs-10-6.fc28.x86_64 requires shim

Hello, I've getting the following error when I try to update from f27 to f28: # dnf system-upgrade download --refresh --releasever=28 Before you continue ensure that your system is fully upgraded by running "dnf --refresh upgrade". Do you want to continue [y/N]: y Fedora 28 - x86_64 - Updates

Re: libevent-2.1.8 SONAME change.

On 02/15/2018 07:04 AM, Peter Robinson wrote: > On Thu, Feb 15, 2018 at 11:51 AM, Steve Dickson wrote: >> Hello, >> >> Yesterday I updated libevent to the latest upstream release. >> >> I mistakenly did not realized there was a SONAME change >> in this upd

libevent-2.1.8 SONAME change.

Hello, Yesterday I updated libevent to the latest upstream release. I mistakenly did not realized there was a SONAME change in this update. So if your package is dependent on libevent, you are going to have to rebuild. My apologies for this oversight... steved. ___

Re: Fwd: Re: Fedora27: NFS v4 terrible write performance, is async working

gt; To: Steven Whitehouse , Development discussions > related to Fedora , Terry Barnaby > > CC: Steve Dickson , Benjamin Coddington > > > > > On 28/01/18 14:38, Steven Whitehouse wrote: >> Hi, >> >> >> On 28/01/18 07:48, Terry Barnaby wrote: >>

Re: F28 System Wide Change: Rename "nobody" user

On 01/15/2018 01:28 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Mon, Jan 15, 2018 at 11:04:32AM -0500, Steve Dickson wrote: >> >> >> On 01/10/2018 05:46 AM, Jan Kurik wrote: >>> = System Wide Change: Rename "nobody" user = >>> https://fedorap

Re: F28 System Wide Change: Rename "nobody" user

On 01/10/2018 05:46 AM, Jan Kurik wrote: > = System Wide Change: Rename "nobody" user = > https://fedoraproject.org/wiki/Changes/RenameNobodyUser A nit... The proposed rename looks like: nobody:x:65534:65534:Kernel Overflow User:/:/sbin/nologin Now that this is going to be used for NFS, shou

Re: F28 System Wide Change: Rename "nobody" user

ros. The Details: On 01/13/2018 06:18 PM, Zbigniew Jędrzejewski-Szmek wrote: > On Sat, Jan 13, 2018 at 10:18:14AM -0500, Steve Dickson wrote: >> On 01/13/2018 08:50 AM, Steve Dickson wrote: >>> So I guess the next question is what the current >>> nobody id (25) used f

Re: F28 System Wide Change: Rename "nobody" user

On 01/13/2018 08:50 AM, Steve Dickson wrote: > So I guess the next question is what the current > nobody id (25) used for and why does it exist? Doing some research on this back in Aug 2001 nfsnobody was added to nfs-utils for the reasons stated in https://bugzilla.redhat.com/show_bug.

Re: F28 System Wide Change: Rename "nobody" user

On 01/12/2018 07:32 PM, Louis Lagendijk wrote: > On Fri, 2018-01-12 at 07:20 -0500, Steve Dickson wrote: >> Instead of doing the blow by blow these threads >> always turn into I'm just going jump to the point. >> >> systemd wants to use uid 65534 and it can&

Re: F28 System Wide Change: Rename "nobody" user

On 01/12/2018 05:11 PM, Neal Gompa wrote: >> Side Note: I have a ping out to a SUSE guy to see how they handle this >> but the guy lives on the other side of the earth so I probably >> will not get a response until tomorrow. > I can tell you what that is, as I run (open)SUSE systems. > > SUSE syst

Re: F28 System Wide Change: Rename "nobody" user

On 01/12/2018 10:57 AM, Daniel Walsh wrote: > On 01/12/2018 10:41 AM, Steve Dickson wrote: >> >> On 01/12/2018 09:47 AM, Lennart Poettering wrote: >>> On Fr, 12.01.18 09:28, Steve Dickson (ste...@redhat.com) wrote: >>> >>>>> User namespacing

Re: F28 System Wide Change: Rename "nobody" user

On 01/12/2018 09:47 AM, Lennart Poettering wrote: > On Fr, 12.01.18 09:28, Steve Dickson (ste...@redhat.com) wrote: > >>> User namespacing is a Linux kernel feature. It's most well known >>> consumers are probably Docker, and maybe flatpak/bubblewrap and LXC. >&g

Re: F28 System Wide Change: Rename "nobody" user

On 01/12/2018 07:40 AM, Lennart Poettering wrote: > On Fr, 12.01.18 07:20, Steve Dickson (ste...@redhat.com) wrote: > >> Instead of doing the blow by blow these threads >> always turn into I'm just going jump to the point. >> >> systemd wants to use uid 6

Re: F28 System Wide Change: Rename "nobody" user

Instead of doing the blow by blow these threads always turn into I'm just going jump to the point. systemd wants to use uid 65534 and it can't because NFS is using it. So instead of changing systemd needs they want to change NFS potentially break all NFS environments. Is or isn't this what we a

Re: F28 System Wide Change: Rename "nobody" user

On 01/10/2018 11:14 AM, Stephen John Smoogen wrote: > On 10 January 2018 at 08:50, Neal Gompa wrote: >> On Wed, Jan 10, 2018 at 5:46 AM, Jan Kurik wrote: > >>> The new mapping for nobody:nobody would be implemented in two redundant >>> ways: >>> * as a static allocation in /etc/passwd and

Re: F28 System Wide Change: Rename "nobody" user

WOW... Why do you guys keep picking on NFS?? :-) On 01/10/2018 05:46 AM, Jan Kurik wrote: > = System Wide Change: Rename "nobody" user = > https://fedoraproject.org/wiki/Changes/RenameNobodyUser > > Change owner(s): > *Zbigniew Jędrzejewski-Szmek > * Lennart Poettering > > Use "nobody:nobody"

  1   2   3   >