Re: common source package for use in Debian and Ubuntu

2011-01-18 Thread Raphael Hertzog 
On Tue, 18 Jan 2011, Joachim Wiedorn wrote:
 I want to realize the idea of a debian directory usable for Debian *and*
 Ubuntu. It works with a switch in the clean target of debian/rules:

Great!

 ifeq ($(shell dpkg-vendor --is Ubuntu  echo yes),yes)
   @echo modify changelog and control file for vendor Ubuntu:
   cat debian/control.Ubuntu debian/control
   cat debian/changelog.Ubuntu debian/changelog.base debian/changelog
 else
   @echo modify changelog and control file for vendor Debian:
   cat debian/control.Debian debian/control
   cat debian/changelog.Debian debian/changelog.base debian/changelog
 endif

No so great... see below.

 Now my questions:
 
 1. is this a good way for switching contol file? 
It must switch the maintainer lines because Ubuntu has another policy.

No. Ubuntu doesn't change maintainer fields if the package in Ubuntu
doesn't have modifications compared to Debian. If you do the work to have
all Ubuntu specific changes in common source package there's really no
need to have a different control file.

 2. this way is not the best for the changelog file because every change
in debian/changelog must copied into the both other changelogs. 
Does anyone know a better way ?

Again, the same changelog file is used when there's a common source
package. No customization needed here.

 4. Can I let all Ubuntu changelog parts (beside the very last) inside 
the changelog of Debian? Then changelog.Debian would be unnecessary.

It's quite common to have some bits of Ubuntu history in official Debian
packages... but mainly for packages created by Ubuntu and then integrated
in Debian.

If you want to keep the Ubuntu history now that you create a common source
package, why not. It's up to you I guess.

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/20110118080335.gc31...@rivendell.home.ouaza.com

Re: HOWTO: Source a common shell script between DEBIAN/config and DEBIAN/preinst

2011-01-18 Thread Thomas Goirand 
On 01/18/2011 03:13 PM, harish badrinath wrote:
 Given that i was told that you can deterministically determine which
 file would run first DEBIAN/control _or_ DEBIAN/preinst, I have this
 following query.

 I want to source a common file between these two scripts to ensure
 that  if the package cant automatically detect sane values, it prompt
 the user for input as the last resort. The values given itself are
 trivial in nature, but if not done correctly would make the system
 unusable by locking all the users out of the machine.
   
You know that your scripts can be run non-interactively and that this
is a *strong* requirement of Debian, right?

Thomas Goirand (zigo)


-- 
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/4d3547ae.2030...@debian.org

Re: HOWTO: Source a common shell script between DEBIAN/config and DEBIAN/preinst

2011-01-18 Thread harish badrinath 
On Tue, Jan 18, 2011 at 1:26 PM, Thomas Goirand z...@debian.org wrote:
 On 01/18/2011 03:13 PM, harish badrinath wrote:
 Given that i was told that you can deterministically determine which
 file would run first DEBIAN/control _or_ DEBIAN/preinst, I have this
 following query.
Sorry i was told that you *cannot * deterministically determine
 You know that your scripts can be run non-interactively and that this
 is a *strong* requirement of Debian, right?
In extremely simple terms
Basically if i want to source a file in DEBIAN/control, where should
that file be located ??

 Thomas Goirand (zigo)




-- 
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/AANLkTik4NaTFXZCFyzaHUBZE-548+OOJZeQkm=abr...@mail.gmail.com

Re: HOWTO: Source a common shell script between DEBIAN/config and DEBIAN/preinst

2011-01-18 Thread Roland Mas 
harish badrinath, 2011-01-18 13:00:03 +0530 :

 I want to source a common file between these two scripts 

  You can't be sure that the common file is present on the system when
config runs (since that may be before the package is unpacked).  You
can, however, maintain the common part as a separate file in your source
package and inline it in both files of the generated binary.  A very
ugly implementation of this is in the fusionforge source package, using
an ad-hoc tool I called DSF-Helper (short for Debian SourceForge
helper -- that's how old it is).

Roland.
-- 
Roland Mas

One... two... one, two, many, lots!
  -- Lias, in Soul music (Terry Pratchett)


-- 
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/87y66i1uln@mirexpress.internal.placard.fr.eu.org

Re: RFS: rman (updated package)

2011-01-18 Thread Niels Thykier 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2011-01-17 22:04, Anton Gladky wrote:
 Hi, Niels,
 

Hey

 I have uploaded a new version of rman. Could you not, please, have a look?
 It seems, that I have fixed all issues, which were suggested by you.
 

Sure; I have a question to the realloc replacement.  It seems like your
replacement will be unable to handle if there was not enough memory in
the first iteration.

@@ -4615,10 +4615,10 @@ char *
 filesuck(FILE *in) {
   const int inc=1024*100;  /* [...] */
   int len=0,cnt;
- -  char *file = malloc(1);  /*[...] */
+  char *file;

   do {
- -file = realloc(file, len+inc+1);   /* w[...] */
+file = malloc(len+inc+1);  /* [...] */
 cnt = fread(file[len], 1, inc, in);
 len+=cnt;
   } while (cnt==inc);
- 

I believe the following pattern can be used to solve the original problem.

char *tmp = realloc(file, len + inc + 1);
if(!tmp) { free(file); fail-in-a-sane-way; }
file = tmp;

 I did not sent a patch, which fixes cppcheck warnings,  to upstream as
 those warnings were done by adding gzip-feature to the code (probably,
 maintainer).
 

Admittedly upstream looks rather dead. :)

 Thank you.
 
 Anton
 
 [...]

Also, please change unstable to experimental in the changelog.
Without approval from the Release Team we cannot upload to unstable this
deep in a freeze.  It can easily be re-uploaded to unstable when the
freeze is over.

There are also a couple of Lintian info tags.  About the no-doc-base I
think it is related to the removal of d/rman.doc-base.manual (though
honestly I did not check your binary package with Lintian the last
time).  Note these are only emitted by Lintian with the extra flags (-I
in the particular case), since they are more pedantic or less serious
than other tags.

I: rman: possible-documentation-but-no-doc-base-registration
I: rman: spelling-error-in-manpage usr/share/man/man1/rman.1.gz
extention extension
I: rman: example-wrong-path-for-interpreter
./usr/share/doc/rman/examples/hman.cgi (#!/usr/bin/ksh != /bin/ksh)
I: rman: example-wrong-path-for-interpreter
./usr/share/doc/rman/examples/hman.ksh (#!/usr/bin/ksh != /bin/ksh)
I: rman: example-wrong-path-for-interpreter
./usr/share/doc/rman/examples/man2html (#!/usr/bin/ksh != /bin/ksh)


I think that is about it. :)

~Niels

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

iQIcBAEBCAAGBQJNNWEOAAoJEAVLu599gGRC3dQQAKz9iGQyCJSMVF+51F8j+lwq
bpARdvr/O/Sj/YRDdkdqKHPID61klXHMRla/GKxnNBRoDCbDJE6R+VCLouUmTXwF
u1Bvwo7tOX1S4dNv+tf9IEZ30nLgvUDWjRKTC1bi308wSdxnElEwT+ec2hK0o942
X5n4i7761C3/vBdI9r9NeA1A77EAJDTlAozyG/zcPUTQ+tUFW6HUMFP4lCsU4ZE2
mnrUb9T6+yufs84ldmRW3FdLOKukX0bBHEVB+pDy4W114kKkG3AC/BzyytS15gGR
/6E8A5LmXH01VPIVLpqs5Xdu5lqni8bDsAWJM6lIMpY7oFPP+rR4DH0jwvcpuE5q
QTg24yuMHriWb8XMOfoaDcgqAR5Tm+1P22NU+bRfeLF0Bzo/hlggG5Lrp56m7dqe
MEV1oc68yulMCcMPBfQp0r86cXxzMnaPtf4SxA3gHesGFvb8r/qS47unnwfJZJpv
pvh/k9zWHA1C08nkhrSkn8XWthdAXg/3bYj7PdGuzYAEwJMQAMbPVHiFvGnFi0Vi
umLNfZTnmg0Fj+6JQ9nvpzL/YIwy4GxUpi6f53YHekhhkX8vcy71OrN+rlGV2Qkz
KcCDonqo9CctSqLO5lTDTucJTLZQI3qBvG4B0jk4aXrOlC5aLnYKbiH1LHRSu9fF
l9IFOzascmvgjaLk3FcC
=GjPn
-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/4d35610f.6050...@thykier.net

Re: RFS: rman (updated package)

2011-01-18 Thread Anton Gladky 
Hi, Niels,

I have re-uploaded that.

Thanks.

Anton




On Tue, Jan 18, 2011 at 10:44 AM, Niels Thykier ni...@thykier.net wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 On 2011-01-17 22:04, Anton Gladky wrote:
 Hi, Niels,


 Hey

 I have uploaded a new version of rman. Could you not, please, have a look?
 It seems, that I have fixed all issues, which were suggested by you.


 Sure; I have a question to the realloc replacement.  It seems like your
 replacement will be unable to handle if there was not enough memory in
 the first iteration.

 @@ -4615,10 +4615,10 @@ char *
  filesuck(FILE *in) {
   const int inc=1024*100;      /* [...] */
   int len=0,cnt;
 - -  char *file = malloc(1);  /*[...] */
 +  char *file;

   do {
 - -    file = realloc(file, len+inc+1);   /* w[...] */
 +    file = malloc(len+inc+1);  /* [...] */
     cnt = fread(file[len], 1, inc, in);
     len+=cnt;
   } while (cnt==inc);
 - 

 I believe the following pattern can be used to solve the original problem.

 char *tmp = realloc(file, len + inc + 1);
 if(!tmp) { free(file); fail-in-a-sane-way; }
 file = tmp;

 I did not sent a patch, which fixes cppcheck warnings,  to upstream as
 those warnings were done by adding gzip-feature to the code (probably,
 maintainer).


 Admittedly upstream looks rather dead. :)

 Thank you.

 Anton

 [...]

 Also, please change unstable to experimental in the changelog.
 Without approval from the Release Team we cannot upload to unstable this
 deep in a freeze.  It can easily be re-uploaded to unstable when the
 freeze is over.

 There are also a couple of Lintian info tags.  About the no-doc-base I
 think it is related to the removal of d/rman.doc-base.manual (though
 honestly I did not check your binary package with Lintian the last
 time).  Note these are only emitted by Lintian with the extra flags (-I
 in the particular case), since they are more pedantic or less serious
 than other tags.

 I: rman: possible-documentation-but-no-doc-base-registration
 I: rman: spelling-error-in-manpage usr/share/man/man1/rman.1.gz
 extention extension
 I: rman: example-wrong-path-for-interpreter
 ./usr/share/doc/rman/examples/hman.cgi (#!/usr/bin/ksh != /bin/ksh)
 I: rman: example-wrong-path-for-interpreter
 ./usr/share/doc/rman/examples/hman.ksh (#!/usr/bin/ksh != /bin/ksh)
 I: rman: example-wrong-path-for-interpreter
 ./usr/share/doc/rman/examples/man2html (#!/usr/bin/ksh != /bin/ksh)


 I think that is about it. :)

 ~Niels

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

 iQIcBAEBCAAGBQJNNWEOAAoJEAVLu599gGRC3dQQAKz9iGQyCJSMVF+51F8j+lwq
 bpARdvr/O/Sj/YRDdkdqKHPID61klXHMRla/GKxnNBRoDCbDJE6R+VCLouUmTXwF
 u1Bvwo7tOX1S4dNv+tf9IEZ30nLgvUDWjRKTC1bi308wSdxnElEwT+ec2hK0o942
 X5n4i7761C3/vBdI9r9NeA1A77EAJDTlAozyG/zcPUTQ+tUFW6HUMFP4lCsU4ZE2
 mnrUb9T6+yufs84ldmRW3FdLOKukX0bBHEVB+pDy4W114kKkG3AC/BzyytS15gGR
 /6E8A5LmXH01VPIVLpqs5Xdu5lqni8bDsAWJM6lIMpY7oFPP+rR4DH0jwvcpuE5q
 QTg24yuMHriWb8XMOfoaDcgqAR5Tm+1P22NU+bRfeLF0Bzo/hlggG5Lrp56m7dqe
 MEV1oc68yulMCcMPBfQp0r86cXxzMnaPtf4SxA3gHesGFvb8r/qS47unnwfJZJpv
 pvh/k9zWHA1C08nkhrSkn8XWthdAXg/3bYj7PdGuzYAEwJMQAMbPVHiFvGnFi0Vi
 umLNfZTnmg0Fj+6JQ9nvpzL/YIwy4GxUpi6f53YHekhhkX8vcy71OrN+rlGV2Qkz
 KcCDonqo9CctSqLO5lTDTucJTLZQI3qBvG4B0jk4aXrOlC5aLnYKbiH1LHRSu9fF
 l9IFOzascmvgjaLk3FcC
 =GjPn
 -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/4d35610f.6050...@thykier.net




--
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/AANLkTikvPOotnozNF=q69_shoj2aeksbw2npn-y-s...@mail.gmail.com

Re: RFS: openteacher

2011-01-18 Thread Arvind S Raj 
On Mon, Jan 17, 2011 at 1:11 PM, Andreas Tille andr...@an3as.eu wrote:

 [Arvind, I hope you don't mind if I publish quotes from your private
  mail to the public list.  I do not really consider the information very
  private and it is important to share the information.  Otherwise you will
  not get further helpful input of other mentors.]


Not an issue; I will mail the entire list in future.



 On Mon, Jan 17, 2011 at 09:00:50AM +0530, Arvind S Raj wrote:
  Also do forgive me if I'm asking really stupid questions-it's my first
 ever
  time at packaging and maintaining. Never done it before.

 Sure.  No problem at all.

- #Vcs-*
  - any reason why not just injecting the package to Vcs?  I'm in
 big favour of using team maintenance and thus I would really like
 you to use the Vcs and set the Tags accordingly
  
 
  I thought it is sufficient to add the launchpad link since it takes you
 to
  their official page that also has the links to the source.

 The Vcs fields in Debian are used by some applications and thus should be
 properly set.  Launchpad is not used inside applications at any debian.org
 service.

  1. I actually downloaded the source from sourceforge. They do their
 version
  control at launchpad. Do I have to add those links?

 H, I admit I have no idea in how far sourceforge projects can do
 version control at launchpad.  The sense of the Vcs tags in the Debian
 package is to give links where *the* *Debian* *packaging* *stuff* (so
 the content of your debian/ directory) is maintained.  In collab-qa you
 do not keep just another copy of upstream code but you maintain the code
 which is for Debian exclusively and you should NOT maintain the debian/
 directory in the upstream source tree (for several reasons discussed
 several times before).

 When using Git it is a matter of policy if you keep a clone of the
 upstream code or not in collab-qa.  In Svn usually only the debian/
 directory is kept.

  2. They use bzr for version control and so when I add the line Vcs-Bzr:
 bzr
  branch lp:openteacher, it highlights bzr branch lp:openteacher in red.
 Is
  there anything wrong in the way I specified the bzr branch?

 I further admit that I have no idea about bzr.  If you want me to
 sponsor openteacher I would like to ask you to stick to SVN or Git for
 maintaining the debian/ dir.  For the upstream code I do not need to
 access the Vcs directly because only the tarball is used I do not care
 at all about the Vcs.


Their development happens in launchpad but they release new source packages
in sourceforge-at least the new version was released there. *Also, a new
version was released-2.0. It's no longer in beta. So, I will be packaging
that from scratch now.*


 
- long description: nitpicking mode onPlease do not add newlines
 inbetween each single item, using two spaces in the beginning of a
 line is sufficient to get the wanted pacing.  It might disturb the
 rendering in some applicationsnitpicking mode off
 
  Done; do take a look if the present changes are sufficient once I've
  uploaded. I've also changed the description a bit.

 If you would decide for a Vcs location at Alioth I could have a look...


I have registered a project under the name openteacher at alioth. Awaiting
review of the administrators.


  What do I add in the watch file? I assumed that upstream sources are
 always
  in the archive format so what can I watch?

 Try

   man uscan

 In Debian there exist tools to scan upstream websites for new releases
 to inform the maintainer that he needs to package this new version.


I will update the watch page in the new packaging that I will upload soon as
I have created uploaded debian/ to alioth.



   debian/opentecher.1: Manpage needs to be installed
  What did you mean by needs to be installed? I didn't get you.

 $ lintian openteacher_2.0beta2-1_amd64.deb
 W: openteacher: binary-without-manpage usr/bin/openteacher

 To fix this you want to add a file

  debian/manpages

 with the content

 debian/openteacher.1

 (see man dh_installman) to make sure that the manpage you provided is
 actually moved to the package.

 Hope this helps

   Andreas.

 --
 http://fam-tille.de




-- 
Arvind S Raj

Re: RFS: openteacher

2011-01-18 Thread Arvind S Raj 
Hello,
What should preferably be used for packaging-the sources from sourceforge
and the stable bazaar branch maintained at launchpad?

-- 
Arvind S Raj

Atrakcyjne ceny przesylek kurierskich

2011-01-18 Thread Polska Korporacja Wydawcow i Dystrybutorow 
Szanowni Państwo,
 
W związku  z ustawą z dnia 18 lipca 2002 roku o świadczeniu usług drogą 
elektroniczną (dz.U.nr144 z 9 września 2002 r.,poz1204), prosimy o wyrażenie 
zgody na przesłanie drogą elektroniczną oferty dotyczącej:
 
DYSTRYBUCJI KRAJOWYCH I ZAGRANICZNYCH PRZESYŁEK KURIERSKICH
 
Polska Korporacja Wydawców i Dystrybutorów jest największym pośrednikiem usług 
kurierskich w Polsce.
 
Chcemy zaproponować usługi kilku najlepszych i najbardziej znanych firm 
kurierskich oferując bardzo atrakcyjne warunki współpracy.
 
Nasi klienci decydując się na współpracę z nami zyskują:
- atrakcyjne warunki cenowe,
- możliwość korzystania wg potrzeby z kilku firm kurierskich jednocześnie,
- stałą opiekę przedstawiciela handlowego,
- stałą opiekę pracownika w naszym Dziale Obsługi Klienta (nie trzeba 
kontaktować się z firmami kurierskimi),
- jedną fakturę zbiorczą (bez względu na ilość obsługujących firm kurierskich),
- program do drukowania listów przewozowych,
 
Jeżeli wyrażacie Państwo zgodę na przesłanie oferty, prosimy o kliknięcie w 
poniższy link:

TAK, jestem zainteresowany (a) ofertą
w odpowiedzi proszę podać dane kontaktowe:
nazwa firmy, nazwisko i imię, telefon kontaktowy, ilość paczek/palet wysyłanych 
w skali miesiąca.

Jeżeli nie wyrażacie Państwo zgody, prosimy o kliknięcie w poniższy link:
 
NIE jestem zainteresowany(a)

Z wyrazami szacunku
Dział Handlowy
Polska Korporacja Wydawców i Dystrybutorów
ul. Księżycowa 1, 01-934 Warszawa
www.pkwid.com.pl
 
Telefony stacjonarne:
(22) 896 91 35, (22) 896 91 36, (22) 896 91 37,
(22) 896 91 38, (22) 896 91 39, (22) 663 00 16,
(22) 663 00 53.

Re: RFS: openteacher

2011-01-18 Thread Andreas Tille 
On Tue, Jan 18, 2011 at 06:35:42PM +0530, Arvind S Raj wrote:
 
 Their development happens in launchpad but they release new source packages
 in sourceforge-at least the new version was released there. *Also, a new
 version was released-2.0. It's no longer in beta. So, I will be packaging
 that from scratch now.*

Ahh, that's good.  Hint for the watch file.  You can use SourceForge
redirector which should lock somethink LIKE (the suggestions does NOT
work!!!) this:

version=3
http://sf.net/openteacher/openteacher-(.*)\.tgz

Just use the correct strings here and try

   uscan --verbose

if it fetches the latest upstream.
 
  If you would decide for a Vcs location at Alioth I could have a look...
 
 
 I have registered a project under the name openteacher at alioth. Awaiting
 review of the administrators.

Hmmm, a separate alioth project is most probably real overkill.  Why not
simply using

   Vcs-Git: git://git.debian.org/collab-maint/openteacher.git

(as it was metioned in your debian/control file) or

   Vcs-Svn: svn://svn.debian.org/svn/collab-maint/ext-maint/openteacher/trunk/

if you prefer SVN???  The purpose of collab-maint is described in the Wiki
(sorry, I assumed you know this because it was just in your control file):

   http://wiki.debian.org/CollaborativeMaintenance
   http://wiki.debian.org/Alioth/PackagingProject
 
 I will update the watch page in the new packaging that I will upload soon as

See above for the watch file.

Kind regards

 Andreas.

-- 
http://fam-tille.de


-- 
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/20110118143553.gc16...@an3as.eu

Re: RFS: openteacher

2011-01-18 Thread Andreas Tille 
On Tue, Jan 18, 2011 at 06:43:28PM +0530, Arvind S Raj wrote:
 What should preferably be used for packaging-the sources from sourceforge
 and the stable bazaar branch maintained at launchpad?

You should not maintain the source but just provide some patches for the
simply downloaded released tarball.  So you will not really need a VCS
for the source.

Kind regards

 Andreas.

-- 
http://fam-tille.de


-- 
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/20110118143704.gd16...@an3as.eu

Re: RFS: rman (updated package)

2011-01-18 Thread Niels Thykier 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2011-01-18 12:15, Anton Gladky wrote:
 Hi, Niels,
 
 I have re-uploaded that.
 
 Thanks.
 
 Anton
 
 
 
 
 On Tue, Jan 18, 2011 at 10:44 AM, Niels Thykier ni...@thykier.net wrote:
 On 2011-01-17 22:04, Anton Gladky wrote:
 Hi, Niels,

 
 Hey
 
 I have uploaded a new version of rman. Could you not, please, have a look?
 It seems, that I have fixed all issues, which were suggested by you.

 
 Sure; I have a question to the realloc replacement.  It seems like your
 replacement will be unable to handle if there was not enough memory in
 the first iteration.
 
 @@ -4615,10 +4615,10 @@ char *
  filesuck(FILE *in) {
   const int inc=1024*100;  /* [...] */
   int len=0,cnt;
 -  char *file = malloc(1);  /*[...] */
 +  char *file;
 
   do {
 -file = realloc(file, len+inc+1);   /* w[...] */
 +file = malloc(len+inc+1);  /* [...] */
 cnt = fread(file[len], 1, inc, in);
 len+=cnt;
   } while (cnt==inc);
 
 
 I believe the following pattern can be used to solve the original problem.
 
 char *tmp = realloc(file, len + inc + 1);
 if(!tmp) { free(file); fail-in-a-sane-way; }
 file = tmp;
 
 [...]

Better, but it is still lacking the fail-in-a-sane-way part :)

Right now it will free file and continue, leading to a null pointer
dereference when it calls fread().  You should be able to use

fprintf(stderr, Out of memory\n);
exit(EXIT_FAILURE);

as a sane way to fail.

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

iQIcBAEBCAAGBQJNNbpYAAoJEAVLu599gGRCZuwP/1qlMa4A8+qEFPeVHh5kv057
NTZXxHyLqWcHDy/LHVa/1uDjYglo/dvIuQZgZonUS3rGxJMQhS6UaWzCd8eoKCm0
0Mm7g+Z0+xsy3Kr5ymhtiOYugCf/RKfQLB3iqzWEeOiVUEn2av5XMUvtqmUhfgKk
sgppTKLYLyMOhaHHzgIA9Hl9UYahOZRGOmb0uFYVr5pQQVY8RpfEHn9OZKQvIrJv
IexJI6rESTCXFitp3HidUQZPD2xZhKhLRlGBKxEw+qXtkP3/QAgowb54eXF3f9mE
LNmzbQkHfqQUCIwBplvNvGx9gm91DRgli135U4pJMdXhaWYxZt1SUgQQ6A3xyF4l
Dy3xWzjnasI+gnvlgwuytiBwCbAdFXU3/d1nR7wO59PtdKf8qN3W/1jue0tfBF0N
6hqNWejhsLsD0s6qnPd0cKgqV/KWS0wMqAp17Re0RqdieB7dDSoTMwIsd4QsTXVC
GlCPqZnAddIHwBtxQHsFhzfzmlIAY8vEup+MW3iysp4VJJWR2whwY2/LujNNCiWN
Z3YyEZW/chUnIlwN288e4XCh2MtkfUqtyKdEr2zCxtcmZJid5r3SyXHRsnsE0Mes
F1hFclFIVAqfr7IhYPh4FWOUZlRq7vFH06xTPAGXcFrD7NATFLKmWnFfxSrqhgzB
IvaVsw4oyA7TxiKag89R
=50Rw
-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/4d35ba59.9010...@thykier.net

Re: RFS: pev

2011-01-18 Thread Niels Thykier 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2011-01-16 02:16, Fernando Mercês wrote:
 Niels,
 
 You're right in all points. Thank you for help. I've used the new tool
 for DEP-5 and got no warnings. I've fixed the other issues too.
 
 Please, can you check the package now (already re-uploaded)?
 
 Best regards,
 Fernando Mercês
 Linux Registered User #432779
 www.mentebinaria.com.br
 http://linuxreversing.org
 http://softwarelivre-rj.org
 --
 Participe do I Hack'n Rio, dias 8 e 9 de abril na UFRJ!
 --
 [...]

Hey,

Uploaded, thanks for your contribution and feel free to contact me in
private if you have a new version of pev ready. :)

~Niels

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

iQIcBAEBCAAGBQJNNbyzAAoJEAVLu599gGRCcOwQAJKlf9rl6mv8hY6s+GjC4xAm
sJxh52NSZwBEYEbCVmVqXdn2FaGlpwRpflkuUCHKAQrOAjg9OrEsK3T+OAyylRQs
0G5JkYYQYwmu8qbrGobNvqZsV2oHvzcBasXCjkeECz7u6ao/bYzHsJpbZdFjmIA4
cx5hcm9UbEef9y/d3Mj0PpGdEuXDj2TY7IyBMjbe/GOh/KDtxg+jhNVQgkY1g+4W
PMDIwb1aClnlXCmqRhZvStRYMDPRtapDijycqh07qiDr3oFglySazA0E4DvC/w7j
H2H7FUmEcxTpyyt0eCF0NBsyhg2mekkec0Bmxcavxejbt+P/HJJoxYwRVMjoIU6x
GZeMLZIklk7btNFZ5jcdHowO03Ph3ylQo/ZxqOT5MNAREIIr+LGcMW2aQWcBfjS8
iUqhqvRzohiOlrHTEGDAdM2i2LNnM0dCO5a6q6D9DLLBAthX/FjUl4kcjLWA+EiN
e63rv7vZIRCxVTiIL9jGtt9FvUPkI0oq9CRB7XOy58LLrPSyLFHLEm/rnKSbvJTk
s6D2LE2sg5ec3lFEEG0/PamMKiiTrXks2XNK6U/7ZVk44IUWRzTOaWCT2LAvaXNv
x2wXqoHCS2q/FfJPbVm9DCi1fvFGAt2aU14+pm6E2c+KNXQ4lCnBxfI1G+tAVWVD
vR6hQ2YWiHq4zl0gtlkF
=N51K
-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/4d35bcb3.2000...@thykier.net

Re: RFS: rman (updated package)

2011-01-18 Thread Anton Gladky 
Ups, sorry.

Uploaded.

Anton




On Tue, Jan 18, 2011 at 5:05 PM, Niels Thykier ni...@thykier.net wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 On 2011-01-18 12:15, Anton Gladky wrote:
 Hi, Niels,

 I have re-uploaded that.

 Thanks.

 Anton




 On Tue, Jan 18, 2011 at 10:44 AM, Niels Thykier ni...@thykier.net wrote:
 On 2011-01-17 22:04, Anton Gladky wrote:
 Hi, Niels,


 Hey

 I have uploaded a new version of rman. Could you not, please, have a look?
 It seems, that I have fixed all issues, which were suggested by you.


 Sure; I have a question to the realloc replacement.  It seems like your
 replacement will be unable to handle if there was not enough memory in
 the first iteration.

 @@ -4615,10 +4615,10 @@ char *
  filesuck(FILE *in) {
   const int inc=1024*100;      /* [...] */
   int len=0,cnt;
 -  char *file = malloc(1);  /*[...] */
 +  char *file;

   do {
 -    file = realloc(file, len+inc+1);   /* w[...] */
 +    file = malloc(len+inc+1);  /* [...] */
     cnt = fread(file[len], 1, inc, in);
     len+=cnt;
   } while (cnt==inc);
 

 I believe the following pattern can be used to solve the original problem.

 char *tmp = realloc(file, len + inc + 1);
 if(!tmp) { free(file); fail-in-a-sane-way; }
 file = tmp;

 [...]

 Better, but it is still lacking the fail-in-a-sane-way part :)

 Right now it will free file and continue, leading to a null pointer
 dereference when it calls fread().  You should be able to use

 fprintf(stderr, Out of memory\n);
 exit(EXIT_FAILURE);

 as a sane way to fail.

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

 iQIcBAEBCAAGBQJNNbpYAAoJEAVLu599gGRCZuwP/1qlMa4A8+qEFPeVHh5kv057
 NTZXxHyLqWcHDy/LHVa/1uDjYglo/dvIuQZgZonUS3rGxJMQhS6UaWzCd8eoKCm0
 0Mm7g+Z0+xsy3Kr5ymhtiOYugCf/RKfQLB3iqzWEeOiVUEn2av5XMUvtqmUhfgKk
 sgppTKLYLyMOhaHHzgIA9Hl9UYahOZRGOmb0uFYVr5pQQVY8RpfEHn9OZKQvIrJv
 IexJI6rESTCXFitp3HidUQZPD2xZhKhLRlGBKxEw+qXtkP3/QAgowb54eXF3f9mE
 LNmzbQkHfqQUCIwBplvNvGx9gm91DRgli135U4pJMdXhaWYxZt1SUgQQ6A3xyF4l
 Dy3xWzjnasI+gnvlgwuytiBwCbAdFXU3/d1nR7wO59PtdKf8qN3W/1jue0tfBF0N
 6hqNWejhsLsD0s6qnPd0cKgqV/KWS0wMqAp17Re0RqdieB7dDSoTMwIsd4QsTXVC
 GlCPqZnAddIHwBtxQHsFhzfzmlIAY8vEup+MW3iysp4VJJWR2whwY2/LujNNCiWN
 Z3YyEZW/chUnIlwN288e4XCh2MtkfUqtyKdEr2zCxtcmZJid5r3SyXHRsnsE0Mes
 F1hFclFIVAqfr7IhYPh4FWOUZlRq7vFH06xTPAGXcFrD7NATFLKmWnFfxSrqhgzB
 IvaVsw4oyA7TxiKag89R
 =50Rw
 -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/aanlktikelwc3d3a_4rrwqm4zza84gvdmjf6qg_txi...@mail.gmail.com

Re: would like review of my polipo-tor packaging

2011-01-18 Thread travis+ml-debian-mentors 
On Mon, Jan 17, 2011 at 11:20:29PM -0500, Scott Howard wrote:
 Hello- non-DD review. I haven't built it yet but there are some quick
 cosmetic things to do first:

Thanks so much for the feedback!  I'll look into doing these next time
I get some spare brain cycles.

 Standards-Version: 3.8.4 should be 3.9.1

I used the dh tools to make this, and I've seen debuild complain
about this, but really didn't know what I should be doing in this
case - funny thing is, both tools were up-to-date from teh ubuntu
repo.  Is a text edit in order, or something else need doing?

 I haven't read the details of your package - it seems to install
 configurations and sets up a log directory. I'm not familiar with
 these packages, but is a separate package to set up this configuration
 necessary - or is there a way you can include this functionality in
 existing packages (or maybe add a new binary package to existing
 packages instead of a new source package)?

It basically installs polipo as a prereq, and then sets up a parallel
polipo instance to forward through tor.  This isn't ideal, but allows
debuntu users to avoid having to set them up manually.

I doubt the package will make it into the debian repo, since the
prereqs aren't even there - TOR hasn't gotten their act together
yet.  So not sure if merging everything into one changelog makes
sense yet.  It's certainly been in my repo for a while, and been
through a couple of changes.

Thanks again, and hoping some Debian Devs will look @ it too,
Travis
-- 
Effing the ineffable since 1997. | http://www.subspacefield.org/~travis/
My emails do not usually have attachments; it's a digital signature
that your mail program doesn't understand.
If you are a spammer, please email j...@subspacefield.org to get blacklisted.


pgp6SzDIBcS34.pgp
Description: PGP signature

Re: common source package for use in Debian and Ubuntu

2011-01-18 Thread Joachim Wiedorn 
Raphael Hertzog hert...@debian.org wrote on 2011-01-18 09:03:

 On Tue, 18 Jan 2011, Joachim Wiedorn wrote:
 
  Now my questions:
  
  1. is this a good way for switching contol file? 
 It must switch the maintainer lines because Ubuntu has another policy.
 
 No. Ubuntu doesn't change maintainer fields if the package in Ubuntu
 doesn't have modifications compared to Debian. If you do the work to have
 all Ubuntu specific changes in common source package there's really no
 need to have a different control file.
This is new for me. I took the changes which were made from the Ubuntu
developer who created the Ubuntu package of lilo. But without different
control files it is easier.

  2. this way is not the best for the changelog file because every change
 in debian/changelog must copied into the both other changelogs. 
 Does anyone know a better way ?
 
 Again, the same changelog file is used when there's a common source
 package. No customization needed here.
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?

  4. Can I let all Ubuntu changelog parts (beside the very last) inside 
 the changelog of Debian? Then changelog.Debian would be unnecessary.
 
 It's quite common to have some bits of Ubuntu history in official Debian
 packages... but mainly for packages created by Ubuntu and then integrated
 in Debian.
 
 If you want to keep the Ubuntu history now that you create a common source
 package, why not. It's up to you I guess.
It was a wish of the Ubuntu developer. So I think I can copy the Ubuntu
changelogs in the changelog of the common package.

Thanks for your valuable help.

---
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/20110118210951.61f1f...@jupiter.home

Re: RFS: yade-0.60

2011-01-18 Thread Anton Gladky 
Hi, all!

I have received a valuable advices and suggestions from some
debian-developers (Ansgar Burchardt, Niels Thykier, Jakub Wilk and
others), working on other packages. So I need to modify yade-0.60 to
make it lintian clean completely.

After work is finished, I will reupload yade-0.60.
Thanks
Anton




On Thu, Jan 6, 2011 at 1:48 PM, Anton Gladky gladky.an...@gmail.com wrote:
 Dear mentors,
 I am looking for a sponsor for my package yade-0.60.
 * Package name    : yade-0.60
  Version         : 0.60-1
  Upstream Author : https://launchpad.net/~yade-dev
 * URL             : https://launchpad.net/yade
 * License         : GNU GPL v2
  Section         : x11
 It builds these binary packages:
 yade       - Platform for discrete element modeling.
 yade-0.60  - Platform for discrete element modeling.
 yade-0.60-dbg - Platform for discrete element modeling.
 yade-0.60-doc - Platform for discrete element modeling.
 yade-dbg   - Platform for discrete element modeling.
 yade-doc   - Platform for discrete element modeling.

 My motivation for maintaining this package is: I am one of developers
 and users of this software. We would be glad to have it in Debian
 repository.

 Discrete element method is the numerical method of modelling a large
 number of particles, their stresses and displacements. It can be used
 as for granular material simulating as well as solid materials (rocks,
 concrete etc.).

 The YADE is mostly developed and used in universities and scientific
 laboratories in France, Great Britain, Czech Republic, Russia...
 Developers are PHD-students, Post-docs and scientists.

 The package can be found on mentors.debian.net:
 - URL: http://mentors.debian.net/debian/pool/main/y/yade-0.60
 - Source repository: deb-src http://mentors.debian.net/debian unstable
 main contrib non-free
 - dget 
 http://mentors.debian.net/debian/pool/main/y/yade-0.60/yade-0.60_0.60-1.dsc
 I would be glad if someone uploaded this package for me.

 Kind regards
  Anton Gladky



--
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/aanlktik+dyronb9qiykzza9q-ptusxncqnte5wd5f...@mail.gmail.com

Re: common source package for use in Debian and Ubuntu

2011-01-18 Thread Raphael Hertzog 
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

Re: common source package for use in Debian and Ubuntu

2011-01-18 Thread Paul Tagliamonte 
On Tue, Jan 18, 2011 at 3:42 PM, Raphael Hertzog hert...@debian.org 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

Re: would like review of my polipo-tor packaging

2011-01-18 Thread Scott Howard 
On Tue, Jan 18, 2011 at 3:12 PM,
travis+ml-debian-ment...@subspacefield.org wrote:
 Standards-Version: 3.8.4 should be 3.9.1

 I used the dh tools to make this, and I've seen debuild complain
 about this, but really didn't know what I should be doing in this
 case - funny thing is, both tools were up-to-date from teh ubuntu
 repo.  Is a text edit in order, or something else need doing?

Yes, you can change it with a text editor [1]. If you're not including
it in Debian, this is a minor issue. It mostly just lets us (and you)
know the last time the maintainer made sure it was policy compliant.
You should recheck and bump that every new policy version.

 I doubt the package will make it into the debian repo, since the
 prereqs aren't even there - TOR hasn't gotten their act together
 yet.  So not sure if merging everything into one changelog makes
 sense yet.  It's certainly been in my repo for a while, and been
 through a couple of changes.

TOR not having their act together - does that mean that they haven't
released a stable version yet or that no stable package is in Debian?
Would you be interested in packaging and maintaining TOR in Debian?

If you're not planning on having this in Debian, then changelog also
doesn't matter. But, in general, your first official Debian changelog
will simply be New packaging (Closes: #{ITP_BUG_NUMBER}) with no
other entries, and targeting the unstable distribution.

References [2-3] are good to check out to get more information.

Cheers,
Scott


[1] 
http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-Version
[2] http://www.debian.org/doc/developers-reference/pkgs.html
[3] http://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog


--
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==k2usgwvsu53pl6dm7fmug6su-cbtovv3o...@mail.gmail.com

Re: would like review of my polipo-tor packaging

2011-01-18 Thread Scott Howard 
On Tue, Jan 18, 2011 at 4:34 PM, Scott Howard showard...@gmail.com wrote:
 TOR not having their act together - does that mean that they haven't
 released a stable version yet or that no stable package is in Debian?
 Would you be interested in packaging and maintaining TOR in Debian?


Sorry, just saw [1] - have you contacted TOR and polipo's maintainers?
They are probably the best resources

[1] http://packages.qa.debian.org/t/tor.html

~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/aanlktim-bsvasanphnkc5+n4ryzmzddgvttyv5evm...@mail.gmail.com

[UDD] Packages flagged 'error' in DEHS import

2011-01-18 Thread Andreas Tille 
Hi,

I was wondering, why DEHS claims ncbi-tools6 as not 'uptodate' but rather 
'error'.
The DEHS page[1] says for experimental

# Watch: view (comments below)

 Too bad uscan doesn't actually honor downloadurlmangle for FTP urls. :-/
 [would use downloadurlmangle=s|$|/ncbi.tar.gz|]

# Uscan errors:
uscan.pl warning: In /tmp/ncbi-tools6_watchiu1iwq no matching files for watch 
line
ftp://ftp.ncbi.nlm.nih.gov/toolbox/ncbi_tools/old/(\d{8}[a-z]*)


and if I try

$ uscan --verbose
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
   opts=uversionmangle=s|^|6.1.|   
ftp://ftp.ncbi.nlm.nih.gov/toolbox/ncbi_tools/old/(\d{8}[a-z]*)
Useless content call in void context at /usr/share/perl5/LWP/Protocol/ftp.pm 
line 379
uscan warning: In watchfile debian/watch, reading FTP directory
  ftp://ftp.ncbi.nlm.nih.gov/toolbox/ncbi_tools/old/ failed: 400 FTP return 
code 000
-- Scan finished


I'm actually running into an error.  What I really do not understand is,
that the package in unstable has the very same watch file and does not
seem to produce an error because it correctly detects outdated and is
linking to the new version.

Any reasonable explanation for this?

Kind regards

 Andreas.

[1] http://dehs.alioth.debian.org/report.php?package=ncbi-tools6

-- 
http://fam-tille.de


-- 
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/20110118215423.gc2...@an3as.eu

Re: RFS: roxterm (updated package for experimental)

2011-01-18 Thread Tony Houghton 
I've filed a bug against vte upstream which you may want to subscribe
to. I don't know if they'll take much notice, because the affected vte
function is deprecated and I think its replacement is OK, but somebody
there might know what's going on.

https://bugzilla.gnome.org/show_bug.cgi?id=639900


-- 
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/20110118220050.74069...@realh.co.uk

Re: RFS: triggerhappy

2011-01-18 Thread Stefan Tomanek 
Dies schrieb Nick Leverton (n...@leverton.org):

  Every .c-file has to contain that header? Sure, possible, but seems very 
  awkward?
 
 It helps, the Debian tool licensecheck can then scan and report on the
 contents of the package.  Also if a source is borrowed elsewhere, the
 authorship is still clear.

Do you have an example for such an header? I tried a few variants, but
could not get licensecheck to work.


-- 
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/20110118214753.gi18...@zirkel.wertarbyte.de

RFS: mobile-broadband-provider-info (updated package)

2011-01-18 Thread Bhavani Shankar R 
Dear mentors,

I am looking for a sponsor for the new version 20110118-1
of my package mobile-broadband-provider-info.

It builds these binary packages:
mobile-broadband-provider-info - database of mobile broadband service providers

The package appears to be lintian clean.

The package can be found on mentors.debian.net:
- URL: 
http://mentors.debian.net/debian/pool/main/m/mobile-broadband-provider-info
- Source repository: deb-src http://mentors.debian.net/debian unstable
main contrib non-free
- dget 
http://mentors.debian.net/debian/pool/main/m/mobile-broadband-provider-info/mobile-broadband-provider-info_20110118-1.dsc

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

Kind regards


-- 
Bhavani Shankar
Ubuntu Developer   |  www.ubuntu.com
https://launchpad.net/~bhavi


--
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/AANLkTin2BCF6sqp1_hTj7kf2vH79fC=6vn8qdlpby...@mail.gmail.com