Re: Looking for advice - ffmpeg-free and wf-recorder

[Bob Hepple]

> What if you use libvpx-vp9 for video, opus for audio, and use an mkv file
extension? Does it work better?

No, it doesn't  ...

$ wf-recorder -c libvpx-vp9 -C opus -f recording.mkv
$ file recording.mkv
recording.mkv: Matroska data

... but it still takes a looong time to build the index.

On VP9:
Maybe I'll just settle on libvpx-vp9 and patch the source so that on SIGINT
it prints "SIGINT received: please wait for index building". That's the
easiest fix - but maybe we'll get 'oh fedora is s slw' whinges.

On VP8:
alabastr gave me the hint that using "--muxer webm" would make v8 work -
and it terminates quickly, so this is another possibility.
The only question is - is it naf to have a webm in an mp4? Also, is it too
naf to patch the source to force '--muxer webm' if codec is detected as
libvpx?

$ wf-recorder -c libvpx -m webm
Output file "recording.mp4" exists. Overwrite? Y/n: y
selected region 0,0 0x0
Using video filter: null
[libvpx @ 0x7f6d40001e80] v1.12.0
[libvpx @ 0x7f6d40001e80] Neither bitrate nor constrained quality
specified, using default CRF of 32 and bitrate of 256kbit/sec
Output #0, webm, to 'recording.mp4':
  Stream #0:0: Video: vp8, yuv420p(pc), 1920x1080 [SAR 1:1 DAR 16:9],
q=2-31, 256 kb/s
^C
$ file recording.mp4
recording.mp4: WebM  <<<<< TOO NAF?

On Sun, 18 Dec 2022 at 10:54, Neal Gompa  wrote:

> On Sat, Dec 17, 2022 at 7:49 PM Bob Hepple  wrote:
> >
> > Thanks to all of you for the helpful hints!
> >
> > I will release in f37 too as suggested - I understand that I can only
> retire from rpmfusion in rawhide/f38, but I guess that's OK.
> >
> > libvpx-vp9 does indeed work in both ffmpegs - the only downside is that
> it takes >25s to terminate on SIGINT ^C (the normal way to stop
> wf-recorder). Many users will grow impatient and use pkill/SIGTERM and get
> a corrupt mp4 file - I certainly did at first. Not the best experience. I
> have taken this up with upstream.
> >
> > libvpx (vp8) does not work at all - again, maybe an upstream issue.
> >
> > So I don't have an ideal codec candidate that I am quite happy to
> unleash on the world at the moment - upstream may give me a clue.
> >
> > Or should I just go ahead with libvpx-vp9?
> >
>
> What if you use libvpx-vp9 for video, opus for audio, and use an mkv
> file extension? Does it work better?
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Looking for advice - ffmpeg-free and wf-recorder

[Bob Hepple]

Thanks to all of you for the helpful hints!

I will release in f37 too as suggested - I understand that I can only
retire from rpmfusion in rawhide/f38, but I guess that's OK.

libvpx-vp9 does indeed work in both ffmpegs - the only downside is that it
takes >25s to terminate on SIGINT ^C (the normal way to stop wf-recorder).
Many users will grow impatient and use pkill/SIGTERM and get a corrupt mp4
file - I certainly did at first. Not the best experience. I have taken this
up with upstream.

libvpx (vp8) does not work at all - again, maybe an upstream issue.

So I don't have an ideal codec candidate that I am quite happy to unleash
on the world at the moment - upstream may give me a clue.

Or should I just go ahead with libvpx-vp9?


Cheers


Bob


On Sat, 17 Dec 2022 at 20:44, Neal Gompa  wrote:

> On Sat, Dec 17, 2022 at 12:29 AM Bob Hepple  wrote:
> >
> > I am the packager for wf-recorder (a wl-roots/wayland screen recorder)
> which presently resides in rpmfusion - it uses proprietary ffmpeg codecs by
> default (libx246).
> >
> > Now that we have ffmpeg-free we have an opportunity to move wf-recorder
> to the mainstream and change the default codec to the non-proprietary
> libopenh264. This woud be in rawhide/f38 and on.
> >
> > This all works fine in testing on f37. The fly in the ointment is that
> if ffmpeg/rpmfusion is installed in place of ffmpeg-free, then wf-recorder
> can no longer access libopenh264 and fails with an error. There is a
> workaround in the use of the option -c libx264.
> >
> > Several solutions occur to me and I'm looking for guidance on which path
> to take:
> >
> > 0. leave wf-recorder where it is, in rpmfusion as in f37 and earlier.
> > A. compile wf-recorder as shipped by upstream with the default libx264 -
> the '-c libopenh264' workaround would be needed if ffmpeg-free is
> installed. This annoys users who install stock fedora.
> > B. compile wf-recorder with libopenh264 as the default - the '-c
> libx264' workaround would be needed if ffmpeg/rpmfusion is installed and
> would annoy those users.
> > C. leave wf-recorder in rpmfusion and create a wf-recorder-free package
> by analogy to ffmpeg (this might be obscure as it's not likely to get much
> publicity - and annoy everyone sooner or later)
> > D. the best option might be to choose a codec common to both ffmpeg and
> ffmpeg-free. I'm not terribly au fait with the various codecs so which
> would I choose? These codecs appear to be in both packages:
> >
>
> I suggest going with option D, and my suggestion is libvpx-vp9.
>
> libvpx-vp9 is common to both and reasonably fast. I made a similar
> change to O3DE some time ago for similar reasons:
>
> https://github.com/o3de/o3de/commit/add4ad4ad42fe36b04e80b3ee4ab2358fe5fd35e
>
>
>
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Looking for advice - ffmpeg-free and wf-recorder

[Bob Hepple]

I am the packager for wf-recorder (a wl-roots/wayland screen recorder)
which presently resides in rpmfusion - it uses proprietary ffmpeg codecs by
default (libx246).

Now that we have ffmpeg-free we have an opportunity to move wf-recorder to
the mainstream and change the default codec to the non-proprietary
libopenh264. This woud be in rawhide/f38 and on.

This all works fine in testing on f37. The fly in the ointment is that if
ffmpeg/rpmfusion is installed in place of ffmpeg-free, then wf-recorder can
no longer access libopenh264 and fails with an error. There is a workaround
in the use of the option -c libx264.

Several solutions occur to me and I'm looking for guidance on which path to
take:

0. leave wf-recorder where it is, in rpmfusion as in f37 and earlier.
A. compile wf-recorder as shipped by upstream with the default libx264 -
the '-c libopenh264' workaround would be needed if ffmpeg-free is
installed. This annoys users who install stock fedora.
B. compile wf-recorder with libopenh264 as the default - the '-c libx264'
workaround would be needed if ffmpeg/rpmfusion is installed and would annoy
those users.
C. leave wf-recorder in rpmfusion and create a wf-recorder-free package by
analogy to ffmpeg (this might be obscure as it's not likely to get much
publicity - and annoy everyone sooner or later)
D. the best option might be to choose a codec common to both ffmpeg and
ffmpeg-free. I'm not terribly au fait with the various codecs so which
would I choose? These codecs appear to be in both packages:

 h263_v4l2m2m V4L2 mem2mem H.263 encoder wrapper (codec h263)
 h264_amf AMD AMF H.264 Encoder (codec h264)
 h264_nvenc   NVIDIA NVENC H.264 encoder (codec h264)
 h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel
Quick Sync Video acceleration) (codec h264)
 h264_v4l2m2m V4L2 mem2mem H.264 encoder wrapper (codec h264)
 h264_vaapi   H.264/AVC (VAAPI) (codec h264)
 hevc_amf AMD AMF HEVC encoder (codec hevc)
 hevc_nvenc   NVIDIA NVENC hevc encoder (codec hevc)
 hevc_qsv HEVC (Intel Quick Sync Video acceleration) (codec
hevc)
 hevc_v4l2m2m V4L2 mem2mem HEVC encoder wrapper (codec hevc)
 hevc_vaapi   H.265/HEVC (VAAPI) (codec hevc)
 libaom-av1   libaom AV1 (codec av1)
libopenjpeg  OpenJPEG JPEG 2000 (codec jpeg2000)
 librav1e librav1e AV1 (codec av1)
 libsvtav1SVT-AV1(Scalable Video Technology for AV1) encoder
(codec av1)
 libtheoralibtheora Theora (codec theora)
 libvpx   libvpx VP8 (codec vp8)
 libvpx-vp9   libvpx VP9 (codec vp9)
 libwebp_anim libwebp WebP image (codec webp)
 libwebp  libwebp WebP image (codec webp)
 mjpeg_qsvMJPEG (Intel Quick Sync Video acceleration) (codec
mjpeg)
 mjpeg_vaapi  MJPEG (VAAPI) (codec mjpeg)
 mpeg2_qsvMPEG-2 video (Intel Quick Sync Video acceleration)
(codec mpeg2video)
 mpeg2_vaapi  MPEG-2 (VAAPI) (codec mpeg2video)
 mpeg4_v4l2m2mV4L2 mem2mem MPEG4 encoder wrapper (codec mpeg4)
 vp8_v4l2m2m  V4L2 mem2mem VP8 encoder wrapper (codec vp8)
 vp8_vaapiVP8 (VAAPI) (codec vp8)
 vp9_qsv  VP9 video (Intel Quick Sync Video acceleration)
(codec vp9)
 vp9_vaapiVP9 (VAAPI) (codec vp9)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Question about git signed tags

[Bob Hepple]

Thanks to all respondents - an interesting discussion. I think I'm now
equipped to respond to upstream.

Bob

On Wed, 30 Nov 2022 at 08:15, Björn Persson  wrote:

> Vitaly Zaitsev via devel wrote:
> > On 29/11/2022 17:33, Todd Zullinger wrote:
> > > One of reasons being that it's (at least slightly) easier to
> > > notice a change to the public key / keyring when it's in
> > > dist-git versus the lookaside cache
> >
> > It depends on public key format. Armored (ASCII format) vs. binary keys.
> >
> > Storing binaries in Git is a bad idea.
>
> Why is that? Does 8-bit data break Git somehow?
>
> A key is a small file. It doesn't bloat the repository like a tarball
> would. When a key needs replacing, the new key is entirely different
> whether it's ASCII-armored or not, so there's nothing to gain by
> storing a diff instead of the whole file.
>
> ASCII-armor is for sending messages over old 7-bit protocols, just like
> Base64 and UUencoding. In 8-bit-clean channels ASCII-armor doesn't
> accomplish anything other than making the message slightly larger. I
> can't believe that Git wouldn't be 8-bit-clean.
>
> Björn Persson
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Question about git signed tags

[Bob Hepple]

Here's a question from one of my upstream devels. Not sure I understand
exactly what he's asking but I thought I'd post here in the hope that
someone can enlighten him (and me!).

"... Arch supports signed git tags. I'm hoping Fedora does too.

I'm thinking of dropping this cumbersome process (i.e: signing and pushing
the .sig and .tar.gz) for the next release. Simply sign the tag and create
a release out of it. Can you please do a bit of research on your side to
see if that's possible?

Also, for your consideration, git now supports ssh-based signatures
. I won't stop using
PGP because I think distros don't support this very well but just so you
know."

If we _do_ support "signed git tags" how do we code for it in the spec
file? Presently I have this:

Source0: %{url}/releases/download/v%{version}/%{name}-%{version}.tar.gz
Source1: %{url}/releases/download/v%{version}/%{name}-%{version}.tar.gz.sig
Source2: 6A6B35DBE9442683.gpg

...

%prep
%gpgverify -k 2 -s 1 -d 0
%autosetup -p1



Thanks



Bob
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: -D_FORTIFY_SOURCE not defined errors

[Bob Hepple]

Hrmph! Those errors are gone but I now have others - looks like the
compiler has become much stricter:

/usr/include/c++/12/bits/basic_string.h:235:28: error: 'MEM[(const
struct basic_string *) + 176B]._M_dataplus._M_p' may be used
uninitialized [-Werror=maybe-uninitialized]

Hopefully I can patch them.

Cheers


Bob

On Sun, 30 Jan 2022 at 00:19, Sérgio Basto  wrote:
>
> On Sat, 2022-01-29 at 09:56 +0100, Jakub Jelinek wrote:
> > On Sat, Jan 29, 2022 at 04:03:06PM +1000, Bob Hepple wrote:
> > > One of my packages, stable for a long time, is now getting exotic
> > > errors in rawhide such as
> > >
> > > -D_FORTIFY_SOURCE not defined
> > > -D_GLIBCXX_ASSERTIONS not defined
> > >
> > > Yesterday I saw (somewhere in here) that those errors are fixed in
> > > the
> > > latest annobin.
> > >
> > > Should I just wait for that fix to land in koji? If so, how long?
> >
> > It was fixed yesterday.
> > Are you sure your builds were against
> > gcc-12.0.1-0.3.fc36 annobin-10.51-2.fc36
> > and not an older version of annobin?
>
> But rawhide compose of last 2 days failed , so new annobin is not in
> buildroot  and this problem will still happen on copr for example
>
> > Jakub
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> > Do not reply to spam on the list, report it:
> > https://pagure.io/fedora-infrastructure
>
> --
> Sérgio M. B.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

-D_FORTIFY_SOURCE not defined errors

[Bob Hepple]

One of my packages, stable for a long time, is now getting exotic
errors in rawhide such as

-D_FORTIFY_SOURCE not defined
-D_GLIBCXX_ASSERTIONS not defined

Yesterday I saw (somewhere in here) that those errors are fixed in the
latest annobin.

Should I just wait for that fix to land in koji? If so, how long?

Thanks

Bob
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Let's retire original glib and gtk+

[Bob Hepple]

There may be more to that iceberg than appears above the surface in
the form of non-distributed or private software outside the realm of
the public repositories.

As for examples, I can only point to some of my own ancient binaries
which I would certainly not suggest as a plea to preserve glib1.

But there may be other more significant interests with software
vendors and large private users.

I have no idea how significant this might be, but perhaps this should
be discussed more publicly.

Cheers


Bob

On Sat, 8 May 2021 at 00:45, Michael Catanzaro  wrote:
>
> Hi, I'd like to retire the original glib, GLib 1 from the GNOME 1 era.
> This is would take out the gtk+ package (GTK 1) along with it. (I'm not
> proposing to remove GTK 2.) GLib 1 has been obsolete for 19 years now,
> since GLib 2 was released in March 2002. That's a real long time to
> maintain a compatibility package, so I'm not sympathetic to anything
> that still requires it.
>
> GLib 2 has been API and ABI stable for 19 years now, so it's not moving
> too fast for your package to depend on. :) The full list of packages
> still depending on GLib 1 is below. If you own one of the below
> packages, please consider upgrading to GLib 2. The only one that I
> recognize is Sagemath.
>
> $ sudo dnf repoquery --recursive --whatrequires glib
> Last metadata expiration check: 0:28:04 ago on Fri 07 May 2021 09:06:03
> AM CDT.
> Singular-0:4.1.1p3-24.fc34.x86_64
> Singular-doc-0:4.1.1p3-24.fc34.x86_64
> Singular-emacs-0:4.1.1p3-24.fc34.x86_64
> Singular-surfex-0:4.1.1p3-24.fc34.x86_64
> bubblemon-0:1.46-29.fc34.x86_64
> collectd-xmms-0:5.12.0-2.fc34.x86_64
> gap-pkg-happrime-0:0.6-5.20190208.edfbd41.fc34.noarch
> gap-pkg-happrime-doc-0:0.6-5.20190208.edfbd41.fc34.noarch
> gap-pkg-singular-0:2020.12.18-2.fc34.noarch
> gap-pkg-singular-doc-0:2020.12.18-2.fc34.noarch
> glib-devel-1:1.2.10-62.fc34.i686
> glib-devel-1:1.2.10-62.fc34.x86_64
> golang-github-mattn-gtk-devel-0:0-0.7.20200729gitaf2e013.fc34.noarch
> gtk+-1:1.2.10-96.fc34.i686
> gtk+-1:1.2.10-96.fc34.x86_64
> gtk+-devel-1:1.2.10-96.fc34.i686
> gtk+-devel-1:1.2.10-96.fc34.x86_64
> gxvattr-0:1.3-42.fc34.x86_64
> librcc-devel-0:0.2.12-18.fc34.i686
> librcc-devel-0:0.2.12-18.fc34.x86_64
> librcc-gtk+-0:0.2.12-18.fc34.i686
> librcc-gtk+-0:0.2.12-18.fc34.x86_64
> logjam-xmms-1:4.6.2-25.fc34.x86_64
> manedit-0:1.2.1-25.fc34.x86_64
> qepcad-B-0:1.74-1.fc34.x86_64
> sagemath-0:9.2-4.fc34.x86_64
> sagemath-core-0:9.2-4.fc34.x86_64
> sagemath-data-0:9.2-4.fc34.noarch
> sagemath-data-combinatorial_designs-0:9.2-4.fc34.noarch
> sagemath-data-conway_polynomials-0:9.2-4.fc34.noarch
> sagemath-data-elliptic_curves-0:9.2-4.fc34.noarch
> sagemath-data-elliptic_curves_large-0:9.2-4.fc34.noarch
> sagemath-data-etc-0:9.2-4.fc34.noarch
> sagemath-data-graphs-0:9.2-4.fc34.noarch
> sagemath-data-polytopes_db-0:9.2-4.fc34.noarch
> sagemath-jupyter-0:9.2-4.fc34.x86_64
> sagemath-sagetex-0:9.2-4.fc34.x86_64
> surf-geometry-0:1.0.6-29.fc34.x86_64
> xarchon-0:0.50-35.fc34.x86_64
> xconvers-0:0.8.3-27.fc34.x86_64
> xdialog-0:2.3.1-28.fc34.x86_64
> xmms-1:1.2.11-41.20071117cvs.fc34.x86_64
> xmms-devel-1:1.2.11-41.20071117cvs.fc34.i686
> xmms-devel-1:1.2.11-41.20071117cvs.fc34.x86_64
> xmms-flac-0:1.3.3-7.fc34.x86_64
> xmms-libs-1:1.2.11-41.20071117cvs.fc34.i686
> xmms-libs-1:1.2.11-41.20071117cvs.fc34.x86_64
> xmms-pulse-0:0.9.4-27.fc34.x86_64
>
> Michael
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

wdisplays - change of license and new repo

[Bob Hepple]

In the case of https://github.com/cyclopsian/wdisplays the author's
entire corpus has gone. I believe his fleshware name is Jason Francis.
It was licensed "MIT and GPLv3+ and CC0 and CC-BY-SA". I've had no
response from his latest email address.

There is a new repo https://github.com/artizirk/wdisplays which is a
copy of the original - and I have exchanged email with the owner who
has committed  to supporting it. The ARCH project has adopted it.

He has also changed the license to "GPLv3+"

I intend to re-base the package to the artizirk repo and release
version 1.1 (which contains fixes by the maintainer of sway
'emersion')

Cheers


Bob
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: How to build CPM.cmake packages?

[Bob Hepple]

Thanks Vitaly,

I'll follow up on that this week.

Cheers


Bob

On Sat, 16 Jan 2021 at 20:45, Vitaly Zaitsev via devel
 wrote:
>
> On 16.01.2021 08:57, Bob Hepple wrote:
> > Any ideas how to overcome this?
>
> UPD: CPM can use packaged versions[1]. You just need to forward
> -DCPM_USE_LOCAL_PACKAGES:BOOL=TRUE.
>
> Example:
>
> %build
> %cmake \
>  -DCPM_USE_LOCAL_PACKAGES:BOOL=TRUE \
>  -DCPM_LOCAL_PACKAGES_ONLY:BOOL=TRUE
>
> [1]: https://github.com/TheLartians/CPM.cmake#cpm_use_local_packages
>
> --
> Sincerely,
>Vitaly Zaitsev (vit...@easycoding.org)
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

How to build CPM.cmake packages?

[Bob Hepple]

One of my packages has started to use CPM.cmake
(https://github.com/TheLartians/CPM.cmake) which is a "Setup-free
CMake dependency management" addon script for cmake.

I'm hoping someone out there has some expertise and can coach me
through this - I'm frankly bewildered by it.

My problem is that CPM.cmake requires the use of the network at build
time to download CPM.cmake itself and then to download the source of
various dependency libraries. This is forbidden in fedora by
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_build_time_network_access
- fedora builds must be done offline.

Any ideas how to overcome this?

I had thought of building it on my local machine, doing a 'make clean'
equiv and using that as a tarball including all the dependency
libraries. But that seems rather naff.


TIA


Bob
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: ShotCut: dependency problems

[Bob Hepple]

Works for me on f32: http://ix.io/2LCc


On Mon, 11 Jan 2021 at 08:38, Marius Schwarz  wrote:
>
> Hi,
>
> it's impossible to install Shotcut, not as 20.11.28 nor 20.04.12 :
>
>
> $ sudo dnf install shotcut
> [sudo] Passwort für X:
> Letzte Prüfung auf abgelaufene Metadaten: vor 0:01:11 am So 10 Jan 2021
> 23:23:40 CET.
> Fehler:
>   Problem: conflicting requests
>- package shotcut-20.11.28-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_6.22.0)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3()(64bit), but none of the providers can be installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_0.8.8)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_0.9.0)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_0.9.2)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_0.9.4)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_0.9.8)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_6.10.0)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_6.14.0)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_6.18.0)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_6.20.0)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt++.so.3(MLTPP_6.8.0)(64bit), but none of the providers can be
> installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt.so.6()(64bit), but none of the providers can be installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt.so.6(MLT_0.8.8)(64bit), but none of the providers can be installed
>- package shotcut-20.04.12-1.fc32.x86_64 requires
> libmlt.so.6(MLT_6.8.0)(64bit), but none of the providers can be installed
>- package mlt-6.22.1-1.fc32.x86_64 requires opencv-core, but none of
> the providers can be installed
>- package mlt-6.20.0-1.fc32.x86_64 requires opencv-core, but none of
> the providers can be installed
>- package opencv-core-4.2.0-8.fc32.i686 requires libClp.so.1, but
> none of the providers can be installed
>- package opencv-core-4.2.0-5.fc32.i686 requires libClp.so.1, but
> none of the providers can be installed
>- package opencv-core-4.2.0-8.fc32.x86_64 requires
> libClp.so.1()(64bit), but none of the providers can be installed
>- package opencv-core-4.2.0-5.fc32.x86_64 requires
> libClp.so.1()(64bit), but none of the providers can be installed
>- package coin-or-Clp-1.17.5-1.fc32.i686 requires libCbc.so.3, but
> none of the providers can be installed
>- package coin-or-Clp-1.17.5-1.fc32.x86_64 requires
> libCbc.so.3()(64bit), but none of the providers can be installed
>- package coin-or-Cbc-2.10.5-2.fc32.i686 requires libasl.so.3, but
> none of the providers can be installed
>- package coin-or-Cbc-2.10.5-1.fc32.i686 requires libasl.so.3, but
> none of the providers can be installed
>- package coin-or-Cbc-2.10.5-2.fc32.x86_64 requires
> libasl.so.3()(64bit), but none of the providers can be installed
>- package coin-or-Cbc-2.10.5-1.fc32.x86_64 requires
> libasl.so.3()(64bit), but none of the providers can be installed
>- package mp-3.1.0-26.20200215git71c21a5.fc32.i686 requires jacop,
> but none of the providers can be installed
>- package mp-3.1.0-26.20200215git71c21a5.fc32.x86_64 requires jacop,
> but none of the providers can be installed
>- package jacop-4.7-1.fc32.noarch requires
> mvn(org.scala-lang:scala-library), but none of the providers can be
> installed
>- package jacop-4.7-1.fc32.noarch requires
> mvn(org.scala-lang:scala-compiler), but none of the providers can be
> installed
>- package scala-2.10.6-17.fc32.noarch is filtered out by modular
> filtering
> (try to add '--skip-broken' to skip uninstallable packages)
>
>
> best regards,
> Marius
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To 

Change of License - ydotool

[Bob Hepple]

Ref: https://github.com/ReimuNotMoe/ydotool

The author has changed from MIT to AGPLv3 which is on the 'good' list
but I am required to post the change here for comment.

The author has also declared an intention to apply for a copyright in
China. Does that change anything? I'm guessing not.

Comments?

Here is the pertinent paragraph:

Licensing

The license has been changed to AGPLv3, to stop large tech companies
from modifying this project and only use internally.

In order to (hopefully) stop these free software license violations in
China, the project is going to apply for a software copyright (软件著作权)
in China. Doing so will give me a way to sue them.

If you want to contribute to this project from now on, you need to
agree that your work will be copyrighted by me (only in China).

If you are a former contributor and you don't want your work to be
copyrighted by me in China, please open an issue to let me know. I
will then replace your work with a clean room implementation.

If you know a free software license violation of this project, please
don't hesitate to let me know.

ydotool will always be a free software.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Self Introduction: Tom Yates

[Bob Hepple]

Welcome!

FWIW I'm probably older and yes - I used to use RCS (and sccs, cvs,
perforce, svn) and I still use ESR's SRC package (which is based on
RCS) on a daily basis:

https://www.emacswiki.org/emacs/VersionControlAlways
FAQ http://www.catb.org/~esr/src/FAQ.html
resources http://www.catb.org/~esr/src/
man page http://www.catb.org/~esr/src/src.html
source: https://gitlab.com/esr/src

... not for Fedora stuff obviously, as that's all git, but for my
small stuff like config and .org files

Hope you enjoy your time here ...


Cheers


Bob

On Tue, 15 Sep 2020 at 21:50, Tom Yates  wrote:
>
> Hello.  I'm Tom Yates, I've been using free software since the late '80s,
> and Red Hat since RHL 4.2 (ie, the late '90s).  Because I'm really that
> ancient, I fairly extensively use RCS (a very old revision control system)
> and am posting with a view to becoming co-maintainer for an RCS package in
> EPEL for RHEL8 (and later).
>
> During work times I'm principally a consultant free software sysadmin,
> with a sideline in writing, mostly for LWN.
>
>
> --
>
>Tom Yates  -  
> https://www.teaparty.net___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Review swap: wlr-sunclock - Show the sun's shadows on earth (for wayland)

[Bob Hepple]

Thanks Carson,

I'm up for that ...

See you in bugzilla ...


Cheers


Bob

On Mon, 17 Aug 2020 at 13:01, Carson Black  wrote:
>
> Ello,
>
> The review process is documented on the wiki here:
> https://fedoraproject.org/wiki/Package_Review_Process
> In short, set the fedora-review flag on the bug to ? when you're
> reviewing a package. When you approve a package, change the flag to +.
>
> I'll take this review swap. In return, I'd appreciate it if you
> reviewed https://bugzilla.redhat.com/show_bug.cgi?id=1869128, which is
> also a fairly straightforward package using meson.
>
> Thanks,
>
> -- Carson Black [ jan Pontajosi ]
>
>
> Am So., 16. Aug. 2020 um 21:16 Uhr schrieb Bob Hepple :
> >
> > Hi,
> >
> > I'm still not 100% sure that I'm able to approve a package - I have
> > "Fedora Packager GIT Commit Group (packager)", I've been through
> > sponsorship and I've had packages approved and released. If someone
> > can point out the doco on this point, I'd be grateful as my searches
> > haven't come up with anything yet.
> >
> > I'm willing to try a review swap for a simple package - I'm still new to 
> > this.
> >
> > This one has been open for 10 days, It's a simple meson package but
> > rather fun for the desktop:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1867267
> >
> >
> > Thanks
> >
> >
> > Bob
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Review swap: wlr-sunclock - Show the sun's shadows on earth (for wayland)

[Bob Hepple]

Hi,

I'm still not 100% sure that I'm able to approve a package - I have
"Fedora Packager GIT Commit Group (packager)", I've been through
sponsorship and I've had packages approved and released. If someone
can point out the doco on this point, I'd be grateful as my searches
haven't come up with anything yet.

I'm willing to try a review swap for a simple package - I'm still new to this.

This one has been open for 10 days, It's a simple meson package but
rather fun for the desktop:

https://bugzilla.redhat.com/show_bug.cgi?id=1867267


Thanks


Bob
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Need a package review (aml)

[Bob Hepple]

it's done - Thanks Aleksei!

On Tue, 4 Aug 2020 at 12:02, Bob Hepple  wrote:
>
> Hi,
>
> The upstream author of wayvnc (a VNC server for Wayland) has split
> some code out into a separate tiny package (aml) for which I'm waiting
> to get a review request done, since 28th July.
>
> I'm blocked from packaging the new release wayvnc-0.2.0 until that one
> is done and I need to get that new version out as it has a fix for the
> FTBFS errors on rawhide/f33.
>
> Sorry if this is the wrong place to ask for this - I see people
> offering review swaps but I don't think I'm authorised to do reviews.
>
> Anyways, if anyone can do me a review, I'll be ever grateful. It's a
> very small, simple package.
>
> The bugzilla is here: https://bugzilla.redhat.com/show_bug.cgi?id=1861216
>
> Thanks
>
>
> Bob
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Need a package review (aml)

[Bob Hepple]

Hi,

The upstream author of wayvnc (a VNC server for Wayland) has split
some code out into a separate tiny package (aml) for which I'm waiting
to get a review request done, since 28th July.

I'm blocked from packaging the new release wayvnc-0.2.0 until that one
is done and I need to get that new version out as it has a fix for the
FTBFS errors on rawhide/f33.

Sorry if this is the wrong place to ask for this - I see people
offering review swaps but I don't think I'm authorised to do reviews.

Anyways, if anyone can do me a review, I'll be ever grateful. It's a
very small, simple package.

The bugzilla is here: https://bugzilla.redhat.com/show_bug.cgi?id=1861216

Thanks


Bob
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Fedora Packager Dashboard available for testing

[Bob Hepple]

Nice!

Is the ourobolos (the snake eating its own tail) supposed to animate
all the time? To me, that kinda sorta means something is working - but
what? Hovering over it gives no clue.

Or should I just wait a bit longer for it to finish? (I already waited
a few minutes)

Cheers


Bob


On Wed, 24 Jun 2020 at 02:29, Josef Skladanka  wrote:
>
> Hi,
>
> We'd like to announce public testing of the Packager Dashboard - a new
> service for Fedora package maintainers aiming to provide all relevant
> data: FTBFS/FTI status (from both Bugzilla, Koschei and health check),
> orphan warnings, bugzillas, pull requests, active overrides and
> updates - at a single place in an easy to read and filter way.
>
> The Dashboard is now available: https://packager.fedorainfracloud.org/
>
> Packager Dashboard leverages caching in the Oraculum backend to
> significantly speed-up loading times with comparison to querying all
> the relevant resources separately. We, of course, can't cache the
> entire Bugzilla, Pagure, Bodhi... so we only cache data for users who
> visit Packager Dashboard at least once per 14 days. Please keep in
> mind that the first load for a “new” user might take a while. Most of
> the data sources are refreshed every hour.
>
> You can use the Dashboard for individual accounts as well as for FAS groups.
>
> We'd love to hear your feedback. Please keep in mind that this is
> testing deployment - it's currently running on a server with very
> limited resources and we're aiming for production deployment on
> CommuniShift during this summer.
>
> Feel free to provide ideas or bug reports at
> https://pagure.io/fedora-qa/packager_dashboard or simply send an email
> reply to this thread with all kinds of feedback.
>
> I'd like to mention the other people who made this possible:
>  - Miro Hrončok (churchyard) - Original idea
> 
> and ideas for data to display
>  - František Zatloukal - Backend 
>  - Lukáš Brabec - Frontend 
>
> Josef
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Review request

[Bob Hepple]

Thanks!

On Mon, 4 May 2020 at 18:12, Vascom  wrote:
>
> I will do it.
>
> пн, 4 мая 2020 г., 11:03 Bob Hepple :
>>
>> Hello,
>>
>> Although I'm new here, I've had a few packages go through review
>> already and I'm very grateful for the help and education provided by
>> the reviewers.
>>
>> But there is one package that I put up for review about a month ago
>> and I haven't had any luck in attracting a reviewer. It's here -
>> https://bugzilla.redhat.com/show_bug.cgi?id=1821172
>>
>> Now it may have been my fault as at the time I thought I was supposed
>> to include a run of fedora-review, and prospective reviewers may have
>> scanned the request and assumed that it has already been reviewed.
>>
>> If anyone out there in reviewer-land would like to take a look at the
>> package I think it could be a useful addition to the fedora wayland
>> offering. The short description is:
>>
>> wl-gammactl - Small GTK GUI application to set contrast, brightness
>> and gamma for wayland compositors
>>
>> Thanks muchly
>>
>> Bob Hepple
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Review request

[Bob Hepple]

Hello,

Although I'm new here, I've had a few packages go through review
already and I'm very grateful for the help and education provided by
the reviewers.

But there is one package that I put up for review about a month ago
and I haven't had any luck in attracting a reviewer. It's here -
https://bugzilla.redhat.com/show_bug.cgi?id=1821172

Now it may have been my fault as at the time I thought I was supposed
to include a run of fedora-review, and prospective reviewers may have
scanned the request and assumed that it has already been reviewed.

If anyone out there in reviewer-land would like to take a look at the
package I think it could be a useful addition to the fedora wayland
offering. The short description is:

wl-gammactl - Small GTK GUI application to set contrast, brightness
and gamma for wayland compositors

Thanks muchly

Bob Hepple
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Unretire gjots2 (gtk heirarchical note jotter)

[Bob Hepple]

Done - https://bugzilla.redhat.com/show_bug.cgi?id=1823599

On Fri, 17 Apr 2020 at 12:50, Bob Hepple  wrote:
>
> Well I eventually woke up, got out of bed and read my email!!
>
> I'll fix up the address and rebuild, no problemo.
>
> Cheers
>
>
> Bob
>
> On Wed, 15 Apr 2020 at 01:06, Petr Pisar  wrote:
> >
> > On Tue, Apr 14, 2020 at 04:51:04PM +0200, Alexander Ploumistos wrote:
> > > On Tue, Apr 14, 2020 at 4:40 PM Petr Pisar  wrote:
> > > >
> > > > On Tue, Apr 14, 2020 at 04:27:06PM +0200, Alexander Ploumistos wrote:
> > > > > The FSF address should be the most straightforward to fix.
> > > > >
> > > > Straightforward, but impossible for a pacakger. Because it's a part of 
> > > > the
> > > > license declaration, only an author can change it, as the license reads:
> > > >
> > > > [...]keep intact all the
> > > > notices that refer to this License [...]
> > > >
> > > > That's the reason why I consider this rpmlint warning quite unhelpful.
> > > >
> > >
> > > Do you mean the author of the software or the license?
> >
> > Author of the software. Author can replace the license declaration as well 
> > the
> > license text.
> >
> > > I've seen that debated over and over again and my understanding is that
> > > packagers are not supposed to patch the file, but upstream developers 
> > > (which
> > > is the case here) should correct that error.
> >
> > Exactly.
> >
> > > Our wiki links to a version of
> > > GPL 2 with the correct address:
> > > https://fedoraproject.org/wiki/Common_Rpmlint_issues#incorrect-fsf-address
> >
> > That's a new revision of GPL 2. Author of the license, updates it whenever 
> > he
> > moves to a different place. That's fine. Author of the software just copies
> > the updated revision into his software. That's also fine.
> >
> > -- Petr
> >
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Unretire gjots2 (gtk heirarchical note jotter)

[Bob Hepple]

Well I eventually woke up, got out of bed and read my email!!

I'll fix up the address and rebuild, no problemo.

Cheers


Bob

On Wed, 15 Apr 2020 at 01:06, Petr Pisar  wrote:
>
> On Tue, Apr 14, 2020 at 04:51:04PM +0200, Alexander Ploumistos wrote:
> > On Tue, Apr 14, 2020 at 4:40 PM Petr Pisar  wrote:
> > >
> > > On Tue, Apr 14, 2020 at 04:27:06PM +0200, Alexander Ploumistos wrote:
> > > > The FSF address should be the most straightforward to fix.
> > > >
> > > Straightforward, but impossible for a pacakger. Because it's a part of the
> > > license declaration, only an author can change it, as the license reads:
> > >
> > > [...]keep intact all the
> > > notices that refer to this License [...]
> > >
> > > That's the reason why I consider this rpmlint warning quite unhelpful.
> > >
> >
> > Do you mean the author of the software or the license?
>
> Author of the software. Author can replace the license declaration as well the
> license text.
>
> > I've seen that debated over and over again and my understanding is that
> > packagers are not supposed to patch the file, but upstream developers (which
> > is the case here) should correct that error.
>
> Exactly.
>
> > Our wiki links to a version of
> > GPL 2 with the correct address:
> > https://fedoraproject.org/wiki/Common_Rpmlint_issues#incorrect-fsf-address
>
> That's a new revision of GPL 2. Author of the license, updates it whenever he
> moves to a different place. That's fine. Author of the software just copies
> the updated revision into his software. That's also fine.
>
> -- Petr
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Unretire gjots2 (gtk heirarchical note jotter)

[Bob Hepple]

Thanks Alexander,

I am (recently) a member of the packagers group - just finding my feet!

I have done the review request here:
https://bugzilla.redhat.com/show_bug.cgi?id=1823599

I also made a request on releng to resurrect the git repo for f-31, 32 & epel8


Cheers


Bob

On Tue, 14 Apr 2020 at 11:27, Alexander Ploumistos
 wrote:
>
> Hello Bob,
>
> On Tue, Apr 14, 2020 at 3:12 AM Bob Hepple  wrote:
> > I'd like to unretire the package gjots2 package
> > Full disclosure - I'm upstream. The package has been updated to python3
>
> Since gjots2 had been orphaned quite some time ago, it will need to be
> reviewed again:
> https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers
>
> If you are not already a member of the packagers group, the procedure
> in order to join is outlined here:
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
>
> Best regards,
> A.
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Unretire gjots2 (gtk heirarchical note jotter)

[Bob Hepple]

I'd like to unretire the package gjots2 package

Full disclosure - I'm upstream. The package has been updated to python3
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Re: Self Introduction: Bob Hepple

[Bob Hepple]

Hi Kevin,

Pleased to meet you and thanks for the welcome!

Yeah - 30,000 packages out there. More the merrier, of course.

Bob

On Sat, 7 Mar 2020 at 10:59, Kevin Fenzi  wrote:
>
> On Sat, Mar 07, 2020 at 10:00:22AM +1000, Bob Hepple wrote:
> ...snip...
> >
> > That's enough from me, please don't hesitate to contact!
>
> Welcome Bob!
>
> I have too many packages already to take on more, but if you get stuck
> anywhere feel free to drop me a line and I can help out or point you to
> who might be able to help.
>
> Always great to see new folks in the community.
>
> kevin
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org

Self Introduction: Bob Hepple

[Bob Hepple]

Hello.

I'm a 2-years retired engineer with a tediously long resume - in short
I've been packaging RPMs for big and small companies for, h, maybe
20 years. Unix since 1983, Linux since SLS days, kernel 0.9x, then
RedHat/Fedora. I started with Algol, Cobol and Fortran but jumped into
C as soon as I discovered it and loved it. Wrote crypto code for
RSA/BSafe, device drivers for Linux, HPUX, Solaris, AIX etc. Jenkins
CI/CD. Python mostly nowadays - a hobby.

I thought I knew a lot about RPM packaging but discovered there's a
lot of new stuff around and then there are the fedora strict
requirements (rightfully strict).

So, why am I here? I just recently made the jump to wayland / sway on
fedora and found that there were a few packages that I really wanted
but were not yet in fedora - so I built them in COPR for myself and
others to enjoy -
https://www.reddit.com/r/Fedora/comments/fc4qmt/fedora_package_of_wofi11_is_available/.
I suggest that though these packages may be minor and of secondary
importance that they will enhance the sway experience on fedora and
help the move away from X11 - as in my experience.

Some have started the journey into fedora and I had help from a
friendly guy who reviewed a library I packaged -
https://bugzilla.redhat.com/show_bug.cgi?id=1808276

Now I need to take the next step - if anyone wants to adopt one of
those packages, please go ahead (I think imv(1) is already spoken
for). Otherwise if I can have a sponsor I will do my best to get them
into the mainstream and support them.

That's enough from me, please don't hesitate to contact!

Cheers


Bob

Tamborine Mountain
Queensland
Australia
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel@lists.fedoraproject.org