Bug#701706: RFS: ocamlrss/2.0-1 [ITP] -- RSS 2.0 parser and printer for OCaml
Le 23/05/2013 05:45, Prach Pongpanich a écrit :
Packaging a new upstream 2.2.0:
Sorry for taking so long, but I wanted to look at the whole thread
first... which I haven't done so far. Anyway, since you've been waiting
for some time now, I've just directly looked at your package without
looking at previous comments.
dget -x
http://mentors.debian.net/debian/pool/main/o/ocamlrss/ocamlrss_2.2.0-1.dsc
http://anonscm.debian.org/gitweb/?p=pkg-ocaml-maint/packages/ocamlrss.git
Please do not override Lintian tags about hardening.
Native plugins should be installed only when natdynlink is available,
please consider s/OPT/DYN/ in librss-ocaml.install.in.
Please add ${shlibs:Depends} to -dev package as well.
The relationship with Cameleon described in the description suggests a
versioned Breaks/Replaces relationship instead of a Conflicts.
A period is missing at the end of the -dev description.
rss_date.* files have been removed in version 2.1.0. Please update
debian/copyright accordingly.
You say LGPL-3+ in debian/copyright whereas it is written LGPL-3 (no
or later clause) everywhere else. Please fix.
Cheers,
--
Stéphane
--
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/519dffb3.8000...@debian.org
Re: What the proper way to update debian/changelog
Hi Tong,
You can try make a test, put your package in mentors.debian.net and
send us the link, asking for a revision. I and others can help you to
understand the process.
You should do what Prach Pongpanich said. And you can see what other
people done in their packages. A tip:
$ find /usr/share/doc/ -name 'changelog.Debian.gz' -exec zcat {} \;
~/changelog.Debian
Have a nice day!!!
Regards,
Eriberto - Brazil
2013/5/23 T o n g mlist4sunt...@yahoo.com:
Please bear in mind that you'd be explaining to someone who has never
maintained a debian package before, and is only testing-the-water
through reading.
--
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/CAP+dXJd2HAnMU_cXY6AaC9VfW1J2+6ayOwmmv-Gq+=m_+dz...@mail.gmail.com
Please help with Java issue where it seems to make a difference where JAR is installed
tags 697604 help thanks Hi, I'm a bit lost with my bit of Java knowledge if it comes to internals. I can only confirm that I can perfectly reproduce the problem using the data file submitted in [1] for testing and one reporter states in [2]: I downloaded upstream FastQC and there was no such problem. The only difference that I see is that in Debian a fastqc.jar is used while in upstream it's unpacked in the root directory. My conclusion is that this specific way with getSystemResource searches only the location where main class resides. In Debian's case it's fastqc.jar and in upstream it's FastQC directory. Any help is really welcome Andreas. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697604#15 [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697604#5 -- 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/20130523143637.gd30...@an3as.eu
Bug#706361: gti review
Hello Felix, Thank you for your corrections. We're almost there, but I hope that few more pedantic issues could be fixed... :) I take it it is not customary to provide overrides for pedantic warnings? You can do it and on some occasions I overridden some pedantic warnings to acknowledge that I've had a look at it and no further action is necessary. I found overrides useful with maintaining many packages where I tend to forget whenever I already dealt with the warning in particular package. But it is important to recognise unnecessary overrides such as those that tell you about problems that can be addressed by you or by upstream developer(s). It is not good to silence such warnings so the best would be to keep them as reminders however unimportant they may appear. No upstream changelog can remind you to include changelog if/when upstream decide to add it or it may be a reminder to suggest upstream to ship it. Also you may choose to generate changelog if you produce orig.tar from repository checkout. Perhaps there is no reason to silence this particular warning if upstream changelog is not shipped... License name MIT is incorrect even though upstream may refer to this license as such. MIT is considered ambiguous by the Free Software Foundation. Yes, I saw that, which is why I included the full license text. I assumed that would disambiguate it. Does the ambiguous designation mean that the name MIT should simply not be used? I have changed it to MIT Old Style. I think you can use MIT to refer to new MIT license text but perhaps it would be better to call it Expat as advised in copyright-format-specification-1.0: There are many versions of the MIT license. Please use Expat instead, when it matches. Please do not use spaces in short license name -- see examples in copyright-format-1.0 specification which clearly state that License names are case-insensitive, and may not contain spaces. Remember I suggested to use MIT-old-style not MIT Old Style? ;) Specifically I think it is a good practice to maintain Forwarded and Last-Update headers. All patches now have these. Thanks. As for usage of Forwarded field it is unusual to leave it empty. When your patch have only debian customisation and not useful for upstream just use Forwarded: not-needed and you can skip long explanation (in description) why and how this patch is not useful for forwarding. Again, thank you for your review. I appreciate all the information you've shared, and I think the package is much improved after these changes. Thank you, it's been a pleasure to help. :) I checked updated version and to my taste the car is still moving too fast. Of course this is not a problem, just feedback. All the best, Dmitry Smirnov GPG key : 4096R/53968D1B --- I hate all sports as rabidly as a person who likes sports hates common sense. -- H. L. Mencken -- 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/201305240707.15512.only...@member.fsf.org
Bug#709547: RFS: mapcatcher/0.8.0.0-1 [put in ITP, ITA, RC, NMU if applicable]
Package: sponsorship-requests Severity: normal Package: sponsorship-requests Severity: normal [important for RC bugs, wishlist for new packages] Dear mentors, I am looking for a sponsor for my package mapcatcher, ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589254 Package name: mapcatcher Version : 0.8.0.0-1 Upstream Author : Helder Sepu URL : https://code.google.com/p/gmapcatcher/ License : GPL-3+ Section : web It builds those binary packages: mapcatcher - offline maps viewer. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/mapcatcher Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/mapcatcher/mapcatcher_0.8.0.0-1.dsc Note that a git repository is here https://gitorious.org/debian-mapcatcher. There are several relevant points for this package. - This is my first python package, and - I have had to make significant changes to remove non-free components from the package. Regards, D. Haley -- 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/20130523230338.12819.39829.reportbug@localhost
Re: What the proper way to update debian/changelog
On Thu, 23 May 2013 09:55:06 -0300, Eriberto wrote: You should do what Prach Pongpanich said. And you can see what other people done in their packages. A tip: . . . Thanks Prach Eriberto for your answers. I posted my OP, then I thought, since this is the first time I'm posting here, better make it clear, so I posted the second message, didn't realized that Prach has already answered. I was totally unprepared for a turn around answer that fast. Sorry Prach, it looked like I was ignoring you, but actually I didn't know. Thanks again for your helps. -- 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/knmg9k$m39$1...@ger.gmane.org
Re: What the proper way to update debian/changelog
On Thu, 23 May 2013 09:55:06 -0300, Eriberto wrote: You can try make a test, put your package in mentors.debian.net and send us the link, asking for a revision. I and others can help you to understand the process. I really appreciate the mentoring, and understand that each case would be difference. And the best approach to handle the situation is to deal it in case-by-case bases. However, I'm a system learner. I.e., I learn through build up my overall knowledge first, before rolling up my sleeves and dive in. While trying to learn to maintain debian packages, I realized that there are A LOT to learn, which is hard. And I found what makes it even harder is that I have to learn such practical things bits by bits here and there. I.e., if such practical issues has been written out clearly, my life would be much easier. Not complaining, Debian has lot of good documents. Just that they are not to my taste. :-) They are written in the reference book style, whereas I more prefer a cook book style. :-) Still not complaining -- We've got to appreciate what we already have so far. -- 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/knmief$m39$2...@ger.gmane.org
Bug#709564: RFS: irssi-scripts/20130508
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package irssi-scripts * Package name: irssi-scripts * Version : 20130508 * URL: http://scripts.irssi.org/ * License : GPL-2.0+ Section: net It builds those binary packages: irssi-scripts - collection of scripts for irssi To access further information about this package, please visit the following URL: http://mentors.debian.net/package/irssi-scripts Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/i/irssi-scripts/irssi-scripts_20130508.dsc Changes since the last upload: * New upstream release. + Updated: logresume.pl, cap_sasl.pl, topic-diff.pl, repeat.pl, bantime.pl, whitelist.pl * debian/control + Bump standard versions 3.9.4 (no changes) * Update INDEX file + Url nickident.pl script + Url akilluser.pl script + Url challenge.pl script + Url quiet.pl script + Url whitelist.pl script + Url auto_away.pl script + Url bantime.pl script * debian/patches + Add change_mode_awayproxy_script.diff patch + change the default value for script_mode to 2. Closes: #680918 + Remove topic-diff.pl.diff patch + merge with upstream Regards, Daniel Echeverry -- Epsilon http://wiki.debian.org/DanielEcheverry Linux user: #477840 Debian user -- Epsilon http://wiki.debian.org/DanielEcheverry Linux user: #477840 Debian user Software libre liberar blackberry Libros online garmin y campin -- 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/caji_fcj+pk6xwzz6jetdm5wscda5ffec6vg-cqpwrpbp_1k...@mail.gmail.com
Re: What's the proper way to build from debian dsc
On Fri, 24 May 2013 02:14:39 +, T o n g wrote: I'm a system learner. I.e., I learn through build up my overall knowledge first, before rolling up my sleeves and dive in. While trying to learn to maintain debian packages, I realized that there are A LOT to learn, which is hard. And I found what makes it even harder is that I have to learn such practical things bits by bits here and there. I.e., if such practical issues has been written out clearly, my life would be much easier. I had always been trying to maintain some useful debian packages that are orphaned. More than 10 years ago, when glimpse was removed from the repo [1], I told myself it was time to learn to maintain debian packages, so that I could maintain glimpse (IMHO, glimpse is so far still the best *personal* searching tool, and I still think it is more a 'political' decision for it to be removed). [1] http://lists.debian.org/debian-user/2001/09/msg00312.html But I have to admit that maintaining debian/ubuntu packages is convoluted to me, even though I've tried to pick it up many times. I was always defeated merely by reading through the overwhelmingly vast information, and made only half way through. So it never happened. More than 10 years later, now I'm hoping to do it with a different approach. In stead of starting background reading from the start over and over again and never able to make it to the end, I'm going to start with the easiest step that I can think of -- try to build and upload a orphaned/removed package as the first step. So I found the glimpse dsc file at ftp://ftp.cstone.net/debian/pool/non-free/g/glimpse/glimpse_4.18.5-1.dsc Can anyone explain me in simple commands how I can build and test upload this glimpse package please? Of course, starting from to get it, and then properly update the debian/changelog, all the way to test upload, in as few steps as possible. Maybe increase the least significant version # and add my change comment, and my id can be handled by a single properly parameterized dch command, or maybe not. But proper commands always speaks for themselves. Thanks -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/knmojm$cem$1...@ger.gmane.org
Re: What's the proper way to build from debian dsc
On Thu, May 23, 2013 at 8:59 PM, T o n g mlist4sunt...@yahoo.com wrote: On Fri, 24 May 2013 02:14:39 +, T o n g wrote: I'm a system learner. I.e., I learn through build up my overall knowledge first, before rolling up my sleeves and dive in. While trying to learn to maintain debian packages, I realized that there are A LOT to learn, which is hard. And I found what makes it even harder is that I have to learn such practical things bits by bits here and there. I.e., if such practical issues has been written out clearly, my life would be much easier. I had always been trying to maintain some useful debian packages that are orphaned. More than 10 years ago, when glimpse was removed from the repo [1], I told myself it was time to learn to maintain debian packages, so that I could maintain glimpse (IMHO, glimpse is so far still the best *personal* searching tool, and I still think it is more a 'political' decision for it to be removed). [1] http://lists.debian.org/debian-user/2001/09/msg00312.html But I have to admit that maintaining debian/ubuntu packages is convoluted to me, even though I've tried to pick it up many times. I was always defeated merely by reading through the overwhelmingly vast information, and made only half way through. So it never happened. More than 10 years later, now I'm hoping to do it with a different approach. In stead of starting background reading from the start over and over again and never able to make it to the end, I'm going to start with the easiest step that I can think of -- try to build and upload a orphaned/removed package as the first step. So I found the glimpse dsc file at ftp://ftp.cstone.net/debian/pool/non-free/g/glimpse/glimpse_4.18.5-1.dsc Can anyone explain me in simple commands how I can build and test upload this glimpse package please? Of course, starting from to get it, and then properly update the debian/changelog, all the way to test upload, in as few steps as possible. Maybe increase the least significant version # and add my change comment, and my id can be handled by a single properly parameterized dch command, or maybe not. But proper commands always speaks for themselves. Thanks Fetch the source tarball and debian diff: $ dget ftp://ftp.cstone.net/debian/pool/non-free/g/glimpse/glimpse_4.18.5-1.dsc $ cd glimpse-4.18.5 Add new changelog entry: $ dch -i Build (an unsigned) package: $ dpkg-buildpackage -rfakeroot -us -uc Upload to ftpmaster.d.o (but there's no point in doing this if you're not a DD/DM): $ dput glimpse_$VERSION_$ARCH.changes There's obviously more to it, e.g. working with a patch system (quilt, or a VCS), running lintian, building in a clean environment with tools like pbuilder/sbuild, etc., but that'll get you started. One word of advice: pick a package that's more modern to learn from. Modern, short-hand dh is generally easier to work with (especially for simple packages) than classic debhelper. Regards, Vincent -- 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/caczd_tcjcx65r0hj9oxhwc_4bbmr1wcp4h6k3xfo4hsvoho...@mail.gmail.com
Re: What's the proper way to build from debian dsc
T o n g mlist4sunt...@yahoo.com writes: So I found the glimpse dsc file at ftp://ftp.cstone.net/debian/pool/non-free/g/glimpse/glimpse_4.18.5-1.dsc Can anyone explain me in simple commands how I can build and test upload this glimpse package please? Of course, starting from to get it, and then properly update the debian/changelog, all the way to test upload, in as few steps as possible. Maybe increase the least significant version # and add my change comment, and my id can be handled by a single properly parameterized dch command, or maybe not. But proper commands always speaks for themselves. % export DEBEMAIL=mlist4sunt...@yahoo.com % export DEBFULLNAME=T o n g # or whatever you want to use % dget ftp://ftp.cstone.net/debian/pool/non-free/g/glimpse/glimpse_4.18.5-1.dsc % cd glimpse-4.18.5 # make required changes to the package # change Maintainer in debian/control to match DEB* settings above % dch -i # add descriptions of your changes using your editor, opened by dch # save and exit % debuild # if build is successful, *.deb packages will be left up one level # install packages, test, iterate as needed % cd .. % debsign *.changes # the previous step requires you have a GnuPG key set up They're now ready to upload, which you probably want to do with dput. If you're uploading it to mentors, see the mentors documentation for the correct dput configuration and target. -- Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/ -- 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/874ndt583k@windlord.stanford.edu
Re: What the proper way to update debian/changelog
Le Fri, May 24, 2013 at 02:14:39AM +, T o n g a écrit : Not complaining, Debian has lot of good documents. Just that they are not to my taste. :-) They are written in the reference book style, whereas I more prefer a cook book style. :-) Still not complaining -- We've got to appreciate what we already have so far. Hi, have you considered the following tutorial ? http://www.debian.org/doc/devel-manuals#packaging-tutorial 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/20130524042425.ga7...@falafel.plessy.net
