-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/21/12 11:11, Antoine Beaupré wrote:
> On Tue, 20 Mar 2012 18:17:25 -0500, Mike Mestnik
<che...@mikemestnik.net> wrote:
>> Too much drama. Some users are familiar with Atheme's stance on
>> packaging, so you'll be asked to not package Atheme by just about
>> anybody. After so much time has passed it would be important to
>> re-affirm permission and also determine who has the right to suggest to
>> Debian that they would prefer there to not be a package and who has the
>> right to grant permission.
>>
>> It would be important for any mentor to understand the landscape. We
>> may have to disclaim that there is no support whatsoever from upstream
>> of this package or at least inform users that a "handful of Atheme
>> users" will angrily reject any requests pertaining to the Debian package.
>>
>> As far as Atheme's stance on this issue I have no idea, I can't even say
>> with any certainty who Atheme is aside from the copyright Upstream
>> Authors. Could any one of there objections prevent inclusion into Debian?
>>
>> It also should be noted that I have a mental illness, as I'm sure many
>> can relate, in working with ppl. I really only understand the actions
>> of computers and this causes humans to hate me, in my opinion
unjustifiably.
>
> I appreciate you being straightforward about this.
>
> I have communicated with upstream and I think I have cleared those
> issues. I have talked specifically with William Pitcock which gave us a
> go on IRC and they have formally changed their website to reflect that,
> as I mentionned in this bug report earlier.
Great!

6.0.10 is the latest and per upstream request the watch file will not
try and pull anything other then 6.x.
http://mikemestnik.net/debian/atheme-services/

I've went over my pkg and had only one hold back from uploading it to
mentors and that's the debian/copyright file.  I've made a lot of
changes and I believe it's in good shape but I feel it will need two
things, both are two ways of saying the same thing thankfully.  It
should need to be forward ported from the pkg-irc version
2.2.0+hg20071209-1 and that's assuming it was correct at that time.  I
have merged this tree with Lenny atheme-services_3.0.4-1.diff, so we
should be good up-to that point.

The second task is to make sure that every file in the completed source
tree is included in the copyright as the current copyright file lists
the status of each file individually.

http://mikemestnik.net/debian/atheme-services/debian/copyright

There is always something else I'll remember.  The build log spits out a
message about unnecessarily linking with libssl.  I'm sure that's true
of most of the binaries, but there must be one that makes use of it.  To
that end we need to make sure we are following current practices in
regards to libssl copyright.

* Note the pkg screams and dies if the embedded copy of libmowgli is
used.  One interesting note is that it would be possible for a user to
build a package like this with -d, if this were removed.  I'd like to
extend the pkg to support this, but in that case the correct control
file contains conflicts libmowgli.

Regardless auditing of the pkg is necessary as it's my vary first and
I've taken liberties.  It's possible it's vary far from being usable.

>
> If you are unconfortable to deal with upstream, please let me deal with
> them. I can operate humans maybe a little bit better, and I will not
> hate you for having trouble operating me. ;) I also have a good relation
> with upstream so far.
There are a number of notes for upstream.

1. The libssl, I'm supposed to ask them to remove it.  That is, for
example, it's not necessary on most of the modules that currently link
to it.

2. .hgtags in *libmowgli, they can remove these in the next tarball. 
>From what I gather these are files created by a VCS.

>
> In other words, I can mentor this package, given time.
I don't think anyone has taken a good look at the pkg yet, so you may
want to wait for it to sit on mentors for a bit so that I can say with
some certainty that it's good to go.

>
> A.
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPapw1AAoJEOPRqa2O3KuKn0sP/0a0IZXOxf+toyAKmGBBob+2
qq1h8Ih2B0rAaPkuNswwa7hjPzh5/lb+aKi/ZeVp1dG3mY4cSl2fMoRgNAl6hTSN
bjbdPoMRZfT3fGYu787TQ1L0o1hbOurEGcZChheP/IX2O+TFwdXn17VVnKrgQpP1
DOCWtfpMNtqKaGiQQPNBluQ/9AlJyNxOY1G7yemXcHC5kuBY/U6ndwz3fHLMg20k
R9IcABP8DXAQLHKhRVPloLlS00nJP8f8CR4+3EWM/BVmpQj5wqxMM/ROlH2PUrO/
0yMDzFCUady2tnZnxExwT1iDJdWGb3yI+6KkQ/TLpLiFm/AlSFH++92IoGNYH9PY
wxP/0Sn4K6VG8PYsQ80ijHrWt5JXmWoIoww+wbvELgqv7nPcfAJpRole3t2aaJob
cMH+cLfcGaLAXeVfvVTilSTK8V33ioR9M2hTFjyplhp0VugvAXnkzWFUXVZF5pae
H/M1rOhLLTJd/r02JmpMofHQS1DCwWTViGJJTVTKHRga2Uf826IBqwrAo/kh+TOF
i1VId+5FuYHCV37RFYUQW4BnRM8RXjPEPxToROztBG2puuDYHB+1s1lFjKdoSiS/
JF57sq+yy5Jk+/Juv2RLwJTOXT5Lm/iPdWgh0Fpr/mACWb8z2B3+ZxQo5NA976Po
r/mE1cVw0bsXyW7hNVCu
=GWbb
-----END PGP SIGNATURE-----




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to