Re: about my e-mail of today in the morning

[Paul Tagliamonte]

On Thu, Feb 16, 2012 at 4:56 PM, Arno Töll  wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 16.02.2012 22:28, SchmiTTT wrote:
>> This is no April's joke in this February ...
>
> Yet it is off-topic here and your gibberish does not seem to make any
> sense to me.
>
> You could send out proper mail headers at least, which would allow us
> to ignore you more easily.

Yeesh, ouch!

I don't want to ride you too hard here, because I both respect and
love working with you, but this email is just crazy out of line.

I'm personally a bit perturbed with the choice of phrases you've
picked, and I really don't think there's any point in beating up
someone who's not used or familiar with our protocols

I don't think this conveys the tone we wish to set in this group, and
for that, I apologize to Val.

>
> 
>
> - --
> with kind regards,
> Arno Töll
> IRC: daemonkeeper on Freenode/OFTC
> GnuPG Key-ID: 0x9D80F36D
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQIcBAEBAgAGBQJPPXuAAAoJEMcrUe6dgPNtN4MP+wUdyD+eBFaqPUAP4bqf8EIM
> K3049OV6GKSIn3DhPce99fyX73Nd/mnX+WLBXryVp3qOvQx3wC0AQoFf4cVrGijJ
> hyWGA8gNFas9A2zLT5Jxr3PgVevIzALsrBFWrkrLzSo35+7wQzvMCLxCkukVSAzD
> zGFwPmFnywTxtpFNH/cBRWqNJeP8aHcHFLH8JIQabFs3pjo69H4whqeK/c1TvpIP
> YBqiGKZ7uKu28VNZ6qsV96kROVQaSBZwJhHKpOpefVsPNJbVe9D1XMVNYto2zocp
> o3K4xkcrt3YYKMAy/oJeJYT6A8RFSyO9UYwg67QGhCiI5ruWcpqw6y+DUPnsmG5P
> Z7izdVHOL7XgO7tFWcUyNFEX/gRO9hPVoQK3UVVo/yV6vDouVy78Dohm+1y5amVJ
> eR/o4TYEd6/XrxsnnW56Y2TKQ187pRc5C876/KtaKcj7mnaIMTqiy/piz431D29x
> UCiHO/64C8DAcJGMTCqLwKyY6zpBVObcXYnVL3VfLxTVBQcHN9QSAeG8+B2P2daL
> /F7Lv9KE3Y3OUnbUIs+GhUTAd3tT1Q1uwSBTVq7Sxcz9vLeQhBSEb5rRl3tazJpT
> Afn4ojfNoJ2hB7eDnX3Npe1yOpcQVWNHSdCf+4jUAnGMHC/xCzu/rEqzy895HhCu
> cvTq1IRpCPGkqL2RvkkV
> =hrDo
> -END PGP SIGNATURE-
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4f3d7b80.3070...@toell.net
>

Val:

Perhaps you should look at making this into an upstream project, so
motivated Debian contributors may work on getting this software into
Debian?

We don't usually accept code snippits as full packages, so perhaps if
you were to get this into a larger utils project, or even start a
collection for working with BIOSs, or something.

Best of luck!
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cao6p2qq1gk2ktn8he_tjm7tgcpqkcbz4aursmgbjz-cjvje...@mail.gmail.com

Bug#658160: RFS: libapache2-mod-socket-policy-server 0.0.7-1 [NEW] -- An Apache2 module for serving Adobe socket policies.

[Paul Tagliamonte]

I don't see a dsc on that page or in the description you've provided.

You should consider using mentors.debian.net.

Cheers,
Paul


signature.asc
Description: Digital signature

Bug#661511: tpb/0.6.4-8 ftbfs with clang

[Paul Tagliamonte]

Howdy Prach,

I took the liberty of attempting to build your package with clang
(rather then gcc) as the compiler.

The package appeard to fail in my sbuild chroot, so I double checked
(since the error was not clear it was because of clang), and found that
using clang does, in fact, cause the configure script to fail.

Here's the error:

| checking for xosd-config... /usr/bin/xosd-config
| checking for libxosd... yes
| checking for version of libxosd... < 0.7.0, failed
| *** The version of XOSD library installed is not 0.7.0 or
| *** above, make sure the correct version is installed.

And a quick tripple check:

| [tag@leliel:~/reviews/debian/tpb-0.6.4][08:22 PM]$ CC=gcc ./configure 
>/dev/null 
| [tag@leliel:~/reviews/debian/tpb-0.6.4][08:26 PM]$ echo $?
| 0
| [tag@leliel:~/reviews/debian/tpb-0.6.4][08:26 PM]$ CC=clang ./configure 
>/dev/null
| [tag@leliel:~/reviews/debian/tpb-0.6.4][08:26 PM]$ echo $?
| 1

Since clang is not a supported buildd compiler, this is not critical to
fix. Something to send upstream, though.

Thanks for helping make Debian better,
Paul


signature.asc
Description: Digital signature

Bug#661511: (another) ftbfs

[Paul Tagliamonte]

Your package also ftbfs when built twice in a row

>From my output:

| dpkg-source -b tpb-0.6.4
| dpkg-source: info: using source format `3.0 (quilt)'
| dpkg-source: info: building tpb using existing ./tpb_0.6.4.orig.tar.gz
| dpkg-source: warning: ignoring deletion of directory autom4te.cache
| dpkg-source: warning: ignoring deletion of file autom4te.cache/output.0
| dpkg-source: warning: ignoring deletion of file autom4te.cache/requests
| dpkg-source: warning: ignoring deletion of file autom4te.cache/traces.0
| dpkg-source: info: local changes detected, the modified files are:
|  tpb-0.6.4/config.h.in
|  tpb-0.6.4/configure
|  tpb-0.6.4/stamp-h.in
| dpkg-source: info: you can integrate the local changes with
dpkg-source --commit
| dpkg-source: error: aborting due to unexpected upstream changes, see
/tmp/tpb_0.6.4-8.diff.XRpvcn
| dpkg-buildpackage: error: dpkg-source -b tpb-0.6.4 gave error exit status 2

Thanks again!
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq



-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAO6P2QTSQy0a=xe__mqdnpwvdldk6bnw2igpuhfxmo+1b4m...@mail.gmail.com

Re: sponsorship-requests mails should not go to debian-mentors

[Paul Tagliamonte]

On Tue, Mar 6, 2012 at 5:47 PM, Samuel Bronson  wrote:
> It's getting to the point where I think it would be best if we do one
> of two things:
>
>  1. Split out sponsorship-requests bug mail to a new mailing list.
>
>  2. Stop sending it anywhere, and let people subscribe through the PTS
> if they care.
>
> How about you?

I hate to +1 without much content, but IMHO the "right" thing to do
would be to split off people trying to give or receive help and
automated mail regarding requests for sponsorship.

The percent of RFS mail / mail is much higher then !(spam-mail) / mail.

In the end, this needs to go to the listmasters and get a change on
the BTS side as well. Perhaps we should start that flame war again.

>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/cajyzjmd5dzthos4fysn0gsh7wzvp_2z0uftot8cakdmcg7a...@mail.gmail.com
>

-T

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAO6P2QSOzn9NEHqVg3nUBmgRsNQzKznGV=xrpmxy8qvkcmx...@mail.gmail.com

Bug#664533: RFS: fbautostart/2.7182818-1 [RFS]

[Paul Tagliamonte]

Package: sponsorship-requests
Severity: normal
thanks

Dear mentors,

I am looking for a sponsor for my package "fbautostart"

 * Package name: fbautostart
   Version : 2.7182818-1
   Upstream Author : Paul Tagliamonte 
 * URL : https://launchpad.net/fbautostart
 * License : Expat
   Section : misc

It builds those binary packages:

  fbautostart - XDG compliant autostarting app for Fluxbox

To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/fbautostart

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/f/fbautostart/fbautostart_2.7182818-1.dsc

Changes since the last upload:

  fbautostart (2.7182818-1) unstable; urgency=low

* New upstream release. Solves an issue with failing to ignore
  files that end with something other then .desktop.
* Routine update to the packaging.
  - debian/copyright updated to version 1.0 of DEP5.
  - Standards bump to 3.9.3, no changes needed.

   -- Paul Tagliamonte   Fri, 16 Mar 2012 17:00:00 -0400


Regards,
   Paul Tagliamonte


signature.asc
Description: Digital signature

Bug#660049: mosh sponsorship and name

[Paul Tagliamonte]

reopen 660049 =
reopen 631139 =
thanks

On Sun, Mar 25, 2012 at 3:39 PM, Christine Spang  wrote:
> hi David,
>
> As you may have noticed from the activity on your mosh ITP, I didn't
> check the WNPP bugs list before sponsoring another package with the name
> 'mosh', which has now clearned NEW and entered the archive.
>
> Would you be willing to rename your mosh package to, say, mosh-scheme?
> I'd be happy to then sponsor your package to the archive and be your
> sponsor for future uploads.
>
> apologies,
> Christine
>
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20120325193927.GA14223@localhost.localdomain
>

Ach, I totally closed this without paying close attention. Sorry, all.
Re-opening the RFS and ITP.

Thanks for paying attention, Christine.

-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq



-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAO6P2QRs8k8zVT_zRKDLd1VL+DaXyk_Dm=ib9a5+jucpybf...@mail.gmail.com

Bug#660049: mosh sponsorship and name

[Paul Tagliamonte]

On Tue, Mar 27, 2012 at 4:06 AM, David Banks  wrote:
> Hi Christine,
>
> On 25 March 2012 20:39, Christine Spang  wrote:
>> As you may have noticed from the activity on your mosh ITP, I didn't
>> check the WNPP bugs list before sponsoring another package with the name
>> 'mosh', which has now clearned NEW and entered the archive.
>>
>> Would you be willing to rename your mosh package to, say, mosh-scheme?
>> I'd be happy to then sponsor your package to the archive and be your
>> sponsor for future uploads.
>
> Well, mosh seems like an older program, having been begun by the R6RS
> process in 2008; but I would concede that keithw/mosh probably has a
> larger user base.  As these rename issues can get thorny and mosh is
> already in the archive in any case, I'll be willing to rename.
> Hopefully the technical barriers will not be too hard to surmount.
>
> Aside: CCing to both bugs to be safe.  However, how should the
> existing bugs be handled in this case?  Simply rename the ITP and RFS
> to 'mosh-scheme'?

Yeah, that should work just fine :)

>
> Cheers,
> --
> David Banks  
>
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/caobnz7z3njvyv2grnywr1ratlbtv5pm8zp8_ckn4si...@mail.gmail.com
>



-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq



--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cao6p2qteb_q+ysptwbb7vusbvmaovs5qqggrq75i5m-qhrg...@mail.gmail.com

Bug#661570: Is this done?

[Paul Tagliamonte]

This looks done, because the uploaded version[1] was -2, but there's
also a -3[2] in the mentors.d.n - retitile / close + refile?

-T

[1]: http://packages.qa.debian.org/c/cvc3/news/20120304T093218Z.html
[2]: http://mentors.debian.net/package/cvc3


-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq



-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cao6p2qszq6ffj3tjhs+uvjthgetgy-h7m-aseekadwsbcsm...@mail.gmail.com

Re: Documentation generated by doxygen and Debian Policy

[Paul Tagliamonte]

On Thu, Apr 19, 2012 at 3:36 AM, Boris Pek  wrote:
> Hi list,
>
> I found that in package qxmpp is used HTML documentation from upstream 
> tarball.
> This documentation was not generated by doxygen during build process. Should
> I make a bug report? If yes, which section of Debian Policy I should point to?

Well, there's nowhere in the DFSG or copyright (i'm assuming)
that says that it must be in some format X. If the original source is,
in fact, HTML, there's no problem.

The idea is that you communicate the program in a preferable format
which can be used (or in some cases, actually is) the thing you
distribute.

If the docs were generated, and they have a better source format, you
should encourage them to use that.

The relevant Debian policy is DFSG point 2[1] (Must include source code) :)

>
> Best regards,
> Boris
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/175731334821...@web6g.yandex.ru
>

HTH,
Paul

[1]: http://www.debian.org/social_contract

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAO6P2QTJUn8+occ1E=uP787PGYYXM6dyJabcCVOeGYKYoQYy=q...@mail.gmail.com

Re: Documentation generated by doxygen and Debian Policy

[Paul Tagliamonte]

On Thu, Apr 19, 2012 at 9:18 AM, Boris Pek  wrote:
>>>  I found that in package qxmpp is used HTML documentation from upstream 
>>> tarball.
>>>  This documentation was not generated by doxygen during build process. 
>>> Should
>>>  I make a bug report? If yes, which section of Debian Policy I should point 
>>> to?
>>
>> Well, there's nowhere in the DFSG or copyright (i'm assuming)
>> that says that it must be in some format X. If the original source is,
>> in fact, HTML, there's no problem.
>>
>> The idea is that you communicate the program in a preferable format
>> which can be used (or in some cases, actually is) the thing you
>> distribute.
>>
>> If the docs were generated, and they have a better source format, you
>> should encourage them to use that.
>>
>> The relevant Debian policy is DFSG point 2[1] (Must include source code) :)
>
> Thank you for a reply.
>
> Perhaps I wrote unclear. In few steps:
> 1) There is some HTML documentation [1] in upstream tarball.
> 2) This documentation was generated using Doxygen.

A, I see.

> 3) This documentation was packaged in package libqxmpp-doc as is.
> 4) I can not find in tarball the necessary sources for Doxygen and 
> instructions
>   how to generate this documentation manually.

Are these API docs? Is it just a case of a missing Doxyfile (I think
that's the name) or is there something more? Is it missing from
Upstream's source tree?

>
> The question is: should I make a bug report in this case?

It's important to protect our users' freedoms, and it'd be the clear
right thing to do to include source in the source dist in Debian, but
I'd not accuse upstream of anything.

I'd send a mail out, asking where the source is for the docs, and how
one might rebuild them.

>
> I am not subscribed to debian-devel list, so I've asked here.

This is a perfect place to ask.

>
> Best regards,
> Boris
>
> [1] http://qxmpp.googlecode.com/svn-history/tags/qxmpp-0.4.0/doc/html/

Just a quick glance shows this:

http://qxmpp.googlecode.com/svn-history/tags/qxmpp-0.4.0/doc/doc.pro

Could that be used to generate a Doxyfile and run the generation of
the docs? I've not looked at it in a super long time, so I'm not sure
how Doxygen works anymore.

>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/69811334841...@web30e.yandex.ru
>



-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/cao6p2qtfxvqwukrrey5eekzyrheq614ehqe5-8zpq9jsagu...@mail.gmail.com

Bug#672701: partial review

[Paul Tagliamonte]

INADD, but here's a very partial review,

I've only had a quick second to glance at the package, but here's a
partial set of comments:

 * Please use dpkg-statoverride rather then that rules override you've got
   in there, since you can have some problems on upgrade, etc.

 * You should also consider using DEP5 for your copyright.

I didn't have a chance to look at it in detail, but just noticed those
things.

Good luck!
  - Paul


signature.asc
Description: Digital signature

Bug#672701: partial review

[Paul Tagliamonte]

On Mon, May 14, 2012 at 10:01:52AM +0200, Andrew Shadura wrote:
> Hello,
> 
> On Sun, 13 May 2012 21:45:10 -0400
> Paul Tagliamonte  wrote:
> 
> >  * Please use dpkg-statoverride rather then that rules override
> > you've got in there, since you can have some problems on upgrade, etc.
> 
> How it that going to help? It's build-time thing, it doesn't matter, I
> guess.

It was late, you're right. Well, you're wrong, but you're right. The
*real* reason not to use this is because it's really more for end-users
and sysadmins, like dpkg-divert. It'd add a dpkg entry that the package
shouldn't be shipping, and chmod is right. My bad.

> 
> >  * You should also consider using DEP5 for your copyright.
> 
> May be or may not be needed. It's optional at this moment, so I don't
> use it widely (yet).

It's in the packaging manual, and it's been accepted. You should be
taking it more seriously. It's perhaps not a requirement, but it's a
good thing to have.

> 
> -- 
> WBR, Andrew




signature.asc
Description: Digital signature

Re: Bug#677277: lists.debian.org: new list: sponsorship-reque...@lists.debian.org

[Paul Tagliamonte]

On Tue, Jun 12, 2012 at 4:58 PM, Don Armstrong  wrote:
> On Tue, 12 Jun 2012, Arno Töll wrote:
>> upon rough consensus and after discussing with formorer [1] I'd like
>> to to request a new list dedicated to sponsorship requests. The list
>> would be used to manage sponsorship-requests bug traffic as a
>> pseudo-package owner [2].
>
> I'd personally prefer that all of the sponsorship-requests bug traffic
> still go to this list. The primary reasons are:
>
> 1) People who sponsor are already subscribed to -mentors

This drives people who sponsor off the list -- we therefore loose
people, not gain any.

> 2) Problems with RFS require mentoring and are discussed on -mentors

I'd be happy to subscribe to the new list and help there, as others
are, I'm sure.

> 3) Random sponsorship requests that don't get into the BTS go to -mentors

I'm all for keeping new bug messages going to mentors, but not every
control message.

> 4) Those who don't want to receive BTS mail can trivially filter it out

Those who want it can subscribe to a new list :)

> 4a) I don't actually know who would want to be subscribed to -mentors
>    but not to sponsorship-requests

I know of a few, and I've been tempted a few times.

>
> That said, if the consensus is that -mentors subscribers but non
> sponsorship-requests subscribers is large enough to warrant having
> everyone who wants to receive both subscribe to a new list, I'm ok
> with doing the work to change the maintainer address. [But I don't
> want to change it back after I've changed it... so please decide once
> and for all.]
>
> I'll just try this selectricity poll for now so we don't get billions
> of votes here:
>
> http://selectricity.org/quickvote/debianrfslist
>
>
> Don Armstrong
>
> --
> My spelling ability, or rather the lack thereof, is one of the wonders
> of the modern world.
>
> http://www.donarmstrong.com              http://rzlab.ucr.edu
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20120612205812.gc32...@rzlab.ucr.edu
>

-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAO6P2QRrCU579rHy0-cUZzBPþ3v_pjifihlcueac7ayds...@mail.gmail.com

Bug#677581: RFS: udj-desktop-client/0.5.0-1 [ITP] -- social music player

[Paul Tagliamonte]

On Thu, Jun 14, 2012 at 07:41:03PM -0500, Nathan Handler wrote:
> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "udj-desktop-client"
> 
>  * Package name: udj-desktop-client
>  Version : 0.5.0-1
>  Upstream Author : Kurtis L. Nusbaum 
>  * URL : https://www.udjplayer.com/
>  * License : GPL-2+
>  Section : sound
> 
> It builds those binary packages:
> 
>   udj-desktop-client - social music player
> 
> To access further information about this package, please visit the
> following URL:
> 
> http://mentors.debian.net/package/udj-desktop-client
> 
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
> http://mentors.debian.net/debian/pool/main/u/udj-desktop-client/udj-desktop-client_0.5.0-1.dsc
> 
> More information about hello can be obtained from http://www.example.com.
> 
> Changes since the last upload:
> 
> udj-desktop-client (0.5.0-1) unstable; urgency=low
> 
>   * Initial release (Closes: #677526)
> 
>  -- Nathan Handler   Thu, 14 Jun 2012 10:21:47 -0500
> 
> 
> Regards,
>  Nathan Handler
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/cacwwrb-xa751unko1rhvippydyuez+tk-mxbecehcv6pvpq...@mail.gmail.com
> 

I gave a quick review, and Nathan has addressed all my concerns quickly.
This package appears to build fine, and I see no serious issues in the
packaging.

Thanks for your work!
Paul


signature.asc
Description: Digital signature

Re: freeze policy - open requests for sponsorship

[Paul Tagliamonte]

On Tue, Jul 03, 2012 at 08:20:20AM +0200, Thibaut Paumard wrote:
> Le 03/07/12 01:41, Adam Borowski a écrit :
> > On Mon, Jul 02, 2012 at 09:06:25AM -0600, Paul Wise wrote:
> >> Perhaps use wheezy-ignore for stuff that shouldn't be in wheezy?
> > 
> > Isn't that completely contrary to that tag's usual meaning?
> > 
> > You set it for stuff that should be in wheezy despite the bug.
> > 
> > What we'd want here, is some way to convey "do not waste your time messing
> > with this bug if you care only about the next stable release".  This
> > includes unstable-only packages like gcc-snapshot.
> > 
> 
> Hi,
> 
> We could agree on a usertag then, for instance:
> 
> User: sponsorship-reque...@packages.debian.org
> Usertags: not-for-wheezy
> 
> Using sponsorship-reque...@packages.debian.org as the User, we should be
> able to rearrange the default view of
> bugs.debian.org/sponsorship-requests to have the "for-wheezy" bugs on
> top (subclassified by severity) followed by the not-for-wheezy bugs.
> 
> cf. http://wiki.debian.org/bugs.debian.org/usertags

FWIW, I was about to sit down and suggest almost the same thing. I think
this is a great idea.

This makes it even easier to get pending RFSs via local scripts, which
is always a good thing(tm).

> 
> Regards, Thibaut.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4ff28f24.8010...@free.fr
> 

We'll just have to watch out for false tags (e.g. NEW and `for-wheezy'
shoudn't be set on the same package (at least, without consent from the
release-team, which means the package is important, which means it might
likely have a sponsor, or team interested in sponsoring the package.)

+1 for usertags.

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#680141: RFS: liblastfm/0.4.0~git20090710-2 [RC]

[Paul Tagliamonte]

On Wed, Jul 04, 2012 at 02:03:57PM -0400, Asheesh Laroia wrote:
> I'm concerned by the following lintian warnings on mentors,
> which I can reproduce locally:
> 
> W: liblastfm-fingerprint0: hardening-no-fortify-functions 
> usr/lib/x86_64-linux-gnu/liblastfm_fingerprint.so.0.4.0
> W: liblastfm0: hardening-no-fortify-functions 
> usr/lib/x86_64-linux-gnu/liblastfm.so.0.4.0
> 
> Other than that, this seems reasonable so far!
> 
> 

These tests are super buggy and have been removed in the deafult profile
for lintian+1 :)

I had a similar issue, as long as you look at the build logs and ensure
the binary (and all it's .o friends) are being built with the correct
flags, it's likely OK :)

> 
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/1341424965-sup-4...@rose.makesad.us
> 

Fondly,
 Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Default RFS update behavior

[Paul Tagliamonte]

On Tue, Jul 17, 2012 at 11:44:52AM +0200, José Luis Segura Lucas wrote:
> Hi all!
> 
> I have made a few days ago a RFS. I'm wondering would will be the right
> behavior to refresh my RFS petition looking for an sponsor.
> 
> I think that the better way is to reply to the same RFS, updating the
> state of the package (if it has changed) and mentioning that I don't
> have still an sponsor. Is it ok or it would be considered as spam?

Nah, totally fine. It shows you care. I'd venture a guess that a "bump"
every week or so would be totally fine.

In fact, it shows you care :)

> 
> Thanks in advance for your replies
> 
> -- 
> José Luis Segura Lucas
> Blue Telecom
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/50053414.5010...@blue-tc.com
> 

Cheers,
   Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: freeze policy - open requests for sponsorship

[Paul Tagliamonte]

On Wed, Jul 18, 2012 at 02:31:16PM +0200, Thibaut Paumard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Le 16/07/12 11:05, Thibaut Paumard a écrit :
> > Le 03/07/12 08:20, Thibaut Paumard a écrit :
> >> Le 03/07/12 01:41, Adam Borowski a écrit : Hi,
> > 
> >> We could agree on a usertag then, for instance:
> > 
> >> User: sponsorship-reque...@packages.debian.org Usertags: 
> >> not-for-wheezy
> > 
> >> Using sponsorship-reque...@packages.debian.org as the User, we 
> >> should be able to rearrange the default view of 
> >> bugs.debian.org/sponsorship-requests to have the "for-wheezy"
> >> bugs on top (subclassified by severity) followed by the
> >> not-for-wheezy bugs.
> > 
> >> cf. http://wiki.debian.org/bugs.debian.org/usertags
> > 
> > Hi,
> > 
> > (For the record, IANADD... yet)
> > 
> > I was about to triage some bugs with these two usertags
> > (for-wheezy and not-for-wheezy), but I realized it is impossible to
> > do without the assent from the submitter. Actually, I have read the
> > first 10 RFSes or so, and if I could, I would not upload any of
> > them because they are not fit for wheezy and they don't state
> > whether they are aiming for wheezy.
> 
> Hi again,
> 
> I propose two _additional_ tags that could be set independently from
> the maintainer: fit-for-wheezy and not-fit-for wheezy. Those two would
> be used to show that the package has been reviewed and is/is not fit
> for wheezy. For instance if I review a package and it does too much
> modifications, I tag it "not-fit-for-wheezy". The maintainer has then
> two basic options:
>   - revert the useless changes, remove the "not-fit-for-wheezy" tag
> and add the "for-wheezy" tag;
>   - tag the package "not-for-wheezy" and/or set distribution to
> experimental.
> 
> Unless there are objections, I will start setting the
> (not-)fit-for-wheezy usertags tomorrow.
> 
> Reminder: this is to help our sponsors, I can't sponsor myself. If you
> don't like the idea, please say so.

This would be (to me anyway) be very useful. -- if you wouldn't mind
using "debian-mentors@lists.debian.org" as the user, that'd be awesome.

barring considered and correct objection, of course.

It'd also be nice to automatically set not-fit-for-wheezy uploads to
"wishlist" severity (or something) unless they're targeting experimental
(in which case, motivation to use that suite!)

> 
> Kind regards, Thibaut.
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.8 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQIcBAEBCAAGBQJQBqyTAAoJEJOUU0jg3ChAcrQP/A6e0HjgCeX5wKo9Jic3NBJg
> EBm/hyYA8upempwqZj3gQGsFqWPTh67SB1WpAK7kZvVDYfDvmGsTol14V7PBDnLy
> RqNMMDOU1xPj92eSf3B/nXZaQp0T8r9Jq8iZz0aObraIVgTvhjAzC5u5I+Gur8v7
> zpzHr6YVfuvcrLOfBQ1haE0R3+5gHDEPn57lVz6iijPihsth/WdC5acsVbu7ogjk
> oNPkC8B0S8/W7LLCCybW5Ffq/ApMTP//mqzbS2IClP7HGB7TF73pIkw90j33PiH/
> uQsVSDsgcMJrR4HJvSbR0zXfFTnD0a3p3H4e3vROrxIQ/B0koxtGmAGQWfHJlb+5
> 6UgPTCGuj2UhsUfKrGqqVxmGy7JXtHmIVSzw2tUZrg11BwXXWmZnXxVJUg3foukK
> 1/XmQNb1sZrxpcFT4EJl7V/f9fPxBBL2r3eayZGIh4CHy7RX1NfDst4EUnZQATdD
> Mu9q7EJFIQTuaQ2Ml3xaiM2ftOWOWRYvllQGb47VUMH83/R/Xp0WG6gxWnzNIZTa
> 2REUe2n7tS/tgJIH3tBYdKv/M7peF9T6HxOLE7bwwtkAIl1t5OMgxMvwSHxFgw1t
> qH62AJh+5g3fGgCReBM+XGVSwKojnUSCYcUYDoEtRumbCNbIX/sdSR1Y5jTRyiJn
> YrMiZ5X57azs5qaapAMG
> =x6tG
> -END PGP SIGNATURE-
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/5006ac94.6090...@users.sourceforge.net
> 

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: freeze policy - open requests for sponsorship

[Paul Tagliamonte]

On Wed, Jul 18, 2012 at 09:09:20PM +0200, Thibaut Paumard wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Le 18/07/12 15:42, Paul Tagliamonte a écrit :
> > On Wed, Jul 18, 2012 at 02:31:16PM +0200, Thibaut Paumard wrote: Le
> > 16/07/12 11:05, Thibaut Paumard a écrit :
> >>>> Le 03/07/12 08:20, Thibaut Paumard a écrit :
> >>>>> Le 03/07/12 01:41, Adam Borowski a écrit : Hi,
> >>>> 
> >>>>> We could agree on a usertag then, for instance:
> >>>> 
> >>>>> User: sponsorship-reque...@packages.debian.org Usertags: 
> >>>>> not-for-wheezy
> >>>> 
> >>>>> Using sponsorship-reque...@packages.debian.org as the User,
> >>>>> we should be able to rearrange the default view of 
> >>>>> bugs.debian.org/sponsorship-requests to have the
> >>>>> "for-wheezy" bugs on top (subclassified by severity)
> >>>>> followed by the not-for-wheezy bugs.
> 
> > 
> >>> Hi again,
> > 
> >>> I propose two _additional_ tags that could be set independently
> >>> from the maintainer: fit-for-wheezy and not-fit-for wheezy.
> >>> Those two would be used to show that the package has been
> >>> reviewed and is/is not fit for wheezy.
> > 
> > This would be (to me anyway) be very useful. -- if you wouldn't
> > mind using "debian-mentors@lists.debian.org" as the user, that'd be
> > awesome.
> > 
> > barring considered and correct objection, of course.
> 
> Hi,
> 
> I think sponsorship-reque...@packages.debian.org is better because, as
> I understand it, this would allow to show those tags by default and
> even to organize the bug list according to those tags.

For that we need to use usercategory to set that up[1], but sounds like
a good idea to me!

We should perhaps agree on which ones to use (and yes, for that, we
would need the packages.d.o address, so I think you're right)

> 
> Regards, Thibaut.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.8 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQIcBAEBCAAGBQJQBwnfAAoJEJOUU0jg3ChAS1wP/1JfpXLw8f38an2hQHXagkoR
> lR/UFkCP/yVBqBy12z2hAjkhTMrBc1JIDaYjU4UNCtO0emGSR9v4t4CEe45cqeXe
> ITLtd/x3OPZxpYWNM/DXgGXyJksvoSy2I6UtP1v1a7GglFOpyHtAruXT5WqVGzor
> yyUSYbShb2+PD07LedW2klr+hvKe9CjCd0Is4pOONJ0KzN1yRtOXYPkvh2BiZkGj
> t0pQgksoIk7xLsIXKtGWfm9SVCnb73WQEbNv2F/cutv4XaeHZuOKUbU25+RYX9vq
> mZ3ri19hpSALMUU9JxqKI9H9Y1glMJA5nDRWyML8K9FwXfQG76Z3k5jeLcZMXSE6
> L+Ch+XiE7JZlEAP/NY0+otKP51jKd64WlpOF3S0dS4vzSqeV5wLAz8YCiJMJShRv
> yQ+ON1d1s5rv7dOcB91W17dLRkbgU7iqefkWkohe4MXGDzohKJUgNHuwxeXVM52n
> Hgjzl7+OYe2IpcMzHT6VSZBgUkEWR/XUZfLvNzO/+dOsWKEG5SEJAq3F0kfXzHij
> Aj+AzovO2++ZGGfIGHc6EKcsXgGYUwenmJtnWIuM/Awu8HLHxvGyEPXTwsjIKQNn
> ebBKxS7/6sqsZ77bZ5InlXhO1OXgo96ygOXuhvXBfC730A7usmsMPXDzlSVAHeUa
> kwAoAnNPWrj5QeyuM0qh
> =7LGD
> -END PGP SIGNATURE-
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/500709e0.2070...@users.sourceforge.net
> 

Cheers,
  Paul

[1]: 
http://wiki.debian.org/bugs.debian.org/usertags#Display_usertags_on_the_web_BTS_view

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: freeze policy - open requests for sponsorship

[Paul Tagliamonte]

On Thu, Jul 19, 2012 at 07:27:01PM +, Bart Martens wrote:
> On Thu, Jul 19, 2012 at 04:57:44PM +0200, Thibaut Paumard wrote:
> > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sponsorship-requests;ordering=wheezy-bilevel
> > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sponsorship-requests;ordering=wheezy-view
> > http://wiki.debian.org/Mentors/BTS#Usertags
> > 
> > If consensus is reached (or if noone reacts negatively)
> 
> I'm happy with your efforts on this.  Please continue.

Seconded, for sure. Thanks, Thibaut!

> 
> Regards,
> 
> Bart Martens
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20120719192701.gc24...@master.debian.org
> 

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: [poke] RFS: xinetd

[Paul Tagliamonte]

On Fri, Aug 17, 2012 at 10:49:40AM +0200, Salvo Tomaselli wrote:
> Greetings

Greets!

> 
> could someone sponsor this upload to experimental? So at least i would become 
> responsible for the package and receive emails for bugs.
> 
> http://galileo.dmi.unict.it/~ltworf/xinetd/

As a xinetd (sometimes) user, I'm interested in it's fate. Thanks for
wanting to help take over a less-glamorous package, for the betterment
of Debian!

> 
> Thanks
> -- 
> Salvo Tomaselli

In your changelog, I'd add a ~exp1 or so to the version string. The
version you have now is perfect for unstable, but we're not going there
:)

Usually, in the changelog, you should mention, well, changes made --
Rater then something like:

  * Correct typo in README.Debian (Closes: 611637)
  * Defaults to rsyslog (Closes: #526923)

I'd prefer something like:

  * Changed the typo "for" -> "foo" in README.Debian (...)
  * I changed the default logger in $FILE from blerg to rsyslogd (...)

The idea is I should be able to get back to where you were before.

Usually I prefer lines not going over 80 chars in the debian/rules (see:
line 7) - you can wrap lines with a backslash (\)

The line:
 debhelper (>> 9.0.0)

should be changed to something like:

 debhelper (>= 9)

See jwilk's (small) rant on this subject[1].

In your xinetd.d/* files, you've got a mess of spaces (spaces all the
way to 80 chars) over all your curly braces

You should consider adding a watch file :)

You should also consider DEP3 headers on 07-CVE-2012-0862.patch

Lintian complaints:

  usr/sbin/xconv.pl  <-- does this need to have the .pl extention for
 legacy issues?

  etc/init.d/xinetd  <-- You should add LSB headers

  usr/share/man/man5/xinetd.conf.5.gz <-- mispelling: avaliable available

  You've also got a ton of FSSTND-dir-in-manual-page tags being emited,
  the manpage might nice to fix :)

  You've also got a possible-documentation-but-no-doc-base-registration
  -- it might be seeing the debian/xinetd.org-FAQ.html being put in.
  It'd be nice to register this with doc-base, but it's not the end of
  the world.

  (you should try running Lintian (with something like -IE --pedantic)
  on the .changes *after* a build as well ;) )

This diff is, well, massive, so it's going to take some time to look
over. Looks like some files are getting thrown around. I'll have to
review that in detail, but today, i've got a lot of work stuff.

Q'plah, (and thanks again),
  Paul

[1]: http://jwilk.net/blog/20120710-debhelper-build-dependencies

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#685582: RFS: scim-tables/0.5.9-2 [RC]

[Paul Tagliamonte]

Was going to upload this, but it's already been uploaded.

Closing.

Thanks,
 Paul

On Wed, Aug 22, 2012 at 01:51:31PM +0800, Tz-Huan Huang wrote:
> Package: sponsorship-requests
> Severity: important
> 
> Dear mentors,
> 
> I have got the approval to upload scim-tables to testing-proposed-updates
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685368).
> I didn't get any response from my sponsor for several days, so I am looking
> for a sponsor to upload the package "scim-tables" due to the urgency.
> 
>  * Package name: scim-tables
>Version : 0.5.9-2
>Upstream Author : The scim project
>  * URL : http://sourceforge.net/projects/scim/
>  * License : GPLv2
>Section : utils
> 
> It builds those binary packages:
> 
>  scim-modules-table - generic tables IM engine module for SCIM platform
>  scim-tables-additional - miscellaneous input method data tables for
> SCIM platform
>  scim-tables-ja - Japanese input method data tables for SCIM platform
>  scim-tables-ko - Korean input method data tables for SCIM platform
>  scim-tables-zh - Chinese input method data tables for SCIM platform
> 
> To access further information about this package, please visit the
> following URL:
> 
>   http://mentors.debian.net/package/scim-tables
> 
> 
> Alternatively, one can download the package with dget using this command:
> 
> dget -x 
> http://mentors.debian.net/debian/pool/main/s/scim-tables/scim-tables_0.5.9-2.dsc
> 
> More information about scim-tables can be obtained from
> http://sourceforge.net/projects/scim/
> 
> Changes since the last upload:
> 
> scim-tables (0.5.9-2) testing-proposed-updates; urgency=low
> 
>   * debian/patches/20_gtk3.dpatch: fix FTBFS (Closes: #684835).
>   * debian/rules, scim-modules-table.install:
> let scim-tables built-able with both multi-archified and
> non-multi-archified libscim-dev.
> 
>  -- Tz-Huan Huang   Tue, 21 Aug 2012 11:12:47 +0800
> 
> Regards,
> Tz-Huan Huang
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/cansek7wvb8aszhp09uelmf7dlthvcvngmcd2o5avpzubu9z...@mail.gmail.com
> 

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Handling of sponsorship requests

[Paul Tagliamonte]

On Fri, Aug 24, 2012 at 12:06:27AM +0200, Patrick Matthäi wrote:
> Hello list,

Hello!

> 
> as sponsor I realy welcome the decission and changes to handle
> sponsoring requests about our bugtracker, but there are still two
> questions/disadvantages from my side:
> 
> a) How should we handle requests, where the maintainer *may* be MIA?
> Just for an example #658114 - a realy simple question is unanswered for
> about 6 months!

IMHO, let the mentors-reaper-bot kill the package from mentors after a
few months, and then poke the bug as incomplete / moreinfo, and then
close the bug after $TIME

> IMO they should be pinged one more time, maybe they have overseen the
> response, but if I want to see a package in Debian, I would track it, so
> I also would see such "maintainers" as possible MIA candidates just
> after their first uploads. So on they may be not qualified to maintain
> packages/bugs within a distribution.

Here here!

> 
> b) Should we assume that the uploader is aware about freeze and realy
> delay typical "new upstream release" uploads to unstable? IMO I do not
> think so. The process is a bit more complicated but it is still possible
> to update testing packages without unstable upoads.

Yeah, but it's a major PITA and involves a lot more work (and sometimes,
lost history if it's updated out of sync with unstable)

> Surely it is not the cleanest way but sponsorship requests should be
> processed :)

Sure, but might as well throw them up in exp. I mean, it's easy, and fun
for the whole family :)

> 
> 
> Personaly I would not sponsor packages in the a) case, so on I think
> they should be closed and some more active and interested mentor could
> do this job.

+1.

> 
> b) is controverse when testing is freezed, but the number of requests
> will just grow and grow! Maybe also some warning to the uploader like
> "we are frozen, please only upload important bugfixes to sid if
> required, if not please use experimental"

Yeah, mentors has this warning, where else would you suggest putting it
to make sure people, well, read it? :)

> 
> -- 
> /*
> Mit freundlichem Gruß / With kind regards,
>  Patrick Matthäi
>  GNU/Linux Debian Developer
> 
>   Blog: http://www.linux-dev.org/
> E-Mail: pmatth...@debian.org
> patr...@linux-dev.org
> */
> 

-Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Interaction between m.d.n. and Ubuntu

[Paul Tagliamonte]

On Fri, Sep 07, 2012 at 10:57:09PM +0300, Boris Pek wrote:
> >>  I need to upload updated package with Ubuntu-specific patch. This
> >>  package will be uploaded into Ubuntu by avoiding Debian archive.
> >
> > Wouldn't an Ubuntu PPA be more appropriate for that use case?
> 
> Add temporary PPA for this? These files will needed during less than a day in 
> my case.

I assure you no one will mind having one hang around. PPAs are nice to
have around, even if you don't use them.

I have one that I use for stuff like this, it's not like it's a burden
on the system.

I suggest you use a PPA, that's the best way to get sponsored in Ubuntu,
IMHO.

After all, they'll get built for a few arches, on the PPA farm, whereas mentors
will just hold the source. You'd be doing your sponsor a favor!

> 
> > How does uploading Ubuntu-specific packages to Debian's MDN help with
> > getting them sponsored directly into Ubuntu?
> 
> In no way. I usually maintain packages for Debian. But now faced with 
> necessary
> to do Ubuntu-specific update. And usual way of exchanging files is not 
> working.
> Could you suggest any free hosting where I can put source package files and
> they will be available using dget?

Launchpad's PPA system will work great. Use that! :)

> 
> Regards,
> Boris
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/68931347047...@web26d.yandex.ru
> 

Cheers,
  Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


signature.asc
Description: Digital signature

Bug#688122: NMU Uploaded

[Paul Tagliamonte]

tags 688122 + pending
thanks

Uploaded to DELAYED/4, thanks!

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#688124: Uploaded to DELAYED/4

[Paul Tagliamonte]

tags 688124 + pending
tags 685959 + pending
thanks

Hello,

I've uploaded this bug to DELAYED/4, please let me know if I should cut
the upload or move it to 0-day.

Debdiff attached.

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag
diff -u kic-2.4a/debian/control kic-2.4a/debian/control
--- kic-2.4a/debian/control
+++ kic-2.4a/debian/control
@@ -1,7 +1,7 @@
 Source: kic
 Section: non-free/x11
 Priority: optional
-Maintainer: Gürkan Sengün 
+Maintainer: Gürkan Sengün 
 Build-Depends: debhelper (>= 5), autotools-dev, libxmu-dev, libxmuu-dev, 
libxext-dev, libxdmcp-dev
 Standards-Version: 3.7.2
 
diff -u kic-2.4a/debian/changelog kic-2.4a/debian/changelog
--- kic-2.4a/debian/changelog
+++ kic-2.4a/debian/changelog
@@ -1,3 +1,12 @@
+kic (2.4a-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control:
+- Maintainer email address was invalid and bounced. Update it to
+  use a valid address. (Closes: #685959)
+
+ -- Markus Koschany   Wed, 12 Sep 2012 15:43:26 +0200
+
 kic (2.4a-1) unstable; urgency=low
 
   * Initial release (Closes: #448342)


signature.asc
Description: Digital signature

Bug#688126: NMU uploaded to DELAYED/4

[Paul Tagliamonte]

tags 688126 + pending
tags 675220 + pending
thanks

Howdy,

I've uploaded this to DELAYED/4, please let me know if I should cut the
upload, or move it to 0day.

Debdiff attached.

Thanks!
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag
diff -u textedit.app-4.0+20061029/debian/control 
textedit.app-4.0+20061029/debian/control
--- textedit.app-4.0+20061029/debian/control
+++ textedit.app-4.0+20061029/debian/control
@@ -1,7 +1,7 @@
 Source: textedit.app
 Section: editors
 Priority: optional
-Maintainer: Gürkan Sengün 
+Maintainer: Gürkan Sengün 
 Build-Depends: debhelper (>= 4.0.0), libgnustep-gui-dev (>= 0.12.0), 
gnustep-make
 Standards-Version: 3.7.2
 Homepage: http://www.nongnu.org/backbone/apps.html
diff -u textedit.app-4.0+20061029/debian/changelog 
textedit.app-4.0+20061029/debian/changelog
--- textedit.app-4.0+20061029/debian/changelog
+++ textedit.app-4.0+20061029/debian/changelog
@@ -1,3 +1,12 @@
+textedit.app (4.0+20061029-3.4) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * debian/control:
+- Maintainer email address was invalid and bounced. Update it to
+  use a valid address. (Closes: #675220)
+
+ -- Markus Koschany   Wed, 12 Sep 2012 15:49:59 +0200
+
 textedit.app (4.0+20061029-3.3) unstable; urgency=low
 
   * Non-maintainer upload.


signature.asc
Description: Digital signature

Re: libticonv 1.1.3-1 at mentors

[Paul Tagliamonte]

On Thu, Sep 27, 2012 at 05:10:09AM +, Bart Martens wrote:
> Hi Albert,
>
> I looked at the package uploaded to mentors on 2012-09-27 00:31.

Albert came on IRC, and was so enthusiastic I had a look too

These are comments I've also expressed on IRC, but I'm just putting them
on the record here. They're also in addition to Bart's comments (which
are, as usual, fantastic)

I believe this should target experimental, not unstable - this is a new
upstream release with a lot of changes (can't remember of what order it
was, but either 8K or 80K lines in the debdiff)

There are also fixes that are not minimal in the upload, so I'd
encourage three points:

  - Before any sponsor uploads this, please get a statement from the
release team ACKing (in theory, at least) this change.

  - If they refuse to allow this to migrate, please retarget to
experimental. Please also take a look to see if you may port some of
the bugfixes you're introducing here back to the old code.

  - If they allow it, it'd be nice to poke this thread to let us know :)

>
> On Wed, Sep 26, 2012 at 09:49:39PM -0400, Albert Huang wrote:
> > Before that Bart Martens wrote:
> > > I read this in README :
> > >
> > >   |  (A special exception applies when linking the library into TilEm, see
> > >   |  the COPYING file for details.)
> > >
> > > But I don't find such exception in COPYING.  Actually, the file COPYING is
> > > identical to /usr/share/common-licenses/GPL-2 so there's nothing specific
> > > to "linking the library into TilEm" in COPYING.
> > >
> > Upstream confirms that this exception no longer applies, and as you've said
> > COPYING does not have said exception. I've added a patch to remove that
> > confusing clause.
>
> I read this in debian/patches/remove-tilem-copyright-exception.patch :
>
>   |  Description: remove tilem copyright exception
>   |   Removes the now invalid TilEm copyright exception from the README, 
> since the
>   |   LICENSE file makes no mention of it, and upstream confirms that this 
> exception
>   |   is no longer valid.
>   |  Author: Albert Huang 
>
> But there is no LICENSE file.  I guess you meant the COPYING file.
>
> I suggest to not patch README but to quote what upstream wrote about this in
> debian/copyright including upstream's From and Date headers.
>
> Regards,
>
> Bart Martens
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20120927051009.gb20...@master.debian.org
>

--
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: ovito at mentors

[Paul Tagliamonte]

On Tue, Oct 23, 2012 at 04:01:32PM +0300, Pekko Metsä wrote:
> On Thu, Sep 27, 2012 at 6:43 PM, Bart Martens  wrote:
> > Hi Pekko Metsä,
> >
> > I had a look at your package at mentors uploaded there on 2012-09-27 11:46.
> >
> > Why version 1.1.0-1~1 and not simply 1.1.0-1 ? Maybe I have overlooked some 
> > new
> > version numbering policy for experimental.

I prefer 1.0-1~exp1, so that I can keep uploads that are intended for
stable release sequential.

I've only seen this written as I do it (~exp1) or ~experimental1 (which
I don't like as much).

Some sponsors (such as myself) much prefer this.

>
> I'm very sorry for not noticing your email.  I have been scanning my
> gmail account daily in the hopes someone notices my ovito package.
> Today I found your message from the debian-mentors archive and
> realised that Google had marked your message as spam.  Please accept
> my apologies!  I kept thinking that all mentors are just too busy with
> the freeze..
>
> But anyways, thank you for your time and for your valuable answer!
> My plan was to use version numbers like 1.1.0-1~n and only bump the
> version to 1.1.0-1 after it is finally accepted.  But I made the
> corrections you suggested below and just uploaded the new package as
> 1.1.0-1. I'll upload the next versions as 1.1.0-n.

Of course, this is up to Bart (or whoever might sponsor this), but I do
think it's nice to append ~expN to experimental releases.

YMMV,
  Paul

>
> Best Regards,
> Pekko
>
> > I compared this package with version 0.9.5-2, and I see more changes to the
> > Debian packaging than mentioned in debian/changelog.
> >
> > If you intend to adopt this package, then please retitle bug 674283 from O 
> > to
> > ITA and set yourself as the owner.
> >
> > I see that debian/copyright needs an update, see for example
> > src/tachyon/tachyonlib/Copyright.
> >
> > Regards,
> >
> > Bart Martens
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/cag-kx9vsawz-aurffuze9xvm+ooja1j_admsxy3mzt+cizg...@mail.gmail.com
>

--
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Once more: Need help updating my DM upload permissions

[Paul Tagliamonte]

On Fri, Nov 16, 2012 at 02:09:52PM +0100, Thomas Friedrichsmeier wrote:
> Hi Bart,
>
> I've been sitting here, for an hour, pondering whether I should actually hit
> "Send". I admit I have difficulty trying to understand your reasons, and I'm
> beginning to doubt that these rest in the subject matter, itself.
>
> Perhaps you simply disagree with the concept of DM, in general. Or perhaps
> this matter simply became personal somewhere along the road. Perhaps I've used
> some unlucky wording, somewhere, or perhaps I've missed some subtle hints from
> your side. If so, please accept my apologies. Also, please excuse that bit of
> sarcasm, in the second half. I know that's crossing a line. But I really *am*
> failing to find different words.
>
> So, perhaps this mail does *not* make things better. But I happen to care
> about this, too, and so here's my reply:
>
> On Friday 16 November 2012, Bart Martens wrote:
> > On Fri, Nov 16, 2012 at 10:32:29AM +0100, Thomas Friedrichsmeier wrote:
> > > So far the only result has been a new bug report against my package, and
> > > some controversy around how to handle this
> >
> > The easy way would have been to upload a fix for bug 689982 in unstable and
> > request an unblock.  Instead you questioned and lowered the severity of the
> > bug, and uploaded a newer upstream release to unstable, so now it's more
> > difficult to get the bug fixed in wheezy.
>
> I'll fill in a few blanks, for you:
>
> - I have added a first reply to the bug report within 100 *minutes* after you
> filed it. In this initial feedback, I pointed you to a preview of my fix,
> *and* I stated explicitly, that I intended to upload a new upstream release,
> first, *and* that I did not agree with severity serious.
> - After four days without any reply, I went ahead and lowered severity to
> "normal", with a more elaborate explanation, and with you on CC.
> - After twelve more days without any reply, I went ahead, and uploaded the new
> upstream release, as announced.
>
> Up to this point, I had *no* indication, whatsoever, that you did not agree
> with my assessment.
>
> - On the same day (Octobor, 24), I contacted you in PM, asking whether you
> would be willing to help me with upload permissions, now.
> - I did receive a reply, this time. In entirety (omitting salutation,
> citation, and signature) it was "The issue has not yet been fixed in wheezy."
> - Still on the same day, I replied, pointing out that I did not agree with
> severity "serious", that I had changed severity on October, 12, and asked you
> to comment, why you insisted on RC status.
> - One week later, - without any reply - I posted to the list, again.
> - As a reaction to this, you *finally* cared to give a rough explanation of
> your point of view, in that mail on Nov, 2, you are referring to.
>
> > This would have been prevented
> > via sponsorship.  As I wrote before on 2 Nov 2012, on copyright and
> > licenses you seem to need a sponsor.
>
> Excuse me, if there is a bit of sarcasm showing in the following paragraph. I
> don't want that, but in all sincerity, I'm completely at a loss, as to how to
> reply, otherwise:
>
> Do you think that Henrique Holschuh and Steve Langasek seem to need a sponsor?
> Or did you not read the other replies on debian-policy? Or did you fail to
> acknowledge that these diverged from your point of view?
>
> Yes, the copyright file had bugs beyond this discussion. I have acknowledged
> that more than once. Yes, I can see your interpretation of policy on this
> point. No, your interpretation of policy on this point is *not* the one and
> only possible reading. And, disagreeing with your reading, I seem to find
> myself in prominent company.
>
> Look, yes, I could have just gone ahead and accepted your initial assessment.
> But I did not, precisely *because* I am trying to make informed and reasonable
> decisions in such matters. A process, which involves me forming my own
> thoughts, and putting my view to discussion, when it differs from yours. I
> feel that's not merely my "right", but it's absolutely my responsibility as a
> DM.
>
> And also, I do think that if you do hold a firm opinion on a subject, and you
> do care about it, then you should communicate that a bit sooner, and a bit
> more clearly. That, too is a question of respect and responsibility - towards
> a random DM as much as to the project.
>
> Regards
> Thomas

I can sense your frustration, and I thank you for keeping it civil, I'll
take care of helping you migrate the permissions.

Let's take it off-list and get in touch with your old sponsor (with a
timeout) and migrate the permissions.

Cheers,
  Paul

--
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Maintainer address for collab-maint team maintained packages

[Paul Tagliamonte]

On Mon, Nov 19, 2012 at 12:51 PM, Marc Haber  wrote:

> On Mon, Nov 19, 2012 at 05:34:58PM +, Bart Martens wrote:
> > On Mon, Nov 19, 2012 at 03:28:55PM +0100, Marc Haber wrote:
> > > I am participating in a team-maintained package which is hosted on
> > > collab-maint.
> >
> > Which package ?
>
> If that has anything to do with it, it's libopendbx, which has not yet
> been pushed to collab-maint.
>
> > > We would like to have the Maintainer: address of that
> > > package to forward to all members of the team,
> >
> > Why would you want to do that ? I mean, is the package you work on
> related to
> > all other maintainers maintaining other packages in collab-maint ?
>
> Misunderstanding, either accidental or deliberate. I want the
> Maintainer address to forward to all people listed in Uploaders: of
> the respective package, not to all 519 members of the collab-maint
> Alioth project. I am not out of my mind.
>
> > http://wiki.debian.org/Teams/CollabMaint
> > "not connected to any other teams"
>
> I believe that I am working well within the definition of
> collab-maint, thanks for trying to ask in a very subtle way.
>
> > Would modifying lintian be a solution for your problem ?
>
> Probably not, since the people behind lintian usually have sound
> reasons for putting in errors and warnings, especially such with
> Certainty: certain.
>

Yeah, I think I might have had something to do with this at some point. I
remember wondering if it would lead to a MUA loop (since it would send to
it's self)


>
> > > There do not seem to be public mailing lists on the collab-maint
> > > Alioth project.
> >
> > Does this one not work ?
> > http://lists.alioth.debian.org/mailman/listinfo/collab-maint-devel
> > "To post a message to all the list members, send email to
> > collab-maint-de...@lists.alioth.debian.org."
>
> https://alioth.debian.org/projects/collab-maint/
> "Mailing Lists (0 public mailing lists)"
>
> > > Do we really need to create a dedicated Alioth project just to get a
> > > mailing list which can be used as Maintainer? Or am I missing a
> > > policy-compliant possibility to do this with available resources?
> >
> > I agree that creating an Alioth project just for the mailing list feels
> > somewhat uncomfortable.
>
> Indeed.
>
> Greetings
> Marc, now tryin to bring blood pressure down again
>
> --
>
> -
> Marc Haber | "I don't trust Computers. They | Mailadresse im Header
> Mannheim, Germany  |  lose things."Winona Ryder | Fon: *49 621 31958061
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive:
> http://lists.debian.org/20121119175108.gk28...@torres.zugschlus.de
>
>


-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq

Re: Maintainer address for collab-maint team maintained packages

[Paul Tagliamonte]

On Tue, Nov 20, 2012 at 08:04:04AM +0900, Charles Plessy wrote:
> Le Mon, Nov 19, 2012 at 06:54:26PM +0100, Arno Töll a écrit :
> > 
> > On 11/19/2012 03:28 PM, Marc Haber wrote:
> > > @packages.debian.org seems to add that header automatically
> > > before forwarding to the PTS, but using that address as Maintainer: is
> > > a lintian _error_ (not even a warning) ("Severity: serious, Certainty:
> > > certain").
> > 
> > Thing is, you can't use the QA forwarder because it relies on your
> > source control field to learn about actual forwardings. If you would add
> > right that address, the result would be an infinite loop because you
> > would essentially forward mail to @packages.debian.org to
> > @packages.debian.org. I hope it is clear why this won't work.
> 
> Hi all,
> 
> I think that the best way forward would be to fix the PTS and remove the
> infinite loop.  This would be tremendously useful for many packages that are
> collectively maintained.

This seems pretty silly - the Maintainer: field should be useful, not a
hack just to get email (more preceisely, it says: The maintainer of this
package is the maintainer of this package)

I'd much rather see something like what Arno is talking about, at least
that's a *bit* more descriptive and less tautological

> 
> I have no time to do it myself, but see the following wiki page to contribute.
> 
>   http://wiki.debian.org/qa.debian.org/pts
> 
> Have a nice day,
> 
> -- 
> Charles Plessy
> Tsurumi, Kanagawa, Japan
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20121119230404.gb10...@falafel.plessy.net
> 

Cheery-bye,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#694431: RFS: couchdb/1.2.0-2.1 [NMU] [RC]

[Paul Tagliamonte]

I'm on the way into work, but I'm interested. Someone else feel free to
sponsor, but ill hit this tonight ig no one does
On Nov 26, 2012 7:45 AM, "Dominik George"  wrote:

> Package: sponsorship-requests
> Severity: important
>
> Dear mentors,
>
> I am looking for a sponsor for my package "couchdb". The upload would fix
> RC bug #692295.
>
> * Package name: couchdb
>   Version : 1.2.0-2.1
> * URL : http://couchdb.apache.org/
> * License : Apache-2.0
>   Section : misc
>
>   It builds those binary packages:
>
> couchdb- RESTful document oriented database
>
> To access further information about this package, please visit the
> following URL:
>
>   http://mentors.debian.net/package/couchdb
>
>
>  Alternatively, one can download the package with dget using this
> command:
>
> dget -x
> http://mentors.debian.net/debian/pool/main/c/couchdb/couchdb_1.2.0-2.1.dsc
>
> Changes since the last upload:
>
> couchdb (1.2.0-2.1) unstable; urgency=low
>
>   * Non-maintainer upload.
>   * Use SIGTERM instead of SIGHUP for graceful shutdown
> (Closes: #692295) [varacanero]
>
>  -- Dominik George   Mon, 26 Nov 2012 12:54:05 +0100
>
> The debdiff is attached.
>
> Regards,
>   Dominik George
>

Bug#694431: RFS: couchdb/1.2.0-2.1 [NMU] [RC]

[Paul Tagliamonte]

On Mon, Nov 26, 2012 at 4:50 PM, Nobuhiro Iwamatsu wrote:

> Hi,
>
> version 1.2.0-3 of couchdb already uploaded.
>

(Literally just now)



> In this version, the problem of SIGHUP is corrected.
>

Righto.

If you feel this sponsorship request is no longer needed, please feel free
to close the bug.

Thanks for your hard work, Dominik!

Paul


>
> Best regards,
>   Nobuhiro
>
> On Mon, Nov 26, 2012 at 9:54 PM, Paul Tagliamonte 
> wrote:
> > I'm on the way into work, but I'm interested. Someone else feel free to
> > sponsor, but ill hit this tonight ig no one does
> >
> > On Nov 26, 2012 7:45 AM, "Dominik George"  wrote:
> >>
> >> Package: sponsorship-requests
> >> Severity: important
> >>
> >> Dear mentors,
> >>
> >> I am looking for a sponsor for my package "couchdb". The upload would
> fix
> >> RC bug #692295.
> >>
> >> * Package name: couchdb
> >>   Version : 1.2.0-2.1
> >> * URL : http://couchdb.apache.org/
> >> * License : Apache-2.0
> >>   Section : misc
> >>
> >>   It builds those binary packages:
> >>
> >> couchdb- RESTful document oriented database
> >>
> >> To access further information about this package, please visit the
> >> following URL:
> >>
> >>   http://mentors.debian.net/package/couchdb
> >>
> >>
> >>  Alternatively, one can download the package with dget using this
> >> command:
> >>
> >> dget -x
> >>
> http://mentors.debian.net/debian/pool/main/c/couchdb/couchdb_1.2.0-2.1.dsc
> >>
> >> Changes since the last upload:
> >>
> >> couchdb (1.2.0-2.1) unstable; urgency=low
> >>
> >>   * Non-maintainer upload.
> >>   * Use SIGTERM instead of SIGHUP for graceful shutdown
> >> (Closes: #692295) [varacanero]
> >>
> >>  -- Dominik George   Mon, 26 Nov 2012 12:54:05 +0100
> >>
> >> The debdiff is attached.
> >>
> >> Regards,
> >>   Dominik George
>
>
>
> --
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6
>



-- 
:wq

Re: DM upload permission help

[Paul Tagliamonte]

If you get your old sponsor to ACK it with a signed mail to me, I'd be
happy to set them for them, or help them to set the permissions on their
own.

Cheers,
  Paul

On Fri, Dec 7, 2012 at 4:54 PM, Tomasz Muras  wrote:

> Dear Mentors,
>
> I am a Debian Maintainer of a moodle package and another small one -
> gnome-screensaver-flags. I have problems getting in touch with the Debian
> Developer that I've originally worked with, when becoming a DM, could
> someone else update my DM flag as per new procedure?
>
> Some of the links related to my work:
> http://qa.debian.org/**developer.php?login=nexor1984@**gmail.com
> http://packages.qa.debian.org/**m/moodle.html
> http://wiki.debian.org/Moodle
>
> cheers,
> Tomasz Muras
>
>
> --
> To UNSUBSCRIBE, email to 
> debian-mentors-REQUEST@lists.**debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/**50c2659d.5090...@gmail.com
>
>


-- 
:wq

Re: Bug#651606: RFP: gitlab -- git project/repository hosting management app

[Paul Tagliamonte]

On Wed, Dec 19, 2012 at 02:44:00PM +0100, Raphael Hertzog wrote:
> [ CCing debian-mentors in the hope to find someone who is willing to
> package this software ]
>
> On Sat, 10 Dec 2011, Bernd Zeimetz wrote:
> > Package: wnpp
> > Severity: wishlist
> >
> > * Package name: gitlab
> >   Version : 1.2.0 (+git...)
> >   Upstream Author : Dmitriy Zaporozhets
> > * URL : http://gitlabhq.com
> > * License : MIT
> >   Programming Lang: Ruby
> >   Description : git project/repository hosting management app
> >
> > Ruby on Rails based application to manage your own git
> > project/repository hosting, using gitosis or gitolite to manage ssh
> > access.
>
> FWIW, there are some unofficial Debian package at
> https://github.com/gitlabhq/gitlab-public-wiki/wiki/GitLab-Debian-packages-%28unofficial%29
> but they are far from perfect since many gems are
> packaged in a giant gitlab-bundle.
>
> Cheers,
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Get the Debian Administrator's Handbook:
> → http://debian-handbook.info/get/
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/20121219134400.ga26...@x230-buxy.home.ouaza.com
>

I'd also love to add my +1 to this RFP. It's sorely needed software, and
I'd be happy to help a future maintainer get this going.

--
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Bug#651606: RFP: gitlab -- git project/repository hosting management app

[Paul Tagliamonte]

On Wed, Dec 19, 2012 at 04:09:00PM +0100, Raphael Hertzog wrote:
> On Wed, 19 Dec 2012, Daniel Martí wrote:
> > Is there any packaging team I should contact? Should I start using
> > collab-maint on anonscm.debian.org for its packaging right away?
>
> The packaging work will surely require you to create a bunch of ruby gems
> so you might want to joint the ruby extras team.
>
> http://wiki.debian.org/Teams/Ruby
>
> But for gitlab itself, collab-maint is certainly OK.
>
> > On a side note, I'm neither a DD nor a DM yet - a sponsor would be needed.
>
> I think Paul just volunteered to sponsor ;-)

Aye! While I'm not up on Ruby policy, I'd be more then happy to brush up
and sponsor it on an ongoing basis.

>
> Cheers,
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Get the Debian Administrator's Handbook:
> → http://debian-handbook.info/get/

Cheers,
  Paul

--
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#696600: Sponsoring sun - schedule tasks at sunrise/set

[Paul Tagliamonte]

On Tue, Dec 25, 2012 at 05:27:28PM +0100, gregor herrmann wrote:
> On Tue, 25 Dec 2012 16:02:58 +0100, Steffen Vogel wrote:
> 
> > Here are my proposals:
> > 
> > sun - fits calculations related to the planet sun
> > 
> > suncal - seems only to be correct for time/date related calculus.
> > Determination of the sun position in coordinates is not covered.
> 
> Depends on if you expand "cal" to "calendar" or "calculation(s)" :)
> (Maybe suncalc would be clearer for the latter.)

A agree, suncal isn't bad, but what's neat about sun is how the command
invocation flows:

$ sun rise $FOO
$ sun set $FOO

So, my money is on "atsun" just do to:

$ atsun rise $FOO
$ atsun set $FOO

Or, see if you can barter with the FTP folks to keep `sun'

>  
> Cheers,
> gregor
>  
> -- 
>  .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
>  : :' : Debian GNU/Linux user, admin, and developer  -  http://www.debian.org/
>  `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
>`-   NP: Pink Floyd: Comfortably Numb


-T


signature.asc
Description: Digital signature

Bug#674109: RFS: turses/0.2.10-1 [ITP] -- Twitter client for the console (third try)

[Paul Tagliamonte]

owner 674109 !
thanks


signature.asc
Description: Digital signature

Bug#694778: A little test message to see whether our filters work now

[Paul Tagliamonte]

On Tue, Jan 15, 2013 at 9:58 AM, Arno Töll  wrote:
> Sorry for the hijack of your RFS, I'm testing our new mail filter.
> Please ignore me :)

(don't tell me what to do)

>
> --
> with kind regards,
> Arno Töll
> IRC: daemonkeeper on Freenode/OFTC
> GnuPG Key-ID: 0x9D80F36D
>



-- 
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAO6P2QS3W0=+WGkDpn35m1jV_T-V=KB9fZoV=duyxbg11m+...@mail.gmail.com

Bug#694778: A little test message to see whether our filters work now

[Paul Tagliamonte]

I should also note a review for this package was sent off-report :)

Cheers,
  T

On Tue, Jan 15, 2013 at 10:01 AM, Paul Tagliamonte  wrote:
> On Tue, Jan 15, 2013 at 9:58 AM, Arno Töll  wrote:
>> Sorry for the hijack of your RFS, I'm testing our new mail filter.
>> Please ignore me :)
>
> (don't tell me what to do)
>
>>
>> --
>> with kind regards,
>> Arno Töll
>> IRC: daemonkeeper on Freenode/OFTC
>> GnuPG Key-ID: 0x9D80F36D
>>
>
>
>
> --
> :wq



-- 
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAO6P2QRN0mJYZhk9EGuO-6z2SSs7v6yFGx6VM-2XRv_pD4Lx=q...@mail.gmail.com

Bug#699474: RFS: b43-fwcutter/1:017-1 [ITA]

[Paul Tagliamonte]

On Thu, Jan 31, 2013 at 06:56:03PM -0400, David Prévot wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Hi,
> 
> Le 31/01/2013 17:25, John Paul Adrian Glaubitz a écrit :
> > 
> > And there is also no need for experimental.
> 
> Yes there is. Better safe than sorry.
> 
> > The package doesn't have any
> > RC bugs in testing,
> 
> yet…
> 
> > so we don't need to resort to experimental due to
> > the freeze.
> 
> That sound like a misguided advice.
> 
> Please, do not upload to unstable packages not aimed for Wheezy during
> the freeze* (IOW, thanks to the sponsoree for proposing this upload to
> experimental).

If it's worth anything, I do agree as well.

A few nice things about not breaking unstable:

  - Important bugfixes can be folded in with an RC bugfix upload (sweet)
  - Your package updates will get testing through unstable users, rather
then no testing via TPU (and perhaps resulting in another upload to
TPU)
  - Being able to sleep at night knowing the release team isn't plotting
to frame you for something nasty

> 
> Regards
> 
> David
> 
> P.-S.: *except if they are not already present in Wheezy, or maybe if
> the version in Sid is already messed up, which is not the case here.
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.12 (GNU/Linux)
> 
> iQIcBAEBCAAGBQJRCvaDAAoJELgqIXr9/gnykfcP/RdyIr74/+CFgal8kwUml/Ux
> VCZVvfk8wde99M4+QbnSGfx/KrFAyogg6VQEf6AG2L+fbsJu9zO6KCYlgrDJCAIj
> L/5MxkOA/9mf+2kK2OCIGDYwFhv8pNAQdoEsLI3H0xuJFxcvXotUf5POm2mByUKN
> 6cTY3Fs2iV7pByySNxXtRgRFGFQzAQQflJoeEjJN2drHzd3rjH7IM7smzdNOWfTF
> YrBAS8ykYJ5GhjiLf+h6UIH5QS6+U1qoWVfX3uKUVY8pv7qz1t+t94lmPUKRNnAQ
> wB/73DDceoA8bV3njhIofb3j47AOA88j05vLbkLIvbVVQiZP+Zp2KT+sT/G8QI8E
> rDB2ngWgNaDnGmeITs48KNt4WUPCy1inYgzqHBm7o333ZTp6+QYPka/yXc+DqSX8
> kTV/gn5M3NmrwFsc7/hFAcLfcoTHGR+/ke9qWL4DtnfJaR9/sQqvFX+wf3Z+hEQc
> n2wSPvGZG7THxAo9QXP8UdWDdJKazsRrqH5RzdsMD6LyBtHzPtlbxflr4iH0UnVq
> Kkcu5fL6pYfnP6TCjZENU3fDUY3cG43KR1N6bVsQwRQ4Q1TMcCWKSD8FS9nhsTNh
> QurI3Lxd+2brMqttku/bzh1DagvoH9kCMPseivudXXdAucw67bt/hy3kenQOmJhE
> j7vKUeAVf4IPdGzES0rU
> =jdlE
> -END PGP SIGNATURE-
> 
> 
> -- 
> To UNSUBSCRIBE, email to package-sponsorship-requests-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/510af683.3020...@tilapin.org
> 

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Why is it so hard to get sponsors.....?

[Paul Tagliamonte]

On Tue, Feb 26, 2013 at 03:09:04PM +0100, Willem van den Akker wrote:
> Hi,
> 
> I have 2 packages for which I request sponsoring.
> http://mentors.debian.net/package/jabberd2  Bug #698547
> http://mentors.debian.net/package/jabber-muc Bug #698548
> 
> But until now nobody seemed to be interested in sponsoring them.
> I got messages  not familiar with these packages or something like that.
> 
> In the past I had some other packages and also had problems to get a sponsor.

Yeah, me too. Even as a sponsored uploader & a DM.

> 
> Why is it so hard to get a sponsor?

While this isn't true of the general case, which I think there's valid
concern about, it is currently during freeze, most DDs are working on RC
bugs :)

Some sponsorship does still go on -- perhaps you could ask some of the
DDs who maintain jabber servers -- the ejabberd folks or so, or the xmpp
team.

Also, the jabberd2 package in the PTS[1] has Debian XMPP team on
maintainer. Are there no DDs willing to sponsor a routine upload there?

> 
> Greetings,
> Willem
> 
> 

Cheers,
  Paul


[1]: http://packages.qa.debian.org/j/jabberd2.html

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#701016: closing 701016

[Paul Tagliamonte]

close 701016 
thanks


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1369083201-3715-bts-paul...@debian.org

Re: svn revs as version number

[Paul Tagliamonte]

On Mon, Jun 03, 2013 at 08:07:32PM +0200, Felix Natter wrote:
> hi,
> 
> finally we've talked the JMapViewer maintainers into making proper
> release archives, and they did, but unfortunately, they used svn
> revision numbers instead of adequate versions:
> 
> http://svn.openstreetmap.org/applications/viewer/jmapviewer/releases/29618/JMapViewer-29618-Source.zip
> 
> => The question is: Can we use "29618" (or "svn29618" or "r29618") as
> the debian version number (consistent with upstream) or do we have to
> use "0.0+svn29618"?

As hilarious as it is, that's fine. 29618-1 sounds OK. It's a bit
insane, but it's OK.

If they move to low numbers (1.0), you can bump the epoch (1:1.0-1) to
match, since that's what they did in reality.

> 
> A pointer to debian policy is appreciated. I couldn't find anything
> here:
>   http://www.debian.org/doc/debian-policy/

Section 5.6.12 covers the epoch :)

> 
> Thanks and Best Regards,
> -- 
> Felix Natter

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#714734: RFS: marisa/0.2.4-1 [ITP] - Tools and libs for a static and space-efficient trie data structure

[Paul Tagliamonte]

On Thu, Aug 01, 2013 at 06:43:19PM +0200, Jakub Wilk wrote:
> I'm a bit late, as the package is already in NEW, but anyway here's

I've REJECTED this package from new based on the perl package name,
primarally.

Thanks, jwilk.

> my quick review:
> 
> * Mitsuya Shibata , 2013-07-02, 19:11:
> >http://mentors.debian.net/debian/pool/main/m/marisa/marisa_0.2.4-1.dsc
> 
> Why is your .orig.tar different than the one downloaded by uscan?
> 
> Package synopses are not sentences, therefore they shouldn't end with full
> stops.
> 
> The Perl package name is wrong; as per Perl Policy §4.2 it should be
> libmarisa-perl.
> 
> /lib/perl5/i486-linux-gnu-thread-multi-64int/ is certainly not the
> correct directory to install Perl modules into...
> 
> According to both Lintian and blhc, at least some parts of the
> packages are not built with hardening.
> 
> lintian4python emits:
> i: marisa source: python-provides-considered-harmful python-marisa
> i: marisa source: python-provides-considered-harmful python3-marisa
> w: python-marisa: egg-info-version-mismatch 0.0.0 0.2.4
> e: python-marisa: python-module-in-multi-arch-foreign-package
> w: python3-marisa: egg-info-version-mismatch 0.0.0 0.2.4
> e: python3-marisa: python-module-in-multi-arch-foreign-package
> 
> -- 
> Jakub Wilk
> 
> 
> --
> To UNSUBSCRIBE, email to package-sponsorship-requests-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20130801164319.ga3...@jwilk.net
> 

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: DFSG and assembler code

[Paul Tagliamonte]

On Tue, Aug 20, 2013 at 12:30:32AM +0200, Adam Borowski wrote:
> On Mon, Aug 19, 2013 at 11:55:12PM +0200, Andreas B. Mundt wrote:
> > It contains so-called ROM-dumpers in assembler code which have been
> > removed for DFSG reasons on the older versions of this package, and I
> > followed that example and removed them from the version in sid as
> > well.
> > 
> > However, as dumping the ROM of the calculator is an important feature,
> > I had a closer look at the files removed and I found that they are all
> > GPLv2+ (the upstream changelog mentions some rewrite and also some
> > licence changes).  However, they are still assembler.
> 
> Assembler is just as valid a programming language as any other (or more,
> compared to, say, Malbolge).  And here you have comments, #ifdefs and so
> on, so it's not the result of disassembly.

I agree with this

> 
> Ie, fully kosher DFSG code.
> 
> > Is it necessary to remove the files for DFSG reasons?
> 
> No, why?  They come with source which is clearly the preferred form for
> modification.  If assembler was forbidden, we'd have to kick out such
> unimportant packages as linux, etc.

If there is code that was the result of disassembly in-line (e.g. take
the code, make sense of it, change some names), there's a good chance
that code is still under the license of the app from which it was
taken.

if that is the case, this code would be non-free.

From a quick glance, it doesn't appear this is an issue.Have you asked
the old maintainer why?

-T

> 
> -- 
> ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20130819223032.ga11...@angband.pl
> 

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#718323: another hyperrogue suggestion from debian reviewers

[Paul Tagliamonte]

On Sun, Sep 15, 2013 at 07:16:27PM +0200, Zeno Rogue wrote:
>Neon Corridor has agreed to compose music for HyperRogue, under the
>Creative Commons BY-NC-ND 3.0 licence. Is this OK for Debian?

Howdy there.

CC-BY-NC-ND 3.0

CC-BY (OK so far)

NC (noncomerical):

DFSG point 6:

  No Discrimination Against Fields of Endeavor
  
  The license must not restrict anyone from making use of the program in a
  specific field of endeavor. For example, it may not restrict the program
  from being used in a business, or from being used for genetic research.


ND (no-dirivs):

DFSG point 3:

   Derived Works

   The license must allow modifications and derived works, and must
   allow them to be distributed under the same terms as the license of
   the original software.


CC-BY-NC-ND 3.0 is not suited for Debian for those reasons.

the 3.0 part is nice, though.

Perhaps consider CC-BY-SA 3.0

Cheers,
  Paul


-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#706904: Chinese Checkers RFS review

[Paul Tagliamonte]

On Fri, Sep 20, 2013 at 08:00:23AM -0400, Dave Steele wrote:
> Do you have a source for that?  I was told otherwise before.

This is what defines a Debian native package.

Here's why it's stupid for non-native packages:

 Upstream: 1.0
 Debian package number: 1.0


Now, when yo update it, you'll have to do something like 1.0+1 for each
upload after. Which sucks. This also means everything will think this
string is the *UPSTREAM* version number, which is really a disaster.

In addition, we use pristine (and hash-identical) tarballs with upstream
releases. You can't do this with 3.0 (native), without being upstream.


I'm all for allowing native packages, but newbies shouldn't be using
them to package software with an upstream.

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: An Analysis of the RFS Process

[Paul Tagliamonte]

On Fri, Sep 20, 2013 at 10:32:17AM +0200, Kevin Bortis wrote:

[snip]

> BTW: There is an upcomming Debian project which could help
> implementing a new parallel, non-official, community driven build
> infrastructure called debile (formerly know as debuild.me).
> https://alioth.debian.org/projects/pkg-debile/ It is planed that
> debile could potentially implement something like PPA's.

(one of the buffoons, here)

This is true!

a PPA type system would be implementable in the debile 1.0 package set,
but this code really isn't ready for this yet.

I'm planning on running a *very* light PPA-alike (mostly for myself, but
I'd be open to friends and collaborators adding builders to the cluster)
at somewhere like deb.io

Nothing hard yet, feel free to hang out in #debile on oftc if anyone
wants to learn more.

> 
>   Kevin

Cheers,
  Paul


signature.asc
Description: Digital signature

Bug#706904: Chinese Checkers RFS review

[Paul Tagliamonte]

On Fri, Sep 20, 2013 at 10:18:18AM -0400, Dave Steele wrote:
> I'm not sure we are clear with terms here. The newbie is the upstream,
> and he has chosen to include the debian directory in his main
> repository. Should he choose to rev the packaging, upstream is
> coordinated, by definition.

As such, a trivial debian package change would trigger a new upstream
release. If this is the intent, that's fineish in my view, but remember,
this screws up and chance of cross-distro work (since a change to RPM
local stuff, as example, would trigger a new upstream, and a no change
rebuild in Debian to match)

I really discourage this usage a lot. Native packages must be for
packages local to Debian only.

> I'm good with the idea that using 'native' with non-native packages is
> 'stupid'. My question was about resolving the definition of 'native'.
> Shouldn't it simply mean that upstream is the Debian maintainer, and
> that the packaging is included? That is the guidance I was given
> regarding one of my packages.
> 
> -- 
> "Le mieux est l'ennemi du bien" - Voltaire

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#706904: Chinese Checkers RFS review

[Paul Tagliamonte]

On Fri, Sep 20, 2013 at 11:06:57AM -0400, Dave Steele wrote:
> In any case, it sounds like the guidance on this ticket is that either
> solution is fineish.

Uh. The guidance is only use a Debian native package iff the software is
*ONLY* for Debian alone.


Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#728716: RFS: xchroot/2.3.2-9 [ITP] -- Hi Debian!

[Paul Tagliamonte]

Control: tag -1 moreinfo

On Mon, Nov 04, 2013 at 05:31:40PM +0100, Elmar Stellnberger wrote:
>  The xchroot S-FSL v1.3.1 license would need some legal review. It was 
> especially designed for
>  distributions available free of charge like Debian. The license has been 
> revised thouroughly
>  and should not pose any restrictions concerning re-distribution by 
> Debian or any other free
>  distro. The author plans to publish more software under this or a 
> reworked version of the
>  S-FSL license.

This license will be considered non-free in Debian. Please re-upload
targeting non-free or change the license terms.

 o It forces distribution of changes to third parties.
 o One may not change for the software (or use it in a commercial product),
   or be used *from* non-free software as a plugin (etc). The phrasing
   in here is odd.

I strongly encourage you to not write your own license terms. Please
consider using a well-known and understood license.

Cheers,
  Paul


signature.asc
Description: Digital signature

Bug#728716: RFS: xchroot/2.3.2-9 [ITP] -- Hi Debian!

[Paul Tagliamonte]

On Mon, Nov 04, 2013 at 06:22:15PM +0100, Elmar Stellnberger wrote:
> Is it really a problem? If yes then I can add an exception for
> distributors like Debian.

Perhaps you're interesting in reading our guidelines:

  http://www.debian.org/social_contract#guidelines

point 8 is "License Must Not Be Specific to Debian".

> However what I want is being noticed somehow about changed versions
> of my programmes.

That's OK. It just means you need to upload to non-free.

> This is to collect new use cases and get updates quickly
> incorporated (Early versions of
> my program were heavily rewritten and patched as googeling has
> shown; though that time
> not even granted explicitly.). Being notified by third party users
> about their concerns and
> changes would yield major contribution to the future development.
> (There are no copyright
> issues though since the actual code added by me so far has been
> completely different from
> the diversions found out there; though it has been very useful in
> extracting new use cases.).

> >  o One may not change for the software (or use it in a commercial product),
> >or be used *from* non-free software as a plugin (etc). The phrasing
> >in here is odd.

> Well this is already the standard for the GPL-license: GPL programs
> as far as being
> compiled can not be incorporated into commercial software; you have
> to use L-GPL.
> Why not establish a similar standard for protecting intellectual
> property also for
> programs written in a script language? (i.e. this is the reason why
> I called it S-FSL).

That's not true; commercial software *can be paid software*. So long as
the software is compatable (and the work on the whole is distributed as
GPL), this isn't a problem.

Please, if you don't know how the GPL works, I have to strongly insist
on you not writing your own license.

> If the phrasing is odd we will have to rework it; it is my intention
> to have a license
> clear to everyone; not only to lawyers.
> >
> >I strongly encourage you to not write your own license terms. Please
> >consider using a well-known and understood license.
>
> Well to me it is an issue under which license to publish. I do not
> want to burden
> my distributor unncessarily but actually want to retain as much
> rights as possible
> because writing, maintaining the software and supporting also casual
> users is a
> major effort.

It's a lot more effort for the distributors to review this license and
attempt to figure out how it applies in different jursidictions, with
other licenses and how to properly comply.

> >
> >Cheers,
> >   Paul
> 
> Many Thanks for your Commitment,
> Elmar

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#728716: RFS: xchroot/2.3.2-9 [ITP] -- Hi Debian!

[Paul Tagliamonte]

On Mon, Nov 4, 2013 at 12:42 PM, Paul Tagliamonte wrote:

> On Mon, Nov 04, 2013 at 06:22:15PM +0100, Elmar Stellnberger wrote:
> > Is it really a problem? If yes then I can add an exception for
> > distributors like Debian.
>
> Perhaps you're interesting in reading our guidelines:
>
>   http://www.debian.org/social_contract#guidelines
>
> point 8 is "License Must Not Be Specific to Debian".
>
> > However what I want is being noticed somehow about changed versions
> > of my programmes.
>
> That's OK. It just means you need to upload to non-free.
>
> > This is to collect new use cases and get updates quickly
> > incorporated (Early versions of
> > my program were heavily rewritten and patched as googeling has
> > shown; though that time
> > not even granted explicitly.). Being notified by third party users
> > about their concerns and
> > changes would yield major contribution to the future development.
> > (There are no copyright
> > issues though since the actual code added by me so far has been
> > completely different from
> > the diversions found out there; though it has been very useful in
> > extracting new use cases.).
>
> > >  o One may not change for the software (or use it in a commercial
> product),
> > >or be used *from* non-free software as a plugin (etc). The phrasing
> > >in here is odd.
>
> > Well this is already the standard for the GPL-license: GPL programs
> > as far as being
> > compiled can not be incorporated into commercial software; you have
> > to use L-GPL.
> > Why not establish a similar standard for protecting intellectual
> > property also for
> > programs written in a script language? (i.e. this is the reason why
> > I called it S-FSL).
>
> That's not true; commercial software *can be paid software*. So long as
>

can be free software* (sorry!)


> the software is compatable (and the work on the whole is distributed as
> GPL), this isn't a problem.
>
> Please, if you don't know how the GPL works, I have to strongly insist
> on you not writing your own license.
>
> > If the phrasing is odd we will have to rework it; it is my intention
> > to have a license
> > clear to everyone; not only to lawyers.
> > >
> > >I strongly encourage you to not write your own license terms. Please
> > >consider using a well-known and understood license.
> >
> > Well to me it is an issue under which license to publish. I do not
> > want to burden
> > my distributor unncessarily but actually want to retain as much
> > rights as possible
> > because writing, maintaining the software and supporting also casual
> > users is a
> > major effort.
>
> It's a lot more effort for the distributors to review this license and
> attempt to figure out how it applies in different jursidictions, with
> other licenses and how to properly comply.
>
> > >
> > >Cheers,
> > >   Paul
> >
> > Many Thanks for your Commitment,
> > Elmar
>
> Cheers,
>   Paul
>
> --
>  .''`.  Paul Tagliamonte 
> : :'  : Proud Debian Developer
> `. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
>  `- http://people.debian.org/~paultag
>



-- 
:wq

Bug#728716: RFS: xchroot/2.3.2-9 [ITP] -- Hi Debian!

[Paul Tagliamonte]

;distribution describes shipping of a given set of software and its
> >documentation with adherent materials."
> >
> >So if I strip away parts of the software (like documentation), and
> >publish that, does that count as distribution? Strictly reading the
> >license: no, because adherent materials are not shipped with it.
> replaced by and/or; forgetting about docs should no more matter
> >
> >  "Availablity free of charge or costs includes tools, software and
> >  manuals needed to download or obtain the distribution in a finally
> >  usable state as well as the possibility to verify the integrity of the
> >  download securely but not general connectivity to the internet."
> >
> >This part is also quite vague. Lets imagine the following scenario:
> >there's Joe Average user, installing GNU/Linux for the first time. He
> >has absolutely no idea how to do it, so he buys a book about the topic.
> >To install additional software, such as those covered by this license,
> >he uses tools and techniques described in the manual, for which he paid
> >for. In this case, the distribution is not allowed to let Joe Average
> >install programs covered by this license, because he needed a paid-for
> >manual to install the distribution and the software covered by the
> >license in question.
>  Thanks for that hint. My intention was that a technically experienced user
> should be able to do it. For OS/2 Warp 4.5 doing the updates without
> purchasing docs was even impossible for a technical expert user before
> http://www.elstel.org/OS2Warp/InstallUpdate.html. That is the only issue
> I want to prevent.
> :: replaced by the term 'averagely experienced technical user'
> 
> >>> That's not true; commercial software *can be paid software*. So
> >>> long as
> >>>
> >>>
> >>>can be free software* (sorry!)
> >>>
> >>> the software is compatable (and the work on the whole is
> >>> distributed as
> >>> GPL), this isn't a problem.
> >>>
> >>> Please, if you don't know how the GPL works, I have to strongly insist
> >>> on you not writing your own license.
> >>>
> >>   Oops there we have an error! (Well I clearly know how it works with GPL.)
> >>Commercial software does not need to be paid software. Well, to me a
> >>similar restriction like for GPL could be very handy: having to put
> >>all of the
> >>software under any OSS-compliant license as soon as an S-FSL program
> >>is incorporated (That would also limit possible interference with other
> >>licenses).
> >>Would that be acceptible?
> >I'm not exactly sure I understand what you mean here. If you mean that
> >any program or distribution that incorporates an S-FSL licensed program
> >will need to comply with the S-FSL license terms aswell, that will not
> >work. First of all, the S-FSL is not compatible with the GPL, so you
> >can't "link" it or integrate it with anything that is GPL'd.
> >Furthermore, DFSG#9: a license must not contaminate other, unrelated
> >software.
> no just compliance with any OSS-license like f.i. GPL so that S-FSL is
> 'compatible' to other licenses; see for S-FSL v1.3.3
> 
> 

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#728716: [License-review] For Approval: Scripting Free Software License, Version 1.3.5 (S-FSL v1.3.5)

[Paul Tagliamonte]

On Fri, Nov 08, 2013 at 04:15:30PM +, Elmar Stellnberger wrote:
> >>"specific to someone": Well this is an unavoidable necessity in order to
> >Maybe, but specific clauses like this clearly violate OSD #3 and #5
> >(#3: if your downstream “A” is a “public distribution” and A’s
> >downstream “B” isn’t, B cannot distribute them under the same terms
> >as it got them from A under).
> Well we could crop out this special facilitation but that would make
> the license less fit for practical purposes. I do not want to sacrifice
> practical fitness towards perfectly strict OSI compliance.

To be clear, not satisfying OSD 3 & 5 (DFSG 3 and 5 as well) this will
*NOT* be fit for Debian main. You're free to try to get it into
non-free.

Thanks!
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#728716: xchroot: packaging as non-free

[Paul Tagliamonte]

Email ftpmas...@ftp-master.debian.org with your license, and the ftpteam
will disucss if we can distribute it safely. If so, you can upload it to
non-free. Ask your sponsor for more information on that.

Please note that non-free is *not* Debian (the distribution), but is
mearely software hosted on Debian boxes, and given small amounts of
infra (such as the BTS). We will *not* autobuild the package on the
buildd network, and you won't see project members coming to help fix RC
bugs (it's more likely it'll be removed if bugs are not tended to
quickly).

Cheers,
  Paul

On Fri, Nov 08, 2013 at 06:03:35PM +, Elmar Stellnberger wrote:
> >  You're free to try to get it into non-free.
> >
> >Thanks!
> >   Paul
> >
> How to apply for acceptance in non-free?

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Bug#728716: [License-review] For Approval: Scripting Free Software License, Version 1.3.5 (S-FSL v1.3.5)

[Paul Tagliamonte]

On Sun, Nov 10, 2013 at 05:07:00PM +, Elmar Stellnberger wrote:
> 
> Am 08.11.2013 16:33, schrieb Paul Tagliamonte:
> >On Fri, Nov 08, 2013 at 04:15:30PM +, Elmar Stellnberger wrote:
> >>>>"specific to someone": Well this is an unavoidable necessity in order to
> >>>Maybe, but specific clauses like this clearly violate OSD #3 and #5
> >>>(#3: if your downstream “A” is a “public distribution” and A’s
> >>>downstream “B” isn’t, B cannot distribute them under the same terms
> >>>as it got them from A under).
> >>Well we could crop out this special facilitation but that would make
> >>the license less fit for practical purposes. I do not want to sacrifice
> >>practical fitness towards perfectly strict OSI compliance.
> >To be clear, not satisfying OSD 3 & 5 (DFSG 3 and 5 as well) this will
> >*NOT* be fit for Debian main. You're free to try to get it into
> >non-free.
> 
> Concerning OSD conformance please see for the discussion at 
> http://projects.opensource.org/pipermail/license-discuss/2013-November/001358.html.

Debian doesn't use OSI conformance as it's measure for free software. We
have our own tests (the DFSG), and a team to work out if a license is
free (the ftpteam).

Last I checked, your license will still not be fit for Debian main.

Cheers!
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Debian/Ubuntu Package Developing with Docker

[Paul Tagliamonte]

On Mon, Nov 11, 2013 at 12:30:33AM +, T o n g wrote:
> Hi, 
> 
> I found that Docker is the best tool for developing Debian/Ubuntu 
> packages, but seems no one has talked about it in Debian world

In fact, I have. I've got a few tools brewing for Debian that use
Docker. I've got it packaged and it'll be in Debian soon.

Thanks for your interest! :)

Cheers,
Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Debian/Ubuntu Package Developing with Docker

[Paul Tagliamonte]

Hey gustavo and Tong,

On Mon, Nov 11, 2013 at 06:20:14PM +0800, gustavo panizzo  wrote:
> On 11/11/2013 08:36 AM, Paul Tagliamonte wrote:
> > 
> > In fact, I have. I've got a few tools brewing for Debian that use
> > Docker. I've got it packaged and it'll be in Debian soon.
> 
> do you have a package, even preview quality, to use it?
> i would check git.d.o but is down :(

No, not yet. This is all pre-published work. I've been following docker
upstream since they announced it (they announced it in a lightning talk
after my lightning talk announcing Hy :) ), and have been working a few
issues out (slowly)

This work is less useful for Daily developers, since schroot can do what
docker does just fine (e.g. for sbuild, etc), but docker is going to be
a huge win for a cluster of build nodes for debile.

Much love!
  Paul

-- 
 .''`.  Paul Tagliamonte 
: :'  : Proud Debian Developer
`. `'`  4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
 `- http://people.debian.org/~paultag


signature.asc
Description: Digital signature

Re: Debian/Ubuntu Package Developing with Docker

[Paul Tagliamonte]

Sorry, I missed it. We're actually the same team, we just now have 2 WNPP
bugs. We can merge them. docker.io will be the binary name.


  -T


On Tue, Nov 26, 2013 at 11:50 PM, Yaroslav Halchenko  wrote:

>
> On Mon, 11 Nov 2013, Paul Tagliamonte wrote:
>
> > Hey gustavo and Tong,
>
> > On Mon, Nov 11, 2013 at 06:20:14PM +0800, gustavo panizzo  wrote:
> > > On 11/11/2013 08:36 AM, Paul Tagliamonte wrote:
>
> > > > In fact, I have. I've got a few tools brewing for Debian that use
> > > > Docker. I've got it packaged and it'll be in Debian soon.
>
> > > do you have a package, even preview quality, to use it?
> > > i would check git.d.o but is down :(
>
> > No, not yet. This is all pre-published work. I've been following docker
> > upstream since they announced it (they announced it in a lightning talk
> > after my lightning talk announcing Hy :) ), and have been working a few
> > issues out (slowly)
>
> why then there is now two ITPs:
> (ITP - #730569) http://bugs.debian.org/730569 docker.io  -- yours
> (ITP - #706060) http://bugs.debian.org/706060 lxc-docker -- upstream's
> ?
>
> --
> Yaroslav O. Halchenko, Ph.D.
> http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org
> Senior Research Associate, Psychological and Brain Sciences Dept.
> Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
> Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
> WWW:   http://www.linkedin.com/in/yarik
>



-- 
:wq

Re: Restrictive Artwork License

[Paul Tagliamonte]

On Sat, Dec 28, 2013 at 07:36:42PM +0100, Felix Natter wrote:
> (upstream) Freeplane 1.3.x will have new icons (application icon,
> document icon), but the artist wants to keep all rights and only grant
> the Freeplane project all rights of use.

> --> Is that ok for Debian?

Not for Debian main, no. You will have to strip the icons from the
software, or move it to non-free.

> --> Is it even compatible with the GPL-2+ license of Freeplane?

Yes[*]

> Thanks and Happy New Year,
> -- 
> Felix Natter

[*]: So long as the icons are totally and sepretely loaded. For
 instance, no one would claim the GPL'd GIMP program can only edit
 GPL compatable images, just as in the general case, I don't think
 it's a problem for a GPL'd program to render or load in non-GPL'd
 assets.


Cheers,
  Paul


-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: Restrictive Artwork License

[Paul Tagliamonte]

On Sun, Dec 29, 2013 at 08:01:13PM +0100, Eric Lavarde - Debian wrote:
> I guess, it means that having the icons in a jar file isn't OK, having
> them in the file system is OK

Jar files are .zip files. Does this mean that you can't have images in
the same tarball as a GPL'd program in a tarfile?

I don't think that's right. As far as I know, this only triggers when
it's a derived work and/or sharing memory (speaking in the general
case), not when it's distributed in the same zip file.

> but java was always a border case because
> it doesn't "link" as it was understood when the GPL2 was written (GPL3
> might even be another story).

Even considering code in the same jarfile as "linked", I don't think
you can link an image to code in the same way.

Much love,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: Restrictive Artwork License

[Paul Tagliamonte]

On Mon, Dec 30, 2013 at 02:17:12PM +1100, Craig Small wrote:
> On Sun, Dec 29, 2013 at 02:19:38PM -0500, Paul Tagliamonte wrote:
> > Even considering code in the same jarfile as "linked", I don't think
> > you can link an image to code in the same way.
> I've seen it before. Takes an image and makes a C file, something like
> char my_img={ 0x11, 0x22, ... etc}

That becomes part of the C source, and isn't something it's dynamically
loading, and I think it's a different situation entirely.

BTW; the comments on the whole (for clarity, in case anyone quotes this
later) -- This isn't with my ftpteam hat on, but it's something in-line with
the ftpteam view on this.

Much love,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: DFSG package to remove images/documentation

[Paul Tagliamonte]

On Sun, Jan 12, 2014 at 05:27:45PM +0100, Pau Koning wrote:
> I have here a tarball which includes a prebuild version of the manual and all
> images are png files. But it also includes the source for the documentation
> (the python files) and the source for the images (dia and svg files).

Sweet!

> Is my understanding correct that the autogenerated documentation and images
> should be generated from the source files?

That's right!

> The problem is now that the images would have to be overwritten when they are
> converted from the source files to the input files for the manual generation.
> Is this a reason to make a DFSG tarball or do i interpret the Debian policy
> wrong? Maybe it is important to know here that I was not able to generate a
> pixel perfect equal version of the included images (which doesn't harm the
> quality of the image content at all).

The source seems like it'd be intact; you can just rm and rebuild at
build-time or something - might make the `clean' step a little harder
since you'll end up with changed binary files, but this isn't an
uncommon problem.

Of course, if you want to repack the binaries away, it'd save us all
lots of archive space, but I can see that being overkill for a few
files.

Anyway; I'd personally do a non-dfsg repack myself, but either way
works.

Cheers,
  Paul

[without any hats on other than his DD one]

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: Can't push new mcron package to FTP

[Paul Tagliamonte]

This is a question for the ftpteam, but here's the reason why::

Apr 29 14:22:47 processing /mcron_1.0.7-1_i386.changes
Apr 29 14:22:47 GnuPG signature check failed on mcron_1.0.7-1_i386.changes
Apr 29 14:22:47 /mcron_1.0.7-1_i386.changes has bad PGP/GnuPG signature!
Apr 29 14:22:47 Removing /mcron_1.0.7-1_i386.changes, but keeping its
associated files for now.
Apr 30 14:22:42 Deleted stray file /mcron_1.0.7-1_i386.deb
Apr 30 14:22:42 Deleted stray file /mcron_1.0.7-1.dsc
Apr 30 14:22:42 Deleted stray file /mcron_1.0.7-1.debian.tar.gz
Apr 30 14:22:42 Deleted stray file /mcron_1.0.7.orig.tar.gz


Was it signed by a key in the keyring?

Cheers,
  Paul


On Thu, May 1, 2014 at 12:38 PM,   wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello, a couple of days ago I uploaded a new version of
> mcron to the upload FTP server, and heard not a titter about
> it (it does not seem to have gone through).  It is a while
> since I last did this... can someone help me please?
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.19 (GNU/Linux)
>
> iEYEARECAAYFAlNid8kACgkQ5KKKrDEYI0JxjwCdHgHVM1XLmLl8LZRa8krUv7ie
> 8hEAn0YhauA0w62OicoEnwAnorzMMtgP
> =Cea5
> -END PGP SIGNATURE-
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/e1wfu06-00048q...@rdmp.org
>



-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cao6p2qrzb_aedtm3ajeariyoqrvm8116zg-grs5rxvntdqf...@mail.gmail.com

Re: Licensing question

[Paul Tagliamonte]

On Fri, Jul 11, 2014 at 04:03:26PM +0200, Eric Maeker wrote:
> Thanks Guido,
> 
> I've read the thread. I think we should include this complex discussion
> inside the Debian wiki.
> 
> If I've clearly understood, a package that would contain any data with
> this licence would not be elligible to the free repo of Debian even if
> these data remain "exactly as is".
> 
> We could think that these data could be distributed non modified with an
> application and then when user runs this application for the first time,
> data are processed. In this case, Debian distribute unmodified data. Am
> I wrong?
> 
> Eric
> 

I'll of course defer to Charles' ability to understand french, so
working from the English translation (which is to say, I might be
missing something), I don't see the same issues he does.


Both the ISC and MIT/Expat license don't explicitly allow distribution
of modified works, but it's pretty implicit:

/ ISC
| Permission to use, copy, modify, and/or distribute this software for
| any purpose with or without fee is hereby granted, provided that the
| above copyright notice and this permission notice appear in all copies.
\ ISC

(OK, this has an and/or, so perhaps not the best example, sorta like how
 the BSD licenses do this explicitly)

/ Expat
| Permission is hereby granted, free of charge, to any person obtaining a
| copy of this software and associated documentation files (the
| "Software"), to deal in the Software without restriction, including
| without limitation the rights to use, copy, modify, merge, publish,
| distribute, sublicense, and/or sell copies of the Software, and to
| permit persons to whom the Software is furnished to do so, subject to
| the following conditions:
\ Expat

/ LOOL
| • To reproduce, copy, publish and transmit the « Information »
| • To disseminate and redistribute the « Information »
| • To adapt, modify, transform and extract from the « Information »,
|   for instance to build  upon it in order to create « Derivative information »
| • To exploit the « Information » commercially, for example, by
|   combining it with other « Information », or by including it in your own
|   product or application. 
\ LOOL

I'd have to think more about it.

Cheers,
   T

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: Licensing question

[Paul Tagliamonte]

On Sat, Jul 12, 2014 at 08:18:06AM +0900, Charles Plessy wrote:
> Hi all,
> 
> the essence of my conclusion in 2012 was: “in doubt, ask Upstream”.  Sorry 
> that
> it was not clear.  Also, if after reading the email of Jonathan Keller in the
> same thread you still have no doubts, go ahead with your conclusion; the worst
> case scenario is only to have to remove the packages from our Project's main
> archive later.

After reading the mail you refrence, I agree with consensus. Seems
shady. Ask upstream for clarification.

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

Re: Build-depending on non-free package

[Paul Tagliamonte]

On Tue, Sep 02, 2014 at 05:43:15PM +0200, Ole Streicher wrote:
> > It requires manually vetoing which packages from non-free are safe to
> > be used as contrib build dependencies (much like we manually veto what
> > packages from non-free can be autobuilt).
> 
> Why would we need to manually select them?

We don't know what makes them non-free. The contents of the license may
have restrictions that impose legal risk.

https://lists.debian.org/debian-devel-announce/2006/11/msg00012.html

[snip]

> > it will likely require autobuilder tooling changes to check for a
> > "xs-autobuild: yes" flag when resolving dependencies from non-free, or
> > something to that effect.

Recentish thread: 

https://lists.debian.org/debian-project/2010/09/msg00044.html

[snip]

> We want to provide a binary distribution to our end users, and we want
> to have best possible experience, right?

We want to provide a libre / *free* distribution to our end users.
Anything else is just tolerated / hosted. non-free is *not* Debian (the
distribution), it's simply hosted on Debian project infra.

Cheers,
  Paul

-- 
 .''`.  Paul Tagliamonte   |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `- http://people.debian.org/~paultag/conduct-statement.txt


signature.asc
Description: Digital signature

GPG Signature

[Paul Tagliamonte]

Hey Mentors,

I sent a message to the front desk to no avail on this subject.

I added myself as requesting a GPG signature in the Cleveland area
from a DD ( the only thing holding me back from starting the new
maintainer process ) and really felt that I gave it due discourse (
the wiki, front desk and a few hours searching for DDs in the
Cleveland area have all proven fruitless ).

Any ideas on next steps?

Paul Tagliamonte

-- 
#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/bc5805c31003211938k2aaa86eap16608e6706da5...@mail.gmail.com

Re: GPG Signature

[Paul Tagliamonte]

On Mon, Mar 22, 2010 at 1:14 AM, Paul Wise  wrote:
> On Mon, Mar 22, 2010 at 9:38 AM, Paul Tagliamonte  wrote:
>
>> I added myself as requesting a GPG signature in the Cleveland area
>> from a DD ( the only thing holding me back from starting the new
>> maintainer process ) and really felt that I gave it due discourse (
>> the wiki, front desk and a few hours searching for DDs in the
>> Cleveland area have all proven fruitless ).
>
> There don't appear to be an DDs listing Cleveland in their LDAP information.
>
>> Any ideas on next steps?
>
> You can apply without having your key signed and then get it signed
> before you finish the process.

Did not know that. Thank you!

>
> It is not too far to NYC, you could come to the keysigning at DebConf10.

Aye. I will have to see if I can make it out that way.

>
> There is a keysigning offer listed for Pittsburgh, which seems close.

Yeah, 3 hours is not bad. I might look into that.

>
> --
> bye,
> pabs
>
> http://wiki.debian.org/PaulWise
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/e13a36b31003212214m71f46944if7f26eba9b958...@mail.gmail.com
>
>

Thanks :)

Paul

-- 
#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/bc5805c31003212219u3e629548nc8f1fe3cf1481...@mail.gmail.com

Re: GPG Signature

[Paul Tagliamonte]

On Thu, Apr 8, 2010 at 7:05 PM, Pablo Duboue  wrote:
> On Monday 22 March 2010, Paul Tagliamonte wrote:
>> On Mon, Mar 22, 2010 at 1:14 AM, Paul Wise  wrote:
>> > On Mon, Mar 22, 2010 at 9:38 AM, Paul Tagliamonte 
> wrote:
>> >> I added myself as requesting a GPG signature in the Cleveland area
>> >> from a DD ( the only thing holding me back from starting the new
>> >> maintainer process ) and really felt that I gave it due discourse (
>> >> the wiki, front desk and a few hours searching for DDs in the
>> >> Cleveland area have all proven fruitless ).
>> >
>> > There don't appear to be an DDs listing Cleveland in their LDAP
>> > information.
>> >
>> >> Any ideas on next steps?
>> >
>> > You can apply without having your key signed and then get it signed
>> > before you finish the process.
>>
>> Did not know that. Thank you!
>>
>> > It is not too far to NYC, you could come to the keysigning at DebConf10.
>>
>> Aye. I will have to see if I can make it out that way.
>
> Even better, you can help us out with DC10 and stop by NYC a few months
> earlier :-) :-)
>
> There are plenty of DDs in the New York metro area.
>
> For opportunities to volunteer take a look at
>
>   http://wiki.debconf.org/wiki/DebConf10
>
> or just stop by #debconf-nyc at IRC.
>
> Cheers,
>
> Pablo
>

I'll try my best Pablo! I hear Debconf is a blast!

I did get this all set, there were three DDs in Boston nice enough to
sign my key while I was on Vacation :)

All the best,
Paul Tagliamonte

-- 
#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/o2ubc5805c31004081619y5373848auba0a6a22eb7b3...@mail.gmail.com

Lintian thinks a Non-Debian Native package is Debian Native

[Paul Tagliamonte]

Hey Mentors,


My maintainer ( on Fluxbox ) is on vacation. I'm an Uploader.

My package is whining that it's debian native, when Fluxbox is
maintained outside of Debian.

This cropped up after there were dfsg changes, but this is not why (
Lintian whines that we have a dfsg on a native package, as it should )


I'd love to get the package lintian clean again before he gets back.
Can anyone shed light on this[1] ?

I'm pretty sure it's a small mistake on my part.


( Yes I know about .git, yes, I know how to fix that one ;) )


Thanks, Mentors!
-Paul

[1]: http://lintian.debian.org/maintainer/un...@debian.org.html#fluxbox

-- 
#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktile90pkg9-u6-xbxzuez9yqbynnjsijlvphd...@mail.gmail.com

Re: Lintian thinks a Non-Debian Native package is Debian Native

[Paul Tagliamonte]

On Thu, Jun 24, 2010 at 8:39 AM, Johan Van de Wauw
 wrote:
> Paul,
>
> I'm not an expert, but it seems that your fluxbox_1.1.1+dfsg1-1.tar.gz
> contains your debian directory.
> You should repackage your upstream source doing the dfsg cleaning and
> make it fluxbox-*+dfsg.orig.tar.gz
> *Don't add your debian dir to the repackaged sources*
> (Apart from that, you should describe in debian/copyright which files were
> removed from the upstream release)

We just updated them. We got Upstream to relicense, and change their
tgz. I merged the new files + copyright head into the branch. I'll
note that, thanks :)

>
> Johan
>
> On Thu, Jun 24, 2010 at 2:22 PM, Paul Tagliamonte  wrote:
>> Hey Mentors,
>>
>>
>> My maintainer ( on Fluxbox ) is on vacation. I'm an Uploader.
>>
>> My package is whining that it's debian native, when Fluxbox is
>> maintained outside of Debian.
>>
>> This cropped up after there were dfsg changes, but this is not why (
>> Lintian whines that we have a dfsg on a native package, as it should )
>>
>>
>> I'd love to get the package lintian clean again before he gets back.
>> Can anyone shed light on this[1] ?
>>
>> I'm pretty sure it's a small mistake on my part.
>>
>>
>> ( Yes I know about .git, yes, I know how to fix that one ;) )
>>
>>
>> Thanks, Mentors!
>> -Paul
>>
>> [1]: http://lintian.debian.org/maintainer/un...@debian.org.html#fluxbox
>>
>> --
>> #define sizeof(x) rand()
>> :wq
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>> Archive: 
>> http://lists.debian.org/aanlktile90pkg9-u6-xbxzuez9yqbynnjsijlvphd...@mail.gmail.com
>>
>>
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/aanlktimjgm6bat3ttftkmocgq6ftfqd5pmr9upx92...@mail.gmail.com
>
>



-- 
#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikvn4kayxhtw35h6epociy6y3u_imfsepkbh...@mail.gmail.com

Re: Lintian thinks a Non-Debian Native package is Debian Native

[Paul Tagliamonte]

On Thu, Jun 24, 2010 at 8:46 AM, Nick Leverton  wrote:
> On Thu, Jun 24, 2010 at 08:22:37AM -0400, Paul Tagliamonte wrote:
>> Hey Mentors,
>>
>>
>> My maintainer ( on Fluxbox ) is on vacation. I'm an Uploader.
>>
>> My package is whining that it's debian native, when Fluxbox is
>> maintained outside of Debian.
>>
>> This cropped up after there were dfsg changes, but this is not why (
>> Lintian whines that we have a dfsg on a native package, as it should )
>
> In my own experience, the commonest way of accidentally building a Debian
> native package (a source format, nothing to do with where it's maintained)
> is to have a wrongly named upstream tarball, which dpkg-source will not
> associate with your package.
>
> For a package of fluxbox 1.1.1+dfsg1-1 your Debian revision is -1,
> and the tarball should thus be fluxbox_1.1.1+dfsg1.orig.tar.gz.
> Everything before the dash is counted as the upstream version number,
> even when it's a result of DFSG re-packaging.

This makes a lot of sense. Thanks Nick, Nigel!

>
> Nick
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/20100624124646.ga30...@leverton.org
>
>

-Paul

-- 
#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktim-j5fi9kff1t1es7uesqxxpqs0faxm_ccia...@mail.gmail.com

Default Configuration Issues

[Paul Tagliamonte]

Hey Mentors,

I'm a co-maintainer on the "Fluxbox" package.

I have recently moved to packaging their git head, as their last
release was 2008 ( even though they have had regular development since
then ).

The stock ( un-configured ) behavior of Fluxbox was to allow
window-dragging with a left-click. This has been changed for the next
release ( and thusly, the git head ).

Since this was stock before, the old version of the debian keys file
does not have the configuration directive ( OnTitlebar Mouse1
:StartMoving ) to enable left-click window moving. I found this out
early, and patched the global configuration file. Fluxbox, however,
copies the file to the ~/.fluxbox folder, and uses that without
checking for additional directives in the global conf file. Whoops.

This is causing breakage of old installs that are upgrading. What is
the "right" way of fixing this?

-Paul Tagliamonte

-- 
#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktims+5oftjhy71pylyjwnb0xsz1k97p=ecgqo...@mail.gmail.com

Re: Default Configuration Issues

[Paul Tagliamonte]

2010/8/14 Rogério Brito :
> Hi, Paul.
>
> On Aug 13 2010, Paul Tagliamonte wrote:
>> I'm a co-maintainer on the "Fluxbox" package.
>
> I happen to be a user of fluxbox.

Thank you :)

>
> Oh, just one stylistic note about the way that you write things both in
> your text and in your changelogs:
>
>> ( even though they have had regular development since then ).
>
> You seem to put one space after a left parenthesis and one before the
> right parenthesis. The usual rules for typesetting text dictates that
> there should be no such spaces. Therefore, the text above should be
> written as:
>
>   (even though they have had regular development since then).

Noted duly. I'll make sure I do this from now on. It's a habit from
how I program.

>
>> The stock ( un-configured ) behavior of Fluxbox was to allow
>> window-dragging with a left-click.
>
> You probably meant window dragging with a left click on the title bar,
> right?

Yes

>
>> Since this was stock before, the old version of the debian keys file
>> does not have the configuration directive ( OnTitlebar Mouse1
>> :StartMoving ) to enable left-click window moving.
>
> OK.
>
>> I found this out early, and patched the global configuration file.
>
> OK.
>
>> Fluxbox, however, copies the file to the ~/.fluxbox folder,
>
> "the file" means the global configuration file?

Yup.

>
>> and uses that without checking for additional directives in the global
>> conf file. Whoops.
>
> This is not clear: you say that "uses that" (the global config file?)
> "without checking for additional directives in the global conf file".
> If it is using the global configuration file, it is honoring the
> settings there, isn't it?

I thought that when I patched the global settings file that fluxbox
would import settings from there, then import settings from the user
local config file. Since the configuration directive is not in the
user local settings for fluxboxes (or is that fluxboxii) of years
past, I thought it would have pulled from the global file and not
caused issues.

I was wrong.

>
> Your description didn't sound precise here.
>
>> This is causing breakage of old installs that are upgrading. What is
>> the "right" way of fixing this?
>
> In general, a change in behavior can be handled gracefully with some
> time for "transitions", so that they users can adapt to that (before
> that becomes the default) and with a conspicuous notice (say, in NEWS).

Hurmm. This makes perfect sense. Is there anything I can do after the
fact? I've done the damage, and I'd really not like to leave people
with half-working installs of fluxbox when they upgrade.

>
>
> Regards,
>
> --
> Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
> http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
> DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
>

Thanks,
Paul Tagliamonte

-- 
#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimikr2k5c81xxj-r2bu0jsf5myg9ewmwelni...@mail.gmail.com

Re: preinstall

[Paul Tagliamonte]

Hey,

You should read the packaging basics page --

http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html

Check at chapter 7.6

I've also noticed you've been asking a lot of these types of
questions, perhaps you should read up a bit more before you start
trying to take on such a large project. Nothing against asking
questions, but these are all in the basic manuals.

Godspeed,
-Paul

On Sun, Aug 22, 2010 at 1:07 PM, Zvi Dubitzky  wrote:
> Hi
> is there a preinstall script defined for a Debian installation (I  see a
> postinstall and potsrm)
>
> thanks
>
> Zvi Dubitzky
> Email:d...@il.ibm.com
> IBM Haifa Research Laboratory    Phone: +972-4-8296182
> Haifa, 31905, ISRAEL
>
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/of61e5b816.d5c78354-onc2257787.005df904-c2257787.005e1...@il.ibm.com
>
>



-- 
#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlkti=lvakx0mcjytrnxtdpdlfaycbjweaxeuj71...@mail.gmail.com

Re: RFS: fritzing

[Paul Tagliamonte]

You should avoid getting it into the Ubuntu repositories directly --
there is a sync every cycle, if it's uploaded to Debian, it will be in
Ubuntu in time for the next release, try focusing on getting this RFS
through the Debian system -- no need to use REVU for this.

2010/10/3 Enrique Hernández Bello :
> Dear mentors,
> I am looking for a sponsor for my package "fritzing".
> * Package name    : fritzing
>   Version         : 0.4.3b-1
>   Upstream Author : Fritzing Developers 
> * URL             : http://fritzing.org
> * License         : GPLv3 & CC:BY-SA
>   Section         : electronics
> It builds these binary packages:
> fritzing   - Easy-to-use, electronic design software
> My motivation for maintaining this package is:
>   I want to collaborate with this project and I would like my package in
> official repos of
>   Debian and Ubuntu. This is my second try and now I have a valid branch in
> launchpad.
>   I will try to upload to REVU, too.
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/f/fritzing
> - Source repository: deb-src http://mentors.debian.net/debian unstable main
> contrib non-free
> - dget
> http://mentors.debian.net/debian/pool/main/f/fritzing/fritzing_0.4.3b-1.dsc
> I would be glad if someone uploaded this package for me.
> Kind regards
>  Enrique Hernández Bello
> --
> Enrique Hernández Bello
>



-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlkti=njpnsvmuwo4fzarjmtuqcwhgh0vxhm=lxh...@mail.gmail.com

Re: RFS: jsl - JavaScript program checker

[Paul Tagliamonte]

Aye, is it a lint-esque checker or some sort of library for debugging?

On Sat, Oct 23, 2010 at 1:22 PM, Thomas Goirand  wrote:
> On 10/23/2010 11:08 PM, Laurent Arnoud wrote:
>> It builds these binary packages:
>> jsl        - JavaScript program checker
>>
>> My motivation for maintaining this package is:
>> I'm currently using it as a web developer.
>>
> Hi,
>
> Would you mind describing a bit more the package,
> and tell why it's useful?
>
> Thomas
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4cc319e7.8040...@debian.org
>
>



-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktim1wsr3i4az=9kav6bppu3bh_8o-zoovm_w+...@mail.gmail.com

Re: RF[CS]: ubiquity (mozilla extension) in Debian

[Paul Tagliamonte]

On Tue, Oct 26, 2010 at 9:48 AM, Gabriele Giacone <1o5g4...@gmail.com> wrote:
> On 10/26/2010 08:52 AM, Luca Falavigna wrote:
>> Just for the records, Ubuntu has a ubiquity source package already (it's
>> the d-i frontend), so if you're interested in having such package in
>> Ubuntu too, you should consider using a different source name.
>>
> I'm not interested in ubuntu.
> Rename could be even done by ubuntu maintainers, couldn't it?

We try and maintain a symbiotic relationship with Debian. If we fix
something, we send it upstream to help Debian. When Debian fixes
something, we benefit.

If we spent all our time renaming packages in Debian, we would have
forked packages and a whole lot of mess.

After all, you'd accept a patch from an Ubuntu hacker, right? Why
treat Ubuntu so poorly? Be nice, please :)

Honestly, since this is a minor package, and ubiquity is the Ubuntu
installer, and this is a minor plugin, someone would most likely
blacklist your package, and it would not be included in Ubuntu.

>
> Anyway, your sponsorship might convince me to rename it :)
>
>
> Cheers,
> Gabriele
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4cc6dc38.3070...@gmail.com
>
>

Good luck!

-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikwfbnsd4nqt9jjyut7b8jm7s=12jzmdzj2m...@mail.gmail.com

Re: RF[CS]: ubiquity (mozilla extension) in Debian

[Paul Tagliamonte]

On Fri, Oct 29, 2010 at 6:57 PM, Gabriele Giacone <1o5g4...@gmail.com> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 10/26/2010 07:41 PM, Paul Tagliamonte wrote:
>> We try and maintain a symbiotic relationship with Debian. If we fix
>> something, we send it upstream to help Debian. When Debian fixes
>> something, we benefit.
>
> IMHO just the latter is always true.

I'm working with Debian, and I'm not a DM, DD or anything. Therefore
saying that the latter is always true is wrong. However, your bias is
clearly noted. Also wrong, but noted.

>
>
> Anyway, renamed.
>
> http://mentors.debian.net/debian/pool/main/u/ubiquity-mozilla/ubiquity-mozilla_0.6-1.dsc

You're having trouble following the rules. I'm going to CC the Debian
Group to see if they could help you.

I quote:

The binary package's name should be xul-ext- with  being the
extension's name. E.g. xul-ext-nostalgy for Icedove's nostalgy
extension.

( as was noted before at http://wiki.debian.org/Mozilla/ExtensionsPolicy )


You should rename the package to fix Debian's conventions.

>
>
> - --
> Gabriele
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iEYEARECAAYFAkzLUXIACgkQp3cdCbVcnCvPjwCg1pRGZCs4nVbR/+3ShVs5Ysu5
> TyAAoIfJbDVfrejkfRY+U5qnPuXT/hLp
> =K63L
> -END PGP SIGNATURE-
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4ccb5172.7070...@gmail.com
>
>

You should also consider being nicer to people and sister projects.
Such unjustified and blind hate is not proper. It makes me not want to
help you, at all.

-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikj5ngesximasibds0n_angq7xyqsnfqkysc...@mail.gmail.com

Re: RFS: remotepad-server

[Paul Tagliamonte]

On Tue, Nov 23, 2010 at 10:51 PM, Paul Wise  wrote:
> On Thu, Nov 18, 2010 at 2:27 AM, Alexandre Rossi
>  wrote:
>
>> I am looking for a sponsor for my package "remotepad-server".
>>
>> * Package name    : remotepad-server
>>  Version         : 1.10+dfsg.1-1
>>  Upstream Author : Kawamoto Yosihisa 
>> * URL             : http://www.tenjin.org/RemotePad/
>> * License         : GPL2, BSD style
>>  Section         : x11
>>
>> It builds these binary packages:
>> remotepad-server - Server for mouse/keyboard X11 remote control using
>> Apple's iPhone
>
> Hmm, if the client were ported to Debian/X11 then I might like to
> sponsor this, since I run Debian on my OpenMoko FreeRunner and played
> with this air-mouse project that does something similar. You might
> want to put those two upstreams in touch with each other:
>
> http://code.google.com/p/air-mouse/
>
> --
> bye,
> pabs
>
> http://wiki.debian.org/PaulWise
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/aanlktim0ssdxdydcgvnmo4a7ekmu3z9vwdv+0joob...@mail.gmail.com
>
>

Just FYI ( for anyone on the list ) -- there's software in Debian that
does this already -- rinputd

cheers,
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikcyvivytw3rt4l--p-xdqju8n_yztjos=we...@mail.gmail.com

Re: RFS: mosquitto

[Paul Tagliamonte]

I'm not a Debian Developer, but here's my review:

On Sun, Nov 28, 2010 at 5:45 PM, Roger Light  wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "mosquitto".
>
> * Package name    : mosquitto
>  Version         : 0.9-1
>  Upstream Author : Roger Light 
> * URL             : http://mosquitto.org/
> * License         : BSD
>  Section         : net
>
> It builds these binary packages:
> libmosquitto0 - MQTT version 3.1 client library
> libmosquitto0-dev - MQTT version 3.1 client library, development files
> libmosquittopp0 - MQTT version 3.1 client C++ library
> libmosquittopp0-dev - MQTT version 3.1 client C++ library, development files
> mosquitto  - MQTT version 3 compatible message broker
> mosquitto_pub - Mosquitto command line publish client
> mosquitto_sub - Mosquitto command line subscribe client
> python-mosquitto - MQTT version 3.1 client library, python bindings
>
> The package appears to be lintian clean.
>
> The upload would fix these bugs: 605319
>
> My motivation for maintaining this package is that I'm the upstream
> author and want to make it easier for people to get access to it. I
> don't believe it's just a vanity upload! :)
>
> I've been packaging mosquitto for a fair while in Ubuntu PPA without
> any complaints of odd package behaviour, but it's not the simplest of
> packages and I'm a beginner so I'd certainly appreciate any comments
> you have, even if they're just stylistic problems.
>
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/m/mosquitto
> - Source repository: deb-src http://mentors.debian.net/debian unstable
> main contrib non-free
> - dget 
> http://mentors.debian.net/debian/pool/main/m/mosquitto/mosquitto_0.9-1.dsc
>
> I would be glad if someone uploaded this package for me.
>
> Thanks,
>
> Roger Light
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/aanlkti=a-acsxb3mgfnattveqmx+c_gltybm+bkgq...@mail.gmail.com
>
>

You have one wishlist lintian issue ( try running with -iIE --pedantic )

I: mosquitto source: duplicate-long-description libmosquitto0 libmosquitto0-dev
N:
N:The listed binary packages all share the same extended description. Some
N:additional information in the extended description explaining what is in
N:each package and how it differs from the other packages is useful,
N:particularly for users who aren't familiar with Debian's package naming
N:conventions.
N:
N:Severity: wishlist, Certainty: certain
N:
I: mosquitto source: duplicate-long-description libmosquittopp0
libmosquittopp0-dev

I'm not sure about the binary packages:

mosquitto_pub
mosquitto_sub

I don't know if you can have underscores. Might want to change those
to dashes. Might want to add DEP3 headers to the patches and change
the Copyright to DEP5 while you're in there as well.

I just tried to do a build and it FTBFS because of the package names.
Turns out I was right on my guess.

Needs some love :)

-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinq-+3zdwyxkxmxbenyxhfz8pxukwnn=yd6r...@mail.gmail.com

Re: RFS: mosquitto

[Paul Tagliamonte]

On Sun, Nov 28, 2010 at 5:54 PM, Paul Tagliamonte  wrote:
> I'm not a Debian Developer, but here's my review:
>
> On Sun, Nov 28, 2010 at 5:45 PM, Roger Light  wrote:
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "mosquitto".
>>
>> * Package name    : mosquitto
>>  Version         : 0.9-1
>>  Upstream Author : Roger Light 
>> * URL             : http://mosquitto.org/
>> * License         : BSD
>>  Section         : net
>>
>> It builds these binary packages:
>> libmosquitto0 - MQTT version 3.1 client library
>> libmosquitto0-dev - MQTT version 3.1 client library, development files
>> libmosquittopp0 - MQTT version 3.1 client C++ library
>> libmosquittopp0-dev - MQTT version 3.1 client C++ library, development files
>> mosquitto  - MQTT version 3 compatible message broker
>> mosquitto_pub - Mosquitto command line publish client
>> mosquitto_sub - Mosquitto command line subscribe client
>> python-mosquitto - MQTT version 3.1 client library, python bindings
>>
>> The package appears to be lintian clean.
>>
>> The upload would fix these bugs: 605319
>>
>> My motivation for maintaining this package is that I'm the upstream
>> author and want to make it easier for people to get access to it. I
>> don't believe it's just a vanity upload! :)
>>
>> I've been packaging mosquitto for a fair while in Ubuntu PPA without
>> any complaints of odd package behaviour, but it's not the simplest of
>> packages and I'm a beginner so I'd certainly appreciate any comments
>> you have, even if they're just stylistic problems.
>>
>> The package can be found on mentors.debian.net:
>> - URL: http://mentors.debian.net/debian/pool/main/m/mosquitto
>> - Source repository: deb-src http://mentors.debian.net/debian unstable
>> main contrib non-free
>> - dget 
>> http://mentors.debian.net/debian/pool/main/m/mosquitto/mosquitto_0.9-1.dsc
>>
>> I would be glad if someone uploaded this package for me.
>>
>> Thanks,
>>
>> Roger Light
>>
>>
>> --
>> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
>> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>> Archive: 
>> http://lists.debian.org/aanlkti=a-acsxb3mgfnattveqmx+c_gltybm+bkgq...@mail.gmail.com
>>
>>
>
> You have one wishlist lintian issue ( try running with -iIE --pedantic )
>
> I: mosquitto source: duplicate-long-description libmosquitto0 
> libmosquitto0-dev
> N:
> N:    The listed binary packages all share the same extended description. Some
> N:    additional information in the extended description explaining what is in
> N:    each package and how it differs from the other packages is useful,
> N:    particularly for users who aren't familiar with Debian's package naming
> N:    conventions.
> N:
> N:    Severity: wishlist, Certainty: certain
> N:
> I: mosquitto source: duplicate-long-description libmosquittopp0
> libmosquittopp0-dev
>
> I'm not sure about the binary packages:
>
> mosquitto_pub
> mosquitto_sub
>
> I don't know if you can have underscores. Might want to change those
> to dashes. Might want to add DEP3 headers to the patches and change
> the Copyright to DEP5 while you're in there as well.
>
> I just tried to do a build and it FTBFS because of the package names.
> Turns out I was right on my guess.
>
> Needs some love :)
>
> -Paul
>
> --
> All programmers are playwrights, and all computers are lousy actors.
>
> #define sizeof(x) rand()
> :wq
>

Sorry, forgot to attach logs, to help you with debugging. Excuse the spam :)

dpkg-shlibdeps: warning: dependency on libgcc_s.so.1 could be avoided
if "debian/libmosquittopp0/usr/lib/libmosquittopp.so.0" were not
uselessly linked against it (they use none of its symbols).
   dh_installdeb
   dh_gencontrol
dpkg-gencontrol: error: Illegal package name `mosquitto_pub'
dh_gencontrol: dpkg-gencontrol -pmosquitto_pub -ldebian/changelog
-Tdebian/mosquitto_pub.substvars -Pdebian/mosquitto_pub returned exit
code 255
make: *** [binary] Error 9
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package
I: unmounting /var/cache/pbuilder/ccache filesystem
I: unmounting dev/pts filesystem
I: unmounting proc filesystem
I: cleaning the build env
I: removing directory /var/cache/pbuilder/build//5552 and its subdirectories

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlkti=wvekphfy43_db0-mqh3grvkshb0hoy+64y...@mail.gmail.com

Re: RFS: mosquitto

[Paul Tagliamonte]

On Sun, Nov 28, 2010 at 7:04 PM, Roger Light  wrote:
> Hi Paul,
>
> Thanks for the pointers.

Pay it forward ;)

>
>> You have one wishlist lintian issue ( try running with -iIE --pedantic )
>>
>> I: mosquitto source: duplicate-long-description libmosquitto0 
>> libmosquitto0-dev
>> I: mosquitto source: duplicate-long-description libmosquittopp0
>> libmosquittopp0-dev
>
> I've fixed these.
>
>> I'm not sure about the binary packages:
>>
>> mosquitto_pub
>> mosquitto_sub
>>
>> I don't know if you can have underscores. Might want to change those
>> to dashes.
>
> Ah, I just changed those two packages from being a combined single
> package. Names are now fixed.

Understandable. Next time ( No judgment here ) try a pbuild before an
upload. I know it takes a few extra minutes ( esp for a multi-binary
package like this ), but it's worth it.

>
>> Might want to add DEP3 headers to the patches and change
>> the Copyright to DEP5 while you're in there as well.
>
> Done and done.
>
> I've re-uploaded the changes.

Yup, the dsc is now lintian clean, and the DEP headers look great.
Outstanding work.

>
>> dpkg-shlibdeps: warning: dependency on libgcc_s.so.1 could be avoided
>> if "debian/libmosquittopp0/usr/lib/libmosquittopp.so.0" were not
>> uselessly linked against it (they use none of its symbols).
>
> I don't know how to fix this. Any suggestions?

You should go through the CFLAGS and check to see where it's linking
against -lgcc ( IIRC, that could be wrong ). This is a low-priority
issue, and an upstream one. I don't think many DDs would have you
apply a patch for this before an upload ( again, I could be wrong ).

Now, we also have some issues with the .deb files. Let me post my
issues ( I've removed the expanded info to avoid spamming everyone )

P is pedantic ( Very picky, but most DDs prefer that they're not
present ), and I ( informational issues ).

P: libmosquitto0: no-upstream-changelog

This one is tricky because you have a multi-binary. I'm not sure it's
best to deal with this yet. The issue is that you have to install the
Changelog to the system, but since you're installing more then one
binary package, only one should get installed ( or many partial ones
). This is pedantic for that reason. Best judgment case.

Personally, I'd put it off until someone wants a clean fix.

I: libmosquitto0: no-symbols-control-file usr/lib/libmosquitto.so.0
I: libmosquitto0-dev: extended-description-is-probably-too-short

P: libmosquitto0-dev: no-upstream-changelog

Again, there is a reason all these are marked Pedantic ;)

I: libmosquittopp0: extended-description-is-probably-too-short
P: libmosquittopp0: no-upstream-changelog
I: libmosquittopp0: no-symbols-control-file usr/lib/libmosquittopp.so.0
P: libmosquittopp0-dev: no-upstream-changelog
W: mosquitto: wrong-name-for-upstream-changelog
usr/share/doc/mosquitto/ChangeLog.txt.gz
I: mosquitto: hyphen-used-as-minus-sign
usr/share/man/man5/mosquitto.conf.5.gz:83
P: mosquitto-pub: no-upstream-changelog

W: mosquitto-pub: empty-binary-package

This is a pretty big issue. Are you not installing things to the .deb?
Check the .install ( or makefile ) for that target

P: mosquitto-sub: no-upstream-changelog

W: mosquitto-sub: empty-binary-package

Same as -pub :)

I: python-mosquitto: capitalization-error-in-description python Python

Small issue, this should be a quick fix

P: python-mosquitto: no-upstream-changelog


A lot of these are dupes. See if you can pick away one some of these.

Other then the -sub and -pub binaries being empty, nothing is too much
of a showstopper, I think. I'm rusty on that one I tag, so I'm not
sure how severe that is.

>
> Thanks,
>
> Roger
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/aanlktiko2+wri5p_axae_=p+6ir=zd0yesykg6j7p...@mail.gmail.com
>
>

Keep up the great work,
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinqg4dsk6wj2gmzbd=xlsobxud7owdxbm3ah...@mail.gmail.com

Re: RFS: qmagneto

[Paul Tagliamonte]

I'm not a Debian Developer, so I can't upload. Anyway, here's a review:

On Mon, Nov 29, 2010 at 5:11 PM, Jean-Luc Biord  wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "qmagneto".
>
> * Package name: qmagneto
>   Version : 1.3-4
>   Upstream Author : Jean-Luc Biord 
>
> * URL : http://biord-software.org/qmagneto/
> * License : GPL
>   Section : graphics
>
> It builds these binary packages:
> qmagneto   - QMagneto is an EPG (Electronic Program Guide) which displays
> the TV programs. It also able to record programs by call an external program
> as
>
>  VLC or mencoder. It is thus possible to record programs from a french BOX
> (Neufbox or Freebox) or a DVB-T device.
>
>
> The package appears to be lintian clean.
>
> The upload would fix these bugs: 603806
>
>
> My motivation for maintaining this package is: Provide a new EPG for debian
> compatible with the XMLTV format.
>
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/q/qmagneto
>
> - Source repository: deb-src http://mentors.debian.net/debian unstable main
> contrib non-free
> - dget
> http://mentors.debian.net/debian/pool/main/q/qmagneto/qmagneto_1.3-4.dsc
>
>
> I would be glad if someone uploaded this package for me.
>
> Kind regards
>  Jean-Luc Biord
>

One lintian warning with your dsc:

W: qmagneto source: out-of-date-standards-version 3.8.4 (current is 3.9.1)

postinst should be qmagneto.postinst
install should be qmagneto.install
menu should be qmagneto.menu

manpages is empty, you should delete that file.
docs is empty, you should delete that file

watch is empty, you should fix it.

As much as I love Ubuntu, you should not have Ubuntu versions in the
Changelog. This looks like a new package, so this must be left over
from your PPA. FYI, the versions should be appended with ~ppaN. That's
secondary to the fact that they should not be here :)

You should also be on revision qmagneto_1.3-1, not 4.

Remove all the old uploads from the file, and close an ITP on the
upload. If you don't have an ITP you should create one.

Your desktop file has an error:

qmagneto.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated

You should fix this as well.

I did not build the application, my netbook has a hard time. I'll
build it and look at the debs when I get back to my computer.

Cheers,
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinemm3y6kzgwahmw9e0zxmuyvbwfczyojufe...@mail.gmail.com

Re: RFS: qmagneto

[Paul Tagliamonte]

On Mon, Nov 29, 2010 at 5:23 PM, Paul Tagliamonte  wrote:
> I'm not a Debian Developer, so I can't upload. Anyway, here's a review:
>
[snip]
>
> One lintian warning with your dsc:
>
> W: qmagneto source: out-of-date-standards-version 3.8.4 (current is 3.9.1)
>
> postinst should be qmagneto.postinst
> install should be qmagneto.install
> menu should be qmagneto.menu
>
> manpages is empty, you should delete that file.
> docs is empty, you should delete that file
>
> watch is empty, you should fix it.
>
> As much as I love Ubuntu, you should not have Ubuntu versions in the
> Changelog. This looks like a new package, so this must be left over
> from your PPA. FYI, the versions should be appended with ~ppaN. That's
> secondary to the fact that they should not be here :)
>
> You should also be on revision qmagneto_1.3-1, not 4.
>
> Remove all the old uploads from the file, and close an ITP on the
> upload. If you don't have an ITP you should create one.

Sorry, I see you have one, and you're closing it. Just move the
changelog entry to the bottom and get rid of all the other entries.

Also, the close should be the only thing on that line. It's good
you're noting changes, but you don't need to on the first upload. You
should also wrap lines earlier, 80 wide is normal.

>
> Your desktop file has an error:
>
> qmagneto.desktop: warning: key "Encoding" in group "Desktop Entry" is 
> deprecated
>
> You should fix this as well.
>
> I did not build the application, my netbook has a hard time. I'll
> build it and look at the debs when I get back to my computer.
>


Sidenote before I get to the goodies: It looks like you ship the logos
of some channels in your source. Does this comply with their license?
Can you do that? I'm pretty sure there might be an issue with doing
that. Please double check, and email debian-legal if you are unsure.
That could be enough for the ftp-masters to deny the package.

( but it is impressive how much work you went through for that )

So, I built your package, it built fine. You do, however, have a
litany of issues with the deb:

E: qmagneto: description-starts-with-package-name
I: qmagneto: description-synopsis-might-not-be-phrased-properly
W: qmagneto: description-too-long
E: qmagneto: extended-description-is-empty
P: qmagneto: no-homepage-field
P: qmagneto: copyright-refers-to-symlink-license usr/share/common-licenses/GPL
I: qmagneto: desktop-entry-contains-encoding-key
/usr/share/applications/qmagneto.desktop:2 Encoding
E: qmagneto: menu-item-creates-new-root-section user /usr/share/menu/qmagneto:4
P: qmagneto: no-upstream-changelog
W: qmagneto: syntax-error-in-debian-changelog line 68 "badly formatted
trailer line"
W: qmagneto: syntax-error-in-debian-changelog line 77 "badly formatted
trailer line"
W: qmagneto: debian-changelog-line-too-long line 1
W: qmagneto: binary-without-manpage usr/bin/qmagneto
W: qmagneto: maintainer-script-ignores-errors postinst
E: qmagneto: missing-dependency-on-libc needed by ./usr/bin/qmagneto


I'd fix these up while you're in there working on the debdir. Good luck!


Hope to see the package fixed up!
-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimwcgtaxaypg7zpmyy5_ugb-y1z6okwzpmav...@mail.gmail.com

Re: RFS: mosquitto

[Paul Tagliamonte]

On Mon, Nov 29, 2010 at 7:03 PM, Roger Light  wrote:
> Hi,
>
 dpkg-shlibdeps: warning: dependency on libgcc_s.so.1 could be avoided
 if "debian/libmosquittopp0/usr/lib/libmosquittopp.so.0" were not
 uselessly linked against it (they use none of its symbols).
>>>
>>> I don't know how to fix this. Any suggestions?
>>
>> You should go through the CFLAGS and check to see where it's linking
>> against -lgcc ( IIRC, that could be wrong ).
>
> It's something that g++ is adding itself, it's not anywhere in CFLAGS
> or CXXFLAGS. That's why it's a confusing warning. Surely it must be
> using symbols, otherwise g++ wouldn't be adding it?

I honestly don't know that much about the build system anymore. I
don't think this is a showstopper :)

There might be a bug with the build system or something ( or it's
doing something "smart", as a "feature" )

>
>> W: mosquitto: wrong-name-for-upstream-changelog
>> I: python-mosquitto: capitalization-error-in-description python Python
>> I: libmosquitto0-dev: extended-description-is-probably-too-short
>> I: mosquitto: hyphen-used-as-minus-sign
>
> I've fixed all of these.

Confirmed. Looks ship-shape. New patches look in order, headers and
all. Well done.

>
>> W: mosquitto-pub: empty-binary-package
>>
>> This is a pretty big issue. Are you not installing things to the .deb?
>> Check the .install ( or makefile ) for that target
>
> Stupid mistake not renaming the install files after changing the
> names. Fixed for both of them.

Confirmed. Looks good :)

>
> The remaining lintian notes are:
>
>> P: libmosquitto0: no-upstream-changelog
>
> I've left this. The lintian tag page suggests a number of ways of
> dealing with this for multiple binary packages, one of which is to
> include it in the "main" package which is what happens here.

I'm inclined to agree with you. Perhaps a similink if someone is
*crazy* picky about it, but it looks like the other packages all
depend on libmosquittopp, so it's in order ( at least in my eyes ).
Since they're pedantic, it's not even worth overriding.

>
>> I: libmosquitto0: no-symbols-control-file usr/lib/libmosquitto.so.0
>> I: libmosquittopp0: no-symbols-control-file usr/lib/libmosquittopp.so.0
>
> I've also left these for the moment. I don't believe they are as
> relevant because this is the first packaged version. Feel free to tell
> me I'm wrong :)

I'm not sure at all, perhaps someone who knows lib packaging better
then me can butt in

>
> Cheers,
>
> Roger
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/aanlktin3dvetpaeazbxkvi9fkwkk49vc8cg=meqes...@mail.gmail.com
>
>

100% of the objections I raised look complete.

Well done, really outstanding work. Keep on it!

-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktik6weyok=u4hoynfgqhqowhbxfqqmqtnv9qm...@mail.gmail.com

Re: RFS: mosquitto

[Paul Tagliamonte]

>
> Yes, exactly :) Better to get it sorted sooner rather than later.
>
> I've uploaded a new version which adds symbol files for the two
> libraries. It also hides internal symbols for libmosquitto. This was
> actually quite easy to manually generate with only the relative few
> symbols.
>
> As far as I can tell, the only remaining lintian pedantic warning is
> no-upstream-changelog for the multiple binaries.

If it's really bugging you, you can similink. I think that might be
overkill ( imho ). I think it's fine as is ( thanks, Peter! )

>
> Thanks,
>
> Roger
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/aanlktim-md4e7kthsdec1xihkya4mtcbvwgnpqffd...@mail.gmail.com
>
>

Great work :)

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktini7c=wype44k-ddx1m4m9fxyprrpayvpdkg...@mail.gmail.com

Re: RFS: sslh (updated package)

[Paul Tagliamonte]

2010/12/13 Guillaume Delacour :
> dget http://mentors.debian.net/debian/pool/main/s/sslh/sslh_1.7a-3.dsc
>

Howdy,

I'm not a DD, and I can't upload, but here are some notes ( mostly nit-picks )

Might want to consider using DEP5 and DEP3

You should consider breaking up the Depends in the control to newline
after 80 chars

One lintian issue on the deb:

P: sslh: no-upstream-changelog

I'm not sure if this is just because I compiled it on Ubuntu, or if
it's actually an issue. I'll dig into it later if no one responds
telling me I'm wrong ( a bit short on time right now )

I get why you do it, but this is interesting in init :)

# Do NOT "set -e"

You can use a patch to put the file where it should be ( and not keep
it in the debdir ).

There is a lot of odd stuff going on, but it looks OK at first glance.
Like I said, I'll look more at it later unless someone else gets there
first :)

Cheers!
Paul


-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktim+jt6mhcvxcc2prn+rfru9=9b+32mqtb5kx...@mail.gmail.com

Re: RFS: pgfouine (updated package) (second try)

[Paul Tagliamonte]

On Wed, Dec 15, 2010 at 5:36 PM, Luis Uribe  wrote:
> Dear mentors,
>
> I'm looking for a sponsor for the new version of pgfouine
>
> It builds these binary packages:
> pgfouine   - PostgreSQL log analyzer
>
> The package appears to be lintian clean, and i'm using it in a few servers
> since a few months.
>
> Matthew Palmer [1]review it but seems that he hasn't the time to upload it.
>
> [1] http://lists.debian.org/debian-mentors/2010/10/msg00041.html

Erm, http://lists.debian.org/debian-mentors/2010/10/msg00074.html

I'll quote:

The package is really, *really* not Lintian clean, and claiming otherwise in
the RFS was bad form.  All those CVS dirs in the resulting package
definitely need gutting, and you'll want to look into why geshi is still
getting installed in the package, given that it appears to be correctly
depended on.

Apart from that, though, it builds, installs, and runs pgfouine --help, so
you're over most of the big humps.

- Matt

I'd take his advice :/

>
> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/p/pgfouine
> - Source repository: deb-src http://mentors.debian.net/debian unstable main
>  contrib non-free
> - dget
>  http://mentors.debian.net/debian/pool/main/p/pgfouine/pgfouine_1.2-2.dsc
>
> I would be glad if someone uploaded this package for me.
>
> Thanks,
>
> --
> Luis
> http://eviled.org
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.10 (GNU/Linux)
>
> iQIcBAEBAgAGBQJNCULlAAoJEDhUhRfa09XuFqIP/0/hXQpTHo8wtQ4oZkVe7wwO
> xecJvGUZcR4/pZjaCovadKI8XTFTBtY3o70+96xfCKclsjy84ygCgXkSE8e2n9cK
> bYkpeffQno9vVZebnbOTK8xcZh1KrzDODeqUKbkxlVv6QqDrldmAleasvzwljZZf
> CaNVEdrfpSBKBi1UIfZ/kFQW8I0GrelsLK2wJE/kGyYRCQZI1kiuKBnWs6mg9ut+
> nXc+BeKY8FX0Sbl99NCbJjqPZtB1R/3PPGdsIIUECkMgvGzuk6Q88A1bviwyR8ET
> ef3I2sKqhpWC8c/1BYhaKyL5X/4YNBNqb1ARi87PANO7Bh21NpYMyBaU41PvTFIU
> 8E3ofNa13GBvRTy0swUzreyelEw1tUvH7f6aG3pgtSvkOddRkszHlPgwHuAGqaS1
> UnoUot9xFTFxJhk0TcAJimI7LW6yC3DPkgB6pbxNAVx3qFpH5CKWSYD5cgjnY8Zi
> EklQwX42xf+xCmkDSYW4ubPExg2Wqof9tTvQDu0d710Gk1KXoXHqH+fLgucyrTBs
> ZcvnQb38KALD2va9XjcDtiJuHQltXjxsz2nxKS9vXxYPDmH/sV2L2zvYZfu27zAH
> 4kQ/LA7wWEG8ulYs6OHo4CifkHylbHGlgbw5bd96rkZT0SOtEH4+4vskfM79okgC
> 1Xg6JdAmUq/ixdkO1o3X
> =Umru
> -END PGP SIGNATURE-
>
>

-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikzp1enkkzhs1c_su1mdkoxf5h+mghdc0q_t...@mail.gmail.com

Re: RFS: php-pager (updated package)

[Paul Tagliamonte]

I'm not a DD, I can't upload. Here's a review:

On Wed, Dec 15, 2010 at 5:37 PM, Luis Uribe  wrote:
> http://mentors.debian.net/debian/pool/main/p/php-pager/php-pager_2.4.8-1.dsc

Consider DEP5 and DEP3.

I'd consider actually using quilt for your patches, you say it's
already in 3.0 quilt format, but you're not using it :)

You don't need the + signs in the changelog.

Foo bar baz foo ( ... ) bar
 foo bar baz foo

not:

Foo bar baz foo ( ... ) bar
 + foo bar baz foo


You have a FTBFS:

Warning: Invalid argument supplied for foreach() in
PEAR/Downloader/Package.php on line 168
PHP Warning:  Invalid argument supplied for foreach() in
/usr/share/php/PEAR/Downloader/Package.php on line 168
download directory "/build/buildd/php5-5.3.3/pear-build-download" is
not writeable.  Change download_dir config variable to a writeable dir
Cannot download non-local package "Pager-2.4.8/package.xml"
install failed
make: *** [common-install-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
E: Failed autobuilding of package

Cheers,
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktin+26a+qkdzz6e-q5ju4jd-=g+uj0wn3kfaj...@mail.gmail.com

Re: RFS: Gummi - GTK+ based LaTeX editor with live preview pane

[Paul Tagliamonte]

I'm not a Debian Developer, but my notes follow:


On Sun, Dec 19, 2010 at 5:55 PM, Daniel Stender
 wrote:
> Hi mentors,
>
> I would like to refresh my RFS call for Gummi, the GTK+ based LaTeX editor 
> with preview pane.
>
> I have improved the build by giving custom LDFLAGS, for this a couple of 
> spurious shlib deps
> observed by dh_shlibdeps are now vanished.
>
> Because of my limited bandwith here I've builded again with debuild, if you 
> please recheck the fresh
> packet (with pbuilder etc.) please be my guest. Any pointers highly 
> appreciated.
>
> The source is again to be found at: 
> http://mentors.debian.net/debian/pool/main/g/gummi

No lintian errors at all. Rules file looks tight, DEP5 and 3, uscan
works and reports back correctly.

Builds great on my pbuilder, and no lintian errors here :)

>
> Thanks you very much in advance & greets,
> Daniel Stender
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: http://lists.debian.org/4d0e8d7d.6080...@danielstender.com
>
>

Great work, keep it up! Hope you find a sponsor!
-Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimahyknejogfydyqm49ku4yg5fx4l6ud5qkn...@mail.gmail.com

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

[Paul Tagliamonte]

On Tue, Jan 4, 2011 at 1:29 AM, Richard Laager  wrote:
> On Tue, 2011-01-04 at 10:52 +0530, Bhavani Shankar R wrote:
>> as the README
>> says its safe to update the package at any stage.
>
> Isn't this basically the same as saying, "We don't introduce bugs in our
> software."? If they put the wrong information into this package,
> wouldn't that break your mobile broadband connection just as if there
> was a kernel bug for your USB 3G modem?
>
> Richard
>

FWIW, this package was unblocked a few times already, IIRC. I think
Paul Wise sponsored one of them, unless I'm going crazy ( which there
is a decent chance of ).

Cheers,
Paul

-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktikrdeqjcaf04vp6fk5dxake84qtpbde1yoak...@mail.gmail.com

Re: (future unblock) RFS: mobile-broadband-provider-info (updated package)

[Paul Tagliamonte]

> FWIW, this package was unblocked a few times already, IIRC. I think
> Paul Wise sponsored one of them, unless I'm going crazy ( which there


Sorry for the quick double post. Here's the thread.

pabs uploaded -- http://lists.debian.org/debian-mentors/2010/11/msg00143.html
medhi unblocked -- http://lists.debian.org/debian-mentors/2010/11/msg00145.html

Cheers,
Paul


-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktiktowyky6q36nb0fwpwdtaj8nqswp_g7umdv...@mail.gmail.com

Re: RFS: hydra

[Paul Tagliamonte]

Scuse the top posting and kurt prose, I'm on my droid.

Since it links against the openssl library, it causes an issue with the GPL
license. It'd have to be lgpl licensed iirc?

Might be worth a trip to debian-legal ;)

Paul

On Jan 15, 2011 9:51 PM, "mezgani ali"  wrote:

No not really, Hydra is under GPLv3, seems to be good and the bugs is not
closed In the fact i reply to this bug 602923.

Regards,



On Sun, Jan 16, 2011 at 2:07 AM, Daniel Echeverry 
wrote:
>
> On 15/01/11 19:...

Re: common source package for use in Debian and Ubuntu

[Paul Tagliamonte]

On Tue, Jan 18, 2011 at 3:42 PM, Raphael Hertzog  wrote:
> On Tue, 18 Jan 2011, Joachim Wiedorn wrote:
>> Ok, but how should I manage the last changelog entry (in time frame and
>> in handling)?
>>
>> Debian should have e.g:
>>    lilo (1:23.1-1) unstable; urgency=low
>> and then Ubuntu should have e.g:
>>    lilo (1:23.1-1ubuntu1) natty; urgency=low
>>
>>    lilo (1:23.1-1) unstable; urgency=low
>>
>> and the last Ubuntu changelog usually have some ubuntu specific bug fix
>> entries. Or should I write the ubuntu bugfixes into the Debian part of
>> changelog?
>
> Packages can be synced into Ubuntu without having any Ubuntu-specific
> changelog. Look for example:
> http://changelogs.ubuntu.com/changelogs/pool/main/s/smartmontools/smartmontools_5.39.1+svn3124-2/changelog
>
> It's a normal Debian changelog, yet it's part of Ubuntu.
>
> So use your changelog like usual and yes you should put Ubuntu bugfixes
> and Debian bugfixes in the same changelog entry. Don't create fake Ubuntu
> entries.
>
> Cheers,
> --
> Raphaël Hertzog ◈ Debian Developer
>
> Follow my Debian News ▶ http://RaphaelHertzog.com (English)
>                      ▶ http://RaphaelHertzog.fr (Français)
>
>
> --
> To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: 
> http://lists.debian.org/20110118204229.gb1...@rivendell.home.ouaza.com
>
>

When I was doing this for Fluxbox, the command dpkg-vendor ( usage in
my case: `dpkg-vendor --derives-from Ubuntu' ) came in really useful.

It helps to act as a switch for such things as themes.

Hope that helps!
-Paul


-- 
All programmers are playwrights, and all computers are lousy actors.

#define sizeof(x) rand()
:wq


--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTimiXgAuGC1KuOVDOyFA-78hVjs_kE=vdifhr...@mail.gmail.com