Letsencrypt added Wheezy's backports repo to Virtualmin, and I now receive package updates emails about those backports


It started a week ago, in my inbox, in place of the regular usual emails from Virtualmin to tell me there were package updates, I started receiving wrong emails from virtualmin to tell me there were package updates.

An example:
“Package updates on ns***************”
“(…) An update to postfix from 2.9.6-2 to 2.11.2-1~bpo70+1 is available. (…)”

Of course, when I go to the package updates section of virtualmin, nothing is mentioned. Please notice the “bpo” part in the packet name.
I searched, and found the addition, one week ago, of /etc/apt/sources.list.d/wheezy-backports.list , that’s the one calling for the backports.

And I finally correlated this to my installation of Letsencrypt, that I ran following strictly this guide: https://www.virtualmin.com/node/38853

I wouldn’t have imagined there’d be a relation, but the time stamps on the files of letsencrypt and in /etc/apt/sources.list.d/ are very precisely matching, while I did nothing else in my shell in the two days before and after this event.

So, please, may I ask if, in somebody’s eyes, there is a logical explanation here ?
My wheezy isn’t obsolete yet, my web searches didn’t return something particular linking letsencrypt, debian wheezy and the backports… so I’m kinda stuck.

If someone has an idea (for instance: is it safe to dectivate the backports call in /etc/apt ?), I will be most grateful to read it, thank you :slight_smile:

Replying to myself. I had help elsewhere, so I come to report about it.

Letsencrypt only exists as a Stretch Debian package family, not as Jessie or WHeezy.

Demonstration: searching for “strech” in the Debian package list
If you try to do the same search on any other, Jessie, Wheezy and such, there will be no results.

This is seriously weird, please, is it normal that the addition of wheezy-backports.list to /etc/apt/sources.list.d/ made by Letsencrypt, results in a change in the emails virtualmin is sending me about updates, and would you know if there’s a way around it ?

I understand that removing the entry for wheezy-backports.list would be a mistakes as updates to letsencrypt would cease, but, still… it’s a temptation to get rid of it…