On 10/22/2017 10:10 AM, Alessandro Selli wrote: > On Sun, 22 Oct 2017 at 08:22:57 -0400 > fsmithred <[email protected]> wrote: > >> On 10/22/2017 06:51 AM, Alessandro Selli wrote: >>> On Sun, 22 Oct 2017 at 06:33:58 -0400 >>> fsmithred <[email protected]> wrote: >>> >>>> On 10/22/2017 05:18 AM, Alessandro Selli wrote: >>>>> On Fri, 20 Oct 2017 at 16:47:57 -0500 >>>>> [email protected] wrote: >>>>>> We are happy to announce that 'amprolla3', the rewrite of nextime's >>>>>> amprolla by parazyd and Wizzup, is finally up and running and ready >>>>>> to be tested. >>>>> >>>>> All right, tested: >>>>> 164 packages upgraded, >>>>> 74 installed. >>>>> >>>>> Kernel went from linux-image-4.9+80+deb9u2-amd64 to >>>>> linux-image-4.12.0-0.bpo.2-amd64, libreoffice went from 5.2.7-1 to >>>>> 5.4.1-1, tor from 0.2.9.11-1 to 0.3.1.7-1, pulseaudio is still out of >>>>> the way and, as far as I'm concerned, everything, including https://, >>>>> works like a charm. >>>> >>>> >>>> Your libreoffice went from ascii to buster and tor went from ascii to >>>> buster/sid/ceres. Does your sources.list say "testing" instead of >>>> "ascii"? >>> >>> No, but I have ascii-backports configured, could that be the reason? >>> >>> >>> >> >> If it's from backports, there should be a bpo in the version. Other than >> that, the numbers are the same for ascii-backports and buster. Here's the >> full list of what I find for libreoffice. (Note: I don't install anything >> or upgrade with these sources enabled.) >> >> $ apt-cache policy libreoffice >> libreoffice: >> Installed: 1:4.3.3-2+deb8u7 >> Candidate: 1:5.4.1-1~bpo9+1 > > [...] > > Sorry I didn't check it myself, but I'm very busy today (SMAU and LinuxDay > coming next week). Well yes, they're from backports: > > $ apt-cache policy libreoffice-core tor > libreoffice-core: > Installed: 1:5.4.1-1~bpo9+1 > Candidate: 1:5.4.1-1~bpo9+1 > Version table: > *** 1:5.4.1-1~bpo9+1 500 > 500 https://pkgmaster.devuan.org/merged ascii-backports/main amd64 > Packages 100 /var/lib/dpkg/status > 1:5.2.7-1 500 > 500 https://pkgmaster.devuan.org/merged ascii/main amd64 Packages > tor: > Installed: 0.3.1.7-1~bpo9+1 > Candidate: 0.3.1.7-1~bpo9+1 > Version table: > *** 0.3.1.7-1~bpo9+1 500 > 500 https://pkgmaster.devuan.org/merged ascii-backports/main amd64 > Packages 100 /var/lib/dpkg/status > 0.2.9.12-1 500 > 500 https://pkgmaster.devuan.org/merged ascii-security/main amd64 > Packages 0.2.9.11-1~deb9u1 500 > 500 https://pkgmaster.devuan.org/merged ascii/main amd64 Packages > > > Didn't think about disabling backports before doing the update/upgrade, i > should have. Well, even then amprolla3 didn't do anything wrong, to my > utmost pleasure. Thank you, guys! >
Backports should have a lower priority to prevent this kind of thing from happening. 100 http://debian.csail.mit.edu/debian/ stretch-backports/main amd64 release o=Debian Backports,a=stretch-backports,n=stretch-backports,l=Debian Backports,c=main 500 http://pkgmaster.devuan.org/merged/ ascii-backports/main amd64 release v=2.0.0,a=testing-backports,n=ascii-backports,l=Devuan,c=main fsmithred _______________________________________________ Dng mailing list [email protected] https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
