#184 Update Fedora-Legal-README.txt hopefully in a version agnostic way.
Closed 3 years ago by sgallagh. Opened 3 years ago by kevin.
Unknown source update-legal  into  rawhide

file modified
+3 -3
@@ -10,7 +10,7 @@

  

  = Source Availability =

  

- The accompanying Fedora 31 release includes copyrighted

+ The accompanying Fedora Linux 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
@@ -18,10 +18,10 @@

  

  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.

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

Assuming somebody actually sends that check and writes this in the memo line, what version of Fedora Linux sources will be mailed to them?

  

  You may also access a copy of this source code at:

- http://dl.fedoraproject.org/pub/fedora/linux/releases/31/Everything/source/

+ http://dl.fedoraproject.org/pub/fedora/linux/releases/<version>/Everything/source/

  

  This offer is valid to anyone in receipt of this information and shall

  expire three years following the date of the final distribution of

Build failed. More information on how to proceed and troubleshoot errors available at https://fedoraproject.org/wiki/Zuul-based-ci

Assuming somebody actually sends that check and writes this in the memo line, what version of Fedora Linux sources will be mailed to them?

Assuming somebody actually sends that check and writes this in the memo line, what version of Fedora Linux sources will be mailed to them?

Yeah, that's a definite hypothetical concern. I kinda want to try it just to see what happens.

I was going to suggest doing something ugly like sed in the appropriate number when building the RPM, but it looks like we already do that on line 810. So the right answer here is to restore the substitution string in the txt file.

I can do a test build tomorrow during the release party and submit a new PR. Probably worth taking the opportunity to review the rest of the file and make sure nothing else needs to be updated anyway.

Pull-Request has been closed by sgallagh

3 years ago
Metadata