2023.2.2 missing: pylutron-caseta==0.18.1 #957

New Issue

onkelbeh · 2023-02-05T08:45:31+01:00

onkelbeh commented

2023-02-05 08:45:31 +01:00

a package is required for 2023.2.2 release:

requirement: pylutron-caseta==0.18.1
Package: pylutron-caseta-0.18.1
python_use_dep:

source: lutron_caseta: ['pylutron-caseta==0.18.0'] -> ['pylutron-caseta==0.18.1']

a package is required for 2023.2.2 release: requirement: pylutron-caseta==0.18.1 Package: pylutron-caseta-0.18.1 python_use_dep: source: lutron_caseta: ['pylutron-caseta==0.18.0'] -> ['pylutron-caseta==0.18.1']

onkelbeh self-assigned this 2023-02-05 08:45:31 +01:00

onkelbeh added the

Bump/Update

label 2023-02-05 08:48:21 +01:00

onkelbeh added this to the 2023.2.3 milestone 2023-02-05 08:48:34 +01:00

inode64 referenced a pull request that will close this issue

2023-02-05 12:18:40 +01:00

pylutron-caseta==0.18.1 #963

inode64 commented

2023-02-08 13:05:55 +01:00

How do you see the commit? Is there a problem? I didn't want to upload more until I was clear about how to help me properly

onkelbeh closed this issue

2023-02-11 10:29:03 +01:00

onkelbeh commented

2023-02-11 11:07:55 +01:00

to be honest, I saw it not until I did my version, then I messed up merging it, bad git skills :-)

your version is so much better than mine was, so I took yours now.

what we should discuss:

KEYWORDS="amd64 arm arm64 x86": this is part of my cleanup job, this one is limited to the platforms I am sure about somebody is using, it was added to the cleanup at times I used repoman to check. repoman generated less warnings about missing constraints with lesser platforms. In addition I would not be able to test all these platforms
currently I remove old versions during the commit of the new version, as soom as a directory is visited. I don't know why mgorny does this in seperate commits. pkgdev generates good commit text as long as only one old Ebuild is removed.

I just gave you permissions to read https://git.edevau.net/onkelbeh/ha-tools, where I keep my scripts, all of them very dirty hacks, grown over the years.

You'd need access to my database, I'm sure we can do this, currently it's on my internal mariadb. Can you use wireguard?

I use 3 scripts often, first is

pp2e
this one imports data from pypi's json api, does metadata and suggests a version to copy the last ebuild to

rpmm
cleans some things up, does the manifest, test compile and commits if emerge runs through

har.py
creates the big ebuilds, and tries to read requirements from site-packages/homeassistant, it also makes the gitea tickets when something is missing.

Lets keep this ticket open for now.

to be honest, I saw it not until I did my version, then I messed up merging it, bad git skills :-) your version is so much better than mine was, so I took yours now. what we should discuss: - KEYWORDS="amd64 arm arm64 x86": this is part of my cleanup job, this one is limited to the platforms I am sure about somebody is using, it was added to the cleanup at times I used repoman to check. repoman generated less warnings about missing constraints with lesser platforms. In addition I would not be able to test all these platforms - currently I remove old versions during the commit of the new version, as soom as a directory is visited. I don't know why mgorny does this in seperate commits. pkgdev generates good commit text as long as only one old Ebuild is removed. I just gave you permissions to read https://git.edevau.net/onkelbeh/ha-tools, where I keep my scripts, all of them very dirty hacks, grown over the years. You'd need access to my database, I'm sure we can do this, currently it's on my internal mariadb. Can you use wireguard? I use 3 scripts often, first is **pp2e** this one imports data from pypi's json api, does metadata and suggests a version to copy the last ebuild to **rpmm** cleans some things up, does the manifest, test compile and commits if emerge runs through **har.py** creates the big ebuilds, and tries to read requirements from site-packages/homeassistant, it also makes the gitea tickets when something is missing. Lets keep this ticket open for now.

onkelbeh reopened this issue

2023-02-11 11:07:58 +01:00

onkelbeh commented

2023-02-11 11:16:12 +01:00

btw, thank you very much for offering help, forgot first to thanks in flurry :-)

one more thought,
we should do commits to a branch, not to the master.
I have a running CI env on github (but currently not enought time to keep it green).
I'll push my current 2023.2.3 now, so you can see whats up.

Have to take the dogs out now, will be back in 1-2 hours.

btw, thank you very much for offering help, forgot first to thanks in flurry :-) one more thought, we should do commits to a branch, not to the master. I have a running CI env on github (but currently not enought time to keep it green). I'll push my current 2023.2.3 now, so you can see whats up. Have to take the dogs out now, will be back in 1-2 hours.

onkelbeh removed this from the 2023.2.3 milestone 2023-02-11 11:17:29 +01:00

onkelbeh closed this issue

2023-02-12 09:40:43 +01:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: onkelbeh/HomeAssistantRepository#957