Processed: owner 666243, owner 663916

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Let's try again, now that #681853 is fixed:
> owner 666243 !
Bug #666243 [sponsorship-requests] RFS: peg/0.1.9-1 [ITP] -- recursive-descent 
parser generators for C
Owner recorded as Jakub Wilk .
> owner 663916 !
Bug #663916 [sponsorship-requests] RFS: phonetisaurus/0.4-1 [ITP] -- Grapheme 
to Phoneme conversion tool
Owner recorded as Jakub Wilk .
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
663916: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663916
666243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.134268199611504.transcr...@bugs.debian.org

Bug#663916: RFS: phonetisaurus

[Giulio Paci]

Hi Bart!

On 19/07/2012 07:23, Bart Martens wrote:
> I see that you updated the package at mentors around 24 June 2012, but the
> package is no longer there.  What happened ?


It happened that I contacted Jakub Wilk that is wishing to review and to
sponsor both openfst and phonetisaurus. I published the git repositories
on collab-maint and we are using them to keep track of the latest
updates (openfst packages expecially are big and it would be a waste of
time and resources to upload them on mentors).

The latest version of phonetisaurus is available at:
git://git.debian.org/git/collab-maint/phonetisaurus.git

You can browse sources at:
http://anonscm.debian.org/gitweb/?p=collab-maint/phonetisaurus.git

Bests,
Giulio.


-- 
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/5007d892.50...@gmail.com

Bug#666243: RFS: peg/0.1.9-1 [ITP] -- recursive-descent parser generators for C

[Jakub Wilk]

* Giulio Paci , 2012-07-19, 04:09:

The current version appears to be at:
http://mentors.debian.net/debian/pool/main/p/peg/peg_0.1.9-1.dsc

I updated it.

In addition to your recommendations I also changed section from "misc" 
to "devel".


Very well.

The examples directory could act as a test suite. Please run it at 
build time.

Done.


Please honour DEB_BUILD_OPTIONS=nocheck.

In my opinion, the long description is a bit too… long. I would remove 
at least the citation, maybe something more, but I'm not sure what. 
You might want to ask debian-l10n-english@ for an advice.
I removed most of the description, using *yacc packages as reference. 
It seems more readable now.


That's better. You probably want to add a new line (escaped with a dot), 
between "it." and "Unlike". Otherwise, they'll be considered a single 
logical line.


I always feel uneasy about “Forwarded: not-needed” patches. I believe 
parts of makefile_configuration.patch could be forwarded upstream, and 
the rest of the logic could be moved to debian/rules


In this case "Forwarded: not-needed" means that upstream changed its 
building scheme completely internally,


Fair enough.


-PREFIX = /usr/local
+PREFIX = /usr

Could be overridden in debian/rules.
As far as I know I should either move the binaries by hand or patch the 
Makefile so that ?= is used in place of =. Is there any other solution?


You can keep "=":

":=" assignments can't be overridden;
"=" assignments can be overridden by "make VARIABLE=new-value".
"?=" assignments can be overridden by environment variables or by "make 
VARIABLE=new-value".



%.peg-c : %.peg compile.c
-   ./peg -o $@ $<
+   #./peg -o $@ $<

leg.o : leg.c

leg.c : leg.leg compile.c
-   ./leg -o $@ $<
+   #./leg -o $@ $<

Hmm, why?


Because otherwise the compilation fails if the directory is clean, but 
compile.c or .leg/.peg files have a more recent timestamp than the 
target.


So that shouldn't normally happen, unless someone modified *.leg/*.peg 
stuff. But in the latter case, the person wants either the .c files 
updated, or at least be notified that this cannot be done automatically.


These instructions are only useful when developing peg and leg and are 
safe to skip.


The great thing about free software, is that everybody can develop it, 
including Debian users. So let's not make that harder than necessary. :)


--
Jakub Wilk


--
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/20120719114126.gb4...@jwilk.net

Processed: Re: RFS: sstp-client/1.0.7 [ITP]

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package sponsorship-requests
Limiting to bugs with field 'package' containing at least one of 
'sponsorship-requests'
Limit currently set to 'package':'sponsorship-requests'

> severity 671492 wishlist
Bug #671492 [sponsorship-requests] RFS: sstp-client/1.0.7 [ITP]
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
671492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.13426987261401.transcr...@bugs.debian.org

Processed: re: RFS: bilibop/0.3.3 (ITP #675467)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 675532 wishlist
Bug #675532 [sponsorship-requests] RFS: bilibop/0.3.3 (ITP #675467)
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
675532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.13426988791824.transcr...@bugs.debian.org

Processed: RFS for new package should have severity: wishlist

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> package sponsorship-requests
Limiting to bugs with field 'package' containing at least one of 
'sponsorship-requests'
Limit currently set to 'package':'sponsorship-requests'

> severity 676408 wishlist
Bug #676408 [sponsorship-requests] RFS: fusiondirectory/1.0.3-1 ITP -- 
FusionDirectory is web  interface, designed to handle LDAP based network 
infrastructures.
Severity set to 'wishlist' from 'normal'
> severity 680544 wishlist
Bug #680544 [sponsorship-requests] RFS: muffin/1.0.3-1 [ITP]
Severity set to 'wishlist' from 'normal'
> severity 680546 wishlist
Bug #680546 [sponsorship-requests] RFS: cinnamon/1.4+up3+repack-1 [ITP]
Severity set to 'wishlist' from 'normal'
> severity 681167 wishlist
Bug #681167 [sponsorship-requests] RFS: cellml-api/20120711-1
Severity set to 'wishlist' from 'normal'
> severity 681444 wishlist
Bug #681444 [sponsorship-requests] RFS: grive/0.2.0-1 [ITP #675310]
Severity set to 'wishlist' from 'normal'
> severity 681933 wishlist
Bug #681933 [sponsorship-requests] RFS: boogiewoogie/0.9-1 [ITP] -- Reads and 
stores graphics from iMPROV's Boogie Board
Severity set to 'wishlist' from 'normal'
> severity 681968 wishlist
Bug #681968 [sponsorship-requests] RFS: scscp-imcce/0.6.4+ds-1 [ITP] -- IMCCE 
SCSCP C Library
Severity set to 'wishlist' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
676408: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676408
680544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680544
680546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680546
681167: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681167
681444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681444
681933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681933
681968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.13426999087508.transcr...@bugs.debian.org

how to upgrade from sqeeze to wheezy?

[vykuntam srinivas]

hi,friends.
i am using sqeeze now and i want to move to wheezy.I have googled it and
find so many answers,but i  have installed some non free softwares in my
SQUEEZE . I think that it may give problems at time of upgrade.I am pasting
sources.list

deb-src http://security.debian.org/ squeeze/updates main
> deb http://security.debian.org/ squeeze/updates main contrib non-free
> deb http://mozilla.debian.net/ squeeze-backports iceweasel-release
>
> #backports
> deb http://backports.debian.org/debian-backports squeeze-backports main
> deb http://backports.debian.org/debian-backports squeeze-backports main
> contrib non-free
>
> #mirror
> deb http://ftp.us.debian.org/debian squeeze main contrib non-free
>
> #multimedia
> deb ftp://ftp.deb-multimedia.org squeeze main non-free
>




can any one please brief the upgrade process?

Re: freeze policy - open requests for sponsorship

[Thibaut Paumard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Le 19/07/12 15:15, Thibaut Paumard a écrit :
> user sponsorship-reque...@packages.debian.org usercategory
> wheezy-status * Wheezy Status [tag=] + Intended for Wheezy
> [for-wheezy] + Not Intended for Wheezy [not-for-wheezy] + Fit for
> Wheezy [fit-for-wheezy] + Not Fit for Wheezy [not-fit-for-wheezy] +
> Uncategorized [] usercategory wheezy-view * status * wheezy-status 
> * severity thanks
> 

I think this is better:

user sponsorship-reque...@packages.debian.org
usercategory wheezy-intention
 * Wheezy Status [tag=]
   + Intended for Wheezy [for-wheezy]
   + Not Intended for Wheezy [not-for-wheezy]
   + No Intention Stated []
usercategory wheezy-fitness
 * Wheezy Fitness [tag=]
   + Fit for Wheezy [fit-for-wheezy]
   + Not Fit for Wheezy [not-fit-for-wheezy]
   + Unreviewed for Wheezy Fitness []
usercategory wheezy-bilevel
 * status
 * wheezy-intention
 * wheezy-fitness
 * severity
thanks

This way, bugs are sorted
 1- by status (Outstanding/Resolved), as usual;
 2- then by intention (for-wheezy, not-for-wheezy, unstated);
 3- then by fitness for Wheezy (fit-for-wheezy, not-fit-for-wheezy,
unstated)
 4- then by severity.

Check it out on:

http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sponsorship-requests;ordering=wheezy-bilevel

You can also try (from my previous experiment):
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=sponsorship-requests;ordering=wheezy-view

I have documented that in
http://wiki.debian.org/Mentors/BTS#Usertags

If consensus is reached (or if noone reacts negatively), I propose to
eventually have wheezy-bilevel become the default BTS view by sending
to control:

user sponsorship-reque...@packages.debian.org
usercategory normal
 * status
 * wheezy-intention
 * wheezy-fitness
 * severity
thanks

Regards, Thibaut.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCAAGBQJQCCBnAAoJEJOUU0jg3ChAnHkP/34m2fYAwMkhfvrDwJKMXchs
Ij/26r6ybk34XSpUg/P2bnIjuZUj4Vp1RpcyWmuwawqU6ZMTYqfMMs5XG3oOlKNj
etD9DIAHnlTrWY/Par6ptBoog2YuKZk0EF1fRPoPKYeHNYd5q6WMJL0GSYX22Rmq
wScfwbBU0x2MyDQI6bX0hT3uO2s25xbZX/8GEDMb0HbsJnmpNvnc1p/IYZsJoxol
bjHwqr7qCe/MI0f3hibChB65hfT35uMU6rfD4vxHJuAASr4YBqJfsyvDNjeZ9JHh
89Cg/siQEKv3iTCPAR4Li4t8ImkrkJCHwP7sfN6i4pZfISUFtTQ0Iq4Y7iaaesHS
gFy43UWzFEpUXwKmqb3h2cMcqQ+T/C89zJA0ElrpDq04sepX4nk9jYETanv7i+wa
TSlY/yXp0SMnQPLwEq4Acoa+6BfgJrNmTOuNqva1PWfLZcSclNPaGimkO1jIe21n
XheIGdCGHVJ2c8GJ+vXVk1kHz+LyyqvWM5L/xr8FyApGKMBh6+xkeKSXRm2ADE4p
Wg+qr+Gbx31Bo3rXBislmNln1Jtb0VxcBgU+DY7KHP0F0StdsUPRsSvVAZrQAsM6
u/O/AJ6PAutSoIBMxO0AxVTTtriWa+RyRlCXKW3M36WJeBMiHSMA2jiQqzGEIqOA
rJ/IUxzeof8w1w/sukld
=Dkhc
-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/50082068.6080...@users.sourceforge.net

Re: how to upgrade from sqeeze to wheezy?

[Alexander Toresson]

Hello Igor,

This looks like it'll upgrade him to unstable, which he may not want to do.

// Alexander

(resent because I forgot to reply to the list too)

On Thu, Jul 19, 2012 at 3:48 PM, Игорь Пашев  wrote:
> Here is my sources.list:
>
> deb http://ftp.fi.debian.org/debian/ testing main non-free contrib
> deb-src http://ftp.fi.debian.org/debian/ testing main non-free contrib
>
> deb http://ftp.fi.debian.org/debian/ unstable main non-free contrib
>
> deb http://www.debian-multimedia.org wheezy main non-free
>
>
> You can replace your entries with these, and command
> apt-get update
> apt-get dist-upgrade
>
> 2012/7/19 vykuntam srinivas :
>> hi,friends.
>> i am using sqeeze now and i want to move to wheezy.I have googled it and
>> find so many answers,but i  have installed some non free softwares in my
>> SQUEEZE . I think that it may give problems at time of upgrade.I am pasting
>> sources.list
>>
>>> deb-src http://security.debian.org/ squeeze/updates main
>>> deb http://security.debian.org/ squeeze/updates main contrib non-free
>>> deb http://mozilla.debian.net/ squeeze-backports iceweasel-release
>>>
>>> #backports
>>> deb http://backports.debian.org/debian-backports squeeze-backports main
>>> deb http://backports.debian.org/debian-backports squeeze-backports main
>>> contrib non-free
>>>
>>> #mirror
>>> deb http://ftp.us.debian.org/debian squeeze main contrib non-free
>>>
>>> #multimedia
>>> deb ftp://ftp.deb-multimedia.org squeeze main non-free
>>
>>
>>
>>
>>
>> can any one please brief the upgrade process?
>
>
> --
> 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/CALL-Q8yscmbBH=axizxpqxq0gosxsjoref4n3+bdomrto6o...@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/CAM9MDpdrKyw3bfHB6vDSqA0SMresQLF1ENj--nyMqmS=nwp...@mail.gmail.com

Re: how to upgrade from sqeeze to wheezy?

[vykuntam srinivas]

Thanks for reply!
No problem, i have commented that line having string "unstable"

On Thu, Jul 19, 2012 at 8:31 PM, Alexander Toresson <
alexander.tores...@gmail.com> wrote:

> Hello Igor,
>
> This looks like it'll upgrade him to unstable, which he may not want to do.
>
> // Alexander
>
> (resent because I forgot to reply to the list too)
>
> On Thu, Jul 19, 2012 at 3:48 PM, Игорь Пашев 
> wrote:
> > Here is my sources.list:
> >
> > deb http://ftp.fi.debian.org/debian/ testing main non-free contrib
> > deb-src http://ftp.fi.debian.org/debian/ testing main non-free contrib
> >
> > deb http://ftp.fi.debian.org/debian/ unstable main non-free contrib
> >
> > deb http://www.debian-multimedia.org wheezy main non-free
> >
> >
> > You can replace your entries with these, and command
> > apt-get update
> > apt-get dist-upgrade
> >
> > 2012/7/19 vykuntam srinivas :
> >> hi,friends.
> >> i am using sqeeze now and i want to move to wheezy.I have googled it and
> >> find so many answers,but i  have installed some non free softwares in my
> >> SQUEEZE . I think that it may give problems at time of upgrade.I am
> pasting
> >> sources.list
> >>
> >>> deb-src http://security.debian.org/ squeeze/updates main
> >>> deb http://security.debian.org/ squeeze/updates main contrib non-free
> >>> deb http://mozilla.debian.net/ squeeze-backports iceweasel-release
> >>>
> >>> #backports
> >>> deb http://backports.debian.org/debian-backports squeeze-backports
> main
> >>> deb http://backports.debian.org/debian-backports squeeze-backports
> main
> >>> contrib non-free
> >>>
> >>> #mirror
> >>> deb http://ftp.us.debian.org/debian squeeze main contrib non-free
> >>>
> >>> #multimedia
> >>> deb ftp://ftp.deb-multimedia.org squeeze main non-free
> >>
> >>
> >>
> >>
> >>
> >> can any one please brief the upgrade process?
> >
> >
> > --
> > 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/CALL-Q8yscmbBH=axizxpqxq0gosxsjoref4n3+bdomrto6o...@mail.gmail.com
> >
>

Bug#681968: RFS: scscp-imcce/0.6.4+ds-1 [ITP] -- IMCCE SCSCP C Library

[Jerome BENOIT]

Dear Mentors:

On 18/07/12 11:22, Thibaut Paumard wrote:

Le 18/07/12 10:40, Jerome Benoit a écrit :

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "scscp-imcce"

[...]


SCSCP stands for Symbolic Computation Software Composibility Protocol.
This protocol is developed by the European project SCIEnce - Symbolic
Computation Infrastructure for Europe: http://www.symbolic-computing.org/


Dear Jérôme,

What about putting your package under collaborative maintenance in by
the Debian Science Team?


I am on my way to do so.

 See:


http://debian-science.alioth.debian.org/debian-science-policy.html

It may then be easier for you to find a sponsor within the team.

I can help you with that (setting up a git repository on alioth and all)


I will have an attentive look before asking.


but I can't sponsor you (yet).

Regards, Thibaut.



Sincerely,
Jerome


--
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/50081603.5060...@rezozer.net

Re: Bug#662736: ITP: maxwell -- entropy-gathering daemon

[Antti-Juhani Kaijanaho]

On Wed, Jul 18, 2012 at 10:43:23PM +0200, Martin Eberhard Schauer wrote:
> 
> >Package: wnpp
> >Followup-For: Bug #662736
> >Owner: "Pedro I. Sanchez"
> >
> >Package: wnpp
> >Followup-For: Bug #662736
> >Owner: "Pedro I. Sanchez"
> >
> >Package: wnpp
> >Followup-For: Bug #662736
> >Owner: "Pedro I. Sanchez"
> >
> >Package: wnpp
> >Severity: wishlist
> Hi Pedro,
> 
> if I understand things right, you missed a CC to
> 
> |  cont...@bugs.debian.org
> 
> and a separate line
> 
>thanks
> 
> to make your control commands become effictive.

There are no control commands in that message, and thus CC to
cont...@bugs.debian.org would be inappropriate.  Adding a thanks line would be
unnecessary, for the same reason.

Control commands have the form 
  command bugnumber parameters
all in one line for a single command.  The above lines are pseudo-headers
(unnecessarily repetitive ones) and should not be sent to control@bugs.

By the way, my custom is to never CC control@bugs, instead I tend to BCC it.
That way, any reply-to-all to such a message will not get accidentally copied
to control@.

-- 
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
http://www.flickr.com/photos/antti-juhani/


-- 
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/20120719165004.ga3...@kukkavihko.kaijanaho.fi

Bug#666243: RFS: peg/0.1.9-1 [ITP] -- recursive-descent parser generators for C

[Antti-Juhani Kaijanaho]

On Thu, Jul 19, 2012 at 04:09:25AM +0200, Giulio Paci wrote:
> On 16/07/2012 17:24, Jakub Wilk wrote:
> >> -PREFIX = /usr/local
> >> +PREFIX = /usr
> > 
> > Could be overridden in debian/rules.
> 
> As far as I know I should either move the binaries by hand or patch the
> Makefile so that ?= is used in place of =. Is there any other solution?

You can override Makefile variables on the make command line.  Thus,

$(MAKE) PREFIX=/usr

overrides PREFIX for the duration of that call to make.

-- 
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
http://www.flickr.com/photos/antti-juhani/


--
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/20120719165301.gb3...@kukkavihko.kaijanaho.fi

Re: how to upgrade from sqeeze to wheezy?

[Joachim Wiedorn]

Игорь Пашев wrote on 2012-07-19 17:48:

> You can replace your entries with these, and command
> apt-get update
> apt-get dist-upgrade

Before you do a complete "dist-upgrade" I recommend to upgrade
some essential packages:

  apt-get install debian-keyring debian-archive-keyring
  apt-get install apt apt-utils dpkg aptitude
  apt-get -u install libc6 base-files lsb-base
  apt-get -u install perl perl-base perl-modules bash

  apt-get autoremove

  apt-get -u install grub-pc
  #(or lilo)

  apt-get -u install linux-base linux-image-3.2.0-3-amd64
  #(or similar kernel package)

After rebooting you computer you can start:

  apt-get dist-upgrade

---
Have a nice day.

Joachim (Germany)


--
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/20120719194820.4336f...@jupiter.home

Bug#660955: RFS: gcc-4.6-doc-non-dfsg

[Samuel Bronson]

On Thu, Jul 19, 2012 at 1:32 AM, Bart Martens  wrote:
> retitle 619933 RFP: gcc-4.6-doc -- documentation for the GNU compilers (gcc, 
> gobjc, g++)
> retitle 656044 RFP: gcc-4.6-doc -- documentation for the GNU compilers (gcc, 
> gobjc, g++)
> noowner 619933
> stop
>
>
> Hello Samuel,
>
> The package at mentors is no longer there, so there is currently no package to
> sponsor.  Also, I don't remember receiving an answer to my question.  So I
> guess you're no longer working on this package.

I got kind of overwhelmed by two things:

1. How to manage the non-GCC-version-specific packages that are,
nevertheless, built as part of one of the gcc-X.Y-doc[-non-dfsg]
packages.

2. How to make the packages built from gcc-doc-defaults track the
gcc-defaults packages; that is, how to make them pull in the right doc
packages on every architecture

If you actually want to take a look, I believe I've pushed all my code
to .


-- 
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/cajyzjmdci_eq206_zyu-w9ygeilu9xw-t7ozjeg+ngndh1p...@mail.gmail.com

Bug#666243: RFS: peg/0.1.9-1 [ITP] -- recursive-descent parser generators for C

[Giulio Paci]

On 19/07/2012 18:53, Antti-Juhani Kaijanaho wrote:
> On Thu, Jul 19, 2012 at 04:09:25AM +0200, Giulio Paci wrote:
>> On 16/07/2012 17:24, Jakub Wilk wrote:
 -PREFIX = /usr/local
 +PREFIX = /usr
>>>
>>> Could be overridden in debian/rules.
>>
>> As far as I know I should either move the binaries by hand or patch the
>> Makefile so that ?= is used in place of =. Is there any other solution?
> 
> You can override Makefile variables on the make command line.  Thus,
> 
>   $(MAKE) PREFIX=/usr
> 
> overrides PREFIX for the duration of that call to make.
> 

Thank you for your hint. I just re-uploaded peg package using this
strategy (thus reducing the Makefile patch size).

Bests,
Giulio.


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

Bug#666243: RFS: peg/0.1.9-1 [ITP] -- recursive-descent parser generators for C

[Giulio Paci]

On 19/07/2012 13:41, Jakub Wilk wrote:
> * Giulio Paci , 2012-07-19, 04:09:
>>> The examples directory could act as a test suite. Please run it at
>>> build time.
>> Done.
> 
> Please honour DEB_BUILD_OPTIONS=nocheck.

Fixed.

> That's better. You probably want to add a new line (escaped with a dot),
> between "it." and "Unlike". Otherwise, they'll be considered a single
> logical line.

Done.

> You can keep "=":
> 
> ":=" assignments can't be overridden;
> "=" assignments can be overridden by "make VARIABLE=new-value".
> "?=" assignments can be overridden by environment variables or by "make
> VARIABLE=new-value".

Thank you very much: this is a very clear and useful explanation.

 %.peg-c : %.peg compile.c
 -   ./peg -o $@ $<
 +   #./peg -o $@ $<

 leg.o : leg.c

 leg.c : leg.leg compile.c
 -   ./leg -o $@ $<
 +   #./leg -o $@ $<
>>> Hmm, why?
>>
>> Because otherwise the compilation fails if the directory is clean, but
>> compile.c or .leg/.peg files have a more recent timestamp than the
>> target.
> 
> So that shouldn't normally happen, unless someone modified *.leg/*.peg
> stuff. But in the latter case, the person wants either the .c files
> updated, or at least be notified that this cannot be done automatically.
> 
>> These instructions are only useful when developing peg and leg and are
>> safe to skip.
> 
> The great thing about free software, is that everybody can develop it,
> including Debian users. So let's not make that harder than necessary. :)

It happens 1) when you retrieve files from VCS systems or 2) when you
need to patch one of those files (it was required in a previous version
of the package).
I think the benefit to allow users developing peg/leg using the Debian
package sources does not compensate the trouble it gives to Debian
maintainers using a VCS.
I agree that a proper patch allowing peg/leg development and building
from scratch would be better, but I have no time for this.

Bests,
Giulio.


-- 
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/5008597a.10...@gmail.com

Re: freeze policy - open requests for sponsorship

[Bart Martens]

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.

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

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

Processed: tagging as pending bugs that are closed by packages in NEW

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Thursday 19 July  20:03:07 UTC 2012
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: fractalnow
> tags 677239 + pending
Bug #677239 [sponsorship-requests] RFS: fractalnow/0.8.1-1 [ITP #673395] -- 
Fast, advanced fractal generator
Added tag(s) pending.
> # Source package in NEW: fractalnow
> tags 673395 + pending
Bug #673395 [wnpp] ITP: fractalnow -- Fast, advanced fractal generator
Added tag(s) pending.
> # Source package in NEW: libregexp-debugger-perl
> tags 681944 + pending
Bug #681944 [wnpp] ITP: libregexp-debugger-perl -- Perl module providing 
interactive run-time visualizations of regular expressions
Added tag(s) pending.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
673395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673395
677239: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677239
681944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
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/handler.s.c.134272819728145.transcr...@bugs.debian.org

Backporting a multi-arched package

[Martin Eberhard Schauer]

Hi,

I contributed updated (and new)manpage translations for a
package which had not been updated for ages. Therefore I
would like to provide the German users of (old)stable with
 recent translations.

Last time I made my private backport I had to compile code
extracted from the sources (not part of Squeeze) and install that
package first. It worked on my Squeeze system, but I did not
manage to compile the main package in a pbuilder environment.

Now there is one more problem: I found the changelog entry

 Make $package Multi-Arch: foreign.

As Squeeze is not (?) multiarch-aware, the way to go would
be

   - make the build-dependency available in squeeze-backports,
   - backport the package reversing the multiarch stuff ?

Thank you very much (in advance) for your hints (to multiarch-doc)
and advice,

Martin






--
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/50087c0b.2030...@gmx.de

Bug#666243: RFS: peg/0.1.9-1 [ITP] -- recursive-descent parser generators for C

[Jakub Wilk]

* Giulio Paci , 2012-07-19, 21:01:

It happens 1) when you retrieve files from VCS systems or


Fair enough. (Although I'd rather touch the generated files in 
debian/rules than patch upstream makefile.)


2) when you need to patch one of those files (it was required in a 
previous version of the package).


dpkg-source is supposed to set the same mtime on all patched files, so 
this shouldn't be a problem.


I see the following warnings in the build log:
| 3 combinations of copyright and licensing found.
| WARNING: The following (and possibly more) new or changed notices discovered:
|
|  debian/patches/1001_manpage_fixes.patch
|  debian/patches/2001_makefile_configuration.patch
|  debian/patches/2002_examples_fixes.patch
|  debian/peg.links
|
| To fix the situation please do the following:
|   1) Fully compare debian/copyright_hints with debian/copyright_newhints
|   2) Update debian/copyright as needed
|   3) Replace debian/copyright_hints with debian/copyright_newhints

Please update format URI in debian/copyright.

Lintian says: P: peg: no-upstream-changelog
I see that upstream does maintain a changelog on the project's website. 
You could ask him to include it in the future tarballs.


--
Jakub Wilk


--
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/20120719223704.ga2...@jwilk.net

RFS: libnet 1.1.6 (try #2)

[Stefanos Harhalakis]

Dear mentors,

Can someone please upload the new version of libnet to unstable?

It is usually uploaded by Nelson A. de Oliveira but he's experiencing some 
technical difficulties so I'm asking here instead.

In short the changes are:
* Packaging of new upstream release (1.1.6)
* Compile with -Werror
* Multiarch (for libnet1 and libnet1-dbg)
* Remove libnet.la
* Remove .dirs files
* Clean debian/changelog

The package is in mentors:
- http://mentors.debian.net/package/libnet
- http://mentors.debian.net/debian/pool/main/libn/libnet/libnet_1.1.6-1.dsc

AFAIKT it's lintian clean.

I'm not subscribed to the list so please CC me.

Thanks,
Stefanos

Re: automatic removal of packages from mentors

[Asheesh Laroia]

On Thu, 19 Jul 2012, Bart Martens wrote:


Hi supp...@mentors.debian.net,

I understand that packages must be removed from mentors, because disk 
space is not infinite.  I have heard from multiple people requesting 
sponsorship that one of the reasons to remove packages is that no 
sponsor was found within 20 weeks.  However, some of the removed 
packages have an open RFS with recent comments.  Can you send a copy of 
the automatic notification to the RFS ?  Can you also check the age of 
the most recent comment on the RFS before removing the package ? Also, 
it would be nice that packages for which the packager does not respond 
to review comments within a reasonable time are removed first, so that 
packages waiting for a first review can remain at mentors for a bit 
longer than 20 weeks.  Of course, I understand that at some point you 
must also remove packages waiting for a first review due to lack of disk 
space.


Personally, I believe we shouldn't delete these packages from mentors 20 
weeks later.


To archive them out of the UI is something that would make sense to me.

Curious to hear the thoughts of the current mentors.debian.net 
maintainers, especially on the reasoning behind the deletion, so I can 
better understand and see if I can come up with an alternative I like 
more.


I'm typing this quickly, so if it comes out curt, pardon me! I mean to 
also send warm regards to the hard-working people who make 
mentors.debian.net go forward.


-- Asheesh.


--
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/alpine.deb.2.00.1207191944560.13...@rose.makesad.us

Re: Bug#666243: RFS: peg/0.1.9-1 [ITP] -- recursive-descent parser generators for C

[Giulio Paci]

On 20/07/2012 00:37, Jakub Wilk wrote:
> * Giulio Paci , 2012-07-19, 21:01:
>> 2) when you need to patch one of those files (it was required in a
>> previous version of the package).
> 
> dpkg-source is supposed to set the same mtime on all patched files, so
> this shouldn't be a problem.

The fact is that not all the prerequisites are used to build the target,
so you may need to patch compile.c and this patch does not affect
peg.peg-c or leg.c.

> Please update format URI in debian/copyright.

Done.

> Lintian says: P: peg: no-upstream-changelog
> I see that upstream does maintain a changelog on the project's website.
> You could ask him to include it in the future tarballs.

I will.

Bests,
Giulio.


-- 
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/5008a51c.80...@gmail.com

Re: automatic removal of packages from mentors

[Arno Töll]

Hi,

On 20.07.2012 01:47, Asheesh Laroia wrote:
> Curious to hear the thoughts of the current mentors.debian.net
> maintainers, especially on the reasoning behind the deletion, so I can
> better understand and see if I can come up with an alternative I like more.

well, packages consume space and resources. Disk space is not infinite
either. Opening the packages list in the browser already lasts a
substantial amount of time. That's because lots of data needs to be
retrieved for every package listing the more packages are in the database.

I do also wonder what the benefit to keep packages forever would be. 5
months is a lot of time to keep packages around. Packages can be
uploaded any time again, and we try to avoid deleting packages which are
in an active review process (yes, this needs to be improved i.e.
implemented).

Things change in Debian, packages change, packages may need an update
and someone who cares about. But we remove packages which weren't
touched or even sponsored over a long time. This is more of a problem of
Debian's sponsoring process than mentors.debian.net I'd say.




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



signature.asc
Description: OpenPGP digital signature