Something wrong with kernel-headers on fedora 30?

[Joseph D. Wagner]

I am on kernel 5.3.8 but I still have 
kernel-headers-5.3.6-200.fc30.x86_64, which hasn't updated.


Is there a reason a new kernel-headers package hasn't been generated for 
the newer versions?  Has it be superseded by another package? If so, 
then dependencies on glibc-headers need to be fixed.


Joseph D. Wagner
___
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 32 System-Wide Change proposal: x86-64 micro-architecture update

[Joseph D. Wagner]

On 2019-07-22 13:12, Felix Kaechele via devel wrote:


On 2019-07-22 2:51 p.m., Ben Cotton wrote:


After preliminary discussions with CPU vendors, we propose AVX2 as the
new baseline.  AVX2 support was introduced into CPUs from 2013 to
2015. See 
[https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX2

CPUs with AVX2].


Here's a JSON file of all Intel CPUs that do not have any AVX extension 
support that were released after January 1, 2013:

https://odata.intel.com/API/v1_0/Products/Processors()?&$filter=not%20substringof(%27AVX%27,InstructionSetExtensions)%20and%20LaunchDate%20gt%20DateTime%272013-01-01T00:00:00.00Z%27&$format=json

There are Pentium and Celeron CPUs being released today that don't even 
support AVX.


I may have to turn in my nerd card for not being able to pull this 
myself, but what would this list look like if the baseline was SSSE3?  
Just curious.


Joseph D. Wagner
___
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

Bug 1742953 - No Screensaver/Powerdown after Inactivity at LUKS Password Prompt [FutureFeature]

[Joseph D. Wagner]

Sorry if this is the wrong place to post. I need to start somewhere.

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

Description of problem:
The Plymouth LUKS password prompt will wait FOREVER for me to type in a
password without powering down the monitor or blanking the screen. This
leaves me vulnerable to screen burn-in if 1) there was an unexpected
reboot like a crash, or 2) another OS (which shall remain nameless)
rebooted after update, but the dual-boot started in Linux instead of
the other OS.

How reproducible:
100%

Steps to Reproduce:
1. Wait at LUKS prompt until you need to throw away your monitor.

Actual results:
A bill for an expensive new monitor.

Expected results:
The monitor goes into powersaver mode after a reasonable time, like 20
minutes, or at least blanks.
___
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: Bug 1742953 - No Screensaver/Powerdown after Inactivity at LUKS Password Prompt [FutureFeature]

[Joseph D. Wagner]

On 2019-08-18 02:57, Vitaly Zaitsev via devel wrote:


On 18.08.2019 2:24, Joseph D. Wagner wrote:

The Plymouth LUKS password prompt will wait FOREVER for me to type in 
a

password


This is intended, because system is not even started yet on
LUKS-encrypted media attach stage.


It is intended to display the same image on the screen continuously 
until I suffer from screen burn-in?



If you don't want to enter LUKS password on every boot, you should use
TPM or hardware tokens.


My issue is not with waiting forever on the password prompt. My issue is 
with displaying the same password prompt forever, causing screen 
burn-in.  There are unexpected reboots, like crashes and dual-boot 
systems where a non-default OS decides to automatically reboot for 
updates, only for the reboot to go into the default with LUKS.


Joseph D. Wagner
___
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

python-xpyb

[Joseph D. Wagner]

There appears to be a python2 version of this package, but not a python3 
version.


Should there be?

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Moving kdump location - what needs to change

[Joseph D. Wagner]

I changed kdump.conf from /var/crash to /boot/crash, because I have an 
encrypted root fs.


I was looking for other places it might need to be changed, and I came 
across this line


File /usr/lib/systemd/system/abrt-vmcore.service

ConditionDirectoryNotEmpty=/var/crash

Should this be changed to /boot/crash as well?  Or are there other 
processes to take care of this?


Thanks.

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Kernel 4.20 rebase plans

[Joseph D. Wagner]

IIRC, there is major performance degradation (anti-Spectre) in 4.20 that
will be turned off by default 4.21. 

Will it be turned off by default in the 4.20 rebase? 

Joseph D. Wagner 

On 2019-01-08 14:31, Justin Forbes wrote:

> The 4.20 kernel was released just before the end of the year, but the
> first stable update should be dropping in the next day or two.  We
> have a 4.20 test day scheduled for Tuesday, January 15th.  Depending
> on the results of that test day, Fedora 29 will be rebased very
> shortly afterwards, followed by F28 approximately a week later.  Of
> course the results of the test day could end up changing this, but it
> is the current plan.
> 
> Thanks,
> Justin
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> 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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

RE: System freezes randomly - need to reboot

[Joseph D. Wagner]

Do you have a nvidia card?

 

Joseph D. Wagner

 

From: arnaud gaboury  
Sent: Monday, January 14, 2019 4:31 AM
To: Development discussions related to Fedora 
Subject: System freezes randomly - need to reboot

 

Hello everyone,

 

##

$ cat /etc/os-release

NAME=Fedora
VERSION="29.20181230.0 (Workstation Edition)"
ID=fedora
VERSION_ID=29
VERSION_CODENAME=""
PLATFORM_ID="platform:f29"
PRETTY_NAME="Fedora 29.20181230.0 (Workstation Edition)"

VARIANT="Workstation Edition"
VARIANT_ID=workstation
OSTREE_VERSION=29.20181230.0
###

 

Wayland with Gnome session

 

My system freezes randomly and I need to reboot. I can't spot any specific 
action or app that could trigger the freeze, as it happens with  my regular app 
open: Gnome terminal, Firefox, Telegram desktop. When running the following 
command,I get some hints:

 

###

$ journalctl --system

.

Jan 14 09:04:51 yogabx audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 
ses=4294967295 msg='unit=systemd-coredump@3-3825-0 comm="systemd" 
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succes>
Jan 14 09:04:51 yogabx systemd-coredump[3826]: Process 3819 (fwupd) of user 0 
dumped core.
   
   Stack trace of thread 3819:
   #0  0x7f549d033f42 
__strcmp_avx2 (libc.so.6)
   #1  0x7f549d3f43e5 n/a 
(libgio-2.0.so.0)
   #2  0x7f549d3f547f 
g_unix_is_mount_path_system_internal (libgio-2.0.so.0)
   #3  0x7f549d3f56e8 n/a 
(libgio-2.0.so.0)
   #4  0x7f549d3f5b07 
g_unix_mount_at (libgio-2.0.so.0)
   #5  0x7f548c9272f7 
fu_plugin_coldplug (libfu_plugin_uefi.so)
   #6  0x557cbc21f550 
fu_plugin_runner_coldplug (fwupd)
   #7  0x557cbc206a98 n/a 
(fwupd)
   #8  0x557cbc20f7fa 
fu_engine_load (fwupd)
   #9  0x557cbc1ff55a main 
(fwupd)
   #10 0x7f549cefb413 
__libc_start_main (libc.so.6)
   #11 0x557cbc1ff86e _start 
(fwupd)
   
   Stack trace of thread 3821:
   #0  0x7f549cfc9421 __poll 
(libc.so.6)
   #1  0x7f549c820d5f n/a 
(libusb-1.0.so.0)
   #2  0x7f549d0a558e 
start_thread (libpthread.so.0)
   #3  0x7f549cfd46a3 __clone 
(libc.so.6)
   
   Stack trace of thread 3823:
   #0  0x7f549cfc9421 __poll 
(libc.so.6)
   #1  0x7f549d5033a6 n/a 
(libglib-2.0.so.0)
   #2  0x7f549d503762 
g_main_loop_run (libglib-2.0.so.0)
   #3  0x7f549d3ca10a n/a 
(libgio-2.0.so.0)
   #4  0x7f549d52c2aa n/a 
(libglib-2.0.so.0)
   #5  0x7f549d0a558e 
start_thread (libpthread.so.0)
   #6  0x7f549cfd46a3 __clone 
(libc.so.6)
   
   Stack trace of thread 3820:
   #0  0x7f549cfc9421 __poll 
(libc.so.6)
   #1  0x7f549d5033a6 n/a 
(libglib-2.0.so.0)
   #2  0x7f549d5034d0 
g_main_context_iteration (libglib-2.0.so.0)
   #3  0x7f549d503521 n/a 
(libglib-2.0.so.0)
   #4  0x7f549d52c2aa n/a 
(libglib-2.0.so.0)
   #5  0x7f549d0a558e 
start_thread (libpthread.so.0)
   #6  0x7f549cfd46a3 __clone 
(libc.so.6)
   
   Stack trace of thread 3822:
   #0  0x7f549cfc9421 __poll 
(libc.so.6)
   #1  0x7f

pgadmin3 & pgadmin4 - No/Non-Responding Maintainer

[Joseph D. Wagner]

Fedora is now on postgresql 10.x.
pgadmin3 stopped being supported with postgresql 9.5.
pgadmin4 isn't packaged in the repositories.

Hence, Fedora no longer has a gui for postgresql.

Is the maintainer here that we could get help with this?  If not, is 
there anyone willing to rise to the challenge?


Status: Itamar Reis Peixoto helped update all the prerequisite packages 
(thanks), but there is still no pgadmin4 package in the repositories.


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

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/5VMWKIXDFIHZLNWXTOTA54DB4XBR52IS/

FESCo Request to Retire pgadmin3

[Joseph D. Wagner]

I am requesting the retirement of pgadmin3.  It is no longer supported
upstream, and it does not work with the version of PostgreSQL that Fedora is
shipping.

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PH6CQ5ZAD6XNK2WD7WOAP46RJJHRFLFZ/

Seeking New Maintainer for python-html5lib

[Joseph D. Wagner]

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

Current maintainer said:
Praveen Kumar  --- Apologies, I caught
up with some other work and not able to maintain this package, I am happy to
give the ownership if someone willing to maintain it.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/IDGXPLBU4RES34AG4XX4MON32IAXOPDK/

Non-responsive maintainer for python-simplejson

[Joseph D. Wagner]

It hasn't been updated in over a year, and it's updates are sorely needed.

Trying to get updated before the beta freeze.

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

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CWHI6WPU5B733ISMAPQEXHRKINZYPZWQ/

Non-responsive maintainer for python-pytz

[Joseph D. Wagner]

It hasn't been updated in almost a year, and it's updates are sorely 
needed.


Trying to get updated before the beta freeze.

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

Joseph D. Wagner

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/2GSZ5VJIDMGTVF7D7ABDROPX7KJWBPLU/

python-pycrypto package?

[Joseph D. Wagner]

Is python-pycrypto a package?  If not, I'm starting to think it should 
be.  I'm seeing it show up as requirements for some python projects I'd 
like to work on.


Thoughts?

https://pypi.org/project/pycrypto/

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

python-sshtunnel?

[Joseph D. Wagner]

Is python-sshtunnel a package?  If not, I'm starting to think it should 
be.  I'm seeing it show up as requirements for some python projects I'd 
like to work on.


Thoughts?

https://pypi.org/project/sshtunnel/

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

pgadmin4 prerequisites and status report for fedora 29

[Joseph D. Wagner]

The following custom rpms will be obsolete in Fedora 29:

pgadmin4-python3-blinker-1.4-3.f28.noarch    => 
python3-blinker.noarch 1.4-3.fc29
pgadmin4-python3-fixtures-3.0.0-5.f28.noarch => 
python3-fixtures.noarch 3.0.0-11.fc29
pgadmin4-python3-flask-0.12.2-1.f28.noarch   => 
python3-flask.noarch 1:1.0.2-3.fc29
pgadmin4-python3-flask-babel-0.11.1-4.f28.noarch => 
python3-flask-babel.noarch 0.11.2-3.fc29
pgadmin4-python3-flask-babelex-0.9.3-1.f28.noarch    => 
python3-flask-babelex.noarch 0.9.3-3.fc29
pgadmin4-python3-flask-gravatar-0.5.0-1.f28.noarch   => 
python3-flask-gravatar.noarch 0.5.0-3.fc29
pgadmin4-python3-flask-login-0.3.2-3.f28.noarch  => 
python3-flask-login.noarch 0.4.1-3.fc29
pgadmin4-python3-Flask-Mail-0.9.1-4.f28.noarch   => 
python3-flask-mail.noarch 0.9.1-4.fc29
pgadmin4-python3-flask-migrate-2.1.1-1.f28.noarch    => 
python3-flask-migrate.noarch 2.1.1-3.fc29
pgadmin4-python3-flask-paranoid-0.2-1.f28.noarch => 
python3-flask-paranoid.noarch 0.2.0-4.fc29
pgadmin4-python3-flask-principal-0.4.0-14.f28.noarch => 
python3-flask-principal.noarch 0.4.0-17.fc29
pgadmin4-python3-flask-security-3.0.0-1.f28.noarch   => 
python3-flask-security.noarch 3.0.0-3.fc29
pgadmin4-python3-flask-wtf-0.14.2-1.f28.noarch   => 
python3-flask-wtf.noarch 0.14.2-3.fc29
pgadmin4-python3-html5lib-1.0.1-1.f28.noarch => 
python3-html5lib.noarch 1.0.1-1.fc29
pgadmin4-python3-pyrsistent-0.14.2-1.f28.x86_64  => 
python3-pyrsistent.x86_64 0.14.2-5.fc29
pgadmin4-python3-sqlalchemy-1.2.5-1.f28.x86_64   => 
python3-sqlalchemy.x86_64 1.2.11-1.fc29
pgadmin4-python3-sqlparse-0.2.4-1.f28.noarch => 
python3-sqlparse.noarch 0.2.4-3.fc29
pgadmin4-python3-wtforms-2.1-3.f28.noarch    => 
python3-wtforms.noarch 2.2.1-3.fc29



The following custom rpms need to be retained unless the fedora version 
is updated:


pgadmin4-python3-dateutil-2.7.2-1.f28.noarch <= 
python3-dateutil.noarch 1:2.7.0-3.fc29
Updated version requested: 
https://bugzilla.redhat.com/show_bug.cgi?id=1560212


pgadmin4-python3-flask-htmlmin-1.3.2-1.f28.noarch    <= 
python3-flask-htmlmin.noarch 1.3.1-3.fc29
Updated version requested: 
https://bugzilla.redhat.com/show_bug.cgi?id=1622327


pgadmin4-python3-passlib-1.7.1-1.f28.noarch  <= 
python3-passlib.noarch 1.7.0-10.fc29
Updated version requested: 
https://bugzilla.redhat.com/show_bug.cgi?id=1620382


pgadmin4-python3-simplejson-3.13.2-1.f28.x86_64  <= 
python3-simplejson.x86_64 3.10.0-10.fc29
Updated version requested: 
https://bugzilla.redhat.com/show_bug.cgi?id=1462583



The following custom rpms have no fedora equivalent:

pgadmin4-python3-dateutil-doc-2.7.2-1.f28.noarch
Is this one really needed?

pgadmin4-python3-sshtunnel-0.1.3-1.f28.noarch
What can we do to create a python3-sshtunnel package in fedora?


Once the custom rpms are no longer needed, it will be an easy matter to 
create a fedora package for pgadmin4.


Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: python-sshtunnel?

[Joseph D. Wagner]

I'd be happy to help, but I feel overwhelmed.  I've never used the whole
stack of koji, src.fedoraproject.org, fedpkg, etc. 

I need someone to help walk me through the first one. 

Joseph D. Wagner 

On 2018-08-26 07:59, Miro Hrončok wrote:

> On 26.8.2018 09:28, Joseph D. Wagner wrote: 
> 
>> Is python-sshtunnel a package?
> 
> https://src.fedoraproject.org/rpms/python-sshtunnel
> 
> No, it isn't.
> 
>> If not, I'm starting to think it should be.  I'm seeing it show up as 
>> requirements for some python projects I'd like to work on.
> 
> If you need it as a dependency for another package, package it, why not?___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: pgadmin4 prerequisites and status report for fedora 29

[Joseph D. Wagner]

all packages required already in fedora, all you need todo is update 
pgadmin4 spec and get it approved.



First, I've never used any of the online tools (e.g. koji, etc) for 
building a RPM before.  I would need someone to walk me through the 
first one.


Second, I tried your branch RPM, but I couldn't get it to run.  I could, 
however, get the one from the POSTGRESQL repository to run.


I will try yours again.

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Non-responsive maintainer for python-dateutil

[Joseph D. Wagner]

Per policy for non-responsive maintainers 
(https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers)


There has been an outstanding update request since March 24, 2018.

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

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Recompiling Packages with Optimization Flags

[Joseph D Wagner]

Forgive me if this is the wrong spot to ask.

I'm doing some CPU intensive work, and I'd like to optimize a few 
packages.  Even if it's only a 5% gain, it will add up over many 
hours/days of continuous runtime.


Back in the day, I could recompile a package like this:

rpmbuild --rebuild --target=pentium3 package.srpm

And it would produce a package with source compiled using -march=pentium3.

That doesn't appear to be the case anymore for a couple of reasons:

1) /usr/lib/rpm/platform has only the generic x86_64, causing rpm macros 
for more specific microarchitectures, like znver2, to fail.


2) Some configure/make scripts incorrectly recognize "znver2" as a 
request for a cross-compiler, and exit the build with an error.


3) Some rpm spec files appear to use the x86_64 architecture as a test 
for 64-bit capable, so providing a more specific microarchitecture, like 
znver2, actually disables 64-bit extensions in those packages.


Is there a way to pass '-march=znver2' to the compiler from rpmbuild?  
Or are these all bugs that have crept in over the years?


Thanks for your help.

Joseph D. Wagner
___
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

Adding pgadmin4 to Fedora repository

[Joseph D. Wagner]

Fedora 28 launched with PostgreSQL 10.  The PostgreSQL GUI tool in the 
repository -- pgadmin3 -- only works through version 9.x.  Hence, there 
has been a loss of functionality that I have been trying to get back.


All of the prerequisites for pgadmin4 were taken care of here:
BUG 1380826 - Review Request: pgadmin4 - Management tool for PostgreSQL
https://bugzilla.redhat.com/show_bug.cgi?id=1380826

The developer created a working package in a branch here:
https://copr.fedorainfracloud.org/coprs/itamarjp/pgadmin4/build/772898/

However, it looks like the final step of actually adding pgadmin4 as a 
package in the main repository didn't happen.  (At least, I couldn't 
find it the last time I checked.)


Could someone please help me through the next steps?  What must be done 
to get pgadmin4 into the repository?


I would really appreciate any help to get the GUI for PostgreSQL working 
again.


Thanks.

Joseph D. Wagner
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/C7O4JQVQBHLLC4JHRX5JBN2VBO5IH3E3/