public inbox for gentoo-guru@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-guru] Getting setup questions.
@ 2022-04-09 19:27 Philippe Chaintreuil
  2022-04-09 19:54 ` Andrew Ammerlaan
  0 siblings, 1 reply; 3+ messages in thread
From: Philippe Chaintreuil @ 2022-04-09 19:27 UTC (permalink / raw
  To: gentoo-guru

Greetings all!


I've just been added to the GURU project, and I have a few questions. 
Feel free to point me to "RTFM" that cover these if they exist.


1.  Following along with the "Information for Contributors" page[1] I'm 
getting an error when attempting to run "pkgdev commit" on a local branch.

=====================================================================
pkgdev commit: error: repo init failed: repo 'guru' at path 
'/home/peep/git/guru' has missing masters: 'gentoo'
=====================================================================

Google's not giving me very good results for that error and this is my 
first pkgdev use.  (I've used repoman in the past.)  Does pkgdev only 
work in ebuild repositories?  Should this git checkout be converted into 
one?


2.  What's the protocol for committing to "dev" and getting it reviewed 
by a trusted contributor?  Are people just always watching for new 
submissions, or do I need to post somewhere?  (I'm used to making Github 
pull requests.)


Thanks in advance!

           -- Philippe Chaintreuil



[1] https://wiki.gentoo.org/wiki/Project:GURU/Information_for_Contributors


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-guru] Getting setup questions.
  2022-04-09 19:27 [gentoo-guru] Getting setup questions Philippe Chaintreuil
@ 2022-04-09 19:54 ` Andrew Ammerlaan
  2022-04-12 15:48   ` Philippe Chaintreuil
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Ammerlaan @ 2022-04-09 19:54 UTC (permalink / raw
  To: gentoo-guru

On 09/04/2022 21:27, Philippe Chaintreuil wrote:
> Greetings all!
> 
> 
> I've just been added to the GURU project, and I have a few questions. 
> Feel free to point me to "RTFM" that cover these if they exist.
> 
> 
> 1.  Following along with the "Information for Contributors" page[1] I'm 
> getting an error when attempting to run "pkgdev commit" on a local branch.
> 
> =====================================================================
> pkgdev commit: error: repo init failed: repo 'guru' at path 
> '/home/peep/git/guru' has missing masters: 'gentoo'
> =====================================================================
> 
> Google's not giving me very good results for that error and this is my 
> first pkgdev use.  (I've used repoman in the past.)  Does pkgdev only 
> work in ebuild repositories?  Should this git checkout be converted into 
> one?

This error indicates that pkgdev can't find ::gentoo. Do you have an 
entry for ::gentoo in your repos.conf? Did you perhaps include the main 
Gentoo repository under a different name?

> 2.  What's the protocol for committing to "dev" and getting it reviewed 
> by a trusted contributor?  Are people just always watching for new 
> submissions, or do I need to post somewhere?  (I'm used to making Github 
> pull requests.)

You can just directly commit and push to the dev branch. Every now and 
then a trusted contributor will check all the new commits and push them 
to the master branch.

> 
> Thanks in advance!
> 
>            -- Philippe Chaintreuil
> 
> 
> 
> [1] https://wiki.gentoo.org/wiki/Project:GURU/Information_for_Contributors
> 

Best regards,
Andrew


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [gentoo-guru] Getting setup questions.
  2022-04-09 19:54 ` Andrew Ammerlaan
@ 2022-04-12 15:48   ` Philippe Chaintreuil
  0 siblings, 0 replies; 3+ messages in thread
From: Philippe Chaintreuil @ 2022-04-12 15:48 UTC (permalink / raw
  To: gentoo-guru

On 4/9/2022 3:54 PM, Andrew Ammerlaan wrote:
> On 09/04/2022 21:27, Philippe Chaintreuil wrote:
>> =====================================================================
>> pkgdev commit: error: repo init failed: repo 'guru' at path 
>> '/home/peep/git/guru' has missing masters: 'gentoo'
>> =====================================================================
> 
> This error indicates that pkgdev can't find ::gentoo. Do you have an 
> entry for ::gentoo in your repos.conf? Did you perhaps include the main 
> Gentoo repository under a different name?

	Thanks!

	Seems this was happening because my install is so ancient I still had 
PORTDIR=/usr/portage (and it's DISTDIR + PKGDIR friends) in my 
/etc/portage/make.conf.
	My /etc/portage/repos.d/eselect-repo.conf had a "gentoo" repo defined 
and "location = /var/db/repos/gentoo", but PORTDIR was overriding this 
as demonstrated by running "portageq get_repo_path / gentoo" [which 
returned /usr/portage].  I'm guessing this disconnect was what was 
confusing pkgdev.  (/var/db/repos/gentoo did not exist.)

	I followed the instructions by John R. Graham in this forum comment and 
pkgdev seems happy: 
https://forums.gentoo.org/viewtopic-t-1102294.html#8373904

	(Now I'll just have to re-train my fingers -- they've been typing 
"/usr/portage" for over 15 years.)

>> 2.  What's the protocol for committing to "dev" and getting it 
>> reviewed by a trusted contributor?  Are people just always watching 
>> for new submissions, or do I need to post somewhere?  (I'm used to 
>> making Github pull requests.)
> 
> You can just directly commit and push to the dev branch. Every now and 
> then a trusted contributor will check all the new commits and push them 
> to the master branch.

	Thanks again for the answers!  Off to go make my first commit.


				-- Philippe Chaintreuil


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2024-11-24 22:47 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-04-09 19:27 [gentoo-guru] Getting setup questions Philippe Chaintreuil
2022-04-09 19:54 ` Andrew Ammerlaan
2022-04-12 15:48   ` Philippe Chaintreuil

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox