Updates - Upgrade -> unstable packets ¿?

T

trantor

New Member
Proxmox Subscriber
Mar 5, 2019
16
0
1
48
i would like ask,
why when i'm going to updates -> Refresh and i see the changelog, i can read "unstable" ( in origin: debian )
i have a suscription on this server, is ok read in some packets, that it is unstable ¿?

Thanks!
 
hmm - which packets are 'unstable'?
please post the complete output in 'code' blocks
 
i posted on networking and firewall, this thread should be go to other section - sorry.
I updated the server, isn't on production yet.
But the packets are like to :
( tihs other server without suscripton now ): cups (2.2.1-8) unstable; urgency=medium
 
hmm - that's odd.

please post (again in code tags):
* `cat /etc/apt/sources.list`
* `cat /etc/apt/sources.list.d/*list`
 
thanks!

Code: 
cat /etc/apt/sources.list
deb http://ftp.es.debian.org/debian stretch main contrib
deb http://ftp.es.debian.org/debian stretch-updates main contrib
# security updates
deb http://security.debian.org stretch/updates main contrib

cat /etc/apt/sources.list.d/*list
deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise
 
that looks correct - but for me I see the last cups version as:
Code: 
cups (2.2.1-8+deb9u3) stretch; urgency=low
(so not from unstable)
please post the output of:
* `apt update`
* `apt full-upgrade`
 
Mmm on the updated server, i don't see cups, i see:

Code: 
dpkg -l | grep cups
ii  libcups2:amd64                       2.2.1-8+deb9u3                 amd64        Common UNIX Printing System(tm) - Core library
 
more info from the updated server.

pveversion -v

Code: 
pveversion -v
proxmox-ve: 5.3-1 (running kernel: 4.15.18-11-pve)
pve-manager: 5.3-9 (running version: 5.3-9/ba817b29)
pve-kernel-4.15: 5.3-2
pve-kernel-4.15.18-11-pve: 4.15.18-33
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-46
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-38
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-33
pve-container: 2.0-34
pve-docs: 5.3-2
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-17
pve-firmware: 2.0-6
pve-ha-manager: 2.0-6
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 3.10.1-1
qemu-server: 5.0-46
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1

apt-update
Code: 
apt update
Ign:1 http://ftp.es.debian.org/debian stretch InRelease
Hit:2 http://security.debian.org stretch/updates InRelease   
Hit:3 http://ftp.es.debian.org/debian stretch-updates InRelease
Hit:4 http://ftp.es.debian.org/debian stretch Release
Hit:6 https://enterprise.proxmox.com/debian/pve stretch InRelease
Reading package lists... Done
Building dependency tree       
Reading state information... Done

apt full-upgrade
Code: 
apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 
You don't have any upgrades available?
Where do you see the 'unstable'?

please post this output/screenshot
 
This server was updated yesterday.
I saw it on proxmox-webgui, the forms for update with the changelog etc. i haven't screenshot.
This server ins't in production yet.
Perhaps the most fast is reinstall the server :>
 
anyway with this all should be ok.
should readt the ChangeLog.
don't want bother more ;) thanks for your patience. I
thanks!

Code: 
cat /etc/apt/sources.list
deb http://ftp.es.debian.org/debian stretch main contrib
deb http://ftp.es.debian.org/debian stretch-updates main contrib
# security updates
deb http://security.debian.org stretch/updates main contrib

cat /etc/apt/sources.list.d/*list
deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise
 
having unstable in a changelog does not mean anything bad - almost all package releases are uploaded to Debian "unstable" first, then migrate to Debian "testing" (without a new changelog entry) which in turn becomes the next stable release after a period called "freeze" (which is currently happening for the next Debian release called "Buster"). the only packages which do not get uploaded to "unstable" initially are
- test packages uploaded to "experimental" (irrelevant for production systems)
- security or point release updates (those have the stable codename in the suite, e.g., "stretch-proposed-updates" or "stretch")
- backported backports (e.g., "stretch-backports")
 
Thanks for answer.
Today i see new options for update, by example:

Origin Proxmox:
libpve-common-perl
Code: 
libpve-common-perl (5.0-47) unstable; urgency=medium * partially fix #2023: Switch to https for yubico.com API * Fix 1891: Add zsh command completion generator -- Proxmox Support Team <support@proxmox.com> Wed, 20 Feb 2019 12:23:56 +0100

pve-docs
Code: 
pve-docs (5.3-3) unstable; urgency=medium * add zsh completion targets * improve gramar and typography * Fix #2018: CephFS client needs newer binaries * Fix #2015: add how to get a auth secret for cephfs -- Proxmox Support Team <support@proxmox.com> Wed, 20 Feb 2019 12:20:05 +0100

pve-kernel
Code: 
pve-kernel (4.15.18-34) unstable; urgency=medium * backport fix for possible ipset memory exhaustion bug * backport fix for possible use after free in crypto stack * backport fixes for multiple KVM vulnerabilities: CVE-2019-6974, CVE-2019-7221, CVE-2019-7222 -- Proxmox Support Team <support@proxmox.com> Mon, 25 Feb 2019 14:51:06 +0100

pve-manager
Code: 
pve-manager (5.3-11) unstable; urgency=medium * fix #2108: ceph: 'osd pools set' cannot accept integers anymore, thus ceph pool creation failed in some cases, e.g., CephFS creation over GUI, API or CLI and pool creation over CLI or API depending on parameters passed. -- Proxmox Support Team <support@proxmox.com> Wed, 20 Feb 2019 19:40:43 +0100

only this is setup as stable pve-qemu-kvm:
Code: 
pve-qemu-kvm (2.12.1-2) stable; urgency=medium * fix CVE-2019-3812: Out-of-bounds read in hw/i2c/i2c-ddc.c allows for memory disclosure * fix CVE-2018-18849: lsi53c895a: OOB msg buffer access leads to DoS * fix CVE-2018-20124: rdma: OOB access when building scatter-gather array * fix CVE-2019-6778: slirp: heap buffer overflow in tcp_emu() -- Proxmox Support Team <support@proxmox.com> Tue, 19 Feb 2019 09:28:42 +0100
 
apt update
Code: 
apt update
Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 http://ftp.es.debian.org/debian stretch InRelease
Get:3 http://ftp.es.debian.org/debian stretch-updates InRelease [91.0 kB]
Hit:4 https://enterprise.proxmox.com/debian/pve stretch InRelease
Hit:5 http://ftp.es.debian.org/debian stretch Release
Fetched 91.0 kB in 0s (150 kB/s)                   
Reading package lists... Done
Building dependency tree       
Reading state information... Done
5 packages can be upgraded. Run 'apt list --upgradable' to see them.

apt full-upgrade
Code: 
apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libpve-common-perl pve-docs pve-kernel-4.15.18-11-pve pve-manager
  pve-qemu-kvm
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 72.8 MB of archives.
After this operation, 37.9 kB of additional disk space will be used.
Do you want to continue? [Y/n]

and one screenshot
 

Attachments

  • unstableproxmox.jpg
    unstableproxmox.jpg
    110.6 KB · Views: 6
The "unstable" in the changelog entry is the pocket into which a package gets uploaded. For cups 2.2.1-8 that was the version that got uploaded to Debian unstable back in 2017, before stretch was released. That's the way the package workflow works within Debian.

As for the proxmox packages, we actually do write unstable in there, but it is of no real relevance, as the way we maintain our package archives isn't using that part. The packaging toolchains though defaults to writing "unstable" in there and we didn't bother to change it. Like said, it has no influence for our infrastructure. What is of relevance is where you pull the packages from. You can see that when using e.g. "apt-cache policy libpve-common-perl" on the package to see where an update would get pulled from.

Sorry if that cause confusion
 
  • Like
Reactions: mhagen and James Crook
rhonda said:
The "unstable" in the changelog entry is the pocket into which a package gets uploaded. For cups 2.2.1-8 that was the version that got uploaded to Debian unstable back in 2017, before stretch was released. That's the way the package workflow works within Debian.

As for the proxmox packages, we actually do write unstable in there, but it is of no real relevance, as the way we maintain our package archives isn't using that part. The packaging toolchains though defaults to writing "unstable" in there and we didn't bother to change it. Like said, it has no influence for our infrastructure. What is of relevance is where you pull the packages from. You can see that when using e.g. "apt-cache policy libpve-common-perl" on the package to see where an update would get pulled from.

Sorry if that cause confusion
Click to expand...

I just had this ! Have a node with a subscription, but two others with non, and the packages were all marked as unstable.

Many thanks for this info.
 
You must log in or register to reply here.
Top Bottom