Hello dkg!
I finally took the time to "become a historian" for smartlist.
This is now my working copy:
https://salsa.debian.org/sanvila/smartlist-not-yet
I'm going to use this email as a changelog for what I did:
- I've excluded releases 3.10-6 and 3.10-16 because they were under a non-DFSG
license.
License said "not to be sold", but there was an addendum from the author
saying
Debian and its derivatives were allowed to distribute it. However, since this
was
not enough (DFSG #8), the author finally made it GPL (and later GPL +
Artistic),
starting from version 3.11pre7 (3.10.7-x in Debian).
- I've excluded 3.15-5.woody.1 and 3.10.7-2bo5 because they were not uploads
for unstable,
and they would break the principle of "linear history". To be precise:
Release 3.15-5.woody.1 was an upload for "stable-security".
Release 3.10.7-2bo5 was an upload for "bo-unstable". I had to look for that
because
I forgot, and found this gem:
https://archive.debian.org/debian/dists/bo/bo-unstable/README
In other words, this was a "backports" repository before we started to use
the term later.
- In addition to snapshot.debian.org, I found some releases in my computer. The
series 3.15-x
is now almost complete. For some reason I did not keep 3.15-7 and 3.15-8.
Maybe the bugs
in the confirm suite were serious enough that I decided at the time that
those releases
were not worthy to be kept "for posterity".
- I had to fight with "gbp import-dsc", as it did not want to put the commits
in the
"right" order by default. If you do "git log" in your repo, you will see the
upstream 3.10 commit at the bottom, then upstream 3.10.7, then upstream 3.13,
while I expected 3.10-x debian releases to come after upstream 3.10 and so on.
Why does "gbp import-dsc" behave like that? I don't know, so I decided to
create the
repo using a script, which I attach for your amusement.
When it comes the time and I'm comfortable enough with this salsa thing, I'll
drop
the "-not-yet" prefix and add the vcs-* fiels to the control file (and only then
will close this bug).
Note: This has been fun, but it's not an invitation to submit merge request via
salsa...
While I still use smartlist myself, it's very old software and it's not actively
maintained by upstream, so I would advise users to look for alternatives.
Thanks.
#!/bin/sh
set -e
my_gbp_import_dsc() {
export GIT_AUTHOR_DATE="$1"
export GIT_COMMITTER_DATE="$1"
gbp import-dsc --author-date-is-committer-date --skip-debian-tag
../smartlist_${2}.dsc
export GIT_COMMITTER_DATE="$(dpkg-parsechangelog -SDate)"
gbp tag
}
my_gbp_import_dsc_simple() {
gbp import-dsc --author-date-is-committer-date --skip-debian-tag
../smartlist_${1}.dsc
export GIT_COMMITTER_DATE="$(dpkg-parsechangelog -SDate)"
gbp tag
}
git init
my_gbp_import_dsc "1997-06-18 12:00 UTC" "3.10.7-5"
my_gbp_import_dsc "1999-04-19 12:00 UTC" "3.13-2"
my_gbp_import_dsc_simple "3.13-3"
my_gbp_import_dsc "2001-01-14 12:00 UTC" "3.15-1"
for a in $(seq 2 6); do
my_gbp_import_dsc_simple 3.15-$a
done
for a in $(seq 9 26); do
my_gbp_import_dsc_simple 3.15-$a
done
