Bug#840122: Incorrect idescription in debian/copyright
Okay, I merged your NMU etc. One question. I didn't understand this: > It seems I should have added symlink in debian/rules as > cd debian/fossil/usr/share/bash-completion/completions; \ > ln -sf fossil f > to make it work in the first invocation. and couldn't find documentation about adding such a link. So I skipped it, in case there was a typo or some such. But if you could explain, or even better send a pointer, I'd appreciate it. Cheers, --Barak.
Bug#840122: Incorrect idescription in debian/copyright
As one point apparently fossil could use a git repo as its database. There really isn't any particular semantic mismatch. But that code was experimental and isn't in the current main release. I also am a git person. But I cannot really package fossil without doing it in a fossil repo, right? There is an easy way to import/export fossil/git though, see below. Which I have not used. Anyway, thanks again for the patch. I will pull it into my packaging repo when I get a chance. Will add and test your bash completion link above when I do that. Cheers, --Barak. $ fossil export --help Usage: fossil export --git ?OPTIONS? ?REPOSITORY? Write an export of all check-ins to standard output. The export is written in the git-fast-export file format assuming the --git option is provided. ...
Bug#840122: Incorrect idescription in debian/copyright
Hi, On Sun, Oct 09, 2016 at 04:05:14PM +0100, Barak A. Pearlmutter wrote: > Would you like to co-maintain? Thanks. No I am handful. I only worked on low hanging fruits for fossil this time. My patches are available in BTS and my NMU in unstable. It seems I should have added symlink in debian/rules as cd debian/fossil/usr/share/bash-completion/completions; \ ln -sf fossil f to make it work in the first invocation. I am mostly "git" person. My interest was fossil's good personal wiki feature with cryptography embedded. As I see, tough problem is: #828301 FTBFS with openssl 1.1.0 fossil repo has some code already. If git, I would cherry pick ... but I have no idea how I work with fossil. If I package, I import upstream into git branch such as fossil-upstream and use git-buildpackage as the work horse to play with released tarballs. That doesn't sounds like what the real fossil maintainer should be doing. Osamu
Bug#840122: Incorrect idescription in debian/copyright
Would you like to co-maintain? The packaging repo is a fossil repo (of course) see debian/README.Debian so if you do co-maintain you can either make you own and we can sync, or we can try to tickle the linux ACLs on the fossil repo database (it's on a debian server) to give you write access. I'd welcome help, since I have not really been using fossil much lately so I have not been driven to update the debian package. To get to the particular points you raise: - been meaning to package the latest version - upstream copyright must have shifted, will try to fix it. ... Ooops, I was in the middle of finishing this when I got email that you already did an upload. Excellent, thank you! Will merge your mods into the packaging repo. And naturally the above still stands. --Barak.
Bug#840122: Incorrect idescription in debian/copyright
Package: fossil
Version: 1:1.33-3+b1
Severity: normal
The upstream (Sqlite fame) is famous for his preference on BSD over GPL.
So when I saw debian/copyright file, it was not just old format but
declaring GPL. Wow, this can't be true. I checked the current source
which comes with COPYRIGHT-BSD2.txt. Basically, all files in the source
are in BSD-2, MIT, Zlib.
With careful scanning of source using my debmake command, I only see a
few FSF/GPL related files but they are all in autosetup/*.
# As a special exception to the GNU General Public License, if you
# distribute this file as part of a program that contains a
# configuration script generated by Autoconf, you may include it under
# the same distribution terms that you use for the rest of that
# program. This Exception is an additional permission under section 7
# of the GNU General Public License, version 3 ("GPLv3").
Yes, these are permissive special ones.
Did FTP master overlooked this when accepting this package? Did
upstream switched license? (I doubt both and confused ...)
At least we should update debian/copyright matching the current source.
Also, the upstream has the bash completion file but this is not installed.
The latest is Version 1.35 (2016-06-14) Why not updated for the last 1
year with 2 releases...
Well bug #693570 should be closed by now. Leaving it as resolved is
confusing.
Maybe this package needs love ..
Osamu
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (98, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fossil depends on:
ii libc6 2.23-5
ii libfuse2 2.9.7-1
ii libreadline6 6.3-8+b4
ii libsqlite3-0 3.14.2-1
ii libssl1.0.2 1.0.2h-1
ii zlib1g1:1.2.8.dfsg-2+b1
fossil recommends no packages.
Versions of packages fossil suggests:
ii gnupg 1.4.20-6
ii gnupg2 2.1.11-7
-- no debconf information
