I Inherited a legacy Project using this tool to count pages. I use this tool
as part of a tea4cups hook . are you aware of any substitutes for pkpgcounter
Thanks
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email t
On 7/5/24 17:05, Siteshwar Vashisht wrote:
Hello,
I am writing this message to get feedback from the community on possibly new
defects identified by static analyzers in Critical Path Packages that have
changed in Fedora 41. For context, please see my previous email[1].
TLDR: This report[2] co
Hi all,
a new version rpkg-1.67 together with fedpkg-1.45 are released containing
both features and bugfixes.
Currently, all supported versions (Fedora 39, Fedora 40, Fedora rawhide,
EPEL 8, EPEL 9) are present in stable repositories.
Some subsequent fedpkg updates are waiting in Bodhi.
Changelog
On Tue, Jul 9, 2024 at 2:49 PM Wolfgang Ulbrich wrote:
>
> Btw. Why not splitting anconda RPM in a main part which support only wayland
> with a new sub package for X11?
> Than you can reduce package size for workstation and desktops which are ready
> for wayland.
> In my opinion this is way to
On Tue, Jul 09, 2024 at 04:03:10PM -0400, David Malcolm wrote:
> On Tue, 2024-07-09 at 13:37 +0200, Siteshwar Vashisht wrote:
> > On Tue, Jul 9, 2024 at 1:16 PM Daniel P. Berrangé
> >
> > wrote:
> >
> > > For packages I'm involved in (QEMU, libvirt), there are a huge
> > > number of
> > > reporte
(Message resent due to https://pagure.io/fedora-infrastructure/issue/12046 --
this time only yo devel-announce.)
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 41 approximately one week before branching.
5 weekly re
HISTORY
---
The antlr4-project package was introduced in early 2020. It contains
a parser generator written in Java, and runtimes for various
languages, currently Java, JavaScript, C++, Python, and Go. At the
time, various packages had bundled copies of the language runtimes,
which were moved
On Tue, 2024-07-09 at 13:37 +0200, Siteshwar Vashisht wrote:
> On Tue, Jul 9, 2024 at 1:16 PM Daniel P. Berrangé
>
> wrote:
>
> > On Sat, Jul 06, 2024 at 02:05:37AM +0200, Siteshwar Vashisht wrote:
> > > Hello,
> > >
> > > I am writing this message to get feedback from the community on
> > > pos
On Tue, 2024-07-09 at 13:37 +0200, Siteshwar Vashisht wrote:
> On Tue, Jul 9, 2024 at 1:16 PM Daniel P. Berrangé
>
> wrote:
>
> > On Sat, Jul 06, 2024 at 02:05:37AM +0200, Siteshwar Vashisht wrote:
> > > Hello,
> > >
> > > I am writing this message to get feedback from the community on
> > > pos
On Tue, 9 Jul 2024 at 14:58, Kevin Fenzi wrote:
>
> Hey folks.
>
> I happened to notice the other day that f41 branching is currently
> scheduled for 2024-08-06. This is the day before flock.
>
> https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html
>
> I don't think this is a good tim
On Tue, Jul 9, 2024 at 2:58 PM Kevin Fenzi wrote:
>
> Hey folks.
>
> I happened to notice the other day that f41 branching is currently
> scheduled for 2024-08-06. This is the day before flock.
>
> https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html
>
> I don't think this is a good t
Text Log:
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-09/fesco.2024-07-09-17.00.log.txt
HTML Log:
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-09/fesco.2024-07-09-17.00.log.html
Text Minutes:
https://meetbot.fedoraproject.org/meeting_matr
Hey folks.
I happened to notice the other day that f41 branching is currently
scheduled for 2024-08-06. This is the day before flock.
https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html
I don't think this is a good time. :)
While Samyak (who will be doing most/all of the releng wo
Hello,
and thank you for the feed back, the thing is I am self-taught, that is
the very first time,
that I read that autotools are 'old stuff', so to speak ...
I figured to introduce something else was mandatory, so I picked CMake
and try to learn how
to use it (I prefer the autotools surprisi
Btw. Why not splitting anconda RPM in a main part which support only wayland
with a new sub package for X11?
Than you can reduce package size for workstation and desktops which are ready
for wayland.
In my opinion this is way to go to support X11 desktops until X11 itself is
obsolete.
Wolfgang
The "-C--enable-qcas" is rejected.
>>>
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py
-C--enable-qcas
/home/sagitter/rpmbuild/BUILD/giacpy-0.7.3/pyproject-wheeldir
Usage:
/usr/bin/python3 -m pip wheel [options] ...
/usr/bin/python3 -m pip wheel [options] -r ...
/usr/bin
I am owner of MATE desktop spin.
Will anconda run on a x11 desktop (liveCD) ?
Mate wayland support is highly experimental and far away from a production
state to use as desktop for fedora.
When anconda won't run on x11 it isn't possible to install MATE desktop from
the spin, in result this break
On Tue, Jul 9, 2024 at 11:29 AM David Bold wrote:
>
> Sandro wrote:
> > On 09-07-2024 17:01, David Bold wrote:
> > > Is it possible to have a PR without any code changes?
> > > Is there an alternative, recommended way to ask for rebuilds?
> > Specifically in the case of %autorelease, you can bump
On Mon, May 13, 2024 at 3:58 PM Benjamin Gilbert wrote:
> The affected image formats are ANI, BMP, ICNS, ICO,
> PNM, QTIF, TGA, XBM, and XPM.
>
> [...]
>
> gdk-pixbuf upstream is discussing splitting these loaders out into a
> separate project. Once the plan firms up, I'll package the new
> proje
On 09. 07. 24 17:01, David Bold wrote:
Gi,
I tried to open a PR to get petsc rebuild for a recent update of openmpi.
However, I cannot open a PR, which I think might be related that I only have an
empty commit [0].
I have been told I should open PRs for rebuilds [1].
Is it possible to have a P
On 09-07-2024 17:22, David Bold wrote:
Sandro wrote:
On 09-07-2024 17:01, David Bold wrote:
Is it possible to have a PR without any code changes?
Is there an alternative, recommended way to ask for rebuilds?
Specifically in the case of %autorelease, you can bump the release with
an empty commi
Sandro wrote:
> On 09-07-2024 17:01, David Bold wrote:
> > Is it possible to have a PR without any code changes?
> > Is there an alternative, recommended way to ask for rebuilds?
> Specifically in the case of %autorelease, you can bump the release with
> an empty commit:
> git commit --allow-empty
On 2024/07/09 17:09, Sandro via devel wrote:
On 09-07-2024 17:01, David Bold wrote:
Is it possible to have a PR without any code changes?
Is there an alternative, recommended way to ask for rebuilds?
Specifically in the case of %autorelease, you can bump the release
with an empty commit:
g
On 09-07-2024 17:01, David Bold wrote:
Is it possible to have a PR without any code changes?
Is there an alternative, recommended way to ask for rebuilds?
Specifically in the case of %autorelease, you can bump the release with
an empty commit:
git commit --allow-empty -m 'Rebuild for ...'
-
Gi,
I tried to open a PR to get petsc rebuild for a recent update of openmpi.
However, I cannot open a PR, which I think might be related that I only have an
empty commit [0].
I have been told I should open PRs for rebuilds [1].
Is it possible to have a PR without any code changes?
Is there an a
There have been a number of PRs[1] opened to workaround problems
with pkg-config not finding .pc files when dependencies have
been built in flatpak context.
Normally pkg-config would always find .pc files in any system
dirs. ie
/usr/local/lib64/pkgconfig
/usr/local/share/pkgconfig
/usr/lib6
Thanks for your hint
Regards
Martin
--
___
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/
Lis
On 09/07/2024 15:13, Martin Gansser wrote:
i want to build a %check section for qt5 and qt6 for qhotkey
Just use different directories for Qt 5 and Qt 6 builds.
You can use this SPEC as an example:
https://src.fedoraproject.org/rpms/qcoro/blob/rawhide/f/qcoro.spec
--
Sincerely,
Vitaly Zaits
On Tue, Jul 9, 2024 at 2:28 PM Richard W.M. Jones wrote:
> On Tue, Jul 09, 2024 at 01:37:20PM +0200, Siteshwar Vashisht wrote:
> > I request somebody from the tools team to comment on these concerns. We
> only
> > report the defects identified by gcc, clang etc.
>
> You wrote:
>
> > TLDR: This
Hi,
i want to build a %check section for qt5 and qt6 for qhotkey
[1] https://martinkg.fedorapeople.org/ErrorReports/qhotkey.spec
or can i simply use this line Version=5 for qt5 an VERSION=6 for qt6 ?
%cmake HotkeyTest -DQT_DEFAULT_MAJOR_VERSION=5 -DQHOTKEY_EXAMPLES=ON
%cmake HotkeyTest -DQT_DEF
On Tue, Jul 09, 2024 at 01:37:20PM +0200, Siteshwar Vashisht wrote:
> I request somebody from the tools team to comment on these concerns. We only
> report the defects identified by gcc, clang etc.
You wrote:
> TLDR: This report[2] contains 73976 identified defects.
and again above said they w
Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 41 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 3 weeks, i.e. around 2024-07-30.
Policy:
On Tue, Jul 9, 2024 at 11:15 AM Michal Konecny wrote:
> Should speakers get the ticket as well?
>
>
Yes please, speakers should get their tickets from eventbrite too.
--
Aoife Moloney
Fedora Operations Architect
Fedora Project
Matrix: @amoloney:fedora.im
IRC: amoloney
--
_
> Is the registration link only for in person attendance?
>
Yes, this is for in-person attendees right now.
>
> As the talks will be streamed live, will there be some way for people
> watching the streams to ask questions, for example through chat? If so,
> will registration be needed for this?
>
On Tue, Jul 9, 2024 at 1:16 PM Daniel P. Berrangé
wrote:
> On Sat, Jul 06, 2024 at 02:05:37AM +0200, Siteshwar Vashisht wrote:
> > Hello,
> >
> > I am writing this message to get feedback from the community on possibly
> > new defects identified by static analyzers in Critical Path Packages that
On Sat, Jul 06, 2024 at 02:05:37AM +0200, Siteshwar Vashisht wrote:
> Hello,
>
> I am writing this message to get feedback from the community on possibly
> new defects identified by static analyzers in Critical Path Packages that
> have changed in Fedora 41. For context, please see my previous ema
Otto Liljalaakso kirjoitti 28.5.2024 klo 22.28:
Hello,
Pull requests are an important aspect of how Fedora packaging works,
and, crucially, the easiest way for new contributors to get started.
Unfortunately, there has been almost no documentation available about
that topic. To remedy that si
hi , i used to contribute to winget-pkgs back when i was using windows and
various other open source initiatives. need someone to aprove
https://bugzilla.redhat.com/show_bug.cgi?id=2296293
--
___
devel mailing list -- devel@lists.fedoraproject.org
To u
On Sat, Jul 6, 2024 at 2:05 AM Siteshwar Vashisht
wrote:
> Hello,
>
> I am writing this message to get feedback from the community on possibly
> new defects identified by static analyzers in Critical Path Packages that
> have changed in Fedora 41. For context, please see my previous email[1].
>
Should speakers get the ticket as well?
Michal
On 08. 07. 24 19:12, Aoife Moloney wrote:
Hi folks,
On behalf of the Flock to Fedora organiser team, we would like to
share that the Flock to Fedora 2024 schedule is now live [1] and so is
our registration [2]. Please note that some talks may c
OLD: Fedora-Rawhide-20240707.n.1
NEW: Fedora-Rawhide-20240709.n.0
= SUMMARY =
Added images:0
Dropped images: 2
Added packages: 8
Dropped packages:0
Upgraded packages: 181
Downgraded packages: 0
Size of added packages: 7.88 MiB
Size of dropped packages:0 B
On Sun, Jul 07, 2024 at 12:09:21PM +0200, Sébastien Le Roux wrote:
> https://github.com/Slookeur/OPEN
Hi Sébastien,
This is a very impressive introduction to Autotools and Cmake (and other
things).
In teaching there's the technique of listing things that the reader
will "know" and be able to do
42 matches
Mail list logo
