Re: Problem with updating powerdevil and libddcutil from F38

[Qiyu Yan]

Hi,

Just looked into the issue, the root cause is due to that 2 different 
updates are being built and pushed simultaneously in 2 different 
side-tags for 2 different sobumps, and one overrides another.


This is being be sorted out by following update:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-581f3d0e12

Following the instructions you should be able to update both ddcutil and 
powerdevil.


And question for development list: how can we avoiding this sort of 
things from happening again, like always setup buildroot override for 
pending (in testing) so-name change updates that it will propagate to 
other side-tags?


Cheers,
Qiyu


Related updates:
ddcutil: https://bodhi.fedoraproject.org/updates/FEDORA-2023-e4abfc9685
KDE: https://bodhi.fedoraproject.org/updates/FEDORA-2023-cae9bc16b8

在 2023/11/15 11:35, Jeffrey Walton 写道:

Hi Everyone,

I'm trying to upgrade a KDE-based workstation from F38 to F39. I
delayed the upgrade to ensure this workstation would remain available.
The delay allowed a problem with powerdevil and libddcutil to creep
in. It is causing `dnf update` and `dnf update --refresh` to fail.

I use only Fedora repos. I don't have any third party repos enabled,
like RPM Fusion.

I see a couple of other specific questions about powerdevil and
libddcutil from F38, but I don't see a clear path forward.

How do I fix the problem?

Thanks in advance.

-

$ sudo dnf update
Package manager: /bin/dnf
Fedora 38 - x86_64  8.7 MB/s |  83 MB 00:09
Fedora 38 OpenH264 (from Cisco) - x86_645.6 kB/s | 2.5 kB 00:00
Fedora Modular 38 - x86_64  2.3 MB/s | 2.8 MB 00:01
Fedora 38 - x86_64 - Updates9.8 MB/s |  35 MB 00:03
Fedora Modular 38 - x86_64 - Updates2.5 MB/s | 2.1 MB 00:00
Metadata cache created.
Last metadata expiration check: 0:00:04 ago on Wed 15 Nov 2023 06:12:54 AM EST.
Dependencies resolved.

  Problem: package powerdevil-5.27.9-2.fc38.x86_64 from @System
requires libddcutil.so.4()(64bit), but none of the providers can be
installed
   - cannot install both libddcutil-2.0.0-1.fc38.x86_64 from updates
and libddcutil-1.4.1-1.fc38.x86_64 from @System
   - cannot install both libddcutil-2.0.0-1.fc38.x86_64 from updates
and libddcutil-1.4.1-1.fc38.x86_64 from fedora
   - cannot install the best update candidate for package
libddcutil-1.4.1-1.fc38.x86_64
   - problem with installed package powerdevil-5.27.9-2.fc38.x86_64

  PackageArchitecture   VersionRepository   Size

Skipping packages with conflicts:
(add '--best --allowerasing' to command line to force their upgrade):
  libddcutil x86_64 2.0.0-1.fc38   updates 319 k

Transaction Summary

Skip  1 Package

$ sudo dnf update --best --allowerasing
Fedora 38 - x86_64   11 MB/s |  83 MB 00:07
Fedora 38 OpenH264 (from Cisco) - x86_641.4 kB/s | 2.5 kB 00:01
Fedora Modular 38 - x86_64  3.4 MB/s | 2.8 MB 00:00
Fedora 38 - x86_64 - Updates4.0 MB/s |  35 MB 00:08
Fedora Modular 38 - x86_64 - Updates1.8 MB/s | 2.1 MB 00:01
Error:
  Problem: The operation would result in removing the following
protected packages: plasma-desktop
(try to add '--skip-broken' to skip uninstallable packages)

$ sudo dnf update --best --allowerasing --skip-broken
Last metadata expiration check: 0:00:24 ago on Wed 15 Nov 2023 06:14:00 AM EST.
Error:
  Problem: The operation would result in removing the following
protected packages: plasma-desktop
___
users mailing list -- us...@lists.fedoraproject.org
To unsubscribe send an email to users-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/us...@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: Second call for rebuilding powerdevil and call for help from provenpackagers

[Qiyu Yan]

Hi all,

It is nearly a full month since last mail. And seems that koji has 
recycled the side tags due to inactivity. I re-created them:


 * f40-build-side-76474
 * f39-build-side-76476
 * f38-build-side-76478

Seems that I don't have the permission to push to powerdevil and rebuild 
it so maybe any provenpackagers can help?


Cheers,
Qiyu

在 2023/9/29 14:04, Qiyu Yan 写道:

Hi all,

I am planning to update package ddcutil to latest upstream release 
2.0.0. This will introduce a soname bump for libddcutil.so from 
libddcutil.4 to libddcutil.5. I checked that the only affected package 
due to this update will be powerdevil.


dnf repoquery --whatrequires "libddcutil.so.4()(64bit)" --release=40
...
powerdevil-0:5.27.8-1.fc40.x86_64

I have built ddcutil in following side-tags:

 * f38-build-side-74742
 * f39-build-side-74740
 * f40-build-side-74738

If possible, please built powerdevil in those side-tags that we can 
push the update together.


Cheers,
Qiyu
___
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

Update for ddcutil and for dependent package (powerdevil)

[Qiyu Yan]

Hi all,

I am planning to update package ddcutil to latest upstream release 
2.0.0. This will introduce a soname bump for libddcutil.so from 
libddcutil.4 to libddcutil.5. I checked that the only affected package 
due to this update will be powerdevil.


dnf repoquery --whatrequires "libddcutil.so.4()(64bit)" --release=40
...
powerdevil-0:5.27.8-1.fc40.x86_64

I have built ddcutil in following side-tags:

 * f38-build-side-74742
 * f39-build-side-74740
 * f40-build-side-74738

If possible, please built powerdevil in those side-tags that we can push 
the update together.


Cheers,
Qiyu
___
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: checksec: Problem: conflicting requests in s390x

[Qiyu Yan]

Sorry my mistake for not using full path, should be fixed now

Jun Aruga (he / him)  于 2023年9月8日周五 下午4:53写道：

> Hi,
> I am running the scratch build for rpms/ruby [1] rawhide branch right
> now, and I see the following error in the root.log on only s390x CPU
> architecture. Do you know what's wrong?
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=105910607
>
> s390x:
> https://kojipkgs.fedoraproject.org//work/tasks/753/105910753/root.log
> DEBUG util.py:442:  No matches found for the following disable plugin
> patterns: local, spacewalk, versionlock
> DEBUG util.py:442:  Error:
> DEBUG util.py:442:   Problem: conflicting requests
> DEBUG util.py:442:- nothing provides nm needed by
> checksec-2.6.0-5.fc40.noarch from build
> DEBUG util.py:442:- nothing provides python3.12dist(unicorn) >=
> 1.0.2~rc1 needed by python3-pwntools-4.9.0-4.fc39.noarch from build
>
> [1] https://src.fedoraproject.org/rpms/ruby
>
> --
> Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
> See  for
> the timezone.
> ___
> 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: Dropping of sshd.socket unit

[Qiyu Yan]

Just a question, do we have any mechanism to migrate users from 
sshd.socket to sshd.service? Otherwise someone may suddenly lose access 
to their headless systems after an upgrade.


在 2023/8/3 10:29, Dmitry Belyavskiy 写道:

Dear colleagues,

I've pushed a fresh build of OpenSSH to rawhide.
We decided to drop the sshd.socket unit from rawhide. We don't think
it's worth going through the changes process, but would like to
provide a heads-up.

See the details in https://bugzilla.redhat.com/show_bug.cgi?id=2025716.


___
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

Orphaned Onboard

[Qiyu Yan]

Hi all,

I've orphaned the Onboard package. I stopped using it personally and don't have 
enough time to handle some bug report.

If anyone want to take it please do so.

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

Need help with bodhi pushing failure

[Qiyu Yan]

Hi,

I encountered a pushing failure after editing a update from side-tag,
bodhi says 

FEDORA-2022-a0a90518a0 ejected from the push because "Cannot find
relevant tag for fcitx5-5.0.17-1.fc36. None of ['f36-build-side-53961']
are in [... lot of tags ...]

Related update is
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a0a90518a0

Could anyone help me pushing this update to testing/stable?

Cheers,
Qiyu

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12
About: https://fedoraproject.org/wiki/User:Yanqiyu






signature.asc
Description: This is a digitally signed message part
___
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

fcitx5-qt was missing from a QT5 update

[Qiyu Yan]

Hi Jan Grulich, 

Seems that fcitx5-qt was missing from from a recent qt5 update [1]. I
have noticed that and rebuilt it in your side-tag [2]. I think we
should add that build into your bodhi update to avoid any conflict in
stable repo, but I don't have the permission to do so, could you (or
any provenpackager) do that for me.

Thanks!

Cheers,
Qiyu Yan

[1]: https://bodhi.fedoraproject.org/updates/FEDORA-2022-26f40bcde1
[2]: https://koji.fedoraproject.org/koji/taskinfo?taskID=84626449
-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12
About: https://fedoraproject.org/wiki/User:Yanqiyu






signature.asc
Description: This is a digitally signed message part
___
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: Updates failed to push, may need manual operation from releng

[Qiyu Yan]

Thanks, I added a comment in https://pagure.io/releng/issue/10590 hope
this will be fixed then.

Ankur Sinha  于2022年1月28日周五 20:54写道：
>
> On Fri, Jan 28, 2022 20:43:12 +0800, Qiyu Yan wrote:
> > Hi,
> >
> > One of my package update:
> > https://bodhi.fedoraproject.org/updates/FEDORA-2022-9e8da7bd9f failed
> > to push to stable, error message is "FEDORA-2022-9e8da7bd9f ejected
> > from the push because "Cannot find relevant tag for
> > fcitx5-qt-5.0.9-4.fc35. None of ['f35-updates-testing',
> > 'f35-updates-pending'] are in ...(a lot tags)"
> >
> > May be manual fixing is needed from releng?
>
> Seems to be affecting a few packages. I've filed a ticket here for mine,
> so probably best to file one for yours there too:
> https://pagure.io/releng/issue/10601
>
> --
> Thanks,
> Regards,
> Ankur Sinha "FranciscoD" (He / Him / His) | 
> https://fedoraproject.org/wiki/User:Ankursinha
> Time zone: Europe/London
> ___
> 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

Updates failed to push, may need manual operation from releng

[Qiyu Yan]

Hi,

One of my package update:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-9e8da7bd9f failed
to push to stable, error message is "FEDORA-2022-9e8da7bd9f ejected
from the push because "Cannot find relevant tag for
fcitx5-qt-5.0.9-4.fc35. None of ['f35-updates-testing',
'f35-updates-pending'] are in ...(a lot tags)"

May be manual fixing is needed from releng?

Regards,
Qiyu Yan
___
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: A way to request/vote for packages to add next to Fedora Linux?

[Qiyu Yan]

在 2021-11-19星期五的 05:32 +，Reon Beon via devel写道：
> Video2X would be a nice add.
Not really, see https://github.com/k4yt3x/video2x .
It seems that Video2X depends on ffmpeg, which is only available in
rpmfusion. You may ask in rpmfusion list to see if anyone is interested
to package Video2X.
> ___
> 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

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12
About: https://fedoraproject.org/wiki/User:Yanqiyu






signature.asc
Description: This is a digitally signed message part
___
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

Need help pushing updates to bodhi (tagging problem)

[Qiyu Yan]

Hi all,

Yesterday I updated some fcitx5 related packages for f34 and f35, they
are built in side-tags. But a bug in my scripts causes one package
(fcitx5-mozc) did not build. Before I realized this, I have already
pushed the update in bodhi. Then I manually built it in side-tags, and
updated bodhi update manually (by using "edit" and the refersh
button). Then since those side-tags will not be used anymore, I
removed them.

Today I am getting errors from bodhi saying "Cannot find relevant tag
for ...", and the package is not tagged in koji. (I suppose bodhi
should have already tagged those package?)

My question is
 - What is the right way if you want add package to a side-tag update
 - How to resolve this problem

Retards,
Qiyu Yan

---
related updates:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-5616170e50
https://bodhi.fedoraproject.org/updates/FEDORA-2021-eaf29d8a38
___
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: FF builds

[Qiyu Yan]

在 2021-09-09星期四的 02:49 +，Bojan Smojver via devel写道：
>  Just being devil's advocate for a second here... 
>  
>  Two days to build FF in koji? Has it gotten that big or are the
> builds that slow? 
It should not be that slow, if you look at build.log you can see
```
... timed out waiting for test to complete ...
```
Seems that some bugs in checks block the build to finish or fail for
long time.
>  
>   :-) 
>  
> -- 
> Bojan
> ___
> 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

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12
About: https://fedoraproject.org/wiki/User:Yanqiyu






signature.asc
Description: This is a digitally signed message part
___
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: Self Introduction: Xiaofeng, FAS: wasphin

[Qiyu Yan]

在 2021-06-01星期二的 16:18 +0800，xiaofeng写道：
> Hi, all,
> 
> My name is Xiaofeng, I am using Fedora for the first time since Fedora
> 13. Currently I work on RHEL like distributions for C++ development, I
> am willing to join the fedora packager group, especially the epel
> group.
Welcome! You can start with
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
> 
> By now, I want to co-maintain the qt-creator for epel8, it does not
> work since the llvm upgrade to 11, 
Is llvm 11 available in RHEL8? IIRC, it's not the case. Or you compiled
and installed it by yourself? Since llvm is provided by RedHat in
RHEL8, qt-creator in epel should be compiled against the llvm in RHEL8.
And it will and should break when you update major llvm version
yourself.

It can be hard to fix from epel side, but a copr may help...by
rebuilding llvm 11 and rebuild everything which depends on llvm.
> I am really appreciated if someone can sponsor me, thanks.
> 

> Thanks and regards.
> Xiaofeng
> 
> ___
> 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

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12
About: https://fedoraproject.org/wiki/User:Yanqiyu






signature.asc
Description: This is a digitally signed message part
___
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: RPM name collisions

[Qiyu Yan]

在 2021-05-05星期三的 07:44 +0200，Dan Čermák写道：
> przemek klosowski via devel  writes:
> 
> > Is that something we need to worry about? I couldn't think of any new
> > rules to impose on repositories, but maybe dnf should have more
> > explicit 
> > warnings when it sees multiple versions of the same package, or at
> > least 
> > a way to show such versions.
> 
> Or how about teaching dnf that only certain repositories are allowed to
> be used for updates (with an allowedlist for exceptions)? Then
> microsoft
> or any other third party repo could put hello-5000-1 into their repo
> and
> it could never compromise your system, as dnf would not consider the
> 3rd
> party repo a valid update repo for a base system package.
> 
> That would require dnf to track where it got the package from though
> and I am not sure if it does that at the moment?
This reminds me of an idea named Vendor Change from Zypper of openSUSE
https://en.opensuse.org/SDB:Vendor_change_update
This approach seems to solve our problems here? 
> 
> 
> Cheers,
> 
> Dan
> ___
> 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

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12
About: https://fedoraproject.org/wiki/User:Yanqiyu






signature.asc
Description: This is a digitally signed message part
___
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: New RPM submission

[Qiyu Yan]

在 2021-04-29星期四的 13:25 +0100，Joan Moreau via devel写道：
> Thank you
> Concretely, how to "find a sponsor" ?
FYI:
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group


-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12






signature.asc
Description: This is a digitally signed message part
___
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: Fedora-Legal-README.txt in installation media outdated?

[Qiyu Yan]

在 2021-04-28星期三的 13:40 -0700，Kevin Fenzi写道：
> On Wed, Apr 28, 2021 at 02:12:15PM +0800, Qiyu Yan wrote:
> > If you download a Fedora 34 live iso at https://getfedora.org/
> > with filename: Fedora-Workstation-Live-x86_64-34-1.2.iso
> > 
> > Mount it and see Fedora-Legal-README.txt in the image. There are
> > many
> > Fedora 31 things show up, should this file be updated on each
> > release
> > cycle?
> > 
> > (Maybe not, unless someone like me mounts the iso file by mistake,
> > and
> > check the Legal file by curiosity LOL)
> 
> It is. It's updated in the prep of fedora-release package, but
> perhaps
> something went wrong and the image didn't get the updated version. :(
> 
> Can you file a bug on fedora-release about this and we can try and
> track
> it down. If someone would like to investigate, please do. ;) 
https://bugzilla.redhat.com/show_bug.cgi?id=1954896
done.
> 
> kevin
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-
> US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject
> .org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-
> infrastructure

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12






signature.asc
Description: This is a digitally signed message part
___
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

Fedora-Legal-README.txt in installation media outdated?

[Qiyu Yan]

If you download a Fedora 34 live iso at https://getfedora.org/
with filename: Fedora-Workstation-Live-x86_64-34-1.2.iso

Mount it and see Fedora-Legal-README.txt in the image. There are many
Fedora 31 things show up, should this file be updated on each release
cycle?

(Maybe not, unless someone like me mounts the iso file by mistake, and
check the Legal file by curiosity LOL)

--
Part of the file:
The accompanying Fedora 31 release includes copyrighted
software that is licensed under the GNU General Public License and
other licenses. You may obtain the complete machine-readable source
code corresponding to portions of this release by sending a check or
money order in the amount of US $5.00 to:

VP, Legal - Products & Technologies | Red Hat, Inc. | 100 East Davie
Street | Raleigh, NC 27601 USA

Please write "source for Fedora 31" in the memo line of your payment.

You may also access a copy of this source code at:
http://dl.fedoraproject.org/pub/fedora/linux/releases/31/Everything/source/

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12






signature.asc
Description: This is a digitally signed message part
___
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: Gnome BZ untouched for years #1414539

[Qiyu Yan]

在 2021-04-26星期一的 08:17 +0200，Michal Schorm写道：
> How many more years can I expect it will take to resolve or at least
> seriously examine this following BZ?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1414539

Just gone through the thread and it seems to be a selinux problem.
Maybe the BZ should be moved to selinux-policy or udisk2?

-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12






signature.asc
Description: This is a digitally signed message part
___
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: F35 Change: CompilerPolicy Change (System-Wide Change proposal)

[Qiyu Yan]

在 2021-04-23星期五的 11:18 -0400，Ben Cotton写道：
> The policy update will also recommend that packagers use standardized
> macro names when using conditional options to control the compiler
> choice:
> 
> %bcond_with toolchain_clang
> %bcond_with toolchain_gcc
replacing current 
%global toolchain clang
or
%global toolchain gcc

described at
https://src.fedoraproject.org/rpms/redhat-rpm-config//blob/rawhide/f/macros#_41
?
-- 
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12






signature.asc
Description: This is a digitally signed message part
___
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: Spaces in tarball directory name

[Qiyu Yan]

在 2021-04-18星期日的 19:20 +0200，Vitaly Zaitsev via devel写道：
> Hello.
> 
> I have an upstream tarball with the "Foo Bar-1.0.0" directory name.
> Is 
> it possible to use spaces in the %autosetup/%setup macros?
> 
> Trying: %autosetup -n "Foo Bar-%{version}", but got an error:
What if %autosetup -n Foo\ Bar-%{version} ?
> 
> Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.eAQck5
> + umask 022
> + cd /home/vitaly/rpmbuild/BUILD
> + cd /home/vitaly/rpmbuild/BUILD
> + rm -rf 'Foo  -q
> '
> + /usr/bin/gzip -dc /home/vitaly/rpmbuild/SOURCES/Foo.Bar-
> 1.0.0.tar.gz
> + /usr/bin/tar -xof -
> + STATUS=0
> + '[' 0 -ne 0 ']'
> + cd 'Foo  -q
> '
> /var/tmp/rpm-tmp.eAQck5: line 41: cd: $'Foo  -q\n': No such file or 
> directory
> error: Bad exit status from /var/tmp/rpm-tmp.eAQck5 (%prep)
> 
> -- 
> 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.fedoraproje
> ct.org
> Do not reply to spam on the list, report it:
> https://pagure.io/fedora-infrastructure



signature.asc
Description: This is a digitally signed message part
___
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

[EPEL-devel] Re: Getting conman into EPEL8

[Qiyu Yan]

在 2021-04-13星期二的 14:15 +，treyd...@gmail.com写道：
> It appears like RHEL8 dropped conman RPMs but they do exist in Fedora
> and appear to be receiving updates.  I found a wiki page that said to
> contact the maintainers via email but I was unable to find the emails
> associated with the maintainers so I opened a bugzilla but wasn't
You don't need to find the mail address, fedora already has mail alias 
package-ow...@fedoraproject.org or
package-maintain...@fedoraproject.org to contact maintainers.
> sure if I did this bugzilla in appropriate place:
> https://bugzilla.redhat.com/show_bug.cgi?id=1947480
> 
> I'd be happy to become the maintainer of conman for EPEL8 if that would
> help get conman RPMs into EPEL8.  Any pointers on how to go about
> getting conman into EPEL8 would be appreciated, in case the current
> approach I took is incorrect.
> 
> Thanks,
> - Trey
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-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/epel-
> de...@lists.fedoraproject.org
> Do not reply to spam on the list, report it: https://pagure.io/fedora-
> infrastructure



signature.asc
Description: This is a digitally signed message part


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

Re: F34 xscreensaver

[Qiyu Yan]

在 2021-04-10星期六的 10:25 +0200，Łukasz Posadowski写道：
> 
> Hi.
> 
> I have an old laptop with a minimal graphical interface, which
> includes Xscreensaver. It was updated to version 6 and I have a
> little problem. I'm using a little script to force screen lock:
> 
> sudo date --set='+1 hour'
> sleep 5
> sudo date --set='-1 hour'
> 
> It was working fine with Xscrensaver 5.x, but not now. Is there a
> way to force a screen lock with Xscreensaver 6? 
I personally don't use xscreensaver, but with some searching on the web
I found that xscreensaver-command --lock may do your work?

refs: https://www.jwz.org/xscreensaver/man3.html
> 
> thanks
> 
> -- 
> Łukasz Posadowski
> 
> ___
> 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



signature.asc
Description: This is a digitally signed message part


smime.p7s
Description: S/MIME cryptographic signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Request to include package: coreboot

[Qiyu Yan]

romulasry via devel  于2021年3月5日周五 下午2:04写道：
>
> Preferribly a git version with all packages would be nice
>
> Hope this is the right place to put this, if not what list, thanks in advance.
> https://www.coreboot.org/
Is coreboot intended to be shipped as part of distribution? I think it
should be something that being shipped with a hardware.
>
>
> Sent with ProtonMail Secure Email.
>
> ___
> 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: Packaging question: Rebuild initramfs after adding to dracut.conf.d

[Qiyu Yan]

Eric Edens via devel  于 2021年2月4日周四
上午10:54写道：

> I'm working on a package that adds a configuration to dracut.conf.d. [1]
> To rebuild initramfs, upstream's spec file calls `dracut --force` in
> `%post` . [2]
>
> Questions:
> - Is it recommended that the RPM updates initramfs?

- If so, what's the recommended method?
>
I think this should be taken care of by kernel package via
%transfiletriggerin and transfiletriggerpostun, since there can be multiple
initramfs to be updated.

>
> As background, the RPM will be used in the Google Cloud kickstart [3]
> during image creation, but it will also be used to allow users to import
> existing installations to run on Google Cloud.
>
> What I've done so far:
> - Read through https://docs.fedoraproject.org/en-US/packaging-guidelines/
> - Search for example usages of `dracut`, `new-kernel-pkg`, and
> `installkernel` in http://src.fedoraproject.org/
>
> 1.
> https://github.com/GoogleCloudPlatform/guest-configs/blob/master/src/etc/dracut.conf.d/gce.conf
> 2.
> https://github.com/GoogleCloudPlatform/guest-configs/blob/master/packaging/google-compute-engine.spec#L82
> 3.
> https://pagure.io/fedora-kickstarts/blob/main/f/fedora-cloud-base-gcp.ks
> ___
> 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: Fedora 34 Change: Unify the GRUB configuration files location across all supported architectures (System-Wide Change proposal)

[Qiyu Yan]

Vitaly Zaitsev via devel 
于2020年12月31日周四 下午6:12写道：
>
> On 30.12.2020 20:53, Ben Cotton wrote:
> > This change makes the GRUB configuration files layout to be consistent
> > across all the supported architectures. Currently EFI is a special
> > case since the GRUB configuration file and environment variables block
> > are stored in the EFI System Partition (ESP) instead of the boot
> > partition (or `/boot` directory if no boot partition is used).
>
> Why not switch from the ancient GRUB2 to the modern systemd-boot?
iirc systemd-boot don't support legacy BIOS system.
>
> --
> 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 troubleshoot aarch64 and s390x?

[Qiyu Yan]

Richard Shaw  于2020年12月17日周四 下午9:34写道：
>
> I'm working on building the new openexr package but the unit tests are 
> failing but just on aarch64 and s390x.
And if having problems with s390x, https://linuxone.cloud.marist.edu/
provides a free s390x vps (at least last time I used its service)
>
> The aarch64 test instances are down due to the infra move and there are none 
> for s390x.
>
> What's the best way to work around this? An emulated aarch64 install of 
> Fedora?
>
> 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

Re: How to troubleshoot aarch64 and s390x?

[Qiyu Yan]

Richard Shaw  于2020年12月17日周四 下午9:34写道：
>
> I'm working on building the new openexr package but the unit tests are 
> failing but just on aarch64 and s390x.
>
> The aarch64 test instances are down due to the infra move and there are none 
> for s390x.
>
> What's the best way to work around this? An emulated aarch64 install of 
> Fedora?
I may use a raspberry pi for testing aarch64 applications, or if
downloading fails for some reason, maybe it could be possible to
download those files in advance and specify a local path?
>
> 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

Re: Lenovo portals for South America

[Qiyu Yan]

While this mail list is public itself. I hope lenovo will check on checkout or 
they may see abuse someday.
___
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: Can a bugzilla issue be locked because of spam?

[Qiyu Yan]

Fabio Valentini  于2020年8月31日周一 下午7:54写道：
> I'm getting *pretty annoyed* with a similar (but way worse) issue as well:
> https://bugzilla.redhat.com/show_bug.cgi?id=810049
>
> It's worse because there are way more spam comments and they get
> amplified by the mails to the package-review lists as well ...

Thanks to god they didn't spam to mailing list directly.

> I was told to just mark comments as spam and by "magic" those accounts
> will get banned.
> Thing is, new accounts get created and just keep on posting spam.

If tons of spam accounts are getting created continuously, then I think locking
bugs won't help. IMHO the only way that will help is ask RedHat to set
a more strict
anti-spam procedure when creating new accounts.

> The bug I linked had over 140 spam comments up until now, and like
> you, I tried to mark them as spam and remove the spammer's email
> addresses from the CC list, but to no avail.

Why the bots stick to several bugs rather than spamming randomly on
every bugs? Just
by design or something in those bugs triggered those bots?

>
> Fabio
> ___
> 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: Help needed with new pcl: cloudcompare FTBFS

[Qiyu Yan]

> Hello Rich, Orion.
> 
> I see you've managed to build pcl that was updated to 1.11 2 months ago but 
> only 
> built recently for Fedora 33+:
> 
> https://src.fedoraproject.org/rpms/pcl/commits/master
> 
> 
> cloudcompare now FTBFS:
> 
> 
> https://koschei.fedoraproject.org/package/cloudcompare?collection=f33
> 
> 
> In file included from /usr/include/pcl-1.11/pcl/pcl_macros.h:77,
>   from /usr/include/pcl-1.11/pcl/PCLPointCloud2.h:8,
>   from 
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/filters/../utils/PCLConv.h:30,
>   from 
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/filters/MLSSmoothingUpsampling.cpp:22:
> /usr/include/pcl-1.11/pcl/pcl_config.h:7:4: error: #error PCL requires C++14 
> or 
> above
>  7 |   #error PCL requires C++14 or above
>|^
> 
> 
> So I've attempted a trivial workaround:
> 
>  sed -i 's/-std=c++11/-std=c++14/' $(grep -rl -- '-std=c++11')
> 
> or
> 
>  sed -i 's/-std=c++11/-std=gnu++14/' $(grep -rl -- '-std=c++11')
> 
> However the error is now:
> 
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=49241500
> 
> 
> In file included from 
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:21:
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/my_point_types.h:34:12:
> 
> error: 'uint8_t' in namespace 'boost' does not name a type
> 34 | boost::uint8_t b;
>|^~~
> 
> 
> And:
> 
> 
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:
>  
> In member function 'pcl::PCLPointCloud2::Ptr cc2smReader::getColors() const':
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:275:21:
>  
> error: 'struct OnlyRGB' has no member named 'r'
>275 |pcl_cloud->at(i).r = static_cast(rgb[0]);
>| ^
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:276:21:
>  
> error: 'struct OnlyRGB' has no member named 'g'
>276 |pcl_cloud->at(i).g = static_cast(rgb[1]);
>| ^
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:277:21:
>  
> error: 'struct OnlyRGB' has no member named 'b'
>277 |pcl_cloud->at(i).b = static_cast(rgb[2]);
>|
In this case, looking into the code itself is a must, check if the code 
correctly defined OnlyRGB before those lines (and with this error, seems 
upstream code didn't). I think this is due to an upstream coding issue. Try to 
find the definition and move it to a right place.
> 
> 
> Any idea what needs to be changed and how? Note that my C++ skills are rusty 
> at 
> least. Thanks for help.
___
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: Help needed with new pcl: cloudcompare FTBFS

[Qiyu Yan]

Miro Hrončok  于2020年8月14日周五 下午6:09写道：
>
> Hello Rich, Orion.
>
> I see you've managed to build pcl that was updated to 1.11 2 months ago but 
> only
> built recently for Fedora 33+:
>
> https://src.fedoraproject.org/rpms/pcl/commits/master
>
>
> cloudcompare now FTBFS:
>
>
> https://koschei.fedoraproject.org/package/cloudcompare?collection=f33
>
>
> In file included from /usr/include/pcl-1.11/pcl/pcl_macros.h:77,
>   from /usr/include/pcl-1.11/pcl/PCLPointCloud2.h:8,
>   from
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/filters/../utils/PCLConv.h:30,
>   from
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/filters/MLSSmoothingUpsampling.cpp:22:
> /usr/include/pcl-1.11/pcl/pcl_config.h:7:4: error: #error PCL requires C++14 
> or
> above
>  7 |   #error PCL requires C++14 or above
>|^
>
>
> So I've attempted a trivial workaround:
>
>  sed -i 's/-std=c++11/-std=c++14/' $(grep -rl -- '-std=c++11')
>
> or
>
>  sed -i 's/-std=c++11/-std=gnu++14/' $(grep -rl -- '-std=c++11')
>
> However the error is now:
>
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=49241500
>
>
> In file included from
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:21:
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/my_point_types.h:34:12:
> error: 'uint8_t' in namespace 'boost' does not name a type
> 34 | boost::uint8_t b;
>|^~~
boost::uint8_t is defined in /usr/include/boost/cstdint.hpp, could you
check if the source file have includes boost/stdint.hpp
>
> And:
>
>
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:
> In member function 'pcl::PCLPointCloud2::Ptr cc2smReader::getColors() const':
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:275:21:
> error: 'struct OnlyRGB' has no member named 'r'
>275 |pcl_cloud->at(i).r = static_cast(rgb[0]);
>| ^
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:276:21:
> error: 'struct OnlyRGB' has no member named 'g'
>276 |pcl_cloud->at(i).g = static_cast(rgb[1]);
>| ^
> /builddir/build/BUILD/CloudCompare-2.9.1/plugins/qPCL/PclUtils/utils/cc2sm.cpp:277:21:
> error: 'struct OnlyRGB' has no member named 'b'
>277 |pcl_cloud->at(i).b = static_cast(rgb[2]);
>|
Don't know why, get error above fixed and see if this remains?
>
>
> Any idea what needs to be changed and how? Note that my C++ skills are rusty 
> at
> least. Thanks for help.
>
> --
> 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
___
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

Bringing fcitx5 to Fedora, and Review Swap

[Qiyu Yan]

Hello all,

I am going to bring fcitx5 to fedora, fcitx5 is the next generation
for fcitx and upstream decided to treat fcitx and fcitx5 as a
different project (different git repo, different file paths and names
and configuration files). So, like most other distro do, I think we
are going to treat fcitx5 as a different package.

So I opened several review requests at Bugzilla, overall there are 11
packages and you can see a block tree here:
https://bugzilla.redhat.com/buglist.cgi?bug_id=1868845_id_type=andblocked=tvp_id=11288407_dir=blocked

The review process should be:
Stage1: https://bugzilla.redhat.com/show_bug.cgi?id=1868845
Stage2: https://bugzilla.redhat.com/show_bug.cgi?id=1868846
Stage3: https://bugzilla.redhat.com/show_bug.cgi?id=1868847
  https://bugzilla.redhat.com/show_bug.cgi?id=1868848
  https://bugzilla.redhat.com/show_bug.cgi?id=1868849
  https://bugzilla.redhat.com/show_bug.cgi?id=1868851
  https://bugzilla.redhat.com/show_bug.cgi?id=1868854
  https://bugzilla.redhat.com/show_bug.cgi?id=1868861
Stage4: https://bugzilla.redhat.com/show_bug.cgi?id=1868853
  https://bugzilla.redhat.com/show_bug.cgi?id=1868857
  https://bugzilla.redhat.com/show_bug.cgi?id=1868850

And a copr for the whole thing can be found
https://copr.fedorainfracloud.org/coprs/yanqiyu/fcitx5 , this may help
when you are looking for built packages.

This is a lot work, take it freely, and I can do reviews in exchange.



-- 
Best regards,
Qiyu Yan
___
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

A few questions about rpmdev-bumpspec tool

[Qiyu Yan]

Hello all,

I have some problem with rpmdev-bumpspec recently.

In the latest version of rpmdevtools, rpmdev-bumpspec has changed to
use time+date in the changelog it generates[1], while the packaging
guidelines have not been updated accordingly[2], should the guideline
be updated to the rpmdev-bumpspec change?

I am packaging fcitx5 using forge macros, and upstream have never
tagged a version, in this case, I am packaging like this [3] (The
snapshot dates and git short commit hashesin changelog is manually
added). With this spec file, I noticed that when I try to use
rpmdev-bumpspec to generate a changelog, it will give things like this
[4].

You can see that, in case of using forge, rpmdev-bumpspec can't
include either snapshot dates nor git short commit hashes, will this
be fine (and we can ignore the warning from rpmlint when ran on the
built packages, and start the review process) or I should always
manually include snapshot dates and git commit hashes in the
changelog. Or I should wait for this change [5] to be done and ignore
all changelog things? (and submit for review then?)

Thanks.

[1]: https://pagure.io/rpmdevtools/c/d205ad9cfc4b7123acd573e028f8c4521ec79300
[2]: https://docs.fedoraproject.org/en-US/packaging-guidelines/#changelogs
[3]: https://github.com/karuboniru/fcitx5-fedora/blob/master/fcitx5/fcitx5.spec
[4]: 
https://github.com/karuboniru/fcitx5-fedora/blob/972fd2e2e84e6ca136a9c5f4f8ad20653cca3594/fcitx5/fcitx5.spec
[5]: 
https://fedoraproject.org/wiki/Changes/Patches_in_Forge_macros_-_Auto_macros_-_Detached_rpm_changelogs
--
And the snapshot dates generated on my machine and copr can be
different, I think this is related to time zone (I am in UTC+8), I
don't think it is a bug, but I hope this will be improved.
-- 
Best regards,
Qiyu Yan
___
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: Unable to login with FAS

[Qiyu Yan]

Scott Talbert  于2020年8月9日周日 下午10:30写道：
>
> There seems to be some sort of problem with FAS right now.  (I would have
> reported this to fedora-infrastructure Pagure, but I can't log in to
> Pagure.)
>
> When trying to log into Bodhi, I'm getting:
> 500 Internal Server Error
>
> Could not convert return value of the view callable function
> pyramid_fas_openid.view.verify_openid into a response object. The value
> returned was None. You may have forgotten to return a value from the view
> callable.
>
> When trying to log into Pagure, I'm getting:
> Strange state: failure
I had been facing this error for hours, and it seems to have fixed
now. Can you try again?
>
> Thanks,
> Scott
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Review exchange

[Qiyu Yan]

Qiyu Yan  于2020年7月28日周二 下午1:56写道：
>
> Hello all!
>
> I am trying to package a golang program to fedora and found that I
> need to bring those dependencies:
>
> - https://bugzilla.redhat.com/show_bug.cgi?id=1861185
> - https://bugzilla.redhat.com/show_bug.cgi?id=1861187
> - https://bugzilla.redhat.com/show_bug.cgi?id=1861188
> - https://bugzilla.redhat.com/show_bug.cgi?id=1861190

Above is done, and included into rawhide, and I need following
 - https://bugzilla.redhat.com/show_bug.cgi?id=1862660
to be reviewed to finish. Anyone interested in this?

Still, let me know if you need me to do some review in exchange!

>
> I think they will be trivial to review (go2rpm and fix all #FIXME
> parts), can someone help me?
>
> I can do reviews in exchange.
>
> --
> Best regards,
> Qiyu Yan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Review swaps

[Qiyu Yan]

Robert-André Mauchin  于2020年8月2日周日 上午1:47写道：
>
> On Saturday, 1 August 2020 05:07:52 CEST Qiyu Yan wrote:
> > Jerry James  于 2020年8月1日周六 上午5:24写道：
> >
> > > I need two packages reviewed to enable some optional functionality in
> > > the normaliz package.  The second depends on the first:
> > >
> > > antic: https://bugzilla.redhat.com/show_bug.cgi?id=1862615
> >
> > Done for this.
> >
> > > e-antic: https://bugzilla.redhat.com/show_bug.cgi?id=1862616
> >
> > Maybe we should wait the former one to be ready in rawhide, then this?
> >
>
> You can use the -L switch in fedora-review to install packages prior to
> testing. For example, you create a "deps" folder, and add bug 1862615 RPM
> results in it. Then you pass -L deps to fedora review:
>
> fedora-review -r fedora-rawhide-x86_64 -L deps theSRPM
This works, but due to the mass rebuild and the mirrors available for
me didn't get synced. Preparing the buildroot will take unreasonable
long time here, maybe letting others interested to continue.
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Review swaps

[Qiyu Yan]

Jerry James  于 2020年8月1日周六 上午5:24写道：

> I need two packages reviewed to enable some optional functionality in
> the normaliz package.  The second depends on the first:
>
> antic: https://bugzilla.redhat.com/show_bug.cgi?id=1862615

Done for this.

>
> e-antic: https://bugzilla.redhat.com/show_bug.cgi?id=1862616

Maybe we should wait the former one to be ready in rawhide, then this?

>
>
> Let me know what I can review for you in exchange.   Thanks,
> --
> Jerry James
> http://www.jamezone.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: Review exchange

[Qiyu Yan]

Robert-André Mauchin  于2020年7月29日周三 上午3:43写道：
>
> On Tuesday, 28 July 2020 07:56:52 CEST Qiyu Yan wrote:
> > Hello all!
> >
> > I am trying to package a golang program to fedora and found that I
> > need to bring those dependencies:
> >
> > - https://bugzilla.redhat.com/show_bug.cgi?id=1861185
> > - https://bugzilla.redhat.com/show_bug.cgi?id=1861187
> > - https://bugzilla.redhat.com/show_bug.cgi?id=1861188
> > - https://bugzilla.redhat.com/show_bug.cgi?id=1861190
> >
> > I think they will be trivial to review (go2rpm and fix all #FIXME
> > parts), can someone help me?
> >
> All good, approved.
> Please consider adding 'go-sig' as a maintainer once you request the packages.
> And add them to Koschei too.
Thanks, all done expect being to be added to go sig, and how do I add
those packages into go-sig package group in Koschei?
>
> Best regards,
>
> Robert-André
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Review exchange

[Qiyu Yan]

Hello all!

I am trying to package a golang program to fedora and found that I
need to bring those dependencies:

- https://bugzilla.redhat.com/show_bug.cgi?id=1861185
- https://bugzilla.redhat.com/show_bug.cgi?id=1861187
- https://bugzilla.redhat.com/show_bug.cgi?id=1861188
- https://bugzilla.redhat.com/show_bug.cgi?id=1861190

I think they will be trivial to review (go2rpm and fix all #FIXME
parts), can someone help me?

I can do reviews in exchange.

-- 
Best regards,
Qiyu Yan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora flatpaks on non-x86 architectures

[Qiyu Yan]

John M. Harris Jr  于 2020年7月26日周日 下午2:43写道：

> On Saturday, July 25, 2020 11:31:18 PM MST Qiyu Yan wrote:
> > John M. Harris Jr  于 2020年7月26日周日 下午2:25写道：
> >
> > > On Saturday, July 25, 2020 10:29:45 PM MST Qiyu Yan wrote:
> > > > But your advice to use dnf is not a good one. The thread is about the
> > >
> > > topic
> > >
> > > > of using silverblue, dnf won't apply here unless with fedora-toolbox
> and
> > > > using rpm-ostree to layering needs reboot and is not the
> best-practice.
> > >
> > > What does Silverblue use, if not `dnf`?
> >
> > rpm-ostree, see
> > https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started/
>
> Oh, I thought this was about Fedora. Looks like Silverblue is another
> distro?
> I wonder if it has its own mailing lists. I've seen some Silverblue stuff
> on
> the forums set up for Fedora.
>
It is fedora, but a different variant. It is based on atomic project, an
atomic variant fedora workstation.

>
> --
> John M. Harris, Jr.
>
> ___
> 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: Fedora flatpaks on non-x86 architectures

[Qiyu Yan]

John M. Harris Jr  于 2020年7月26日周日 下午2:25写道：

> On Saturday, July 25, 2020 10:29:45 PM MST Qiyu Yan wrote:
> > But your advice to use dnf is not a good one. The thread is about the
> topic
> > of using silverblue, dnf won't apply here unless with fedora-toolbox and
> > using rpm-ostree to layering needs reboot and is not the best-practice.
>
> What does Silverblue use, if not `dnf`?

rpm-ostree, see
https://docs.fedoraproject.org/en-US/fedora-silverblue/getting-started/

>
> --
> John M. Harris, Jr.
>
> ___
> 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: Fedora flatpaks on non-x86 architectures

[Qiyu Yan]

John M. Harris Jr  于 2020年7月26日周日 下午1:02写道：

> On Saturday, July 25, 2020 4:28:19 PM MST Erich Eickmeyer wrote:
> > On 7/25/2020 3:39 PM, John M. Harris Jr wrote:
> > > The solution is to run the following command:
> > >
> > > `dnf install $package`. This will install your arch's version of the
> > > package you're looking for.
> >
> > John,
> >
> > This is neither helpful, nor warranted. It is clear that you don't like
> > the direction that Fedora is going,
>
> What exactly do you mean by that? That's helpful, that's how you install a
> package for your arch. I don't have any issue with where Fedora is going,
> though I certainly do intend to weigh in on actual Changes, which this was
> not, to try to keep Fedora going in the right direction. Not every Change
> is
> good. Not every Change is bad.
>
> > so perhaps it's time that you left the project and stop commenting in the
> > mailing list.
>
> That's not very kind.. Please don't be so hostile with members of the
> Fedora
> community. There are people around here who may not take these sorts of
> comments as I do, and I'm pretty sure people would waste time trying to do
> CoC
> violation nonsense with you.
>
Yes... I think that response is not kind, which is not suitable in this
list. We should be kind to each other anyway.

But your advice to use dnf is not a good one. The thread is about the topic
of using silverblue, dnf won't apply here unless with fedora-toolbox and
using rpm-ostree to layering needs reboot and is not the best-practice.

>
> > Your needs and wants are completely different than the direction Fedora
> is
> > going and you are attempting to impede progress by nay-saying every
> single
> > change that comes across and then poo-pooing newer technologies such as
> > flatpak.
>
> I fail to see where there's anything about a Change in the email I
> responded
> to. I simply provided instructions for installing a package for the
> system's
> arch.
>
> > I suggest you move project that doesn't move as quickly so that you can
> > keep things the way you like it, such as Debian, or perhaps even Devuan
> > since you seem to have a disdain for systemd as well. Either way, you
> > need to stop posting to this list.
>
> I like that Fedora gets me the latest tech as soon as it's reasonably
> stable.
> That's one of the many reasons I'm involved in the Fedora project.
> Further, I
> have no issue with systemd doing its job, being an init system. My problem
> is
> when everything else gets thrown under the systemd name.
>
> > Your comment shows that you don't like flatpaks, and that's fine and you
> > can have that opinion, but you didn't need to respond at all.
>
> I don't understand what you mean by that. If I'm not mistaken, the
> question
> was how to install a Fedora package for the host arch.
>
> --
> John M. Harris, Jr.
>
> ___
> 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: Fedora flatpaks on non-x86 architectures

[Qiyu Yan]

John Doe  于2020年7月26日周日 上午10:47写道：
>
> > I don't have a machine of other than x86_64 so I can't test, but does this
> > mean fedora's flatpak source is totally unavailable on secondary arches? Or
> > I have any misunderstanding of flatpak image building?
>
> It looks like it, but it shouldnt be hard to add aarch64 and ppc64le, just a 
> matter of changing a config file, everything should build fine on either 
> arches.
>
> > And changing clusters for koji system is a work for infrastructure team,
> > maybe a issue at fedora-infrastructure is needed.
>
> I see, where exactly do I reach them? Is there a mailing list, you say 
> "issue", a bug tracker maybe?
https://pagure.io/fedora-infrastructure/issues
> ___
> 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: Fedora flatpaks on non-x86 architectures

[Qiyu Yan]

John Doe  于 2020年7月26日周日 上午3:23写道：

> Hello!
>
> I am looking for the place where Fedora flatpaks are built, as explained
> here: https://docs.fedoraproject.org/en-US/flatpak/concepts/#_oci_images
>
> I could find a koji task that builds one:
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1520683 - and there
> we can observe in orchestrator.log:
>
> 2020-06-04 10:16:48,929 platform:- -
> atomic_reactor.plugins.check_and_set_platforms - INFO - Checking koji
> target for platforms
> 2020-06-04 10:16:48,991 platform:- -
> atomic_reactor.plugins.check_and_set_platforms - INFO - Koji platforms are
> ['aarch64', 'armv7hl', 'i686', 'ppc64le', 's390x', 'x86_64']
> 2020-06-04 10:16:48,992 platform:- -
> atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found
> for platform 'armv7hl' in reactor config map, skipping
> 2020-06-04 10:16:48,992 platform:- -
> atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found
> for platform 'i686' in reactor config map, skipping
> 2020-06-04 10:16:48,992 platform:- -
> atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found
> for platform 'aarch64' in reactor config map, skipping
> 2020-06-04 10:16:48,992 platform:- -
> atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found
> for platform 'ppc64le' in reactor config map, skipping
> 2020-06-04 10:16:48,992 platform:- -
> atomic_reactor.plugins.check_and_set_platforms - WARNING - No cluster found
> for platform 's390x' in reactor config map, skipping
>
> And I would want to add a "cluster", for ppc64le in particular, but
> aarch64 would be good too. This is for Fedora Silverblue specially.
>
I see, at https://koji.fedoraproject.org/koji/builds?tagID=20245 , seems
all flatpak builds are for x86_64 only.

I don't have a machine of other than x86_64 so I can't test, but does this
mean fedora's flatpak source is totally unavailable on secondary arches? Or
I have any misunderstanding of flatpak image building?

And changing clusters for koji system is a work for infrastructure team,
maybe a issue at fedora-infrastructure is needed.

>
> Any help is welcome!
>
> Thank you!
> ___
> 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

[EPEL-devel] Re: gcc-gnat

[Qiyu Yan]

Erick Wittman  于 2020年7月14日周二 上午11:22写道：

> Hi EPEL developers.
>
> I am using CentOS 8 and am using various packages in the EPEL
> repository. I am interested in seeing gcc-gnat added to EPEL.
>
> I cannot find a current Fedora maintainer listed for this package, but it is 
> available in Fedora (at least in version 32).
>
> AKAIK gcc-gnat should be a sub package for gcc, making this appear in EPEL
should be just a tweak in gcc's spec file.
So, you should contact gcc's maintainer to check what to do.

> Are there any EPEL
> maintainers who are interested in creating an EPEL version of this package?
>
> Thank you
>
> ___
> epel-devel mailing list -- epel-devel@lists.fedoraproject.org
> To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
>
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org

Re: Fedora 33 System-Wide Change proposal: CMake to do out-of-source builds

[Qiyu Yan]

Richard Shaw  于 2020年7月8日周三 上午6:11写道：

> Ok, so it appears this change was for F32+ only, so I can't merge master
> into f32 or earlier...
>
 Maybe wait it to be backported into f31. The documents said this will be
backported into older supported version.

But now, merging master into older version is impossible, can cause FTBTS.

>
> This whole change is still broken AF.
>
> 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

Re: Fedora 33 System-Wide Change proposal: Make btrfs the default file system for desktop variants

[Qiyu Yan]

David Sterba  于2020年7月7日周二 下午6:09写道：
>
> > Yes, BtrFs was very unstable, but before. Every software has this process.  
> > I
> > have talked to one of the maintainer of BtrFs, she thinks that BtrFs is 
> > ready
> > to production usage. (few years before, she is strongly against using BtrFs
> > for production purpose).
>
> May I ask who was the person you talked to? I'm asking as the active 
> maintainer
> of btrfs. I'm familiar who does what in the community and overall status so it
> would be of my community interest to know who is speaking on behalf of the
> project, without me having even a slightest idea who that could be.
I may have take it wrongly, she is an developer at SUSE but not a maintainer.
Sorry for my mistake and that is only a personal opinion.

And that is a private talk.
>
> If you don't want to disclose the name in public, feel free to respond in
> private.
>
> Thanks.
[1] https://twitter.com/mawei_spoiler/status/1275692573999407108
___
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: Latest fedora on docker hub

[Qiyu Yan]

Seems that fedora:latest is f31 at dockerhub, is this intentional?

CC: cve...@fedoraproject.org, maintainer for the docker image at dockerhub

Christoph Junghans  于2020年7月4日周六 上午4:49写道：
>
> Hi,
>
> it seems fedora:latest on docker hub is still F31.
> $ docker run -it fedora:latest cat /etc/redhat-release
> Unable to find image 'fedora:latest' locally
> latest: Pulling from library/fedora
> 4c69497db035: Pull complete
> Digest: 
> sha256:ee55117b3058f2f12961184fae4b9c392586e400487626c6bd0d15b4eae94ecc
> Status: Downloaded newer image for fedora:latest
> Fedora release 31 (Thirty One)
>
> The README on docker hub (https://hub.docker.com/_/fedora) suggests it
> should be F32.
>
> Cheers,
>
> Christoph
>
>
> --
> Christoph Junghans
> Web: http://www.compphys.de
> ___
> 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: Latest fedora on docker hub

[Qiyu Yan]

You can try fedora:rawhide instead...while I don't know to whom this
problem should be reported.

And Fedora have registry.fedoraproject.org/fedora, where fedora:latest
= fedora 33(rawhide)

Christoph Junghans  于2020年7月4日周六 上午4:49写道：
>
> Hi,
>
> it seems fedora:latest on docker hub is still F31.
> $ docker run -it fedora:latest cat /etc/redhat-release
> Unable to find image 'fedora:latest' locally
> latest: Pulling from library/fedora
> 4c69497db035: Pull complete
> Digest: 
> sha256:ee55117b3058f2f12961184fae4b9c392586e400487626c6bd0d15b4eae94ecc
> Status: Downloaded newer image for fedora:latest
> Fedora release 31 (Thirty One)
>
> The README on docker hub (https://hub.docker.com/_/fedora) suggests it
> should be F32.
>
> Cheers,
>
> Christoph
>
>
> --
> Christoph Junghans
> Web: http://www.compphys.de
> ___
> 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: orphaned nuttcp

[Qiyu Yan]

Nikos Mavrogiannopoulos  于2020年7月2日周四 下午8:17写道：
>
> Hi,
>  I've orphaned the nuttcp component. It is long time since I last used
> it, and I do not plan updating it again. If you like networking tools
> this may be a package for you!
OKay, I am taking this.
>
> regards,
> Nikos
> ___
> 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: The future of legacy BIOS support in Fedora.

[Qiyu Yan]

Yes...Dropping support for BIOS will enable us to switch to
systemd-boot, which is the benefit. But just out of curiosity, what is
the benefit of switching from GRUB to systemd-boot.

Dropping support for 32-bit x86 surely can make maintainers be free
from one old platform (and less package to compile... etc.). But
supporting BIOS is just work for GRUB (and anaconda, not system-wide)
and when system is booted, BIOS or UEFI won't show such a significant
difference, not so great work is put into this.

Jóhann B. Guðmundsson  于2020年6月30日周二 下午9:34写道：
>
> Given Hans proposal [1] introduced systemd/grub2/Gnome upstream changes
> it beg the question if now would not be the time to stop supporting
> booting in legacy bios mode and move to uefi only supported boot which
> has been available on any common intel based x86 platform since atleast
> 2005.
>
> Now in 2017 Intel's technical marketing engineer Brian Richardson
> revealed in a presentation that the company will require UEFI Class 3
> and above as in it would remove legacy BIOS support from its client and
> datacenter platforms by 2020 and one might expect AMD to follow Intel in
> this regard.
>
> So Intel platforms produced this year presumably will be unable to run
> 32-bit operating systems, unable to use related software (at least
> natively), and unable to use older hardware, such as RAID HBAs (and
> therefore older hard drives that are connected to those HBAs), network
> cards, and even graphics cards that lack UEFI-compatible vBIOS (launched
> before 2012 – 2013) etc.
>
> This post is just to gather feed back why Fedora should still continue
> to support legacy BIOS boot as opposed to stop supporting it and
> potentially drop grub2 and use sd-boot instead.
>
> Share your thoughts and comments on how such move might affect you so
> feedback can be collected for the future on why such a change might be
> bad, how it might affect the distribution and scope of such change can
> be determined for potential system wide proposal.
>
>
> Regards
>
>   Jóhann B.
>
>
> 1.
> https://fedoraproject.org/wiki/Changes/CleanupGnomeHiddenBootMenuIntegration
> ___
> 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: Fedora 33 System-Wide Change proposal: Make btrfs the default file system for desktop variants

[Qiyu Yan]

And to add, since zfs can't be supported by Fedora by now, the only
filesystem that can identify file corruption and bit flip in your memory.
So, if btrfs is stable enough, this will be absolutely a benefit to users.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 33 System-Wide Change proposal: Make btrfs the default file system for desktop variants

[Qiyu Yan]

Yes, BtrFs was very unstable, but before. Every software has this process.
I have talked to one of the maintainer of BtrFs, she thinks that BtrFs
is ready to production usage. (few years before, she is strongly
against using BtrFs for production purpose).

But after all, this is an open-topic we should talk about, is BtrFs
stable enough for users.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 33 System-Wide Change proposal: Make nano the default editor

[Qiyu Yan]

Jaroslav Skarvada  于2020年6月26日周五 下午9:41写道：
>
>
>
> - Original Message -
> >
> >
> > Adam Williamson < adamw...@fedoraproject.org > 于 2020年6月26日周五 上午9:32写道：
> >
> >
> > On Fri, 2020-06-26 at 08:44 +0800, Qiyu Yan wrote:
> > > What about to provide a prompt to the user telling them the difference
> > > between editors?
> > > For example, when a new user to fedora first invokes git commit
> > > without $EDITOR set, a program named fedora-default-editor comes up
> > > and asks: Which editor do you like?
> > > User can do his or hers choice and the choice will be remembered by
> > > setting $EDITOR in his or hers ~/.bashrc
> > >
> > > The fedora-default-editor can be a small script that shows user all
> > > the difference and set $EDITOR for the user.
> >
> > It's a nice idea, but the problem with things like this is they
> > *always* introduce bugs, and often wind up being unmaintained, because
> > keeping them working is kind of a thankless task.
> >
> > IMHO it's better to keep things simple and just pick a default. And the
> > default should definitely be nano. :D
> > Then I will +1 for this proposal. Yes, this certainly will make Fedora 
> > easier
> > use for beginners. And for those who would like to use vi as default, we
> > should make this as easy as possible.
> >
> > I has been asked "how to exit this hell?" multiple times by my new-to-Linux
> > friends, that time I would always suggest them to set nano as default. Vim
> > is great though, it is not for beginners.
> >
> Why not just patch vim-minimal to show the hint on the CTRL+C?
> Problem solved :)
Ctrl + C in vi will give you a
Type :qa and press  to exit Vim
>
> Jaroslav
> ___
> 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: Fedora 33 System-Wide Change proposal: Make nano the default editor

[Qiyu Yan]

Adam Williamson  于 2020年6月26日周五 上午9:32写道：

> On Fri, 2020-06-26 at 08:44 +0800, Qiyu Yan wrote:
> > What about to provide a prompt to the user telling them the difference
> > between editors?
> > For example, when a new user to fedora first invokes git commit
> > without $EDITOR set, a program named fedora-default-editor comes up
> > and asks: Which editor do you like?
> > User can do his or hers choice and the choice will be remembered by
> > setting $EDITOR in his or hers ~/.bashrc
> >
> > The fedora-default-editor can be a small script that shows user all
> > the difference and set $EDITOR for the user.
>
> It's a nice idea, but the problem with things like this is they
> *always* introduce bugs, and often wind up being unmaintained, because
> keeping them working is kind of a thankless task.
>
> IMHO it's better to keep things simple and just pick a default. And the
> default should definitely be nano. :D
>
Then I will +1 for this proposal. Yes, this certainly will make Fedora
easier use for beginners. And for those who would like to use vi as
default, we should make this as easy as possible.

I has been asked "how to exit this hell?" multiple times by my new-to-Linux
friends, that time I would always suggest them to set nano as default. Vim
is great though, it is not for beginners.

> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora 33 System-Wide Change proposal: Make nano the default editor

[Qiyu Yan]

What about to provide a prompt to the user telling them the difference
between editors?
For example, when a new user to fedora first invokes git commit
without $EDITOR set, a program named fedora-default-editor comes up
and asks: Which editor do you like?
User can do his or hers choice and the choice will be remembered by
setting $EDITOR in his or hers ~/.bashrc

The fedora-default-editor can be a small script that shows user all
the difference and set $EDITOR for the user.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Fedora Packager Dashboard available for testing

[Qiyu Yan]

Christopher Engelhard  于2020年6月24日周三 下午7:25写道：
>
> This is awesome, thank you.
>
> On my dashboard (https://packager.fedorainfracloud.org/lcts), the
> mouse-over tooltips of top-row icons don't show up (I can see them in
> other people's dashes).
>
> This might be related to the fact that my packages currently have
> nothing to display, as the same thing happens for dashboards of
You are right, you currently have no related bugs or updates to deal with.
> non-existent accounts: https://packager.fedorainfracloud.org/xxyyzz
>
> Christopher
>
> On 23.06.20 18:28, Josef Skladanka wrote:
> > Hi,
> >
> > We'd like to announce public testing of the Packager Dashboard - a new
> > service for Fedora package maintainers aiming to provide all relevant
> > data: FTBFS/FTI status (from both Bugzilla, Koschei and health check),
> > orphan warnings, bugzillas, pull requests, active overrides and
> > updates - at a single place in an easy to read and filter way.
> >
> > The Dashboard is now available: https://packager.fedorainfracloud.org/
> >
> > Packager Dashboard leverages caching in the Oraculum backend to
> > significantly speed-up loading times with comparison to querying all
> > the relevant resources separately. We, of course, can't cache the
> > entire Bugzilla, Pagure, Bodhi... so we only cache data for users who
> > visit Packager Dashboard at least once per 14 days. Please keep in
> > mind that the first load for a “new” user might take a while. Most of
> > the data sources are refreshed every hour.
> >
> > You can use the Dashboard for individual accounts as well as for FAS groups.
> >
> > We'd love to hear your feedback. Please keep in mind that this is
> > testing deployment - it's currently running on a server with very
> > limited resources and we're aiming for production deployment on
> > CommuniShift during this summer.
> >
> > Feel free to provide ideas or bug reports at
> > https://pagure.io/fedora-qa/packager_dashboard or simply send an email
> > reply to this thread with all kinds of feedback.
> >
> > I'd like to mention the other people who made this possible:
> >  - Miro Hrončok (churchyard) - Original idea
> > 
> > and ideas for data to display
> >  - František Zatloukal - Backend 
> >  - Lukáš Brabec - Frontend 
> >
> > Josef
> > ___
> > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
> > To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: 
> > https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
> >
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: SELinux question

[Qiyu Yan]

Run your program in permissive mode and use audit2why [1], to see what's wrong.
If you have to allow that, you can use audit2allow [2] to produce a
policy package to allow that behavior in package.
I don't know how to make this into a package, maybe [3] will help.

[1] https://fedoraproject.org/wiki/SELinux/audit2why
[2] https://fedoraproject.org/wiki/SELinux/audit2allow
[3] https://fedoraproject.org/wiki/SELinux/IndependentPolicy
___
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: Orphaned packages looking for new maintainers (~200 nodejs packages to be retired in 2 days)

[Qiyu Yan]

I am going to take gpredict, I like this software : )
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: CPE Weekly: 2020-06-21

[Qiyu Yan]

Ronaldo Mercado  于2020年6月22日周一 下午3:43写道：
>
> Thanks for your message.
>
> > See our wiki page here for more
> > information:https://docs.fedoraproject.org/en-US/cpe/
>
> I am replying because the link in your message reports "403 Forbidden"
I think that is because the data center move somehow brokes
docs.fedoraproject.org, wait for it to restore.
>
> I copy below the message from firefox.
>
> Best wishes,
>
> R Mercado
>
> Forbidden
>
> You don't have permission to access this resource.
> Apache Server at docs.fedoraproject.org Port 443
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Self Introduction: Qiyu Yan

[Qiyu Yan]

I am Qiyu Yan, mail: yanqiy...@gmail.com, a 5-yesr Fedora user and a 
undergraduate student in Physics.

I started doing packaging because I want to setup development environment for 
my lab's computers, the software I first packaged is geant4 on copr 
http://copr.fedorainfracloud.org/coprs/yanqiyu/geant4/

By improving the package forked from someone else, I started to know how to do 
packaging. (geant4 is a complexed software, I need more time to package it well)

But I am not trying to join devel to bring geant4 to official repository here:

I want to make an open-source anti-censorship proxy software 
[Trojan](https://github.com/trojan-gfw/trojan) [GPL-3.0 license] available to 
Fedora's official repositories. Will that be  possible? (Its named as trojan 
but it is a proxy, which pretends to be a TLS server which makes it possible to 
bypass China, or any other government's censorship)

Fedora's official repositories already have a python3-shadowsocks with similar 
functions, but that project is likely to be out of maintenance. I think having 
a new one will be great. 

I have made it to be able to build on 
[koji](https://koji.fedoraproject.org/koji/taskinfo?taskID=45580956) what to do 
next to carry on?

And I want to add more proxy software, such as 
[V2ray](https://github.com/v2ray/v2ray-core) and 
[Shadowsocks-libev](https://github.com/shadowsocks/shadowsocks-libev) later.

Why I want to build those proxies into fedora's official repository? That is 
because downloading those software from GitHub or COPR will be extremely slow, 
but if them can enter official repository, they will be mirrored into China, 
which will make it easier to install for Chinese users. 

And they are not a Chinese only software, they are also useful when you don't 
want someone else to know if you are using a proxy, wireguard or IPSec just do 
encryption but not confuse possible attackers.
___
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