Re: RFS: g3dviewer
Hi Sven, Thanks for your contribution to Debian! On Freitag, 27. November 2009, Sven Eckelmann wrote: I am looking for a sponsor for my package g3dviewer. Uploaded. Could you please ask the upstream author to publish signed checksums on his webpage, like he already does with libg3d? cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: RFS: g3dviewer
Holger Levsen wrote: Hi Sven, Thanks for your contribution to Debian! On Freitag, 27. November 2009, Sven Eckelmann wrote: I am looking for a sponsor for my package g3dviewer. Uploaded. Thanks for the fast upload. Could you please ask the upstream author to publish signed checksums on his webpage, like he already does with libg3d? I've sent him a mail and I am quite sure that he will do it. Best regards, Sven signature.asc Description: This is a digitally signed message part.
Re: Writing manpages (was: Re: Man and UTF-8.)
On Wed, Nov 18, 2009 at 05:30:33AM -0200, Rogerio Brito wrote: On Nov 17 2009, Roger Leigh wrote: However, TTBOMK UTF-8 manpages should be OK as well, though I have found some issues with more esoteric characters. I would suggest reporting bugs or contacting the maintainer or groff upstream if you run into problems here. OK, since the project strongly advises for the availability of manpages (and I love manpages), comes the question: what do you people use to type manpages? Using troff is simply nasty and hard, with all the typesetting getting in the way of seeing the content that one has typing (that's not to even mention the need to memorize the black magic-esque mnemonics). Just for the record (and I know I'm resurrecting an already pretty much closed discussion), I personally am quite used to writing mdoc manual pages. Well, okay, so that shows my FreeBSD alignment ;) But IMHO mdoc is a *lot* more readable (and writeable) than plain troff with the an macros. All the utilities that I've developed (e.g. confget, pslist, and timelimit in Debian) have their manpages in mdoc format, and when I need to write a manpage for something else, I use it too (like I converted the wmanager manpages to mdoc when I took over the package). Of course, I like both reST and POD too, it's just that mdoc is a bit closer to the manpage structure than POD, and reST just wasn't around ten years ago :) And I'm pretty much used to mdoc by now :) G'luck, Peter -- Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 This sentence every third, but it still comprehensible. pgp1Wfl6BAAfK.pgp Description: PGP signature
Re: RFS: roxterm (updated package)
On Sat, 28 Nov 2009 09:53:09 +0200 George Danchev danc...@spnet.net wrote: On Fri, 27 Nov 2009 21:39:25 +0200 George Danchev danc...@spnet.net wrote: Package looks good and 557049 seems to be addressed as well, at least works for me;-). JFYI I just run into some leftovers in the roxterm(1) and roxterm- config(1) manpages -- they both contain [FIXME: manual] and [FIXME: source], and these are also shown in the man browser too. This is not a huge problem per se, and the package in sid also has it, but I think you might want to know about it and address it further. I use that package and I'm willing to upload. Thanks. I've added the missing elements to the DocBook files the man pages are generated from, I hope they're OK now. This was an upstream change so I've uploaded a new version: - URL: http://mentors.debian.net/debian/pool/main/r/roxterm - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/r/roxterm/roxterm_1.16.2-1.dsc Good. It turns out that yesterday I had installed autotools-dev by accident in my supposed to be clean chroot, so I failed to spot the following failure (and manage to complete the whole check cycle including install/deinstall/running). checking whether i486-linux-gnu-gcc and cc understand -c and -o together... yes configure: error: cannot run /bin/sh ./config.sub make: *** [config.status] Error 127 dpkg-buildpackage: error: debian/rules build gave error exit status 2 Adding autotools-dev back to build-dependencies fixes it, OK, I've added that dependency back. I've duploaded a replacement, but I haven't changed the version number because I think it's better not to when it hasn't been released yet. I also tried running autotools-dev's autogen.sh, but that resulted in a lintian report: P: roxterm source: direct-changes-in-diff-but-no-patch-system po/Makevars.template so I thought I'd better avoid that for now. I'll replace my bootstrap.sh with it in future upstream versions though. however I wonder what were your considerations to remove it in the first place from there? I thought the autotools were supposed to generate self-contained tarballs. I must have got the wrong idea. -- TH * http://www.realh.co.uk -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: gnomad2 (updated package)
Dear mentors, I would adopt gnomad2 I am looking for a sponsor for the new version 2.9.4-1 of that package. It builds these binary packages: gnomad2- Manage a Creative Labs Nomad Jukebox The package appears to be lintian clean. The upload would fix these bugs: 494730, 557276 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gnomad2 - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gnomad2/gnomad2_2.9.4-1.dsc I would be glad if someone uploaded this package for me. Kind regards Alessio Treglia -- Alessio Treglia quadris...@ubuntu.com Ubuntu MOTU Developer | Homepage: http://www.alessiotreglia.com 0FEC 59A5 E18E E04F 6D40 593B 45D4 8C7C DCFC 3FD0 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RFS: twitim
Dear mentors, I am looking for a sponsor for my package twitim. * Package name: twitim Version : 1.3-2 Upstream Author : Yoshizumi Endo y-endo(at)ceres.dti.ne.jp * URL : http://code.google.com/p/twitim/ * License : GPL2 or later. Section : net It builds these binary packages: twitim - Twitter client for GNOME The package appears to be lintian clean. My motivation for maintaining this package is: Upstream Author create Debian/Ubuntu packages. I hope this package into Debian official distribution. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/twitim - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/twitim/twitim_1.3-2.dsc I would be glad if someone uploaded this package for me. Kind regards --- Youhei SASAKI uwab...@gfd-dennou.org Key fingerprint: 8BF1 ABFE 00D2 526D 6822 2AC6 13E0 381D AEE9 95F4 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: RFS: roxterm (updated package)
On Sat, 28 Nov 2009 09:53:09 +0200 --cut-- Adding autotools-dev back to build-dependencies fixes it, OK, I've added that dependency back. I've duploaded a replacement, but I haven't changed the version number because I think it's better not to when it hasn't been released yet. This is fine with me, this is now uploaded. Thank you. I also tried running autotools-dev's autogen.sh, but that resulted in a lintian report: P: roxterm source: direct-changes-in-diff-but-no-patch-system po/Makevars.template Because your diff.gz directly touches files outside debian/. I guess lintian does something like: lsdiff -z -x '*/debian/*' *.diff.gz so I thought I'd better avoid that for now. I'll replace my bootstrap.sh with it in future upstream versions though. Okay, however I wonder what were your considerations to remove it in the first place from there? I thought the autotools were supposed to generate self-contained tarballs. I must have got the wrong idea. They are self-contained unless config.sub and config.guess helper scripts got unexpectedly outdated. Rf: /usr/share/doc/autotools-dev/README.Debian.gz. -- pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu signature.asc Description: This is a digitally signed message part.
Re: RFS: gnomad2 (updated package)
Alessio Treglia wrote: Dear mentors, I would adopt gnomad2 I am looking for a sponsor for the new version 2.9.4-1 of that package. It builds these binary packages: gnomad2- Manage a Creative Labs Nomad Jukebox The package appears to be lintian clean. The upload would fix these bugs: 494730, 557276 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/g/gnomad2 - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/g/gnomad2/gnomad2_2.9.4-1.dsc I would be glad if someone uploaded this package for me. Kind regards Alessio Treglia Uploaded, thanks. Barry deFreese -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Graphviz 2.24.0
Hi Mentors, I've been working on upgrading the graphviz package to the latest 2.24.0 upstream version, primarily because I needed it while playing around with the ControlFlowGraph plugin for KDevelop4 (which I still haven't got working, but that's another story ... :-) At the time there was a RFH on the package, so I figured I'd tidy up what I'd done and let the maintainer take a look at it. However while I was getting around to it, Cyril orphaned the package. So now I'm thinking, since I've already done all this work and I've got a bit of an interest in the package, maybe I could pick it up? However, this would be the first library package I've done and it's not the simplest of packages - I don't want to bite off more than I can chew ;-) So, rather than jumping straight in with a ITA, I wonder if I could ask someone to take a look at what I've done and see if it looks OK? If it's not too far off the mark, I'd be interested in maintaining it. OTOH if the response is go away and come back when you know what you're doing then fair enough :-) Cheers, David. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Graphviz 2.24.0
David Claughton wrote: Hi Mentors, I've been working on upgrading the graphviz package to the latest 2.24.0 upstream version, primarily because I needed it while playing around with the ControlFlowGraph plugin for KDevelop4 (which I still haven't got working, but that's another story ... :-) At the time there was a RFH on the package, so I figured I'd tidy up what I'd done and let the maintainer take a look at it. However while I was getting around to it, Cyril orphaned the package. So now I'm thinking, since I've already done all this work and I've got a bit of an interest in the package, maybe I could pick it up? However, this would be the first library package I've done and it's not the simplest of packages - I don't want to bite off more than I can chew ;-) So, rather than jumping straight in with a ITA, I wonder if I could ask someone to take a look at what I've done and see if it looks OK? If it's not too far off the mark, I'd be interested in maintaining it. OTOH if the response is go away and come back when you know what you're doing then fair enough :-) Cheers, David. I'd probably help if I remembered to mention where you can get the package :-) I've uploaded it to mentors.d.n, so you can get it from the following URL : http://mentors.debian.net/debian/pool/main/g/graphviz Cheers, David. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Can /usr/share/doc/pkg be deleted on upgrade ?
Hi, Ben: On Saturday 28 November 2009 08:59:13 Ben Finney wrote: Jesús M. Navarro jesus.nava...@undominio.net writes: Not personal but sysadmin related. When I want to find information about a given package I go to /usr/share/doc/pkg so I find reasonable that the local sysadmin would add notes about the package right there if needed. No, I don't think that's reasonable. The ‘/usr’ hierarchy (with the important exception of ‘/usr/local’) should be considered entirely the province of the package management system; any files there can appear or disappear as dictated by the packages. The sysadmin's site-local files should be going under ‘/usr/local’, which *is* out of bounds for the package manager. Strongly questionable: notes about package emacs, installed via package manager might go under /usr/share/doc/emacs, why not. Less surprise path. That's the benefit of following standards like the FHS: there are places like ‘/usr’ that can be managed entirely by the package manager. Anyone surprised by that isn't following established convention. Quite a strong asumption given that FSH doesn't say a word *at all* about package managers. And what it says about /usr is: /usr is the second major section of the filesystem. /usr is shareable, read-only data. That means that /usr should be shareable between various FHS-compliant hosts and must not be written to. Any information that is host-specific or varies with time is stored elsewhere. regarding /usr/share it says: The /usr/share hierarchy is for all read-only architecture independent data files. So: a) Nothing is said about /usr being package manager's-only realm. b) Nothing prevents the administrator to peruse /usr/share/doc/ from including architecture-independent data regarding whatever is installed, specially if its about something root-based (in contrast to local-based). c) deleting whole directories disregarding their contents is not what Debian usually does. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Can /usr/share/doc/pkg be deleted on upgrade ?
On Sat, Nov 28 2009, Jesús M. Navarro wrote: Hi, Ben: On Saturday 28 November 2009 08:59:13 Ben Finney wrote: Jesús M. Navarro jesus.nava...@undominio.net writes: Not personal but sysadmin related. When I want to find information about a given package I go to /usr/share/doc/pkg so I find reasonable that the local sysadmin would add notes about the package right there if needed. No, I don't think that's reasonable. The ‘/usr’ hierarchy (with the important exception of ‘/usr/local’) should be considered entirely the province of the package management system; any files there can appear or disappear as dictated by the packages. The sysadmin's site-local files should be going under ‘/usr/local’, which *is* out of bounds for the package manager. Strongly questionable: notes about package emacs, installed via package manager might go under /usr/share/doc/emacs, why not. Why not? Because it is not safe, that's why. There is no guarantee made by Debian that your files shall not be stomped on, or that user data will be preserved. Less surprise path. That's the benefit of following standards like the FHS: there are places like ‘/usr’ that can be managed entirely by the package manager. Anyone surprised by that isn't following established convention. Quite a strong asumption given that FSH doesn't say a word *at all* about package managers. a) Nothing is said about /usr being package manager's-only realm. b) Nothing prevents the administrator to peruse /usr/share/doc/ from including architecture-independent data regarding whatever is installed, specially if its about something root-based (in contrast to local-based). c) deleting whole directories disregarding their contents is not what Debian usually does. But Debian also does not tell you that your file will be there with the next upload. If you name your file foo.txt, there is nothing that guarantees that the next version will not have an empty file called foo.txt in that dir in /usr. Nothing checks to see i there is a user file there. And, by the same token, when the next+1 version removes foo.txt, dpkg will happily remove it. So, the user is well advised not to trust any user data under /usr/share, should be using /usr/local anyway. Given that, while a trifle odd, I see nothing wrong in removing and recreating /usr/share/doc/pkg with every install. manoj -- Grinnell's Law of Labor Laxity: At all times, for any task, you have not got enough done today. Manoj Srivastava sriva...@debian.org http://www.debian.org/~srivasta/ 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[Future Icon Records] You've been added to our mailing list.
Hi I represent KONVICT MUSIC recording artist COLBY O'DONIS br/(Just Dance Ft Colby O'Donis. Beautiful Ft Colby O'Donis) br/and we want to share with you His first Originalbr/Christmas song br/ br/I made a radio edit of so happy br/here it is if you like itbr/Radio Edit Of - So Happybr/https://rcpt.yousendit.com/782608652/9a8972b464bfc006aa5139a89722060dbr/ br/Instrumental Radio Edit - So Happybr/https://rcpt.yousendit.com/782608822/4c2efde9129f9900fe9782387ef48410br/ Get your free download from Future Icon Records here: http://fburls.com/14-p2V4bpSX You have been added to the Future Icon Records fan list! If you would like to verify your info or add more to your fan profile, you can do so by clicking on the following link: http://www.FanBridge.com/signup/fansignup.php?userid=129853email=debian-ment...@lists.debian.orgconfCode=b2Pt5kFU1Kha45h475BbFKFr46 -- This list is powered by FanBridge, the world's leading provider of fan relationship management services for artists. With FanBridge your information is always secure. For more information about FanBridge please visit http://www.FanBridge.com/learn/ -- ***Important: Please be sure to add the email address (futureiconreco...@live.com) to your safe senders list.*** Here's how: Gmail 1. Click Contacts along the left side of any Gmail page. 2. Click Add Contact. 3. In the primary email address box, type futureiconreco...@live.com. 4. Click Save. AOL (version 9.0 or higher) 1. Click the Mail menu and select Address Book. 2. In the pop up box, click the Add button. 3. In the Other E-Mail field, type futureiconreco...@live.com. 4. Make our From address the Primary E-Mail address by checking the associated check box. 5. Click the Save button. AOL 8.0 1. Open this confirmation email. 2. Click Add Address. 3. Verify the sender's contact information (futureiconreco...@live.com). 4. Click Save. Yahoo! 1. Click the addresses button 2. Select Add Contact 3. Save the futureiconreco...@live.com to your contacts list. Hotmail 1. Click Options. 2. On the left side of the page, click Mail, and then click Junk E-Mail Protection. 3. Click Safe List. 4. Type futureiconreco...@live.com, and then click Add. Outlook 1. Right-click on a message from futureiconreco...@live.com. 2. Point to Junk E-mail, and click Add Sender to Safe Senders List. Future Icon Records sent this email to debian-mentors@lists.debian.org Questions? Contact futureiconreco...@live.com or Future Icon Records, c/o FanBridge, Inc. - 14525 SW Millikan Way, #16910, Beaverton, Oregon 97005, United States Update Your Information - http://fburls.com/42-2HxEwp1e Forward to a friend - http://fburls.com/1-73LcjAtD Unsubscribe - http://fburls.com/5-sJ3Pe2mi Privacy Policy - http://www.FanBridge.com/learn/privacy.php This email message is powered by FanBridge: http://www.FanBridge.com/b.php?id=129853 Powering Valuable Fan Relationships -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
