Re: unable to branch to epel8

[Kevin Fenzi]

On 8/20/19 8:50 AM, Dave Love wrote:
> Kevin Fenzi  writes:
> 
>> Hum. I see you have a lot of custom rules. Sadly the interface for doing
>> rules is confusing and over detailed. Would you be willing to do the
>> reset on them, then slowly re-add the filtering out of ones you don't
>> want? I think something in your rules is negating each ruleset and
>> making it not send anything.
> 
> To follow up on this, after reset the rules I am now at least getting a
> lot more (including stuff from CentOS??).  I wonder why that worked now
> when it didn't before...  Anyhow, thanks for getting me to try again,
> despite the quote about insanity attributed to Einstein.

Glad it's working at least somewhat for you now.

The CentOS messages are likely from centos-ci... Fedora uses the CentOS
CI setup to run tests on packages. :)

kevin




signature.asc
Description: OpenPGP digital 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

Re: unable to branch to epel8

[Dave Love]

Kevin Fenzi  writes:

> Hum. I see you have a lot of custom rules. Sadly the interface for doing
> rules is confusing and over detailed. Would you be willing to do the
> reset on them, then slowly re-add the filtering out of ones you don't
> want? I think something in your rules is negating each ruleset and
> making it not send anything.

To follow up on this, after reset the rules I am now at least getting a
lot more (including stuff from CentOS??).  I wonder why that worked now
when it didn't before...  Anyhow, thanks for getting me to try again,
despite the quote about insanity attributed to Einstein.
___
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

Re: unable to branch to epel8

[Dave Love]

Kevin Fenzi  writes:

> Let me step back a bit here...
>
> pagure.io is a general source forge for open source projects. It's run
> by Fedora Infrastructure, but it uses another domain so people don't
> think they have to only use it for Fedora related projects.
>
> src.fedoraproject.org is also running a pagure instance in front of the
> Fedora rpms/modules/containers/flatpacks. This also is run by Fedora
> Infrastructure.
>
> I am guessing you are talking about the src.fedoraproject.org instance
> here? But it would help to know so we can debug in the right place.

I think I'm talking about both (and probably other services).  I assume
it's at least clear how this can be confusing, especially as there are
multiple places to raise issues.

> Hum. I see you have a lot of custom rules. Sadly the interface for doing
> rules is confusing and over detailed. Would you be willing to do the
> reset on them, then slowly re-add the filtering out of ones you don't
> want? I think something in your rules is negating each ruleset and
> making it not send anything.

I've been through the resetting business more than once, and that state
was from changing things to see if it changed anything.  At times I've
had things come through and then stop for no apparent reason, but then
it's difficult to know what should appear.  (I agree about the
interface, especially as it contains stuff I didn't think existed now.)
I've reset again, anyhow.  Thanks for the help.
___
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

Re: unable to branch to epel8

[Dave Love]

Miro Hrončok  writes:

>> Remote: Creating a new reference/branch is not allowed in this project.
>> To ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv
>>   ! [remote rejected] epel8 -> epel8 (pre-receive hook declined)
>> error: failed to push some refs to
>> 'ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv'
>
> Try going to https://src.fedoraproject.org/rpms/procenv/settings#hooks-tab
>
> Click *Prevent creating new branches by git push*
> Uncheck *Active*
> Click *Update*
>
> push
>
> Check *Active*
> Click *Update*

Success -- thanks!  There's clearly something wrong with the branch
creation, though, as I've had several fail to create the branches, so I
assume this will be useful to others.
___
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

Re: unable to branch to epel8

[Kevin Fenzi]

On 8/16/19 2:40 AM, Dave Love wrote:
> Kevin Fenzi  writes:
> 
>>> Also, I don't get any notifications from pagure (as with various other
>>> -- most? -- services), despite turning on anything relevant-looking in
>>> the notifications app.  I've asked several times about lack of
>>> notifications with no luck or suggestions how to debug it.  Can anyone
>>> make any suggestions now?
>>
>> Can you expand on 'any notifications from pagure' ? pagure.io?
>> src.fedoraproject.org? what sort of notifications?
> 
> I don't know exactly what should be sending them, and quite what's
> covered by pagure.  It's thoroughly confusing, especially when you have
> to interact with something apparently outside Fedora/Red Hat.

Let me step back a bit here...

pagure.io is a general source forge for open source projects. It's run
by Fedora Infrastructure, but it uses another domain so people don't
think they have to only use it for Fedora related projects.

src.fedoraproject.org is also running a pagure instance in front of the
Fedora rpms/modules/containers/flatpacks. This also is run by Fedora
Infrastructure.

I am guessing you are talking about the src.fedoraproject.org instance
here? But it would help to know so we can debug in the right place.

> I get no notifications for instance for closed tickets or modifications
> to repos for my packages (which I might reasonably want to know about
> when others make them).  I don't know if I should get anything from
> Koschei about failures, but I don't.  Also release-monitoring now seems
> broken.
> 
>> Can you point to a thing that should have notificed you?
> 
> Recent mass modifications to packages, for instance.  I often make mods
> to a checkout and then find I have to merge them with changes I didn't
> know about.

Hum. I see you have a lot of custom rules. Sadly the interface for doing
rules is confusing and over detailed. Would you be willing to do the
reset on them, then slowly re-add the filtering out of ones you don't
want? I think something in your rules is negating each ruleset and
making it not send anything.

Just click on the party perished and it should give you the default set.
See if you get notifications there, if not, we need to look more. If so,
you can one at a time add the filters you want.

kevin





signature.asc
Description: OpenPGP digital 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

Re: unable to branch to epel8

[Miro Hrončok]

On 16. 08. 19 11:13, Dave Love wrote:

Robert-André Mauchin  writes:


The PDC is the Product Definition Center:


Thanks.


Your package has already a EPEL8 branch in the PDC:
https://pdc.fedoraproject.org/rest_api/v1/component-branches/?
global_component=procenv

If the branch has not been created in dist-git, you can create it manually:

git checkout -b epel8
git push --set-upstream origin epel8


Thanks again, but that fails:

Remote: Creating a new reference/branch is not allowed in this project.
To ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv
  ! [remote rejected] epel8 -> epel8 (pre-receive hook declined)
error: failed to push some refs to 
'ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv'


Try going to https://src.fedoraproject.org/rpms/procenv/settings#hooks-tab

Click *Prevent creating new branches by git push*
Uncheck *Active*
Click *Update*

push

Check *Active*
Click *Update*



--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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

Re: unable to branch to epel8

[Robert-André Mauchin]

On Friday, 16 August 2019 11:13:56 CEST Dave Love wrote:
> Robert-André Mauchin  writes:
> 
> 
> > The PDC is the Product Definition Center:
> 
> 
> Thanks.
> 
> 
> > Your package has already a EPEL8 branch in the PDC:
> > https://pdc.fedoraproject.org/rest_api/v1/component-branches/?
> > global_component=procenv
> >
> >
> >
> > If the branch has not been created in dist-git, you can create it
> > manually:
>
> >
> >
> > git checkout -b epel8
> > git push --set-upstream origin epel8
> 
> 
> Thanks again, but that fails:
> 
> Remote: Creating a new reference/branch is not allowed in this project.
> To ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv
>  ! [remote rejected] epel8 -> epel8 (pre-receive hook declined)
> error: failed to push some refs to
> 'ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv'


Weird. Then file a releng ticket explaining the situation:
https://pagure.io/releng/issues

___
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

Re: unable to branch to epel8

[Dave Love]

Kevin Fenzi  writes:

>> Also, I don't get any notifications from pagure (as with various other
>> -- most? -- services), despite turning on anything relevant-looking in
>> the notifications app.  I've asked several times about lack of
>> notifications with no luck or suggestions how to debug it.  Can anyone
>> make any suggestions now?
>
> Can you expand on 'any notifications from pagure' ? pagure.io?
> src.fedoraproject.org? what sort of notifications?

I don't know exactly what should be sending them, and quite what's
covered by pagure.  It's thoroughly confusing, especially when you have
to interact with something apparently outside Fedora/Red Hat.

I get no notifications for instance for closed tickets or modifications
to repos for my packages (which I might reasonably want to know about
when others make them).  I don't know if I should get anything from
Koschei about failures, but I don't.  Also release-monitoring now seems
broken.

> Can you point to a thing that should have notificed you?

Recent mass modifications to packages, for instance.  I often make mods
to a checkout and then find I have to merge them with changes I didn't
know about.

> This is probibly best as a infrastructure ticket, feel free to file
> there: https://pagure.io/fedora-infrastructure/issues
>
> and we will get to the bottom of it.
>
>> I'm increasingly un-motivated to do maintenance particularly because of
>> continual infrastructure problems.
>
> Very sorry to hear it. We are trying the best we can with the resources
> we have. ;(

I'm sure, and thanks.  The continual churn clearly isn't helping either
people trying to keep services running, or maintainers trying to use
them, especially when they go backwards in functionality.
___
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

Re: unable to branch to epel8

[Dave Love]

Robert-André Mauchin  writes:

> The PDC is the Product Definition Center:

Thanks.

> Your package has already a EPEL8 branch in the PDC:
> https://pdc.fedoraproject.org/rest_api/v1/component-branches/?
> global_component=procenv
>
> If the branch has not been created in dist-git, you can create it manually:
>
> git checkout -b epel8
> git push --set-upstream origin epel8

Thanks again, but that fails:

Remote: Creating a new reference/branch is not allowed in this project.
To ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv
 ! [remote rejected] epel8 -> epel8 (pre-receive hook declined)
error: failed to push some refs to 
'ssh://lovesh...@pkgs.fedoraproject.org/rpms/procenv'
___
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

Re: unable to branch to epel8

[Kevin Fenzi]

On 8/15/19 3:18 AM, Dave Love wrote:
> I've tried to get a couple of epel8 branches created, and the tickets
> have been closed (twice in one case after I re-opened it) with "The
> branch in PDC already exists".  (It worked for other packages.)  I don't
> know what PDC is, but the branch definitely isn't in git.  An example is
> .  Can someone
> tell me what to do about that?

I'm not sure why this sometimes happens. As the downthread reply notes
you can just push the branch yourself now after it's been created in the
product definition center. We should really track that down, but the
entire request system is going to be replaced soon, so hard to dig too
far. ;(

> 
> Also, I don't get any notifications from pagure (as with various other
> -- most? -- services), despite turning on anything relevant-looking in
> the notifications app.  I've asked several times about lack of
> notifications with no luck or suggestions how to debug it.  Can anyone
> make any suggestions now?

Can you expand on 'any notifications from pagure' ? pagure.io?
src.fedoraproject.org? what sort of notifications?

Can you point to a thing that should have notificed you?

This is probibly best as a infrastructure ticket, feel free to file
there: https://pagure.io/fedora-infrastructure/issues

and we will get to the bottom of it.

> I'm increasingly un-motivated to do maintenance particularly because of
> continual infrastructure problems.

Very sorry to hear it. We are trying the best we can with the resources
we have. ;(

kevin



signature.asc
Description: OpenPGP digital 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

Re: unable to branch to epel8

[Robert-André Mauchin]

On Thursday, 15 August 2019 12:18:12 CEST Dave Love wrote:
> I've tried to get a couple of epel8 branches created, and the tickets
> have been closed (twice in one case after I re-opened it) with "The
> branch in PDC already exists".  (It worked for other packages.)  I don't
> know what PDC is, but the branch definitely isn't in git.  An example is
> .  Can someone
> tell me what to do about that?
> 
> Also, I don't get any notifications from pagure (as with various other
> -- most? -- services), despite turning on anything relevant-looking in
> the notifications app.  I've asked several times about lack of
> notifications with no luck or suggestions how to debug it.  Can anyone
> make any suggestions now?
> 
> I'm increasingly un-motivated to do maintenance particularly because of
> continual infrastructure problems.


The PDC is the Product Definition Center:

> The Product Definition Center is repository and API for storing and querying 
metadata related to packages, product releases, engineering processes and 
artifacts which are required to support automation of release engineering 
workflows (or productization processes). It aims to support the development of 
automation that ties in the different tools to streamline productization 
processes and create more efficient workflows.

https://pdc.fedoraproject.org/

Your package has already a EPEL8 branch in the PDC:
https://pdc.fedoraproject.org/rest_api/v1/component-branches/?
global_component=procenv

If the branch has not been created in dist-git, you can create it manually:

git checkout -b epel8
git push --set-upstream origin epel8

Best regards,

Robert-André

___
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

unable to branch to epel8

[Dave Love]

I've tried to get a couple of epel8 branches created, and the tickets
have been closed (twice in one case after I re-opened it) with "The
branch in PDC already exists".  (It worked for other packages.)  I don't
know what PDC is, but the branch definitely isn't in git.  An example is
.  Can someone
tell me what to do about that?

Also, I don't get any notifications from pagure (as with various other
-- most? -- services), despite turning on anything relevant-looking in
the notifications app.  I've asked several times about lack of
notifications with no luck or suggestions how to debug it.  Can anyone
make any suggestions now?

I'm increasingly un-motivated to do maintenance particularly because of
continual infrastructure problems.
___
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