Ian Jackson <[email protected]> wrote:
> Thanks. This kind of use case has been discussed before, in eg
> #848193 and #877969. The hard part is deciding on the details of what
> the UI and behaviour shouold be.
Yes. I see in the other tickets that there's at least a distinction
between
(a) the most up-to-date version from the combination of package suites
that my apt is currently configured to talk to
(b) the specific version that is installed right this instant on my
machine, even if a later version is available via an 'apt update' I
haven't got round to running.
(I believe 'apt source' does (a).)
For my purposes I don't especially care about the difference, because I
apt update frequently in general, and moreover, if anything on my system
is actively confusing me, I'll probably do a precautionary update before
I put any real effort into figuring it out, in case it's been recently
fixed. So if (a) and (b) don't agree with each other, then my own
opinion is that that's on me, and I don't mind which dgit does.
But I can certainly see that other people might care!
Cheers,
Simon
--
for k in [pow(x,37,0x1a1298d262b49c895d47f) for x in [0x50deb914257022de7fff,
0x213558f2215127d5a2d1, 0x90c99e86d08b91218630, 0x109f3d0cfbf640c0beee7,
0xc83e01379a5fbec5fdd1, 0x19d3d70a8d567e388600e, 0x534e2f6e8a4a33155123]]:
print("".join([chr(32+3*((k>>x)&1))for x in range(79)])) # <[email protected]>
