The test is well defined now, without spending more debug time let us
check how a blunt straight forward rebuild nowadays would behave.

If building as-is today the build dependencies turn out to be just the
very same as they were used in [1], so expectations for this are low
:-). And as expected it behaves the same.

Due to the way golang works, there is a plethora of toolchains in jammy
by now

$ apt search golang-1 | grep -e '[0-9]/'
golang-1.13/jammy-updates,jammy-security 1.13.8-1ubuntu2.22.04.2 all
golang-1.17/jammy-updates,jammy-security 1.17.13-3ubuntu1.3 all
golang-1.18/jammy-updates,jammy-security 1.18.1-1ubuntu1.2 all
golang-1.20/jammy-updates,jammy-security 1.20.3-1ubuntu0.1~22.04.1 all
golang-1.21/jammy-updates,jammy-security 1.21.1-1~ubuntu22.04.3 all
golang-1.22/jammy-updates,jammy-security 1.22.2-2~22.04.3 all
golang-1.23/jammy-updates,jammy-security 1.23.1-1~22.04.2 all

The dependencies are not that manyfold, they moved to the new versions before 
jammy was released.
root@j-aptly-updates:~# apt policy golang-golang-x-crypto-dev
golang-golang-x-crypto-dev:
  Installed: (none)
  Candidate: 1:0.0~git20211202.5770296-1
  Version table:
     1:0.0~git20211202.5770296-1 500
        500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages


So it is time to consider:
- building it with 1.17 again that worked before
- building it with something >1.18
- Check newer versions of aptly and dependencies in newer revisions (For 
example maybe it is a bug in golang-golang-x-crypto-dev)
- Debug what exactly is failing to come to the root cause (more work, but then 
less guessing)

@Allan since it was your change in the first place, any opinion or
preference?

[1]: https://launchpadlibrarian.net/759251044/buildlog_ubuntu-jammy-
amd64.aptly_1.4.0+ds1-6ubuntu0.1_BUILDING.txt.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2140498

Title:
  aptly fails to create new mirrors or decode previous mirror data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptly/+bug/2140498/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to