Hi,
building with the -mno-ssse3 causes build failure, e.g.:
CFLAGS="-O2 -march=bonnell -mtune=bonnell -mno-ssse3"
...
gcc -I. -I./lib -Ilib -I./lib -Isrc -I./src -mavx -mpclmul -O2
-march=bonnell -mtune=bonnell -mno-ssse3 -c -o
src/libcksum_pclmul_a-cksum_pclmul.o `test -f
If hound mode is enabled and frequency is manually changed by entering
the frequency directly to the "band" box and hitting enter, e.g:
18.107
the TX is activated. It happens anytime the frequency is changed this
way. What's worse is that if there is TX period the radio is
immediately keyed. This
On Thu, Jan 26, 2023 at 1:09 PM Neal Gompa wrote:
>
> On Thu, Jan 26, 2023 at 7:02 AM Jaroslav Skarvada wrote:
> >
> > Hi,
> >
> > it seems Anitya correctly distinguishes stable and pre-release
> > releases but where to set that I want Fedora bugs only for
Hi,
it seems Anitya correctly distinguishes stable and pre-release
releases but where to set that I want Fedora bugs only for the stable
releases? IIRC Pagure had a switch for it, but I am unable to find it
on the https://src.fedoraproject.org/rpms/. There is only
"No-Monitoring", "Monitoring",
On Wed, Jan 25, 2023 at 12:13 PM Miro Hrončok wrote:
>
> On 25. 01. 23 11:50, Vít Ondruch wrote:
> > Reading the thread, I was afraid this will be the end result. Nevertheless,
> > given this would be used just for side-tags, is there a chance to exclude
> > side
> > tags from the policy? Who
On Tue, Jan 24, 2023 at 9:37 PM Neal Gompa wrote:
>
> On Tue, Jan 24, 2023 at 3:00 PM Kevin Fenzi wrote:
> >
> > On Tue, Jan 24, 2023 at 07:54:29PM +0100, Jaroslav Skarvada wrote:
> > >
> > > I initially thought about:
> > > release bump
> &
On Tue, Jan 24, 2023 at 7:42 PM Neal Gompa wrote:
>
> On Tue, Jan 24, 2023 at 1:39 PM Jaroslav Skarvada wrote:
> >
> > Hi,
> >
> > I need to bootstrap package which has bootstrap support written
> > according to the [1]. I am able to boot
Hi,
I need to bootstrap package which has bootstrap support written
according to the [1]. I am able to bootstrap it locally (rpmbuild,
mock, ...) with the "--with bootstrap" or "-D '_with_bootstrap 1'". Is
there support for it in koji? E.g. something like:
koji build SIDE-TAG PACKAGE --bootstrap?
https://bugs.kde.org/show_bug.cgi?id=442782
--- Comment #4 from Jaroslav Skarvada ---
+1, please add option to disable and manual enable only when needed. Otherwise
it's unusable for me. Moreover, it's better for security not to run services
you don't need at the moment.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=442782
Jaroslav Skarvada changed:
What|Removed |Added
CC||jskar...@redhat.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #63 from Jaroslav Skarvada ---
(In reply to Jaroslav Skarvada from comment #62)
> Regarding the libwdi, I could try to get it into the MXE, but it seems it
> needs bundling of the libusb windriver which I currently don't know whether
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #62 from Jaroslav Skarvada ---
Regarding the libwdi, I could try to get it into the MXE, but it seems it needs
bundling of the libusb windriver which I currently don't know whether it's
possible from the MXE, but I will check
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #61 from Jaroslav Skarvada ---
I built the git head (at the time I started with it it was
v7.5.0-322-gb6a672426b) and it works for me. This time it was nearly
straightforward experience, I only hit one MXE FTBFS bug and created PR
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #60 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #59)
> Hi Jaroslav,
>
> New 7.6.0 pre-release Windows installer is online with last libgphoto2
> 2.2.58.
>
> https://files.kde.org/digikam/
&g
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #57 from Jaroslav Skarvada ---
You also need to follow the steps from the comment 34, because normally the
windows mass storage or PTP driver will take over the libgphoto2/libusb
drivers.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #56 from Jaroslav Skarvada ---
You may also try rebuilding the libgphoto2 with the legacy libusb enabled (i.e
try dropping the --with-libusb=no from the mxe). Maybe there is some wrong
ifdef in the code.
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #55 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #54)
> Hi Jaroslav,
>
> I rebuild libexif + libgphoto with the update of MXE, rebuild the digiKam
> installer.
> But, no chance, the list of libgphoto
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #50 from Jaroslav Skarvada ---
(In reply to Jaroslav Skarvada from comment #49)
> Thanks for applying the patches. So does it work now? IIRC there was some
> problem with the libusb on the MXE side, but it should be solved soon:
&
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #49 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #48)
> Hi Jaroslav,
>
> Correction. I upgraded libgphoto2 under MacOS from 2.5.27 to 2.5.28, and now
> problem disappear :
>
> https://i.img
Hi,
it seems the following README files are not included in the conf/postfix-files:
BDAT_README
MAILLOG_README
POSTSCREEN_3_5_README
SMTPUTF8_README
Is it intended?
Checked with the postfix-3.6.4.
Downstream Fedora bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=2041056
thanks & regards
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #36 from Jaroslav Skarvada ---
digiKam PR:
https://invent.kde.org/graphics/digikam/-/merge_requests/136
Unofficial unsupported build for testing (it's built from the v7.3.0 tag):
https://jskarvad.fedorapeople.org/digiKam/digiKam-7.3.0
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #34 from Jaroslav Skarvada ---
I got it working even for non-admin user. I also tried the libusb-win32 driver,
but it's crashing during download of the photos. The WinUSB driver seems to
work the most reliable way.
Steps how to install
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #33 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #32)
> To implement a Windows native support in digiKam import tool, this interface
> must be re-implemented :
>
> https://invent.kde.org/graphics/di
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #31 from Jaroslav Skarvada ---
Also probably dupes (maybe there are more):
https://bugs.kde.org/show_bug.cgi?id=398061
https://bugs.kde.org/show_bug.cgi?id=379970
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #30 from Jaroslav Skarvada ---
I finally got it working, gphoto2 upstream bug:
https://github.com/gphoto/libgphoto2/issues/706
TLDR the digiKam has to be running under the admin account and I had to replace
the windows PTP drivers for all
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #29 from Jaroslav Skarvada ---
I finally cross-compiled gphoto2 in the mxe with some effort, spotted gphoto2
bug:
https://github.com/gphoto/gphoto2/issues/448
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #27 from Jaroslav Skarvada ---
(In reply to Jaroslav Skarvada from comment #26)
> FTR I am testing on the Windows 10, the latest stable build. I am using the
> latest master of the digiKam.
64 bit Windows 10, 64 bit digiKam/libraries
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #26 from Jaroslav Skarvada ---
FTR I am testing on the Windows 10, the latest stable build. I am using the
latest master of the digiKam.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #25 from Jaroslav Skarvada ---
(In reply to caulier.gilles from comment #23)
> I think that libgphoto2 needs libusb1 at run time (or something like that).
>
Yep, I already had it (libusb1). I verified it's bundled and loaded (I p
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #24 from Jaroslav Skarvada ---
Another libgphoto2 PR:
https://github.com/gphoto/libgphoto2/pull/705/
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #22 from Jaroslav Skarvada ---
The camera is detected fine, but I am getting: GP_ERROR_IO_USB_CLAIM (Could not
claim the USB device -53) from the libgphoto2 when trying to access it. I tried
multiple cameras, but it's still the same
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #21 from Jaroslav Skarvada ---
Another digiKam PR:
https://invent.kde.org/graphics/digikam/-/merge_requests/135
libexif mxe PR:
https://github.com/mxe/mxe/pull/2700
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #20 from Jaroslav Skarvada ---
Related digiKam PR (just for the reference, it's unrelated to the comment 19):
https://invent.kde.org/graphics/digikam/-/merge_requests/133
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=398166
--- Comment #19 from Jaroslav Skarvada ---
It seems I am slowly progressing. There were several problems. I will PR more
patches to mxe, libgphoto2 upstreams and also to digiKam.
At the moment under Win 10 it successfully detects the camera and adds
https://bugs.kde.org/show_bug.cgi?id=398166
Jaroslav Skarvada changed:
What|Removed |Added
CC||jskar...@redhat.com
--- Comment #16 from
On Thu, Jul 29, 2021 at 3:15 PM Wietse Venema wrote:
>
> Wietse Venema:
> > Wietse Venema:
> > > Jaroslav Skarvada:
> > > > Hi,
> > > >
> > > > glibc-2.34 introduced the closefrom function which causes postfix build
> > &g
Hi,
glibc-2.34 introduced the closefrom function which causes postfix build to fail:
In file included from ./vstream.h:22,
from attr_print64.c:100:
/usr/include/unistd.h:363:13: error: conflicting types for 'closefrom'; have 'vo
363 | extern void closefrom (int __lowfd)
Reproducer:
# useradd -c " " myuser # or more whitespaces
# su - myuser
$ echo | mail -s TEST root@localhost
# journalctl -u postfix | tail
Jun 30 13:31:13 vm-postfix8 postfix/pickup[4476]: 91309115983C:
uid=1000 from=
Jun 30 13:31:13 vm-postfix8 postfix/pickup[4476]: warning:
https://bugs.kde.org/show_bug.cgi?id=438984
--- Comment #1 from Jaroslav Skarvada ---
The reproducer should be:
valgrind --log-file=/var/tmp/log --trace-origins=yes powertop
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438984
Bug ID: 438984
Summary: Uncomplete report with C++ and --track-origins=yes
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Hi,
on fedora rawhide the stack-overflow test is failing for grep-3.6:
...
stack-overflow: failed test: grep never printed "stack overflow"
FAIL: stack-overflow
..
Manual run:
# ASAN_OPTIONS=help=true grep --version 2>&1 | grep -q AddressSanitizer
# echo $?
1
# i=3;printf %0${i}d 0|tr 0 '('
Hi,
PCRE library has been superseded with PCRE2 project by PCRE
upstream in 2015. PCRE upstream considers PCRE obsolete now
and does not devote any resources to PCRE except of critical
bugs. Please consider adding PCRE2 support.
Downstream Fedora bug:
Hi,
we run coverity & clang scans time to time. I filtered all the
false positives and the following are results which seemed
suspicious to me. It's mostly for unlikely code paths which
could be triggered by error state or invalid input. I am not
familiar with the code internals, so maybe it's
Hi,
there is Fedora review [1]. The package contains the PATENTS file [2]
which for me seems like additional restrictions of the license (e.g. the
text from the line 14). Is it OK to package it into Fedora?
thanks & regards
Jaroslav
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1922315
[2]
I am encountering the same problem since yesterday. All my builds are
failing on s390x this way e.g. [1], [2]. Could somebody fix it?
thanks & regards
Jaroslav
[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=60132339
[2] https://koji.fedoraproject.org/koji/taskinfo?taskID=60132333
- Original Message -
>
>
> Le 1/13/21 à 4:25 PM, Jan Zerdik a écrit :
> > Hi. My name is Jan and I'm a new red hatter. I'll be a TuneD co-maintainer.
> > My experience with open source projects is mostly just as a user, but I'm
> > looking forward to joining the community.
> >
> >
- Original Message -
> On Fri, Sep 18, 2020 at 6:03 PM Neal Gompa wrote:
> >
> > On Fri, Sep 18, 2020 at 5:59 PM Richard Fontana
> > wrote:
> > >
> > > On Fri, Aug 28, 2020 at 8:16 AM Jaroslav Skarvada
> > &g
- Original Message -
>
>
> - Original Message -
> > On Tue, Aug 25, 2020 at 9:41 AM David Cantrell
> > wrote:
> > >
> > > Back to the original question... what short name do we give this license?
> > >
> > > - It has an advertising clause
> > > - It forbids relicensing under any
- Original Message -
> On Tue, Aug 25, 2020 at 9:41 AM David Cantrell wrote:
> >
> > Back to the original question... what short name do we give this license?
> >
> > - It has an advertising clause
> > - It forbids relicensing under any form of the GPL (curious what that means
> >
- Original Message -
> Am Montag, den 24.08.2020, 03:18 -0400 schrieb Jaroslav Skarvada:
> > Hi,
> >
> > the code contains the following text:
> > * wrote this file. As long as you retain this
> > notice you
> > * can do whatever
Hi,
the code contains the following text:
* wrote this file. As long as you retain this notice you
* can do whatever you want with this code, except you may not
* license it under any form of the GPL.
* A postcard or QSL card showing me you appreciate
* this code would be nice. Diane Bruce
- Original Message -
> On Mon, Aug 03, 2020 at 01:30:56PM -0400, Jaroslav Skarvada wrote:
> >
> > Most of my FTBFSs are in form:
> > BuildrootError: Requested repo (1785390) is DELETED
> >
> > Wtf?
> >
> > E.g.:
> > https://bu
- Original Message -
> On 8/3/2020 9:42 AM, Neal Gompa wrote:
> > On Mon, Aug 3, 2020 at 12:32 PM Gary Buhrmaster
> > wrote:
> >> On Mon, Aug 3, 2020 at 3:15 PM Richard Hughes wrote:
> >>
> >>> Most of those are the libcroco->gettext breakage, no?
> >> From a very cursory scan (not at
> pidgin: https://bugzilla.redhat.com/1856866
Hi,
pidgin maintainer here. I really don't understand what are
you trying to achieve by this. I am maintaining/co-maintaining
over 100 packages in Fedora and if you think the
reaction time for bugzillas should be less than 24 hours
feel free to help
- Original Message -
> > -1 for the change. If the so called 'end-user' (whatever does it mean)
> > can learn git, she or he can also learn 'vi' or at least how to enable
> > the preferred editor. Personally, I can see nothing special on the
> > nano, for me it qualifies as very poor
- Original Message -
> Jaroslav Skarvada 于2020年6月26日周五 下午9:41写道：
> >
> >
> >
> > - Original Message -
> > >
> > >
> > > Adam Williamson < adamw...@fedoraproject.org > 于 2020年6月26日周五 上午9:32写道：
> > >
> > &g
- Original Message -
>
>
> Adam Williamson < adamw...@fedoraproject.org > 于 2020年6月26日周五 上午9:32写道：
>
>
> On Fri, 2020-06-26 at 08:44 +0800, Qiyu Yan wrote:
> > What about to provide a prompt to the user telling them the difference
> > between editors?
> > For example, when a new user
- Original Message -
> El jue., 25 jun. 2020 a las 21:45, Qiyu Yan (< yanq...@fedoraproject.org >)
> escribió:
>
>
> What about to provide a prompt to the user telling them the difference
> between editors?
> For example, when a new user to fedora first invokes git commit
> without
- Original Message -
> I prepared a protobuf update for rawhide to 3.12. It requires a rebuild
> of all dependencies and of the 55 dependencies currently 10 fail to
> rebuild. The following packages are failing:
>
> clementine
> closure-compiler
> fawkes
> gazebo
> hidviz
> kismet
>
> jskarvad gnuradio gr-air-modes gr-fcdproplus gr-hpsdr gr-iqbal gr-osmosdr
> gr-rds hamlib pidgin
pidgin - it calls Py_Initialize, so I kept is as is
hamlib - fixed & forwarded upstream
gnuradio stuff - it doesn't seem it calls Py_Initialize, but linking without
-python failed:
/usr/bin/ld:
Hi,
it fails with the following error:
...
/builddir/build/BUILD/wsjtx-2.1.2/wsjtx/lib/ft8/filt8.f90:32:14:
12 | call four2a(x,NFFT,1,-1,0) !r2c
| 2
..
32 | call four2a(cx,nfft,1,1,-1) !c2r
| 1
Error: Type mismatch
/usr/bin/ld:
anvil_clnt.o:/builddir/build/BUILD/postfix-3.4.9/src/global/./mail_params.h:3999:
multiple definition of `var_tlsp_clnt_policy';
abounce.o:/builddir/build/BUILD/postfix-3.4.9/src/global/./mail_params.h:3999:
first defined here
/usr/bin/ld:
- Original Message -
> Jaroslav Skarvada:
> > Hi Wietse,
> >
> > thanks for info. Are you going to introduce this patch upstream?
>
> The process is as follows:
>
> 1) I sadistically keep the fix for myself and let everyone else suffe
- Original Message -
> Jaroslav Skarvada:
> > Hi,
> >
> > it seems the resolver was rewritten (probably in postfix 3.1.x), but
> > it seems it now uses res_query instead of the res_search which results
> > in RES_DEFNAMES and RES_DNSRCH not su
Hi,
it seems the resolver was rewritten (probably in postfix 3.1.x), but
it seems it now uses res_query instead of the res_search which results
in RES_DEFNAMES and RES_DNSRCH not supported with smtp_host_lookup=dns,
example:
# postconf -e "relayhost = [smtp]"
# postconf -e smtp_host_lookup=dns
#
Hi,
alsa-1.1.9 has been recently released. One of the change is drop of
the -I/usr/include/alsa from the alsa.pc [1], so the brltty sources
have to be changed to cope with it. Alsa upstream recommends using
#include instead of #include [2]
thanks & regards
Jaroslav
[1]
Hi,
I spotted it on the Fedora rawhide (f31) with the glibc-2.29.9000-18.fc31:
...
BUILDSTDERR: dns_str_resflags.c:63:22: error: 'RES_INSECURE1' undeclared here
(not in a function); did you mean 'RES_RECURSE'?
BUILDSTDERR:63 | "RES_INSECURE1", RES_INSECURE1,
BUILDSTDERR: |
Hi,
it seems gfortran dropped GNU extension for iand, compare [1] and [2].
Previously there was: "As a GNU extension, different kinds are also permitted",
which is there no more, so the wsjtx now fails to build with the gfortran-9:
> 16 |
Hi,
I got to Coverity static analysis scan report for postfix. Most of the
errors were false positives, but two minor errors seems suspicious, that
it could cause leaks, so sharing them for review. Unfortunately, it's
result for postfix-3.2.5, but the same code is in the latest postfix -
just the
- Original Message -
> On Monday 01 October 2018 22:13:41 Richard Weinberger wrote:
> > On Mon, Oct 1, 2018 at 10:01 PM Andreas Dilger wrote:
> > > If the current dosfstools maintainer is non-responsive, you could always
> > > fork the project in GitHub, land the critical patches into
- Original Message -
> On Monday 01 October 2018 22:13:41 Richard Weinberger wrote:
> > On Mon, Oct 1, 2018 at 10:01 PM Andreas Dilger wrote:
> > > If the current dosfstools maintainer is non-responsive, you could always
> > > fork the project in GitHub, land the critical patches into
Hi,
just running 'make check' with glibc-2.28 on grep git master results in:
...
XPASS: backref-alt
...
+ grep -E 'b|(.)b|\1|b' in
grep: Invalid back reference
+ status=2
+ test 2 -eq 2
+ grep -E '0|()0|\1|0' in
grep: Invalid back reference
+ status=2
+ test 2 -eq 2
+ Exit 0
...
Testsuite summary
Hi Lars,
- Original Message -
> Hi, Jaroslav!
>
> About the BRLTTY-dracut module, you wrote:
>
> > It's in Fedora 28 updates-testing repository. If you have an older Fedora,
> > e.g. 27, I can built it for you.
>
> I'm currently using Fedora 27 on my systems. Is it possible that we
>
- Original Message -
> [quoted lines by Dave Mielke on 2018/06/02 at 22:15 -0400]
>
> >Now for something that I hope can be fixed. I normally don't have a monitor
> >connected. What I've discovered is that, when gdm is enabled, login (getty)
> >prompts on other ttys are blocked until
Hi,
proof of concept implementation:
https://src.fedoraproject.org/rpms/brltty/c/5f009fa9a69939c3dc8b6d50c053bb72f02f406d?branch=master
There is a room for improvement, but it seems to work (at least).
It:
- adds to the initramfs what the user has enabled on the host system
(drivers, tables,
> Thanks for these instructions. These are post-installationsteps,
> right? If yes, still a deaf-blind person wouldn't be able to install
> Fedora on his/her own.
>
I fully agree that it kills the purpose of assistive technology, that's why
I propose to the Anaconda bugzilla how they should fix
- Original Message -
> On Mon, 28 May 2018, Jaroslav Skarvada wrote:
>
> > OK, thanks for info, please provide me the patch / commit link once
> > the feature is ready. FYI Tomas has just started working on the dracut
> > module
>
> While
- Original Message -
> [quoted lines by Jaroslav Skarvada on 2018/05/28 at 05:12 -0400]
>
> >please provide me the patch / commit link once the feature is ready.
>
> It's in the latest development code. I did it in something like 4 commits
> that
> aren't a
- Original Message -
> [quoted lines by Jaroslav Skarvada on 2018/05/25 at 05:40 -0400]
>
> >Please add such option (it could be just experimental patch). I think it
> >would
> >be useful for development of the dracut module. The best would
> >be forma
- Original Message -
> [quoted lines by Jaroslav Skarvada on 2018/05/24 at 05:29 -0400]
>
> >In rawhide I changed systemd service WantedBy to:
> >WantedBy=default.target emergency.target
>
> Thanks. Would it make sense to also add rescue.target?
>
OK, I t
- Original Message -
>
>
> - Original Message -
> > [quoted lines by Jaroslav Skarvada on 2018/05/22 at 11:42 -0400]
> >
> > >> Are you the person who maintains brltty for Fedora?
> > >>
> > >I am co-maintainer in Fe
- Original Message -
> [quoted lines by Jaroslav Skarvada on 2018/05/22 at 11:42 -0400]
>
> >> Are you the person who maintains brltty for Fedora?
> >>
> >I am co-maintainer in Fedora, maintainer in RHEL
>
> Looking at Fedora 28, the syste
- Original Message -
> [quoted lines by Jaroslav Skarvada on 2018/05/22 at 07:59 -0400]
>
> >I received report that the LDFLAGS are still not taken into account for
> >libbrlapi
> >and corresponding bindings. I used the attached patch downstream in addi
- Original Message -
>
>
> - Original Message -
> > [quoted lines by Jaroslav Skarvada on 2018/04/24 at 16:49 -0400]
> >
> > >It didn't work for me. There is original build log:
> > >https://kojipkgs.fedoraproject.org/packages/brltt
- Original Message -
> [quoted lines by Jaroslav Skarvada on 2018/04/24 at 16:49 -0400]
>
> >It didn't work for me. There is original build log:
> >https://kojipkgs.fedoraproject.org/packages/brltty/5.6/7.fc29/data/logs/x86_64/build.log
>
> okay, I didn't full
Hi,
there is the following downstream Fedora bugzilla [1] requesting
the drivers to be build with the distribution LDFLAGS.
I used the attached hack to fix the problem, but I think it
should be also addressed upstream (probably more clean way)
thanks & regards
Jaroslav
[1]
- Original Message -
>
>
> - Original Message -
> >
> >
> > - Original Message -
> > > The gcc reponse to this problem is "not a bug" since the standard
> > > requires
> > > len=1 as the only valid thing for type c_char in the iso_c_binding
> > > The FORTRAN group
- Original Message -
>
>
> - Original Message -
> > The gcc reponse to this problem is "not a bug" since the standard requires
> > len=1 as the only valid thing for type c_char in the iso_c_binding
> > The FORTRAN group response is that gcc has had a bug allowing len>1 since
>
- Original Message -
> The gcc reponse to this problem is "not a bug" since the standard requires
> len=1 as the only valid thing for type c_char in the iso_c_binding
> The FORTRAN group response is that gcc has had a bug allowing len>1 since
> this has been true since FORTRAN 2003.
>
>
i,c)
> use, intrinsic :: iso_c_binding, only: c_char
> integer i
> type, bind(C) :: params_block
> character(kind=c_char,len=10) :: c
> end type params_block
> write(*,*) 'X',c,'Z'
> end
>
> de Mike W9MDB
>
> On Thursday, March 15, 2018, 6:09:27 AM CDT, Jaros
Hi,
with gfortran 8.0.1 the compilation of wsjtx fails with the following error:
make[2]: Leaving directory '/builddir/build/BUILD/wsjtx-1.9.0-rc2/wsjtx/build'
jt9com.f90:44:47:
Error: Component 'datetime' of BIND(C) type at (1) must have length one
jt9com.f90:45:45:
Error: Component 'mycall'
- Original Message -
> On Fri, Jan 19, 2018 at 9:03 AM, Jaroslav Skarvada < jskar...@redhat.com >
> wrote:
>
>
>
>
>
>
> OK, no problem, I added you. I have no problem with EPEL-7, I didn't request
> it in the beginning, just because I didn't
- Original Message -
> I somehow completely missed that. I've been maintaining a COPR for some time
> now which includes support for EL 7.
> If you want to add me as a maintainer (FAS: hobbes1069) I'll put in a ticket
> for EPEL 7 so I can close my COPR.
> Thanks,
> Richard
OK, no
>> On Fri, Jan 19, 2018 at 6:44 AM, Jaroslav Skarvada <jskar...@redhat.com>
>> wrote:
>> I am Fedora packager, and AFAIK the answer is NO. Also it seems there is
>> no Fedora global policy about it. Just rpmlint is complaining. I fixed the
>> spec not to enfor
> stack, are the Fedora team really going to deny that technique for all
> applications?
I am Fedora packager, and AFAIK the answer is NO. Also it seems there is
no Fedora global policy about it. Just rpmlint is complaining. I fixed the
spec not to enforce the NX stack and released updated
- Original Message -
> On 18/01/2018 17:38, Jaroslav Skarvada wrote:
>
>
>
> - Original Message -
>
>
>
> Out of curiosity I ran rpmlint on wsjtx and most of the output was pretty
> much what I expected but one line in particular caugh
- Original Message -
> Out of curiosity I ran rpmlint on wsjtx and most of the output was pretty
> much what I expected but one line in particular caught my eye.
>
> wsjtx.x86_64: W: executable-stack /usr/bin/jt9
>
> $ rpmlint -I executable-stack
> executable-stack:
> The binary
- Original Message -
> On 18/01/2018 12:40, Michael Pittaro wrote:
> > I'm seeing a fairly consistent failure where jt9 crashes when it's
> > started by wsjt-x on Fedora 27.
> >
> > The crash happens right after decode starts. It's somewhat
> > intermittent - it seems to always happen
- Original Message -
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Thu, 2017-09-14 at 13:18 -0400, Jaroslav Skarvada wrote:
> > Hi,
> Hi,
> >
> > I am trying to add new package to fedora, I did:
> >
> > $ fedrepo-req wsjtx -t
- Original Message -
> Hi,
>
> I am trying to add new package to fedora, I did:
>
> $ fedrepo-req wsjtx -t 1487776 -m monitoring
> Error: The Bugzilla ticket could not be verified. The following error was
> encountered: have expired. You may login again to get new cookies or a new
1 - 100 of 228 matches
Mail list logo
