ITR: scrotwm - dynamic tiling window manager
Hi Andrea, On 09/05/17 23:36 +0200, Andrea Bolognani said ... On Mon, 20 Apr 2009 10:48:12 +0200 Andrea Bolognani e...@kiyuko.org wrote: I am looking for a sponsor for my package scrotwm. The upload would fix these bugs: 514322 I would be glad if someone uploaded this package for me. I will review this package. The packaging repository has been made available under the collab-maint umbrella[1], and the package itself has been uploaded to mentors[2]. [1] http://bzr.debian.org/bzr/collab-maint/scrotwm/trunk This is empty. Did you forget to push your changes to bzr.d.o? Cheers, Giridhar -- Y Giridhar Appaji Nag | http://people.debian.org/~appaji/ signature.asc Description: Digital signature
Re: ITR: scrotwm - dynamic tiling window manager
On Mon, 18 May 2009 13:41:35 +0530 Y Giridhar Appaji Nag app...@debian.org wrote: I will review this package. Thank you very much. The packaging repository has been made available under the collab-maint umbrella[1], and the package itself has been uploaded to mentors[2]. [1] http://bzr.debian.org/bzr/collab-maint/scrotwm/trunk This is empty. Did you forget to push your changes to bzr.d.o? $ bzr log http://bzr.debian.org/bzr/collab-maint/scrotwm/trunk | wc -l 278 $ So no, the repository is definitely not empty ;) If you want to take a look at the contents from within your browser, the correct URL is [1]; I haven't used this URL in the Vcs-Browser field only because Loggerhead support on bzr.debian.org is marked as experimental. [1] http://bzr.debian.org/loggerhead/collab-maint/scrotwm/trunk/ -- Andrea Bolognani e...@kiyuko.org Resistance is futile, you will be garbage collected. pgpcxEzrY7k3J.pgp Description: PGP signature
Help with makefiles
I have a lot of manpages written in pod and instead of 15 lines in rules I want to have just 3. It's not quite working though =((( ./debian/rules -n build/manpages for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs vpl2mod vs2osisref tei2mod xml2gbs installmgr; do pod2man --release= --center -n `echo | tr '[a-z]' '[A-Z]'` debian/.1.pod (i).1 done ./debian/rules build/manpages for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs vpl2mod vs2osisref tei2mod xml2gbs installmgr; do /bin/sh: Syntax error: end of file unexpected make: *** [build/manpages] Error 2 Any suggestions? in acctual rules file tabs *are* present.. -- With best regards Dmitrijs Ledkovs (for short Dima), Ледков Дмитрий Юрьевич -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Help with makefiles
Dmitrijs Ledkovs wrote: I have a lot of manpages written in pod and instead of 15 lines in rules I want to have just 3. It's not quite working though =((( ./debian/rules -n build/manpages for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs ^ ; ? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
Re: Help with makefiles
[Eugene V. Lyubimkin, 2009-05-18] Dmitrijs Ledkovs wrote: ./debian/rules -n build/manpages for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs ^ ; ? ^ \ (\n escaped) ? -- http://people.debian.org/~piotr/sponsor -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Help with makefiles
Dmitrijs Ledkovs wrote: I have a lot of manpages written in pod and instead of 15 lines in rules I want to have just 3. It's not quite working though =((( ./debian/rules -n build/manpages for i in addld mkfastmod mod2imp osis2mod imp2gbs imp2ld imp2vs vpl2mod vs2osisref tei2mod xml2gbs installmgr; do pod2man --release= --center -n `echo | tr '[a-z]' '[A-Z]'` debian/.1.pod (i).1 done Are there newlines in the for-loop? They must be removed or replaced by a backslash in a Makefile: target: for i in whatever; do \ foo $i ; \ done Regards, Daniel -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: ITR: scrotwm - dynamic tiling window manager
On 09/05/18 10:52 +0200, Andrea Bolognani said ... On Mon, 18 May 2009 13:41:35 +0530 Y Giridhar Appaji Nag app...@debian.org wrote: [1] http://bzr.debian.org/bzr/collab-maint/scrotwm/trunk This is empty. Did you forget to push your changes to bzr.d.o? $ bzr log http://bzr.debian.org/bzr/collab-maint/scrotwm/trunk | wc -l 278 $ So no, the repository is definitely not empty ;) Indeed, false alarm. Thank you for clarifying :) Giridhar -- Y Giridhar Appaji Nag | http://people.debian.org/~appaji/ signature.asc Description: Digital signature
RFS: rkward
Dear mentors, I'm looking for a new sponsor for package rkward. My current sponsor, Roland Marcus Rutschmann in CC, would like to pass sponsoring for rkward to somebody who is actively using rkward, R or related packages on a regular basis. So, in the mid-term, I'm looking for a regular sponsor of rkward. In the short-term, I'm looking for someone to upload version 0.5.0d-3 of rkward, which fixes an FTBFS-bug in the last upload: #529024 rkward: FTBFS: error: X11/X.h: No such file or directory severity: serious The package can be found at http://rkward.sourceforge.net/debian/ . Description: a KDE frontend to the R statistics language RKWard aims to become an easy to use, transparent frontend to R, a powerful system for statistical computation and graphics. Besides a convenient GUI for the most important statistical functions, future versions will also provide seamless integration with an office-suite. . RKWard is still in development status. Right now it is most useful as an IDE to users with some experience in R, or willing to learn R. Regards Thomas Friedrichsmeier signature.asc Description: This is a digitally signed message part.
RFS: codeville - NMU
Hi, I've prepared an NMU that fixes some small RC bugs on codeville package, I've filled a follow-up to the bug report including the debdiff patch. Please, can someone make a review, and in case the upload? The package can be found on mentors.debian.net: - dget http://mentors.debian.net/debian/pool/main/c/codeville/codeville_0.8.0-1.1.dsc Best regards Francesco Namuri -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Dash and dot in package version
On Sun, May 17, 2009 at 8:18 PM, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: In 7337540c0905160100g59c1a3dem9f7622da6ca42...@mail.gmail.com, Ludovico Cavedon wrote: I think I'll go for 2.2~rc3+hg365+dfsg1 Just, IMO: I prefer 2.2~rc3+hg365~dfsg1 so that 2.2~rc3+hg365 would be greater than it. In this way, it would allow distribution of the same upstream without repacking for Debian by a non-Debian (or simply unofficial) group. I think yours is a good point. However, as observed Magnus: However, that won't work if you have already uploaded e.g. version 1.2-3 of a package, and then somebody files a bug that the tarball contains some non-free file, and you'd like to upload 1.2~dfsg-1 to fix it without waiting for a new upstream release. Thanks. Ludovico -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Dash and dot in package version
On Sat, May 16, 2009 at 1:00 AM, Ludovico Cavedon ludovico.cave...@gmail.com wrote: so I think I'll go for 2.2~rc3+hg365+dfsg1 Uhm, anyway, + sorts *before* ., so until next upstream release I must go with 2.2~rc3.hg365+dfsg1 Cheers, Ludovico -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: flowscan (updated package)
Dear mentors, I am looking for a sponsor for my package flowscan. * Package name: flowscan Version : 1.006-13 Upstream Author : Dave Plonka plo...@doit.wisc.edu * URL : http://net.doit.wisc.edu/~plonka/FlowScan/ * License : GPL-2 Section : net It builds these binary packages: flowscan - flow-based IP traffic analysis and visualization tool The package appears to be lintian clean. The upload would fix these bugs: 402663 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/f/flowscan - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/f/flowscan/flowscan_1.006-13.dsc I would be glad if someone uploaded this package for me. -- Kind regards Guillaume Delacour signature.asc Description: PGP signature
Re: Dash and dot in package version
In 7337540c0905181406k63858584r28dbd4883869c...@mail.gmail.com, Ludovico Cavedon wrote: On Sun, May 17, 2009 at 8:18 PM, Boyd Stephen Smith Jr. b...@iguanasuicide.net wrote: Just, IMO: I prefer 2.2~rc3+hg365~dfsg1 so that 2.2~rc3+hg365 would be greater than it. In this way, it would allow distribution of the same upstream without repacking for Debian by a non-Debian (or simply unofficial) group. I think yours is a good point. However, as observed Magnus: However, that won't work if you have already uploaded e.g. version 1.2-3 of a package, and then somebody files a bug that the tarball contains some non-free file, and you'd like to upload 1.2~dfsg-1 to fix it without waiting for a new upstream release. In that case +dfsg would be fine (.dfsg is problematic is upstream decides to release a 1.2.1), but you could change it to ~dfsg for the next upstream release. While there are always exceptions, I use the following guidelines: Reserve '.' and digits to upstream. Use + as a decoration when it a a debian addition (e.g. pull from more recent VCS revision). Use ~ as a decoration when it is a debian removal (e.g. DFSG cleaning). '~alphaN', '~betaN' and '~rcN' conveniently sort the way they should, so you can use $next_upstream_version followed by them or just treat them like VCS snapshots. Still, what version you use should be guided by functionality (how does it sort) rather than pretty stuff. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: RFS: wbar (4th try)
Hi Krzysztof, sorry for this late reply On Sat, May 9, 2009 at 13:20, Krzysztof Burghardt krzysz...@burghardt.pl wrote: 2009/4/18 Sandro Tosi mo...@debian.org: - no need for 'a ' in the short description Removed. - long descriptions is a little too short maybe? (dunno, it's just a feeling it's a merge of short sentences taken from website and package description) That's right. I just add annother short sentence to make it a bit longer ;-) - you have to add the repack script, for example debian/repack.sh, and add it as parameter to debian/watch file. Done. - from where did you inferred 2007 as copyright years? Only 2006 is clearly stated as copyright year for the code. Changed to 2006. - without config file it's doesnt start: $ wbar Can't stat a config file. Try # make install or -config cfgfile Fixed by including simple configuration file in wbar config search path. Now should work. sadly no (and I was really about to upload the package): $ wbar Using /usr/share/wbar/dot.wbar config file. Using a Super Bar. /usr/share/icons/hicolor/48x48/apps/pidgin.png - Couldn't load icon image. $ wbar --config /usr/share/doc/wbar/examples/dot.wbar Using /usr/share/doc/wbar/examples/dot.wbar config file. iconpack/wbar.osx/osxbarback.png - Image not found. Maybe using a relative path? I suppose there's something else to adjust here. and since we are at it, there is a small typo in long description s/its/it's/ and you can experiment with the rules.tiny file for debian/rules since you're using a pretty straight debhelper template, you can use teh new dh7 short rules format. Let me know if you need some clarification. Cheers, -- 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: subtitlecomposer (new package, second try)
Dear mentors, I am looking for a sponsor for my package subtitlecomposer. * Package name: subtitlecomposer Version : 0.5.2-1 Upstream Author : Sergio Pistone sergio_pist...@yahoo.com.ar * URL : http://sourceforge.net/projects/subcomposer * License : GPL-2+ Section : kde Programming Language: C++ It builds these binary packages: subtitlecomposer - subtitles editor for KDE 4 The package appears to be lintian clean. The upload would fix these bugs: 516372 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/subtitlecomposer - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/subtitlecomposer/subtitlecomposer_0.5.2-1.dsc I've uploaded this package again because I noticed there was an important bug with the video which I've fixed, see changelog. I would be glad if someone uploaded this package for me. Kind regards José Manuel Santamaría Lema
Re: architecture wildcards, type-handling, etc.
Hello Salvatore, On Thu, 14 May 2009 19:25:46 +0200, Salvatore Bonaccorso wrote: Dear reader of debian-mentors, I read the following, following a discussion on debian-devel, which I do not understand. On Thu, May 14, 2009 at 04:26:56PM +0200, Cyril Brulebois wrote: brian m. carlson sand...@crustytoothpaste.ath.cx (14/05/2009): I've worked on FTBFS-with-new-GCC bugs before, and realized only after putting significant work into the bug that the package didn't build on amd64, only on i386. Therefore, I think that the package should have a proper list of archs that prevents this problem. P-a-s is fine for the buildds, but if you actually want people to volunteer to fix bugs on your package, you shouldn't make it harder on them. Which is why people are expected to: - Make their packages FTBFS ASAP in the build system, to make it obvious it's not intended to even be tried on $archs. - Then get the P-a-s entry added. Could that a bit be explainend? I do not understand the following: Assuming I have a package, which I know it is only working under i386 and amd64, but has the bug that it builds correctly on another architecture (but is then not usable there), does this mean, that I should not put only i386 and amd64 in Architecture field, but instead nevertheless let any by in the Architechture field, but then on build time, let the build fail on say powerpc? Many thanks Salvatore btw, what p-a-s mean in this context? p-a-s : dict say Publicly Available Specifications (ISO) I think this is the correct signification but i am not sure... For your main question, i am not sure but in Debian policy i remember that a FTBFS has to be forward to the upstream project (with or not a patch) and has to be integrated in the next version of the upstream package or stay in specific Debian patch (not the best solution). If upstream doesn't want to support other architecture (i don't see why ?), i think the two solutions are good technically, but only one is good according to Debian project goals : any... May be i am wrong and i am just a beginner in Debian, so advanced Debian programmers can take place and have another opinion on the problem. Best regards, Laurent. -- Laurent Guignard, Registered as user #301590 with the Linux Counter Site : http://www.famille-guignard.org Blog : http://blog.famille-guignard.org Projet : http://sicontact.sourceforge.net GULL de Villefranche sur Saône : http://www.cagull.org signature.asc Description: Digital signature
