Wed Oct 23 13:38:30 CEST 2013, chris

metapackage "kernel-headers 3.X" would ease upgrades

Tue Sep 3 17:29:19 CEST 2013, chris

kernel-image should alternatively depend on grub2 (grub-pc >= 1.99 ?)

Mon Jul 15 14:58:19 CEST 2013, chris

for compiling ancient (not listed on Welcome_to_Linux-VServer.org) 
kernels the detection of corresponding patches doesn't work. 
We have to dig this information from 
http://vserver.13thfloor.at/Experimental/ et. al.

Mon Apr 15 14:36:22 CEST 2013, chris

firmware-paket(e) aus kernel-firmware-repository erzeugen

Mon Apr 15 14:36:22 CEST 2013, chris

build i386 kernels

Tue Oct 1 15:20:53 CEST 2013, chris (closed 2013-01-01, chris)

 kernel < 3.7.0 has no ipv6 nat - so skip this test in "internal-tests"

Mon Sep 30 17:46:16 CEST 2013, chris (closed 2013-09-30, chris)

error conditions from the iptables tests do not reach kernel_autobuild, 
so they do not cause program termination

Tue Sep 3 16:17:28 CEST 2013, chris (closed 2013-09-10, chris)

version of metapackage lacks "+lihasX" version string part
fix: kab_build_meta_package:
     CHANGELOG_VERSION=$KSRCVER--${PVER}--${SEQUENTIAL} 
  -> CHANGELOG_VERSION=$KSRCVER-${PVER}+${PROVIDER_TAG}${SEQUENTIAL}
PROVIDER_TAG set to "lihas" in /etc/kernel-autobuild.conf

Tue Sep 3 18:26:41 CEST 2013, chris (closed 2013-09-10, chris)

PROVIDER_TAG durchgaengig einsetzen:
- cmdline parameter
- cmdline parameter f. modules

Wed Apr 17 11:19:44 CEST 2013, chris (closed 2013-09-10, chris)

enable multiple file uploads in one single http-request on repository 

Tue Sep 3 18:29:22 CEST 2013, chris (closed 2013-09-04, chris)

#cpu as set in /etc/kernel-autobuild.conf does not appear in build module
fix: set defaults /before/ reading /etc/kernel-autobuild.conf

Mon Sep 2 19:07:51 CEST 2013, chris (closed 2013-09-03, chris)

not exactly suitable dependency:
apt-get install linux-image-3.10-vserver-amd64
The following packages will be REMOVED:
  linux-firmware-image-3.4 linux-image-3.4-vserver-amd64

fix: 3.4 uses /lib/firmware so we need depend, conflict, provide firmware set to "linux-firmware-image"
     3.(>=7) uses /lib/firmware/X.Y.Z so depend on $fullversion, provide $fullversion, conflict $fullversion
 so there is a modified patch against script/package/builddeb named patch-scripts-package-builddeb-v3.7+.diff

		19c19
		< +fwpackagename=linux-firmware-image-$version_12
		---
		> +fwpackagename=linux-firmware-image-$version
		52c52
		< +Recommends: $fwpackagename (>= ${version}), util-vserver
		---
		> +Recommends: $fwpackagename, util-vserver
		72,74c72,74
		< +Conflicts: linux-firmware-image
		< +Replaces: linux-firmware-image
		< +Provides: linux-firmware-image
		---
		> +Conflicts: $fwpackagename
		> +Replaces: $fwpackagename
		> +Provides: $fwpackagename

Mon Sep 2 17:48:03 CEST 2013, chris (closed 2013-09-03, chris)

kernel-autobuild --pver vs2.3.6.6 ... dies, because without retrieving the patch version it also lacks the patch url.
fix: kab_identify_vserver_patch returns PURL="", KURL="", PKVER="" if given "--pver"

Wed Aug 27 15:09:58 CEST 2013, chris (closed 2013-08-27, chris)

build process produces (u.a.):
linux-firmware-image-3.10_3.10.9-vs2.3.6.6+lihas1+lihas1+lihas1+lihas1+lihas1-1_amd64.deb
linux-headers-3.10.9-vs2.3.6.6+lihas1+lihas1+lihas1+lihas1+lihas1_3.10.9-vs2.3.6.6+lihas1+lihas1+lihas1+lihas1+lihas1-1_amd64.deb
linux-image-3.10.9-vs2.3.6.6+lihas1+lihas1+lihas1+lihas1+lihas1_3.10.9-vs2.3.6.6+lihas1+lihas1+lihas1+lihas1+lihas1-1_amd64.deb
linux-libc-dev-3.10_3.10.9-vs2.3.6.6+lihas1+lihas1+lihas1+lihas1+lihas1-1_amd64.deb

only happens if the same packet is rebuilt with "no-download" 
cause: patchfile is overwritten by kab_apply_vserver_patch
solved: changed name (suffix .mod) of the file to be written and used to patch the kernel afterward

Mon Jul 15 14:55:03 CEST 2013, chris (fixed some time before 2013-09-03, chris)

f. 3.9er kernel ist jeweils ein firmware-paket pro image notwendig,
da der Pfad komplett codiert ist:

init:/lib/firmware> ls -l
drwxr-xr-x 31 root root  4096 Jul 15 14:44 3.9.10-vs2.3.6.5+lihas1/

init:/lib/firmware> uname -a
Linux init 3.9.6-vs2.3.6.5+lihas1 #1 SMP Fri Jun 14 14:01:03 CEST 2013 x86_64 GNU/Linux

todo: change control file

Mon Apr 15 14:36:22 CEST 2013, chris (closed 2013-05-20, chris)

kernel 3.4 zieht firmware-package 3.7.10 an.
dies legt ein eigenes unterverzeichnis mit kernel-version an, 
kernel 3.4 kommt dann nicht an die firmware

apt-get -d install linux-image-3.4-vserver-amd64
-> 
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Note, selecting 'linux-image-3.4-vserver-amd64' for regex 'inux-image-3.4-vserver-amd64'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   linux-image-3.4-vserver-amd64 : Depends: linux-firmware-image (= 3.4.40-vs2.3.3.9+lihas1-1) but 3.7.10-vs2.3.5.6+lihas1-1 is to be installed
  E: Broken packages

$ apt-cache policy linux-firmware-image                 
linux-firmware-image:
  Installed: (none)
  Candidate: 3.7.10-vs2.3.5.6+lihas1-1
  Version table:
     3.7.10-vs2.3.5.6+lihas1-1 0
        200 http://ftp.lihas.de/lihas-kernel/ stable/main amd64 Packages
     3.4.40-vs2.3.3.9+lihas1-1 0
        200 http://ftp.lihas.de/lihas-kernel/ stable/main amd64 Packages
	...

Hmmm, da bleibt nur, linux-firmware-image im namen mit einer versionnummer zu versehen.
-> kernel patchen.

in scripts/package/builddeb
	fwpackagename=linux-firmware-image
	->
	fwpackagename=linux-firmware-image-$version

Mon Apr 15 14:36:22 CEST 2013, chris (closed 2013-05-20, chris)

ich hab mir grade mal Spa?eshalber so nen vServer Kernel von Dir gezogen.

erst mal schl?gt das beschriebene

   apt-get install linux-image-3.4-vserver-amd64

fehl, weil es versucht, den 3.7er kernel zu laden ...


Hab also dann zu Fuss den 3.4.39-vs2.3.3.9+lihas1 geladen.
Funzt so weit ganz gut, aber mein Firewall-Script kommt nicht
mehr hoch mit den durch libvirtd eingetragenen Erg?nzungen.

Konkret h?ngt es an der CHECKSUM Target, die in Deinem kernel fehlt.

  iptables -t mangle -A POSTROUTING -o virbr0 -p udp -m udp --dport 68 -j
  CHECKSUM --checksum-fill

geht nicht.

Sun, 07 Apr 2013 18:03:24 +0000, chris

beim durchfuehren von "aptitude update" kommt folgende Fehlermeldung:

W: Herunterladen von gzip:/var/lib/apt/lists/partial/ftp.lihas.de_lihas-kernel_dists_stable_main_binary-i386_Packages

fehlgeschlagen: Hash-Summe stimmt nicht überein
E: Some index files failed to download. They have been ignored, or old
ones used instead.
E: Paket-Zwischenspeicher konnte nicht neu erzeugt werden

Status: closed - not reproduceable