Upgrade conflict in /etc/apt/apt.conf.d/50unattended-upgrades

[benjaoming]

Wondering what I did for this to happen. Using Ubuntu 18.04. I don't think that I edited this manually.

It's trying to install unattended-upgrades (1.1ubuntu1.18.04.14) ...

Line by line differences between versions                                                                                        

Old file: /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2020-02-27 17:08:37                                           
New file: /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 2020-02-17 11:37:03                                    

// Unattended-Upgrade::Origins-Pattern controls which package | // Automatically upgrade packages from these (origin:archive)    
// upgraded. | //                                                                                                                
Unattended-Upgrade::Origins-Pattern { | // Note that in Ubuntu security updates may pull in new depen                            
 "origin=Ubuntu,archive=${distro_codename}-security"; | // from non-security sources (e.g. chromium). By allowing the            
 > // pocket these get automatically pulled in.                                                                                  
 > Unattended-Upgrade::Allowed-Origins {                                                                                         
 > "${distro_id}:${distro_codename}";                                                                                            
 > "${distro_id}:${distro_codename}-security";                                                                                   
 > // Extended Security Maintenance; doesn't necessarily                                                                         
 > // every release and this system may not have it inst                                                                         
 > // available, the policy for updates is such that una                                                                         
 > // should also install from here by default.                                                                                  
 > "${distro_id}ESMApps:${distro_codename}-apps-security                                                                         
 > "${distro_id}ESM:${distro_codename}-infra-security";                                                                          
 > // "${distro_id}:${distro_codename}-updates";                                                                                 
 > // "${distro_id}:${distro_codename}-proposed";                                                                                
 > // "${distro_id}:${distro_codename}-backports";                                                                               
 }; };                                                                                                                           

// List of packages to not update (regexp are supported) // List of packages to not update (regexp are supported)                
Unattended-Upgrade::Package-Blacklist { Unattended-Upgrade::Package-Blacklist {                                                  
 > // "vim";                                                                                                                     
 > // "libc6";                                                                                                                   
 > // "libc6-dev";                                                                                                               
 > // "libc6-i686";                                                                                                              
}; };                                                                                                                            

[benjaoming]

Confirmed on Ubuntu 16.04

Unpacking unattended-upgrades (1.1ubuntu1.18.04.7~16.04.6) over (1.1ubuntu1.18.04.7~16.04.5) ```

[jnv]

This role directly modifies that configuration file so it's not surprising you'd get conflicts during the upgrade. I have made a proposal in #32 to let this role manage its own file and keep the default configuration file untouched and there is a discussion about pros and cons so feel free to chime in.

[benjaoming]

@jnv thanks! I read through the PR and I think there is a solid case to rename the file.

[jnv]

I am closing this issue since this role has been deprecated. Feel free to suggest alternatives in #98.