Re: snap package
Off course like my AppImage the snap package can't launch qet_tb_generator or DXFtoelmt plug-in.
You are not logged in. Please login or register.
QElectroTech → EN : Help, suggestions, discussions, ... → snap package
Off course like my AppImage the snap package can't launch qet_tb_generator or DXFtoelmt plug-in.
We can fix all that and include those in the snap. Let's track all snap related deficiencies @ https://github.com/ppd1990/qelectrotech-snap/issues
A possible solution is perhaps packaging a snap python qet_tb_generator, and for DXFtoelmt a Qt 5 program users put binary into snap env?
We can fix all that and include those in the snap. Let's track all snap related deficiencies @ https://github.com/ppd1990/qelectrotech-snap/issues
Strange file exists.
ls -al /usr/share/libdrm/amdgpu.ids
-rw-r--r-- 1 root root 6682 janv. 22 17:32 /usr/share/libdrm/amdgpu.ids
It is possible to package them separately and then join them via the content interface.
But far simpler is this solution: Just ship everything in the qelectrotech snap itself. That's really easy to do with snapcraft.
What do you think?
ppd wrote:We can fix all that and include those in the snap. Let's track all snap related deficiencies @ https://github.com/ppd1990/qelectrotech-snap/issues
Strange file exists.
ls -al /usr/share/libdrm/amdgpu.ids
-rw-r--r-- 1 root root 6682 janv. 22 17:32 /usr/share/libdrm/amdgpu.ids
The snaps run strictly confined, so it does not see that file unless we include it. I'm preparing an update for the snap as we speak to test a fix.
Laurent,
do you know where to find the source/repo of qet_tb_generator? Or does only the pypi package exist?
It is possible to package them separately and then join them via the content interface.
But far simpler is this solution: Just ship everything in the qelectrotech snap itself. That's really easy to do with snapcraft.
What do you think?
For for far simpler QET search qet_tb_generator installed on the system, and for DXFtoelmt converter is search on Linux QDir::homePath() + "/.qet/DXFtoQET"
https://pypi.org/project/qet-tb-generator/
https://download.qelectrotech.org/qet/b … f_to_elmt/
These two plug-ins are autonomous and can work without QET, but users liked to launch with QET program.
I don't think we will be able to access the system's python packages. It must be installed into the snap itself or be exposed with another snap.
I have make a Debian package on this qet_tb_generator if you want?
You can find it on my PPA's or my Debian Repository.
Thank you, I think I can do it via pip and a bit of hackery.
The QElectroTech project & friends are quite oldschool regarding the source distribution for my juvenile taste, that's all
I think it's a good idea to host as much stuff as accessible as possible. Maybe putting qet-tb-generator on Github isn't too bad of an idea.
We use Tuxfamily.org hosting and services, and I love it.
https://faq.tuxfamily.org/Services/En
Joining us is not that complicated, except maybe for Windows users but WSL2 is coming .. on Win10.. https://devblogs.microsoft.com/commandl … ing-wsl-2/
https://qelectrotech.org/wiki_new/doc/rejoin_project
Hi,
strange. Maybe a temporary problem, given that you have a working internet connection.
Can you give me the output of
snap version
Bust most likely it is/was a temporary problem on the store side
Cheers
Max
Hello Max
I am in another PC, but with similar problems:
juliomarin@Julio-Studio:~$ snap version
snap 2.38
snapd 2.38
series 16
ubuntu 16.04
kernel 4.4.0-150-generic
juliomarin@Julio-Studio:~$ sudo snap install qelectrotech --edge
error: cannot install "qelectrotech": Post
https://api.snapcraft.io/v2/snaps/refresh: proxyconnect tcp: tls:
oversized record received with length 20527
juliomarin@Julio-Studio:~$
I bet you have incorrectly set a https_proxy. Can you show me
echo $https_proxy
and
cat /etc/environment
and
cat
/etc/systemd/system/snapd.service.d/proxy.conf
Or just in general:
env|grep http
I suspect you have set https_proxy=https://something when it should be https_proxy=http://something
Julio could try this command :
traceroute api.snapcraft.io
We use Tuxfamily.org hosting and services, and I love it.
https://faq.tuxfamily.org/Services/EnJoining us is not that complicated, except maybe for Windows users but WSL2 is coming .. on Win10.. https://devblogs.microsoft.com/commandl … ing-wsl-2/
https://qelectrotech.org/wiki_new/doc/rejoin_project
No worries, I haven't worked with Windows in about 15 years. That's not the issue.
I just think qet_tb_generator should have a repository so it can be properly cloned. That may be on tuxfamily for all I care.
Why not, will surely be easier to find for new users, QET guys can find information by Unalcade here : https://qelectrotech.org/forum/viewforum.php?id=16
Also for packaging (as in this case) and for development. I would hardly consider sending a patch or pull request for something that only exists visibly on the pypi registry.
For the moment I'll just include the source you attached in the packaging repo.
You could see the history of this plug-in here :
https://qelectrotech.org/forum/viewtopic.php?id=902
https://qelectrotech.org/forum/viewtopic.php?id=1007
Great stuff. I'll push an updated version tomorrow/later and I hope you'll give it a thorough review.
Nice, thanks Max.
I bet you have incorrectly set a https_proxy. Can you show me
echo $https_proxy
and
cat /etc/environment
and
cat
/etc/systemd/system/snapd.service.d/proxy.conf
Or just in general:
env|grep http
I suspect you have set https_proxy=https://something when it should be https_proxy=http://something
juliomarin@Julio-Studio:~/Proyectos/QET/docs/source$ echo $https_proxy
https://myproxy:3128/
juliomarin@Julio-Studio:~/Proyectos/QET/docs/source$ cat /etc/environment
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"
http_proxy="http://myproxy:3128/"
https_proxy="https://myproxy:3128/"
ftp_proxy="ftp://myproxy:3128/"
socks_proxy="socks://myproxy:3128/"
juliomarin@Julio-Studio:~/Proyectos/QET/docs/source$ env|grep http
http_proxy=http://myproxy:3128/
KIGITHUB=https://github.com/KiCad
https_proxy=https://myproxy:3128/
Note I am before a proxy, and I change the real dir of the proxy to "myproxy"
Julio could try this command :
traceroute api.snapcraft.io
juliomarin@Julio-Studio:~/Proyectos/QET/docs/source$ traceroute api.snapcraft.io
traceroute to api.snapcraft.io (91.189.92.19), 30 hops max, 60 byte packets
1 AtMyNet.es (IP) 3.603 ms 4.415 ms 4.376 ms
2 AtMyNet.es (IP) 4.586 ms 4.547 ms 4.816 ms
3 AtMyNet.es (IP) 3.144 ms 3.113 ms 3.231 ms
4 ge-1-1-5.almeria01.AtMyNet.es (IP) 4.668 ms 4.628 ms 4.861 ms
5 xe-0-2-1.malaga01.AtMyNet.es (IP) 5.629 ms 5.605 ms 5.777 ms
6 cica.ae5-69.uv.rt1.val.red.rediris.es (IP) 16.230 ms 15.960 ms 15.917 ms
7 uv.ae5.telmad.rt4.mad.red.rediris.es (IP) 26.637 ms 23.158 ms 22.651 ms
8 rediris-ias-geant-gw.mar.fr.geant.net (IP) 51.929 ms 51.873 ms 51.844 ms
9 ae8.mx1.gen.ch.geant.net (62.40.98.73) 54.465 ms 54.697 ms 54.270 ms
10 ae6.mx1.par.fr.geant.net (62.40.98.183) 54.224 ms 54.144 ms 54.491 ms
11 ae5.mx1.lon2.uk.geant.net (62.40.98.178) 55.304 ms 54.825 ms 55.233 ms
12 ae6.mx1.lon.uk.geant.net (62.40.98.36) 61.748 ms 61.721 ms 61.651 ms
13 195.66.226.116 (195.66.226.116) 53.373 ms 53.337 ms 53.608 ms
14 173.231.129.65 (173.231.129.65) 54.202 ms 53.533 ms 54.118 ms
15 107.6.86.149 (107.6.86.149) 54.434 ms 54.391 ms 54.344 ms
16 border3.xe-0-1-0-bbnet1.lon003.pnap.net (212.118.240.52) 50.912 ms border3.xe-1-1-0-bbnet2.lon003.pnap.net (212.118.240.116) 50.276 ms border3.xe-0-1-0-bbnet1.lon003.pnap.net (212.118.240.52) 50.248 ms
17 canonical-4.edge1.lon.pnap.net (212.118.242.26) 51.460 ms 51.738 ms 51.368 ms
18 zeeman.canonical.com (91.189.93.205) 51.313 ms 51.222 ms 51.177 ms
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Remove the s from your https_proxy so it looks like https_proxy=http://...
QElectroTech → EN : Help, suggestions, discussions, ... → snap package
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.020 seconds (30% PHP - 70% DB) with 11 queries