Bug#744929: RFS: crashmail/1.5-1
On 04/20/2014 08:05 PM, Vincent Cheng wrote: Just curious, what sort of issues are you having with alioth? Have you tried contacting the alioth admins about it if it's something that you can't fix for yourself? I still need to investigate it further, including checking its config, then decide how to resolve it. Error is with multiple instances of crashmail pre v1.0 tags, that un-annotated tags are not allowed in this repository. RJ Clay j...@rocasa.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744929: RFS: crashmail/1.5-1
Control: tag -1 - moreinfo
On 04/20/2014 04:49 AM, Vincent Cheng wrote:
- debian/copyright: your LGPL-2.1 license block should contain the
standard LGPL header (similar to that of your GPL-2 license block just
below it in your copyright file)
Fixed.
- debian/control: Vcs-{Git,Browser} should point to where your
packaging is stored on alioth, not your upstream git repository (see
Policy 5.6.26 [1])
Specified packaging branch info in Vcs-* URLs.
- debian/rules has a redundant override_dh_installchangelogs target
Fixed.
- your debian/README.source is redundant given that you use source
format 3.0 (quilt)
As I indicated, I would prefer to keep it...
On 04/20/2014 08:05 PM, Vincent Cheng wrote:
Anyways, the d/copyright issue is the only true blocker, fix that and
I can upload this.
Thanks!
Package rebuilt and re-uploaded. URLs same as before.
Robert James Clay
j...@rocasa.us
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744929: RFS: crashmail/1.5-1
Control: tag -1 + moreinfo
On Wed, Apr 16, 2014 at 4:59 AM, RJ Clay j...@rocasa.us wrote:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package crashmail
* Package name : crashmail
Version : 1.5-1
Upstream Author : Robert James Clay jame@rocasa
* URL : http://ftnapps.sourceforge.net/crashmail.html
* License : Permissive
Section : mail
It builds those binary packages:
crashmail - JAM and *.MSG capable Fidonet tosser
crashmail-dbg - debugging symbols for crashmail
To access further information about this package, please visit the following
URL:
http://mentors.debian.net/package/crashmail
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/c/crashmail/crashmail_1.5-1.dsc
More information about Crashmail can be obtained from
http://ftnapps.sourceforge.net/crashmail.html.
Changes since the last upload:
* New upstream release.
- Multiple fixes for compile time build issues.
- Update and reconcile the overall version of Crashmail II with its
existing
tools versioning.
* Rewrite debian/copyright for machine-readable format.
* Rewrite debian/rules for use for newer versions of debhelper.
* Changes to debian/patches/:
- Use 01-ExamplePrefs.patch to set expected Debian paths in
example.prefs.
- Rewrite 02-Makefile.patch to not strip binaries.
* Changes to debian/control:
- Update the Debhelper Build-Depends version to '= 8'.
- Add stanza for debugging symbols crashmail-dbg package.
- Update Standards-Version to v3.9.5, no changes required.
- Update home page and Vcs* entries for SourceForge project.
- Remove Homepage entry in binary package stanza as it is not necessary.
* Add debian/README.source file, detailing using quilt for source
patching.
* Update the Debhelper compatibility to '8' in debian/compat.
* Add debian/crashlistout.1 for the missing man page.
* Add file debian/watch for use by uscan.
- debian/copyright: your LGPL-2.1 license block should contain the
standard LGPL header (similar to that of your GPL-2 license block just
below it in your copyright file)
- debian/control: Vcs-{Git,Browser} should point to where your
packaging is stored on alioth, not your upstream git repository (see
Policy 5.6.26 [1])
- debian/rules has a redundant override_dh_installchangelogs target
- your debian/README.source is redundant given that you use source
format 3.0 (quilt)
Regards,
Vincent
[1]
https://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-VCS-fields
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744929: RFS: crashmail/1.5-1
On 04/20/2014 04:49 AM, Vincent Cheng wrote:
- debian/copyright: your LGPL-2.1 license block should contain the
standard LGPL header (similar to that of your GPL-2 license block just
below it in your copyright file)
I'll be fixing that...
- debian/control: Vcs-{Git,Browser} should point to where your
packaging is stored on alioth, not your upstream git repository (see
Policy 5.6.26 [1])
The one now listed has both the packaging ('debian' branch) and
upstream ('master' branch), and the one at alioth is the same. However,
the one at alioth has been having problems that's been causing issues
with updates to it; I still plan to continue mirroring the repo there
but first I have to fix the issues it has.
But it's also true that the packaging branch in neither repo is not
the default branch, and that unlike github that cannot be changed; so
I'll need to update those fields in the debian/control to include the
branch info.
- debian/rules has a redundant override_dh_installchangelogs target
I don't now recall why I left that in there when I rewrote the
file; I'll fix it...
- your debian/README.source is redundant given that you use source
format 3.0 (quilt)
Perhaps; but while a DD or DM might know that, whom else would? I've
been using such a file since before I joined the Perl team [1], and
haven't really been considering it redundant since many people would not
know what that format means. But you consider not really necessary to
have it?
Robert Jame Clay
j...@rocasa.us
[1] http://pkg-perl.alioth.debian.org/howto/quilt.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744929: RFS: crashmail/1.5-1
On Sun, Apr 20, 2014 at 9:24 AM, RJ Clay j...@rocasa.us wrote:
On 04/20/2014 04:49 AM, Vincent Cheng wrote:
- debian/copyright: your LGPL-2.1 license block should contain the
standard LGPL header (similar to that of your GPL-2 license block just
below it in your copyright file)
I'll be fixing that...
- debian/control: Vcs-{Git,Browser} should point to where your
packaging is stored on alioth, not your upstream git repository (see
Policy 5.6.26 [1])
The one now listed has both the packaging ('debian' branch) and upstream
('master' branch), and the one at alioth is the same. However, the one at
alioth has been having problems that's been causing issues with updates to
it; I still plan to continue mirroring the repo there but first I have to
fix the issues it has.
Just curious, what sort of issues are you having with alioth? Have you
tried contacting the alioth admins about it if it's something that you
can't fix for yourself?
But it's also true that the packaging branch in neither repo is not the
default branch, and that unlike github that cannot be changed; so I'll need
to update those fields in the debian/control to include the branch info.
- debian/rules has a redundant override_dh_installchangelogs target
I don't now recall why I left that in there when I rewrote the file;
I'll fix it...
- your debian/README.source is redundant given that you use source
format 3.0 (quilt)
Perhaps; but while a DD or DM might know that, whom else would? I've been
using such a file since before I joined the Perl team [1], and haven't
really been considering it redundant since many people would not know what
that format means. But you consider not really necessary to have it?
It's redundant in the sense that as long as you use source format 3.0
(quilt), dpkg-source is able to handle quilt-formatted patches by
itself (so you don't need an explicit build-dep on quilt, you don't
need to call dh_quilt in d/rules, etc.), so you don't actually need to
use quilt directly. This is just me being pedantic, however; you can
keep debian/README.source if you want. :)
Anyways, the d/copyright issue is the only true blocker, fix that and
I can upload this.
Regards,
Vincent
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744929: RFS: crashmail/1.5-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package crashmail * Package name : crashmail Version : 1.5-1 Upstream Author : Robert James Clay jame@rocasa * URL : http://ftnapps.sourceforge.net/crashmail.html * License : Permissive Section : mail It builds those binary packages: crashmail - JAM and *.MSG capable Fidonet tosser crashmail-dbg - debugging symbols for crashmail To access further information about this package, please visit the following URL: http://mentors.debian.net/package/crashmail Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/crashmail/crashmail_1.5-1.dsc More information about Crashmail can be obtained from http://ftnapps.sourceforge.net/crashmail.html. Changes since the last upload: * New upstream release. - Multiple fixes for compile time build issues. - Update and reconcile the overall version of Crashmail II with its existing tools versioning. * Rewrite debian/copyright for machine-readable format. * Rewrite debian/rules for use for newer versions of debhelper. * Changes to debian/patches/: - Use 01-ExamplePrefs.patch to set expected Debian paths in example.prefs. - Rewrite 02-Makefile.patch to not strip binaries. * Changes to debian/control: - Update the Debhelper Build-Depends version to '= 8'. - Add stanza for debugging symbols crashmail-dbg package. - Update Standards-Version to v3.9.5, no changes required. - Update home page and Vcs* entries for SourceForge project. - Remove Homepage entry in binary package stanza as it is not necessary. * Add debian/README.source file, detailing using quilt for source patching. * Update the Debhelper compatibility to '8' in debian/compat. * Add debian/crashlistout.1 for the missing man page. * Add file debian/watch for use by uscan. Regards, Robert James Clay
