[prev in list] [next in list] [prev in thread] [next in thread]
List: fedora-devel-list
Subject: Re: Orphaning all my packages
From: Carlos Rodriguez Fernandez <carlosrodrifernandez () gmail ! com>
Date: 2023-10-03 21:50:08
Message-ID: CAMXYTuUxqyGOcrgqTJ1s7Z_xXhk3Vk-7xGUSDyfoQ+J02SYmbQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Because when they ask "where is the code?", they are asking a different
question than yours :)
Regards,
Carlos
On Tue, Oct 3, 2023 at 2:30 PM Simo Sorce <simo@redhat.com> wrote:
> On Tue, 2023-10-03 at 23:13 +0200, Leon Fauster via devel wrote:
> > Am 03.10.23 um 21:29 schrieb Simo Sorce:
> > > On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:
> > > > Am 03.10.23 um 20:46 schrieb Sérgio Basto:
> > > > > On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:
> > > > > > On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce <
> simo@redhat.com>
> > > > > > wrote:
> > > > > > > Additionally *all* of the code is fully available in git form
> on
> > > > > > > gitlab
> > > > > > > as part of CentOS Stream.
> > > > > >
> > > > > > We all know or should know that this is false. It's easy enough
> to
> > > > > > disprove with a counterexample:
> > > > > >
> > > > > > https://access.redhat.com/errata/RHSA-2023:1918
> > > > > >
> > > > > > Try to find the code for that
> webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in
> > > > > > CentOS Stream. It isn't there, and never will be.
> > > > > >
> > > > >
> > > > > it is here :
> > > > >
> https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9
> > > > >
> > > >
> > > >
> > > > Since June 21 the strategy changed. Such commits do not get pushed
> > > > anymore. But you are right, to prove it a different example is
> necessary ...
> > >
> > > You are wrong and have been mislead.
> > > Nothing has changed in how we develop and publish code in gitlab.
> >
> >
> > Nope, I do not argue about processes at all. Its about resulting code
> > fragments. Speak, having in gitlab version 8 of a package and in the
> > current/latest RHEL release (9.2) version 7 with backports of 8 doesn't
> > mean that the code is in gitlab. The code differs and its not
> > accessible. Thats all about.
>
> The code is still in gitlab, in most cases in directly accessible in
> individual commits. In some cases, like the one Michael mentioned,
> where a rebase landed early in the CentOS branch the code may land
> together with other changes, but it is not like it is not there.
> There are is a no regression policy in RHEL, so if CentOS is ahead it
> means it already has all of the code in question.
>
> And if there is an actual reason to need to know what exact change
> landed in RHEL there are several avenues to find out (just grab a
> developer subscription for example).
>
> I just find that this is generally just a mental exercise, but not
> something people do or need to do on a regular basis, and does not
> prevent any use, study, sharing or enjoyment of the code.
>
> Claiming the code is inaccessible sounds odd to me.
> But perhaps I am just old and remember when all you got from upstream
> was a tarball and you had to figure out what actual changes went in
> manually with diff ... no commits or commit messages and often not even
> a reasonable changelog ...
>
> Simo.
>
> --
> Simo Sorce,
> DE @ RHEL Crypto Team,
> Red Hat, Inc
>
>
>
> _______________________________________________
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-leave@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
>
[Attachment #5 (text/html)]
<div dir="auto">Because when they ask "where is the code?", they are asking a \
different question than yours :)</div><div dir="auto"><br></div><div \
dir="auto">Regards,</div><div dir="auto">Carlos</div><div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 3, 2023 at 2:30 PM \
Simo Sorce <<a href="mailto:simo@redhat.com">simo@redhat.com</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 2023-10-03 at 23:13 +0200, \
Leon Fauster via devel wrote:<br> > Am 03.10.23 um 21:29 schrieb Simo Sorce:<br>
> > On Tue, 2023-10-03 at 20:55 +0200, Leon Fauster via devel wrote:<br>
> > > Am 03.10.23 um 20:46 schrieb Sérgio Basto:<br>
> > > > On Tue, 2023-10-03 at 13:13 -0500, Michael Catanzaro wrote:<br>
> > > > > On Tue, Oct 3 2023 at 01:19:20 PM -0400, Simo Sorce <<a \
href="mailto:simo@redhat.com" target="_blank">simo@redhat.com</a>><br> > > \
> > > wrote:<br> > > > > > > Additionally *all* of the \
code is fully available in git form on<br> > > > > > > gitlab<br>
> > > > > > as part of CentOS Stream.<br>
> > > > > <br>
> > > > > We all know or should know that this is false. It's easy \
enough to<br> > > > > > disprove with a counterexample:<br>
> > > > > <br>
> > > > > <a href="https://access.redhat.com/errata/RHSA-2023:1918" \
rel="noreferrer" target="_blank">https://access.redhat.com/errata/RHSA-2023:1918</a><br>
> > > > > <br>
> > > > > Try to find the code for that \
webkit2gtk3-2.36.7-1.el9_1.3.src.rpm in<br> > > > > > CentOS Stream. \
It isn't there, and never will be.<br> > > > > > <br>
> > > > <br>
> > > > it is here :<br>
> > > > <a \
href="https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9" \
rel="noreferrer" target="_blank">https://git.centos.org/rpms/webkit2gtk3/c/2d1b790baa97d14849e56ed21d3f0145268283c2?branch=c9</a><br>
> > > > <br>
> > > <br>
> > > <br>
> > > Since June 21 the strategy changed. Such commits do not get pushed<br>
> > > anymore. But you are right, to prove it a different example is \
necessary ...<br> > > <br>
> > You are wrong and have been mislead.<br>
> > Nothing has changed in how we develop and publish code in gitlab.<br>
> <br>
> <br>
> Nope, I do not argue about processes at all. Its about resulting code<br>
> fragments. Speak, having in gitlab version 8 of a package and in the<br>
> current/latest RHEL release (9.2) version 7 with backports of 8 doesn't<br>
> mean that the code is in gitlab. The code differs and its not<br>
> accessible. Thats all about.<br>
<br>
The code is still in gitlab, in most cases in directly accessible in<br>
individual commits. In some cases, like the one Michael mentioned,<br>
where a rebase landed early in the CentOS branch the code may land<br>
together with other changes, but it is not like it is not there.<br>
There are is a no regression policy in RHEL, so if CentOS is ahead it<br>
means it already has all of the code in question.<br>
<br>
And if there is an actual reason to need to know what exact change<br>
landed in RHEL there are several avenues to find out (just grab a<br>
developer subscription for example).<br>
<br>
I just find that this is generally just a mental exercise, but not<br>
something people do or need to do on a regular basis, and does not<br>
prevent any use, study, sharing or enjoyment of the code.<br>
<br>
Claiming the code is inaccessible sounds odd to me.<br>
But perhaps I am just old and remember when all you got from upstream<br>
was a tarball and you had to figure out what actual changes went in<br>
manually with diff ... no commits or commit messages and often not even<br>
a reasonable changelog ... <br>
<br>
Simo.<br>
<br>
-- <br>
Simo Sorce,<br>
DE @ RHEL Crypto Team,<br>
Red Hat, Inc<br>
<br>
<br>
<br>
_______________________________________________<br>
devel mailing list -- <a href="mailto:devel@lists.fedoraproject.org" \
target="_blank">devel@lists.fedoraproject.org</a><br> To unsubscribe send an email to \
<a href="mailto:devel-leave@lists.fedoraproject.org" \
target="_blank">devel-leave@lists.fedoraproject.org</a><br> Fedora Code of Conduct: \
<a href="https://docs.fedoraproject.org/en-US/project/code-of-conduct/" \
rel="noreferrer" target="_blank">https://docs.fedoraproject.org/en-US/project/code-of-conduct/</a><br>
List Guidelines: <a href="https://fedoraproject.org/wiki/Mailing_list_guidelines" \
rel="noreferrer" target="_blank">https://fedoraproject.org/wiki/Mailing_list_guidelines</a><br>
List Archives: <a href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org" \
rel="noreferrer" target="_blank">https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org</a><br>
Do not reply to spam, report it: <a \
href="https://pagure.io/fedora-infrastructure/new_issue" rel="noreferrer" \
target="_blank">https://pagure.io/fedora-infrastructure/new_issue</a><br> \
</blockquote></div></div>
[Attachment #6 (text/plain)]
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@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
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic