This item: "The apt(8) command no longer accepts regular expressions or wildcards as package arguments, use patterns (see New Features)."<p>Seems like a pretty big breaking change.
I wonder when will apt will start supporting specifying packages per repository. It's not safe how any package could come from any repository by-default, unless annoying effort is spent manually pinning packages.
Does it still redownload 30MB and spin for 10s when you (or an installer script) do “apt update” a few seconds after the last invocation of same instead of comparing a root hash or some other sane method?
After working with Debian/Ubuntu packaging, and switching to Arch and Pacman, it is so much easier to create/maintain packages on Arch and Alpine distros than the alternatives.
Argh. Was just upgrading a Debian machine and was wishing (again) for parallel downloads. <i>apt-fast</i> is a severely limited hack (I couldn't figure out what it actually supports). I assumed any significant apt update would include performance/DL improvement. No?
Cool!<p>Does anybody know if there are plans to fix the .deb size limit? It's a bummer that .debs can't be more than 10 GB. That number seems big, but I've hit it before when packaging custom toolchains for internal use at my company.
Missed opportunity to switch to zstd IMO. Much faster than gzip, especially during decompression, and essentially the same compression ratio. Them apt upgrades take too long.
I know they are kind of just wrapping aptitude but it's frustrating I can't just wildcard for things. It's a package manager not a development framework, why would regex and wildcard not be enough for anyone?