Re: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Smith, Stewart via devel
On Jun 29, 2023, at 7:47 AM, Bastien Nocera  wrote:
> Here is a list of Fedora packages which I maintained or co-maintained which I 
> won't be able to contribute to anymore:
> 
> sloccount

I grabbed sloccount as I’ve found it useful over the years.

It looks the right level of incredibly low maintenance to add to the pile.

___
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: LXQt Spin: packages not updated since April 2022

2023-07-01 Thread Christopher Klooz via devel

Thanks for the quick reply ;)

I was only testing it in a VM as potential solution for a temporary 
weak-hardware use case - and I tend to prefer Qt-based solutions over GTK.


I have already the confined-user/SELinux issue and a project from Fedora 
Docs on my schedule, which are both waiting to start. I cannot put much 
more on my schedule at the moment ;)


However, if the SIG and the related maintainers cannot handle the LXQt 
packages at the moment either, it might be worth to discuss removing it 
from the promoted Spins list for now, doesn't it? Finally, the issue 
here is not just some average application but the desktop environment.


Maybe I am a little too conservative in this respect, but imho once we 
promote and provide it as a Spin, that goes along with some 
responsibility. Users may start to rely on it and use it for 
critical/private data and processes.


On 7/1/23 16:01, Neal Gompa wrote:

On Sat, Jul 1, 2023 at 8:38 AM Christopher Klooz via devel
 wrote:

Hi,

I was testing an instance of the LXQt Spin in a VM and saw that after
updating all packages, the LXQt packages are still with version 1.1.0,
which is from April 2022. Current is 1.3.0.

I read the LXQt team does not maintain itself, and 1.2.0 and 1.3.0 seem
to not contain critical security issues or so, but does someone keep
checking if something urgent comes up that requires action? (security or
compatibility issues, broken processes/automation at maintainers, ...)


Help is always desired and wanted. :)

Certainly if you're interested in LXQt and keeping it up to date,
helping out on that front would be greatly appreciated.




___
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: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

2023-07-01 Thread Sandro

On 01-07-2023 22:05, Michael J Gruber wrote:

I may have a patch for rst2pdf - how do I chain-scratch build against 
f39-python? I probably don't, so how do I mock build with f39-build chroot?



fedpkg mock-config --target f39-python > ~/.config/mock/f39-python.cfg
fedpkg srpm
mock -r f39-python --rebuild $SRPM

That's what I've been doing and what others recommended on IRC.

-- Sandro
___
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: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Kalev Lember

On 6/29/23 16:47, Bastien Nocera wrote:

Hello,

As part of the same process outlined in Matthias Clasen's "LibreOffice 
packages" email, my upstream and downstream work on desktop Bluetooth, multimedia 
applications (namely totem, rhythmbox and sound-juicer) and libfprint/fprintd is being 
stopped, and all the rest of my upstream and downstream work will be reassigned depending 
on Red Hat's own priorities, as I am transferred to another team.

While it's possible that some of the maintenance will stay with me in the new 
team, I've not yet been told which team I would be joining.

Here is a list of Fedora packages which I maintained or co-maintained which I 
won't be able to contribute to anymore:
apfs-fuse
bluez
codespell
eosrei-emojione-fonts
geocode-glib
gnome-bluetooth
gnome-epub-thumbnailer
gnome-kra-ora-thumbnailer
gnome-user-share
gom
grilo
grilo-plugins
ifuse
iio-sensor-proxy
libfprint
libglib-testing
libimobiledevice
libpeas
libplist
libportal
libusbmuxd
low-memory-monitor
malcontent
power-profiles-daemon
sloccount
switcheroo-control
totem
totem-pl-parser
umockdev
usbmuxd


I went ahead and picked up some of the GNOME packages from the list:

gnome-bluetooth
gnome-user-share
gom
libglib-testing
libpeas
libportal
totem
totem-pl-parser

Victor (CC'd), do you want to pick up grilo and grilo-plugins?

--
Kalev
___
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: Red Hat & Fedora -- largely stepping out of this ecosystem

2023-07-01 Thread Carlos Rodriguez-Fernandez



On 7/1/23 12:33, Piotr Szubiakowski wrote:


I think we all have a problem understanding what this announcement
means. I do believe CentOS Stream is awesome software. It has to be
since it's close to what RHEL is. My problem with CentOS Stream is that
it's not a distribution of my choice, and I feel forced to use CentOS
Stream. While at the same time, distributions of my choice Fedora,
Scientific Linux, CentOS Linux, Rocky Linux, and AlmaLinux, are
consequently taken down, to a moment that I'm not sure whenever RHEL is
still an open-source software.


It is still as opensource as it is Ubuntu and SUSE. There are no clones 
of Ubuntu LTS with 10 years lifecycle, nor of SUSE Enterprise with their 
10+ lifecyle.




Most likely, I'm too paranoid, but I'm
afraid that if Red Hat successfully kills RHEL downstream projects, bad
things will start to happen to CentOS Stream as well.


I'm afraid that could be the case too. This move will cool down the EL 
community significantly. I'm concerned of the future of EPEL itself. I 
wish RedHat would reduce their prices significantly for wider adoption, 
or just give the first 5 years for free as Ubuntu does.


Regards,
Carlos.


OpenPGP_0x47EBED05C3375B1F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature
___
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: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

2023-07-01 Thread Michael J Gruber
Some packages may build with py 3.12 but not work with it if they don't have 
tests. For example, python-PyMuPDF fails when it tries to builds its 
documentation, but the error is in rst2pdf. If I disable doc creation then 
python-PyMuPDF builds against py 3.12 (and the tests succeed).

I may have a patch for rst2pdf - how do I chain-scratch build against 
f39-python? I probably don't, so how do I mock build with f39-build chroot?

python-PyMuPDF FTBFS because of rst2pdf: 
https://koji.fedoraproject.org/koji/buildinfo?buildID=2224200

python-PyMuPDF builds without doc: 
https://koji.fedoraproject.org/koji/taskinfo?taskID=102814124

Possible rst2pdf upstream fix: 
https://github.com/rst2pdf/rst2pdf/pull/1171#pullrequestreview-1508457716
(rst2pdf package lags behind upstream releases; upstream patch applies to 0.99 
but not 0.97 where configparser is spelled ConfigParser)
___
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: Red Hat & Fedora -- largely stepping out of this ecosystem

2023-07-01 Thread Piotr Szubiakowski
On Fri, 2023-06-30 at 15:05 +0100, Sérgio Basto wrote:

> First I think this a storm in a teacup .

I tend to agree. In the worst-case scenario, people like me who try to
use open-source solely and don't pay for open-source will find a
distribution that fits them best. And from Red Hat's perspective, we
don't bring much value anyway.

> Second Centos Stream is the RHEL without branding, people in general 
> didn't like the idea of Centos be updated before RHEL , when Centos
> was
> updated after RHEL , but that was the main change. 
> After whats happened was that not all was updated first in Centos
> Stream like kernel (we saw updates with ABI breakage first on RHEL
> ...
> ). This announce is mainly , as I read, saying that exceptions will
> be
> over and all will be first on Centos Stream and than in RHEL

I think we all have a problem understanding what this announcement
means. I do believe CentOS Stream is awesome software. It has to be
since it's close to what RHEL is. My problem with CentOS Stream is that
it's not a distribution of my choice, and I feel forced to use CentOS
Stream. While at the same time, distributions of my choice Fedora,
Scientific Linux, CentOS Linux, Rocky Linux, and AlmaLinux, are
consequently taken down, to a moment that I'm not sure whenever RHEL is
still an open-source software.

Most likely, I'm too paranoid, but I'm
afraid that if Red Hat successfully kills RHEL downstream projects, bad
things will start to happen to CentOS Stream as well.

Cheers,

Piotr 
___
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


Fedora rawhide compose report: 20230701.n.0 changes

2023-07-01 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20230630.n.0
NEW: Fedora-Rawhide-20230701.n.0

= SUMMARY =
Added images:2
Dropped images:  4
Added packages:  5
Dropped packages:0
Upgraded packages:   69
Downgraded packages: 0

Size of added packages:  3.27 MiB
Size of dropped packages:0 B
Size of upgraded packages:   2.53 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   36.33 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: LXQt live x86_64
Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-Rawhide-20230701.n.0.iso
Image: LXQt raw-xz aarch64
Path: Spins/aarch64/images/Fedora-LXQt-Rawhide-20230701.n.0.aarch64.raw.xz

= DROPPED IMAGES =
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20230630.n.0.iso
Image: Sway live x86_64
Path: Spins/x86_64/iso/Fedora-Sway-Live-x86_64-Rawhide-20230630.n.0.iso
Image: Cinnamon live x86_64
Path: Spins/x86_64/iso/Fedora-Cinnamon-Live-x86_64-Rawhide-20230630.n.0.iso
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230630.n.0.iso

= ADDED PACKAGES =
Package: golang-aead-minisign-0.2.0-1.fc39
Summary: A dead simple tool to sign files and verify digital signatures
RPMs:golang-aead-minisign golang-aead-minisign-devel
Size:2.70 MiB

Package: golang-github-bmkessler-fastdiv-0-0.1.20230620git41d5178.fc39
Summary: Fast division, modulus and divisibility checks in Go
RPMs:golang-github-bmkessler-fastdiv-devel
Size:16.12 KiB

Package: golang-github-jtolio-eventkit-0-0.1.20230620gita7bf797.fc39
Summary: A go library for reporting multidimensional events over UDP
RPMs:golang-github-jtolio-eventkit-devel
Size:20.20 KiB

Package: golang-github-maxatome-testdeep-1.13.0-2.fc39
Summary: Tests HTTP APIs and provides tests suite
RPMs:golang-github-maxatome-testdeep-devel
Size:300.10 KiB

Package: python-pdf2image-1.16.3-1.fc39
Summary: Convert PDF to PIL Image object
RPMs:python-pdf2image-doc python3-pdf2image
Size:247.36 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  aardvark-dns-1.7.0-1.fc39
Old package:  aardvark-dns-1.6.0-1.fc39
Summary:  Authoritative DNS server for A/ container records
RPMs: aardvark-dns
Size: 3.78 MiB
Size change:  -3.95 KiB
Changelog:
  * Thu Jun 29 2023 Packit  - 1.7.0-1
  - [packit] 1.7.0 upstream release


Package:  abrt-2.17.1-1.fc39
Old package:  abrt-2.17.0-1.fc39
Summary:  Automatic bug detection and reporting tool
RPMs: abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-pstoreoops 
abrt-addon-upload-watch abrt-addon-vmcore abrt-addon-xorg abrt-atomic abrt-cli 
abrt-console-notification abrt-dbus abrt-desktop abrt-devel abrt-gui 
abrt-gui-devel abrt-gui-libs abrt-libs abrt-plugin-bodhi abrt-plugin-machine-id 
abrt-tui python3-abrt python3-abrt-addon python3-abrt-container-addon 
python3-abrt-doc
Size: 4.99 MiB
Size change:  -20.81 KiB
Changelog:
  * Wed Jun 28 2023 Python Maint  - 2.17.0-2
  - Rebuilt for Python 3.12

  * Fri Jun 30 2023 Michal Srb  - 2.17.1-1
  - Update to upstream release 2.17.1


Package:  annobin-12.17-1.fc39
Old package:  annobin-12.12-1.fc39
Summary:  Annotate and examine compiled binary files
RPMs: annobin-annocheck annobin-docs annobin-libannocheck 
annobin-plugin-clang annobin-plugin-gcc annobin-plugin-llvm
Size: 5.03 MiB
Size change:  4.58 KiB
Changelog:
  * Tue Jun 20 2023 Nick Clifton   - 12.13-1
  - Annocheck: Ignore /dev/null filename in string notes.
  - Annocheck: More tweaks to glibc detection heuristics.  (#2215968)

  * Thu Jun 22 2023 Nick Clifton   - 12.14-1
  - Annocheck: Do not ignore separate debuginfo files that do not contain any 
DWARF.  (#2144553)

  * Mon Jun 26 2023 Nick Clifton   - 12.15-1
  - Annocheck: Add --suppress-version-warnings option.

  * Tue Jun 27 2023 Nick Clifton   - 12.16-1
  - Annocheck: Ignore weak/undef function symbols when checking to see if a 
binary contains code.  (#2217840)

  * Thu Jun 29 2023 Nick Clifton   - 12.17-1
  - Annocheck: Add detection of known parts of libstdc++-nonshared.a that 
contain gaps.  (#2217864)


Package:  aspell-fi-0.7-21.fc39
Old package:  aspell-fi-0.7-20.fc38
Summary:  Finnish dictionaries for Aspell
RPMs: aspell-fi
Size: 2.58 MiB
Size change:  -534 B
Changelog:
  * Fri Jun 30 2023 Johan Swensson  - 0.7-21
  - Deprecate package BZ#2218548


Package:  aspell-la-20020503-20.fc39
Old package:  aspell-la-20020503-19.fc38
Summary:  Latin dictionaries for Aspell
RPMs: aspell-la
Size: 593.51 KiB
Size change:  -825 B
Changelog:
  * Fri Jun 30 2023 Johan Swensson  - 20020503-20
  - Deprecate package BZ#2218561


Package:  aspell-ml-0.03-27.fc39
Old package:  aspell-ml-0.03-27.fc38
Summary:  GNU Aspell Malayalam Dictionary Package
RPMs: aspell-ml
Size: 4.64 MiB
Size change:  -173 B

Package

[Test-Announce] Fedora 39 Rawhide 20230701.n.0 nightly compose nominated for testing

2023-07-01 Thread rawhide
Announcing the creation of a new nightly release validation test event
for Fedora 39 Rawhide 20230701.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
python-blivet - 20230628.n.2: python-blivet-3.7.1-4.fc39.src, 20230701.n.0: 
python-blivet-3.8.0-1.fc39.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/39

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230701.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230701.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230701.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230701.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230701.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230701.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_39_Rawhide_20230701.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@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


[Bug 2219054] perltidy-20230701 is available

2023-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-ab380a326d has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-ab380a326d


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219054%23c3
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[Bug 2219054] perltidy-20230701 is available

2023-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perltidy-20230701-1.fc39
 Status|MODIFIED|CLOSED
Last Closed||2023-07-01 15:03:07



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-ab380a326d has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219054%23c4
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Leon Fauster via devel

Am 01.07.23 um 14:28 schrieb Peter Robinson:

On Sat, Jul 1, 2023 at 12:50 PM Vitaly Zaitsev via devel
 wrote:


On 01/07/2023 13:36, Chris Adams wrote:

A lot of the corporate world has gone to the "cloud"



don't have to worry about local backups of important documents and
spreadsheets, they get sharing with minimal effort, they can access
things from their mobile devices, etc.


And voluntarily hand over all the corporate secrets to Google and
Microsoft. Brilliant idea.


This sort of comment is off topic, various companies are free to do
with their data as they wish, just as you are free to do with it as
you please. Frankly it's often more secure with cloud providers than
on corporate networks. Either way that comment doesn't provide useful
discourse in this discussion.



No really, it defines requirements that a non-cloud solution addresses.
Just to rephrase it; "it's often more secure (confidential) on corporate 
networks than with cloud providers". So a legitimately contribution to

the discourse in having a functional desktop (office) environment.
Whether its being flatpaked, rpmish, immutable packaged or what ever the
future brings ...

--
Leon

___
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


[Bug 2219054] perltidy-20230701 is available

2023-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2219054



--- Comment #1 from Upstream Release Monitoring 
 ---
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs',
'/var/tmp/thn-29_w150n/perltidy.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1688169600
error: Bad file: ./Perl-Tidy-20230701.tar.gz: No such file or directory

RPM build errors:
Bad file: ./Perl-Tidy-20230701.tar.gz: No such file or directory


Traceback:
  File
"/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py",
line 56, in build
result = self.builder.build(request.package, request.opts)
 ^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line
229, in build
raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report
it on the-new-hotness issue tracker:
https://github.com/fedora-infra/the-new-hotness/issues


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219054%23c1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[Bug 2219054] perltidy-20230701 is available

2023-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2219054



--- Comment #2 from Upstream Release Monitoring 
 ---
Created attachment 1973610
  --> https://bugzilla.redhat.com/attachment.cgi?id=1973610=edit
Update to 20230701 (#2219054)


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219054%23c2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


[Bug 2219054] New: perltidy-20230701 is available

2023-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Bug ID: 2219054
   Summary: perltidy-20230701 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perltidy
  Keywords: FutureFeature, Triaged
  Assignee: p...@city-fan.org
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: lxt...@gmail.com, p...@city-fan.org,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 20230701
Upstream release that is considered latest: 20230701
Current version/release in rawhide: 20230309-1.fc39
URL: http://search.cpan.org/dist/Perl-Tidy/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3553/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perltidy


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2219054

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219054%23c0
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: LXQt Spin: packages not updated since April 2022

2023-07-01 Thread Neal Gompa
On Sat, Jul 1, 2023 at 8:38 AM Christopher Klooz via devel
 wrote:
>
> Hi,
>
> I was testing an instance of the LXQt Spin in a VM and saw that after
> updating all packages, the LXQt packages are still with version 1.1.0,
> which is from April 2022. Current is 1.3.0.
>
> I read the LXQt team does not maintain itself, and 1.2.0 and 1.3.0 seem
> to not contain critical security issues or so, but does someone keep
> checking if something urgent comes up that requires action? (security or
> compatibility issues, broken processes/automation at maintainers, ...)
>

Help is always desired and wanted. :)

Certainly if you're interested in LXQt and keeping it up to date,
helping out on that front would be greatly appreciated.



-- 
真実はいつも一つ!/ 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


LXQt Spin: packages not updated since April 2022

2023-07-01 Thread Christopher Klooz via devel

Hi,

I was testing an instance of the LXQt Spin in a VM and saw that after 
updating all packages, the LXQt packages are still with version 1.1.0, 
which is from April 2022. Current is 1.3.0.


I read the LXQt team does not maintain itself, and 1.2.0 and 1.3.0 seem 
to not contain critical security issues or so, but does someone keep 
checking if something urgent comes up that requires action? (security or 
compatibility issues, broken processes/automation at maintainers, ...)


Regards,
Chris
___
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: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Peter Robinson
On Sat, Jul 1, 2023 at 12:50 PM Vitaly Zaitsev via devel
 wrote:
>
> On 01/07/2023 13:36, Chris Adams wrote:
> > A lot of the corporate world has gone to the "cloud"
>
> > don't have to worry about local backups of important documents and
> > spreadsheets, they get sharing with minimal effort, they can access
> > things from their mobile devices, etc.
>
> And voluntarily hand over all the corporate secrets to Google and
> Microsoft. Brilliant idea.

This sort of comment is off topic, various companies are free to do
with their data as they wish, just as you are free to do with it as
you please. Frankly it's often more secure with cloud providers than
on corporate networks. Either way that comment doesn't provide useful
discourse in this discussion.
___
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: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Vitaly Zaitsev via devel

On 01/07/2023 13:36, Chris Adams wrote:

A lot of the corporate world has gone to the "cloud"



don't have to worry about local backups of important documents and
spreadsheets, they get sharing with minimal effort, they can access
things from their mobile devices, etc.


And voluntarily hand over all the corporate secrets to Google and 
Microsoft. Brilliant idea.


--
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
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: [HEADS UP] Fedora 39 Python 3.12 rebuilds to start in a side tag this week

2023-07-01 Thread Frantisek Zatloukal
On Tue, Jun 27, 2023 at 8:44 PM Tomáš Hrnčiar  wrote:

> python-redis cicku kevin maxamillion
>

I've filled https://src.fedoraproject.org/rpms/python-redis/pull-request/13
, that should get python-redis going and unstuck a bunch of packages
depending on it.

Just a note, the failure wasn't caused by Python 3.12, but redis 7.2 rebase
in rawhide.

-- 

Best regards / S pozdravem,

František Zatloukal
Senior Quality Engineer
Red Hat
___
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: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Chris Adams
Once upon a time, Kevin Kofler  said:
> Peter Robinson wrote:
> > I would hardly say Libreoffice, bluetooth on the desktop and certain
> > iDevice pieces is "killing all work on the desktop" it's more focusing
> > on things that are important to their customers in those contexts.
> 
> What corporate desktop customers do not use LibreOffice? If RH considers 
> LibreOffice unimportant to their customers, it is obvious that they only 
> care about server customers.

A lot of the corporate world has gone to the "cloud" (Google Docs or
O365) for their office needs, enough that even where Windows is the
predominant desktop OS, they don't get MS Office licenses either.  They
don't have to worry about local backups of important documents and
spreadsheets, they get sharing with minimal effort, they can access
things from their mobile devices, etc.

-- 
Chris Adams 
___
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: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Peter Robinson
On Sat, Jul 1, 2023 at 12:30 PM Peter Robinson  wrote:
>
> On Sat, Jul 1, 2023 at 12:00 AM Kevin Kofler via devel
>  wrote:
> >
> > Peter Robinson wrote:
> > > I would hardly say Libreoffice, bluetooth on the desktop and certain
> > > iDevice pieces is "killing all work on the desktop" it's more focusing
> > > on things that are important to their customers in those contexts.
> >
> > What corporate desktop customers do not use LibreOffice? If RH considers
> > LibreOffice unimportant to their customers, it is obvious that they only
> > care about server customers.
>
> Well if the customer gets it via Flatpak they still have it, it also
> means it doesn't need to be upgraded in lockstep with the OS so they
> can go to newer versions while keeping the same rev of the desktop or
> vica versa.
>
> But then there's also "desktop usecases like retail point of sale and
> a whole lot of other single use UX graphical like display boards,
> ticket machines, places where they're technical workstations and the
> user has a separate windows device for email/office etc. There's a
> vast array.

Also a lot use online docs like Office365 or Google docs. I personally
used to use Libreoffice a lot but now I mostly use gDocs.
___
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: Orphaning packages (was LibreOffice packages)

2023-07-01 Thread Peter Robinson
On Sat, Jul 1, 2023 at 12:00 AM Kevin Kofler via devel
 wrote:
>
> Peter Robinson wrote:
> > I would hardly say Libreoffice, bluetooth on the desktop and certain
> > iDevice pieces is "killing all work on the desktop" it's more focusing
> > on things that are important to their customers in those contexts.
>
> What corporate desktop customers do not use LibreOffice? If RH considers
> LibreOffice unimportant to their customers, it is obvious that they only
> care about server customers.

Well if the customer gets it via Flatpak they still have it, it also
means it doesn't need to be upgraded in lockstep with the OS so they
can go to newer versions while keeping the same rev of the desktop or
vica versa.

But then there's also "desktop usecases like retail point of sale and
a whole lot of other single use UX graphical like display boards,
ticket machines, places where they're technical workstations and the
user has a separate windows device for email/office etc. There's a
vast array.
___
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: more distinct default bash prompt?

2023-07-01 Thread Björn Persson
Jens-Ulrik Petersen wrote:
> it now defaults to normal green and adds the
> red error code from Stephan (maybe this part could still be improved?)

I like the red error code enough that I'm trying it out on my own
workstation. Yet I doubt it's suitable for the default prompt. I'll
remember what it means because I've configured it myself. To a beginner
who hasn't configured their prompt, the intermittent appearance of a
red number will be very cryptic.

If the error code is included, then appending it to the working 
directory isn't the best choice. It looks like a part of the directory
name, especially to red/green blind users I expect. There should be a
space or other separator, but even then it could be ambiguous as
filenames can contain almost any characters. Writing the error code
before the username is less confusing. Users are unlikely to think that
the digits are part of their username.

This code expands to nothing if the exit code is zero, and to the exit
code followed by a space otherwise:

prompt_result_separator=' '
PS1='\[\e[0;31m\]${?#0}\[\e[0m\]${prompt_result_separator[!$?]}...'

Note also the "0;" in the beginning. I think all prompts should begin
with that to clear any attributes that may have been left behind by a
broken program. (Try "echo -e '\e[8m'" and see if it hides your prompt.)

Björn Persson


pgp_JLupc3tON.pgp
Description: OpenPGP digital signatur
___
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


[Bug 2219043] New: perl-Term-ReadLine-Gnu-1.46 is available

2023-07-01 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=2219043

Bug ID: 2219043
   Summary: perl-Term-ReadLine-Gnu-1.46 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Term-ReadLine-Gnu
  Keywords: FutureFeature, Triaged
  Assignee: emman...@seyman.fr
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: c...@fea.st, emman...@seyman.fr, lkund...@v3.sk,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.46
Upstream release that is considered latest: 1.46
Current version/release in rawhide: 1.45-2.fc38
URL: https://metacpan.org/dist/Term-ReadLine-Gnu/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/7548/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Term-ReadLine-Gnu


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2219043

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202219043%23c0
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue