Hi, Am Freitag, den 22.06.2018, 22:31 +0000 schrieb Clint Adams: > On Fri, Jun 22, 2018 at 05:36:52PM +0200, Mikolaj Konarski wrote: > > 15:33 < dcoutts> mikolaj: yes, all revisions are in the "01" tarball > > 15:33 < dcoutts> but if you unpack with standard 'tar' tools they only > > unpack out the last one > > 15:34 < dcoutts> if you use the Haskell 'tar' lib you can select the > > first if you like > > 15:35 < dcoutts> or e.g. if you want all updates up to a certain date, > > but none after, then take the prefix of the tarfile up to one record > > 15:36 < dcoutts> that's what the cabal update --index-state=STATE does > > Interesting. So test-packages.pl could be rewritten to always > grab the earliest-dated instance of each cabal file needs patching. yes, I think so. Note that I intentionally did not make it completely ignore revisions. Consider this situation: * Debian has text-1.0 and foo-1.0 * foo-1.0r0 depends on text < 1.1 * Later someone added a revision to foo, and foo-1.0r1 depends on text < 1.2 * I plan to upgrade text to 1.1, so I bump it in the package plan. I do this to find out what packages this will break. Under the current scheme, test-packages will not complain, because foo is compatible with 1.1. I go ahead and upgrade text. If we change that, it would say that I cannot upgrade text yet because it believes some reverse dependencies are not compatible with the new version yet. But the script could be smarter about applying the patches to the pristine versions rather than to revisions. Cheers, Joachim -- Joachim “nomeata” Breitner • nomeata@debian.org • https://j.oach.im/
Attachment:
signature.asc
Description: This is a digitally signed message part