On 20/06/2021 06:58, Ed Greshko wrote:
On 19/06/2021 19:22, Patrick O'Callaghan wrote:
On Sat, 2021-06-19 at 11:58 +0800, Ed Greshko wrote:
I removed the WantedBy=multi-user.target from the mount unit. I then
did a daemon-reload.
I noted that there were 2 broken syslinks associated with the
On Jun 19, 2021, at 18:00, Patrick Dupre wrote:
>
> How to I extract the .tgz (or the .spec) file from a src.rpm ?
You already have fedpkg. You can run
fedpkg co -a gsl
(Add a —branch f34 to get the Fedora 34 branch, or check it out manually with
git)
And it will check out the branch
On 19/06/2021 19:22, Patrick O'Callaghan wrote:
On Sat, 2021-06-19 at 11:58 +0800, Ed Greshko wrote:
I removed the WantedBy=multi-user.target from the mount unit. I then
did a daemon-reload.
I noted that there were 2 broken syslinks associated with the mounts
in
On Sat, Jun 19, 2021 at 4:01 PM Patrick Dupre wrote:
>
> Yes,
>
> How to I extract the .tgz (or the .spec) file from a src.rpm ?
If you run "rpm -i https://src.fedoraproject.org/rpms/gsl/tree/rawhide
--
Jerry James
http://www.jamezone.org/
___
users
Yes,
How to I extract the .tgz (or the .spec) file from a src.rpm ?
>
> On 2021-06-19 2:35 p.m., Patrick Dupre wrote:
> > This what I have done.
> >
> > extrated the gsl.spec from gsl-2.7.tgz
> > edited it to set the version (2.7)
> > run rpmbuild -bb gsl.spec
> > It started to work, but
On 2021-06-19 2:35 p.m., Patrick Dupre wrote:
This what I have done.
extrated the gsl.spec from gsl-2.7.tgz
edited it to set the version (2.7)
run rpmbuild -bb gsl.spec
It started to work, but finally stop with
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
* $
This information is probably missing:
/usr/lib/rpm/sepdebugcrcfix: Updated 4 CRC32s, 0 CRC32s did match.
12830 blocks
+ '[' '%{buildarch}' = noarch ']'
+ QA_CHECK_RPATHS=1
+ case "${QA_CHECK_RPATHS:-}" in
+ /usr/lib/rpm/check-rpaths
This what I have done.
extrated the gsl.spec from gsl-2.7.tgz
edited it to set the version (2.7)
run rpmbuild -bb gsl.spec
It started to work, but finally stop with
* Examples:
* - to ignore standard and empty RPATHs, execute 'rpmbuild' like
* $ QA_RPATHS=$(( 0x0001|0x0010 )) rpmbuild
On 2021-06-19 2:00 p.m., Patrick Dupre wrote:
I do not think so.
I downloaded
https://www.gnu.org/software/gsl/gsl-latest.tgz (gsl-2.7)
I thought that fedpkg works with a clone of the git repo for a fedora package.
Is that what you are doing?
That isn't going to work. You need the extra
I do not think so.
I downloaded
https://www.gnu.org/software/gsl/gsl-latest.tgz (gsl-2.7)
> I thought that fedpkg works with a clone of the git repo for a fedora package.
> Is that what you are doing?
>
> Barry
>
> > On 19 Jun 2021, at 15:35, Patrick Dupre wrote:
> >
> > Hello,
> >
> >
I thought that fedpkg works with a clone of the git repo for a fedora package.
Is that what you are doing?
Barry
> On 19 Jun 2021, at 15:35, Patrick Dupre wrote:
>
> Hello,
>
> Trying to build a rpm package for gsl.2.7
> I downloaded gsl-2.7.tar.gz
> I copy
> cp -a gsl.spec.in gsl.spec
>
Actually, now I have:
fedpkg --release fc34 local
sources file doesn't exist. Source files download skipped.
Could not execute local: Could not find the release/dist from branch name fc34
Please specify with --release
using gsl.spec.in (gsl-2.7.tar.gz)
Name: gsl
Summary: GNU Scientific Library
python3-pycurl-7.43.0.6-5.fc34.x86_64
libcurl-7.76.1-4.fc34.x86_64
libcurl-7.76.1-4.fc34.i686
>
> On 2021-06-19 7:34 a.m., Patrick Dupre wrote:
> > import pycurl
> > ImportError: pycurl: libcurl link-time version (7.64.1) is older than
> > compile-time version (7.75.0)
>
> Do you have a
On 2021-06-19 7:34 a.m., Patrick Dupre wrote:
import pycurl
ImportError: pycurl: libcurl link-time version (7.64.1) is older than
compile-time version (7.75.0)
Do you have a self-installed version of pycurl or libcurl somewhere?
What does "rpm -q python3-pycurl libcurl" show?
Here is the new error
rpmbuild -bb perl-PDL-Graphics-PLplot.spec
warning: Macro expanded in comment on line 9:
%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
setting SOURCE_DATE_EPOCH=1624060800
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.N0YTFx
+ umask 022
+ cd
On Sat, Jun 19, 2021 at 9:00 AM Patrick Dupre wrote:
> This spec file provide the an error.
> Can you help me to fix it?
You didn't show the compiler flags in use, so this is just a guess, but ...
> cc1: some warnings being treated as errors
... this message suggests that -Werror is included.
On 19/06/2021 21:44, Stephen Morris wrote:
On 19/6/21 15:31, Ed Greshko wrote:
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34 under a vm,
that fedora does not have a swap specification in fstab anymore, but is using,
in my
Hello,
This spec file provide the an error.
Can you help me to fix it?
PLplot.c: In function 'XS_PDL__Graphics__PLplot_plgfci':
PLplot.c:85895:25: warning: unused variable 'RETVAL' [-Wunused-variable]
85895 | unsigned intRETVAL;
| ^~
Hello,
Trying to build a rpm package for gsl.2.7
I downloaded gsl-2.7.tar.gz
I copy
cp -a gsl.spec.in gsl.spec
and
run (in gsl-2.7)
fedpkg --release fc34 local
but I get
Traceback (most recent call last):
File "/usr/bin/fedpkg", line 33, in
sys.exit(load_entry_point('fedpkg==1.40',
On Sat, 19 Jun 2021 at 05:05, Barry Scott wrote:
>
>
> > On 18 Jun 2021, at 21:50, Jerry James wrote:
> >
> > On Fri, Jun 18, 2021 at 2:40 PM Patrick Dupre wrote:
> >> But
> >>
> >> scilab-bin: symbol lookup error: /lib64/libk5crypto.so.3: undefined
> symbol: EVP_KDF_ctrl, version
On 19/6/21 15:31, Ed Greshko wrote:
On 19/06/2021 12:45, Stephen Morris wrote:
Hi,
I've noticed when trying remediate performance issues in F34
under a vm, that fedora does not have a swap specification in fstab
anymore, but is using, in my case, and 8GB swap partition in
/dev/zram0.
Hello,
There is a new version of gsl (2.7).
http://www.gnu.org/software/gsl/
What are the plans to have it available in fc34?
Thanks
===
Patrick DUPRÉ | | email: pdu...@gmx.com
On Fri, 2021-06-18 at 12:15 -0600, Chris Murphy wrote:
> On Fri, Jun 18, 2021, 11:10 AM Patrick O'Callaghan
>
> wrote:
>
> >
> > My problem is that one drive comes up almost instantly and the other
> > takes 30 seconds. In fact I can live with that. My real gripe is that
> > the kernel makes me
On Sat, 2021-06-19 at 11:58 +0800, Ed Greshko wrote:
> I removed the WantedBy=multi-user.target from the mount unit. I then
> did a daemon-reload.
> I noted that there were 2 broken syslinks associated with the mounts
> in
> /etc/systemd/system/multi-user.target.wants so I deleted them. I
> then
On Fri, 2021-06-18 at 19:26 -0600, Chris Murphy wrote:
> I make fstab mount options include:
>
> nofail,noauto,x-systemd.automount
>
> That way it is only mounted on demand, i.e. when the mount point is
> "touched".
>
> It's also possible to use x-systemd.idle-timeout=300 which will
> unmount
On Fri, 2021-06-18 at 19:36 -0300, George N. White III wrote:
> > The power block says its output is 3A at 12V.
> >
> > The drives are both WD model WD10EZEX, (though the label on one
> > says
> it
> > has a 64MB cache and the other doesn't). Both labels say 5VDC,
> > 0.68A
> > and 12VDC, 0.55A.
On 19/06/2021 11:58, Ed Greshko wrote:
The mount no longer happens at boot time and the status of the automount unit is
Active: active (waiting). And everything works as expected. Mount upon
accessing the
mount point and unmounting happening after the timeout has expired.
Well, I spoke too
> On 18 Jun 2021, at 21:50, Jerry James wrote:
>
> On Fri, Jun 18, 2021 at 2:40 PM Patrick Dupre wrote:
>> But
>>
>> scilab-bin: symbol lookup error: /lib64/libk5crypto.so.3: undefined symbol:
>> EVP_KDF_ctrl, version OPENSSL_1_1_1b
>
> Take a look here:
>
>
28 matches
Mail list logo
