Package arch change from any to all causing problems with availability
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi guys
I have problem with package in DAK which arch has been changed from i386
to all (source any to all).
Original package in repo was 1.2-1_i386 but it should be 1.2-1_all so I
fixed it and uploaded 1.2-2_all, DAK added this package into Packages.gz
for binary-all but apt on installation targeted host is not picking up
this change and package is not available for it.
If I manually add whole entry for this package into
_contrib_binary-i386_Packages on machine which is intended installation
onto and run 'apt-get install package' it will pick up 1.2-2_all and
install it, but if package will be purged and 'apt-get update' run all
above is gone.
When 1.2-3_i386 is created and uploaded to DAK, processed it has been
added into binary-i386/Packages.gz and is available via apt without any
problems.
Thus I have a question: any ideas why it's behaving like that and how to
make above arch change to make 1.2-2_all available via apt, as package
is just a bunch of php scripts and is not arch dependant.
- --
|_|0|_| |
|_|_|0| "Heghlu'Meh QaQ jajVam" |
|0|0|0| -------- kuLa --------- |
gpg --keyserver pgp.mit.edu --recv-keys 0x58C338B3
3DF1 A4DF C732 4688 38BC F121 6869 30DD 58C3 38B3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJPIBRFAAoJEGhpMN1YwzizL1EP/04LihZl8tkrNhMa7a5skMHf
r9Aekk6T986AvhPRugdCeF4+gizZSqPMPcMHRr0MG+BA5pza++GXImI0PoVktN6P
c5T2dGS3O+XL909gEroJ81M91F7Ghl1aKH9AYIE1bnx4iGQXx9qFKnOQtjomq8WM
XTtCeEp0SkCV328cSrEI69jDhPFmD8NC9L/A4nDzTSnaS3oIi1VCw6/aVOZ/pY7v
INuQZ3XyQoU1U6C6Dc5rPH7MXuyKVYXUH91nLpCCe6yDW92pkLEidJwexN++Aj2d
SEH2OWpf4REg7g1HDgpxLzdHvVn7SpBd4mLNkY7DSgJd5t660WYEnBM03bropO2k
86sqfzoRl6mcSg7jhSOzdtsYGTf9qXWw94Kk7SIHXm1cD6pIVK9R9nEyVSiiUifF
bJTZ/mxtKMyy5ymFYJ5eqZ6/KGgqBtJb2b4NmvNfiOpUpBbsQCuC8lZbRU5pmoPA
DYMtywoQ2HrWtxkK9X2HHBrmuMDLgxNhECc7j3lD+Y7gBPGMByX7ItXHYNvn7GS2
iPJjHlMHCW6BxpjQWG8KQU4XymhoRP0ENDoZHhSpAlJaOji27+NxbOxLjS13akWt
v8ohZo9oxHvxVhVsGdaKMirZSAPE3t7EblwN8by8HdxNjAUeOz3ygTudR4WbYRpf
RcKVlzteTairdrG1flYn
=Vu5t
-----END PGP SIGNATURE-----
Reply to: