Skip to contentSkip to conversation

oecommit ml

DISCUSSION Trevor Woerner 4 participants 13 messages Nov 12, 2015 – Feb 16, 2016 1 message not in the archive

lore
Share & tools
lore

Trevor Woerner

author
#0 lore raw

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

#1 lore raw
Quoted 5 lines · Trevor Woerner

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

I've already asked Paul and Michael few times on IRC in last few weeks.

I haven't received any reply from Michael, adding him to To, now.

Quoted 4 lines

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

Yes, I find them useful too (e.g. to report issue with commit which was recently merged) or in general to know that it's worth doing "git pull".

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#2 lore raw
Quoted 10 lines · Martin Jansa
Quoted 5 lines · Trevor Woerner

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

Quoted 3 lines

I've already asked Paul and Michael few times on IRC in last few weeks.

I haven't received any reply from Michael, adding him to To, now.

I see that git-notify hooks have been disabled explicitly for all repos in update.secondary file. thats why the messages are not being sent. We can enable them but I would like to know the reason they were disabled in first place. Since we do not have this under some sort of revision history, I can not find information for them as well. So we need this info before we enable them back.

Quoted 16 lines
Quoted 5 lines

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

Yes, I find them useful too (e.g. to report issue with commit which was recently merged) or in general to know that it's worth doing "git pull".

--
Martin 'JaMa' Jansa jabber: [email protected]
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#3 lore raw

It seems git-notify was sending mail as "[email protected]" and that was causing the mail server to get added to blacklists so it was disabled. I've changed the script and re-enabled it for:

openembedded-core
meta-openembedded
OpenEmbedded (but I don't know if we need it)

Michael Halstead
Yocto Project / SysAdmin

Quoted 30 lines · Khem Raj
Quoted 11 lines · Martin Jansa
Quoted 5 lines · Trevor Woerner

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

I've already asked Paul and Michael few times on IRC in last few weeks.

I haven't received any reply from Michael, adding him to To, now.

I see that git-notify hooks have been disabled explicitly for all repos in update.secondary file. thats why the messages are not being sent. We can enable them but I would like to know the reason they were disabled in first place. Since we do not have this under some sort of revision history, I can not find information for them as well. So we need this info before we enable them back.

Quoted 14 lines
Quoted 4 lines

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

Yes, I find them useful too (e.g. to report issue with commit which was recently merged) or in general to know that it's worth doing "git pull".

--
Martin 'JaMa' Jansa jabber: [email protected]
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#4 lore raw
Quoted 10 lines · Michael Halstead

It seems git-notify was sending mail as "[email protected]" and that was causing the mail server to get added to blacklists so it was disabled. I've changed the script and re-enabled it for:

openembedded-core
meta-openembedded
OpenEmbedded (but I don't know if we need it)

bitbake too plz.

Quoted 37 lines

Michael Halstead
Yocto Project / SysAdmin

Quoted 30 lines · Khem Raj
Quoted 11 lines · Martin Jansa
Quoted 5 lines · Trevor Woerner

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

I've already asked Paul and Michael few times on IRC in last few weeks.

I haven't received any reply from Michael, adding him to To, now.

I see that git-notify hooks have been disabled explicitly for all repos in update.secondary file. thats why the messages are not being sent. We can enable them but I would like to know the reason they were disabled in first place. Since we do not have this under some sort of revision history, I can not find information for them as well. So we need this info before we enable them back.

Quoted 14 lines
Quoted 4 lines

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

Yes, I find them useful too (e.g. to report issue with commit which was recently merged) or in general to know that it's worth doing "git pull".

--
Martin 'JaMa' Jansa jabber: [email protected]
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#5 lore raw

Bitbake is disabled with the note:

# interferes with patchwork sice it sends emails after the patches are
closed
# we could re-enable it if the mails went to someother ml may be
bitbake-commits

This happens because it was mailing [email protected]

We can mail [email protected] which would work fine. Or I can create a [email protected]. Which is better?

Michael Halstead
Yocto Project / SysAdmin

Quoted 45 lines · Khem Raj
Quoted 9 lines · Michael Halstead

It seems git-notify was sending mail as "[email protected]" and that was causing the mail server to get added to blacklists so it was disabled. I've changed the script and re-enabled it for:

openembedded-core
meta-openembedded
OpenEmbedded (but I don't know if we need it)

bitbake too plz.

Quoted 34 lines

Michael Halstead
Yocto Project / SysAdmin

Quoted 29 lines · Khem Raj
Quoted 11 lines · Martin Jansa
Quoted 5 lines · Trevor Woerner

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

I've already asked Paul and Michael few times on IRC in last few weeks.

I haven't received any reply from Michael, adding him to To, now.

I see that git-notify hooks have been disabled explicitly for all repos in update.secondary file. thats why the messages are not being sent. We can enable them but I would like to know the reason they were disabled in first place. Since we do not have this under some sort of revision history, I can not find information for them as well. So we need this info before we enable them back.

Quoted 14 lines
Quoted 4 lines

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

Yes, I find them useful too (e.g. to report issue with commit which was recently merged) or in general to know that it's worth doing "git pull".

--
Martin 'JaMa' Jansa jabber: [email protected]
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#6 lore raw
Quoted 10 lines · Michael Halstead

Bitbake is disabled with the note:

# interferes with patchwork sice it sends emails after the patches are
closed
# we could re-enable it if the mails went to someother ml may be
bitbake-commits
Quoted 5 lines

This happens because it was mailing [email protected]

We can mail [email protected] which would work fine. Or I can create a [email protected]. Which is better?

I think mailing to [email protected] might be ok. with [bitbake] in message subject for filtering help.

Quoted 52 lines

Michael Halstead
Yocto Project / SysAdmin

Quoted 45 lines · Khem Raj
Quoted 9 lines · Michael Halstead

It seems git-notify was sending mail as "[email protected]" and that was causing the mail server to get added to blacklists so it was disabled. I've changed the script and re-enabled it for:

openembedded-core
meta-openembedded
OpenEmbedded (but I don't know if we need it)

bitbake too plz.

Quoted 34 lines

Michael Halstead
Yocto Project / SysAdmin

Quoted 29 lines · Khem Raj
Quoted 11 lines · Martin Jansa
Quoted 5 lines · Trevor Woerner

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

I've already asked Paul and Michael few times on IRC in last few weeks.

I haven't received any reply from Michael, adding him to To, now.

I see that git-notify hooks have been disabled explicitly for all repos in update.secondary file. thats why the messages are not being sent. We can enable them but I would like to know the reason they were disabled in first place. Since we do not have this under some sort of revision history, I can not find information for them as well. So we need this info before we enable them back.

Quoted 14 lines
Quoted 4 lines

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

Yes, I find them useful too (e.g. to report issue with commit which was recently merged) or in general to know that it's worth doing "git pull".

--
Martin 'JaMa' Jansa jabber: [email protected]
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#7 lore raw
Quoted 9 lines · Khem Raj
Quoted 9 lines · Michael Halstead

Bitbake is disabled with the note:

# interferes with patchwork sice it sends emails after the patches are
closed
# we could re-enable it if the mails went to someother ml may be
bitbake-commits
Quoted 6 lines
Quoted 5 lines

This happens because it was mailing [email protected]

We can mail [email protected] which would work fine. Or I can create a [email protected]. Which is better?

I think mailing to [email protected] might be ok. with [bitbake] in message subject for filtering help.

I've altered the script to include [reponame] in the subject of all e-mails and enabled for bitbake.

Michael Halstead
Yocto Project / SysAdmin

Quoted 50 lines
Quoted 50 lines

Michael Halstead
Yocto Project / SysAdmin

Quoted 44 lines · Khem Raj
Quoted 9 lines · Michael Halstead

It seems git-notify was sending mail as "[email protected]" and that was causing the mail server to get added to blacklists so it was disabled. I've changed the script and re-enabled it for:

openembedded-core
meta-openembedded
OpenEmbedded (but I don't know if we need it)

bitbake too plz.

Quoted 33 lines

Michael Halstead
Yocto Project / SysAdmin

Quoted 29 lines · Khem Raj
Quoted 11 lines · Martin Jansa
Quoted 5 lines · Trevor Woerner

It seems I missed some announcement. At first I thought I had been unsubscribed from the openembedded-commits mailing list (since I haven't received any emails on that list since about the end of September). So I looked up http://lists.openembedded.org/pipermail/openembedded-commits/
and it seems to have gone quiet about that time too.

I've already asked Paul and Michael few times on IRC in last few weeks.

I haven't received any reply from Michael, adding him to To, now.

I see that git-notify hooks have been disabled explicitly for all repos in update.secondary file. thats why the messages are not being sent. We can enable them but I would like to know the reason they were disabled in first place. Since we do not have this under some sort of revision history, I can not find information for them as well. So we need this info before we enable them back.

Quoted 14 lines
Quoted 4 lines

I liked being able to watch the commits to see what was going in, and to check if my patches were added (before sending "ping"s, without having to "git pull" and search). Is there a new workflow for seeing what's going in?

Yes, I find them useful too (e.g. to report issue with commit which was recently merged) or in general to know that it's worth doing "git pull".

--
Martin 'JaMa' Jansa jabber: [email protected]
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

#8 lore raw
Quoted 13 lines · Michael Halstead
Quoted 11 lines · Khem Raj
Quoted 11 lines · Michael Halstead

Bitbake is disabled with the note:

# interferes with patchwork sice it sends emails after the patches are
closed
# we could re-enable it if the mails went to someother ml may be
bitbake-commits

This happens because it was mailing [email protected]

Quoted 7 lines
Quoted 4 lines
Quoted 3 lines

We can mail [email protected] which would work fine. Or I can create a [email protected]. Which is better?

I think mailing to [email protected] might be ok. with [bitbake] in message subject for filtering help.

I've altered the script to include [reponame] in the subject of all e-mails and enabled for bitbake.

Seems to be causing some new warnings when pushing to the repo:

OE @ ~/meta-openembedded $ git push origin master
Counting objects: 204, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (193/193), done.
Writing objects: 100% (204/204), 38.00 KiB | 0 bytes/s, done.
Total 204 (delta 147), reused 0 (delta 0)
remote: Scalar found where operator expected at /home/git/git-notify line 140, near "$subject"
remote: (Missing semicolon on previous line?)
remote: Global symbol "@openembedded" requires explicit package name at /home/git/git-notify line 60.
remote: syntax error at /home/git/git-notify line 140, near "$subject "
remote: Execution of /home/git/git-notify aborted due to compilation errors.
remote: E: failed to find patch for rev 7df2b574f1c4ad445b1656666878cb2ceffca2e0.
remote: E: failed to find patch for rev ea5bc66444a1e9b5fb330d8a6d42dc95e4bc9500.
remote: E: failed to find patch for rev 1ec69e6b3891c01734e57a908a2a675128f126eb.
remote: E: failed to find patch for rev a1d3dce036f80867d30993742d55abb17c6bc057.
...

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#9 lore raw
Quoted 24 lines · Martin Jansa
Quoted 13 lines · Michael Halstead
Quoted 11 lines · Khem Raj
Quoted 11 lines · Michael Halstead

Bitbake is disabled with the note:

# interferes with patchwork sice it sends emails after the patches are
closed
# we could re-enable it if the mails went to someother ml may be
bitbake-commits

This happens because it was mailing [email protected]

Quoted 7 lines
Quoted 4 lines
Quoted 3 lines

We can mail [email protected] which would work fine. Or I can create a [email protected]. Which is better?

I think mailing to [email protected] might be ok. with [bitbake] in message subject for filtering help.

I've altered the script to include [reponame] in the subject of all e-mails and enabled for bitbake.

Seems to be causing some new warnings when pushing to the repo:

Quoted 16 lines

OE @ ~/meta-openembedded $ git push origin master
Counting objects: 204, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (193/193), done.
Writing objects: 100% (204/204), 38.00 KiB | 0 bytes/s, done.
Total 204 (delta 147), reused 0 (delta 0)
remote: Scalar found where operator expected at /home/git/git-notify line 140, near "$subject"
remote: (Missing semicolon on previous line?)
remote: Global symbol "@openembedded" requires explicit package name at /home/git/git-notify line 60.
remote: syntax error at /home/git/git-notify line 140, near "$subject "
remote: Execution of /home/git/git-notify aborted due to compilation errors.
remote: E: failed to find patch for rev 7df2b574f1c4ad445b1656666878cb2ceffca2e0.
remote: E: failed to find patch for rev ea5bc66444a1e9b5fb330d8a6d42dc95e4bc9500.
remote: E: failed to find patch for rev 1ec69e6b3891c01734e57a908a2a675128f126eb.
remote: E: failed to find patch for rev a1d3dce036f80867d30993742d55abb17c6bc057.
...

and it got stuck (maybe 5 mins sofar) after few more "failed to find patch" messages
...

remote: E: failed to find patch for rev 035374299937302bf15d14a4175b15b6bfcb4cfa.
remote: E: failed to find patch for rev 1d35641ab6da3d381af511ee406e2c1d3eaf636b.
remote: E: failed to find patch for rev a497a46ef629788b77b9b0b23d1618a673d08709.
remote: E: failed to find patch for rev 45a6d2537dac421803fcefe8d2e4899a3fc39e43.
remote: E: failed to find patch for rev f558b195c3b880069dd51a29be4aefd50eaec329.
remote: E: failed to find patch for rev 9ba2e55b0f1f7f8326523c1b418997eb38276f2e.
remote: E: failed to find patch for rev 2200a08dc60486017e59c1950fd3138f79e21030.
remote: E: failed to find patch for rev 9a381e8c4d4f3ce074a1f934e2f6dfc3172efe8e.
remote: E: failed to find patch for rev b145a503839840c0ea43cdab5dcab3a9c6ca7f7b.
remote: E: failed to find patch for rev 1f96c7d8ce6e18a2c87a180a94afc179f407c5ab.
remote: E: failed to find patch for rev 72c82837f614fa5d1d3677db71243fe74bf5a496.
remote: E: failed to find patch for rev f6a3cd4dcd1654a953c505ff779090717314871a.
remote: E: failed to find patch for rev c3d88ca50de5657b9b6c05ed19ac1702c95b3c9c.
remote: E: failed to find patch for rev e51b35fdbd6bd64b4e8e1b67d76c7e90d7b9f6d6.
remote: E: failed to find patch for rev 99d96c933f3fa4f4d7ef5727154b0d8ef6533caa.
remote: E: failed to find patch for rev 437f22e9aa4977a95cfab5f0dd8359410281bcfd.
remote: E: failed to find patch for rev 926eeea7c613721cf30105f7c6d7ecc531ccc736.
remote: E: failed to find patch for rev 1b2a08a9f1a27426662c703d0cea8091aa77ab11.
remote: E: failed to find patch for rev d70899b30f7acea4eba3870bbe14a37a44ea7528.
remote: E: failed to find patch for rev e528f2e16033dc011e5c8ac2d843af6c78808077.
remote: E: failed to find patch for rev 907037a7f989c5bfe699109cef7aa456995d2fea.
remote: E: failed to find patch for rev df552bed28c6ed983a94ebad4185bc9b2d04486f.

"failed to find patch for rev" isn't new, patchwork hook never finds anything and I have to mark the reviews manually, but it shouldn't be stuck (maybe trying to send e-mails?).

Also strange that I was pushing 33 changes and only 26 messages were shown (sofar).

Regards,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#10 lore raw
In reply to Martin Jansa

I'll get that fixed asap. Probably about 2 hours.

Quoted 56 lines · Martin Jansa
Quoted 3 lines · Michael Halstead
Quoted 1 line · Khem Raj
Quoted 1 line

On Nov 13, 2015, at 1:45 PM, Michael Halstead <

Quoted 9 lines · [email protected]> wrote:
Quoted 9 lines
Quoted 9 lines

Bitbake is disabled with the note:

# interferes with patchwork sice it sends emails after the patches are
closed
# we could re-enable it if the mails went to someother ml may be
bitbake-commits

This happens because it was mailing

[email protected]

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

We can mail [email protected] which would

work

Quoted 1 line
Quoted 1 line
Quoted 1 line

fine. Or I can create a [email protected].

Which is

Quoted 2 lines
Quoted 2 lines
Quoted 1 line

better?

I think mailing to [email protected] might

be ok. with [bitbake] in message subject for filtering help.

Quoted 3 lines

I've altered the script to include [reponame] in the subject of all e-mails and enabled for bitbake.

Seems to be causing some new warnings when pushing to the repo:

OE @ ~/meta-openembedded $ git push origin master
Counting objects: 204, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (193/193), done.
Writing objects: 100% (204/204), 38.00 KiB | 0 bytes/s, done. Total 204 (delta 147), reused 0 (delta 0)
remote: Scalar found where operator expected at /home/git/git-notify line 140, near "$subject"
remote: (Missing semicolon on previous line?)
remote: Global symbol "@openembedded" requires explicit package name at /home/git/git-notify line 60.
remote: syntax error at /home/git/git-notify line 140, near "$subject "
remote: Execution of /home/git/git-notify aborted due to compilation errors.
remote: E: failed to find patch for rev 7df2b574f1c4ad445b1656666878cb2ceffca2e0.
remote: E: failed to find patch for rev ea5bc66444a1e9b5fb330d8a6d42dc95e4bc9500.
remote: E: failed to find patch for rev 1ec69e6b3891c01734e57a908a2a675128f126eb.
remote: E: failed to find patch for rev a1d3dce036f80867d30993742d55abb17c6bc057.
...

--
Martin 'JaMa' Jansa jabber: [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

author
#12 lore raw

It's great to see the OE Commit mailing list is being updated again, thanks! :-)

#13 lore raw
Quoted 1 line · Trevor Woerner

It's great to see the OE Commit mailing list is being updated again, thanks! :-)

but only from meta-openembedded repo :/

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]