Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

2023-09-18 Thread Steven A. Falco

On 9/18/23 11:33 AM, Neal Gompa wrote:

On Mon, Sep 18, 2023 at 11:12 AM Steven A. Falco  wrote:


On 9/17/23 05:48 PM, Kevin Kofler via devel wrote:

Ian Laurie wrote:

I didn't think the greeter used Wayland?  So there may be something else
going on.  I cannot swear to it, but I don't think I've noticed problems
in the greeter before.

As Adam posted, the offset problem already has a bug for it.  Wayland is
certainly unusable in VirtualBox, but now even the greeter has issues,
and I think that's newish.


SDDM was switched to Wayland for F38 and newer. If you want it to use X11,
you have to edit /etc/sddm.conf and set:

[General]
DisplayServer=x11

there.

  Kevin Kofler


Yes - I had to do that because the Wayland version of the SDDM greeter 
apparently doesn't honor xrandr.

I have the following in my /etc/sddm/Xsetup file:

 #!/usr/bin/sh
 # Xsetup - run as root before the login dialog appears
 xrandr --output DisplayPort-0 --right-of DisplayPort-1

If I have the greeter set to x11 that works perfectly, but if I have the 
greeter set to wayland it is ignored.

I don't know if there is a way to tell wayland the desired screen arrangement.  
If there is a way I'd like to hear about it.  If there isn't a way, then I 
guess that should be another bug.



kwin can be configured using kscreen-doctor, as long as the kwin
wayland socket is up.


Thanks, Neal.  I'll give that a try at some point.

Steve

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


Re: Orphaned packages looking for new maintainers

2023-09-18 Thread Ben Beasley
Since the python-qdarkstyle package is needed for the Spyder IDE, I 
ended up claiming it and fixing it. The main change is that I dropped 
the dependency on PySide2, since PySide2 is still broken on Python 3.12.


Now that python-qdarkstyle is installable on F39/F40 again, I was able 
to build electrum without any modifications; I added the builds  to my 
latest updates involving python-qdarkstyle:


F40: https://bodhi.fedoraproject.org/updates/FEDORA-2023-3a1e52015a

F39: https://bodhi.fedoraproject.org/updates/FEDORA-2023-527f01eddb

I’ve never used Electrum, and I didn’t attempt to test the package 
interactively, but at least it is buildable and installable now.



On 9/7/23 7:58 AM, Ben Beasley wrote:
It looks like the Electrum build is currently blocked not by protobuf, 
but by the failure of python-qdarkstyle to rebuild for Python 
3.12[1][2]. That dependency is also currently orphaned.


Grepping through the Electrum source, I see:

    Electrum-4.3.4/contrib/requirements/requirements.txt
    2:protobuf>=3.12,<4

    Electrum-4.3.4/contrib/requirements/requirements-hw.txt
    32:protobuf>=3.12,<4

    Electrum-4.3.4/contrib/deterministic-build/requirements-hw.txt
    175:protobuf==3.20.3 \

    Electrum-4.3.4/contrib/deterministic-build/requirements.txt
    31:protobuf==3.20.3 \

Based on that, it looks like the minimum protobuf version should 
actually be 3.12 (we have 3.19), not 3.20; the latter should only be 
the preferred version for deterministic builds. So I suspect 
everything will be fine if you can get python-qdarkstyle fixed.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=2225768#c6

[2] https://bugzilla.redhat.com/show_bug.cgi?id=2220472

On 9/7/23 05:52, Jonathan Schleifer wrote:
Unfortunately, it is worse than this: Electrum FTI in F39. A newer 
Electrum version would fix that, but F39 still has no new enough 
protobuf.


Is there any other solution here than saying packaging Electrum for 
Fedora 39 is just not possible and remove the package in F39, then 
reintroduce it in F40 (that is, if F40 finally gets a newer protobuf)?



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


Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

2023-09-18 Thread Neal Gompa
On Mon, Sep 18, 2023 at 11:12 AM Steven A. Falco  wrote:
>
> On 9/17/23 05:48 PM, Kevin Kofler via devel wrote:
> > Ian Laurie wrote:
> >> I didn't think the greeter used Wayland?  So there may be something else
> >> going on.  I cannot swear to it, but I don't think I've noticed problems
> >> in the greeter before.
> >>
> >> As Adam posted, the offset problem already has a bug for it.  Wayland is
> >> certainly unusable in VirtualBox, but now even the greeter has issues,
> >> and I think that's newish.
> >
> > SDDM was switched to Wayland for F38 and newer. If you want it to use X11,
> > you have to edit /etc/sddm.conf and set:
> >
> > [General]
> > DisplayServer=x11
> >
> > there.
> >
> >  Kevin Kofler
>
> Yes - I had to do that because the Wayland version of the SDDM greeter 
> apparently doesn't honor xrandr.
>
> I have the following in my /etc/sddm/Xsetup file:
>
> #!/usr/bin/sh
> # Xsetup - run as root before the login dialog appears
> xrandr --output DisplayPort-0 --right-of DisplayPort-1
>
> If I have the greeter set to x11 that works perfectly, but if I have the 
> greeter set to wayland it is ignored.
>
> I don't know if there is a way to tell wayland the desired screen 
> arrangement.  If there is a way I'd like to hear about it.  If there isn't a 
> way, then I guess that should be another bug.
>

kwin can be configured using kscreen-doctor, as long as the kwin
wayland socket is up.


-- 
真実はいつも一つ!/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: F40 Change Proposal: KDE Plasma 6 (System Wide)

2023-09-18 Thread Steven A. Falco

On 9/17/23 05:48 PM, Kevin Kofler via devel wrote:

Ian Laurie wrote:

I didn't think the greeter used Wayland?  So there may be something else
going on.  I cannot swear to it, but I don't think I've noticed problems
in the greeter before.
  
As Adam posted, the offset problem already has a bug for it.  Wayland is

certainly unusable in VirtualBox, but now even the greeter has issues,
and I think that's newish.


SDDM was switched to Wayland for F38 and newer. If you want it to use X11,
you have to edit /etc/sddm.conf and set:

[General]
DisplayServer=x11

there.

 Kevin Kofler


Yes - I had to do that because the Wayland version of the SDDM greeter 
apparently doesn't honor xrandr.

I have the following in my /etc/sddm/Xsetup file:

   #!/usr/bin/sh
   # Xsetup - run as root before the login dialog appears
   xrandr --output DisplayPort-0 --right-of DisplayPort-1

If I have the greeter set to x11 that works perfectly, but if I have the 
greeter set to wayland it is ignored.

I don't know if there is a way to tell wayland the desired screen arrangement.  
If there is a way I'd like to hear about it.  If there isn't a way, then I 
guess that should be another bug.

Steve

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


Fedora 39 compose report: 20230918.n.0 changes

2023-09-18 Thread Fedora Branched Report
OLD: Fedora-39-20230916.n.0
NEW: Fedora-39-20230918.n.0

= SUMMARY =
Added images:2
Dropped images:  0
Added packages:  0
Dropped packages:1
Upgraded packages:   37
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:191.11 MiB
Size of upgraded packages:   2.60 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-39-20230918.n.0.iso
Image: Silverblue dvd-ostree x86_64
Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-39-20230918.n.0.iso

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =
Package: mscore-3.6.2-14.fc38
Summary: Music Composition & Notation Software
RPMs:mscore mscore-bc-fonts mscore-doc mscore-edwin-fonts mscore-fonts 
mscore-fonts-all mscore-gootville-fonts mscore-leland-fonts 
mscore-mscoretab-fonts mscore-mscoretext-fonts mscore-musejazz-fonts
Size:191.11 MiB


= UPGRADED PACKAGES =
Package:  abseil-cpp-20230802.0-1.fc39
Old package:  abseil-cpp-20230125.3-2.fc39
Summary:  C++ Common Libraries
RPMs: abseil-cpp abseil-cpp-devel abseil-cpp-testing
Size: 8.36 MiB
Size change:  170.66 KiB
Changelog:
  * Thu Aug 10 2023 Benjamin A. Beasley  - 20230802.0-1
  - Update to 20230802.0 (Abseil LTS branch, Aug 2023): close RHBZ#2229015


Package:  aom-3.7.0-1.fc39
Old package:  aom-3.6.1-2.fc39
Summary:  Royalty-free next-generation video format
RPMs: aom libaom libaom-devel
Size: 74.31 MiB
Size change:  694.31 KiB
Changelog:
  * Fri Sep 01 2023 Fabio Valentini  - 3.7.0-1
  - Update to version 3.7.0; Fixes RHBZ#2236624


Package:  bear-3.1.3-1.fc39
Old package:  bear-3.1.2-5.fc39
Summary:  Tool that generates a compilation database for clang tooling
RPMs: bear
Size: 2.15 MiB
Size change:  4.36 KiB
Changelog:
  * Tue Aug 29 2023 Benjamin A. Beasley  - 3.1.2-6
  - Rebuilt for abseil-cpp-20230802.0

  * Wed Aug 30 2023 Benjamin A. Beasley  - 3.1.3-1
  - Update to 3.1.3 (close RHBZ#2235568)


Package:  bloaty-1.1-22.fc39
Old package:  bloaty-1.1-21.fc39
Summary:  A size profiler for binaries
RPMs: bloaty
Size: 711.32 KiB
Size change:  1.85 KiB
Changelog:
  * Wed Aug 30 2023 Benjamin A. Beasley  - 1.1-22
  - Rebuilt for abseil-cpp 20230802.0


Package:  credentials-fetcher-1.2.0-3.fc39
Old package:  credentials-fetcher-1.2.0-2.fc39
Summary:  credentials-fetcher is a daemon that refreshes tickets or tokens 
periodically
RPMs: credentials-fetcher
Size: 802.02 KiB
Size change:  401 B
Changelog:
  * Thu Aug 31 2023 Tom Callaway  - 1.2.0-3
  - rebuild for abseil


Package:  fastnetmon-1.2.1-12.20220528git420e7b8.fc39
Old package:  fastnetmon-1.2.1-11.20220528git420e7b8.fc39
Summary:  DDoS detection tool with sFlow, Netflow, IPFIX and port mirror 
support
RPMs: fastnetmon
Size: 4.07 MiB
Size change:  -1.75 KiB
Changelog:
  * Sat Sep 16 2023 Benjamin A. Beasley  - 
1.2.1-12.20220528git420e7b8
  - Rebuilt for abseil-cpp 20230802.0 (with capnproto 1.0.1 too!)


Package:  fcitx5-mozc-2.17.2102.102.1-28.20230508git242b4f7.fc39
Old package:  fcitx5-mozc-2.17.2102.102.1-27.20230508git242b4f7.fc39
Summary:  A wrapper of mozc for fcitx5
RPMs: fcitx5-mozc
Size: 41.77 MiB
Size change:  6.56 KiB
Changelog:
  * Sun Aug 20 2023 Qiyu Yan  - 2.17.2102.102.1-28
  - Fix the build issue with newer abseil.


Package:  firefox-117.0.1-2.fc39
Old package:  firefox-117.0-1.fc39
Summary:  Mozilla Firefox Web browser
RPMs: firefox firefox-langpacks firefox-wayland firefox-x11
Size: 427.13 MiB
Size change:  -42.93 KiB
Changelog:
  * Wed Aug 30 2023 Martin Stransky - 117.0-2
  - Added fix for rhbz#2235654

  * Wed Sep 13 2023 Martin Stransky - 117.0.1-1
  - Updated to 117.0.1

  * Thu Sep 14 2023 Adam Williamson  - 117.0.1-2
  - Pass --with-clang-path to fix build with clang 17 (rhbz#2239047)


Package:  frr-8.5.2-4.fc39
Old package:  frr-8.5.2-2.fc39
Summary:  Routing daemon
RPMs: frr frr-selinux
Size: 20.42 MiB
Size change:  4.00 KiB
Changelog:
  * Wed Aug 30 2023 Benjamin A. Beasley  - 8.5.2-3
  - Rebuilt for abseil-cpp 20230802.0

  * Fri Sep 01 2023 Michal Ruprich  - 8.5.2-4
  - Adding a couple of SELinux rules, includes fix for rhbz#2149299


Package:  grpc-1.48.4-25.fc39
Old package:  grpc-1.48.4-24.fc39
Summary:  RPC library and framework
RPMs: grpc grpc-cli grpc-cpp grpc-data grpc-devel grpc-doc grpc-plugins 
python3-grpcio python3-grpcio+protobuf python3-grpcio-channelz 
python3-grpcio-health-checking python3-grpcio-reflection python3-grpcio-status 
python3-grpcio-testing python3-grpcio-tools
Size: 29.94 MiB
Size change:  -12.74 KiB
Changelog:
  * Tue Aug 29 2023 Benjamin A. Beasley  - 1.48.4-25
  - Reb

Re: An update on RHEL moving to issues.redhat.com

2023-09-18 Thread Colin Walters


On Mon, Sep 18, 2023, at 3:57 AM, Petr Pisar wrote:
> V Fri, Sep 15, 2023 at 01:27:23PM -0400, Colin Walters napsal(a):
>> To state the blindingly obvious thing, RHEL made a decision to centralize on
>> Gitlab.  Having Fedora be on pagure creates IMO unnecessary friction for me.
>> I would be quite curious to get some sort of survey of other engineers for
>> how they feel.
>
> My selfishly preferable option is not to use Gitlab.com for Fedora exactly
> because RHEL uses Gitlab.com. The reason is very practical: You need separate
> accounts for the two projects and GitLab.com is not good at using multiple
> accounts simulatenously. Having different systems makes to problem go away and
> my life easier.

I use https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/ 
for this and other places where I also have work and personal accounts - solves 
the problem nicely for me.  

(Now, one other special twist with two-account gitlab (and github) is dealing 
with ssh keys and remotes, but that's not too hard to solve either)
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Fedora rawhide compose report: 20230918.n.0 changes

2023-09-18 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20230917.n.0
NEW: Fedora-Rawhide-20230918.n.0

= SUMMARY =
Added images:3
Dropped images:  3
Added packages:  10
Dropped packages:0
Upgraded packages:   278
Downgraded packages: 0

Size of added packages:  1.28 MiB
Size of dropped packages:0 B
Size of upgraded packages:   5.70 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20230918.n.0.iso
Image: LXQt live aarch64
Path: Spins/aarch64/iso/Fedora-LXQt-Live-aarch64-Rawhide-20230918.n.0.iso
Image: KDE live aarch64
Path: Spins/aarch64/iso/Fedora-KDE-Live-aarch64-Rawhide-20230918.n.0.iso

= DROPPED IMAGES =
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20230917.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230917.n.0.iso
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20230917.n.0.iso

= ADDED PACKAGES =
Package: rust-bindgen0.63-0.63.0-1.fc40
Summary: Automatically generates Rust FFI bindings to C and C++ libraries
RPMs:rust-bindgen0.63+default-devel rust-bindgen0.63+log-devel 
rust-bindgen0.63+logging-devel rust-bindgen0.63+runtime-devel 
rust-bindgen0.63+static-devel rust-bindgen0.63+testing_only_docs-devel 
rust-bindgen0.63+testing_only_extra_assertions-devel 
rust-bindgen0.63+testing_only_libclang_5-devel 
rust-bindgen0.63+testing_only_libclang_9-devel rust-bindgen0.63+which-devel 
rust-bindgen0.63+which-rustfmt-devel rust-bindgen0.63-devel
Size:262.27 KiB

Package: rust-chic-1.2.2-1.fc40
Summary: Pretty parser error reporting
RPMs:rust-chic+default-devel rust-chic-devel
Size:22.67 KiB

Package: rust-gix-attributes-0.18.0-1.fc40
Summary: Gix implemenation for handling git attributes files
RPMs:rust-gix-attributes+default-devel 
rust-gix-attributes+document-features-devel rust-gix-attributes+serde-devel 
rust-gix-attributes-devel
Size:66.85 KiB

Package: rust-gix-ignore-0.7.0-1.fc40
Summary: Gix implemenation for handling git gitignore files
RPMs:rust-gix-ignore+default-devel rust-gix-ignore+document-features-devel 
rust-gix-ignore+serde-devel rust-gix-ignore-devel
Size:43.05 KiB

Package: rust-gix-revwalk-0.7.0-1.fc40
Summary: Utility library for walking the revision graph
RPMs:rust-gix-revwalk+default-devel rust-gix-revwalk-devel
Size:30.88 KiB

Package: rust-gix-tempfile-9.0.0-1.fc40
Summary: Tempfile implementation with a global registry to assure cleanup
RPMs:rust-gix-tempfile+default-devel 
rust-gix-tempfile+document-features-devel rust-gix-tempfile+hp-hashmap-devel 
rust-gix-tempfile+signals-devel rust-gix-tempfile-devel
Size:67.59 KiB

Package: rust-imara-diff-0.1.5-1.fc40
Summary: Minimal diff library
RPMs:rust-imara-diff+default-devel rust-imara-diff+unified_diff-devel 
rust-imara-diff-devel
Size:54.88 KiB

Package: rust-linux-raw-sys0.3-0.3.8-1.fc40
Summary: Generated bindings for Linux's userspace API
RPMs:rust-linux-raw-sys0.3+default-devel rust-linux-raw-sys0.3+errno-devel 
rust-linux-raw-sys0.3+general-devel rust-linux-raw-sys0.3+ioctl-devel 
rust-linux-raw-sys0.3+netlink-devel rust-linux-raw-sys0.3+no_std-devel 
rust-linux-raw-sys0.3+std-devel rust-linux-raw-sys0.3-devel
Size:186.33 KiB

Package: rust-rustix0.37-0.37.23-1.fc40
Summary: Safe Rust bindings to POSIX/Unix/Linux/Winsock2-like syscalls
RPMs:rust-rustix0.37+all-apis-devel rust-rustix0.37+all-impls-devel 
rust-rustix0.37+cc-devel rust-rustix0.37+default-devel rust-rustix0.37+fs-devel 
rust-rustix0.37+fs-err-devel rust-rustix0.37+io-lifetimes-devel 
rust-rustix0.37+io_uring-devel rust-rustix0.37+itoa-devel 
rust-rustix0.37+libc-devel rust-rustix0.37+libc_errno-devel 
rust-rustix0.37+linux_4_11-devel rust-rustix0.37+linux_latest-devel 
rust-rustix0.37+mm-devel rust-rustix0.37+net-devel 
rust-rustix0.37+once_cell-devel rust-rustix0.37+os_pipe-devel 
rust-rustix0.37+param-devel rust-rustix0.37+process-devel 
rust-rustix0.37+procfs-devel rust-rustix0.37+pty-devel 
rust-rustix0.37+rand-devel rust-rustix0.37+runtime-devel 
rust-rustix0.37+std-devel rust-rustix0.37+termios-devel 
rust-rustix0.37+thread-devel rust-rustix0.37+time-devel 
rust-rustix0.37+use-libc-auxv-devel rust-rustix0.37+use-libc-devel 
rust-rustix0.37-devel
Size:514.81 KiB

Package: rust-uzers-0.11.3-1.fc40
Summary: Library for accessing Unix users and groups
RPMs:rust-uzers+cache-devel rust-uzers+default-devel rust-uzers+log-devel 
rust-uzers+logging-devel rust-uzers+mock-devel rust-uzers-devel
Size:64.53 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  PyDrive2-1.17.0-2.fc40
Old package:  PyDrive2-1.17.0-1.fc40
Summary:  Google Drive API Python wrapper li

Re: An update on RHEL moving to issues.redhat.com

2023-09-18 Thread Michael J Gruber
Am Mo., 18. Sept. 2023 um 12:39 Uhr schrieb Petr Pisar :
>
> V Mon, Sep 18, 2023 at 10:12:17AM +0100, Daniel P. Berrangé napsal(a):
> > On Mon, Sep 18, 2023 at 09:57:28AM +0200, Petr Pisar wrote:
> > > V Fri, Sep 15, 2023 at 01:27:23PM -0400, Colin Walters napsal(a):
> > > > To state the blindingly obvious thing, RHEL made a decision to 
> > > > centralize on
> > > > Gitlab.  Having Fedora be on pagure creates IMO unnecessary friction 
> > > > for me.
> > > > I would be quite curious to get some sort of survey of other engineers 
> > > > for
> > > > how they feel.
> > >
> > > My selfishly preferable option is not to use Gitlab.com for Fedora exactly
> > > because RHEL uses Gitlab.com. The reason is very practical: You need 
> > > separate
> > > accounts for the two projects and GitLab.com is not good at using multiple
> > > accounts simulatenously. Having different systems makes to problem go 
> > > away and
> > > my life easier.
> >
> > You don't require separate accounts. It is a choice developers can
> > make to keep their upstream vs RHEL work in gitlab.com separated,
> > or under the same account. There are pros & cons, so it is really
> > a matter of personal preference.
> >
> It's is a matter of security. With a single account you give Fedora admins
> an access to RHEL and vice versa.

That is an interesting point, and one that was never clear to me from
the wording "organisation xy wants to manage your account": Which kind
of access do you grant Fedora (resp. RHEL) if you "join" that GitLab
organisation with an existing GitLab account?

If it's a Fedora hosted instance things are much clearer.

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


Re: An update on RHEL moving to issues.redhat.com

2023-09-18 Thread Petr Pisar
V Mon, Sep 18, 2023 at 10:12:17AM +0100, Daniel P. Berrangé napsal(a):
> On Mon, Sep 18, 2023 at 09:57:28AM +0200, Petr Pisar wrote:
> > V Fri, Sep 15, 2023 at 01:27:23PM -0400, Colin Walters napsal(a):
> > > To state the blindingly obvious thing, RHEL made a decision to centralize 
> > > on
> > > Gitlab.  Having Fedora be on pagure creates IMO unnecessary friction for 
> > > me.
> > > I would be quite curious to get some sort of survey of other engineers for
> > > how they feel.
> > 
> > My selfishly preferable option is not to use Gitlab.com for Fedora exactly
> > because RHEL uses Gitlab.com. The reason is very practical: You need 
> > separate
> > accounts for the two projects and GitLab.com is not good at using multiple
> > accounts simulatenously. Having different systems makes to problem go away 
> > and
> > my life easier.
> 
> You don't require separate accounts. It is a choice developers can
> make to keep their upstream vs RHEL work in gitlab.com separated,
> or under the same account. There are pros & cons, so it is really
> a matter of personal preference.
>
It's is a matter of security. With a single account you give Fedora admins
an access to RHEL and vice versa.

-- Petr


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


Re: An update on RHEL moving to issues.redhat.com

2023-09-18 Thread Daniel P . Berrangé
On Mon, Sep 18, 2023 at 09:57:28AM +0200, Petr Pisar wrote:
> V Fri, Sep 15, 2023 at 01:27:23PM -0400, Colin Walters napsal(a):
> > To state the blindingly obvious thing, RHEL made a decision to centralize on
> > Gitlab.  Having Fedora be on pagure creates IMO unnecessary friction for me.
> > I would be quite curious to get some sort of survey of other engineers for
> > how they feel.
> 
> My selfishly preferable option is not to use Gitlab.com for Fedora exactly
> because RHEL uses Gitlab.com. The reason is very practical: You need separate
> accounts for the two projects and GitLab.com is not good at using multiple
> accounts simulatenously. Having different systems makes to problem go away and
> my life easier.

You don't require separate accounts. It is a choice developers can
make to keep their upstream vs RHEL work in gitlab.com separated,
or under the same account. There are pros & cons, so it is really
a matter of personal preference.

With regards,
Daniel
___
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: An update on RHEL moving to issues.redhat.com

2023-09-18 Thread Petr Pisar
V Fri, Sep 15, 2023 at 01:27:23PM -0400, Colin Walters napsal(a):
> To state the blindingly obvious thing, RHEL made a decision to centralize on
> Gitlab.  Having Fedora be on pagure creates IMO unnecessary friction for me.
> I would be quite curious to get some sort of survey of other engineers for
> how they feel.

My selfishly preferable option is not to use Gitlab.com for Fedora exactly
because RHEL uses Gitlab.com. The reason is very practical: You need separate
accounts for the two projects and GitLab.com is not good at using multiple
accounts simulatenously. Having different systems makes to problem go away and
my life easier.

-- Petr


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