Spec file using github repo - not tarball

[Kenneth Goldman]

Is it possible for a .spec file to clone a github.com repo rather than 
download a tarball?  Can someone link to a working example?

I found a few hints that it's possible.  However, the fedoraproject.org 
examples use pseudocode or placeholders.  I'd like a working example.


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: Simpler first tutorial package for Package Maintainer Docs

[Kenneth Goldman]

A review from a complete newbie ...

1. The link points to a pull request.  Where is the actual tutorial?

2. The page refers to Pagure, Antora, ... I wonder if they're necessary for 
packaging.

As a newbie, I would like an example that looks like:

1. Push the main branch to github.
2. Do these steps.
n. Push the result to Fedora.

> -Original Message-
> From: Otto Liljalaakso 
> Sent: Monday, April 22, 2024 3:29 PM
> To: Development discussions related to Fedora
> 
> Subject: [EXTERNAL] Simpler first tutorial package for Package Maintainer
> Docs
>
> Hello everybody,
>
> I wrote a pull request for Package Maintainer Docs about adding a simpler
> tutorial package than GNU Hello [1]. Since it is a larger change and I have 
> not
> received any reviews yet, I would like to announce this work here, in hope 
> of
> getting some feedback, before just merging the change. Since I have already
> described the work in the pull request description, I will just copy it here
> below. Feel free to respond on the list or in pull request comments.
>
> [1]: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__pagure.io_fedora-2Ddocs_package-2Dmaintainer-2Ddocs_pull-
> 2Drequest_153=DwIGaQ=BSDicqBQBDjDI9RkVyTcHQ=H5QohD_RgG
> RTOmpJ5rew0X87YNwM_iH7SF9XZijdV0o=ZVYh2Pnj1mqVP5ceO87VGJei
> n8OQF7fgyLfPmsvXyFeH6tl2Kb4aaz2DxgI9q2Qq=9f59NzD15enLv7LSAINyq
> u2CgUH6sNGK-Cg0UcV6s0c=
>
>  > Add simpler Banner package to packaging tutorial  >  > Packaging 
> tutorial's
> approach of packaging GNU Hello has suffered from  > certain complexities in
> GNU Hello package. The package is quite old and  > uses some tooling from
> the GNU project that are not very widely used  > any more, such as Texinfo.
> Also, the package is old and thus suffers  > from e.g. having a file that is 
> not
> UTF-8 encoded. To avoid immediately  > exposing tutorial readers to these
> quirks, make GNU Hello part 2 of the  > tutorial and add a simpler package,
> Banner, as part 1. This way the  > reader can reach a complete specfile,
> compliant with Fedora guidelines,  > quicker, and still get a feeling for
> resolving packaging quirks in the  > second part.
>  >
>  > In the future, basing the first tutorial on real packages should  > 
> probably
> be switched to hosting dedicated "test project", which avoid  > any quirks
> and can be packaged to Fedora requirements using only  > Fedora's set of
> RPM macros. Such package should also avoid GNU  > Autotools and be based
> on CMake or Meson, which are simpler to  > understand and more
> widespread today.
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an
> email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__docs.fedoraproject.org_en-2DUS_project_code-2Dof-
> 2Dconduct_=DwIGaQ=BSDicqBQBDjDI9RkVyTcHQ=H5QohD_RgGRTO
> mpJ5rew0X87YNwM_iH7SF9XZijdV0o=ZVYh2Pnj1mqVP5ceO87VGJein8O
> QF7fgyLfPmsvXyFeH6tl2Kb4aaz2DxgI9q2Qq=tFCi6cDadUhB1bZclnUCohaFJ
> rgTkvR5NnS-SHMxdHc=
> List Guidelines: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__fedoraproject.org_wiki_Mailing-5Flist-
> 5Fguidelines=DwIGaQ=BSDicqBQBDjDI9RkVyTcHQ=H5QohD_RgGRT
> OmpJ5rew0X87YNwM_iH7SF9XZijdV0o=ZVYh2Pnj1mqVP5ceO87VGJein8
> OQF7fgyLfPmsvXyFeH6tl2Kb4aaz2DxgI9q2Qq=LceMIV98ssz8tBj3dPpYKoU
> Q_6FtslD2n8OplfoD2Gs=
> List Archives: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__lists.fedoraproject.org_archives_list_devel-
> 40lists.fedoraproject.org=DwIGaQ=BSDicqBQBDjDI9RkVyTcHQ=H5Q
> ohD_RgGRTOmpJ5rew0X87YNwM_iH7SF9XZijdV0o=ZVYh2Pnj1mqVP5ce
> O87VGJein8OQF7fgyLfPmsvXyFeH6tl2Kb4aaz2DxgI9q2Qq=tUj2hgkHU9Ysg
> n51Pm4QTFm10zvnF42eY0r-1BdLZUc=
> Do not reply to spam, report it:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pagure.io_fedora-
> 2Dinfrastructure_new-
> 5Fissue=DwIGaQ=BSDicqBQBDjDI9RkVyTcHQ=H5QohD_RgGRTOmpJ
> 5rew0X87YNwM_iH7SF9XZijdV0o=ZVYh2Pnj1mqVP5ceO87VGJein8OQF7f
> gyLfPmsvXyFeH6tl2Kb4aaz2DxgI9q2Qq=H_CLa7ff1mo0zci91H2hQCFU8Q6jj
> c64N-4A_lQR_NU=


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: Reichspogromnacht (was: SPDX Statistics - Kristallnacht edition)

[Kenneth Goldman]

For the record, Americans use the term Kristallnacht, and American Jews do
not find it offensive.

It is used as the symbolic start date of the holocaust, and there are often
memorial services.

> > > Note that the term "Kristallnacht" (or "Reichskristallnacht") is
> > > itself a nazi propaganda term, and it is nowadays generally agreed
> > > in Austria and Germany that that term should not be used. Broken
> > > glass is just broken glass, not "crystal". And the term only
> > > (euphemistically) mentions the violence against things and neglects
> > > to mention the violence against people.


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: TSS maintainer volunteer - IBM TSS

[Kenneth Goldman]

I'm not 100% clear on the process.  I have a .spec file that passes fedpkg 
mockbuild.

I submitted the request to 
https://bugzilla.redhat.com/show_bug.cgi?id=2238052.

Is that all?  What else should I do?



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: invalid 'sshpubkey': invalid SSH public key

[Kenneth Goldman]

Thanks.

 

Knowing that it should work, I tried from Windows and it seems OK.  Newline 
issue perhaps.

 

BTW, that mailto was not in my original email.  Some Outlook 'value add', 
detecting the email address and trying to be helpful.  ☹

 

 

From: Kevin P. Fleming  
Sent: Wednesday, April 19, 2023 3:49 PM
To: devel@lists.fedoraproject.org
Subject: [EXTERNAL] Re: invalid 'sshpubkey': invalid SSH public key

 

On 4/19/23 15: 42, Kevin Fenzi wrote: On Wed, Apr 19, 2023 at 06: 45: 57PM 
+, Kenneth Goldman wrote: Newbie - first time . I'm trying to upload my SSH 
public key to my fedora project account. The web page gives me the above error. 
My key is 

ZjQcmQRYFpfptBannerStart




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd

On 4/19/23 15:42, Kevin Fenzi wrote:

On Wed, Apr 19, 2023 at 06:45:57PM +, Kenneth Goldman wrote:

Newbie - first time . I'm trying to upload my SSH public key to my fedora
project account. The web page gives me the above error.
 
My key is an RSA 4096 key.
 
ssh-rsa B3NzaC1yc2EDAQABAAACAQ .  y4lWQ== kgold...@us.ibm.com 
<mailto:kgold...@us.ibm.com> 
 <mailto:kgold...@us.ibm.com> <mailto:kgold...@us.ibm.com> 
 
Is that the wrong format?  Is RSA-4096 invalid.  In the file, the key has no
newlines.  Is that a problem?
 
It works on github and our internal git repo.

No, that should work fine. Make sure you put it all on one line and it
has the full format... ie, 
ssh-rsa the-key-ending-with== comment

Maybe thebit at the end is causing the issue?



-- 
Kevin P. Fleming
He/Him/His
Principal Program Manager, RHEL
Red Hat US/Eastern Time Zone


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

invalid 'sshpubkey': invalid SSH public key

[Kenneth Goldman]

Newbie - first time . I'm trying to upload my SSH public key to my fedora
project account. The web page gives me the above error.

My key is an RSA 4096 key.

ssh-rsa B3NzaC1yc2EDAQABAAACAQ .  y4lWQ== kgold...@us.ibm.com
 

Is that the wrong format?  Is RSA-4096 invalid.  In the file, the key has no
newlines.  Is that a problem?

It works on github and our internal git repo.

--
Work 1-914-945-2415




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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: Package Tutorial bug - another suggestion, section vs. macro

[Kenneth Goldman]

Here's another "surprise for the new user" that I suggest being added.

What does the % character mean?

Sometimes it's the beginning of a section.  Sometimes it's a macro.

I see now that the web page color codes the two differently,
but that's not obvious.

It would be helpful to explain that early and provide links
or other instructions on how to find the list of each.

Someone posted /usr/lib/rpm/macros for the list
of macros and suggested rpm -E macro to
view the expansion.


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fedpkg: Failed to get repository name from Git url or pushurl -> %build

[Kenneth Goldman]

> -Original Message-
> From: Vít Ondruch 
> Sent: Thursday, March 2, 2023 6:58 AM
> To: devel@lists.fedoraproject.org
> Subject: [EXTERNAL] Re: fedpkg: Failed to get repository name from Git url or
> pushurl
> 
> > How does it know what to build.  Does it default to configure;make
> > or something similar?
> 
> You have to specify what are the right steps in the `%build` sections.
> In the tutorial, there are used the `%configure` + `%make_build` macros.
> You could use different build commands (or macros) at this place.

This really helps!

Let's see if I have this right ...

%build
%configure
%make_build

are not three separate steps.  %build is the overall step, and the next two 
lines
are the build steps.  The blank line terminates the %build.  Correct?

Where are the macros defined?  I.e., %configure probably expands
to ./configure and %make_build to make. 

If I want to add some arguments to configure, and add an autoreconf
step before configure, how would I do that?






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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: Package Tutorial bug - missing BuildRequires gcc

[Kenneth Goldman]

> -Original Message-
> From: Jason Tibbitts 
> Sent: Wednesday, March 1, 2023 6:51 PM
> To: Kenneth Goldman 
> Cc: Development discussions related to Fedora 
> Subject: [EXTERNAL] Re: Package Tutorial bug - missing BuildRequires gcc
> 
> >>>>> Kenneth Goldman  writes:
> 
> > but … if the tutorial has a sample .spec file, I think it would help
> > the new user if it was 100% complete.
> 
> I believe that the section "A Complete hello.spec File" at
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__docs.fedoraproject.org_en-2DUS_package-2Dmaintainers_Packaging-
> 5FTutorial-5FGNU-5FHello_-23-5Fa-5Fcomplete-5Fhello-5Fspec-
> 5Ffile=DwIFaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
> mlmiA=eBYtndmk1vCkvHX6y2J15Jeb4NPWWyIr8LJxlHhQRhTpEaQ_m0uKlbT
> oGi5opX06=AcpJmiCpdwml9x3JU0z6dyLZo19mnWH66P6qtnJMlAs=
> is, as indicated, complete.  It does contain the necessary build dependency on
> gcc, as well as the others.  If I'm missing something, please feel free to 
> enlighten
> me.

I see.  This 'hello world' is structured to intentionally have errors.  This 
teaches
the reader how to debug.

I have no issue this approach except that it's unusual.  I suggest some text
at the top of the web page explaining this.

This will help the new student, who might be trained to 'stop reading
on the first error'.



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: Package Tutorial bug - missing BuildRequires gcc

[Kenneth Goldman]

Yes, but … if the tutorial has a sample .spec file, I think

it would help the new user if it was 100% complete.

 

From: Elliott Sales de Andrade  
Sent: Wednesday, March 1, 2023 3:38 PM
To: Development discussions related to Fedora 
Subject: [EXTERNAL] Re: Package Tutorial bug - missing BuildRequires gcc

 

On Wed, Mar 1, 2023 at 3: 35 PM Kenneth Goldman  wrote: 
https: //docs. fedoraproject. org/en-US/package-maintainers/Packaging_Tutorial_ 
GNU_Hello/ The tutorial says: Lines which are not needed (e. g. BuildRequires 
and 

ZjQcmQRYFpfptBannerStart




This Message Is From an Untrusted Sender 


You have not previously corresponded with this sender. 

ZjQcmQRYFpfptBannerEnd

 

On Wed, Mar 1, 2023 at 3:35 PM Kenneth Goldman mailto:kgold...@us.ibm.com> > wrote:

https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_ 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproject.org_en-2DUS_package-2Dmaintainers_Packaging-5FTutorial-5FGNU-5FHello_=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=oNAsMpfTvgxB_VUeQaKDPd94vgV-e2yQhC-wD0ftYY0067zgI2m7qaefZTLCnyMY=46qb9N1fyt9zC5T4qeWW9UyGxitVwd6IG-iDZXqVlb0=>
 
GNU_Hello/

The tutorial says:

Lines which are not needed (e.g. BuildRequires and Requires) can be
commented out with the hash # for now.

However, I believe that this line is needed.  I'm new so perhaps I'm missing
something.

BuildRequires: gcc

 

This is mentioned in the next step, is it not?

https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/#_building_the_package
 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproject.org_en-2DUS_package-2Dmaintainers_Packaging-5FTutorial-5FGNU-5FHello_-23-5Fbuilding-5Fthe-5Fpackage=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=oNAsMpfTvgxB_VUeQaKDPd94vgV-e2yQhC-wD0ftYY0067zgI2m7qaefZTLCnyMY=iTjU5R9y3T7J6s2ncvXrvWVetTVd9fWHV_WBX2krJKM=>
 

 

--

Elliott



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fedpkg: Failed to get repository name from Git url or pushurl

[Kenneth Goldman]

There's Source, Source0, and sources.  What are the definitions?

The tutorial doesn't have a 'sources' tag.  Is that documented?  What should
it be?

The hello tutorial has the URL to the tarball in Source: but it also says to 
use
wget to download the tarball.

The Source: tag doesn't have a list of files, just a pointer to the tarball.

Maybe I'm way off and the source files should be in a local directory?

When I run the tutorial, it seems to ignore the .spec URLs and uses the local
tarball.  How does it even know what the name is?  Does it default to the
file name of the URL?

How does it know what to build.  Does it default to configure;make
or something similar?

> -Original Message-
> From: Artur Frenszek-Iwicki 
> Sent: Wednesday, February 15, 2023 11:43 AM
> To: devel@lists.fedoraproject.org
> Subject: [EXTERNAL] RE: fedpkg: Failed to get repository name from Git url 
> or
> pushurl
>
> > Should that tutorial work?  Is it perhaps obsolete?
> I'd say the opposite of obsolete - it's been updated to suggest using fedpkg 
> all
> along the way, instead of the old rpmbuild tools. But it looks like it 
> wasn't tested
> enough to make sure everything works.
>
> > My newbie understanding is that fedpkg should get the source from the
> > Source0 location and then follow the build instructions.
> > Is that even close?
> This is a bit complicated. When the package is being built, the list of 
> files is taken
> from the Source: tags in the spec file. However, fedpkg keeps a separate 
> file,
> "sources" (no extension), where it lists files uploaded to the Fedora build 
> cache.
> The justification is that keeping source tarballs in the repository is a bad 
> idea,
> since these files can be really large (1GiB+ for game packages), so they're 
> stored
> in a cache instead, and the repository contains only this "sources" file 
> with
> references to said cache. (That being said, you totally can store source 
> files in
> the repo - this is often done with stuff like non-standard Fedora configs.)
>
> As for the "get the source from the Source0 location" bit - no.
> fedpkg will not download stuff from Source: tags for you, only the files 
> listed in
> the "sources" file.
>
> Since my impression is that you want to start experimenting with RPM 
> packaging
> in general, and not specifically fedpkg - I'll do a bit shameless 
> self-promotion
> and link to an article on RPM packaging that I wrote some time ago:
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__blog.svgames.pl_article_basics-2Dof-2Drpm-
> 2Dpackaging=DwIGaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=9Zy9a03p-
> GrtnAWrzttvmFX417X-C_WOqiZaQjuiv1_bUC_4VaDdANM4Cv-
> tBucE=ASsrhv8V4Ny-ujgsugfcpVLuPxEn578dICLLMx2eCYw=
>
> In this article, I show how to build RPM packages using the traditional 
> rpmbuild
> workflow. If you're just starting out with writing specs and such, it should 
> get
> you started enough to make switching to fedpkg later down the road a no-
> brainer.
>
> A.FI.
> ___
> devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an 
> email
> to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__docs.fedoraproject.org_en-2DUS_project_code-2Dof-
> 2Dconduct_=DwIGaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=9Zy9a03p-
> GrtnAWrzttvmFX417X-C_WOqiZaQjuiv1_bUC_4VaDdANM4Cv-
> tBucE=wgOj27qGmhxD4UEHTA9tqeAxCZr1ny0rPQPs7_SL2sQ=
> List Guidelines: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__fedoraproject.org_wiki_Mailing-5Flist-
> 5Fguidelines=DwIGaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=9Zy9a03p-
> GrtnAWrzttvmFX417X-C_WOqiZaQjuiv1_bUC_4VaDdANM4Cv-
> tBucE=cUh77057QE1qCKOAD2SsxFWibxM8aVJOWgvcuUM-1gI=
> List Archives: https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__lists.fedoraproject.org_archives_list_devel-
> 40lists.fedoraproject.org=DwIGaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=9Zy9a03p-
> GrtnAWrzttvmFX417X-C_WOqiZaQjuiv1_bUC_4VaDdANM4Cv-
> tBucE=WiPTKb0_GaJvkLzQAdKMxWSDV8qxvKguXGSvM8rqGgs=
> Do not reply to spam, report it:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__pagure.io_fedora-
> 2Dinfrastructure_new-5Fissue=DwIGaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=9Zy9a03p-
> GrtnAWrzttvmFX417X-C_WOqiZaQjuiv1_bUC_4VaDdANM4Cv-
> tBucE=FMdlaadJWvp1hsOPTPqy9TFB3w7W_bTTIYBf553Savs=


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: 

packaging tutorial error - /usr/bin/systemd-nspawn mock-chroot debug advice

[Kenneth Goldman]

https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/

~~~

when running that tutorial (Fedora 37, x86), I get this error:

ERROR: Exception(/home/kgold/hello/hello-2.10-1.fc37.src.rpm)
Config(fedora-37-x86_64) 0 minutes 18 seconds
INFO: Results and/or logs in: /home/kgold/hello/results_hello/2.10/1.fc37

~~~

The log has at the end:, but I suspect that the python issue is a reporting
issue, not the actual failure.

RPM build errors:
Child return code was: 1
EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M
d0156a2d35ca46a0ba55a993d05852c1 -D /var/lib/mock/fedora-37-x86_64/root -a
-u mockbuild --capability=cap_ipc_lock
--bind=/tmp/mock-resolv.lphffv1r:/etc/resolv.conf --bind=/dev/btrfs-control
--bind=/dev/mapper/control --bind=/dev/loop-control --bind=/dev/loop0
--bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4
--bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8
--bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe
--setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir
--setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin
--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"
--setenv=PS1= \\s-\\v\\$  --setenv=LANG=C.UTF-8
--resolv-conf=off bash --login -c /usr/bin/rpmbuild -bb  --target x86_64
--nodeps /builddir/build/SPECS/hello.spec\n', 1)]
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py",
line 93, in trace
result = func(*args, **kw)
 ^
  File "/usr/lib/python3.11/site-packages/mockbuild/util.py", line 598, in
do_with_status
raise exception.Error("Command failed: \n # %s\n%s" % (command, output),
child.returncode)
mockbuild.exception.Error: Command failed:

~

When I try /usr/bin/systemd-nspawn directly, I get this.  What directory is
it looking for? /var/lib/mock/fedora-37-x86_64/root exists.  I don't run as
root, right?

mock-chroot: No such file or directory.

--
Work 1-914-945-2415



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Package Tutorial bug - missing BuildRequires gcc

[Kenneth Goldman]

https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/

The tutorial says:

Lines which are not needed (e.g. BuildRequires and Requires) can be
commented out with the hash # for now.

However, I believe that this line is needed.  I'm new so perhaps I'm missing
something.

BuildRequires: gcc

--
Work 1-914-945-2415



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: TSS maintainer volunteer

[Kenneth Goldman]

> -Original Message-
> From: Peter Robinson 
> Sent: Friday, February 17, 2023 4:20 AM
> To: Development discussions related to Fedora 
> 
> Subject: [EXTERNAL] Re: TSS maintainer volunteer
>
> On Fri, Feb 17, 2023 at 9:04 AM Petr Pisar  wrote:
> >
> > V Thu, Feb 16, 2023 at 07:29:07PM +, Kenneth Goldman napsal(a):
> > > I think I followed all those steps - identifying the package,
> > > announcing that I want to be the packager, making an account, etc.
> > >
> > > What's next?
> >
> > Submit an updated tss2 package for a package review. As far as I can
> > see, there is no review opened for tss2 now
>
> It was only retired on Jan 9th so should not need a re-review.
>
> I think the process needs to be:
> 1) get a package sponsor. If you don't have one I can possibly do it as I 
> co-
> maintain the intel tpm2 packages

Can you get me a sponsor / sponsor it?  That seems to be the next step.

> 2) request ownership and unblocking of the package

How do I do that?  I did the Pagure, releng tickets

#559 tss2, tss2-devel package maintainer
#11294 Unretire tss2, tss2-devel

> 3) build new versions as follow the process.

I'm working through the tutorial.  If you have an alternate HOWTO, let me 
know.

>
> > <https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__bugzilla.redhat.com_buglist.cgi-3Fcomponent-3DPackage-2520Review-
> 26product-3DFedora-26short-5Fdesc-3Dtss2-26short-5Fdesc-5Ftype-
> 3Dallwordssubstr=DwIGaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
> mlmiA=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9-
> uwvnxzuXat8ZLOJ_EwPWbbZ=ChnuonR2xzfsR-
> 55TVKYnZojmhjceqrcSRl9S_URRow= >.
> > How to do it is described at
> > <https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__docs.fedoraproject.org_en-2DUS_package-2Dmaintainers_Package-
> 5FReview-5FProcess_-23-5Fcontributor=DwIGaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
> mlmiA=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9-
> uwvnxzuXat8ZLOJ_EwPWbbZ=69hUQdHPBi7Qv8EFcTVNjiZd880oTiPox9hM0rB
> oKtg= >.
> > Especially pay attention to:
> >
> > If you are not member of the packager group, you need a sponsor. Add
> > FE-NEEDSPONSOR to the bugs being blocked by your review request.
> >
> > > Does someone approve me?
> >
> > Based on the FE-NEEDSPONSOR blocker someone from sponsors should
> > notice your review request and start to communicate with you in the
> > review request in Bugzilla. (If that does not happen, approach you a
> > sponsor of your choice as recommended at
> > <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproje
> > ct.org_en-2DUS_package-2Dmaintainers_How-5Fto-5FGet-5FSponsored-
> 5Finto
> > -5Fthe-5FPackager-5FGroup_-23how-5Fto-5Ffind-5Fa-
> 5Fsponsor=DwIGaQ=
> > jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-
> mlmiA
> > =LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9-
> uwvnxzuXat8ZLOJ_EwPWbbZ=wQ
> > 0j4l0zTDLd6Wcb3Easz-QF-q_MukicKUX5PjsECMU= >)
> >
> > Once the sponsor finds your package looks good and you understand how
> > to maintain a package, he/she will sponsor you, i.e. adds you into a
> > packagers group. Then you will be able to continue from this item on
> > the Package_Review_Process document:
> >
> > When your package passes the review you should use fedpkg to request a
> Git
> > repository for it.
> >
> > > Move a git repo somewhere?
> >
> > For the purpose of the package review, you need to publish the spec
> > file and the SRPM file somewhere on the Internet. (Once you become a
> > packager, you can also use
> > <https://urldefense.proofpoint.com/v2/url?u=https-3A__fedorapeople.org
> > _=DwIGaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-
> O1GZkt
> > Ffre1-mlmiA=LENjKgA1o8jJJQUeUgkw1NFO085ft2GxJNSWS6C9-
> uwvnxzuXat8ZLOJ
> > _EwPWbbZ=W-SMTTNywFjnciP-Cj5_16Zh9LkcQDkEAEitLklonsA= > server
> for
> > that purpose.)
> >
> > Once the package review passes, the offical git repository (called
> > dist-git in
> > Fedora) for the tss2 package will be reopened with completing this item:
> >
> > Request a Git repository for the package
> >
> > Then you will commit the new spec file into the reopen dist-git 
> > repository.
> >
> > -- Petr
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org To unsubscribe
> > send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct:
> > https://urldefense.proofpoint.com/v2/url

RE: TSS maintainer volunteer

[Kenneth Goldman]

I think I followed all those steps - identifying the package, announcing that 
I want to be the packager, making an account, etc.

What's next?  Does someone approve me?  Are there more steps?  Other accounts 
to make?  Move a git repo somewhere?

> -Original Message-
> From: Petr Pisar 
> Sent: Wednesday, February 15, 2023 3:29 AM
> To: devel@lists.fedoraproject.org
> Subject: [EXTERNAL] Re: TSS maintainer volunteer
>
> V Tue, Feb 14, 2023 at 07:37:30PM +, Kenneth Goldman napsal(a):
> > How do I get packager status?  How do I work with a packager - is that
> > a person or a program?
> >
> > A quick google gave me this link:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraprojec
> > t.org_en-2DUS_package-2Dmaintainers_Joining-5Fthe-5FPackage-5FMaintain
> > ers_=DwMFaQ=jf_iaSHvJObTbx-
> siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1G
> > ZktFfre1-mlmiA=s70Bz9k22m9018JPgVNOAnmz7DqkzTJI_QXmAfcI-
> pzZbLnQwyYpg
> > p0rgTxhQ1Hg=3fAYyQr_EQBDWPP3121TuoPS_dDADrPuxuTVcuf5W88=
> >
> > I found that and followed all the steps.  However, it ends at Finding
> > software you wish to maintain for Fedora".
> >
> You wrote you were interested in tss2 package. Since the package was retired
> from Fedora, it's a great piece of "software to maintain" for you.
>
> > What's next?
>
> There is a subchapter
> <https://docs.fedoraproject.org/en-US/package-
> maintainers/How_to_Get_Sponsored_into_the_Packager_Group/>
> of the Joining page. (A chapter topology is shown in the left column, 
> JavaScript
> required. I also find it hard to discover.)
>
> You basically wants to unretire the package 
> <https://docs.fedoraproject.org/en-
> US/package-maintainers/Package_Retirement_Process/#claiming>.
> That involves reviewing the package
> <https://docs.fedoraproject.org/en-US/package-
> maintainers/Package_Review_Process/>
> and getting a sponsor who will guide you and who will adds you to the 
> packager
> group after finishing the package review.
>
> Your path is a little bit atypical because the documentation is written from 
> a
> point of view of a new packager who wants to add a completely new package
> <https://docs.fedoraproject.org/en-US/package-
> maintainers/New_Package_Process_for_New_Contributors/>.
> You can follow it. The only difference for unretiring packages is a way of
> creating a dist-git repository after passing the review and gettig 
> sponsored.
>
> -- Petr


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fedpkg: Failed to get repository name from Git url or pushurl - solved

[Kenneth Goldman]

> -Original Message-
> From: Miro Hrončok 
> Sent: Thursday, February 16, 2023 8:56 AM
> To: Kenneth Goldman ;
> devel@lists.fedoraproject.org
> Subject: [EXTERNAL] Re: fedpkg: Failed to get repository name from Git url or
> pushurl - solved
> 
> On 16. 02. 23 14:50, Kenneth Goldman wrote:
> > Could not execute mockbuild: Could not query n-v-r of hello: 'utf-8' codec
> can't decode byte 0x93 in position 259: invalid start byte
> 
> That indicates it's not actually UTF-8.

I can only report when I cut and paste the smart quotes
from the web page to the .spec file (Firefox -> emacs), I
get 0x93 and 0x94 and fedpkg reports that error.

The 'utf-8' codec text came from the error message. 


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fedpkg: Failed to get repository name from Git url or pushurl - solved

[Kenneth Goldman]

> -Original Message-
> From: Miro Hrončok 
> Sent: Wednesday, February 15, 2023 5:19 PM
> To: Development discussions related to Fedora ;
> Kenneth Goldman 
> Subject: [EXTERNAL] Re: fedpkg: Failed to get repository name from Git url or
> pushurl - solved
> 
> On 15. 02. 23 22:48, Kenneth Goldman wrote:
> > However, the %Description item has some 'smart quotes', which cut and
> > paste as utf-something.  fedpkg doesn't like those characters.
> 
> What does "fedpkg doesn't like those characters" actually mean? I don't 
> believe
> fedpkg validates the %description and UTF-8 should be totally OK in
> %description RPM-wise.
> 
>   1. What did you do?
>   2. What did you expect to happen?
>   3. What happened instead?

fedpkg is definitely parsing the %description, because the error does not
occur when I delete the characters.

I typed:

> fedpkg --release f37 mockbuild

I expected a build.  What happened was that I got the message in the email 
subject line, repeating forever:

> fedpkg --release f37 mockbuild
Failed to get repository name from Git url or pushurl
Failed to get ns from Git url or pushurl
Failed to get repository name from Git url or pushurl
Failed to get ns from Git url or pushurl
Failed to get repository name from Git url or pushurl
Failed to get ns from Git url or pushurl
Failed to get repository name from Git url or pushurl
Failed to get ns from Git url or pushurl

Someone suggested a different command line (not the one from the tutorial), 
which helped me debug.  I don't know what n-v-r is, but 0x93 came from the web 
page smart quote.  The end quote pastes as 0x94, but the parser doesn't get 
that far.

> fedpkg --release f37 --name hello mockbuild
sources file doesn't exist. Source files download skipped.
Could not execute mockbuild: Could not query n-v-r of hello: 'utf-8' codec 
can't decode byte 0x93 in position 259: invalid start byte


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fedpkg: Failed to get repository name from Git url or pushurl - solved

[Kenneth Goldman]

If a maintainer of the packaging tutorial at

https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/

is listening ...  There is a sample spec file.  An obvious step for a newbie 
after
running rpmdev-newspec is to cut and paste from the web page sample to
.spec file.

However, the %Description item has some 'smart quotes', which
cut and paste as utf-something.  fedpkg doesn't like those
characters.

I suggest removing the quotes from the description.



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fedpkg: Failed to get repository name from Git url or pushurl

[Kenneth Goldman]

> -Original Message-
> From: Artur Frenszek-Iwicki 
> Sent: Tuesday, February 14, 2023 6:03 PM
> To: devel@lists.fedoraproject.org
> Subject: [EXTERNAL] Re: fedpkg: Failed to get repository name from Git url 
> or
> pushurl
>
> > Is there another argument to fedpkg?
> fedpkg has a --name argument, you can try using that.

I tried:

> fedpkg --release f37 --name hello mockbuild
sources file doesn't exist. Source files download skipped.
Could not execute mockbuild: Could not query n-v-r of hello: 'utf-8' codec 
can't decode byte 0x93 in position 194: invalid start byte

The spec file has this contents, right from the tutorial, and the tarball does 
exist there.

Version:2.10
Source0:https://ftp.gnu.org/gnu/hello/hello-%{version}.tar.gz

>
> Alternatively, if you're just taking your first steps with packaging, you 
> can try:
> $ rpmbuild -bs path/to/your.spec
> $ mock path/to/file-created-by-previous-command.srpm
>
> This will first build an SRPM ("source rpm"), and then build it in mock, 
> which is
> pretty much exactly what "fedpkg mockbuild" does.

My .spec file is the one from the tutorial at

https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/

Should that tutorial work?  Is it perhaps obsolete?

My newbie understanding is that fedpkg should get the source from the Source0 
location and then follow the build instructions.  Is that even close?




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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: TSS maintainer volunteer

[Kenneth Goldman]

From: Peter Robinson 
Sent: Monday, February 13, 2023 4:57 PM
To: Development discussions related to Fedora 
Subject: [EXTERNAL] Re: TSS maintainer volunteer
jQcmQRYFpfptBannerEnd

On Mon, Feb 13, 2023 at 9:16 PM Kenneth Goldman <mailto:kgold...@us.ibm.com> 
wrote:
I have a fedora account.

How do I get packager status?  How do I work with a packager - is that a 
person or a program?

A quick google gave me this link: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproject.org_en-2DUS_package-2Dmaintainers_Joining-5Fthe-5FPackage-5FMaintainers_=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=s70Bz9k22m9018JPgVNOAnmz7DqkzTJI_QXmAfcI-pzZbLnQwyYpgp0rgTxhQ1Hg=3fAYyQr_EQBDWPP3121TuoPS_dDADrPuxuTVcuf5W88=

I found that and followed all the steps.  However, it ends at Finding software 
you wish to maintain for Fedora".

What's next?


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

fedpkg: Failed to get repository name from Git url or pushurl

[Kenneth Goldman]

https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_
GNU_Hello/

Working through the basic tutorial there:

fedpkg --release f37 mockbuild

fails with

Failed to get repository name from Git url or pushurl
Failed to get ns from Git url or pushurl
[repeats forever]

How does fedpkg know what to build?  Does it default to whatever .spec file
exists?
Is there another argument to fedpkg. Are there some other steps between
Rpmdev-newspec and fedpkg?

What am I missing?


--
Work 1-914-945-2415



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fkinit -u instructions

[Kenneth Goldman]

> -Original Message-
> From: Clemens Lang 
> Sent: Tuesday, February 14, 2023 12:59 PM
> To: Development discussions related to Fedora

> >> Someone posted that the prompt for an OTP can be ignored and that the
> >> Fedora password is enough.
> >
> > IIRC, if you *have* an OTP, you have to include it. If you *don't*
> > have one, of course you just put your password. We should make this
> > clear too (assuming I'm right).
> 
> You are right, but fkinit will tell you, so I don’t think we need to clarify 
> this in
> the documentation:
> 
> 
> :) cllang@frootmig:~$ fkinit -u clang
> Enter your password and OTP concatenated. (Ignore that the prompt is for
> only the token) Enter OTP Token Value:
> :) cllang@frootmig:~$

For a newbie (me), it's not clear what the OTP is.  Is it something from here?

https://accounts.fedoraproject.org/user/kgold/settings/otp/

If correct, might a link be useful, along with some guidance on then to use it?



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: fkinit -u instructions

[Kenneth Goldman]

Yes, much better, thanks.

Someone posted that the prompt for an OTP can be ignored and that the Fedora 
password is enough.

An explanation of the Kerberos ticket - why it's needed, how long it lasts, 
what fails when it expires, etc. - would be useful.

> -Original Message-
> From: Petr Pisar 
> Sent: Tuesday, February 14, 2023 11:28 AM
> To: devel@lists.fedoraproject.org
> Subject: [EXTERNAL] Re: fkinit -u instructions
>
> V Tue, Feb 14, 2023 at 04:04:06PM +0100, blinxen napsal(a):
> > > 1. fas_id is not defined.  Is it my local Linux user ID, my Fedora
> > > login
> > ID, or something else?
> >
> > "fas_id" is your FAS (Fedora Account) name, for me this would be 
> > "blinxen".
> >
> > > Is password my local or Fedora password?
> >
> > It is your FAS (Fedora Account) password
> >
> Does this make the documentation more understandable
> ?
>
> -- Petr


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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

fkinit -u instructions

[Kenneth Goldman]

I'm working through the Packager instructions at

https://docs.fedoraproject.org/en-US/package-maintainers/Installing_Packager
_Tools/

There is a step:

$ fkinit -u 

1.  fas_id is not defined.  Is it my local Linux user ID, my Fedora
login ID, or something else?
2.  When I try it, I get

Enter your password and OTP concatenated. (Ignore that the prompt is for
only the token)

Is password my local or Fedora password?
What would my OTP be?

--
Work 1-914-945-2415




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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

RE: TSS maintainer volunteer

[Kenneth Goldman]

I have a fedora account.

 

How do I get packager status?  How do I work with a packager - is that a person 
or a program?

 

From: Stephen Smoogen  
Sent: Friday, February 10, 2023 3:04 PM
To: Development discussions related to Fedora 
Subject: [EXTERNAL] Re: TSS maintainer volunteer

 

On Fri, 10 Feb 2023 at 14: 56, Simo Sorce  wrote: On Fri, 
2023-02-10 at 19: 49 +, Kenneth Goldman wrote: > I would like to volunteer 
to maintain the two TSS packages in Fedora: tss2, tss2-devel. > > I currently 

ZjQcmQRYFpfptBannerStart




This Message Is From an External Sender 


This message came from outside your organization. 

ZjQcmQRYFpfptBannerEnd

 

 

On Fri, 10 Feb 2023 at 14:56, Simo Sorce mailto:s...@redhat.com> > wrote:

On Fri, 2023-02-10 at 19:49 +, Kenneth Goldman wrote:
> I would like to volunteer to maintain the two TSS packages in Fedora: tss2, 
> tss2-devel.
> 
> I currently maintain the source.
> 
> I would appreciate any tips on what steps I should take.

I think you should contact the current maintainer first.

 

The package tss2 is currently orphaned. I think that is why they are asking 
here. 

 

Keith, 

The first step you will need to do is create a Fedora account and working with 
a packager on how Fedora packages things up and getting packager status. tss2 
and tss2-devel are built from the tss2 package 
https://src.fedoraproject.org/rpms/tss2 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__src.fedoraproject.org_rpms_tss2=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=CkM4kwDWDkch-KSoO9YPAInQlcU2axk2uv9hDBHot4d4LqAEhs7XtsDUAlC4sH1b=mxemcSKg9Z1JKkmR5m9QVbemgC7G-SHhP3uszflAKkE=>
  (that is the canonical place for the RPM spec file). 

 

 

Simo.

-- 
Simo Sorce
RHEL Crypto Team
Red Hat, Inc


___
devel mailing list -- devel@lists.fedoraproject.org 
<mailto:devel@lists.fedoraproject.org> 
To unsubscribe send an email to devel-le...@lists.fedoraproject.org 
<mailto:devel-le...@lists.fedoraproject.org> 
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/ 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.fedoraproject.org_en-2DUS_project_code-2Dof-2Dconduct_=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=CkM4kwDWDkch-KSoO9YPAInQlcU2axk2uv9hDBHot4d4LqAEhs7XtsDUAlC4sH1b=6WeorCS4JVV3gcHlA1Xs4bCCwDKeA3pLs_nIP1xVlTY=>
 
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Mailing-5Flist-5Fguidelines=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=CkM4kwDWDkch-KSoO9YPAInQlcU2axk2uv9hDBHot4d4LqAEhs7XtsDUAlC4sH1b=JJe4latIftUWbfqYo9rmQ7X_8QSnXUI6TnZczAWIsc4=>
 
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproject.org_archives_list_devel-40lists.fedoraproject.org=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=CkM4kwDWDkch-KSoO9YPAInQlcU2axk2uv9hDBHot4d4LqAEhs7XtsDUAlC4sH1b=jQVI7OT6ohMYxrOiOP-W-7HuXRa2qO8w2z-Mmnxb4ng=>
 
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue 
<https://urldefense.proofpoint.com/v2/url?u=https-3A__pagure.io_fedora-2Dinfrastructure_new-5Fissue=DwMFaQ=jf_iaSHvJObTbx-siA1ZOg=DZCVG43VcL8GTneMZb8k8lEwb-O1GZktFfre1-mlmiA=CkM4kwDWDkch-KSoO9YPAInQlcU2axk2uv9hDBHot4d4LqAEhs7XtsDUAlC4sH1b=-xzGnQaCLNYTMUxRI9yLFbCOHFNkUkZW4SvrrRW1xvM=>
 




 

-- 

Stephen Smoogen, Red Hat Automotive

Let us be kind to one another, for most of us are fighting a hard battle. -- 
Ian MacClaren



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, report it: 
https://pagure.io/fedora-infrastructure/new_issue

TSS maintainer volunteer

[Kenneth Goldman]

I would like to volunteer to maintain the two TSS packages in Fedora: tss2, 
tss2-devel.

I currently maintain the source.

I would appreciate any tips on what steps I should take.
___
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