search

aptly-dev / aptly

aptly - Debian repository management tool
https://www.aptly.info/
MIT License
2.58k stars 376 forks source link

aptly install fails -- aptly conflicts with gnupg1 #1394

Open sf-nwaller opened 3 days ago

sf-nwaller commented 3 days ago

While attempting to try out the Aptly 1.6.0 RC (release candidate) build I encountered this installation error:

~$ sudo dpkg -i aptly_1.6.0~rc1+20241117171302.763b810c_amd64.deb
dpkg: regarding aptly_1.6.0~rc1+20241117171302.763b810c_amd64.deb containing aptly:
 aptly conflicts with gnupg1
  gnupg1 (version 1.4.23-1.1build1) is present and installed.

dpkg: error processing archive aptly_1.6.0~rc1+20241117171302.763b810c_amd64.deb (--install):
 conflicting packages - not installing aptly
Errors were encountered while processing:
 aptly_1.6.0~rc1+20241117171302.763b810c_amd64.deb

I tried previous alpha and beta builds from the 1.6.0 line and they installed fine without any conflicts.

Is Aptly switching to gnupg2 with the 1.6.0 release?

Your Environment

I'm running Ubuntu 22.04 and I'm installing Aptly from a Debian package.

~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.5 LTS
Release:    22.04
Codename:   jammy
sf-nwaller commented 3 days ago

This error is explained by the updated Conflicts field in the Debian control file. Seems it was updated a couple days ago:

https://github.com/aptly-dev/aptly/commit/14e4f3dad8c3fb0764ba8a3e61bd2b912ab3cc99#diff-2a13f1344504379e877324d3a0375adcbcb4cb27d7e575ad8f4618a52d6a00e0R92

But I'm still not clear on the current and planned relationship between Aptly and gnupg.

neolynx commented 3 days ago

Thanks for reporting !

Since we synchronized with the official debian packaging, the Conflict was added. gnupg1 is depreciated, so I guess it is phased out. I will check with the upstream maintainer what the corresponding guidelines are...

However, aptly should not force this in the CI builds. I will revert the change, but until then you could add' -force-depends', as aptly has no hard dependency on gpg2.

neolynx commented 10 hours ago

So, the official debian is already conflicting with gpg1 packages, therefore at some point it would be good to migrate to gpg2 if that is possible. The CI packages will not conflict anymore after #1396 is merged, but we might add it again for the final 1.6.0 version.

would it be possible for you to use gpg2 ?