Maemo Leste Wiki - User contributions [en]

Extras/Barev

2026-07-09T13:04:36Z

Norayr:

==Barev P2P communication protocol==

The protocol was created out of attempts to make serverless communication. The authors were experimenting on how to use standardized serverless protocol: Bonjour(XEP-0174), over the Yggdrasil network.

It turned out we can't implement all Bonjour features without MDNS, so we had to fork the Pidgin Bonjour plugin, and created a Barev plugin, where MDNS dependent Bonjour features were replaced by xmpp stanzas from XEP-0004, XEP-0071, XEP-0085, XEP-0095, XEP-0096, XEP-0153, XEP-0199.

Usually Barev chat is used in Pidgin, as a [https://codeberg.org/norayr/barev-purple purple plugin].
You can chat with people who have Barev messenger - be it in Pidgin, or in Maemo. There are WIP Android/ios clients too.

== What is supported==

On Pidgin, statuses:(Online, Away, Do not disturb), status line, avatars, typing notifications, file transfers, and of course chats are supported.
In maemo/conversations, all the features are supported, except Maemo has no "Away" status, and it has no file transfers.

If the other party is offline, the message will be queued and delivered once the contact becomes available. The messages are queued in memory currently, after the device restart (or pidgin restart) they will be lost.

Each Barev client is one account. So if you have one Barev in Pidgin on your desktop, and one in Maemo, those are different accounts. Your contacts need to choose where to write.

==How to install==

Get <pre>rtcom-accounts-plugin-barev</pre> in Hildon Application Manager.

It will pull as a dependency <pre>Yggdrasil</pre> and <pre>barev-purple</pre>.

== Add an account ==

Go to Settings, <pre>VoIP and IM accounts</pre>

[[File:Voip and im accounts.png]]

It'll show a list of already added accounts.

[[File:Accounts.png]]

Press New to add an account.

[[File:Choose barev.png]]

Choose a nick, type it in:

[[File:Choose nick.png]]

And here's a list of your accounts.

[[File:List of accounts.png]]

That's basically it.

==Add contacts==

Before adding an account, I would recommend to restart the device. Telepathy-haze doesn't always register the account without restart (at least you can find the telepathy daemon and restart?). And that leads to the contact that you'll add in the next step to loose its haze record/misbehave. Better restart now and proceed.

Your Barev address is your nick@your_yggdrasil_ipv6 address. The nick you already chose.

To tell others how to add you, you need to know your Yggdrasil address.

There are several ways to know your Yggdrasil address.

<pre>
sudo yggdrasilctl getself
</pre>

There's a field: <pre>IPv6 address</pre>

You can take it from there.

Other way is to run

<pre>
ip a
</pre>

If you have not configured Yggdrasil yourself, before installing Barev, then Barev have configured you a <pre>barev0</pre> network interface. You can find your Yggdrasil IPv6 address under it.

Now go to the addressbook and let's add a Barev contact.

[[File:Abook.png]]

Tap on "New contact".

[[File:New contact.png]]

Fill the fields, add name, surname, and paste your friend's nick@ipv6 in Barev field.

[[File:Adding barev contact.png]]

Then your addressbook will list your contact, and if the contact also added you back, you'll see them online.

[[File:Abook with barev contact.png]]

==How to add you==

Your contact can add you in Pidgin or other Maemo device.

In pidgin, they must use Buddies -> Add buddy.

Then paste your Yggdrasil address in Buddy's username field, choose a group to which to add you, and that's it.

[[File:Pidgin add barev contact.png]]

And here your maemo account is becoming online.

[[File:Pidgin contact list.png]]

==Start chatting==

You can start chatting with your contact by tapping on Barev field in the contact's page:

[[File:Barev contact page.png]]

[[File:Barev chat window.png]]

==Set status==

You can set Online, Busy, and Offline, and also choose a status line.

[[File:Barev status.png]]

Have fun!!

File:Barev chat window.png

2026-07-08T15:11:49Z

Norayr: Norayr uploaded a new version of File:Barev chat window.png

Extras/Barev

2026-07-08T15:06:40Z

Norayr: /* What is supported */

==Barev P2P communication protocol==

The protocol was created out of attempts to make serverless communication. The authors were experimenting on how to use standardized serverless protocol: Bonjour(XEP-0174), over the Yggdrasil network.

It turned out we can't implement all Bonjour features without MDNS, so we had to fork the Pidgin Bonjour plugin, and created a Barev plugin, where MDNS dependent Bonjour features were replaced by xmpp stanzas from XEP-0004, XEP-0071, XEP-0085, XEP-0095, XEP-0096, XEP-0153, XEP-0199.

Usually Barev chat is used in Pidgin, as a [https://codeberg.org/norayr/barev-purple purple plugin].
You can chat with people who have Barev messenger - be it in Pidgin, or in Maemo. There are WIP Android/ios clients too.

== What is supported==

On Pidgin, statuses:(Online, Away, Do not disturb), status line, avatars, typing notifications, file transfers, and of course chats are supported.
In maemo/conversations, all the features are supported, except Maemo has no "Away" status, and it has no file transfers.

If the other party is offline, the message will be queued and delivered once the contact becomes available. The messages are queued in memory currently, after the device restart (or pidgin restart) they will be lost.

Each Barev client is one account. So if you have one Barev in Pidgin on your desktop, and one in Maemo, those are different accounts. Your contacts need to choose where to write.

==How to install==

Get <pre>rtcom-accounts-plugin-barev</pre> in Hildon Application Manager.

It will pull as a dependency <pre>Yggdrasil</pre> and <pre>barev-purple</pre>.

== Add an account ==

Go to Settings, <pre>VoIP and IM accounts</pre>

[[File:Voip and im accounts.png]]

It'll show a list of already added accounts.

[[File:Accounts.png]]

Press New to add an account.

[[File:Choose barev.png]]

Choose a nick, type it in:

[[File:Choose nick.png]]

And here's a list of your accounts.

[[File:List of accounts.png]]

That's basically it.

==Add contacts==

Your Barev address is your nick@your_yggdrasil_ipv6 address. The nick you already chose.

To tell others how to add you, you need to know your Yggdrasil address.

There are several ways to know your Yggdrasil address.

<pre>
sudo yggdrasilctl getself
</pre>

There's a field: <pre>IPv6 address</pre>

You can take it from there.

Other way is to run

<pre>
ip a
</pre>

If you have not configured Yggdrasil yourself, before installing Barev, then Barev have configured you a <pre>barev0</pre> network interface. You can find your Yggdrasil IPv6 address under it.

Now go to the addressbook and let's add a Barev contact.

[[File:Abook.png]]

Tap on "New contact".

[[File:New contact.png]]

Fill the fields, add name, surname, and paste your friend's nick@ipv6 in Barev field.

[[File:Adding barev contact.png]]

Then your addressbook will list your contact, and if the contact also added you back, you'll see them online.

[[File:Abook with barev contact.png]]

==How to add you==

Your contact can add you in Pidgin or other Maemo device.

In pidgin, they must use Buddies -> Add buddy.

Then paste your Yggdrasil address in Buddy's username field, choose a group to which to add you, and that's it.

[[File:Pidgin add barev contact.png]]

And here your maemo account is becoming online.

[[File:Pidgin contact list.png]]

==Start chatting==

You can start chatting with your contact by tapping on Barev field in the contact's page:

[[File:Barev contact page.png]]

[[File:Barev chat window.png]]

==Set status==

You can set Online, Busy, and Offline, and also choose a status line.

[[File:Barev status.png]]

Have fun!!

Extras/Barev

2026-07-08T14:58:06Z

Norayr:

==Barev P2P communication protocol==

The protocol was created out of attempts to make serverless communication. The authors were experimenting on how to use standardized serverless protocol: Bonjour(XEP-0174), over the Yggdrasil network.

It turned out we can't implement all Bonjour features without MDNS, so we had to fork the Pidgin Bonjour plugin, and created a Barev plugin, where MDNS dependent Bonjour features were replaced by xmpp stanzas from XEP-0004, XEP-0071, XEP-0085, XEP-0095, XEP-0096, XEP-0153, XEP-0199.

Usually Barev chat is used in Pidgin, as a [https://codeberg.org/norayr/barev-purple purple plugin].
You can chat with people who have Barev messenger - be it in Pidgin, or in Maemo. There are WIP Android/ios clients too.

== What is supported==

On Pidgin, statuses:(Online, Away, Do not disturb), status line, typing notifications, file transfers, and of course chats are supported.
In maemo/conversations, all the features are supported, except Maemo has no "Away" status, and it has no file transfers.

If the other party is offline, the message will be queued and delivered once the contact becomes available. The messages are queued in memory currently, after the device restart (or pidgin restart) they will be lost.

Each Barev client is one account. So if you have one Barev in Pidgin on your desktop, and one in Maemo, those are different accounts. Your contacts need to choose where to write.

==How to install==

Get <pre>rtcom-accounts-plugin-barev</pre> in Hildon Application Manager.

It will pull as a dependency <pre>Yggdrasil</pre> and <pre>barev-purple</pre>.

== Add an account ==

Go to Settings, <pre>VoIP and IM accounts</pre>

[[File:Voip and im accounts.png]]

It'll show a list of already added accounts.

[[File:Accounts.png]]

Press New to add an account.

[[File:Choose barev.png]]

Choose a nick, type it in:

[[File:Choose nick.png]]

And here's a list of your accounts.

[[File:List of accounts.png]]

That's basically it.

==Add contacts==

Your Barev address is your nick@your_yggdrasil_ipv6 address. The nick you already chose.

To tell others how to add you, you need to know your Yggdrasil address.

There are several ways to know your Yggdrasil address.

<pre>
sudo yggdrasilctl getself
</pre>

There's a field: <pre>IPv6 address</pre>

You can take it from there.

Other way is to run

<pre>
ip a
</pre>

If you have not configured Yggdrasil yourself, before installing Barev, then Barev have configured you a <pre>barev0</pre> network interface. You can find your Yggdrasil IPv6 address under it.

Now go to the addressbook and let's add a Barev contact.

[[File:Abook.png]]

Tap on "New contact".

[[File:New contact.png]]

Fill the fields, add name, surname, and paste your friend's nick@ipv6 in Barev field.

[[File:Adding barev contact.png]]

Then your addressbook will list your contact, and if the contact also added you back, you'll see them online.

[[File:Abook with barev contact.png]]

==How to add you==

Your contact can add you in Pidgin or other Maemo device.

In pidgin, they must use Buddies -> Add buddy.

Then paste your Yggdrasil address in Buddy's username field, choose a group to which to add you, and that's it.

[[File:Pidgin add barev contact.png]]

And here your maemo account is becoming online.

[[File:Pidgin contact list.png]]

==Start chatting==

You can start chatting with your contact by tapping on Barev field in the contact's page:

[[File:Barev contact page.png]]

[[File:Barev chat window.png]]

==Set status==

You can set Online, Busy, and Offline, and also choose a status line.

[[File:Barev status.png]]

Have fun!!

File:Pidgin contact list.png

2026-07-08T14:57:30Z

Norayr:

File:Pidgin add barev contact.png

2026-07-08T14:46:51Z

Norayr:

Extras/Barev

2026-07-08T14:43:42Z

Norayr:

==Barev P2P communication protocol==

The protocol was created out of attempts to make serverless communication. The authors were experimenting on how to use standardized serverless protocol: Bonjour(XEP-0174), over the Yggdrasil network.

It turned out we can't implement all Bonjour features without MDNS, so we had to fork the Pidgin Bonjour plugin, and created a Barev plugin, where MDNS dependent Bonjour features were replaced by xmpp stanzas from XEP-0004, XEP-0071, XEP-0085, XEP-0095, XEP-0096, XEP-0153, XEP-0199.

Usually Barev chat is used in Pidgin, as a [https://codeberg.org/norayr/barev-purple purple plugin].
You can chat with people who have Barev messenger - be it in Pidgin, or in Maemo. There are WIP Android/ios clients too.

== What is supported==

On Pidgin, statuses:(Online, Away, Do not disturb), status line, typing notifications, file transfers, and of course chats are supported.
In maemo/conversations, all the features are supported, except Maemo has no "Away" status, and it has no file transfers.

If the other party is offline, the message will be queued and delivered once the contact becomes available. The messages are queued in memory currently, after the device restart (or pidgin restart) they will be lost.

Each Barev client is one account. So if you have one Barev in Pidgin on your desktop, and one in Maemo, those are different accounts. Your contacts need to choose where to write.

==How to install==

Get <pre>rtcom-accounts-plugin-barev</pre> in Hildon Application Manager.

It will pull as a dependency <pre>Yggdrasil</pre> and <pre>barev-purple</pre>.

== Add an account ==

Go to Settings, <pre>VoIP and IM accounts</pre>

[[File:Voip and im accounts.png]]

It'll show a list of already added accounts.

[[File:Accounts.png]]

Press New to add an account.

[[File:Choose barev.png]]

Choose a nick, type it in:

[[File:Choose nick.png]]

And here's a list of your accounts.

[[File:List of accounts.png]]

That's basically it.

==Add contacts==

Your Barev address is your nick@your_yggdrasil_ipv6 address. The nick you already chose.

To tell others how to add you, you need to know your Yggdrasil address.

There are several ways to know your Yggdrasil address.

<pre>
sudo yggdrasilctl getself
</pre>

There's a field: <pre>IPv6 address</pre>

You can take it from there.

Other way is to run

<pre>
ip a
</pre>

If you have not configured Yggdrasil yourself, before installing Barev, then Barev have configured you a <pre>barev0</pre> network interface. You can find your Yggdrasil IPv6 address under it.

Now go to the addressbook and let's add a Barev contact.

[[File:Abook.png]]

Tap on "New contact".

[[File:New contact.png]]

Fill the fields, add name, surname, and paste your friend's nick@ipv6 in Barev field.

[[File:Adding barev contact.png]]

Then your addressbook will list your contact, and if the contact also added you back, you'll see them online.

[[File:Abook with barev contact.png]]

==Stach chatting==

You can start chatting with your contact by tapping on Barev field in the contact's page:

[[File:Barev contact page.png]]

[[File:Barev chat window.png]]

==Set status==

You can set Online, Busy, and Offline, and also choose a status line.

[[File:Barev status.png]]

Have fun!!

File:Barev status.png

2026-07-08T14:36:26Z

Norayr:

File:Barev chat window.png

2026-07-08T14:34:56Z

Norayr:

File:Barev contact page.png

2026-07-08T14:33:46Z

Norayr:

File:Abook with barev contact.png

2026-07-08T14:29:59Z

Norayr:

File:Adding barev contact.png

2026-07-08T14:27:38Z

Norayr:

File:New contact.png

2026-07-08T14:24:42Z

Norayr:

Extras/Barev

2026-07-08T14:21:44Z

Norayr:

==Barev communication protocol==

The protocol was created out of attempts to make serverless communication. The authors were experimenting on how to use standardized serverless protocol: Bonjour(XEP-0174), over the Yggdrasil network.

It turned out we can't implement all Bonjour features without MDNS, so we had to fork the Pidgin Bonjour plugin, and created a Barev plugin, where MDNS dependent Bonjour features were replaced by xmpp stanzas from XEP-0004, XEP-0071, XEP-0085, XEP-0095, XEP-0096, XEP-0153, XEP-0199.

==How to install==

Get <pre>rtcom-accounts-plugin-barev</pre> in Hildon Application Manager.

It will pull as a dependency <pre>Yggdrasil</pre> and <pre>barev-purple</pre>.

== Add an account ==

Go to Settings, <pre>VoIP and IM accounts</pre>

[[File:Voip and im accounts.png]]

It'll show a list of already added accounts.

[[File:Accounts.png]]

Press New to add an account.

[[File:Choose barev.png]]

Choose a nick, type it in:

[[File:Choose nick.png]]

And here's a list of your accounts.

[[File:List of accounts.png]]

That's basically it. Your Barev address is your nick@your_yggdrasil_ipv6 address. The nick you already chose.

To tell others how to add you, you need to know your Yggdrasil address.

There are several ways to know your Yggdrasil address.

<pre>
sudo yggdrasilctl getself
</pre>

There's a field: <pre>IPv6 address</pre>

You can take it from there.

Other way is to run

<pre>
ip a
</pre>

If you have not configured Yggdrasil yourself, before installing Barev, then Barev have configured you a <pre>barev0</pre> network interface. You can find your Yggdrasil IPv6 address under it.

to be continued.

File:Abook.png

2026-07-08T14:21:30Z

Norayr:

File:List of accounts.png

2026-07-08T14:18:50Z

Norayr:

File:Choose nick.png

2026-07-08T14:13:28Z

Norayr:

File:Choose barev.png

2026-07-08T14:12:17Z

Norayr:

File:Accounts.png

2026-07-08T14:11:10Z

Norayr:

File:Voip and im accounts.png

2026-07-08T14:09:12Z

Norayr:

Extras/Barev

2026-07-05T18:16:27Z

Norayr: Created page with "==Barev communication protocol== The protocol was created out of attempts to make serverless communication. We were experimenting on how to use standardized serverless protocol: Bonjour, over the Yggdrasil network. It turned out we can't implement Bonjour features without MDNS, so we had to for the Pidgin Bonjour plugin, and created a Barev plugin. ==How to install== Get <pre>rtcom-accounts-plugin-barev</pre> in Hildon Application Manager. to be continued."

==Barev communication protocol==

The protocol was created out of attempts to make serverless communication. We were experimenting on how to use standardized serverless protocol: Bonjour, over the Yggdrasil network.

It turned out we can't implement Bonjour features without MDNS, so we had to for the Pidgin Bonjour plugin, and created a Barev plugin.

==How to install==

Get <pre>rtcom-accounts-plugin-barev</pre> in Hildon Application Manager.

to be continued.

Development/Porting Packages

2026-07-04T12:01:32Z

Norayr:

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-testing/pool/fremantle-1.3/free/source/

If main links above dont work, you can use mirrors:

* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/pool/maemo5.0/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/pool/maemo5.0/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.2/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.2/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.3/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.3/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-devel/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-devel/pool/fremantle/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-testing/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-testing/pool/fremantle/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/community-testing/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/community-testing/pool/fremantle/non-free/

Another mirror is:

* https://maemo.viniciuspaes.com/extras/pool/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `optipng` installed. (media-gfx/optipng in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://git.maemo.org/leste-extras/ maemo-leste-extras] and [https://git.maemo.org/leste-extras/bugtracker/issues/ open an issue] in the [https://git.maemo.org/leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get an invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/excalibur</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@git.maemo.org:leste-extras/msid

$ git remote -v
maemo git@git.maemo.org:leste-extras/msid (fetch)
maemo git@git.maemo.org:leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To git.maemo.org:leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/excalibur
Switched to a new branch 'maemo/excalibur'

$ git push maemo maemo/excalibur
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/excalibur' by visiting:
remote: https://git.maemo.org/leste-extras/msid/pull/new/maemo/excalibur
remote:
To git.maemo.org:leste-extras/msid
* [new branch] maemo/excalibur -> maemo/excalibur
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>

== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Extras/Lagrange

2026-05-01T12:40:21Z

Norayr:

Lagrange is a smolnet browser, it supports Gemini/Spartan/Nex/Titan/Gopher/ protocols.

It is possible to use it as simple HTML browser as well, by connecting to one of HTTP to Gemini proxies, or selfhosting.

Some HTTP to Gemini proxies:

* Duckling proxy
* Stargate proxy

==Screenshots==
[[File:3672ff95-8864-4adb-b828-d7ae1a47fbff.png|thumb]]

[[File:996dcd5a-49f1-41ee-9919-bb5a0a80f276.png|thumb]]

[[File:73c8de3b-3946-49ec-836d-f99402cca13e.png|thumb]]

Gopher:

[[File:0309d876-a1fc-40d5-8b21-95bb27288719.png|thumb]]

Terminal emulation is supported:

[[File:6b6fcb7d-3a91-47bf-a706-459b34d99fd6.png|thumb]]

[[File:48765438-446d-42a2-9d60-c1e72f313941.png|thumb]]

==Tweaks==

===Increase cache size===

This makes touch scrolling working better and cpu usage decreases a lot (on n900). increasing cachesize also makes radio streaming working fine when lagrange is in background.

Edit

<pre>
~/.config/lagrange/prefs.cfg
</pre>

Change cachesize:

<pre>
cachesize.set arg:100
</pre>

===UI Scaling===

Default UI Scaling is 1, setting it to 0.3 helps on n900.

Edit

<pre>
~/.config/lagrange/prefs.cfg
</pre>

Set
<pre>
uiscale arg:0.3
</pre>

File:48765438-446d-42a2-9d60-c1e72f313941.png

2026-05-01T12:40:06Z

Norayr:

ansi

File:6b6fcb7d-3a91-47bf-a706-459b34d99fd6.png

2026-05-01T12:39:27Z

Norayr:

ansi

File:73c8de3b-3946-49ec-836d-f99402cca13e.png

2026-05-01T12:30:22Z

Norayr:

solar power blog

File:0309d876-a1fc-40d5-8b21-95bb27288719.png

2026-05-01T12:28:18Z

Norayr:

gopher page screenshot in lagrange.

File:996dcd5a-49f1-41ee-9919-bb5a0a80f276.png

2026-05-01T12:27:23Z

Norayr:

smolzine capsule.

Extras/Lagrange

2026-05-01T12:18:42Z

Norayr: Created page with "Lagrange is a smolnet browser, it supports Gemini/Spartan/Nex/Titan/Gopher/ protocols. It is possible to use it as simple HTML browser as well, by connecting to one of HTTP to Gemini proxies, or selfhosting. Some HTTP to Gemini proxies: * Duckling proxy * Stargate proxy ==Screenshots== thumb ==Tweaks== ===Increase cache size=== This makes touch scrolling working better and cpu usage decreases a lot (on n900). inc..."

Lagrange is a smolnet browser, it supports Gemini/Spartan/Nex/Titan/Gopher/ protocols.

It is possible to use it as simple HTML browser as well, by connecting to one of HTTP to Gemini proxies, or selfhosting.

Some HTTP to Gemini proxies:

* Duckling proxy
* Stargate proxy

==Screenshots==
[[File:3672ff95-8864-4adb-b828-d7ae1a47fbff.png|thumb]]

==Tweaks==

===Increase cache size===

This makes touch scrolling working better and cpu usage decreases a lot (on n900). increasing cachesize also makes radio streaming working fine when lagrange is in background.

Edit

<pre>
~/.config/lagrange/prefs.cfg
</pre>

Change cachesize:

<pre>
cachesize.set arg:100
</pre>

===UI Scaling===

Default UI Scaling is 1, setting it to 0.3 helps on n900.

Edit

<pre>
~/.config/lagrange/prefs.cfg
</pre>

Set

```
uiscale arg:0.3
```

File:3672ff95-8864-4adb-b828-d7ae1a47fbff.png

2026-05-01T12:17:55Z

Norayr:

lagrange browser screenshot in hildon desktop

Development/Porting Packages

2026-01-25T23:52:39Z

Norayr: added links to maemo repository mirrors

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-testing/pool/fremantle-1.3/free/source/

If main links above dont work, you can use mirrors:

* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/pool/maemo5.0/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/pool/maemo5.0/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.2/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.2/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.3/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras/pool/fremantle-1.3/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-devel/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-devel/pool/fremantle/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-testing/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/extras-testing/pool/fremantle/non-free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/community-testing/pool/fremantle/free/
* https://maemo.plan9.de/apt-mirror/mirror/repository.maemo.org/community-testing/pool/fremantle/non-free/

Another mirror is:

* https://maemo.viniciuspaes.com/extras/pool/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `optipng` installed. (media-gfx/optipng in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://git.maemo.org/leste-extras/ maemo-leste-extras] and [https://git.maemo.org/leste-extras/bugtracker/issues/ open an issue] in the [https://git.maemo.org/leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get an invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@git.maemo.org:leste-extras/msid

$ git remote -v
maemo git@git.maemo.org:leste-extras/msid (fetch)
maemo git@git.maemo.org:leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To git.maemo.org:leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' by visiting:
remote: https://git.maemo.org/leste-extras/msid/pull/new/maemo/beowulf
remote:
To git.maemo.org:leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>

== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Development/Porting Packages

2024-07-14T21:31:59Z

Norayr:

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-testing/pool/fremantle-1.3/free/source/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `optipng` installed. (media-gfx/optipng in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://github.com/maemo-leste-extras/ maemo-leste-extras] and [https://github.com/maemo-leste-extras/bugtracker/issues/new/choose open an issue] in the [https://github.com/maemo-leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get github invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@github.com:maemo-leste-extras/msid

$ git remote -v
maemo git@github.com:maemo-leste-extras/msid (fetch)
maemo git@github.com:maemo-leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To github.com:maemo-leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' on GitHub by visiting:
remote: https://github.com/maemo-leste-extras/msid/pull/new/maemo/beowulf
remote:
To github.com:maemo-leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>
== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Development/Porting Packages

2024-07-14T21:31:21Z

Norayr:

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-testing/pool/fremantle-1.3/free/source/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `sharutils` installed. (media-gfx/optipng in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://github.com/maemo-leste-extras/ maemo-leste-extras] and [https://github.com/maemo-leste-extras/bugtracker/issues/new/choose open an issue] in the [https://github.com/maemo-leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get github invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@github.com:maemo-leste-extras/msid

$ git remote -v
maemo git@github.com:maemo-leste-extras/msid (fetch)
maemo git@github.com:maemo-leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To github.com:maemo-leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' on GitHub by visiting:
remote: https://github.com/maemo-leste-extras/msid/pull/new/maemo/beowulf
remote:
To github.com:maemo-leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>
== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Development/Porting Packages

2023-01-16T21:44:49Z

Norayr:

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-testing/pool/fremantle-1.3/free/source/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `sharutils` installed. (app-arch/sharutils in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://github.com/maemo-leste-extras/ maemo-leste-extras] and [https://github.com/maemo-leste-extras/bugtracker/issues/new/choose open an issue] in the [https://github.com/maemo-leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get github invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@github.com:maemo-leste-extras/msid

$ git remote -v
maemo git@github.com:maemo-leste-extras/msid (fetch)
maemo git@github.com:maemo-leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To github.com:maemo-leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' on GitHub by visiting:
remote: https://github.com/maemo-leste-extras/msid/pull/new/maemo/beowulf
remote:
To github.com:maemo-leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>
== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Development/Porting Packages

2023-01-16T21:43:22Z

Norayr: /* Porting existing Maemo Fremantle packages */

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.3/free/
* http://repository.maemo.org/extras-devel/pool/fremantle-1.2/free/source/
* http://repository.maemo.org/extras-testing/pool/fremantle-1.3/free/source/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `sharutils` installed. (app-arch/sharutils in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://github.com/maemo-leste-extras/ maemo-leste-extras] and [https://github.com/maemo-leste-extras/bugtracker/issues/new/choose open an issue] in the [https://github.com/maemo-leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get github invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@github.com:maemo-leste-extras/msid

$ git remote -v
maemo git@github.com:maemo-leste-extras/msid (fetch)
maemo git@github.com:maemo-leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To github.com:maemo-leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' on GitHub by visiting:
remote: https://github.com/maemo-leste-extras/msid/pull/new/maemo/beowulf
remote:
To github.com:maemo-leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>
== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Development/Porting Packages

2023-01-16T21:35:46Z

Norayr: /* Porting existing Maemo Fremantle packages */

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle/source/free/
* http://repository.maemo.org/extras-testing/pool/fremantle/source/free/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `sharutils` installed. (app-arch/sharutils in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://github.com/maemo-leste-extras/ maemo-leste-extras] and [https://github.com/maemo-leste-extras/bugtracker/issues/new/choose open an issue] in the [https://github.com/maemo-leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get github invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@github.com:maemo-leste-extras/msid

$ git remote -v
maemo git@github.com:maemo-leste-extras/msid (fetch)
maemo git@github.com:maemo-leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To github.com:maemo-leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' on GitHub by visiting:
remote: https://github.com/maemo-leste-extras/msid/pull/new/maemo/beowulf
remote:
To github.com:maemo-leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>
== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Development/Porting Packages

2023-01-16T18:47:57Z

Norayr: /* Porting existing Maemo Fremantle packages */

= Porting / Creating packages =

If you're looking at creating your own package, or porting software, the first things to do are:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Check if there already are Debian packaging scripts/files. Debian packages a LOT of software, so it's likely that the software is already in the Maemo repository, or someone at least has build scripts for it.
# (TODO)

= Porting existing Maemo Fremantle packages =

Maemo Fremantle ("Nokia Maemo for the N900") contains a lot of packages that are open source. Most of them should run with very few changes on Maemo Leste, the main changes you will need to make will be:

# Check if someone already ported the package (if it in the repository? Is there an issue for it?)
# Updating of the Debian packaging files/scripts.
# Porting to newer libraries if old libraries are used (OpenSSL 0.9.8 -> OpenSSL 1.1.x, Qt4 -> Qt5, etc)
# Fixing any compile errors/warnings due to more strict compile flags

Source of the packages can be found at one of these places:

* http://maemo.org/packages/
* https://garage.maemo.org/
* http://repository.maemo.org/extras/pool/fremantle/free/source/
* http://repository.maemo.org/extras-devel/pool/fremantle/free/
* http://repository.maemo.org/extras-testing/pool/fremantle/free/

= Example =

== Getting the source package ==
Let's say we'd like to port a package "msid".

it's here: <pre>http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/</pre>

get the latest version:

<pre>
wget http://repository.maemo.org/extras/pool/fremantle/free/source/m/msid/msid_0.4.8-2.tar.gz
</pre>

<pre>
tar zxvf msid_0.4.8-2.tar.gz
cd msid-0.4.8
</pre>

== Creating new repo ==

init a git repo:

<pre>
git init
git add *
git commit -a -m "initial commit from fremantle sources"
</pre>

change content of `debian/compat` to `9`.

edit <pre>debian/changelog</pre>.

let's say the last release was:

<pre>
msid (0.4.8-2) unstable; urgency=low
</pre>

now the release should be:

<pre>
msid (0.4.8-2+leste1) unstable; urgency=low
</pre>

record your changes, add your name.

look if <pre>debian/control</pre> dependency versions should be changed.

== installing build dependencies==

<pre>
sudo apt build-dep .
</pre>

== building ==

<pre>
dpkg-buildpackage -b -uc
</pre>

add <pre>gbp.conf</pre> file in <pre>debian</pre> directory with the following content:

<pre>
[DEFAULT]
upstream-tag=%(version)s
</pre>

in <pre>debian/control</pre> file add (if not added)

<pre>
XSBC-Bugtracker: mailto:yourname@yourserver.am
</pre>

== icon ==
and the icon (this is not necessary if you port existing maemo5 package).

it is done [http://wiki.maemo.org/Maemo_packaging#Displaying_an_icon_in_the_Application_Manager_next_to_your_package this] way.

you need to have `sharutils` installed. (app-arch/sharutils in gentoo).

* prepare a `48x48` png file.

* optimize it: <pre>optipng -strip all</pre>

* base64 encode it

<pre>
uuencode -m maeFat.png maeFat.png > maeFat.png.base64
</pre>

* Add the field <pre>XB-Maemo-Icon-26</pre> to your <pre>debian/control</pre> (in Maemo 4 the size of the icons was 26×26 pixels, hence the name of the field, which has not changed in Maemo 5)

* Open the <pre>base64</pre> version of your image and copy from the line under <pre>begin-base64 644 <name of 48×48 image></pre> to the line above the <pre>===</pre>.

* Add this to the XB-Maemo-Icon-26 field

* Add a space in front of every line of the encoded icon. You can do that automatically using sed when you base64 encode the image:

<pre>
uuencode -m <name of 48×48 image> <name of 48×48 image> | sed -e s,^,\ , > <name of 48×48 image>.base64
</pre>

== cli apps ==
if the program that is being ported is a <code>cli</code> application, then <code>cli icon</code> can be used.

[http://lists.maemo.org/pipermail/maemo-community/2010-January/003870.html cli icon announcement]

[http://n900.tannerlab.com/tools/cli.icon.txt old unexistent in archive.org too, txt file]

[http://samoff.com/random/maemo/cli_icon/ icons as images]

this is how the icon looks in <code>ham</code>:

[[File:Maemo-cli_icon_appman_sample_v002.png]]

and this is the <code>48x48</code> size icon:

[[File:Maemo-term_icon_v002_a001_48p.png]]

its <code>base64</code> encoded and shifted for <code>maemo</code> <code>text file</code> is [http://norayr.am/tips/port_maemo_package_to_leste/maemo-term_icon_v002_a001_48p.png.base64 here]

or here:
<pre> begin-base64 644 maemo-term_icon_v002_a001_48p.png
iVBORw0KGgoAAAANSUhEUgAAADAAAAAwCAYAAABXAvmHAAAAGXRFWHRTb2Z0
d2FyZQBBZG9iZSBJbWFnZVJlYWR5ccllPAAACYtJREFUeNrUWkurZUcVXvXY
59zbtyXpICEiaFrJQFDo6CDOHAi2UQdOFBw4CAqCDhU0DuIPEBtCRupIBxk4
MBMHgpIMnChE1OAD2uADEkFpUM9z710vv7Wq6ty6u09f0+nb3Tcb6u7Hqb33
96361qq1al/1vscfp+Ac3fjH6+S9v3owP/iYMfqyMaabz2ax62wwtnPDOPgY
ok8pxpQoKKW9UhRC8IFI+UQ4ds7HFKLW1mujffDexRi9MXiGMQG34uborbEO
515pckopZ7RxuN8RyflgtBrxfKeNGlNMY0ppxItGUnowSm3Rr7ezubfdnCwe
SuMw2EsPPvi9x957+SlrNAXvCCTIWkMKvQP6JEYdorQoG6gkUIpo+SgkStyV
SQb0RwOolACOQdBIlAaQ7XGtT4q2lGhDDCjRGsZYg8Qa71sR75WSPe5Z411o
doPfN1rrDs/q8MaVVt5Z5T1dnM++8sEPXHnqXzduxOuv/iVutlsGKeCxJbyE
jxN2uJc3FfkcJzHviBlG5sq/kUq8D4qvyzWKpQ/fzn94H/Mzub88L0hfJc/w
OPc8Ijh3is8xUhqIMZr+woULscMwRmjCwoDdY+959xcXiwX9/KVfRAyV0gYD
xTBVeY2mjJuvAR3+aMrgjPRQKtVzrRSDwE1Kl1uEuBADKCX34g5VzKLk/ihk
lQBl8CKt3IQA5MMEICttPIY5XDw6glSVspv15tGLRxcu/+rl3/D4q9lsJtjl
1WyTA7TxBKRYfjZEO2IMTufRosxdVcoCPvEIQTaBrYlLjuWFH0Z0Y433LC3Y
occ5a3ybz7EvmjdaD9IfvudG57d6G4E12fmse+d6tT76z38XcC6TwcOdEtvj
EGL7jif/fU3x1yaDmWejNuCpEI4ilZT3AFPAwifgA9gPuGMIFAESfqDUBpw2
inWuVNY+6z4l7NkX1ApWgI/QlvuD/qDZoWMEeRskaODBlmJ4oB9HGoYxycCy
1R9OavYtT92nweIRotnn4ZkvBhqfRvc/oM8MUJIQqC00zeemWL/FutRnq8Jp
uam0BtA1yC5x8xLHS7xa9sREEjsy+ogTg4CiASQGpZVDjBMJcTDEEajEeDSM
DjxCHm/s5s96mn0W0ekF3PZ2eSR1n0qk3+/U5koXaQU9G6q6nwCXcMgWF/CF
QAVfQHGESSsmQHTcUiYi0QfH6K8YfF8iGEASnBjagPGgp4SoTdra7tAhEnFc
ZIdVhxD3h3GI1/afgcV/B/pfsnG4plP8pU7q0s76twTPsbyAL3quwKUJUIBa
4HiBvrLHNd6DFI9MqpbvAWsANifPR2iGUnA6JDiwRAcLz547FwQThihxpE5/
Bol3YSS+G0g/iuuPQLxftUHEb9HRngDvmv0O/EQ2FfyqtTg3oBGrcyvgNzje
8nMYKT8XGANvmGhzGG68DzIKc4fJNAmDHC+Gr1kKf1Q0/0Kk7qOJDl/y+vAn
mDyfwOj5E1av4MVJG/CnAW8tn7XfWL6A7xvwwO134GmycUye8+y6+9FCG7/V
kbW+eRJzxcsYlb+q1H0yqQs/852+Ehm2b2QzNpavkmkJTMHv9F4IrCqBBvzY
gOe5aS94IYDOMw7R0oH/HqRkPhJJfyiS+yl+/j3i2FXr+meQ+7wN/J5MWlKE
4xFgy/eNbE61fNF7Bc9EBDzA7sDnWRfx3rlTwYu9Met2nNmIvj1m0YeSPXzR
6fRPIHiii3LrDO49pzyNDSecdtij+XUhsdqneb7GwIvmN9wYPPb8nLHMwCyZ
WHCdull0xghIHgPBk0l/V3H8tlHzrwd9dN1ZhmA/Hg/0OyD26xTdj2Eplo1T
rNFW8xm8Bngrx8tCYNGCLwR2Dgvw/RQ8W/6NgBcCmH2ZgJd8RkmESeM3kW+8
orS9GpX9RNTxFRXG57RzP9Tr9Lra6IcxIg8kg/s4XYXXgHqNSivI6QZAqx34
VRvjJ5bvS7gdVc6Dbgt8HgEE1JRvyK2kYP55ONDzOsyv+QN3zazia5KbsIV6
+zn/UPflcKmZiVPJg8i9oF8dv2H/pDqRUXXYKhukxVFi/EQ2bwq8EAB4Sfkl
rc0kJLNRs2zR8Rm7gKs6nDN4KS7cD8xr/kf6b6mJOJK3ECzb078xV6xvBb5G
GgbPDssZprxn5Een2wIvBJgxW6CkxabMEqk4aYBrSk7DecjOWVe0TQu1Po44
kAVxZEFMZ+mYYwKtbJhkBY/mKni2fDoxPd0mAS73mqSspgmZgJYYz+YZdpGG
HVW3sT6tbxE6V8XyN4Fnh71T8DmMah13TpzTYt0QqOBrmGzj/KbG8X2hskab
Ap5lw5rnRGbkephLzjsFn30AD2IHypUThJJ9IRTnOmn5mg4XSxfwiwJ20ZCR
jHKqebZ8BQ/Nx9MmqDdMQAoOPLg+rJRSgXaVEg3T3KZoejVNhat8JrKpSRk7
rMxObPmzAL8jUPKZpgTMs+wey68ay7fpwLLR/qa1fMlr7gr4EwSK5WNOV2VE
hgJ6O3HQ3ew6Ab8rRKrm26SMl18APp0l+ErAFZ2rov3YyGczyWv2WX65J5c/
kVEiIYu3SofvmECxds/1sKQGx/l967DLKfg9hQjLpm9yeV/Ah7sFvh2BPvuv
LJz4Rj7VYZdTy59SRY37qii6S5tNOaPcFgkxCY5KbMl1ydX3hsry+02yKRnl
/y1Ezm4EkqzZMAj2Xl0WWLcFaAt+57CTdJjJD/cDfK0HhryEsdvGMiInnHYP
+Dq79jU1aMBHukebLbPkuoTRVB24AbwsSx7rPYVIXzPKJh1OdA83Wxx4nYNQ
DqGs7zJhtaFyva+KmoCPdI83duKq91iW0nn9vs0qV00hcqsSMNxry7cFzaaA
5HqA1/T71KyiVctPqig3qV/vC/hcD2QJLWsWWvKfOgKbAn5qeV+qqPhmqqiz
deJs8WVd6yyzabU6E7jJ8qUQSfcbfIlCPOuqKiH+gtKu72wby0sJWAqRcwH+
mECCD+yqMLVbpGoKEUmHzxv4UlIalEZhjVosmKT5i2OtA1rLn2kVdbYE+IOS
0uyknEp7HfUYVeQlQ65fRTZ3oxA5w2xUeaNpw18tEf99UFHWf/iLSLH8uQVf
RyBARltrDaaEEPhbbI408jURmh/TeQWf10ZtF9iRu86mAAImSi4WeLklr5ad
X/BCoOsMf/cdZ11HKJ/4HwdiMHyg0/2cYW8nG+X1IDefzxUI8P9ySP2KITj3
4PMnpqT4ozZrP3bWxq7rUlmle0tsVv6xgWkg/Bg7IxPr/2K8Nbb/CTAAF12f
5l7y6xMAAAAASUVORK5CYII=
====</pre>
Also add the field:

<pre>XSBC-Maemo-Display-Name: Photo light meter</pre>

== pushing to maemo-leste-extras ==
go to [https://github.com/maemo-leste-extras/ maemo-leste-extras] and [https://github.com/maemo-leste-extras/bugtracker/issues/new/choose open an issue] in the [https://github.com/maemo-leste-extras/bugtracker extras bugtracker] repo to request a repository.

ping <code>Wizzup</code> on <code>#maemo-leste@irc.libera.chat</code> to open you repo[s]. then try to be attentive to emails, because you may get github invite which you need to accept, otherwise it’ll time out(not sure when).

push your code to the newly opened repo in <code>maemo/beowulf</code> branch.

<code>beowulf</code> is the codename of the <code>devuan</code> release on which <code>maemo</code> is based.

<pre>$ git remote -v
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git remote add maemo git@github.com:maemo-leste-extras/msid

$ git remote -v
maemo git@github.com:maemo-leste-extras/msid (fetch)
maemo git@github.com:maemo-leste-extras/msid (push)
origin git@github.com:norayr/msid.git (fetch)
origin git@github.com:norayr/msid.git (push)

$ git push maemo main
Enumerating objects: 176, done.
Counting objects: 100% (176/176), done.
Delta compression using up to 4 threads
Compressing objects: 100% (86/86), done.
Writing objects: 100% (176/176), 578.92 KiB | 4.71 MiB/s, done.
Total 176 (delta 105), reused 141 (delta 85)
remote: Resolving deltas: 100% (105/105), done.
To github.com:maemo-leste-extras/msid
* [new branch] main -> main

$ git checkout -b maemo/beowulf
Switched to a new branch 'maemo/beowulf'

$ git push maemo maemo/beowulf
Total 0 (delta 0), reused 0 (delta 0)
remote:
remote: Create a pull request for 'maemo/beowulf' on GitHub by visiting:
remote: https://github.com/maemo-leste-extras/msid/pull/new/maemo/beowulf
remote:
To github.com:maemo-leste-extras/msid
* [new branch] maemo/beowulf -> maemo/beowulf
$
</pre>
the repo needs to be tagged.

<pre>git tag 0.0.1</pre>
and then the tag has to be pushed:

<pre>git push maemo 0.0.1</pre>
in case you did some changes but don’t want to bump a tag/changelog version, you need to delete the tag locally:

<pre>git tag -d 0.0.1
git push maemo :refs/tags/0.0.1</pre>
== phoenix ==
login https://phoenix.maemo.org/

the build sequence is:

* source
* binaries
* repos

find your project. let’s say https://phoenix.maemo.org/job/msid-source/

it has to have ‘build with parameters’ button on the left.

if everything is right it’ll trigger build of binaries https://phoenix.maemo.org/job/msid-binaries/

that link, for instance, will contain <code>arm64</code> build console output: https://phoenix.maemo.org/job/msid-binaries/architecture=arm64,label=arm64/1/console

== wiki ==
add a wiki page about the package [https://leste.maemo.org/Category:Extras here].

links:

https://leste.maemo.org/Development https://leste.maemo.org/Development/Porting_Packages https://leste.maemo.org/Development/Building_Packages https://leste.maemo.org/Development/Modified_Software

If you import a package, please try to preserve history if possible (converting from svn -> git is not too hard)

= Forking Debian/Devuan packages =

(TODO - Describe what branches need to be set up, Jenkins integration, etc)

= Preparing package for the repositories =

See https://leste.maemo.org/Development/Building_Packages

Extras/Amazfish

2023-01-16T17:50:37Z

Norayr: /* Other links */

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== Install ==

find in Application manager

[[Image:Amazfish in ham 202301141803.png|500px]]

or

<pre>
apt-get install harbour-amazfish
</pre>

and this is it:

[[Image:Amazfish icon 202301141810.png|500px]]

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|500px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|500px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:202301161836.png|500px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|500px]]

Tap 'Scan devices'.

[[Image:202301161838.png|500px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|500px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|500px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|500px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Other links ==

* hhttps://github.com/piggz/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T17:49:42Z

Norayr: /* Install */

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== Install ==

find in Application manager

[[Image:Amazfish in ham 202301141803.png|500px]]

or

<pre>
apt-get install harbour-amazfish
</pre>

and this is it:

[[Image:Amazfish icon 202301141810.png|500px]]

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|500px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|500px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:202301161836.png|500px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|500px]]

Tap 'Scan devices'.

[[Image:202301161838.png|500px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|500px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|500px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|500px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T17:48:41Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== Install ==

[[Image:Amazfish in ham 202301141803.png|500px]]
[[Image:Amazfish icon 202301141810.png|500px]]

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|500px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|500px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:202301161836.png|500px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|500px]]

Tap 'Scan devices'.

[[Image:202301161838.png|500px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|500px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|500px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|500px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T17:47:14Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|500px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|500px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:202301161836.png|500px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|500px]]

Tap 'Scan devices'.

[[Image:202301161838.png|500px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|500px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|500px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|500px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T17:44:58Z

Norayr: /* Some pictures */

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|500px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|500px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:202301161836.png|500px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|500px]]

Tap 'Scan devices'.

[[Image:202301161838.png|500px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|500px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|500px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|500px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Some pictures ==

<gallery>
[[Image:Amazfish_in_ham_202301141803.png]]
[[Image:Amazfish_icon_202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T17:44:11Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|500px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|500px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:202301161836.png|500px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|500px]]

Tap 'Scan devices'.

[[Image:202301161838.png|500px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|500px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|500px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|500px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T15:45:30Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|500px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|500px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:File:202301161836.png|500px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|500px]]

Tap 'Scan devices'.

[[Image:202301161838.png|500px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|500px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|500px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|500px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T15:43:23Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png|300px]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|300px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:File:202301161836.png|300px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|300px]]

Tap 'Scan devices'.

[[Image:202301161838.png|300px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|300px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|300px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|300px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|300px]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T15:42:53Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding.

Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

[[Image:202301161835.png|300px]]

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

[[Image:File:202301161836.png|300px]]

You'll see list of watches. I chose Amazfit Bip.

[[Image:202301161837.png|300px]]

Tap 'Scan devices'.

[[Image:202301161838.png|300px]]

Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.

[[Image:202301161839.png|300px]]

You should get the pairing request on the watch.

(btw, the hardware address of the watch is autogenerated upon every reset)

[[Image:202301161840.png|300px]]

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|300px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|300px]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T15:12:00Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding. Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

Tap 'Scan devices'. Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.
You should get the pairing request on the watch.

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg|300px]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png|500px]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T15:10:52Z

Norayr:

{{Infobox Package
|image=[[Image:202301161852.png
|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding. Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

Tap 'Scan devices'. Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.
You should get the pairing request on the watch.

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

Extras/Amazfish

2023-01-16T15:10:16Z

Norayr: Created page with "{{Infobox Package |image=250px |status=Working |date_in_repo=2022-09-16 |maemo_leste_repo=https://github.com/maemo-leste-extras/mstard..."

{{Infobox Package
|image=[[Image:MStarDict_SelectDictionary.png|250px]]
|status=Working
|date_in_repo=2022-09-16
|maemo_leste_repo=https://github.com/maemo-leste-extras/mstardict
|category=Utilities
|packager=[[User:Norayr]]
}}

== What is this. ==

Amazfish is an application and a daemon initially developed to connect a Sailfish OS to Amazfit Bip watches.

Later support for more watches been added. Also the developer rewrote the interface, so that the application would work on non Sailfish Linux

At the moment of writing this page, the [https://github.com/piggz/harbour-amazfish github page] lists these devices:

<pre>
There are 3 tiers of supported devices:
Gold

These are devices I have, have tested and will try not to break any functioanlity for an include:

Amazfit Bip
Amazfit GTS
Amazfit GTR2
Pinetime Infinitme
Bangle.js

Silver

These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:

Amazfit BipS
Amazfit Bip Lite
Amazfit GTS2

I do not promise not to break funcaionality in these, but will fix where I can
Bronze

These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.

MiBand 2/3/4
Amazfit Cor
</pre>

== How to pair ==

Run the service:

<pre>
/usr/libexec/amazfish-launcher
</pre>

run the app from the menu, or, it would be good to run it for the first time also in console to see the output:

<pre>
/usr/libexec/amazfish-ui-launcher
</pre>

On droid4, the window doesn't fit on the screen, so it may make sense to run the program with ssh X forwarding. Though on droid4, the author of this article was not able to pair the Amazfish Bip watch: the watch connects and disconnects, shows a warning 'Disconnected', and this is visible in the output of terminal running amazfish daemon:

[[Image:Droid4 amazfish pairing failed 202301161800.png]]

and the amazfish app outpit is:

<pre>
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
void DaemonInterface::pair(const QString&, QString)
kf.bluezqt: PendingCall Error: "No discovery started"
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::pair(const QString&, QString)
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: pairing
void DaemonInterface::changeConnectionState()
void DaemonInterface::changeConnectionState()
qml: disconnected
</pre>

Now the app started, and at first start will ask to write a name and configure your profile.
On Pinephone, at the time of writing this article, it was not possible to write in the name field without the hardware keyboard.

Then on the main application screen tap on 'Pair watch'.
If it shows 'Unpair', tap on 'Accept', and then choose 'Pair watch' again.

Tap 'Scan devices'. Without this though we see the running circle, the watch won't be found.
When you see the watch, tap on it, or 'Stop scan' and then choose the watch.
You should get the pairing request on the watch.

If you didn't, that's okay. The Amazfish shows the main screen again, and 'Disconnect from watch' in the upper right corner.
That means it thinks everything is right and the watch is connected.
Tap on 'Disconnect the watch', and then to 'Connect', at that moment you may get a pairing request on the watch.

[[Image:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg]]

If not, repeat the whole sequence again: unpair, and try pairing again.

== How to use ==

When the watch paired and connected, try to go to settings, then debug, then tap on buttons that show test notifications.

Notifications routed via libnotify should be shown from all applications.

Tap on 'Data grahps' and then 'Download data' - that would connect and download the recent statistics from the watch.
Important: it may not show downloaded data! tap on arrow right, to see the next day, then arrow left to see the current day.
Now the data will be there!

[[Image:202301161852.png]]

== Some pictures ==

<gallery>
[[Image:Amazfish in ham 202301141803.png]]
[[Image:Amazfish icon 202301141810.png]]
</gallery>

== Other links ==

* https://github.com/norayr/harbour-amazfish
* https://openrepos.net/content/piggz/amazfish

File:20230116 184201 -fujichrome-sensia-400-exp-2011.jpg

2023-01-16T15:09:11Z

Norayr: