Re: RFS: 9menu (updated package)

[Daniel Echeverry]

Hi

I did take a look at your package.  Some comments:

  · debian/changelog: There is a space missing in the last line.

I am a bit confused, I don't understand this

  · debian/compat: You build-depend on debhelper 7, but use compat
level 5.  Is that intentional?
  · debian/rules:
- dh_auto_clean will run $(MAKE) clean for you.
- No need to remove stamp-build as you don't create it.
- You use override_* targets to pass arguments to debhelper tools,
  except for dh_install which uses debian/install.  You might want to use
  only one style.
- Is the chmod in the clean target necessary?
  · debian/watch: The comments in the first lines should be removed as
they don't really apply here.
  · debian/control: I don't think the Homepage field is helpful for end
users.  There is no additional information, only release tarballs.

Done!

I reuploaded my package to mentors, please check out:
http://mentors.debian.net/debian/pool/main/9/9menu/9menu_1.8-3.dsc


Kind regards,
Daniel Echeverry

--

Epsilon
http://www.rinconinformatico.net
http://www.fitnessdeportes.com
http://www.dragonjar.org
Linux user: #477840
Debian 6.0 Squeeze


--
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/4cce26b3.8010...@gmail.com

Re: watch file and kde-looks

[Paul Wise]

2010/11/1 Iker Salmón San Millán :

> So, at least for now the best i can do it's to fill watch file with comments
> describing the situation, isn't it?

Yep, and send an email to gitorious. SInce their website code is free
software, you could also send them a patch if you have time ;)

-- 
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/aanlktinzweok+hlotwabekwko2jugjxmnjhw5efg9...@mail.gmail.com

Re: watch file and kde-looks

[Iker Salmón San Millán]

2010/11/1 Paul Wise 

>
> You might be able to use the tan variable, but there is no indication
> in the href as to what version a particular tan corresponds to.
>
>

> The URLs listed there don't contain tags but commit SHA-1s so that
> wouldn't work.
>
> It would be a good idea to ask gitorious.org to implement something
> that works with our requirements.
>
>
> So, at least for now the best i can do it's to fill watch file with
comments describing the situation, isn't it?

Thanks

iker

Re: [Pkg-mozext-maintainers] RF[CS]: ubiquity (mozilla extension) in Debian

[Gabriele Giacone]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 10/31/2010 05:54 PM, Benjamin Drung wrote:
> Am Sonntag, den 31.10.2010, 02:51 +0200 schrieb Gabriele Giacone:
>>> 1) Please rename the source package to ubiquity-extension (or
>> Done
> 
> Can you rename the git repository too?
Renamed.

>>> 3) "${xpi:Recommends} (>= 3.6)" doesn't work, because multiple items
>>> could be generated. If you want versioned Recommends, mozilla-devscripts
>>> needs to be adjusted.
>> It generates "Recommends: iceweasel (>= 3.6)" which seems to be ok. What
>> multiple items do you mean in this case?
> 
> It depends on your build system (Debian vs Ubuntu) and on the
> install.xpi file. For example, adblock-plus has "iceweasel | icedove |
> iceape | conkeror" in Recommends. Don't rely that it will always be one
> item. Use "Recommends: iceweasel (>= 3.6), ${xpi:Recommends}" or file a
> wishlist bug against mozilla-devscripts.
> 
Probably you meant install.rdf.
I was forgetting that we're also packaging it for ubuntu and was
hardcoding just "iceweasel (>= 3.6)" while you'd prefer adding
unversioned ${xpi:Recommends}.
On ubuntu, would this xpi generate more than one Recommends? If it would
not, I'd set back initial "${xpi:Recommends} (>= 3.6)" which should work
on both worlds and postpone further changes to next upstream release or
until anyone closes the bug I just filed http://bugs.debian.org/602051
Maybe you'll close such bug before I find a sponsor.


Thanks,
Gabriele
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAkzOIpwACgkQp3cdCbVcnCvn6QCfftEX8zW0FIO0F/D4r/l45L2F
noIAoKx9RYoEfuECJTYsdxbvgjz/TdzA
=sSnq
-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/4cce22a2.6000...@gmail.com

Re: watch file and kde-looks

[Paul Wise]

On Mon, Nov 1, 2010 at 9:53 AM, Simon Paillard  wrote:
> On Mon, Nov 01, 2010 at 02:28:29AM +0100, Iker Salmón San Millán wrote:
>> I don't know if it's posible to configure it with kde-look.
>
> Which is the canonical place where the author publish the tarball ?

An example:

http://kde-look.org/content/show.php/Kadu+Penguins?content=66357

You might be able to use the tan variable, but there is no indication
in the href as to what version a particular tan corresponds to.

> Something like
> http://gitorious.org/wicd-client-kde/wicd-client-kde/archive-tarball/v0.2.1
> will work (but gitorious first reply is NOK, until the tarball is generated
> i.e. a few seconds).

The URLs listed there don't contain tags but commit SHA-1s so that
wouldn't work.

It would be a good idea to ask gitorious.org to implement something
that works with our requirements.

-- 
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/aanlktimhnbrktchf1mha2h0arj10oi835v2q=y4hp...@mail.gmail.com

Re: watch file and kde-looks

[Iker Salmón San Millán]

2010/11/1 Simon Paillard 

>
>
> Which is the canonical place where the author publish the tarball ?
>
> There is no canonical place, The author uses debian sid, and he published
the tarball in kde-look:

 http://kde-apps.org/content/show.php/Wicd+Client+KDE?content=132366

Something like
> http://gitorious.org/wicd-client-kde/wicd-client-kde/archive-tarball/v0.2.1
> will work (but gitorious first reply is NOK, until the tarball is generated
> i.e. a few seconds).
>

Yes, wih that link you can download, but the thing is (at least is what i
underestand reading de documentation) that watch file is used to detect new
versions, so should be something like:
http://gitorious.org/wicd-client-kde/wicd-client-kde/archive-tarball/(*)
???

I am a little confused with this...

Thanks a lot for replying

Iker

Re: watch file and kde-looks

[Simon Paillard]

On Mon, Nov 01, 2010 at 02:28:29AM +0100, Iker Salmón San Millán wrote:
> I am trying to edit properly watch file in order tu be able to use uscan but
> i can't do it.
> I've tried a lot of combinations with no results.  I tought that th solution
> was going to be with downloadurlmangle option but i still have no results
> I don't know if it's posible to configure it with kde-look.

Which is the canonical place where the author publish the tarball ? 
 
> I have also been looking wih githubredir.debian.net but i don't know if it
> works also with gitorius
> http://gitorious.org/wicd-client-kde/
> 
> where can i read anything else to find a clue?

Something like
http://gitorious.org/wicd-client-kde/wicd-client-kde/archive-tarball/v0.2.1
will work (but gitorious first reply is NOK, until the tarball is generated
i.e. a few seconds).

-- 
Simon Paillard


-- 
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/20101101015348.gn27...@glenfiddich.ikibiki.org

watch file and kde-looks

[Iker Salmón San Millán]

Hello mentors.

I am trying to edit properly watch file in order tu be able to use uscan but
i can't do it.
I've tried a lot of combinations with no results.  I tought that th solution
was going to be with downloadurlmangle option but i still have no results
I don't know if it's posible to configure it with kde-look.

I have also been looking wih githubredir.debian.net but i don't know if it
works also with gitorius
http://gitorious.org/wicd-client-kde/

where can i read anything else to find a clue?

Regards

Iker

Re: RFS: ovito

[Paul Wise]

2010/11/1 Pekko Metsä :

> Surely you're joking..  Just few hours ago I got my very first Debian
> package uploaded to NEW queue.  I'll definitely be more like needing
> a mentor than able to instruct others here still quite some time.

It is never too early to start reviewing packages :)

Sure, you will make mistakes, but that is part of learning.

Looking at other people's packages (and reading existing reviews in
the list archives) will help you get a feel for how Debian packaging
is done.

-- 
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/aanlktikwfqhs4q_dowitxnnnidupdfsejpm9ccpav...@mail.gmail.com

Re: RFS: fritzing

[Scott Howard]

Thanks for packaging fritzing, btw - it's a good tool to have in Debian.

2010/10/31 Enrique Hernández Bello :
> 2010/10/26 Scott Howard 
>> 2010/10/24 Enrique Hernández Bello :
>> 1) instead of CDBS and explicitly using quilt, would you consider
>> using source format 3.0 (quilt) and debhelper 7 [2]. It should make
>> your debian/rules simpler. It  appears that you are using source 3.0
>> (quilt), but you still have a debian/README.source and explicitly call
>> quilt in your debian/rules. Both of those are probably unnecessary.
>>
> CDBS is comfortable. Do you think that my debian/rules will be more simple
> without it?

CDBS is fine, it's just easier (for me) to figure out what is going
wrong with builds using debhelper (since you were having a problem
with dh_fixperms).
You have the build working, so no need to mess with it. I would look
into getting rid of the explicit quilt dependency since you are
already using source 3.0 (quilt) format to clean up the rules (and
eliminate one of the cdbs mk files, I believe)

> CDBS helper calls to debhelper orders. I don't know why dh_fixperms does not
> work.

I not comfortable with CDBS, but I'm curious why it's happening. Does
anyone else know?

>
>>
>> 3) Consider reformatting your debian/copyright to DEP-5 [3] (this is
>> nit-picking, but good form for a new package).
>>
>> 4) Consider formatting your patch descriptions to DEP-3 [4] (this too
>> is nit-picking, but good form for a new package).
>>
>
> DEP documents mentioned above are really nit-picking. Are they really
> useful?

My sponsors have made me use them in each of my uploads (even when
adopting someone elses package I had to retroactively label each
patch). They are just drafts as of now - but if it isn't much more
work, why not do it? There is no drawback (except your time) and the
benefit is machine parsing of your patches and copyright information
by the debian QA team.

> If I don't increment the release number, I can't upload it to mentors
> repository. What do you suggest? What is the common way to version a
> "pre"-release package? Perhaps adding a suffix like "~mentors1"?
>

Mentors is unique in that they allow repeated uploads of the same
version number for exactly this reason (that we are working on
packages for the same debian release version).

Regards,
Scott


--
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/aanlktinoha_zoxixrfim1t0tgtk+pf+q7h1dy7ua8...@mail.gmail.com

Re: Open RFS lacking (further) response

[The Fungi]

On Sat, Oct 30, 2010 at 11:49:25AM +0200, Niels Thykier wrote:
> Personally I believe that Noel's statement is relates to upstream,
> who have their own packaging + their own little repository as
> compared to upstreams like you, who also work on the Debian side.
[...]

Which was more or less my point as well...

I have my own packaging and I publish it in my own repository too.
However, I spent and continue to spend a disproportionate amount of
time making sure my packaging is correct for the Debian project as a
whole (to a great extent because Debian is also my preferred
operating system and the primary reference platform on which I
develop and test my software). I do that by getting my packaging
peer-reviewed on the mentors list, having an official DD upload my
packages once he's comfortable with the level of effort I've
applied, keeping up with Debian's BTS, participating in discussions
here and on debian-devel, et cetera.

In contrast, the packaging I've seen provided by upstreams who don't
actually put forth the effort to get involved to that degree are
pretty much always non-compliant with Debian standards... many FTBFS
on sid (if they even publish source packages at all), most do not
have proper Debian.changelogs with BTS-relevant closes fields, lots
are ignorant of the FHS or more Debian-specific policy directives,
few run them through QA filters like lintian or test their builds in
clean chroots... I won't even bother to enumerate the more
scary/egregious/brain-dead packaging no-nos I've seen from some.

I expect it would be less work for a seasoned DD or DM to simply
disregard the upstream-provided packaging and redo it from scratch
than try to hunt through it for those kinds of land mines. If it
were my software and I weren't submitting my own packaging work
directly into Debian, I wouldn't take it personally if the package
maintainer scrapped my unofficial packaging work and replaced it
with his own.

> On a related note, while an experienced DD (or non-DD for that
> matter) may make a "better" debian package most of them would
> still be an inferior maintainer. All bug reports are handled by
> one who knows the code and the latency of forwarding upstream bugs
> is ... 0!

A lot of that has to do more generally with the responsiveness of
the upstream developers. I personally take bug reports from any
distribution's users of my software seriously, whether or not they
come through the package maintainers. Though I also work a day job
where I constantly get bombarded by harebrained requests from
clueless users, so I'm used to handling some of the worst sorts of
end-user interaction with a smile and a nod (and the open-source
community is more competent and much easier to deal with than my
day-job customers anyway).

Faster bug triage and awareness of upstream software's development
process aside, I still expect DDs who constantly deal with
maintenance of a broad variety of packages have a more useful
perspective on distribution-wide integration which I lack.

> Personally I think you should have an extra look at the DM role.
> You may not be ready for it just yet, but I think aiming for it
> would be an improvement for you. :)
[...]

It's been on my to do list to look into, but I haven't yet gone out
of my way to pinopint any of my local DDs... no doubt there are many
here near RTP where I live, even though Raleigh is more of a Red Hat
town. I figured I'd revisit the DM process once I found an
opportunity to get a DD signature or two on my key. Also, lack of
some official status hasn't yet been an obstacle for contributing to
Debian in a variety of other ways, so I haven't seen it as a
particularly immediate need. On the other hand, given that I've been
participating in the project in an unofficial capacity for over a
decade, maybe it's time.

Thanks for the suggestion and kind words!
-- 
{ IRL(Jeremy_Stanley); WWW(http://fungi.yuggoth.org/); PGP(43495829);
WHOIS(STANL3-ARIN); SMTP(fu...@yuggoth.org); FINGER(fu...@yuggoth.org);
MUD(kin...@katarsis.mudpy.org:6669); IRC(fu...@irc.yuggoth.org#ccl);
ICQ(114362511); YAHOO(crawlingchaoslabs); AIM(dreadazathoth); }


-- 
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/20101031171757.gg8...@yuggoth.org

Re: RFS: ovito

[Pekko Metsä]

Hi and thanks!

On Sun, Oct 31, 2010 at 9:49 AM, Michael Tautschnig  wrote:
> You might want to ask upstream whether they wouldn't even want to
> release such archives themselves instead of asking people to do svn
> checkouts.

Yes, I will.

> Built & uploaded (but will have to wait in NEW, probably until
> release of squeeze).

Thank you very much for all the help.  After finding a sponsor, the
rest was fast and painless.  So, many thanks!

> I'd like to point you to [1] - if you'd have some time, it would be
> great if you could also help others to get their packages reviewed
> and sponsored. Meanwhile there have been new RFS sent to the list
> [2][3] which might be worth taking.

Surely you're joking..  Just few hours ago I got my very first Debian
package uploaded to NEW queue.  I'll definitely be more like needing
a mentor than able to instruct others here still quite some time.

But don't get me wrong. I really appreciate the hard work you DDs are
doing here, and I'm willing to give back to the community.  Last week
I joined to Debian Science Team, and I'm now looking for some
(existing) packages where I could help the team and gain more
experience.  So, who knows, maybe I'm able to support others sometimes
in future.

King regards,
 Pekko


-- 
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_9_aeuw6_cfvton-g4uq=odbsxinu4wwds...@mail.gmail.com

Re: [Pkg-mozext-maintainers] RF[CS]: ubiquity (mozilla extension) in Debian

[Benjamin Drung]

Am Sonntag, den 31.10.2010, 02:51 +0200 schrieb Gabriele Giacone:
> > 1) Please rename the source package to ubiquity-extension (or
> Done

Can you rename the git repository too?

> > 3) "${xpi:Recommends} (>= 3.6)" doesn't work, because multiple items
> > could be generated. If you want versioned Recommends, mozilla-devscripts
> > needs to be adjusted.
> It generates "Recommends: iceweasel (>= 3.6)" which seems to be ok. What
> multiple items do you mean in this case?

It depends on your build system (Debian vs Ubuntu) and on the
install.xpi file. For example, adblock-plus has "iceweasel | icedove |
iceape | conkeror" in Recommends. Don't rely that it will always be one
item. Use "Recommends: iceweasel (>= 3.6), ${xpi:Recommends}" or file a
wishlist bug against mozilla-devscripts.

-- 
Benjamin Drung
Ubuntu Developer (www.ubuntu.com) | Debian Maintainer (www.debian.org)


signature.asc
Description: This is a digitally signed message part

Re: Open RFS lacking (further) response

[Michael Tautschnig]

> Perhaps (hopefully) this initiative will change the culture of this
> list. I'll certainly try to remember to point out when people are
> ignoring non-DDs input.
> 

Me too, probably I'll even refrain from sponsoring should I note such behavior.

Best regards,
Michael



pgpWQgPPBsI8a.pgp
Description: PGP signature

Re: Open RFS lacking (further) response

[Paul Wise]

Perhaps (hopefully) this initiative will change the culture of this
list. I'll certainly try to remember to point out when people are
ignoring non-DDs input.

-- 
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/aanlktimu2l6dot_db3jsbohxpk1ka-scif07gur8y...@mail.gmail.com

Re: RFS: fritzing

[Enrique Hernández Bello]

2010/10/31 Fernando Lemos 

> Hi,
>
> 2010/10/31 Enrique Hernández Bello :
> >> This is your first release, and version 0.4.3b-1 makes sense to me as
> >> the first debian packaging released.
> >>
> >
> > If I don't increment the release number, I can't upload it to mentors
> > repository. What do you suggest? What is the common way to version a
> > "pre"-release package? Perhaps adding a suffix like "~mentors1"?
>
> Hmmm why can't you? I'm pretty sure I did that last time. Just dput,
> it'll overwrite whatever was there.
>
> Regards,
>
>
> --
> 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/aanlktimfni+p1qdikjszdv0zhqa6k3e2nvsh8zy30...@mail.gmail.com
>
>
I remembered problems overwriting uploads with the same release version but
I'm confused. Maybe it was with launchpad, so I will try again.

Thank you!

-- 
Enrique Hernández Bello

Re: Open RFS lacking (further) response

[Scott Howard]

Hello,

On Fri, Oct 29, 2010 at 3:22 AM, Michael Tautschnig  wrote:
> Unfortunately, proposals such as the collaborative package review by Charles
> Plessy [2] haven't caught any attention. In particular, this is a call to 
> people
> not being DD (yet): Everyone could review packages, but it just seems people
> only keep posting even more RFS.

I'm a non-DD that has done reviews on mentors and IRC. I can report
that there is significant pushback whenever someone hears you are a
non-DD. Understandably, the sponsees don't know if you know if they
can trust what you are saying, and since you don't have power to help
them upload, they don't even have to respond to your comments - only
to a DDs comments. A few times I have suggested something which the
sponsee disregarded (or questioned) to have a DD come and say the same
thing.

My point is that non-DD reviews might not be as helpful as we think,
if the sponsees are going to wait for a DD to respond anyways. It was
a good exercise (for me) to go through other people's packages - but I
understand that they are probably not going to trust something I say
and a DD will have to repeat my work.

Regards,
Scott


-- 
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/aanlktim2h6r-luhw0k2oqdbbngmpob9r3ig1j3q0w...@mail.gmail.com

Re: RFS: fritzing

[Fernando Lemos]

Hi,

2010/10/31 Enrique Hernández Bello :
>> This is your first release, and version 0.4.3b-1 makes sense to me as
>> the first debian packaging released.
>>
>
> If I don't increment the release number, I can't upload it to mentors
> repository. What do you suggest? What is the common way to version a
> "pre"-release package? Perhaps adding a suffix like "~mentors1"?

Hmmm why can't you? I'm pretty sure I did that last time. Just dput,
it'll overwrite whatever was there.

Regards,


--
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/aanlktimfni+p1qdikjszdv0zhqa6k3e2nvsh8zy30...@mail.gmail.com

Re: RFS: ttf-isabella (updated package)

[Charles Plessy]

Le Sun, Oct 31, 2010 at 08:23:00AM -0600, Tony Palma a écrit :
> 
> I am looking for a sponsor for the new version 1.2-1
> of my package "ttf-isabella". Isabella now has 863 characters;
> according to fc-query, it supports 140 different scripts.

Hi Tony,

have you checked with the Debian Fonts Task Force if they
would be interested to host and sponsor your package ?

http://wiki.debian.org/FontsTaskForce

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/20101031143558.ga21...@merveille.plessy.net

RFS: ttf-staypuft (updated package)

[Tony Palma]

Dear mentors,

I am looking for a sponsor for the new version 0.04-4
of my package "ttf-staypuft".

It builds these binary packages:
ttf-staypuft - The Stay-Puft free TrueType font

The package appears to be lintian clean.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/t/ttf-staypuft
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/t/ttf-staypuft/ttf-staypuft_0.04-4.dsc

I would be glad if someone uploaded this package for me. (:

Kind regards, Tony Palma.


signature.asc
Description: PGP signature

Re: RFS: fritzing

[Enrique Hernández Bello]

2010/10/26 Scott Howard 

> 2010/10/24 Enrique Hernández Bello :
> > What is the next step? :)
> > --
> > Enrique Hernández Bello
> >
>
> Hi Enrique,
>
> I'm not a DD yet, but I learned a lot from sponsors being extremely
> picky about my packages. Here are some comments for you to consider:
>
> 1) instead of CDBS and explicitly using quilt, would you consider
> using source format 3.0 (quilt) and debhelper 7 [2]. It should make
> your debian/rules simpler. It  appears that you are using source 3.0
> (quilt), but you still have a debian/README.source and explicitly call
> quilt in your debian/rules. Both of those are probably unnecessary.
>
>
CDBS is comfortable. Do you think that my debian/rules will be more simple
without it?


> 2) in debian/rules you have this comment:
> # dh_fixperms and override_dh_fixperms didn't work.
> The reason it doesn't work is that you are not using debhelper 7 type
> build system, but CDBS. See [2] for how to make debhelper 7 type
> rules.
>
>
CDBS helper calls to debhelper orders. I don't know why dh_fixperms does not
work.


> 3) Consider reformatting your debian/copyright to DEP-5 [3] (this is
> nit-picking, but good form for a new package).
>
> 4) Consider formatting your patch descriptions to DEP-3 [4] (this too
> is nit-picking, but good form for a new package).
>
>
DEP documents mentioned above are really nit-picking. Are they really
useful?


> 5) Since this is the first debian release of your package, I would
> remove all your debian/changelog entries except for:
>
> fritzing (0.4.3b-1) unstable; urgency=low
>
>  * Initial release (Closes: #601230)
>
> This is your first release, and version 0.4.3b-1 makes sense to me as
> the first debian packaging released.
>
>
If I don't increment the release number, I can't upload it to mentors
repository. What do you suggest? What is the common way to version a
"pre"-release package? Perhaps adding a suffix like "~mentors1"?


>
> 6) I like the control.in and debian/rules magic to have different
> dependencies between debian and ubuntu. I haven't seen that before,
> and it prevents a diff between the two.
>
>
Thanks! ;)


> 7) "$ lintian --pedantic -I" is clean.
>
>
> Of the above comments, I think (5) is probably the most important. I
> suggest doing 1-4 as an exercise in "good form"
>
> [1] http://wiki.debian.org/Projects/DebSrc3.0
> [2] http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-defaultrules
> [3] http://dep.debian.net/deps/dep5/
> [4] http://dep.debian.net/deps/dep3/
>
>
> --
> 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/aanlktikj7lzciqbq9kqdqj72bu+gdn77dztv7fje7...@mail.gmail.com
>
>

-- 
Enrique Hernández Bello

RFS: ttf-isabella (updated package)

[Tony Palma]

Dear mentors,

I am looking for a sponsor for the new version 1.2-1
of my package "ttf-isabella". Isabella now has 863 characters;
according to fc-query, it supports 140 different scripts.

It builds these binary packages:
ttf-isabella - The Isabella free TrueType font 

The package appears to be lintian clean.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/t/ttf-isabella
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/t/ttf-isabella/ttf-isabella_1.2-1.dsc

I would be glad if someone uploaded this package for me. (:

Kind regards, Tony Palma


signature.asc
Description: PGP signature

Re: RFS: balazarbrothers (updated package)

[Paul Wise]

On Sun, Oct 31, 2010 at 8:51 PM, Paul Wise  wrote:

> A review...

Two things I forgot:

Please upload a new screenshot, the current one is in French and is very small:

http://screenshots.debian.net/package/balazarbrothers

Please review the debtags and add any appropriate ones:

http://debtags.alioth.debian.org/edit.html?pkg=balazarbrothers

-- 
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/aanlkti=8wdk2dlti4ybqm8ma=p+ufwq_exrc8ytcj...@mail.gmail.com

Re: roxterm resizing bug serious enough for freeze exception?

[Tony Houghton]

On 31/10/10 09:18, Wen-Yen Chuang wrote:

Tony Houghton wrote:

With some window managers and/or when closing many roxterm tabs rapidly
with keyboard auto-repeat, closing tabs may cause the window to shrink,


I am the upstream author and Debian package maintainer of evilvte.

As far as I know, all VTE-based terminal emulators that supports
Tab/Tabbar, all has this kind of window-resizing bug.

Yes. Even gnome-terminal, xfce terminal, and many others, all has this
bug (in some specific window managers).


Thanks for that information. However, I think it's worse with roxterm
than others (gnome-terminal at least). My strategy was to try to correct
the size after receiving size-allocate signals, but there's no way to
reliably predict when a correction will be needed and whether the
size-allocate event will arrive immediately after an action such as
removing a tab or some time later (a g_idle_add callback attempting to
deal with this may be called many times in the meantime!).

I've had a look at gnome-terminal's code and I see it ignores
size-allocate (except for debugging) and instead makes adjustments in
response to a resize-window signal. The purpose of that signal isn't
described very well in vte's API reference, but I can just copy the sort
of thing that g-t and the vte example do with it.

--
TH * http://www.realh.co.uk


--
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/4ccd6889.2030...@realh.co.uk

Re: RFS: balazarbrothers (updated package)

[Paul Wise]

A review...

In exchange for this review, I would be very appreciative if you could
review one of the recent RFS from this list and reply in the thread
for it. This is entirely optional of course.

You might want to consider joining the Debian Games Team, maintain
balazarbrothers there and help us out with other games:

http://wiki.debian.org/Games/Team

At this stage of the release process, you should upload new versions
to experimental not unstable, unless they contain RC fixes.

No need to close #581302 in the changelog since it is already archived.

Please send the FreeDesktop menu file, patches and manual page
upstream if you haven't already.

You might want to consider switching from cdbs to dh from debhelper 7.

The resolution_video.diff patch leads me to believe that the game is
hard-coding a list of resolutions in the code. This is a bad idea.
Instead it should detect which resolutions are available on the
current system. For example my phone is 480x640 (vertical not
horizontal). It doesn't support OpenGL yet, but the game should at
least be able to adapt to arbitrary resolutions. Please discuss this
with upstream and or send them a patch.

Two warnings on the .desktop file. It also contains an unnecessary blank line.

$ desktop-file-validate debian/balazarbrothers.desktop
debian/balazarbrothers.desktop: warning: value
"Application;Game;AdventureGame;ArcadeGame;RolePlaying;" for key
"Categories" in group "Desktop Entry" contains a deprecated value
"Application"
debian/balazarbrothers.desktop: warning: boolean key "Terminal" in
group "Desktop Entry" has value "0", which is deprecated: boolean
values should be "false" or "true"

You depend on debhelper >7 but debian/compat is 5.

You don't need quilt in build-depends with dpkg-source v3.

You use a very different name in debian/control Maintainers than in
your email, what is that about?

debian/control.in says the package is orphaned, something you forgot to update?

Your debian/menu file could use a longtitle like the Comment in the
.desktop file.

Please use DEP-3 compliant headers in the patches.

http://dep.debian.net/deps/dep3/

You might want to check if the two Ubuntu bugs apply to Debian. If
they do and a new version closes them, you can put (LP: #1234) in the
changelog and then they will be closed once the package is synced to
Ubuntu.

https://bugs.launchpad.net/ubuntu/+source/balazarbrothers/+bug/591904
https://bugs.launchpad.net/ubuntu/+source/balazarbrothers/+bug/226921

balazarbrothers is available in FreeBSD (see the output of `whohas
balazarbrothers`). You might want to check if they have any useful
patches or build system things and send them upstream if appropriate.

http://www.freebsd.org/cgi/cvsweb.cgi/ports/games/balazarbrothers/

packaging warnings:

debian/rules:14: Use of DEB_PYTHON_MODULE_PACKAGE is deprecated,
please use DEB_PYTHON_MODULE_PACKAGES instead
pyversions: missing X(S)-Python-Version in control file, fall back to
debian/pyversions
dh_clean: dh_clean -k is deprecated; use dh_prep instead

lintian complaints:

I: balazarbrothers source: quilt-patch-missing-description resolution_video.diff
P: balazarbrothers: no-upstream-changelog

-- 
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/aanlktikrefaxdrzr0xthe-mkg+quz+vfaj49g=qjw...@mail.gmail.com

Re: RFS: calcoo (updated package)

[Charles Plessy]

Le Sun, Oct 31, 2010 at 12:13:24AM -0500, Tony Palma a écrit :
> 
> I am looking for a sponsor for the new version 1.3.18-3
> of my package "calcoo". Just a upgrade.
> 
> It builds these binary packages:
> calcoo - Scientific calculator (GTK+)

Dear Tony,

I had a look at calcoo and your changes for version 1.3.18-3.

The previous maintainer of the calcoo package was the upstream maintainer
himself, and he stopped updating the package at the same time as he stopped
making upstream releases. Did you try to contact him in the past or recently ?
More in general, what is your long-term plan for calcoo? How about maintaining
it in a team (http://wiki.debian.org/Teams), or storing the source package in a
VCS? All of this will help for the cases where you are unavailable for more
than a couple of weeks (as for your balazar packages for instance).

About our changes for 1.3.18-3:

  I noted that you commented one line in debian/rules. Unless the comment is
  there to carry a message, it may be clearer to just delete the line. 

  This comented line is dh_clean -k, that is deprecated by dh_prep. So the most
  proper change would have been to replace it by dh_prep. In the case of your
  package, it does not seem to make a difference…

  Once you have a good grasp of what Debhelper is doing for each key
  target of debian/rules (clean, build, install, binary,…), you may
  be interested in factorizing most of the code by the use of
  Debhelper 7 as in ‘/usr/share/doc/debhelper/examples/rules.tiny’.

  Your package has has a menu file but no FreeDesktop entry.  At your option and
  pace, maybe you can consider adding a ‘.desktop’ file.

I uploaded 1.3.18-3.

You may have noticed the discussions this week: the RFS traffic is increasing
and we need people to step up and reach a level where they can upload
independantly. Your first upload of calcoo was more than one year ago. Do you
think that there is a DD who know your contribution well enough to recommend
you as a DM? Importantly, even after you become a DM you are still most welcome
to ask for advice on this list. After becoming a DD, I still occasionally do as
well.

Lastly, it would be great if you could spare some time to have a look to one
fresh RFS on this list, and report the issues you find, or make suggestions for
improvement.

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/20101031122116.ga18...@merveille.plessy.net

Re: RFS: balazarbrothers (updated package)

[Tony Palma]

El Sun, 31 Oct 2010 06:14:48 -0600
Tony Palma  escribió:

> Dear mentors,
> 
> I am looking for a sponsor for the new version 1.0~rc1-5
> of my package "balazarbrothers". 
> 
> It builds these binary packages:
> balazarbrothers - 3D puzzle game
> 
> The package appears to be lintian clean.
> 
> The upload would fix these bugs: 4531075, 08252, 560100, 581302 
> 
The bugs are: 431075, 508252, 560100, 581302

> The package can be found on mentors.debian.net:
> - URL: http://mentors.debian.net/debian/pool/main/b/balazarbrothers
> - Source repository: deb-src http://mentors.debian.net/debian
> unstable main contrib non-free
> - dget
> http://mentors.debian.net/debian/pool/main/b/balazarbrothers/balazarbrothers_1.0~rc1-5.dsc
> 
> I would be glad if someone uploaded this package for me. (:
> 
> Kind regards, Tony Palma





signature.asc
Description: PGP signature

RFS: balazarbrothers (updated package)

[Tony Palma]

Dear mentors,

I am looking for a sponsor for the new version 1.0~rc1-5
of my package "balazarbrothers". 

It builds these binary packages:
balazarbrothers - 3D puzzle game

The package appears to be lintian clean.

The upload would fix these bugs: 4531075, 08252, 560100, 581302 

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/b/balazarbrothers
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/b/balazarbrothers/balazarbrothers_1.0~rc1-5.dsc

I would be glad if someone uploaded this package for me. (:

Kind regards, Tony Palma


signature.asc
Description: PGP signature

Re: Request for voluntary package reviews

[Alexandre Ratchov]

On Sun, Oct 31, 2010 at 12:03:27AM +0200, chrysn wrote:
> 
> concerning the midish package:
> 
> i've had a look at the midish package mentioned in [1]. it seems to be
> packaged in a reasonable way.
> 
> the only potential issue i've spottet is that Willem van Engen,
> co-author of mdep_alsa.c, is mentioned in the file's copyright section,
> but not in debian/copyright;

Oops. Now Willem in the debian/copyright file

> also, Samuel Mimram did the earlier
> packaging, he might deserve being mentioned in debian/copyright as well,
> unless 0.3.0-1 was a complete re-packaging, in which case that should be
> stated in the changelog.
> 

Yes, 1.0.4-1 is a complete repackaging because many things changed
(the upstream build process, standards, alsa support, ...). I added
the corresponding line in the changelog

> (on the minor end of the severity scale, one might suggest to upstream
> to keep source code, man pages and examples in appropriate
> sub-directories, but that's probably just a matter of style.)
>
> i couldn't test the functionality itself for lack of midi hardware, but
> at least that's reflected by appropriate warnings by midish.

I was mostly concerned by any packaging mistakes, but testing the code
itself never hurts :-)

Thanks for your comments, the new package is on the usual place:

http://mentors.debian.net/debian/pool/main/m/midish

cheers,

-- Alexandre


-- 
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/20101031120631.gc15...@moule.localdomain

Re: roxterm resizing bug serious enough for freeze exception?

[Wen-Yen Chuang]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tony Houghton wrote:
> With some window managers and/or when closing many roxterm tabs rapidly
> with keyboard auto-repeat, closing tabs may cause the window to shrink,

I am the upstream author and Debian package maintainer of evilvte.

As far as I know, all VTE-based terminal emulators that supports
Tab/Tabbar, all has this kind of window-resizing bug.

Yes. Even gnome-terminal, xfce terminal, and many others, all has this
bug (in some specific window managers).

The least buggy one is lilyterm [1], but its author also found some
corner cases that would cause lilyterm to resize itself incorrectly.

If the terminal emulator do not use Tab/Tabbar or additional GTK+
widgets, it is much more easier to keep the correct window size.
For example, the demo program included in libvte, works correctly with
various resizing event.

So, this is basically the bug of all VTE terminal emulators that
supports Tab/Tabbar in Debian.

And, VTE built with GTK+ 3.x(2.9x.x) has changed the widget resizing
behavior.
All VTE terminal emulators will need new codes to cope with the change
to keep correct window size in GTK+ 3.x

Kind regards
 Wen-Yen Chuang (caleb)

[1] http://lilyterm.luna.com.tw/index_en.html
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkzNNH8ACgkQdEpXpumNYVmFqgCeMpfHQqbgAPAxB1RJ494HAA2U
dq4An1n9m6BMnKZUgNki1/Gxm0h/2Zva
=T1M7
-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/4ccd347f.2040...@calno.com

Re: RFS: morse (New upstream release)

[Nanakos Chrysostomos]

Thanks.



On 31 Οκτ 2010, at 3:44, Theppitak Karoonboonyanan   
wrote:



On Sun, Oct 31, 2010 at 12:35 AM, Nanakos Chrysostomos
 wrote:
I agree in the most part. I have added the suggested changelog  
entries

and reuploaded the package to mentors. I hope this is fine now.


Uploaded. I've wrapped the changelog to 80 columns before that,
to get rid of lintian warning.

Cheers,
--
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/


--
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/aanlktik9paqehd4agxhpszaftd5ckvb3hlwhu1ogj...@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/5896240e-e2c7-4602-8954-e96c00381...@wired-net.gr

Re: Open RFS lacking (further) response

[Charles Plessy]

Le Sat, Oct 30, 2010 at 09:59:45PM +0200, Michael Tautschnig a écrit :
> 
> I think this is a superb step in the right direction; while clearly the list 
> on
> mentors.debian.net, as suggested in another email in this thread, is the more
> comprehensive list of packages in need of sponsorship, this web page is a 
> proper
> list of RFS needing attention.

Hi all,

I just read a post on Planet Debian about pull requests:

http://ondrejcertik.blogspot.com/2010/10/git-has-won.html
http://help.github.com/pull-requests/

RFS has something similar in concept to pull requests. How about including in
the RFS emails a link to the most relevant diff in the web interface of the VCS
where the package is stored ? This will help to have the changes seen by many
eyes.

Cheers,

-- 
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/20101031083042.gb11...@merveille.plessy.net

Re: RFS: ovito

[Michael Tautschnig]

Hi again,

[...]

> 
> > I did't do much checking to see where you got it from, but you might
> > want to update the debian/watch file as well.
> 
> Actually I believe the debian/watch should work as it is.  That is my
> first debian/watch file, though, so I'd like to ask you to double
> check it if there is not too much trouble.
> 

Oh, of course it does work - I had just thought you downloaded a ready-made
archive from some other location, but ...

> The upstream source CMake scripts have a bug: the source doesn't
> compile without the .svn directories.  So, in the first version I used
> 'svn checkout' to download the source instead of 'svn export'.  In
> current version the source tree is clean, and I patched the CMake
> scripts to work without .svn dirs (and informed the upstream author).
> AFAIK the watch file is still tracking the next tagged release.
> 

... as you explained here, this is not the case. I had already noticed that you
needed to do some patching. You might want to ask upstream whether they wouldn't
even want to release such archives themselves instead of asking people to do svn
checkouts.

> > Sure, that's ok. But I'm pretty sure the next version (with a fixed
> > copyright file and possibly an updated debian/watch file) is ready
> > to be uploaded, so please switch over to your desired final version.
> 
> Wow, that was easier than I expected.  The version 0.9.2-1 is now
> uploaded in mentors.d.n.  I cleaned the 0.9.2-1~n versions away from
> the changelog.
> 

Built & uploaded (but will have to wait in NEW, probably until release of
squeeze).

I'd like to point you to [1] - if you'd have some time, it would be great if you
could also help others to get their packages reviewed and sponsored. Meanwhile
there have been new RFS sent to the list [2][3] which might be worth taking.

Thanks a lot for your contribution,
Michael

[1] http://lists.debian.org/debian-mentors/2010/10/msg00478.html
[2] http://lists.debian.org/debian-mentors/2010/10/msg00490.html
[3] http://lists.debian.org/debian-mentors/2010/10/msg00491.html



pgpoTBV1cRJdp.pgp
Description: PGP signature

Re: [Pkg-mozext-maintainers] RF[CS]: ubiquity (mozilla extension) in Debian

[Michael Tautschnig]

Hi Gabriele,

> On 10/31/2010 01:00 AM, Benjamin Drung wrote:
> > I did a quick review:
> > 
> > 1) Please rename the source package to ubiquity-extension (or
> Done
> 

Thank you for not making another flamefest out of that one.

[...]

> 
> > 3) "${xpi:Recommends} (>= 3.6)" doesn't work, because multiple items
> > could be generated. If you want versioned Recommends, mozilla-devscripts
> > needs to be adjusted.
> It generates "Recommends: iceweasel (>= 3.6)" which seems to be ok. What
> multiple items do you mean in this case?
> 

${xpi:Recommends} could have expanded to something like iceweasel, foo, bar - in
which case you'd end up with iceweasel, foo, bar (>= 3.6). As you only expect
iceweasel in there (otherwise this version doesn't make sense) you should just
say so instead of using a substvar.

[...]

Best regards,
Michael



pgpJlVRizRyRZ.pgp
Description: PGP signature