[AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[auh]

[-- Attachment #1: Type: text/plain, Size: 957 bytes --]

Hello,

this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *acpid* to *2.0.34* has Succeeded.

Next steps:
    - apply the patch: git am 0001-acpid-upgrade-2.0.33-2.0.34.patch
    - check the changes to upstream patches and summarize them in the commit message,
    - compile an image that contains the package
    - perform some basic sanity tests
    - amend the patch and sign it off: git commit -s --reset-author --amend
    - send it to the appropriate mailing list

Alternatively, if you believe the recipe should not be upgraded at this time,
you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
automatic upgrades would no longer be attempted.

Please review the attached files for further information and build/update failures.
Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler

Regards,
The Upgrade Helper

[-- Attachment #2: 0001-acpid-upgrade-2.0.33-2.0.34.patch --]
[-- Type: application/octet-stream, Size: 1123 bytes --]

From 873eb827cbbc032c803036c4f32e84ad5ac40ba8 Mon Sep 17 00:00:00 2001
From: Upgrade Helper <auh@yoctoproject.org>
Date: Sat, 15 Oct 2022 05:50:33 +0000
Subject: [PATCH] acpid: upgrade 2.0.33 -> 2.0.34

---
 meta/recipes-bsp/acpid/{acpid_2.0.33.bb => acpid_2.0.34.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-bsp/acpid/{acpid_2.0.33.bb => acpid_2.0.34.bb} (66%)

diff --git a/meta/recipes-bsp/acpid/acpid_2.0.33.bb b/meta/recipes-bsp/acpid/acpid_2.0.34.bb
similarity index 66%
rename from meta/recipes-bsp/acpid/acpid_2.0.33.bb
rename to meta/recipes-bsp/acpid/acpid_2.0.34.bb
index 7094ba2662..1e0a6d5f24 100644
--- a/meta/recipes-bsp/acpid/acpid_2.0.33.bb
+++ b/meta/recipes-bsp/acpid/acpid_2.0.34.bb
@@ -3,4 +3,4 @@ require acpid.inc
 LIC_FILES_CHKSUM = "file://COPYING;md5=8ca43cbc842c2336e835926c2166c28b \
                     file://acpid.h;endline=24;md5=324a9cf225ae69ddaad1bf9d942115b5"
 
-SRC_URI[sha256sum] = "0856f71b3eb34a1b663d0a8e6363dfcbc519e63d847330498898658e2972dbe8"
+SRC_URI[sha256sum] = "2d095c8cfcbc847caec746d62cdc8d0bff1ec1bc72ef7c674c721e04da6ab333"
-- 
2.31.1


[-- Attachment #3: buildhistory-diff-full.txt --]
[-- Type: text/plain, Size: 2067 bytes --]

packages/core2-32-poky-linux/acpid/acpid-dbg: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid/acpid-dbg: PKGSIZE changed from 204072 to 207048 (+1%)
packages/core2-32-poky-linux/acpid/acpid-dbg: PV changed from "2.0.33" to "2.0.34"
packages/core2-32-poky-linux/acpid/acpid-dev: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid/acpid-dev: PV changed from "2.0.33" to "2.0.34"
packages/core2-32-poky-linux/acpid/acpid-doc: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid/acpid-doc: PKGSIZE changed from 66152 to 66886 (+1%)
packages/core2-32-poky-linux/acpid/acpid-doc: PV changed from "2.0.33" to "2.0.34"
packages/core2-32-poky-linux/acpid/acpid-locale: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid/acpid-locale: PV changed from "2.0.33" to "2.0.34"
packages/core2-32-poky-linux/acpid/acpid-src: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid/acpid-src: PKGSIZE changed from 169188 to 172541 (+2%)
packages/core2-32-poky-linux/acpid/acpid-src: PV changed from "2.0.33" to "2.0.34"
packages/core2-32-poky-linux/acpid/acpid-staticdev: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid/acpid-staticdev: PV changed from "2.0.33" to "2.0.34"
packages/core2-32-poky-linux/acpid/acpid: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid/acpid: PKGSIZE changed from 95854 to 101010 (+5%)
packages/core2-32-poky-linux/acpid/acpid: PV changed from "2.0.33" to "2.0.34"
packages/core2-32-poky-linux/acpid: PKGV changed from 2.0.33 [default] to 2.0.34 [default]
packages/core2-32-poky-linux/acpid: SRC_URI changed from "https://downloads.sourceforge.net/acpid2/acpid-2.0.33.tar.xz file://init file://acpid.service" to "https://downloads.sourceforge.net/acpid2/acpid-2.0.34.tar.xz file://init file://acpid.service"
packages/core2-32-poky-linux/acpid: PV changed from "2.0.33" to "2.0.34"

Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[Jacob Kroon]

Another AUH mail bomb, another time where I am pressing "delete" 148 
times in my email client. I don't review machine generated emails.
I would not cry if AUH mails were sent to a designated mailing list, one 
that I am not subscribed to.

Jacob

On 10/16/22 00:03, Auto Upgrade Helper wrote:
> Hello,
> 
> this email is a notification from the Auto Upgrade Helper
> that the automatic attempt to upgrade the recipe *acpid* to *2.0.34* has Succeeded.
> 
> Next steps:
>      - apply the patch: git am 0001-acpid-upgrade-2.0.33-2.0.34.patch
>      - check the changes to upstream patches and summarize them in the commit message,
>      - compile an image that contains the package
>      - perform some basic sanity tests
>      - amend the patch and sign it off: git commit -s --reset-author --amend
>      - send it to the appropriate mailing list
> 
> Alternatively, if you believe the recipe should not be upgraded at this time,
> you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
> automatic upgrades would no longer be attempted.
> 
> Please review the attached files for further information and build/update failures.
> Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
> 
> Regards,
> The Upgrade Helper
> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#171742): https://lists.openembedded.org/g/openembedded-core/message/171742
> Mute This Topic: https://lists.openembedded.org/mt/94354924/4454410
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [jacob.kroon@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 

Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 2340 bytes --]

We are asking for help here with version updates. Specifically that you
take at least some of these reports and act on them. If you don’t want to
do this, fine, but demanding that those reports are not produced because
deleting them inconveniences you is both unreasonable and antagonizing.
Keeping core updated should not be ‘Alex problem’ but it de facto is.

Alex

On Sun 16. Oct 2022 at 8.50, Jacob Kroon <jacob.kroon@gmail.com> wrote:

> Another AUH mail bomb, another time where I am pressing "delete" 148
> times in my email client. I don't review machine generated emails.
> I would not cry if AUH mails were sent to a designated mailing list, one
> that I am not subscribed to.
>
> Jacob
>
> On 10/16/22 00:03, Auto Upgrade Helper wrote:
> > Hello,
> >
> > this email is a notification from the Auto Upgrade Helper
> > that the automatic attempt to upgrade the recipe *acpid* to *2.0.34* has
> Succeeded.
> >
> > Next steps:
> >      - apply the patch: git am 0001-acpid-upgrade-2.0.33-2.0.34.patch
> >      - check the changes to upstream patches and summarize them in the
> commit message,
> >      - compile an image that contains the package
> >      - perform some basic sanity tests
> >      - amend the patch and sign it off: git commit -s --reset-author
> --amend
> >      - send it to the appropriate mailing list
> >
> > Alternatively, if you believe the recipe should not be upgraded at this
> time,
> > you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that
> > automatic upgrades would no longer be attempted.
> >
> > Please review the attached files for further information and
> build/update failures.
> > Any problem please file a bug at
> https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
> >
> > Regards,
> > The Upgrade Helper
> >
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#171742):
> https://lists.openembedded.org/g/openembedded-core/message/171742
> > Mute This Topic: https://lists.openembedded.org/mt/94354924/4454410
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> jacob.kroon@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>

[-- Attachment #2: Type: text/html, Size: 3501 bytes --]

Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[Jacob Kroon]

Hi Alex,

On 10/16/22 09:24, Alexander Kanavin wrote:
> We are asking for help here with version updates. Specifically that you 
> take at least some of these reports and act on them. If you don’t want 
> to do this, fine, but demanding that those reports are not produced 
> because deleting them inconveniences you is both unreasonable and 
> antagonizing. Keeping core updated should not be ‘Alex problem’ but it 
> de facto is.
> 

I do think it is reasonable to ask for not being mail-bombed with 
machine generated emails.

I am asking for either to:
* put them on a separate mailing list
* merge them into one email

If keeping core updated still is "Alex's problem" then the AUH emails 
are not having the intended effect *anyway*.

> Alex
> 
> On Sun 16. Oct 2022 at 8.50, Jacob Kroon <jacob.kroon@gmail.com 
> <mailto:jacob.kroon@gmail.com>> wrote:
> 
>     Another AUH mail bomb, another time where I am pressing "delete" 148
>     times in my email client. I don't review machine generated emails.
>     I would not cry if AUH mails were sent to a designated mailing list,
>     one
>     that I am not subscribed to.
> 
>     Jacob
>

Jacob

Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[Alexander Kanavin]

On Sun, 16 Oct 2022 at 09:56, Jacob Kroon <jacob.kroon@gmail.com> wrote:
> I do think it is reasonable to ask for not being mail-bombed with
> machine generated emails.
>
> I am asking for either to:
> * put them on a separate mailing list
> * merge them into one email
>
> If keeping core updated still is "Alex's problem" then the AUH emails
> are not having the intended effect *anyway*.

They do help, just not to the level I would like. They also provide an
easy way for someone who is not yet a contributor to become one,
particularly when AUH did succeed and produced a working patch that
doesn't need manual fixing. They also make the maintenance problem
known and visible. Sweeping it all under the carpet as suggested would
make the situation worse, not better.

If you do not want to mix those emails with those written by humans, I
trust your email client has a filter system. I still cling to the
belief that you would want to help the core, and only personal
circumstances prevent you, and therefore this filter will be set to
put those mails into a separate folder instead of deleting them
ouright.

Alex

Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 2139 bytes --]

On Sun, Oct 16, 2022 at 8:05 AM Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> On Sun, 16 Oct 2022 at 09:56, Jacob Kroon <jacob.kroon@gmail.com> wrote:
> > I do think it is reasonable to ask for not being mail-bombed with
> > machine generated emails.
> >
> > I am asking for either to:
> > * put them on a separate mailing list
> > * merge them into one email
> >
> > If keeping core updated still is "Alex's problem" then the AUH emails
> > are not having the intended effect *anyway*.
>
> They do help, just not to the level I would like. They also provide an
> easy way for someone who is not yet a contributor to become one,
> particularly when AUH did succeed and produced a working patch that
> doesn't need manual fixing. They also make the maintenance problem
> known and visible. Sweeping it all under the carpet as suggested would
> make the situation worse, not better.
>
> If you do not want to mix those emails with those written by humans, I
> trust your email client has a filter system. I still cling to the
> belief that you would want to help the core, and only personal
> circumstances prevent you, and therefore this filter will be set to
> put those mails into a separate folder instead of deleting them
> ouright.
>

I'm with Alex on this.

The email need to be visible and they need to be separate.

People can write filters, or mark them as read the few times they come out.
That level
of effort is not much of an ask, compared to trying to keep things up to
date, and to
keep everyone informed.

Cheers,

Bruce



>
> Alex
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#171893):
> https://lists.openembedded.org/g/openembedded-core/message/171893
> Mute This Topic: https://lists.openembedded.org/mt/94354924/1050810
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

[-- Attachment #2: Type: text/html, Size: 4086 bytes --]

Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 2532 bytes --]

On Sun, Oct 16, 2022 at 9:57 AM Bruce Ashfield <bruce.ashfield@gmail.com>
wrote:

>
>
> On Sun, Oct 16, 2022 at 8:05 AM Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
>
>> On Sun, 16 Oct 2022 at 09:56, Jacob Kroon <jacob.kroon@gmail.com> wrote:
>> > I do think it is reasonable to ask for not being mail-bombed with
>> > machine generated emails.
>> >
>> > I am asking for either to:
>> > * put them on a separate mailing list
>> > * merge them into one email
>> >
>> > If keeping core updated still is "Alex's problem" then the AUH emails
>> > are not having the intended effect *anyway*.
>>
>> They do help, just not to the level I would like. They also provide an
>> easy way for someone who is not yet a contributor to become one,
>> particularly when AUH did succeed and produced a working patch that
>> doesn't need manual fixing. They also make the maintenance problem
>> known and visible. Sweeping it all under the carpet as suggested would
>> make the situation worse, not better.
>>
>> If you do not want to mix those emails with those written by humans, I
>> trust your email client has a filter system. I still cling to the
>> belief that you would want to help the core, and only personal
>> circumstances prevent you, and therefore this filter will be set to
>> put those mails into a separate folder instead of deleting them
>> ouright.
>>
>
> I'm with Alex on this.
>
> The email need to be visible and they need to be separate.
>

And by "separate", I mean not consolidated into a giant digest or report.

Bruce


>
> People can write filters, or mark them as read the few times they come
> out. That level
> of effort is not much of an ask, compared to trying to keep things up to
> date, and to
> keep everyone informed.
>
> Cheers,
>
> Bruce
>
>
>
>>
>> Alex
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>> View/Reply Online (#171893):
>> https://lists.openembedded.org/g/openembedded-core/message/171893
>> Mute This Topic: https://lists.openembedded.org/mt/94354924/1050810
>> Group Owner: openembedded-core+owner@lists.openembedded.org
>> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
>> bruce.ashfield@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await thee
> at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
>

-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II

[-- Attachment #2: Type: text/html, Size: 5002 bytes --]

Re: [OE-core] [AUH] acpid: upgrading to 2.0.34 SUCCEEDED

[Jacob Kroon]

On 10/16/22 14:05, Alexander Kanavin wrote:
> On Sun, 16 Oct 2022 at 09:56, Jacob Kroon <jacob.kroon@gmail.com> wrote:
>> I do think it is reasonable to ask for not being mail-bombed with
>> machine generated emails.
>>
>> I am asking for either to:
>> * put them on a separate mailing list
>> * merge them into one email
>>
>> If keeping core updated still is "Alex's problem" then the AUH emails
>> are not having the intended effect *anyway*.
> 
> They do help, just not to the level I would like. They also provide an
> easy way for someone who is not yet a contributor to become one,
> particularly when AUH did succeed and produced a working patch that
> doesn't need manual fixing. They also make the maintenance problem
> known and visible. Sweeping it all under the carpet as suggested would
> make the situation worse, not better.
> 

Don't put words in my mouth. I gave two alternatives, not to sweep them 
under the carpet. A third option would be to publish the AUH results on 
some webpage and post the link.

> If you do not want to mix those emails with those written by humans, I
> trust your email client has a filter system. I still cling to the
> belief that you would want to help the core, and only personal
> circumstances prevent you, and therefore this filter will be set to
> put those mails into a separate folder instead of deleting them
> ouright.

Fine, I'll setup filtering to forward all AUH emails to the trashbin then.

Jacob