←  [EN] Third-Party Development

Forums

»

Transmission 3.00 planned

pieter532's Photo pieter532 12 Jun 2021

Hi,

 

Does anybody know when Transmission (current package 2.94) will be updated to version 3.00. 

 

There are some improvements (see release notes - https://github.com/t...leases/tag/3.00) I really could use :0)

 

Best regards,

Pieter

 


Edited by pieter532, 12 June 2021 - 15:57.
Quote

WanWizard's Photo WanWizard 12 Jun 2021

When someone does it ;).

 

In general we follow the OpenEmbedded releases, so if nothing specific happens, the next update is for OpenPLi 9.

Quote

rantanplan's Photo rantanplan 12 Jun 2021

but patches need more work

Quote

Dimitrij's Photo Dimitrij 13 Jun 2021

but patches need more work

What kind of improvements? It so happened that I did not check the changes myself.

Quote

A.A.'s Photo A.A. 13 Jun 2021

We need to have at least gatesgarth to get official OE transmission 3.

At this point I'd go straight to hardknott which has verysimilar tc but more fixes.

 

I am now working with master-next for my armv4/5 and mipsel ecosystem without particular issues.

 

Cheers

A.A.

Quote

rantanplan's Photo rantanplan 13 Jun 2021

No we don't need it.
Just port it and it builds without any problems.
The new PR in this regard is also provided.

https://github.com/O...-core/pull/1008

 

@ dimitrj

 

build breaks The patches were not adjusted, or better removed
 


Edited by rantanplan, 13 June 2021 - 10:36.
Quote

A.A.'s Photo A.A. 13 Jun 2021

yes, sure, you can backport anything.

But why have one more recipe to maintain?

 

Cheers

A.A.

Quote

WanWizard's Photo WanWizard 13 Jun 2021

Once 8.1 is out the door, and we have a working buildfarm again, we can look at OpenPLi 9, and which OE version we should target.

 

Note that the past has proven that you should not underestimate the work involved in upgrading OE.

Quote

rantanplan's Photo rantanplan 13 Jun 2021

yes, sure, you can backport anything.

But why have one more recipe to maintain?

 

Cheers

A.A.

The recipe is maintained by pli itself and it could currently be backported.
That's a big difference.
In addition ...
No, you can by far not take over everything backport.
Most of it has to be adjusted consistently and many things definitely don't work.
As WanWizard says ...
It is anything but easy to follow the master branch or the next branch you want.
Zeus is good and should be improved consistently.
Everything that comes after that is probably also a change with regard to Python3 and that is only a simple thing at first glance.
Therefore I am of the opinion that the python2 things should be consistently freed from errors and updated.
Running behind the OE core branches does not bring about a stable system.
More like a permanent construction site

 

There is always something to be done at the Zeus branch too.
The users mostly seem satisfied.
If there are errors or things like the ones mentioned here, then you can solve them (the PR is in place) and maybe the user also mentions what he expects in terms of added value.
Maybe everyone will benefit from possible improvements.

greetings

Quote

pieter532's Photo pieter532 13 Jun 2021

Thank you for all the responses. I do not understand everything I did understood that Transmission 3.0 can be looked at for OpenPli 9.

 

Did I understood that correctly?

Quote

rantanplan's Photo rantanplan 13 Jun 2021

If you can build yourself, then you can take over the PullRequest and it is also available to you.
Tell me which box you have, then I also like to look at the built ipk.

Quote

rantanplan's Photo rantanplan 13 Jun 2021

for mipsel and ARM(Broadcom mio4k(+))

Attached Files

Quote

pieter532's Photo pieter532 14 Jun 2021

@rataplan

Thank you for your help however that's to complex for me. I will wait for OpenPli 9 if I understood it correctly that Transmission 3.0 is part of  that.

Quote

pieter532's Photo pieter532 14 Jun 2021

for mipsel and ARM(Broadcom mio4k(+))

I have a VU+ Zero4k receiver (ARM).

 

Do I only need to install (in my case) "transmission_3.00-r0_armv7vehf-neon-vfpv4.ipkas I only need the daemon?

Quote

rantanplan's Photo rantanplan 14 Jun 2021

I rebuilt it adapted again.
I suppose you need to install all three ipk.
Install the plugin last, otherwise you will miss the other two as a dependency.
Just test it.
Back up the image beforehand, then you can restore it quickly.
greetings

Quote

rantanplan's Photo rantanplan 14 Jun 2021

updated again (thx @ nickersk from OE-Alliance)

 

 

Quote

pieter532's Photo pieter532 3 Jul 2021

Hi, 

I needed some time to prepare a (test) machine (VU Uno 4k SE) to install the ipk-package.

 

I used the following command:
 
opkg install transmission_3.00-r0_armv7vehf-neon-vfpv4.ipk
where "transmission_3.00-r0_armv7vehf-neon-vfpv4.ipk" is the file name of the tranmission package (see previous post).
 
The opkg command responded with the following error message. 
 
==========================
Collected errors:
 * Solver encountered 1 problem(s):
 * Problem 1/1:
 *   - package transmission-3.00-r0.armv7vehf-neon-vfpv4 does not have a compatible architecture
 *
 * Solution 1:
 *   - do not ask to install transmission-3.00-r0.armv7vehf-neon-vfpv4
==========================
 
Any idea why?
 
Best regards 

Edited by pieter532, 3 July 2021 - 15:54.
Quote

WanWizard's Photo WanWizard 3 Jul 2021

Very clear why, "package transmission-3.00-r0.armv7vehf-neon-vfpv4 does not have a compatible architecture".

 

This package is not compatible with VU+ boxes, only the Edision 4K hardware uses "armv7vehf-neon-vfpv4".

Quote

pieter532's Photo pieter532 4 Jul 2021

Very clear why, "package transmission-3.00-r0.armv7vehf-neon-vfpv4 does not have a compatible architecture".

 

This package is not compatible with VU+ boxes, only the Edision 4K hardware uses "armv7vehf-neon-vfpv4".

Thank you for your response.

Quote