Re: bad error on console / shell ... any idea ! ?

[Barry Scott]

> On 30 Mar 2024, at 09:40, Cătălin George Feștilă  
> wrote:
> 
> [root@fedora mythcat]# dnf5 search scV: __reassemble_comp_words_by_ref: 
> command not found
> terminate called after throwing an instance of 'std::invalid_argument'
>  what():  stoi
> V: __reassemble_comp_words_by_ref: command not found
> terminate called after throwing an instance of 'std::invalid_argument'
>  what():  stoi

I hear that this is a known issue with dnf5 at the moment.

Just to check, you are aware that dnf5 is still being developed?

Barry

--
___
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: Donate 1 minute of your time to test upgrades from F39 to F40

[Barry Scott]

On 21/02/2024 07:11, Miroslav Suchý wrote:


dnf --releasever=40 --setopt=module_platform_id=platform:f40 \
--enablerepo=updates-testing \
$(rpm -q fedora-repos-modular >/dev/null && echo 
--enablerepo=updates-testing-modular) \

--assumeno distro-sync


Fedora KDE spin - Intel CPU AMD GPU -

Error:
 Problem: problem with installed package blender-1:4.0.2-1.fc39.x86_64
  - blender-1:4.0.2-1.fc39.x86_64 from @System  does not belong to a 
distupgrade repository
  - nothing provides libopenvdb.so.10.1()(64bit) needed by 
blender-1:4.0.2-1.fc40.x86_64 from fedora

(try to add '--skip-broken' to skip uninstallable packages)

Fedora Server as router - Intel CPU
- No problems.

Fedora Server as router - RaspberryPi
- No problems.

Fedora Server as file server/imapl server/prometheus - Intel CPU
- No problems

Fedora KODI media player - Intel CPU
- No problems

Barry



--
___
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: dmesg restricted to root in Rawhide

[Barry Scott]

> On 28 Feb 2024, at 10:24, Karel Zak  wrote:
> 
> You can restore the original behavior by using:
> 
># sysctl kernel.dmesg_restrict=0
> 
> However, be aware of the security consequences ;-)

Given I can get the same information from journalctl -k what is the improvement?

Barry

--
___
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: Login issues to lists.* and src.*? Any outages?

[Barry Scott]

> On 22 Feb 2024, at 20:20, Christopher  wrote:
> 
> Are there any known issues right now for logging in to 
> lists.fedoraproject.org  or 
> src.fedoraproject.org ?
> Do we have a page for known outages?
> 
> I can log in to accounts.fedoraproject.org 
> , so I know my password and 2FA token 
> still works, but not to src.f.o or lists.f.o.
> I tried to disable my 2FA in there, to see if that had an effect, but it 
> wouldn't let me (I thought it was optional?)
> 
> I'm still in the packager group in accounts.f.o (not inactive). So, I'm not 
> sure what the problem is.
> 
> Is this a known issue? I haven't seen anything about this on the devel list 
> recently.

I am seeing the same issue for https://discussion.fedoraproject.org
When I click to login and try to use my FAS ID I end up on
Here https://id.fedoraproject.org/login/pam
with the error:

Gateway Timeout

The gateway did not receive a timely response from the upstream server or 
application.

But I can and did login successfully to https://accounts.fedoraproject.org

Barry



> 
> Thanks,
> Christopher
> 
> --
> ___
> 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: Mounting USB Storage devices with "sync" option ?

[Barry Scott]

> On 2 Feb 2024, at 17:58, Florian Weimer  wrote:
> 
> The second one is a standard SATA drive in an USB enclosure, and those
> have write-reordering caches, as far as I understand it.

We need a kernel storage expert to tell us the definitive truth on this stuff.
I may be out of date on this stuff.

What I understand is that the drive will be told via the appropriate SCSI(?) 
command
that it must not reorder the writes. Failure to implement that command means the
drive will not have WHQL from Microsoft. Without WHQL its very hard to sell a 
drive
in the market place.

Barry

--
___
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: Mounting USB Storage devices with "sync" option ?

[Barry Scott]

> On 2 Feb 2024, at 11:30, Florian Weimer  wrote:
> 
> Yes, the kernel assumes that there are no such caches, but I think in
> practice there are.  I think this means that journaling file systems are
> not working correctly, in the sense that you do not get just user data
> loss if the device is unplugged prematurely, but also metadata
> corruption.

As I understand it the kernel will request that writes are not cached. Which 
means
that journaling file systems do in fact work well.

As an aside a few years ago (10+ years?) Microsoft found that HDDs where using 
caching
to spoof benchmark results.

But this was leading to support hell for Microsoft with user reporting corrupt 
file systems to them.

What Microsoft did was refuse to issue WHQL for any disk that did not have a 
write
through cache. We in Linux land benefit from this as spoofing hardware, I 
believe, is
not a common occurrence any more.

Barry

--
___
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: fedora-distro-aliases - The easiest way to get numbers of active Fedora releases

[Barry Scott]

> On 17 Jan 2024, at 10:57, Jakub Kadlcik  wrote:
> 
> Hello,
> I just wanted to quickly announce a small project I did in collaboration with 
> the Packit folks.
> 
> Do you have some tools or services that perform actions on all currently 
> active Fedora releases? And do you have to manually update their list every 
> time a new Fedora release is branched or EOLed? The fedora-distro-aliases 
> will make your life easier.
> 
> https://github.com/rpm-software-management/fedora-distro-aliases
> 
> It defines aliases such as `fedora-stable`, `epel-all`, `fedora-latest`, etc. 
> To evaluate them, it queries Bodhi, so they are always up-to-date (but the 
> tradeoff is that it requires an internet connection). There are multiple 
> examples in the project README but the usage is simple, e.g.:
> 
> >>> from fedora_distro_aliases import get_distro_aliases
> >>> aliases = get_distro_aliases()
> >>> [x.namever for x in aliases["fedora-all"]]
> ['fedora-38', 'fedora-39', 'fedora-rawhide']

Yes I have tools I update the list of fedora releases in.
Thanks for this tool!

Now I'm off to update my tools to use this.

> 
> The package is already in Fedora, give it a shot,

And its called python3-fedora-distro-aliases

Barry

> 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, 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

Where to add new ssh key to my FAS account?

[Barry Scott]

I have been changing from SSH RSA key to using ed25519 based keys.
I cannot recall, or track down docs on where to upload my new ssh key to
for my FAS account.

Can you point me in the right direction please?

Barry
--
___
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: F40 Change Proposal: Optimized Binaries for the AMD64 Architecture (System-Wide)

[Barry Scott]

> On 28 Dec 2023, at 16:58, Chris Adams  wrote:
> 
> Anything that depends on PATH entries is IMHO doomed to failure.

Indeed, how would my shell get the right micro architecture into its PATH?
Would konsole on plasma desktop picking up PATH from systemd?

The alternative would be to symlink the "right" version of a program/library 
from
the micro architecture dir into /usr/bin and /usr/lib maybe?

Barry


--
___
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: FAS 2FA recovery keys?

[Barry Scott]

> On 12 Sep 2023, at 10:32, Michael J Gruber  wrote:
> 
> Am Di., 12. Sept. 2023 um 11:22 Uhr schrieb Barry Scott
> :
>> 
>> I have been updating my FAS account security.
>> When I setup 2FA I was not offer any recovery keys.
> 
> You can register multiple OTP tokens:
> https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/2-factor/

I did notice I could setup more then one and have used pass-otp for my 2nd 2FA 
method.

> 
>> In the event that I lose FreeOTP on my phone how do I recover?
> 
> If you lost all of your tokens you can request a reset:
> https://fedoraproject.org/wiki/Infrastructure_Two_Factor_Auth#What_happens_if_I_lost_my_token_or_got_a_new_device?

Good to know.

> 
> That being said, I'm in the same boat: Getting recovery keys *at the
> same time* as activating 2fa has something soothing to it ...

Yep, and its what I have seen for every over service I setup 2FA for.

Barry

> 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, 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

FAS 2FA recovery keys?

[Barry Scott]

I have been updating my FAS account security.
When I setup 2FA I was not offer any recovery keys.

In the event that I lose FreeOTP on my phone how do I recover?

Barry
___
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: SPDX Statistics - Flock edition

[Barry Scott]

On 05/08/2023 08:07, Miroslav Suchý wrote:


Tip of the day:

    Do you want to validate your License string? Use: license-validate 
"$YOUR_LICENSE_STRING"



I dnf installed license-validate on F38
Then run it to check a license and it does this:

$ /usr/bin/license-validate BSD
No terminal defined for 'B' at line 1 col 1

BSD
^

Expecting: {'__ANON_79', 'SWL', '__ANON_91', '__ANON_128', 'TTWL', 
'__ANON_8', '__ANON_253', 'LATEX2E', '__ANON_104', '__ANON_223', '


What am I doing wrong?

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

[Barry Scott]

> On 18 Jun 2023, at 17:41, Miro Hrončok  wrote:
> 
> On 18. 06. 23 15:17, Barry Scott wrote:
>>> On 17 Jun 2023, at 10:50, Miro Hrončok  wrote:
>>> 
>>> Please avoid further rawhide builds of them until the side tag is merged.
>> I have been fixing pycxx and pysvn for python 3.12.
>> I have released new pycxx and pysvn upstream that fix the 3.12 issues.
>> But I did not see your message about not building in rawhide, sorry.
>> python-pycxx was buildt in rawhide.
>> I have not built pysvn in rawhide.
>> For both packages I have pushed updates to sources and spec file that are 
>> needed
>> for 3.12 support.
>> For pycxx need to have conditional access to _Py_PackageContext and replace 
>> use
>> of distutils.
>> For pysvn fix a SEGV when the process exits.
> 
> I'v attempted to rebuild python-pycxx:
> 
> Traceback (most recent call last):
>  File "/builddir/build/BUILD/pycxx-7.1.8/setup.py", line 3, in 
>from distutils.command.install import install
> ModuleNotFoundError: No module named 'distutils'

I have updated the .spec file and pushed to main and rawhide Release 3.

Did:
fedpkg mockbuild --root fedora-rawhide-x86_64

to check but that is still 3.11.

Barry


> 

> 
> The distutils module eas removed from the Python standard library.
> You should be able to fix this by BuildRequiring python3-setuptools.
> 
> Cannot build pysvn yet, as it is blocked by the above.
> 
> -- 
> Miro Hrončok
> -- 
> Phone: +420777974800
> IRC: mhroncok

___
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

[Barry Scott]

> On 18 Jun 2023, at 17:41, Miro Hrončok  wrote:
> 
> On 18. 06. 23 15:17, Barry Scott wrote:
>>> On 17 Jun 2023, at 10:50, Miro Hrončok  wrote:
>>> 
>>> Please avoid further rawhide builds of them until the side tag is merged.
>> I have been fixing pycxx and pysvn for python 3.12.
>> I have released new pycxx and pysvn upstream that fix the 3.12 issues.
>> But I did not see your message about not building in rawhide, sorry.
>> python-pycxx was buildt in rawhide.
>> I have not built pysvn in rawhide.
>> For both packages I have pushed updates to sources and spec file that are 
>> needed
>> for 3.12 support.
>> For pycxx need to have conditional access to _Py_PackageContext and replace 
>> use
>> of distutils.
>> For pysvn fix a SEGV when the process exits.
> 
> I'v attempted to rebuild python-pycxx:
> 
> Traceback (most recent call last):
>  File "/builddir/build/BUILD/pycxx-7.1.8/setup.py", line 3, in 
>from distutils.command.install import install
> ModuleNotFoundError: No module named 'distutils'
> 
> 
> The distutils module eas removed from the Python standard library.
> You should be able to fix this by BuildRequiring python3-setuptools.

On it. I'll fix upstream and update .spec etc.

Barry


> 
> Cannot build pysvn yet, as it is blocked by the above.
> 
> -- 
> Miro Hrončok
> -- 
> Phone: +420777974800
> IRC: mhroncok

___
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

[Barry Scott]

> On 17 Jun 2023, at 10:50, Miro Hrončok  wrote:
> 
> Please avoid further rawhide builds of them until the side tag is merged.

I have been fixing pycxx and pysvn for python 3.12.
I have released new pycxx and pysvn upstream that fix the 3.12 issues.

But I did not see your message about not building in rawhide, sorry.

python-pycxx was buildt in rawhide.
I have not built pysvn in rawhide.

For both packages I have pushed updates to sources and spec file that are needed
for 3.12 support.

For pycxx need to have conditional access to _Py_PackageContext and replace use
of distutils.

For pysvn fix a SEGV when the process exits.

Barry

___
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: F39 proposal: Replace DNF with DNF5 (System-Wide Change proposal)

[Barry Scott]

> On 19 Dec 2022, at 16:50, Jaroslav Mracek  wrote:
> 
> I also remember RHEL8 where we ship DNF as YUM. And DNF is very similar to 
> YUM - both are Python based tool. Anyway in RHEL9 the same tool is shipped as 
> DNF, because it creates a confusion. And I don't want to experience the same 
> issue twice. I understand that the name change is always not nice, but 
> keeping the same name for a different tool is worse.

I'm using Oracle Linux 8 at work and some older scripts use "yum" and newer 
scripts use "dnf" this all just works.

What is the confusion that you are trying to avoid?

The only issue that I recall from earlier in the thread is that dnf version 5 
is not feature complete enough to replace dnf version 4.

Is there any database that is corrupted if dnf v4 and dnf v5 commands are mixed 
on a system?

Barry


___
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: Orphaned packages looking for new maintainers

[Barry Scott]

> On 19 Dec 2022, at 17:40, Ben Cotton  wrote:
> 
> On Mon, Dec 19, 2022 at 12:36 PM Barry  wrote:
>> 
>> Why is pysvn on the list? I the pysvn maintainer and i am active.
>> I am also the upstream maintainer.
> 
> The "main admin" is orphan. You should be able to go to
> https://src.fedoraproject.org/rpms/pysvn and click the "Take" button
> on the left-hand side. (This is an unfortunate side-effect of how
> dist-git works).

Taken and I'm the bugzilla contact as well.

Does "main admin" being "orphan" go away when background processes catch up 
with the changes I just made?

Barry

> 
> -- 
> Ben Cotton
> He / Him / His
> Fedora Program Manager
> Red Hat
> TZ=America/Indiana/Indianapolis
> ___
> 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: Why install rsyslog by default?

[Barry Scott]

> On 25 Aug 2022, at 16:05, Robert Marcano via devel 
>  wrote:
> 
> On 8/25/22 11:02 AM, Barry Scott wrote:
>> I just found that rsyslog is installed and by default creating legacy
>> log files in /var/log like messages and secure.
>> Now that journald has been in Fedora for so long this is useful
>> default to install rsyslog?
> 
> I don't have it installed. I think it is usually Chrome RPM (not Chromium) 
> that bring a lot of awful dependencies because it requires some legacy lsb 
> packages.
> 

Its in the dnf history info 1 so in the Fedora KDE base install, not what you 
suggest,
no chrome stuff installed.

Also dnf remove does not try to pull out any thing by a few deps of rsyslog.

Barry

> Last time I installed it even pulled perl packages.
> 
>> Barry
>> ___
>> 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 
> <mailto:devel@lists.fedoraproject.org>
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org 
> <mailto:devel-le...@lists.fedoraproject.org>
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ 
> <https://docs.fedoraproject.org/en-US/project/code-of-conduct/>
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines 
> <https://fedoraproject.org/wiki/Mailing_list_guidelines>
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org 
> <https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org>
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue 
> <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

Why install rsyslog by default?

[Barry Scott]

I just found that rsyslog is installed and by default creating legacy
log files in /var/log like messages and secure.

Now that journald has been in Fedora for so long this is useful
default to install rsyslog?

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

How to add epel9 branch to my package's git clone?

[Barry Scott]

I want to build my packages for epel9. But that branch is not setup in git.

https://src.fedoraproject.org/rpms/python-pycxx

How do I add epel9?

Barry

___
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

Cannot report selinux bug...

[Barry Scott]

I was told to report an selinux bug.

I clicked the report bug button and was asked for my API key.
Then I created the API key and plugged that in and hit OK.

Now I am being asked to unlock a keyring (?) with the name
"default". It is not locked with my password.

I'm on KDE. Is this "default" a gnome thing? If so how do I
set it up under KDE.

Then I can get back to reporting the selinux bug.

Barry

___
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: remove-retired-packages feedback

[Barry Scott]

> On 26 May 2022, at 14:52, Miroslav Suchý  wrote:
> 
> If you already upgraded to Fedora 36 - what is your feedback about
> 
> https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/sysadmin/System_Utilities/#remove-retired-packages
>  
> 
> Did you run the command `remove-retired-packages`? Do you find it useful? 
> Comments and ideas are welcome either here or at:
> 
> https://github.com/xsuchy/fedora-upgrade/issues 
> 
> Just be sure that you have latest version, i.e., remove-retired-packages-36.3.
> 
Useful command!

It found a number of packages to remove.

One was a package that I built to locally and installed from the command line, 
which it
correctly identified as not in F36.

I like that it prompts for each package on its own. This meant that I could 
remove the
3 that I do not need to keep but leave the one that I do need.

Barry



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

Re: compile a basic example to arm executable on Fedora

[Barry Scott]

> On 13 Mar 2022, at 21:59, Cătălin George Feștilă  
> wrote:
> 
> I asked because I don't think arm development is well implemented. An answer 
> would be as correct as possible from a developer who has worked with 
> something like this, considering that it is not very well documented and I 
> have not seen the tests with this tool that would work with development 
> libraries.

Then you need the fedora arm mailing list.
That is where the arm experts hang out.

Barry


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

Re: compile a basic example to arm executable on Fedora

[Barry Scott]

> On 13 Mar 2022, at 20:46, Cătălin George Feștilă  
> wrote:
> 
> I try to create a hello word arm static executable, with the default example 
> but I got these errors.
> I search on the web and fedora packages to find a way to solve this issue.  

This list is for developing fedora itself, not a programming development list.

I think you are better off asking on the fedora arm mailing list or the fedora 
users mailing list.  

Barry

> I used a basic example source code:
> 
> cat hello.c 
> #include 
> using namespace std;
> int main(void)
> {
>   std::cout << "Hello word! from Fedora Linux!" << std::endl;
>   return 0;
> }
> 
> I install wit the dnf tool 
> 
> dnf install -y libstdc++-static.x86_64
> dnf install -y llvm
> dnf install -y glib-static
> I try also with -static and 
> arm-none-eabi-g++ -static-libstdc++ hello.c -o arm_hello-static 
> but , I got these errors, any help ?
> 
> [root@fedora mythcat]# arm-none-eabi-g++ hello.c -o arm_hello 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-exit.o):
>  in function `exit':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/stdlib/../../../../../newlib/libc/stdlib/exit.c:64:
>  undefined reference to `_exit'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-abort.o):
>  in function `abort':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/stdlib/../../../../../newlib/libc/stdlib/abort.c:59:
>  undefined reference to `_exit'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-fstatr.o):
>  in function `_fstat_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/fstatr.c:55:
>  undefined reference to `_fstat'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-openr.o):
>  in function `_open_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/openr.c:50:
>  undefined reference to `_open'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-sbrkr.o):
>  in function `_sbrk_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/sbrkr.c:51:
>  undefined reference to `_sbrk'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-signalr.o):
>  in function `_kill_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/signalr.c:53:
>  undefined reference to `_kill'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-signalr.o):
>  in function `_getpid_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/signalr.c:83:
>  undefined reference to `_getpid'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-writer.o):
>  in function `_write_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/writer.c:49:
>  undefined reference to `_write'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-closer.o):
>  in function `_close_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/closer.c:47:
>  undefined reference to `_close'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-isattyr.o):
>  in function `_isatty_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/isattyr.c:52:
>  undefined reference to `_isatty'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-lseekr.o):
>  in function `_lseek_r':
> /builddir/build/BUILD/newlib-4.1.0/build-newlib/arm-none-eabi/newlib/libc/reent/../../../../../newlib/libc/reent/lseekr.c:49:
>  undefined reference to `_lseek'
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/bin/ld: 
> /usr/lib/gcc/arm-none-eabi/11.1.0/../../../../arm-none-eabi/lib/libc.a(lib_a-readr.o):
>  in 

dnf install removes /etc/systemd/system/multi-user.wants/myservice.target symlink

[Barry Scott]

This is not for a package in Fedora, its for a package I'm
working on for Oracle Linux 8.

I install /usr/lib/systemd/system/myservice.target
that has:

[Install]
WantedBy=multi-user.target

In %post I run this:

ls -l /etc/systemd/system/multi-user.target.wants
/usr/bin/systemctl --no-reload enable ods-prx.target
ls -l /etc/systemd/system/multi-user.target.wants
echo "Info: post done"

When I dnf install myservice I see that the symlink is
setup from the ls -l output in the %post section.

But later in the output I see this line:

Info: post done

  Running scriptlet: myservice-2022.1-20220207180603.noarch
Removed /etc/systemd/system/multi-user.target.wants/myservice.target.

Is this expected?

How can I stop this happening?

If its not expected how can I pull apart the RPM to find the code that is 
running?

Barry


___
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: Why was node_exporter.service renamed to prometheus-node-exporter.service?

[Barry Scott]

> On 28 Jan 2022, at 15:33, Robert-André Mauchin  wrote:
> 
> Hello,
> 
> I'm sorry, this is entirely my fault. I provided symlinks for the binaries, 
> but didn't think of the systemd unit files symlinks. The services files were 
> added or modified to take into account environment files which were requested 
> multiple times, and without which the package were basically unusable. The 
> binary were renamed to provide commonalities with other distro.
> Alert manager service was added, Node exporter and Prometheus were fixed. 
> There should not be any breaking change for Prometheus though, the only thing 
> added was the Environment file.
> I will seek co-maintainers for these packages as I initially packaged them to 
> be used as dependency for other projects but I never intended to be 
> maintainer of the services, which are a bit out of my depth.
> I will be pushing an update for node-exporter with a service symlink for the 
> old name.


You can add me as co-maintainer. I'm happy to review any future changes
and discuss packing issues.

Also I like that you have made important improvement to the packaging.
I was working around the problems with being able to pass args to the
prometheus and node-exported command lines.

I found that you made another breaking changes.

You changed the UID/GID for node_exporter's text-collector folder from
node_exporter to prometheus. I'm not convinced that is a useful change.
I was running processes that write to that folder Group=node_exporter.
Now I have to use Group=prometheus and that seems wrong to me.

Why can my collector also access prometheus resources via Group permissions?
Isn't it better that node_exporter and prometheus are keep apart?

Barry

___
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: Why was node_exporter.service renamed to prometheus-node-exporter.service?

[Barry Scott]

> On 28 Jan 2022, at 12:28, Tomasz Torcz  wrote:
> 
> On Fri, Jan 28, 2022 at 12:01:43PM +0000, Barry Scott wrote:
>> I just had to fix a number of my servers that use node exporter.
>> 
>> The service name has been changed. Why was this done and did no one
>> think about the impact on users?
> 
>  This was done here:
>  
> https://src.fedoraproject.org/rpms/golang-github-prometheus-node-exporter/c/5ad49dd6ed767d44070866d996d844dec4b5f07b?branch=f35
> 
>  as part of the fix for
>  https://bugzilla.redhat.com/show_bug.cgi?id=2039257
>  (golang-github-prometheus-node-exporter installs service unit in /etc)
> 
>  Moving the unit is fine, but rename should not happen stable release.
> At least some compat symlinks/Alias= should be provided.
> 
>> In the worst case I had a server fail to reboot because I had
>> Requires=node_exporter.service in the default target.
> 
>  It is unfortunate. It is also unfortunate no-one cared enough about
> node-exporter to have it tested during 2 weeks time
> (https://bodhi.fedoraproject.org/updates/FEDORA-2022-e52d3d8db2)
> before it was submitted to stable.

I guess what is surprising me is that it's a breaking change and that was not
noticed in review or dev testing.

I have now updated golong-github-prometheus that has more breaking changes to 
handle.

The change in the way that .service file handles arguments is welcome.
But its not compatible with the previous .service files handling.

Barry
___
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: Why was node_exporter.service renamed to prometheus-node-exporter.service?

[Barry Scott]

On Friday, 28 January 2022 12:01:43 GMT Barry Scott wrote:
> I just had to fix a number of my servers that use node exporter.
> 
> The service name has been changed. Why was this done and did no one
> think about the impact on users?
> 
> In the worst case I had a server fail to reboot because I had
> Requires=node_exporter.service in the default target.

Was:

$ rpm -ql golang-github-prometheus-node-exporter-1.2.2-1.fc35.x86_64 | grep 
service
/etc/systemd/system/node_exporter.service
/usr/share/doc/golang-github-prometheus-node-exporter/examples/systemd/
node_exporter.service

Now is:

$ rpm -ql golang-github-prometheus-node-exporter-1.3.1-4.fc35.x86_64 | grep 
service
/usr/lib/systemd/system/prometheus-node-exporter.service
/usr/share/doc/golang-github-prometheus-node-exporter/examples/systemd/
node_exporter.service

So the why is that it puts the service file in the right place.

That leaves the impact of the fix.

Barry


___
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

Why was node_exporter.service renamed to prometheus-node-exporter.service?

[Barry Scott]

I just had to fix a number of my servers that use node exporter.

The service name has been changed. Why was this done and did no one
think about the impact on users?

In the worst case I had a server fail to reboot because I had
Requires=node_exporter.service in the default target.

Barry
___
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: Fix for python-tzlocal FTBFS

[Barry Scott]

> On 22 Dec 2021, at 21:46, Richard Shaw  wrote:
> 
> On Wed, Dec 22, 2021 at 5:16 AM Barry Scott  <mailto:ba...@barrys-emacs.org>> wrote:
> I have added a patch for the spec file for python-tzlocal.spec
> that allows the 4.1 release to build.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1993583 
> <https://bugzilla.redhat.com/show_bug.cgi?id=1993583>
> 
> I can raise a PR if that helps, but I have not done that before
> so pointers to the work flow would be welcomed.
> 
> A PR is best, that way even a provenpackager can easly help you out if the 
> maintainer doesn't respond. The workflow is very similar to a PR in github if 
> you've done that before.
> 
> Also an email to -maintai...@fedoraproject.org 
> <mailto:maintai...@fedoraproject.org> will send an email to all the 
> maintainers of a package and can be useful for a nudge.

Thanks. I'll follow up when I get a quiet moment.

I have this working in my copr, but it was a lot harder than I hoped.
All the parts are in 
https://copr.fedorainfracloud.org/coprs/barryascott/tools-testing/

This is now a lot more then a PR...

I had to:
* package pytz_deprecation_shim that is a new dependance.
* add boiler plate setup.py to allow the setup.cfg to be used to build tzlocal
* add AutoProvReg: no to stop unused refs being auto added (should only need 
AutoProv: no).
* turn off the tests in %check as they want to use pip to install stuff
* learn that rpmbuild is not close to mock/copr build again :-)

Barry


> 
> Thanks,
> Richard 
> ___
> 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

Re: Fix for python-tzlocal FTBFS

[Barry Scott]

> On 22 Dec 2021, at 11:12, Barry Scott  wrote:
> 
> I have added a patch for the spec file for python-tzlocal.spec
> that allows the 4.1 release to build.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1993583
> 
> I can raise a PR if that helps, but I have not done that before
> so pointers to the work flow would be welcomed.
> 
> I need the 4.1 version for one of my copr projects.

Just found that I also need a pytz-deprecation-shim.
I tried to build on copr into my tools-testing project with:

$ copr-cli buildpypi --chroot=fedora-35-x86_64 
--packagename=pytz-deprecation-shim --pythonversions=3 tools-testing

This fails reporting that setup.py is missing, which is true it provided 
setup.cfg only.
I've not see setup.cfg before but a bit of searching I found that I can build 
via:

$ python3  -m build --no-isolation

That builds a wheel.

Is there an example .spec that I can use to package this setup.cfg only PyPI 
project?

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

PyQt6 for fedora status?

[Barry Scott]

I see that there are packages for qt6, but no python-qt6 yet.

What is the plan for this please?

I have built PyQt5 in the past and, time permitting, can
offer help.

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

Fix for python-tzlocal FTBFS

[Barry Scott]

I have added a patch for the spec file for python-tzlocal.spec
that allows the 4.1 release to build.

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

I can raise a PR if that helps, but I have not done that before
so pointers to the work flow would be welcomed.

I need the 4.1 version for one of my copr projects.

Barry

___
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: locale available in mock build for python package %check

[Barry Scott]

> On 13 Dec 2020, at 16:32, Tom Hughes  wrote:
> 
> On 13/12/2020 16:26, Barry Scott wrote:
> 
>> Is my way forward to add en_US.UTF-8 locale?
>> What do I add to the spec file to do that?
> 
> Adding a BuildRequire on glibc-langpack-en will probably do it.

That works great.

Next time pysvn is build the %check will work.

BArry

> 
> The default build root only has glibc-minimal-langpack which just
> gives you the basic C locale.
> 
> Tom
> 
> -- 
> Tom Hughes (t...@compton.nu)
> http://compton.nu/
> 
___
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

locale available in mock build for python package %check

[Barry Scott]

I'm looking at getting the %check of the pysvn package working.

What I'm seeing is the tests fail because of an issue with python3.9 and 
locales.

The test code uses locale.getdefaultlocale() to find out what can be set and 
uses locale.setlocale() to init the locale.

After mock fails to run the %check I do this to investigate:

$ mock -r fedora-33-x86_64 --shell --no-clean
...
 sh-5.0# locale
LANG=C.UTF-8
LC_CTYPE="C.UTF-8"
LC_NUMERIC="C.UTF-8"
LC_TIME="C.UTF-8"
LC_COLLATE="C.UTF-8"
LC_MONETARY="C.UTF-8"
LC_MESSAGES="C.UTF-8"
LC_PAPER="C.UTF-8"
LC_NAME="C.UTF-8"
LC_ADDRESS="C.UTF-8"
LC_TELEPHONE="C.UTF-8"
LC_MEASUREMENT="C.UTF-8"
LC_IDENTIFICATION="C.UTF-8"
LC_ALL=
 sh-5.0# python3.9
Python 3.9.0 (default, Oct  6 2020, 00:00:00) 
[GCC 10.2.1 20200826 (Red Hat 10.2.1-3)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import locale
>>> locale.getdefaultlocale()
('en_US', 'UTF-8')
>>> locale.setlocale(locale.LC_ALL, 'en_US.UTF-8')
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib64/python3.9/locale.py", line 610, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting
>>> locale.setlocale(locale.LC_ALL, 'C.UTF-8')
'C.UTF-8'
>>> 
 sh-5.0# 

I see this from the f33 command line:

$ LC_ALL=C.UTF-8 python3.9 -c 'import locale;print(locale.getdefaultlocale())'
('en_US', 'UTF-8')
$ LC_ALL=de_DE.UTF-8 python3.9 -c 'import 
locale;print(locale.getdefaultlocale())'
('de_DE', 'UTF-8')
$ LC_ALL=en_GB.UTF-8 python3.9 -c 'import 
locale;print(locale.getdefaultlocale())'
('en_GB', 'UTF-8')

Not sure what is wrong here.

python does not report C.UTF-8 as the default.
mock does not have en_US.UTF-8 setup.

Is my way forward to add en_US.UTF-8 locale?
What do I add to the spec file to do that?

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

fedpkg push - traceback - and a PR created?

[Barry Scott]

$ fedpkg push
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 2 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 353 bytes | 353.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Emitting a message to the fedora-messaging message bus.
remote: Traceback (most recent call last):
remote:   File "/usr/share/git-core/post-receive-fedora-messaging", line 153, 
in 
remote: commits = [_build_commit(rev) for rev in revs]
remote:   File "/usr/share/git-core/post-receive-fedora-messaging", line 153, 
in 
remote: commits = [_build_commit(rev) for rev in revs]
remote:   File "/usr/share/git-core/post-receive-fedora-messaging", line 54, in 
revs_between
remote: for line in stdout.decode('utf-8').strip().split('\n'):
remote: AttributeError: 'str' object has no attribute 'decode'
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 1 commits
remote:   - to fedora-message
remote: 
remote: Create a pull-request for epel8
remote:https://src.fedoraproject.org/rpms/pysvn/diff/master..epel8
remote: 
To ssh://pkgs.fedoraproject.org/rpms/pysvn
   7f8848a..3dba260  epel8 -> epel8

Where do want the traceback reported?

Why is a PR being created? I'm the maintainer and have not seen this before.

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

Live Image hanging problem https://bugzilla.redhat.com/show_bug.cgi?id=1768498

[Barry Scott]

I see that this ticket is still NEW.

I've update with my experience that the suggested fix works.

It would be good to get this fix in for F33.

Is there more testing I can do to help?

Barry
___
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: It seems that gdb cannot find debuginfo on f32

[Barry Scott]

> On 14 Jun 2020, at 08:48, Jan Kratochvil  wrote:
> 
> On Sun, 07 Jun 2020 17:22:33 +0200, Barry Scott wrote:
>> python3-debuginfo.x86_64 3.8.3-1.fc32
>>
>> @updates-debuginfo
> ...
>> Reading symbols from /usr/bin/python3.8...
>> Reading symbols from .gnu_debugdata for /usr/bin/python3.8...
>> (No debugging symbols found in .gnu_debugdata for /usr/bin/python3.8)
>> Missing separate debuginfos, use: dnf debuginfo-install 
>> python3-3.8.3-1.fc32.x86_64
>> (gdb) 
>> 
>> Am I doing something wrong?
> 
> I do not see the problem, you can verify:
> 
> $ ls -l /usr/lib/debug/usr/bin/python3.8-3.8.3-1.fc32.x86_64.debug
> -r--r--r-- 1 root root 17800 May 19 10:31 
> /usr/lib/debug/usr/bin/python3.8-3.8.3-1.fc32.x86_64.debug
> $ rpm -qf /usr/lib/debug/usr/bin/python3.8-3.8.3-1.fc32.x86_64.debug
> python3-debuginfo-3.8.3-1.fc32.x86_64
> $ rpm -V python3-debuginfo-3.8.3-1.fc32.x86_64
> $ _

I tried to reproduce and gdb asked me to install the debug info/source again.
When I did gdb worked as expected.

Thanks for the double check.

Barry


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

It seems that gdb cannot find debuginfo on f32

[Barry Scott]

I'm trying to debug a segv in PyQt5 and I hit a problem with gdb
not finding debug info in f32.

I have installed python3.8 debug info.

$ dnf list installed | grep debug | grep python3
python3-debuginfo.x86_64 3.8.3-1.fc32   

@updates-debuginfo
python3-debugsource.x86_64   3.8.3-1.fc32   

@updates-debuginfo
python3-qt5-base-debuginfo.x86_645.13.2-5.fc32  

@fedora-debuginfo

But still gdb says it cannot find the debuginfos.

$ gdb /usr/bin/python3.8
GNU gdb (GDB) Fedora 9.1-5.fc32
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/python3.8...
Reading symbols from .gnu_debugdata for /usr/bin/python3.8...
(No debugging symbols found in .gnu_debugdata for /usr/bin/python3.8)
Missing separate debuginfos, use: dnf debuginfo-install 
python3-3.8.3-1.fc32.x86_64
(gdb) 

Am I doing something wrong?

Should I raise a BZ?

Barry


___
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: How to debug live CD image?

[Barry Scott]

> On 30 May 2020, at 14:12, Vitaly Zaitsev via devel 
>  wrote:
> 
> On 30.05.2020 15:04, Barry Scott wrote:
>> I use the KDE respin and it hangs at the same place.
>> I waited over an hour to see if will continue.
>> 
>> How can I help debug this?
> 
> I think that your problem is definitely related to this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1830896
> 
> You can install Fedora and try one of the suggested workarounds.

I have Fedora installed on the HDD of this PC and it boots without any issues.

Its only the live CD that has the issue.

Given that my PC boots from HDD but not live USB image I'm not
so sure that that bug is the problem. Especically if its efivars that are
the root cause as that should be the same for my HDD and USB?

Barry


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

Re: How to debug live CD image?

[Barry Scott]

> On 24 May 2020, at 13:21, Vitaly Zaitsev via devel 
>  wrote:
> 
> On 24.05.2020 11:47, Barry Scott wrote:
>> I have tested with both the Workstation image and 
>> the KDE spin image. Both get stuck at the same place.
> 
> Can you check latest respins[1]?
> 
> [1]: https://dl.fedoraproject.org/pub/alt/live-respins/


I use the KDE respin and it hangs at the same place.
I waited over an hour to see if will continue.

How can I help debug this?

Barry



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

Re: How to debug live CD image?

[Barry Scott]

> On 24 May 2020, at 21:55, Paul Dufresne via devel 
>  wrote:
> 
> Le 20-05-24 à 05 h 47, Barry Scott a écrit :
>> ...
>> But I cannot boot a live CD image as it gets stuck
>> in "Monitoring of LVM2 mirrors, ...". This is not a
>> new problem I have seen this for a couple of Fedora
>> releases, but not reported it before.
> 
> Is it possible you don't wait enough, that is about 8 minutes by boot?

It is at 55mins 18s at the moment.

I'll test the respin later and report back.

> 
> Look https://bugzilla.redhat.com/show_bug.cgi?id=1830896
> 
> I was introduced to this from eugine in: 
> https://ask.fedoraproject.org/t/boot-loading-time-is-very-high/6076/8
> 
> 
> ___
> 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 debug live CD image?

[Barry Scott]

My desktop PC is happily running Fedora for years.
Its on Fedora 32 now. It also has Windows 10 dual
boot via Grub.

But I cannot boot a live CD image as it gets stuck
in "Monitoring of LVM2 mirrors, ...". This is not a
new problem I have seen this for a couple of Fedora
releases, but not reported it before.

I have tested with both the Workstation image and 
the KDE spin image. Both get stuck at the same place.

How do I go about debugging what is going on?

Barry


___
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

user services run during system-upgrade

[Barry Scott]

I raise this https://bugzilla.redhat.com/show_bug.cgi?id=1829799 with details
that show that users sessions are started up and user services run during
the dnf system-upgrade. This is clearly not a good idea.

It has been triaged, but its not a RPM script issues as suggested.

I'm not sure who should look at this, but feel that it should not be ignored.

Barry


___
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: What is force erasing python 2 packages like moin?

[Barry Scott]

> On 10 May 2020, at 17:45, Igor Raits  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> On Sun, 2020-05-10 at 17:31 +0100, Barry Scott wrote:
>> I know that python2 is a dead language, but I have a need to use some
>> python 2 code
>> on one of my servers. It's clearly on me to maintain the old code if
>> I choose to use it.
>> 
>> I use MoinMoin via mon_wsgi.
>> 
>> After upgrading to fedora 32 I took the trouble to install moin using
>> the F31 package.
>> And all was good.
>> 
>> But I just did my first dnf update and was surprised to find these
>> lines in the log of 
>> the dnf update:
>> 
>> ---> Package moin.noarch 1.9.10-3.fc31 will be erased
>> ---> Package python2-mod_wsgi.x86_64 4.6.6-2.fc32 will be erased
>> 
>> What is forcing the erase? I need to workaround this.
> 
> fedora-obsolete-packages I guess.
> 
> Just build the packages you need with newer version/release. Then
> python3 subpackage or fedora-obsolete-packages won't remove them.

Thanks for the explanation.

I'll package as barry-XXX to avoid the problem.

Barry



> 
>> Barry
>> ___
>> 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
> - -- 
> Igor Raits 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEEcwgJ58gsbV5f5dMcEV1auJxcHh4FAl64L48ACgkQEV1auJxc
> Hh678xAAo/orxcpLxsOaAAmusa/THRWnHbt8/DTcjZXOB04WzL7gd/jb6HqO/bgg
> bihxGGyzDiFSGi/cIiZ7X9Tweiq2IynjSep2fhVlNUBKcIKKmPaJkDWIlqTaPt+n
> hRpDzKaowwFLHs2N9N9rsQQPm5NLbIIhEH00aWg5KqZ1OErMT2cqM9MS7nLLOakP
> nRqkC+9dbUx8kFdVMDedWQlH1tW2SDi+9mpX6TXqizJuOGHBAIGqhILcrUB8suJl
> vM5XElvHEObmtRksglCjJ+Ogou57SDN0jOik7nwhCvxDgxbC+/DIMPWNXyykWCON
> mkasRJMmhpbSx8JJ5aNnbeCnn9d6NrQv4T9TxriQjzZTs+NUvbYGHmJxQHExEUmP
> A0Ix7V5t8SgKuZ6P9cwlQqEagwntjIr8vyxs6YZscT0L5CGXL1LEKETQRI61JhdG
> /dMIB47qU78HJn/MQmYjyBic5wp7+PrGqPaTtdxxX0Jr/U0HgqLL4JVuN9EVKypb
> rY4ucKqVW4MCHGY2IxLXIbdcoeFtypqwoJagXbf1kBV9fMpVUcPcJqhfNAC29yt1
> I0a2qGlBC9PatWQ6TKPhobVfWFJA//RAvFiRVKnupe6+0aynaT+j377tJoGu9Cdj
> rkatM+zxroo2WjcDkgBvbcjuD1t42y3J46rfn78l1+aHrMPwXgY=
> =Rukt
> -END PGP 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
___
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

What is force erasing python 2 packages like moin?

[Barry Scott]

I know that python2 is a dead language, but I have a need to use some python 2 
code
on one of my servers. It's clearly on me to maintain the old code if I choose 
to use it.

I use MoinMoin via mon_wsgi.

After upgrading to fedora 32 I took the trouble to install moin using the F31 
package.
And all was good.

But I just did my first dnf update and was surprised to find these lines in the 
log of 
the dnf update:

---> Package moin.noarch 1.9.10-3.fc31 will be erased
---> Package python2-mod_wsgi.x86_64 4.6.6-2.fc32 will be erased

What is forcing the erase? I need to workaround this.

Barry
___
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: RFC: Python minimization in Fedora

[Barry Scott]

> On 15 Jan 2020, at 17:05, Miro Hrončok  wrote:
> 
> In Python Maint, we sat down and we came up with several ideas how to 
> minimize the filesystem footprint of Python. Unfortunately, the result is 
> horribly long, sorry about that.

Did you calculate file sizes including rounding up by the
"filesystem block size" (statvfs f_bsize)?

What was the f_bsize of the file system you collected stats on?

The work to stop needing libpython is going to drop the number of files by 1
for the min install.

Can you link some of the .so's from stdlib into the main python image?

If all stdlib .so are linked into the main python and you have .zip for the
.py/.pyc files you can get python down to a handful of files.

Python app making software often exploits a trick that you can concatenate
the .zip on the end of the python image. I'm guessing that would break too many
of the constraints.

I'm not sure how you would do it but what if you created a SquashFS image
for python to lose the f_bsize overhead and use its compression?

Today python has 2 optimised file types. But the python devs have been talking
about ways to implement more optimisations and cache those results as well.
I'll failed to track down the discussion on python dev. I recall wanting to
reduce the file size by storing line number data for traceback outside of
the .pyc.

Barry

___
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 do I add bohdi revelant tag?

[Barry Scott]

I wish to push pycxx for epel7 how do I add a the epel7 tags?

The following comment has been added to the python-pycxx-7.1.3-5.el7 update:

bodhi - 2019-12-24 07:04:49.655106 (karma: 0)
FEDORA-EPEL-2019-476f0d3c08 ejected from the push because "Cannot find relevant 
tag for python-pycxx-7.1.3-5.el7.  None of ['epel7', 'epel7-pending', 
'epel7-override'] are in ['dist-6E-epel-testing', 'epel7-testing', 
'dist-5E-epel-testing', 'f27-modular-updates-testing', 
'f30-modular-updates-testing', 'f30-container-updates-testing', 
'f30-flatpak-updates-testing', 'f28-modular-updates-testing', 
'f28-container-updates-testing', 'epel8-testing', 
'f31-modular-updates-testing', 'f32-container-updates-testing', 
'f31-container-updates-testing', 'f31-flatpak-updates-testing', 
'f29-modular-updates-testing', 'f29-container-updates-testing', 
'f29-flatpak-updates-testing', 'f22-updates-testing', 'f21-updates-testing', 
'f25-updates-testing', 'f24-updates-testing', 'f23-updates-testing', 
'f26-updates-testing', 'f27-updates-testing', 'f30-updates-testing', 
'f28-updates-testing', 'f31-updates-testing', 'f32-updates-testing', 
'f29-updates-testing', 'epel8-modular-updates-testing']."

 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-476f0d3c08

Barry
___
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: Qt 5.14 update plans?

[Barry Scott]

> On 13 Dec 2019, at 02:04, Richard Shaw  wrote:
> 
> Looks like Qt just released 5.14, I believe this officially supports Python 
> 3.8? So it would probably be a good idea to update Rawhide sooner rather than 
> later.
> 
> Rex, I'm willing to help coordinate/perform builds. 

Christian Tismer has been on the python dev list looking for help to fix a ref 
count leak in PySide with python3.8.

Not sure if that is resolved yet.

Barry



> 
> Thanks,
> Richard
> ___
> 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

fedpkg update - Could not generate update request for f31

[Barry Scott]

For python-pycxx I have been working on an update.
The builds for f29, f30 and f31 all all good done on 2019-07-08.

I can use fedpkg update for f29 and f30.
But get this for master (aka f31?) when I ran it today.

$ fedpkg switch-branch master
$ fedpkg update
Could not execute update: Could not generate update request: Cannot find 
release associated with build: python-pycxx-7.1.3-1.fc31, tags: ['f31']

I guess there is something I need to understand/fix to get this to update.

Barry

___
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: Broken modules on rawhide

[Barry Scott]

I see the same messages and its from a mock build.
How does this relate to upgrades? 

Barry

> On 27 Feb 2019, at 11:30, Lukas Ruzicka  wrote:
> 
> Why people disable the repo, I do not know. I might have a slight notion. 
> 
> However, you cannot upgrade from Fedora 29 to Fedora 30 with Modular 
> repositories allowed. It fails with an error similar to what Mirek has 
> reported. Disabling modular repositories fixed the problem and an upgrade was 
> possible, but I see this as quite a serious issue and if it is not fixed, I 
> will definitely report this as a blocker. 
> 
> I do not know, where the problem lies, whether the modules have not been 
> built yet or something, but I would definitely expect that in time of 
> Branching, things like that would have been solved. Otherwise, people will 
> not want to get into problems like this and they might think twice about 
> modular content.
> 
> 
> 
> On Wed, Feb 27, 2019 at 11:37 AM Miro Hrončok  > wrote:
> On 27. 02. 19 11:09, Igor Gnatenko wrote:
> > I think those messages are just informational, because nothing uses those 
> > modules to build packages..  or am I wrong?
> 
> It aborts the build.
> 
> ---
> 
> Modular dependency problems with Defaults:
> 
>   Problem 1: conflicting requests
>- nothing provides module(platform:f30) needed by module 
> avocado:stable:3020190213205848:a5b0195c-0.x86_64
>   Problem 2: conflicting requests
>- nothing provides module(platform:f30) needed by module 
> bat:latest:3020190214090936:e50d0d19-0.x86_64
> ...
>   Problem 12: conflicting requests
>- nothing provides module(platform:f30) needed by module 
> stratis:1:20181215204600:a5b0195c-0.x86_64
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>File "/usr/bin/dnf", line 58, in 
>  main.user_main(sys.argv[1:], exit_code=True)
>File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 193, in 
> user_main
>  errcode = main(args)
>File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main
>  return _main(base, args, cli_class, option_parser_class)
>File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 99, in _main
>  return cli_run(cli, base)
>File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 115, in 
> cli_run
>  cli.run()
>File "/usr/lib/python3.7/site-packages/dnf/cli/cli.py", line 1108, in run
>  return self.command.run()
>File "/usr/lib/python3.7/site-packages/dnf/cli/commands/install.py", line 
> 97, 
> in run
>  module_debsolv_errors))
>File "/usr/lib/python3.7/site-packages/dnf/module/module_base.py", line 
> 604, 
> in format_modular_solver_errors
>  msg = dnf.util._format_resolve_problems(errors)
>File "/usr/lib/python3.7/site-packages/dnf/util.py", line 384, in 
> _format_resolve_problems
>  msg += "\n  - ".join(rs)
> TypeError: sequence item 0: expected str instance, list found
> 
> Could not execute mockbuild: Failed to execute command.
> 
> ---
> 
> Is this a dnf bug?
> 
> -- 
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> 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 
> 
> 
> 
> -- 
> LUKÁŠ RŮŽIČKA
> FEDORA QE, RHCE
> Red Hat 
> 
>  
> Purkyňova 115
> 612 45 Brno - Královo Pole
> lruzi...@redhat.com    
> 
>   
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED. 
> ___
> 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

Self introduction: Barry Scott

[Barry Scott]

I have become the new maintainer for the pysvn package on Fedora.

I am the upstream developer for a number of projects including:
* pysvn - https://pysvn.sourceforge.io/
* pycxx - http://cxx.sourceforge.net/
* Barry's Emacs - http://barrys-emacs.org/
* SCM workbench - http://scm-workbench.barrys-emacs.org/

These days I tend to develop in python and C++ using PyQt for GUI needs.
The above projects work on Unix, macOS and Windows.

I have been using Fedora since FC4 and maybe before,
too long ago to remember.

I would also like to volunteer to be a co-maintainer of
python-pycxx.

My first task will be to update pysvn to its 1.9.9 release
but that requires pycxx to be updated to its 7.1.2 release
to pick up a needed fix.

I have a review up for the changes to python-pycxx at
https://bugzilla.redhat.com/show_bug.cgi?id=1685102

Barry
___
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: Retiring pysvn (was Re: Orphaning pysvn (and non-responsive maintainer: ravenoak))

[Barry Scott]

> On 25 Feb 2019, at 13:07, Stephen Gallagher  wrote:
> 
> On Tue, Feb 19, 2019 at 1:59 PM Barry Scott  wrote:
> 
>> Just heard about this. I'm the author of pysvn.
>> 
>> I'd be willing to maintain the fedora package of
>> pysvn. What do you need me to do?
>> 
>> I am an active user and developer on Fedora and I create and maintain
>> a numbers of RPMs in my work and personal projects.
>> 
> 
> Thanks for taking this over, Barry! I'll get you added as an admin on
> the pysvn package immediately. I see someone (Kevin?) sponsored you as
> a packager already, so that's good.
> 
> I need you to go to https://src.fedoraproject.org/rpms/pysvn and log
> out, then back in. That will update your FAS account with dist-git
> Pagure and I'll be able to make you an admin on that project. Once
> you've done that, please let me know.
> 

Done. Logged  in then out.

Barry
___
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: Retiring pysvn (was Re: Orphaning pysvn (and non-responsive maintainer: ravenoak))

[Barry Scott]

Sorry this was supposed to go only to Kevin.

Barry
___
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: Retiring pysvn (was Re: Orphaning pysvn (and non-responsive maintainer: ravenoak))

[Barry Scott]

> On 18 Feb 2019, at 18:08, Kevin Fenzi  wrote:
> 
> On 2/15/19 5:56 AM, Barry Scott wrote:
>> 
>> 
>>> On 13 Feb 2019, at 13:52, Stephen Gallagher  wrote:
>>> 
>>> On Tue, Feb 5, 2019 at 10:01 AM Stephen Gallagher  
>>> wrote:
>>>> 
>>>> I've been maintaining this for several years since the main admin
>>>> (ravenoak) vanished from Fedora. I don't use it anymore (and most of
>>>> the world has long since switched to git...) and it has yet again
>>>> failed to rebuild during the mass rebuild.
>>>> 
>>>> I'm initiating the Non-Responsive Maintainer process for ravenoak so
>>>> the main admin will be cleared. If anyone wants to take it over, I'll
>>>> happily make them a comaintainer on request.
>>> 
>>> No one seems to be jumping at taking this over, so I'm probably going
>>> to move towards retiring this package before F30 Beta Freeze. It's
>>> currently only used by three packages that I can find:
>> 
>> 
>> Just heard about this. I'm the author of pysvn.
>> 
>> I'd be willing to maintain the fedora package of
>> pysvn. What do you need me to do?
>> 
>> I am an active user and developer on Fedora and I create and maintain
>> a numbers of RPMs in my work and personal projects.
>> 
>> Barry
> 
> Hey Barry. Contact me off list and I can help you get setup.
> 
> You will need a fas account ( https://admin.fedoraproject.org/accounts )
> and take a look at

I already have a fas account username: barryascott

> 
> https://fedoraproject.org/wiki/Join_the_package_collection_maintainers 
> <https://fedoraproject.org/wiki/Join_the_package_collection_maintainers>

I have a bugzilla account under ba...@barrys-emacs.org 
<mailto:ba...@barrys-emacs.org> and can se
the fas login.

> 
> but of course since the package already exists a lot of this will be
> short circuted.

I can start by doing the work to update pysvn to the latest version
using the instruction in the Wiki.

It might be the weekend before I have time to do this.

Do you need to add me to the "fedora packager group"
or do I use the fedpkg clone -a until my first commit is reviewed to
make sure I keep up the standards?

> 
> Thanks so much for taking this on!

No problem.

Barry

> 
> kevin
> 
> ___
> 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: Retiring pysvn (was Re: Orphaning pysvn (and non-responsive maintainer: ravenoak))

[Barry Scott]

> On 13 Feb 2019, at 13:52, Stephen Gallagher  wrote:
> 
> On Tue, Feb 5, 2019 at 10:01 AM Stephen Gallagher  wrote:
>> 
>> I've been maintaining this for several years since the main admin
>> (ravenoak) vanished from Fedora. I don't use it anymore (and most of
>> the world has long since switched to git...) and it has yet again
>> failed to rebuild during the mass rebuild.
>> 
>> I'm initiating the Non-Responsive Maintainer process for ravenoak so
>> the main admin will be cleared. If anyone wants to take it over, I'll
>> happily make them a comaintainer on request.
> 
> No one seems to be jumping at taking this over, so I'm probably going
> to move towards retiring this package before F30 Beta Freeze. It's
> currently only used by three packages that I can find:


Just heard about this. I'm the author of pysvn.

I'd be willing to maintain the fedora package of
pysvn. What do you need me to do?

I am an active user and developer on Fedora and I create and maintain
a numbers of RPMs in my work and personal projects.

Barry




> 
> ReviewBoard (optional dependency for SVN support)
> rabbitvcs
> pyvcs
> 
> I'm the owner of the first one and I'm now CCing the owners of the
> other two, in case they want to take it over.
> ___
> 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

GitPython update blocked by rpkg - how can this be resolved?

[Barry Scott]

In this bug

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

It is implied that rpkg has an unspecified problem with GitPython 2.0.

This is preventing the maintainer from updating to the any GitPython 2 
release.

I'd like to know if there is in fact a problem with rpkg with GitPython 2.0.

If there is a problem it would be nice if the rpkg people could comment on the
difficult of supporting GitPython 2. The python2.6 support question I suspect
can be handled by version checking in any conflicting code.

It seems wrong that rpkg is blocking updating to the latest GitPython,
preventing user of GitPython getting the bugs fixes and (as far as I am aware)
backwards compatible improvements.

Barry
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Self Introduction: Barry Scott

[Barry Scott]

I am the maintainer for a number of open sources projects:

PyCXX - C++ interface to python
PySVN - pythonic OO API to Subversion
PySVN Workbench QUI interface to Subversion
MEINC_Installer - allows python code to packaged into
   executable for for Windows and Linux

I have been in software development for a long time on many OS
(Fedora, OpenBSD, FreeBSD, Windows and DEC-VMS) in a number
of languages (Python, C++, C, shell, Bliss32, Javascript).

I have worked on fixes for the Kernel, Xorg, Python, systemd,
KDE and KMyMoney.

I would like to see Workbench packaged for Fedora and I am
willing to be the Fedora Packager for Workbench.

Barry

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: ntp-4.2.6p5-11.fc19.src.rpm does not rpmbuild...

[Barry Scott]

On Fri 18 Oct 2013 17:59:31 Miroslav Lichvar wrote:
 On Fri, Oct 18, 2013 at 02:14:40PM +0100, Barry Scott wrote:
  On Thu 17 Oct 2013 17:56:57 Barry Scott wrote:
   I need to patch ntp for my uses. But I find that the src rpm will not
   build
   on F19.
   
   cd .  env
   PATH=/home/bscott/rpmbuild/BUILD/ntp-4.2.6p5/ntpd:/home/bscott/bin:/usr
   /loc al/bin:/bin:/usr/bin:/usr/local/sbin:/sbin:/usr/sbin autogen -L
   ../include --writable -Tagman1.tpl -bntpd ntpd-opts.def
   ice-9/psyntax.scm:1259:12: In procedure dobody:
 
   ice-9/psyntax.scm:1259:12: Syntax error:
 That looks like https://bugzilla.redhat.com/show_bug.cgi?id=958908.
 
 It's fixed in autogen-5.18-1.fc20. The F19 ntp spec includes a
 workaround touch ntpd/ntpd.1 util/ntp-keygen.1, which prevents
 autogen from rebuilding the man pages. If you are patching other
 autogen files in the ntp code, you'll need to update the autogen
 package or similarly touch the other man pages.

Thanks for the info.

I found the touch commands in the first F20 ntp SRPM and that got the rpmbuild 
working.

Barry

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: ntp-4.2.6p5-11.fc19.src.rpm does not rpmbuild...

[Barry Scott]

On Thu 17 Oct 2013 17:56:57 Barry Scott wrote:
 I need to patch ntp for my uses. But I find that the src rpm will not build
 on F19.
 
 
 cd .  env
 PATH=/home/bscott/rpmbuild/BUILD/ntp-4.2.6p5/ntpd:/home/bscott/bin:/usr/loc
 al/bin:/bin:/usr/bin:/usr/local/sbin:/sbin:/usr/sbin autogen -L ../include
 --writable -Tagman1.tpl -bntpd ntpd-opts.def ice-9/psyntax.scm:1259:12: In
 procedure dobody:
 ice-9/psyntax.scm:1259:12: Syntax error:
 /usr/share/autogen/agman1.tpl:187:6: definition in expression context, where
 definitions are not allowed, in form (define optname-from _^)
 Scheme evaluation error.  AutoGen ABEND-ing in template
 /usr/share/autogen/agman1.tpl on line 179
 Failing Guile command:  = = = = =
 
 (define opt-arg  )
 (define dis-name )
 (define opt-name )
 (define optname-from A-Z_^)
 (define optname-to   a-z--)
 (if (exist? preserve-case)
(begin
   (define optname-from _^)
   (define optname-to   --)
 )  )
 (if (exist? option-info)
 (string-append \n.PP\n (get option-info) \n) )
 
 =
 
 Is this being worked on or should I report a bug? I'd appreciate know what
 needs fixing.
 
 Barry

I see that some work was done for F20 (fixing date issues in %changelog). But 
it still fails the same way when I build the F20 SRPM on F19.

Barry

-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

ntp-4.2.6p5-11.fc19.src.rpm does not rpmbuild...

[Barry Scott]

I need to patch ntp for my uses. But I find that the src rpm will not build on 
F19.


cd .  env 
PATH=/home/bscott/rpmbuild/BUILD/ntp-4.2.6p5/ntpd:/home/bscott/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/sbin:/usr/sbin
 
autogen -L ../include --writable -Tagman1.tpl -bntpd ntpd-opts.def
ice-9/psyntax.scm:1259:12: In procedure dobody:
ice-9/psyntax.scm:1259:12: Syntax error:
/usr/share/autogen/agman1.tpl:187:6: definition in expression context, where 
definitions are not allowed, in form (define optname-from _^)
Scheme evaluation error.  AutoGen ABEND-ing in template
/usr/share/autogen/agman1.tpl on line 179
Failing Guile command:  = = = = =

(define opt-arg  )
(define dis-name )
(define opt-name )
(define optname-from A-Z_^)
(define optname-to   a-z--)
(if (exist? preserve-case)
   (begin
  (define optname-from _^)
  (define optname-to   --)
)  )
(if (exist? option-info)
(string-append \n.PP\n (get option-info) \n) )

=

Is this being worked on or should I report a bug? I'd appreciate know what 
needs fixing.

Barry


-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct