search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
28.68k stars 4.01k forks source link

Nightly Release For Debian #12616

Open zero77 opened 4 years ago

zero77 commented 4 years ago

qBittorrent version and Operating System

Debian Sid

If on linux, libtorrent-rasterbar and Qt version

image

What is the problem

There's only a stable release branch for debian, which means you have to rebuild for every change to keep up to date.

What is the expected behavior

Have an equivalent repository like ppa:qbittorrent-team/qbittorrent-unstable but for Debian. Perhaps, using the current experimental repository debian has.

Kolcha commented 2 years ago

links will be the same, I'll update packages soon apt-get update will notify you when packages become ready

GvY85 commented 2 years ago

Was monitoring the build process and I got them, working fine so far. Thanks for the work :)!

Kolcha commented 2 years ago

4.4.0 packages are published and available for download, links are the same as in https://github.com/qbittorrent/qBittorrent/issues/12616#issuecomment-974482033, but there are some important notes are below.

packages for ARM architectures may appear with some significant delay, build servers used for them seems to be not so powerful as for x86 builds.

Kolcha commented 2 years ago

small update: qBittorrent 4.4.0 was added into official Debian Unstable repository, so I disabled it in my repositories

GvY85 commented 2 years ago

@Kolcha since yesterday the Testing repo (Stable build's) wants to update my current qBittorrent-nox4.4.0 but also removing libtorrent-rasterbar20 and replace it with libtorrent-rasterbar10 and thus breaking the installation.

Also, it seems at least once a day the packages get updated and the versions increases a minor digit, seemingly without reason?

edit: nvm, that is the official DEbian Testing that does not have rasterbar20 and wants to install rasterbar10... Still, your packages seem to get updated often?

Kolcha commented 2 years ago

seems that qBittorrent 4.4.0 was added to Debian Testing too... not only to Debian Unstable and it is based on libtorrent 1.2.14, libtorrent 2.0.x is still unavailable even in Unstable (looks like only in experimental such package exists). moreover, looks like libtorrent package has no maintainer... so the future of it in Debian is a big question...

official packages took priority on upgrade due to slightly different version number '-2' at the end in official package version number, and '-0' (doesn't matter what goes after it) in my. unfortunately this '-0' can't be changed, build server just doesn't support this, and this '-0' is hardcoded into it's internal scripts, see https://github.com/openSUSE/obs-service-set_version/blob/b85ab00aab7f912c79aa2e5b2aaf0c7dc1e9530e/set_version#L451

very likely that this build server restriction exists because server is OpenSUSE build server, and its primary task is build .rpm packages. and it lack of good support of .deb. but this is unique service I found that even can produce packages for Debian and provides repository out of the box.

for now I suggest to use official Debian qBittorrent 4.4.0 package, I'll disable my own for Debian Testing too (like I did for Debian Unstable). with next qBittorrent release I'll re-enable it.

as alternative solution, I can add something after version, like I added '+p' (full package version looks like '4.4.0+p-0+4.2') for my personal patched qBittorrent version used on my server. this will be greater than the version officially available.

from my point of view there is no reason to provide a custom repository if package in official one has the same version. but in case of qBittorrent libtorrent 2.0 may be a reason.

please let me know your thoughts.

Kolcha commented 2 years ago

regarding version number changes, last digits after '+' in version number are "build number". first is incremented when I made some change in source files (only required for packaging) and thereby triggered a build. consider it as package improvement. the second one (after dot '.') is incremented by automatic build due to some dependency update (libc6, openssl, etc.) and this is not controlled by me. consider it like just a rebuilt to avoid potential compatibility issues.

GvY85 commented 2 years ago

seems that qBittorrent 4.4.0 was added to Debian Testing too... not only to Debian Unstable and it is based on libtorrent 1.2.14, libtorrent 2.0.x is still unavailable even in Unstable (looks like only in experimental such package exists). moreover, looks like libtorrent package has no maintainer... so the future of it in Debian is a big question...

official packages took priority on upgrade due to slightly different version number '-2' at the end in official package version number, and '-0' (doesn't matter what goes after it) in my. unfortunately this '-0' can't be changed, build server just doesn't support this, and this '-0' is hardcoded into it's internal scripts, see https://github.com/openSUSE/obs-service-set_version/blob/b85ab00aab7f912c79aa2e5b2aaf0c7dc1e9530e/set_version#L451

very likely that this build server restriction exists because server is OpenSUSE build server, and its primary task is build .rpm packages. and it lack of good support of .deb. but this is unique service I found that even can produce packages for Debian and provides repository out of the box.

for now I suggest to use official Debian qBittorrent 4.4.0 package, I'll disable my own for Debian Testing too (like I did for Debian Unstable). with next qBittorrent release I'll re-enable it.

as alternative solution, I can add something after version, like I added '+p' (full package version looks like '4.4.0+p-0+4.2') for my personal patched qBittorrent version used on my server. this will be greater than the version officially available.

from my point of view there is no reason to provide a custom repository if package in official one has the same version. but in case of qBittorrent libtorrent 2.0 may be a reason.

please let me know your thoughts.

I would prefer the 4.4.0 based on Libtorrent2.x so if you could keep your version enabled for Testing that would be great.

Kolcha commented 2 years ago

@GvY85 , my libtorrent 2.0 based qBittorrent builds were enabled for Debian Testing and Debian Unstable. I just added '+0' to package version and this is sufficient to override system package. for example package version from my repository 4.4.0+0-0+3.4 is considered newer than 4.4.0-2 provided from official Debian repositories. so, now you can just run apt update and you will get my packages, tested on Debian Unstable

GvY85 commented 2 years ago

Hi, it seems that (at least) in your (Stable) DebianTesting repo there is a problem with libtorrent:

apt update && apt upgrade
Hit:1 https://deb.debian.org/debian testing InRelease
Hit:2 https://deb.debian.org/debian testing-updates InRelease
Hit:3 https://deb.debian.org/debian-security testing-security InRelease
Hit:4 http://www.deb-multimedia.org testing InRelease
Hit:5 http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_Testing  InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libperl5.32 libtorrent-rasterbar20 perl-modules-5.32
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  libperl5.34 libtorrent-rasterbar2.0 perl-modules-5.34
The following packages will be upgraded:
  debian-security-support iputils-ping libldap-2.4-2 liblocale-gettext-perl libproc-processtable-perl
  libterm-readkey-perl libunistring2 mkvtoolnix perl perl-base qbittorrent-nox
11 upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.3 MB of archives.
After this operation, 52.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_Testing  libtorrent-rasterbar2.0 2.0.5+0-0+10.1 [1,467 kB]
Get:2 https://deb.debian.org/debian testing/main amd64 libproc-processtable-perl amd64 0.634-1+b1 [46.9 kB]
Get:3 https://deb.debian.org/debian testing/main amd64 perl-modules-5.34 all 5.34.0-3 [2,850 kB]
Get:4 https://deb.debian.org/debian testing/main amd64 libperl5.34 amd64 5.34.0-3 [4,208 kB]
Get:5 https://deb.debian.org/debian testing/main amd64 perl amd64 5.34.0-3 [297 kB]
Get:6 https://deb.debian.org/debian testing/main amd64 perl-base amd64 5.34.0-3 [1,640 kB]
Get:7 http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_Testing  qbittorrent-nox 4.4.0+0-0+4.1 [6,150 kB]
Get:8 https://deb.debian.org/debian testing/main amd64 liblocale-gettext-perl amd64 1.07-4+b2 [19.2 kB]
Get:9 https://deb.debian.org/debian testing/main amd64 libterm-readkey-perl amd64 2.38-1+b3 [27.8 kB]
Get:10 https://deb.debian.org/debian testing/main amd64 libunistring2 amd64 1.0-1 [416 kB]
Get:11 https://deb.debian.org/debian testing/main amd64 iputils-ping amd64 3:20211215-1 [51.3 kB]
Get:12 https://deb.debian.org/debian testing/main amd64 debian-security-support all 1:12+2022.02.07 [30.4 kB]
Get:13 https://deb.debian.org/debian testing/main amd64 libldap-2.4-2 amd64 2.4.59+dfsg-1+b1 [233 kB]
Get:14 https://deb.debian.org/debian testing/main amd64 mkvtoolnix amd64 65.0.0-1 [5,855 kB]
Fetched 23.3 MB in 2s (14.9 MB/s)
Reading changelogs... Done
Preconfiguring packages ...
(Reading database ... 30956 files and directories currently installed.)
Preparing to unpack .../libproc-processtable-perl_0.634-1+b1_amd64.deb ...
Unpacking libproc-processtable-perl:amd64 (0.634-1+b1) over (0.634-1) ...
Preparing to unpack .../perl_5.34.0-3_amd64.deb ...
Unpacking perl (5.34.0-3) over (5.32.1-6) ...
Selecting previously unselected package perl-modules-5.34.
Preparing to unpack .../perl-modules-5.34_5.34.0-3_all.deb ...
Unpacking perl-modules-5.34 (5.34.0-3) ...
Selecting previously unselected package libperl5.34:amd64.
Preparing to unpack .../libperl5.34_5.34.0-3_amd64.deb ...
Unpacking libperl5.34:amd64 (5.34.0-3) ...
Preparing to unpack .../perl-base_5.34.0-3_amd64.deb ...
Unpacking perl-base (5.34.0-3) over (5.32.1-6) ...
Setting up perl-base (5.34.0-3) ...
(Reading database ... 32860 files and directories currently installed.)
Preparing to unpack .../liblocale-gettext-perl_1.07-4+b2_amd64.deb ...
Unpacking liblocale-gettext-perl (1.07-4+b2) over (1.07-4+b1) ...
Preparing to unpack .../libterm-readkey-perl_2.38-1+b3_amd64.deb ...
Unpacking libterm-readkey-perl (2.38-1+b3) over (2.38-1+b2) ...
Preparing to unpack .../libunistring2_1.0-1_amd64.deb ...
Unpacking libunistring2:amd64 (1.0-1) over (0.9.10-6) ...
Setting up libunistring2:amd64 (1.0-1) ...
(Reading database ... 32858 files and directories currently installed.)
Preparing to unpack .../0-iputils-ping_3%3a20211215-1_amd64.deb ...
Unpacking iputils-ping (3:20211215-1) over (3:20210202-1) ...
Preparing to unpack .../1-debian-security-support_1%3a12+2022.02.07_all.deb ...
Unpacking debian-security-support (1:12+2022.02.07) over (1:12+2021.12.08) ...
Preparing to unpack .../2-libldap-2.4-2_2.4.59+dfsg-1+b1_amd64.deb ...
Unpacking libldap-2.4-2:amd64 (2.4.59+dfsg-1+b1) over (2.4.59+dfsg-1) ...
Selecting previously unselected package libtorrent-rasterbar2.0:amd64.
Preparing to unpack .../3-libtorrent-rasterbar2.0_2.0.5+0-0+10.1_amd64.deb ...
Unpacking libtorrent-rasterbar2.0:amd64 (2.0.5+0-0+10.1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-BCWTXA/3-libtorrent-rasterbar2.0_2.0.5+0-0+10.1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.2.0.5', which is also in package libtorrent-rasterbar20 2.0.5+p-0+2.1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../4-mkvtoolnix_65.0.0-1_amd64.deb ...
Unpacking mkvtoolnix (65.0.0-1) over (64.0.0-1) ...
Preparing to unpack .../5-qbittorrent-nox_4.4.0+0-0+4.1_amd64.deb ...
Unpacking qbittorrent-nox (4.4.0+0-0+4.1) over (4.4.0+0-0+3.11) ...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-BCWTXA/3-libtorrent-rasterbar2.0_2.0.5+0-0+10.1_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

followed by:

apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
  libperl5.32 libtorrent-rasterbar20 perl-modules-5.32
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libtorrent-rasterbar2.0
The following NEW packages will be installed:
  libtorrent-rasterbar2.0
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
11 not fully installed or removed.
Need to get 0 B/1,467 kB of archives.
After this operation, 4,911 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... 32859 files and directories currently installed.)
Preparing to unpack .../libtorrent-rasterbar2.0_2.0.5+0-0+10.1_amd64.deb ...
Unpacking libtorrent-rasterbar2.0:amd64 (2.0.5+0-0+10.1) ...
dpkg: error processing archive /var/cache/apt/archives/libtorrent-rasterbar2.0_2.0.5+0-0+10.1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libtorrent-rasterbar.so.2.0.5', which is also in package libtorrent-rasterbar20 2.0.5+p-0+2.1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libtorrent-rasterbar2.0_2.0.5+0-0+10.1_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Kolcha commented 2 years ago

@GvY85 , sorry for inconvenience, libtorrent package was renamed to follow official package name libtorrent 2.0 was officially packaged for Debian unstable https://packages.debian.org/sid/libtorrent-rasterbar-dev , and now even was migrated even to testing https://tracker.debian.org/pkg/libtorrent-rasterbar . seems, someone maintains this package.

to get everything work again, just remove my libtorrent-rasterbar20 (qbittorrent-nox will be removed too) and then install qbittorrent-nox again.

GvY85 commented 2 years ago

Thanks. 

apt remove qbittorrent-nox
apt autoremove --purge
apt install qbittorrent-nox

Solved it while keeping qbittorrent-nox settings intact

Kolcha commented 2 years ago

Qt6 is appeared in official Debian Testing and Unstable repos https://packages.debian.org/bookworm/qt6-base-dev so, I decided to build qBittorrent packages based on it (separate packages, not replacing already existing Qt5-based)

for now I added Qt6-based build only for "stable" repo: https://software.opensuse.org//download.html?project=home%3Anikoneko%3Atest&package=qbittorrent-qt6 both GUI and "-nox" packages are available. to start using Qt6-based qBittorrent, just install qbittorrent-qt6 or qbittorrent-nox-qt6 package. Qt5-based package you may have already will be uninstalled automatically.

Qt6-based packages are available only for Debian Testing and Unstable: https://build.opensuse.org/package/show/home:nikoneko:test/qbittorrent-qt6

"nightly" repo doesn't have Qt6-based builds yet.

GvY85 commented 2 years ago

Hi @Kolcha, any progress on https://github.com/qbittorrent/qBittorrent/releases/tag/release-4.4.5?

edit: it works as always, thanks for the effort!

Kolcha commented 2 years ago

sorry, now I'm not at home and have no computer with me. I'll back only this Sunday in the evening. so, please wait.

Sent from Mail.ru app for Android Friday, 02 September 2022, 00:03PM +02:00 from GvY85 @.*** :

Hi @Kolcha , any progress on https://github.com/qbittorrent/qBittorrent/releases/tag/release-4.4.5 ? — Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you were mentioned. Message ID: @ github . com>

Kolcha commented 2 years ago

"stable" repo doesn't provide Qt5-based builds for Debian Testing and Unstable anymore, official repositories are updated quit quick and provide up-to-date libtorrent-rasterbar and qbittorrent packages.

"nightly" repo now also contains Qt6-based builds (for Debian Testing and Unstable only). "nightly" builds are not really "nightly" - they are updated in ~1 week.

WolfganP commented 2 years ago

FOA thanks a lot for your nightly builds. Is there any chance you can create another recipe for builds based on libtorrent 1.2_RC as per the latest changes on official releases? Thanks in advance.

Kolcha commented 2 years ago

@WolfganP builds based on libtorrent 1.2 were added! can be installed from there (available for Debian Testing and Unstable), both Qt5 and Qt6 versions are available

WolfganP commented 2 years ago

@WolfganP builds based on libtorrent 1.2 were added! can be installed from there (available for Debian Testing and Unstable), both Qt5 and Qt6 versions are available

Excellent. Thanks a lot @Kolcha! Any chances the raspian11 / armhf versions can be added as in nightly / test? I also noticed that libtorrent is not included in the folder as in nightly & test, did you discard it on purpose or just relying on any specific version? Thanks again!

Kolcha commented 2 years ago

Any chances the raspian11 / armhf versions can be added as in nightly / test?

release builds (aka my "test" repository) are already available for Raspbian 11 (both armhf and aarch64), but they are based on libtorrent 2.0

I also noticed that libtorrent is not included in the folder as in nightly & test, did you discard it on purpose or just relying on any specific version?

this is my black magic :) if you even slightly familiar with C/C++ world, you may know about shared and static libraries. shared libraries are very common in Linux world (and libtorrent is one of them), static are mostly used as "internal" libraries for projects. for this particular case I built libtorrent as static library, packaged it with different package name and NOT published it (but used only for building qBittorrent package) just to overcome the "limit" that libtorrent package in default Linux repositories is newer and I didn't want to override something from standard repo. so, this is expected. also you may notice much bigger executable size comparing to release or current nightly builds, this is the consequence of static library usage (but libtorrent is not required at all in such case!)

I'll add Debian/Raasbian 11 builds this evening. please wait. it requires some work.

Kolcha commented 2 years ago

@WolfganP repositories for Debian/Raspbian 11 were added. packages will be available in ~1 hour. unfortunately arm builds are too slow (especially armv7), very likely build server uses real hardware for it instead of emulation. the link is the same.

WolfganP commented 2 years ago

@WolfganP repositories for Debian/Raspbian 11 were added. packages will be available in ~1 hour. unfortunately arm builds are too slow (especially armv7), very likely build server uses real hardware for it instead of emulation. the link is the same.

Just to confirm, I installed the raspbian armhf -nox build with the static libtorrent and works like a charm. Thanks a lot for adding it!

WolfganP commented 2 years ago

BTW, I couldn't find out on the site, but is there any way to get an RSS notification when a new build is released? (just found browser notifications which aren't too useful)

Kolcha commented 2 years ago

I don't think that such feature exists... and this is pretty useless, it is supposed just to add repository, and packages will be updated as any other system packages. but autoupdate will NOT update packages from custom repositories by default, some configuration is required. what about "update period", there is no any schedule, I trigger builds manually (running some script) approximately every Saturday.

WolfganP commented 1 year ago

Hi @Kolcha It seems that an error cropped up during the past days as the libtorrent 1.2 version didn't build up properly (https://build.opensuse.org/package/live_build_log/home:nikoneko:qbittorrent-nightly-lt12/qbittorrent/Raspbian_11/armv7l) Any chance you can check it?

Kolcha commented 1 year ago

@WolfganP issue is fixed, wait for new qbittorernt package. what happened: for some unknown reason, libtorrent static library in package was corrupted. more correctly, library itself is correct (this is just an archive), but one specific object file (which should contain missing symbols linker complained about) inside it was corrupted. I see no reasonable explanation how it happened (there is no any suspicious output during corresponding file compilation) rather than just some disk I/O error on build agent during that file compilation, because even at the final stage of library creation archiver complained about "unknown format" for that particular object file, but succeeded regardless of it... so, library was created (and later packaged) with corrupted object file inside, and as result some symbols were missing in it.

as far as I know, this build server uses some real hardware for arm builds (at least for some agents), so maybe that "lucky" build was run on hardware with dying flash chip... who knows...

in any case, everything should be fine for now, just wait some time until new qbittorrent package appear. thanks for reporting, I rarely looking into build failures, because they very often happen due to out of memory (especially in case of arm builds) or other reasons completely unrelated to any source code.

WolfganP commented 1 year ago

@WolfganP issue is fixed, wait for new qbittorernt package. what happened: for some unknown reason, libtorrent static library in package was corrupted. more correctly, library itself is correct (this is just an archive), but one specific object file (which should contain missing symbols linker complained about) inside it was corrupted. I see no reasonable explanation how it happened (there is no any suspicious output during corresponding file compilation) rather than just some disk I/O error on build agent during that file compilation, because even at the final stage of library creation archiver complained about "unknown format" for that particular object file, but succeeded regardless of it... so, library was created (and later packaged) with corrupted object file inside, and as result some symbols were missing in it.

as far as I know, this build server uses some real hardware for arm builds (at least for some agents), so maybe that "lucky" build was run on hardware with dying flash chip... who knows...

in any case, everything should be fine for now, just wait some time until new qbittorrent package appear. thanks for reporting, I rarely looking into build failures, because they very often happen due to out of memory (especially in case of arm builds) or other reasons completely unrelated to any source code.

@Kolcha working perfectly now. Thx a lot for the prompt fix!

GvY85 commented 1 year ago

Hi, something seems wrong with your repo keys:

apt update
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
Get:5 http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease [1,540 B]
Hit:6 https://www.deb-multimedia.org bullseye InRelease
Hit:7 https://www.deb-multimedia.org bullseye-backports InRelease
Ign:8 https://mkvtoolnix.download/debian bullseye InRelease
Hit:9 https://mkvtoolnix.download/debian bullseye Release
Err:5 http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease
  The following signatures were invalid: EXPKEYSIG 93368839B2B9A655 home:nikoneko OBS Project <home:nikoneko@build.opensuse.org>
Reading package lists... Done
W: GPG error: http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease: The following signatures were invalid: EXPKEYSIG 93368839B2B9A655 home:nikoneko OBS Project <home:nikoneko@build.opensuse.org>
E: The repository 'http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
root@PiServer:~# echo 'deb http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11/ /' | sudo tee /etc/apt/sources.list.d/home:nikoneko:test.list
deb http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11/ /
root@PiServer:~# curl -fsSL https://download.opensuse.org/repositories/home:nikoneko:test/Debian_11/Release.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_nikoneko_test.gpg > /dev/null
root@PiServer:~# sudo apt update
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
Get:5 http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease [1,540 B]
Ign:6 https://mkvtoolnix.download/debian bullseye InRelease
Hit:7 https://www.deb-multimedia.org bullseye InRelease
Hit:8 https://www.deb-multimedia.org bullseye-backports InRelease
Hit:9 https://mkvtoolnix.download/debian bullseye Release
Err:5 http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease
  The following signatures were invalid: EXPKEYSIG 93368839B2B9A655 home:nikoneko OBS Project <home:nikoneko@build.opensuse.org>
Reading package lists... Done
W: GPG error: http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease: The following signatures were invalid: EXPKEYSIG 93368839B2B9A655 home:nikoneko OBS Project <home:nikoneko@build.opensuse.org>
E: The repository 'http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11  InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Kolcha commented 1 year ago

this is not controlled by me... generated gpg keys used for repo signing expire after some time. and this time is now... all you need to do is just to redownload new generated key. follow the instructions for repo addition (you need to run only one line starting with curl)

Sent from Mail.ru app for Android Monday, 06 February 2023, 09:34AM +01:00 from GvY85 @.*** :

Hi, something seems wrong with your repo keys: http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11 InRelease The following signatures were invalid: EXPKEYSIG 93368839B2B9A655 home:nikoneko OBS Project @.> Reading package lists... Done W: GPG error: http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11 InRelease: The following signatures were invalid: EXPKEYSIG 93368839B2B9A655 home:nikoneko OBS Project @.> E: The repository 'http://download.opensuse.org/repositories/home:/nikoneko:/test/Debian_11 InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

— Reply to this email directly, view it on GitHub , or unsubscribe . You are receiving this because you were mentioned. Message ID: @ github . com>

GvY85 commented 1 year ago

That is what I though as well so I followed the instructions at https://software.opensuse.org//download.html?project=home%3Anikoneko%3Atest&package=qbittorrent

specially curl -fsSL https://download.opensuse.org/repositories/home:nikoneko:test/Debian_11/Release.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_nikoneko_test.gpg > /dev/null

But I get the same error after apt update

Kolcha commented 1 year ago

it seems key was deprecated, but new one was not generated/uploaded for that repo yet Screenshot_20230206_105705 for example, for nightly repo key was added at 1 AM (who knows which time zone, very likely server time) Screenshot_20230206_105238 so, please wait some time. there is nothing depending on me...

Kolcha commented 1 year ago

seems new keys are already available, and can be downloaded manually from here:

at least for "test" repo this key is different comparing to Release.key downloaded from repo.

GvY85 commented 1 year ago

curl -fsSL https://build.opensuse.org/projects/home:nikoneko:test/public_key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/home_nikoneko_test.gpg > /dev/null for Stable works indeed

GvY85 commented 1 year ago

@Kolcha again thanks for the good work!

Now with Bookworm being in hard freeze, are you planning on making a Bookworm repo? I am using Testing currently but a separate Bookworm repo somewhere in the coming months will be appreciated.

Kolcha commented 1 year ago

@GvY85 , sorry, this is doesn't depend on me. I'm using what this "openSUSE build service" provides, this is the only all-in-one solution which can build packages for Debian I found... also I don't think that testing repo will be somehow different to upcoming Bookworm release repo, at least it was so with current Bullseye release -- at the moment of release all repositories were the same (i.e. stable = testing = sid). so, I don't think that some thing can cause any compatibility problems, maybe only python. even more, it seems that build service I'm using updates build environments not so often.

WolfganP commented 1 year ago

Hi @Kolcha . As always, thx for keeping this builds working.

I was surprised I didn't noticed any update since days ago, so I went to your opensuse's project logs and found that it seems the builds weren't triggered since March 25th (not only for the raspbian static libtorrent 1.2 version but for others as well). Any chance to check it? Thanks in advance.

Kolcha commented 1 year ago

Hi @WolfganP . sorry for this. builds are triggered only manually from my personal laptop, but past 3 weeks (since March 26) I was not a home and without my personal laptop. I returned only today, so new builds will appear very soon.

WolfganP commented 1 year ago

Hi @WolfganP . sorry for this. builds are triggered only manually from my personal laptop, but past 3 weeks (since March 26) I was not a home and without my personal laptop. I returned only today, so new builds will appear very soon.

Perfect, thanks @Kolcha. No problem at all with the delay, I just assumed the builds were triggered by commits at github or similar, and something changed at opensuse's side that was worthy to bring to your attention. Thx again!

GvY85 commented 1 year ago

Hi, the Testing repo with qbittorrent-nox-qt6 does not work anymore now that Bookworm is out. Package is held back because it needs libtorrent-rasterbar2.0_2.0.9. That one is in the Debian_11 repo but when you add that one it cannot install because libssl1.? is not available.

Kolcha commented 1 year ago

thanks for notifying, I'm not using Debian anymore, so don't know what happens around it. now I added Debian 12 repos, and disabled Debian Unstable as so as official package is built against Qt6! regarding Debian Testing, it is unclear for now what to do, some time need to pass until Debian updates own repositories, and more important build service updates Debian images used for builds (testing and unstable seems to be updated more rarely rather than stable). similar situation was observed when Debian 11 released in the summer 2021. process should become "smooth" again in about a month.

Debian 12 builds will appear in the repos very soon (in ~1 hour), so you can add and use Debian 12 packages instead of incompatible Debian Testing.

GvY85 commented 1 year ago

Work a charm! Thanks

Kolcha commented 1 year ago

qBittorrent devs raised minimum required Qt version to Qt 6.5, see https://github.com/qbittorrent/qBittorrent/commit/a0fa1709d5b776ddbf238656e64ed9780e269cf2 this makes impossible to build qBittorrent with system-provided Qt even on Debian Unstable (only Qt 6.4.x is available in Debian repos), so builds available right now are the last available for a long time until Debian update Qt 6 in its repos.

even such change is reasonable (at least as for me), as so as drops compatibility stuff from the code base, but imho it a bit early. I'm not sure that Qt 6.5 is available in latest Ubuntu. it will be a breaking change if this will be included into upcoming release...

so, no nightly builds for now. build Qt and qBittorrent by yourself if you want nightly build.

glassez commented 1 year ago

it will be a breaking change if this will be included into upcoming release...

v4_6_x is already branched off and it will be used for v4.6.x releases and it supports Qt 6.2+ (as well as Qt 5.15.2+). master has now set a course for a future major update, which is unlikely to be released earlier than in half a year. Unfortunately, someone will now be disappointed by the lack of these nightly builds. But this is not a critical problem due to the fact that we provide test builds on GitHub.

Kolcha commented 1 year ago

good news everyone! based on ppa mentioned in this discussion https://github.com/qbittorrent/qBittorrent/discussions/19457 , I built static version of Qt 6.5 for Debian

qBittorrent nightly builds for Debian 12+ will be available soon, but there are some difficulties with Debian 11. finding a solution may require some time, but I'm thinking it doesn't worth. so would like to ask some questions:

please leave your comments on it. this is really important, as so as building for different archs and distros is very time- (and resource-) consuming process, and I do not want to just spend build server resources for no value, and also solve any build issues raising from time to time.

also please let me know about any run-time issues, as so as static Qt is very bad idea (at least it was so with Qt 4 and 5, know nothing about Qt 6). I just "smoke" tested GUI build for Debian Unstable, the rest are completely untested, but should be fine.

WolfganP commented 1 year ago

Thanks a lot @Kolcha for keeping these builds alive

* is Debian 11 (including Raspbian 11) still needed? supporting it will require to use backported packages + some hacks/fixes

* is armv7 arch still needed? build time for it is extremely long...

* should I provide builds for arm arch (arm64/aarch64) at all?

I'm using a Raspberry2 (armv7l platform) as a torrent/file/media server, so the builds for qbittorrent-nox for arm7hf with static libtorrent 1.2 are my way to go (I don't really know if full QT is even needed in the build as it's a headless server)

But saying that, I also don't think a nightly/daily build is needed for my use (in case you need to maintain build resources low).

Again, thanks a lot for these builds.

Kolcha commented 1 year ago

Debian 11 (and Raspbian 11) for nightly builds (from master branch) will not be supported anymore - qBittorrent uses some C++20 features which seems unavailable in GCC 10 (Debian 11 default). so, it's time to say goodbye to Debian 11., nightly builds will be available only for Debian 12+

@WolfganP , I'll create new qbittorrent release package based on libtorrent 1.2 in "test" repo where lt2.0 based builds are available. release builds are available for Debian 11+ and for arm and x86, both 32 and 64 bit. and this will be supported for a long time, as so as qBittorrent 4.6.x branch still compatible with older Qt6 and even 5.15

existing lt1.2 based nightly builds repo will be dropped very soon.

WolfganP commented 1 year ago

@WolfganP , I'll create new qbittorrent release package based on libtorrent 1.2 in "test" repo where lt2.0 based builds are available. release builds are available for Debian 11+ and for arm and x86, both 32 and 64 bit. and this will be supported for a long time, as so as qBittorrent 4.6.x branch still compatible with older Qt6 and even 5.15

Much appreciated @Kolcha , thanks a lot.

Kolcha commented 1 year ago

now latest release based on libtorrent 1.2 (static version) is also available in "test" repo (where stable release is available), package name is qbittorrent-lt12, both GUI and "nox" versions are available (append "-lt12" suffix to known package names)

WolfganP commented 1 year ago

now latest release based on libtorrent 1.2 (static version) is also available in "test" repo (where stable release is available), package name is qbittorrent-lt12, both GUI and "nox" versions are available (append "-lt12" suffix to known package names)

Qbt v4.5.5-nox-lt12 working perfectly from the new repository. Thanks a lot!

Updt: it just installed perfectly but doesn't actually work. Can't connect to trackers, saying "Permission denied". I'll troubleshoot and report back.

Updt2: seems like the new libraries and previous instance made a mess. A server restart solved all the issues. Thanks again!

scuffedjosh commented 4 weeks ago

Is Qbit version 5 coming any time soon?