Gesucht: Lösung / Workaround für fehlendes/umbenanntes Paket

KaiS

Active Member
Feb 20, 2019
62
7
28
55
Ich versuche derzeit den "Synology Backup for Business Agent" auf meinen Prxmox VE nodes zu installieren.

Wie in einem anderen Thread gelesen scheitert das Installationsskript jedoch an einer Stelle, wenn versucht wird das Standard Paket:

linux-headers-5.4.78-2-pve

zu installieren und bricht dann ab, da es nicht gefunden werden kann.

Der Proxmox Support schrieb im anderen thread dazu:

------------------------------------------------------------------------------------
bei pmg/pve/pbs heißt das paket einfach anders, nämlich pve-headers-5.4.78-2-pve
-------------------------------------------------------------------------------------

Also habe ich naiv versucht pve-headers-5.4.78-2-pve manuell vorzuinstallieren, was auch geklappt hat.

Das Installationsskript will jedoch weiterhin das Paket linux-headers-5.4.78-2-pve

Jetzt meine Frage: Kennt jemand einen Workaround für dieses bzw. solch ein Problem?

Kann man irgendwie im System eine Art Alias setzen (eventl. mit einem Link?) der dem Installationsskript die pve-headers-5.4.78-2-pve unter dem Namen linux-headers-5.4.78-2-pve ausliefert?

Wäre toll, wenn jemand eine Idee hätte.

Viele Grüße,
Kai
 
hi,

Jetzt meine Frage: Kennt jemand einen Workaround für dieses bzw. solch ein Problem?

kann man nicht bei dem installation skript das bearbeiten und dieses paket weglassen?
 
equivs waere sonst eine moeglichkeit ein 'fake' linux-headers-.. paket das auf pve-headers-... zeigt zu erzeugen..
 
hi,



kann man nicht bei dem installation skript das bearbeiten und dieses paket weglassen?
Soweit ich es verstehe hat das Installationsscript eine umfangreiche eingebaute Checksummen Überprüfung und Teiel des Codes sind auch binär hinterlegt. Einfache Versuche das Script zu bearbeiten sind daran gescheitert :-(
 
yeah, run equivs-control linux-headers-XX.ctl, then open that file in an editor and adapt the Package and Depends lines (Package should be linux-headers-XX, Depends should contain pve-headers-XX, where XX is the kernel version you want to support), set a meaningful description so you still know where those packages come from in two years ;)

then run equivs-build linux-headers-XX.ctl, and you should get a (metadata only) package called linux-headers-XX in version 1.0 that just pulls in the actual headers package pve-headers-XX:

Code:
$ cat linux-headers-ctl
### Commented entries have reasonable defaults.
### Uncomment to edit them.
# Source: <source package name; defaults to package name>
Section: misc
Priority: optional
# Homepage: <enter URL here; no default>
Standards-Version: 3.9.2

Package: linux-headers-5.13.19-1-pve
# Version: <enter version here; defaults to 1.0>
# Maintainer: Your Name <yourname@example.com>
# Pre-Depends: <comma-separated list of packages>
Depends: pve-headers-5.13.19-1-pve
# Recommends: <comma-separated list of packages>
# Suggests: <comma-separated list of packages>
# Provides: <comma-separated list of packages>
# Replaces: <comma-separated list of packages>
# Architecture: all
# Multi-Arch: <one of: foreign|same|allowed>
# Copyright: <copyright file; defaults to GPL2>
# Changelog: <changelog file; defaults to a generic changelog>
# Readme: <README.Debian file; defaults to a generic one>
# Extra-Files: <comma-separated list of additional files for the doc directory>
# Links: <pair of space-separated paths; First is path symlink points at, second is filename of link>
# Files: <pair of space-separated paths; First is file to include, second is destination>
#  <more pairs, if there's more than one file to include. Notice the starting space>
Description: Package to make synology backup agent happy
 Built using equivs, can be removed together with kernel/headers package.

$ dpkg -I linux-headers-5.13.19-1-pve_1.0_all.deb
 new Debian package, version 2.0.
 size 2252 bytes: control archive=612 bytes.
     366 bytes,    11 lines      control
     265 bytes,     3 lines      md5sums
 Package: linux-headers-5.13.19-1-pve
 Version: 1.0
 Architecture: all
 Maintainer: Fabian Grünbichler <f.gruenbichler@proxmox.com>
 Installed-Size: 9
 Depends: pve-headers-5.13.19-1-pve
 Section: misc
 Priority: optional
 Multi-Arch: foreign
 Description: Package to make synology backup agent happy
  Built using equivs, can be removed together with kernel/headers package.

you might need to repeat this for every kernel upgrade that ships a new ABI, not sure what synology is doing there or why it requires the headers to be installed in the first place ;)
 
  • Like
Reactions: UdoB
Hi Fabian, thanks for your advise. Unfortunally I still have the issue.

I first installe equivs with

apt install equivs

After that I do:

equivs-control linux-headers-5.13.19-1-pve.ctl

and paste your text:

### Commented entries have reasonable defaults.
### Uncomment to edit them.
# Source: <source package name; defaults to package name>
Section: misc
Priority: optional
# Homepage: <enter URL here; no default>
Standards-Version: 3.9.2

Package: linux-headers-5.13.19-1-pve
# Version: <enter version here; defaults to 1.0>
# Maintainer: Your Name <yourname@example.com>
# Pre-Depends: <comma-separated list of packages>
Depends: pve-headers-5.13.19-1-pve
# Recommends: <comma-separated list of packages>
# Suggests: <comma-separated list of packages>
# Provides: <comma-separated list of packages>
# Replaces: <comma-separated list of packages>
# Architecture: all
# Multi-Arch: <one of: foreign|same|allowed>
# Copyright: <copyright file; defaults to GPL2>
# Changelog: <changelog file; defaults to a generic changelog>
# Readme: <README.Debian file; defaults to a generic one>
# Extra-Files: <comma-separated list of additional files for the doc directory>
# Links: <pair of space-separated paths; First is path symlink points at, second is filename of link>
# Files: <pair of space-separated paths; First is file to include, second is destination>
# <more pairs, if there's more than one file to include. Notice the starting space>
Description: Package to make synology backup agent happy
Built using equivs, can be removed together with kernel/headers package.




Next step was:

equivs-build linux-headers-5.13.19-1-pve.ctl

Output was:



dpkg-buildpackage: info: source package linux-headers-5.13.19-1-pve
dpkg-buildpackage: info: source version 1.0
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Equivs Dummy Package Generator <root@pve.ahhhkah.local>
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build .
debian/rules clean
dh clean
dh_clean
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
create-stamp debian/debhelper-build-stamp
dh_prep
dh_install
dh_installdocs
dh_installchangelogs
dh_perl
dh_link
dh_strip_nondeterminism
dh_compress
dh_fixperms
dh_missing
dh_installdeb
dh_gencontrol
dh_md5sums
dh_builddeb
dpkg-deb: building package 'linux-headers-5.13.19-1-pve' in '../linux-headers-5.13.19-1-pve_1.0_all.deb'.
dpkg-genbuildinfo --build=binary
dpkg-genchanges --build=binary >../linux-headers-5.13.19-1-pve_1.0_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)

The package has been created.
Attention, the package has been created in the current directory,
not in ".." as indicated by the message above!


Next Step: dpkg -I linux-headers-5.13.19-1-pve_1.0_all.deb


Output:
new Debian package, version 2.0.
size 2264 bytes: control archive=620 bytes.
373 bytes, 11 lines control
265 bytes, 3 lines md5sums
Package: linux-headers-5.13.19-1-pve
Version: 1.0
Architecture: all
Maintainer: Equivs Dummy Package Generator <root@pve.ahhhkah.local>
Installed-Size: 9
Depends: pve-headers-5.13.19-1-pve
Section: misc
Priority: optional
Multi-Arch: foreign
Description: Package to make synology backup agent happy
Built using equivs, can be removed together with kernel/headers package.
root@pve:~# Next Step:
-bash: Next: command not found
root@pve:~# dpkg -I linux-headers-5.13.19-1-pve_1.0_all.deb
new Debian package, version 2.0.
size 2264 bytes: control archive=620 bytes.
373 bytes, 11 lines control
265 bytes, 3 lines md5sums
Package: linux-headers-5.13.19-1-pve
Version: 1.0
Architecture: all
Maintainer: Equivs Dummy Package Generator <root@pve.ahhhkah.local>
Installed-Size: 9
Depends: pve-headers-5.13.19-1-pve
Section: misc
Priority: optional
Multi-Arch: foreign
Description: Package to make synology backup agent happy
Built using equivs, can be removed together with kernel/headers package.


Looks very good for me - so far. ut now I tried to start my installation script again:

./install.run

And still get the error:

Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing Active Backup for Business Agent 100%
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.de.debian.org/debian bullseye InRelease
Hit:3 http://ftp.de.debian.org/debian bullseye-updates InRelease
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
12 packages can be upgraded. Run 'apt list --upgradable' to see them.
* start checking dependency of (4)
* checking linux-headers-5.13.19-1-pve
* found linux-headers-5.13.19-1-pve not installed, install automatically
* installing linux-headers-5.13.19-1-pve
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-headers-5.13.19-1-pve
E: Couldn't find any package by glob 'linux-headers-5.13.19-1-pve'
* install linux-headers-5.13.19-1-pve failed, please try again later, or run 'apt install linux-headers-5.13.19-1-pve manunally or download and install package from https://packages.debian.org/bullseye/linux-headers-5.13.19-1-pve



Can you help? I think the name of the self builded package is not right or it´s on the wrong path?

Best regards,
Kai
 
you have to install it ;) apt install ./path-to-file.deb
 
Ok, sorry ...haha, I installed it.

After that I run the Synology install script. It was running a bit longer, but unfortunally I got another error depending to the headers (i think):

root@pve:~# ./install.run
Verifying archive integrity... 100% MD5 checksums are OK. All good.
Uncompressing Active Backup for Business Agent 100%
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.de.debian.org/debian bullseye InRelease
Hit:3 http://ftp.de.debian.org/debian bullseye-updates InRelease
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
12 packages can be upgraded. Run 'apt list --upgradable' to see them.
* start checking dependency of (4)
* checking linux-headers-5.13.19-1-pve
* linux-headers-5.13.19-1-pve has already installed
* checking dkms
* dkms has already installed
* checking make
* make has already installed
* checking libaio1
* libaio1 has already installed
* start installing snapshot driver and agent service
* snapshot driver has not installed, installing snapshot driver
* installing synosnap-0.10.16.deb
(Reading database ... 73709 files and directories currently installed.)
Preparing to unpack synosnap-0.10.16.deb ...
installed synosnap version is newer or equal
dpkg: warning: old synosnap package pre-removal script subprocess returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK
Unpacking synosnap (0.10.16) over (0.10.16) ...
Setting up synosnap (0.10.16) ...
Removing old synosnap-0.10.16 DKMS files...

------------------------------
Deleting module version: 0.10.16
completely from the DKMS tree.
------------------------------
Done.
Loading new synosnap-0.10.16 DKMS files...
Building for 5.13.19-1-pve
Building initial module for 5.13.19-1-pve
xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
Error! Bad return status for module build on kernel: 5.13.19-1-pve (x86_64)
Consult /var/lib/dkms/synosnap/0.10.16/build/make.log for more information.
dpkg: error processing package synosnap (--install):
installed synosnap package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
synosnap
* failed to install snapshot driver


:_(


Horrible
 
Consult /var/lib/dkms/synosnap/0.10.16/build/make.log for more information.
 
Yes I know. Thank you. But thats way of my knowledge. See attachement

Because of some "redeclaration" errors I think the source of the errors ar my self build .deb package. All functions inside are now twice in the system....
 

Attachments

  • make.zip
    52.2 KB · Views: 4
Hallo Fabian,

Danke für den Hinweis. Ich habe ein ProxMoxVE5 in meinem Lab installiert, bin ale Schritte nochmal durchgegangen und:

Es hat geklappt!

Vielen Dank für Deine tolle Hilfe!

Der Synology Backup Client läuft gut :)

Viele Grüße,
Kai
 
  • Like
Reactions: fabian

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!