yes, that is fixed in the recent upload and a tagged version is uploaded to amber-phone-staging.

I think @adrien.plazas pushed a workaround for this recently: https://source.puri.sm/Librem5/pureos-store/-/merge_requests/14

it looks like a metadata repo issue, we should update the repos. @theodotos.andreou

@adrien.plazas can you close this? I have no perms for it :D

this can be closed, whatip 0.2 is now in the repos

Assign this to me :D

The packaged version here https://source.puri.sm/librem5-apps/tootle is terribly old and not compatible with the Librem 5, we need the master version, or at the *very* least the 1.0-alpha2 version release 12 days ago.

Mmmh, I see it's available here https://source.puri.sm/librem5-apps/whatip so I suppose it's in progress? I'm not sure how all of this works. :)

iirc there was an issue with Avahi.

Is anything blocking that? That would be great to have it.

Is anything blocking that? That would be great to have it especially as they are working on supporting encryption.

since i don't have permissions to edit the content. If a package is blocked at https://master.pureos.net/migrations/
then it has Not touching package due to block request by laniakea in the list of excuses.

That depends on how the suite is set up and where it gets its overrides from - the phone suites do not share overrides with the main amber suite, so everything goes through NEW once (but that also means the changing overrides for the phone suite is easier and there is less room for error and it impacting one of the main suites).

should that read 'If a package (source or binary) is new to a suite of the PureOS archive' since we need to new-process packages NEW in amber-phone that are in byzantium or is that a speciality of amber-phone?

Excellent - we'll get to work on that. :-)

I asked Felix if we can package Shortwave now, he said "sure, there’s a stable release which you can use / package".

Any idea if the situation improved? :)

Erf sorry I duplicated https://tracker.pureos.net/T848…

I believe it's already fixed in amber-phone (we ship gnome-bluetooth 3.34).

We already have GNOME Chess 3.34 in amber-phone.

We already have Taquin 3.34 in amber-phone. Newer versions seem to have problems with the version of Vala used there though.

Opened https://source.puri.sm/Librem5/phoc/-/issues/168

Opened: https://source.puri.sm/Librem5/phosh/-/issues/396

I'm not sure if it was correct to initially set priority of this task to Freedom Issue, because it's possible the issue went unnoticed by team members.

Hmm... sounds a tad expensive to me? Are the other servers located at Hetzner still? Then having storage within their net will be way faster and they also offer pure storage boxes:

Hi @Moop - thanks for reporting this. A new live image has been released. May I ask that you test again?

FWIW Linode provides 250 Gigs for $5 a month. We could get a Terrabyte with them of web addressable storage for USD 20 per month ($240 per year).

So from a quick check it looks like /dev/md3 is the disk that holds our repos;
/dev/md3 1.8T 822G 919G 48% /srv

Something like this maybe:

This IIRC does not work with the Librem laptops since these do not measure the energy properly, instead just estimate based on discharge rate. And even if, it is really rough (even Thinkpads do a pretty bad job at it).

I don't have a power meter but I will use powertop. :-)

@jeremiah.foster powetop shows the amount of power drawn from the battery as a rough indicator

Do you have an AC power meter? That's what I used... let the system sit there idle, battery fully charged, look at power consumption. Then just change _one_ thing at a time, let it settle and become idle again, measure again.

So how do we do this test in a way that produces useful data? Do we run it at two different settings on two laptops concurrently? Or should I measure battery level over time at specific intervals with each setting on the same device?