Re: Bug#534866: ITP: kernelcheck -- tool for an automated build of a kernel from the latest source
On Thu, Jul 2, 2009 at 04:12, Jeff Carr wrote: > On Sun, Jun 28, 2009 at 04:47, George Danchev wrote: > >>> >> is this somehow related to Debian? Can be used on a debian system in a >>> >> productive way? > >>> You didn't answer my question: can this package be useful to a Debian user? >> >> The question could be extended further: ... to be useful to any distro user? > > Having a common tool for this (especially since it makes real .deb > files) would be useful to me. When I want to make kernel .deb files > it's always a PITA. I usually don't even bother anymore. If there was > a simple tool that would be convenient. What's that make-kpkg (from kernel-package) missing? have you ever reported usability bugs against kernel-package to make it more suitable (if it isn't already) for users? would it be better to concentrate on just one standard tool an make it the best? Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: xburst-tools
Dear mentors, I am looking for a sponsor for my package "xburst-tools". * Package name: xburst-tools Version : 0.0+200906-1 Upstream Author : Xiangfu Liu * URL : http://github.com/xiangfu/xburst-tools * License : GPL Section : misc It builds these binary packages: xburst-tools - tools for Ingenic XBurst CPU USB boot and NAND flash access The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/x/xburst-tools - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/x/xburst-tools/xburst-tools_0.0+200906-1.dsc I would be glad if someone uploaded this package for me. -- Best Regards Xiangfu Liu jabber : xiangf...@gmail.com skype : xiangfu.z -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: Link Grammar
Is there someone who could sponsor my an upload of link-grammar 4.5.7-2? The packages are located at http://lingcog.iit.edu/~bloom/link-grammar/ My previous sponsor was Anibal Monsalve Salazar, but he doesn't respond to my emails lately, so I guess I'm looking for a more permenant sponsor, and someone who can eventually advocate for me to be a Debian Maintainer myself so I can upload myself. --Ken -- Chanoch (Ken) Bloom. PhD candidate. Linguistic Cognition Laboratory. Department of Computer Science. Illinois Institute of Technology. http://www.iit.edu/~kbloom1/ signature.asc Description: Digital signature
Re: Bug#534866: ITP: kernelcheck -- tool for an automated build of a kernel from the latest source
On Sun, Jun 28, 2009 at 04:47, George Danchev wrote: >> >> is this somehow related to Debian? Can be used on a debian system in a >> >> productive way? >> You didn't answer my question: can this package be useful to a Debian user? > > The question could be extended further: ... to be useful to any distro user? Having a common tool for this (especially since it makes real .deb files) would be useful to me. When I want to make kernel .deb files it's always a PITA. I usually don't even bother anymore. If there was a simple tool that would be convenient. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: gvpe, the GNU Virtual Private Ethernet daemon
Jonathan Wiltshire wrote:
> I worked through the diff of your proposed changes and integrated almost
> all of them - if I'm right, lots are formatting and style, some cruft
> removal, and some technical.
yes, sorry about not marking the changes specifically.
> The file gvpe.init particularly came mostly from the debhelper
> template, which is why it was weaker. The bits I'm left with are the
> ones I don't quite follow, here as a diff with annotations:
> init.d:
> @@ -31,16 +31,11 @@
> #merely create a single tunnel, it creates a real
> #network with multiple endpoints.
> ### END INIT INFO
>
> -PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
> -
> -DAEMON=/usr/sbin/gvpe
> NAME=gvpe
> DESC="GNU Virtual Private Ethernet daemon"
> -LOGDIR=/var/log/gvpe
> -
> PIDFILE=/var/run/$NAME.pid
>
> -test -x $DAEMON || exit 0
> +test -x /usr/bin/gvpectrl || exit 0
> Ok, I missed the fact that the PATH variable has wrong paths in (oops)
> so that can go in. But why remove the declaration of $NAME and move it
> further down?
do you mean $DAEMON instead of $NAME? $NAME isn't moved...
the DAEMON variable is set later because it's constructed based on the
values of $CIPHER and $DIGEST, which can be overriden by
/etc/default/gvpe. so it has to be set after sourcing the defaults
file.
> I take it the $LOGDIR variable goes because it doesn't get
> used - I assumed that log_daemon_msg and friends used it, probably a bad
> thing to assume.
yes, i tried to remove the unused boilerplate.
> Why test that /usr/bin/gvpectrl is executable but not $DAEMON?
the init script is a conf file which means it remains on the system on
package removal. (conf files are only removed on purge.) so the init
script needs a way to determine if the package is installed so you
usually just test if your daemon's binary still exists.
in this case, though, the path to the daemon is constructed, and it
could be constructed to a nonexistent path (say, a typo in
/etc/default/gvpe) and the init script wouldn't run. so instead test
for a stable binary name included in the package (gvpectrl in this case)
instead.
> @@ -73,8 +66,7 @@
> # Use this if you want the user to explicitly set 'RUN' in
> # /etc/default/
> if [ "x$RUN" != "xyes" ]; then
> -log_failure_msg "$NAME disabled, please adjust the configuration to
> your needs "
> -log_failure_msg "and then set RUN to 'yes' in /etc/default/$NAME to
> enable it."
> +log_failure_msg "$NAME disabled in /etc/default/$NAME."
> exit 1
>
> Is this change to the output text a preference, or is there a style for
> this sort of message that I've missed somewhere?
it looks odd because log_failure_msg prints out the string you gave it
and appends "failed!" in red letters, so your sequence prints out
"failed!" twice. it looks nicer if "failed!" is only printed once.
i don't know if there's a style guide. the message should probably fit
on an 80 column terminal though.
i have ten packages currently installed which install init scripts that
print out a 'disabled' message if they haven't been configured to start,
and they all use only a single line to print the warning. some of them
use log_warning_msg. i don't see any that use log_failure_msg.
> @@ -153,7 +145,7 @@
> log_end_msg 0
> exit 0
> fi
> -if start_server; then
> +if start_server ; then
>
> I think you missed this one ;)
sorry. the template you copied from had a lot of tabs-vs-spaces
confusion too.
> @@ -213,19 +205,11 @@
> fi
> ;;
> reload)
> -log_daemon_msg "Reloading configuration for $DESC" "$NAME"
> -if running; then
> -[ -x /usr/sbin/gvpectrl ] && /usr/sbin/gvpectrl -kHUP
> -log_end_msg 0
> -else
> -log_progress_msg "apparently not running"
> -log_end_msg 1
> -exit 1
> -fi
> +log_warning_msg "Reloading $NAME daemon: not implemented (use
> restart)."
> ;;
> *)
> N=/etc/init.d/$NAME
> -echo "Usage: $N
> {start|stop|force-stop|restart|reload|force-reload|status}" >&2
> +echo "Usage: $N
> {start|stop|force-stop|restart|force-reload|status}" >&2
>
> I only just today noticed that gvpectrl can send a HUP signal to the
> daemon, and tested that it reloads the configuration properly, so I've
> implemented reloading. Does it look correct?
hmm, i don't know how gvpectrl determines what process ID to send the
signal too. probably just reads the pid file?
if you just need to send SIGHUP to the gvpe daemon you might want to
use the $PIDFILE and send the signal yourself.
actually, the whole init script would probably be a lot shorter / neater
if you used start-stop-daemon :)
[ the last init script i wrote was /etc/init.d/unbound in the unbound
package if you need an example of an init script that uses
start-stop-daemon. ]
> debi
Re: RFS: gwibber
Dnia 2009-07-01, śro o godzinie 21:57 +0530, Kartik Mistry pisze: > Its fine. Fix it in next upstream release. Alright (: > Make yourself owner of ITP. Damn, I dunno if I did it properly, could you check it please? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496326 I will quote: Reported by: Daniel Watkins Date: Sun, 24 Aug 2008 13:42:01 UTC Owned by: deb...@hadret.com Severity: wishlist > And reupload fixed package for review :) New release is already on mentors: - URL: http://mentors.debian.net/debian/pool/main/g/gwibber - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gwibber/gwibber_1.2.0 +bzr346-4.dsc -- Filip Chabik -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: gwibber
On Wed, Jul 1, 2009 at 7:29 PM, Filip Chabik wrote: > no-upstream-changelog > > I asked it before, will ask it again: do I have to make use of provided > link by Ryan Paul, or is it better idea to wait until they will make > something better? Its fine. Fix it in next upstream release. > There's still problem with that ITP bug - I wrote there that I'd like to > take off this bug, but nobody answer me. Do I have to wait or should I > make new ITP bug? Make yourself owner of ITP. And reupload fixed package for review :) -- Cheers, Kartik Mistry | 0xD1028C8D | IRC: kart_ Debian GNU/Linux Developer Blog.en: ftbfs.wordpress.com Blog.gu: kartikm.wordpress.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: gyachi
On Wed, Jul 01, 2009 at 05:59:52PM +0800, Loell anthony Erecre wrote: > I am looking for a sponsor for my package "gyachi". > > * Package name: gyachi > Version : 1.1.71-1~debian > Upstream Author : Gregory Hosler > * URL : http://gyachi.sourceforge.net > * License : GPL > Section : x11 > > It builds these binary packages: > gyachi - A Linux client for the Yahoo! Messenger protocol written using > GTK And it builds these lintian warnings: :) W: gyachi source: dh-make-template-in-source debian/postrm.ex W: gyachi source: dh-make-template-in-source debian/cron.d.ex W: gyachi source: dh-make-template-in-source debian/gyachi.doc-base.EX W: gyachi source: dh-make-template-in-source debian/postinst.ex W: gyachi source: dh-make-template-in-source debian/manpage.sgml.ex W: gyachi source: dh-make-template-in-source debian/manpage.1.ex W: gyachi source: dh-make-template-in-source debian/gyachi-default.ex W: gyachi source: dh-make-template-in-source debian/manpage.xml.ex W: gyachi source: dh-make-template-in-source debian/preinst.ex W: gyachi source: dh-make-template-in-source debian/watch.ex W: gyachi source: dh-make-template-in-source debian/prerm.ex W: gyachi source: dh-make-template-in-source debian/menu.ex W: gyachi source: out-of-date-standards-version 3.7.2 (current is 3.8.2) W: gyachi source: native-package-with-dash-version W: gyachi source: diff-contains-cvs-control-dir po/CVS W: gyachi source: diff-contains-cvs-control-dir doc/txt/CVS W: gyachi source: diff-contains-cvs-control-dir doc/html/CVS W: gyachi source: diff-contains-cvs-control-dir doc/CVS W: gyachi source: diff-contains-cvs-control-dir spec_files/gentoo/CVS W: gyachi source: diff-contains-cvs-control-dir spec_files/CVS W: gyachi source: diff-contains-cvs-control-dir lib/CVS W: gyachi source: diff-contains-cvs-control-dir client/CVS W: gyachi source: diff-contains-cvs-control-dir webcam/CVS W: gyachi source: diff-contains-cvs-control-dir themes/gyachi-classic/obsolete/CVS W: gyachi source: diff-contains-cvs-control-dir themes/gyachi-classic/CVS W: gyachi source: diff-contains-cvs-control-dir themes/YMlike/CVS W: gyachi source: diff-contains-cvs-control-dir themes/recre8/CVS W: gyachi source: diff-contains-cvs-control-dir themes/pidgy/CVS W: gyachi source: diff-contains-cvs-control-dir themes/CVS W: gyachi source: diff-contains-cvs-control-dir smileys/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/blowfish/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/gpgme/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/xmms/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/libnotify/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/alsa/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/esd/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/mcrypt/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/pulseaudio/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/gtkspell/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/photos/CVS W: gyachi source: diff-contains-cvs-control-dir plugins/CVS W: gyachi source: diff-contains-cvs-control-dir intl/CVS W: gyachi source: diff-contains-cvs-control-dir tuxvironments/CVS W: gyachi source: diff-contains-cvs-control-dir m4/CVS W: gyachi source: diff-contains-cvs-control-dir audibles/CVS W: gyachi source: diff-contains-cvs-control-dir gyvoice/CVS W: gyachi source: diff-contains-cvs-control-dir gyvoice/wine/CVS W: gyachi source: diff-contains-cvs-control-dir sounds/CVS W: gyachi source: diff-contains-cvs-control-dir CVS Those should be fixed. And what's that weird version number about '~debian'? Hauke signature.asc Description: Digital signature
Re: RFS: python-ipcalc [DONE]
On Wed, Jul 1, 2009 at 2:18 PM, Evgeni Golov wrote: > Hey, > > On Wed, Jul 01, 2009 at 12:55:14PM +, mezgani ali wrote: > > I'll use quilt, if it is God's will ;) > > Heh, god, don't think we should discuss this further ;) > If you think so :) > > > No, i don't have any change, you can upload, thanks > > I had one :) > I added "python" to the list of Depends for the binary package and > uploaded it now. > > Please add that change to your local tree, so you don't overwrite it > later. > Ok, i do > > Regards and thanks for your contribution Thanks for you Evgeni, and for your support > > Evgeni > -- Ali MEZGANI Network Engineering/Security http://securfox.wordpress.com/
Re: RFS: python-ipcalc [DONE]
Hey, On Wed, Jul 01, 2009 at 12:55:14PM +, mezgani ali wrote: > I'll use quilt, if it is God's will ;) Heh, god, don't think we should discuss this further ;) > No, i don't have any change, you can upload, thanks I had one :) I added "python" to the list of Depends for the binary package and uploaded it now. Please add that change to your local tree, so you don't overwrite it later. Regards and thanks for your contribution Evgeni -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: gwibber
Dnia 2009-07-01, śro o godzinie 09:13 +0530, Kartik Mistry pisze: > Heh :) > > No issue if you steal him :P Nobody wants me! ;( Anyway, gwibber package is now far better, than it was. Firstly - many thanks to Piotr for providing help with python-support - it was a very good idea to drop off CDBS. There's only one lintian --pedantic warning, which is: no-upstream-changelog I asked it before, will ask it again: do I have to make use of provided link by Ryan Paul, or is it better idea to wait until they will make something better? There's still problem with that ITP bug - I wrote there that I'd like to take off this bug, but nobody answer me. Do I have to wait or should I make new ITP bug? -- Filip Chabik -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: mscgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for my package "mscgen". Package name: mscgen Version : 0.16~svn31-1 Upstream Author : Michael C McTernan URL : http://www.mcternan.me.uk/mscgen/ License : Partly GPL-2 (or later), partly LGPL-2.1 (or later) Section : devel It builds these binary packages: mscgen - Message Sequence Chart (MSC) generator 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/mscgen - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/m/mscgen/mscgen_0.16~svn31-1.dsc I would be glad if someone uploaded this package for me. Kind regards Niels Thykier -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkpLXXMACgkQVCqoiq1Ylqz/SQCeM1F1N9PNCAe1DSb+uPX0tyT7 7/oAn3w+om7ELlYlyXgDSe7pxe9cS9Xp =XThq -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-ipcalc
On Wed, Jul 1, 2009 at 12:14 PM, Evgeni Golov wrote: > Hi, > > On Wed, 1 Jul 2009 12:01:11 + mezgani ali wrote: > > > I setup the License field in the pkg-info file, also i did some change to > > setup.py. > > those are the changes that i maked to the upstream source. > > and i think that was not really necessary. > > > > The orig.tar.gz looks to be the same as the original upstream tarball. > > Had a brief look at the diff, shouldn't be necessary at all here. > And if you want to have modifications to upstream source, please use a > patchsystem like quilt (or dpatch, but I prefer quilt), don't chage the > orig.tar.gz > The newly uploaded version with the clean tarball builds fine and I > cant find any differences in behaviour or something. > I'll use quilt, if it is God's will ;) > > > > Said that, I see no more problems with the package, and would upload it > > > as soon you exchange the tarball. > > So, anything more you want to change or to know? If not, I'll upload :) > No, i don't have any change, you can upload, thanks > > > There is rwhois (https://sourceforge.net/projects/rwhois/) a recursive > whois > > client that > > can parse records into usable objects, but i never use it and it seems to > be > > outdated because > > last update was the 23th April, 2003. > > Aye, I know rwhois, but its... incomplete and outdated, yeah. > > > You know Evgeni this is a nice idea and must to be translated to a > serious > > project > > "developing whois python lib" :) > > and python miss this module. > > Great, do you have some free time? ;) > Nah, joking, I guess I'd have to do this by myself when I really need > it, until then, the good old whois(1) on the command line is enough :) Of course command line is and still the reference for any usage, but when i need whois in my python applications i use a basic client that bind a socket and connect to port 43, that's all Anyway I'll add python-whois to my todo list :) > Regards > > -- > Bruce Schneier Fact Number 755: > Bruce Schneier can tune an antenna by whistling the desired resonant > frequency. > -- Ali MEZGANI Network Engineering/Security http://securfox.wordpress.com/
Re: RFS: python-ipcalc
Hi, On Wed, 1 Jul 2009 12:01:11 + mezgani ali wrote: > I setup the License field in the pkg-info file, also i did some change to > setup.py. > those are the changes that i maked to the upstream source. > and i think that was not really necessary. > > The orig.tar.gz looks to be the same as the original upstream tarball. Had a brief look at the diff, shouldn't be necessary at all here. And if you want to have modifications to upstream source, please use a patchsystem like quilt (or dpatch, but I prefer quilt), don't chage the orig.tar.gz The newly uploaded version with the clean tarball builds fine and I cant find any differences in behaviour or something. > > Said that, I see no more problems with the package, and would upload it > > as soon you exchange the tarball. So, anything more you want to change or to know? If not, I'll upload :) > There is rwhois (https://sourceforge.net/projects/rwhois/) a recursive whois > client that > can parse records into usable objects, but i never use it and it seems to be > outdated because > last update was the 23th April, 2003. Aye, I know rwhois, but its... incomplete and outdated, yeah. > You know Evgeni this is a nice idea and must to be translated to a serious > project > "developing whois python lib" :) > and python miss this module. Great, do you have some free time? ;) Nah, joking, I guess I'd have to do this by myself when I really need it, until then, the good old whois(1) on the command line is enough :) Regards -- Bruce Schneier Fact Number 755: Bruce Schneier can tune an antenna by whistling the desired resonant frequency. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-ipcalc
On Wed, Jul 1, 2009 at 11:23 AM, Evgeni Golov wrote: > Hi Ali, > > On Wed, 1 Jul 2009 10:48:16 + mezgani ali wrote: > > > I applied the patch, i setup the watch file and the README.source > > Well you did the hard work for me Evengi ;) > > Aye, the new package looks very good. > Just a question, why does your orig.tar.gz have a different md5sum then > the one on pypi? Did you repackage it? The general rule of thumb is to > avoid repackaging and using the original upstream tarball where > possible (and here it looks like it is possible). > I setup the License field in the pkg-info file, also i did some change to setup.py. those are the changes that i maked to the upstream source. and i think that was not really necessary. The orig.tar.gz looks to be the same as the original upstream tarball. > > Said that, I see no more problems with the package, and would upload it > as soon you exchange the tarball. > On another topic, do you know of any decent whois implementation in > Python? One that can whois domains and IPs and tell me the abuse-email > or the name of the owner (so one that can actually parse the output, > not only display me the text-blob)? > There is rwhois (https://sourceforge.net/projects/rwhois/) a recursive whois client that can parse records into usable objects, but i never use it and it seems to be outdated because last update was the 23th April, 2003. You know Evgeni this is a nice idea and must to be translated to a serious project "developing whois python lib" :) and python miss this module. Regards, > > Regards > Evgeni > > -- > Bruce Schneier Fact Number 1269: > Bruce Schneier has a set of SSH Bump Keys. > -- Ali MEZGANI Network Engineering/Security http://securfox.wordpress.com/
Re: RFS: python-ipcalc
Hi Ali, On Wed, 1 Jul 2009 10:48:16 + mezgani ali wrote: > I applied the patch, i setup the watch file and the README.source > Well you did the hard work for me Evengi ;) Aye, the new package looks very good. Just a question, why does your orig.tar.gz have a different md5sum then the one on pypi? Did you repackage it? The general rule of thumb is to avoid repackaging and using the original upstream tarball where possible (and here it looks like it is possible). Said that, I see no more problems with the package, and would upload it as soon you exchange the tarball. On another topic, do you know of any decent whois implementation in Python? One that can whois domains and IPs and tell me the abuse-email or the name of the owner (so one that can actually parse the output, not only display me the text-blob)? Regards Evgeni -- Bruce Schneier Fact Number 1269: Bruce Schneier has a set of SSH Bump Keys. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: python-ipcalc
Hi Evgeni,
On Tue, Jun 30, 2009 at 7:29 PM, Evgeni Golov wrote:
> Hi,
>
>
> On Sat, 27 Jun 2009 22:08:59 +0200 mezgani ali wrote:
>
> > Ok Evgeni, you know it was difficult for me to divine it :)
>
> Yeah I guess so, no problem :)
>
> > > Ok, I'll have a look on Monday or so, quite busy right at the moment.
>
> For some monday==tuesday ;)
> I had a look at your package yesterday and prepared some proposed
> changes now, see the attached debdiff.
>
> First of all: you added python-support to Build-Depends, but did not
> call dh_pysupport in your debian/rules, so it was mostly useless :)
> And your debian/rules was soo long for a so tiny package :)
> debhelper knows perfectly how to handle python setup.py scripts, so I
> just put a
> %:
>dh $@
> into debian/rules and let it build - much cleaner and now with correct
> pysupport integration :)
>
Yes i see this is a very useful tips.
>
> The other changes in the diff are against control:
> Depends: python-support comes out of ${python:Depends}, no need to add
> this manually, lintian complains about ${misc:Depends} missing, so I
> added it.
> Then I added Provides: ${python:Provides} - maybe someone wants so pull
> python2.4-ipcalc for some reason.
> And I reformatted the description a bit, as lintian complained about
> too long lines.
>
> So please have a look at the attached diff, understand it and apply
> it :)
> Whats still open? lintian complains about a missing watch-file. But
> upstreams page looks quite hacky and I did not find an easy way how to
> look up the latest version from it. You can add an override or an empty
> watch file with a comment, I usually do the last, but you can do
> whatever you want - or ignore the warning for the moment and tell
> upstream to publish the source in a more sane way.
> And while at it, please consider adding a README.source as
> described in Policy 4.14 and telling the others how to fetch the latest
> source and create a .orig.tar.gz (writing "go to URL, fetch the .zip
> and convert it with " should be enough).
>
I applied the patch, i setup the watch file and the README.source
Well you did the hard work for me Evengi ;)
The package seems to be lintian clean, please check :
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=python-ipcalc
>
> Regards
> Evgeni
>
> --
> Bruce Schneier Fact Number 188:
> Heisenberg's Uncertainty Principle doesn't protect your qubits from
> Bruce Schneier. Bruce knows with certainty.
>
Regards,
--
Ali MEZGANI
Network Engineering/Security
http://securfox.wordpress.com/
RFS: gyachi
From: Loell Anthony Erecre To: debian-mentors@lists.debian.org Subject: RFS: gyachi Dear mentors, I am looking for a sponsor for my package "gyachi". * Package name: gyachi Version : 1.1.71-1~debian Upstream Author : Gregory Hosler * URL : http://gyachi.sourceforge.net * License : GPL Section : x11 It builds these binary packages: gyachi - A Linux client for the Yahoo! Messenger protocol written using GTK The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gyachi - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gyachi/gyachi_1.1.71-1~debian.dsc I would be glad if someone uploaded this package for me. Kind regards Loell Anthony Erecre -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: upload debian package error
Hi Sandro Tosi Thanks for the reply. I will try my best Sandro Tosi wrote: > Hello xiangfu, > this kind of questions are better addressed to debian-mentors mailing > list, adding it, and you also already received a reply [1] there. > > [1] https://lists.debian.org/debian-mentors/2009/06/msg00573.html > > On Wed, Jul 1, 2009 at 08:55, xiangfu wrote: >> Hi >> I try to upload xburst-tools[1], I have two warning and one error. > > is this a new package? I can't find it in our archive or an ITP for it. > >> my question is >> 1. the version number must 1.0.0(like that). can I use 2009.06(something >> like that to be a version) > > if upstream has a version standard, use that, bu you can also use > dates for version. > > You have to create a non-native package, that's the reason for > "source-nmu-has-incorrect-version-number" > > I think this question proves you didn't read debian policy, developers > reference and new maintainers guide: please fill this gap of knowledge > asap, and before asking further questions. > >> 2. I am not a maintainer. but I want to be this package's maintainer. >> can I add my name and email to the control file > > you MUST add your name if you want to be the maintainer. That's th > reason for "xburst-tools source" lintian error. > >> 3. what am I got do with last warining. > > remove spuriours, auto-generated files in clean debian/rules target. > >> maybe I ignore some help page because My English is not very good. > > English is very important for debian communication, so I strongly > suggest to improve your english. > >> So give me some advice or direct. > > Read teh doc I've mentioned above and use debian-mentors, not -devel. > > Regards, -- Best Regards Xiangfu Liu jabber : xiangf...@gmail.com skype : xiangfu.z -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: xburst-tools
Hi
sorry for reply later.
I am not subscribe the debian-mentor list. so miss this email.
thanks for the help.
I will work on that, to make it no warning.
keep report progress.
(IANADD, review only)
On Mon, Jun 29, 2009 at 11:32:00PM +0800, xiangfu wrote:
> Dear mentors,
>
> I am looking for a sponsor for my package "xburst-tools".
>
> * Package name: xburst-tools
> Version : 20090630-1
> Upstream Author : Xiangfu Liu
> * URL : http://github.com/xiangfu/xburst-tools
> * License : GPLv3
> Section : misc
>
> It builds these binary packages:
> xburst-tools - host tool for Ingenic XBurst CPU USB boot and NAND flash access
Is this meant to be a native package? It doesn't look like it - in which
case you need to have an xburst-tools_2090630.orig.tar.gz file with the
upstream sources in (even if you are upstream), and then when you build
the package you will get a diff.gz file. [1]
Other things you also need to address:
* you need to file an ITP bug and declare it in your changelog [2]
* you should be working to standards version 3.8.2 by now
* the package descriptions need some work. You might like to ask for a
review at the debian-l10n-english mailing list [3].
* if you're using debhelper, you should have a ${misc:Depends} dependency
* the copyright file should make it clearer how this software is licensed
* remove the dh-make hints from your files, like in debian/copyright
* tidy your rules file and remove the commented-out calls, and other cruft
* add a watch file
* please use the lintian tool, there are many warnings:
W: xburst-tools source: out-of-date-standards-version 3.8.0 (current is 3.8.2)
W: xburst-tools source: changelog-should-mention-nmu
W: xburst-tools source: source-nmu-has-incorrect-version-number 20090630-1
W: xburst-tools source: native-package-with-dash-version
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage1/debug.o
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage1/common.o
P: xburst-tools source: source-contains-prebuilt-binary
xburst_stage2/boothandler.o
P: xburst-tools source: source-contains-prebuilt-binary
xburst_stage2/nandflash_4750.o
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage2/serial.o
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage2/udc.o
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage2/head.o
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage1/main.o
P: xburst-tools source: source-contains-prebuilt-binary
xburst_stage2/nandflash_4740.o
P: xburst-tools source: source-contains-prebuilt-binary
xburst_stage1/xburst_stage1.elf
P: xburst-tools source: source-contains-prebuilt-binary
xburst_stage1/board_4740.o
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage1/head.o
P: xburst-tools source: source-contains-prebuilt-binary
xburst_stage1/board_4750.o
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage2/cache.o
P: xburst-tools source: source-contains-prebuilt-binary
xburst_stage2/xburst_stage2.elf
P: xburst-tools source: source-contains-prebuilt-binary xburst_stage2/main.o
W: xburst-tools: binary-without-manpage usr/bin/xburst_tools
E: xburst-tools: FSSTND-dir-in-usr usr/man/
I: xburst-tools: package-contains-empty-directory usr/man/man1/
I: xburst-tools: package-contains-empty-directory usr/share/xburst-tools/
P: xburst-tools: copyright-refers-to-symlink-license
usr/share/common-licenses/GPL
W: xburst-tools: copyright-lists-upstream-authors-with-dh_make-boilerplate
W: xburst-tools: copyright-contains-dh_make-todo-boilerplate
W: xburst-tools: description-synopsis-might-not-be-phrased-properly
W: xburst-tools: new-package-should-close-itp-bug
W: xburst-tools: wrong-bug-number-in-closes l3:#
(use [4] if you don't understand them)
1: http://www.debian.org/doc/manuals/developers-reference/pkgs.html#sourcelayout
2: http://www.debian.org/devel/wnpp/
3: http://lists.debian.org/debian-l10n-english/
4: http://lintian.debian.org/tags.html
--
Best Regards
Xiangfu Liu
jabber : xiangf...@gmail.com
skype : xiangfu.z
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: gvpe, the GNU Virtual Private Ethernet daemon
On Wed, Jun 24, 2009 at 11:51:44PM +0300, George Danchev wrote: > already uploaded in Debian. Unfortunately, code dups, also means (security) > bugs dups, like that conditional `devision by zero' in ev_select.c line 105 > which seems to be windows-specific (NFBITS previously and conditionally > defined > as 0). > > Also, this would properly deallocate a previously dynamically allocated array > (as found by cppcheck, another package I'm looking at;-) I meant to say last night: I also mentioned these problems to upstream when I mailed him yesterday. -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: upload debian package error
Hello xiangfu, this kind of questions are better addressed to debian-mentors mailing list, adding it, and you also already received a reply [1] there. [1] https://lists.debian.org/debian-mentors/2009/06/msg00573.html On Wed, Jul 1, 2009 at 08:55, xiangfu wrote: > Hi > I try to upload xburst-tools[1], I have two warning and one error. is this a new package? I can't find it in our archive or an ITP for it. > my question is > 1. the version number must 1.0.0(like that). can I use 2009.06(something like > that to be a version) if upstream has a version standard, use that, bu you can also use dates for version. You have to create a non-native package, that's the reason for "source-nmu-has-incorrect-version-number" I think this question proves you didn't read debian policy, developers reference and new maintainers guide: please fill this gap of knowledge asap, and before asking further questions. > 2. I am not a maintainer. but I want to be this package's maintainer. > can I add my name and email to the control file you MUST add your name if you want to be the maintainer. That's th reason for "xburst-tools source" lintian error. > 3. what am I got do with last warining. remove spuriours, auto-generated files in clean debian/rules target. > maybe I ignore some help page because My English is not very good. English is very important for debian communication, so I strongly suggest to improve your english. > So give me some advice or direct. Read teh doc I've mentioned above and use debian-mentors, not -devel. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
