Bug#913493: RFS: geneweb/6.08+git20181019+dfsg-1
Le 27/12/2018 à 21:00, Guillaume Brochu a écrit : https://github.com/geneweb/geneweb/issues/642 Fixes ocaml warnings and correct English errors * New maintainer (Guillaume Brochu), Christian Perrier now in uploaders You can even remove me from Uploaders. I anyway need to ask this for the gazillion package where I'm listed, as part of a future resignation from Debian Merci encore pour ton travail !
Re: [Pkg-fonts-devel] pkg-fonts team needs help to maintain font-forge
Quoting Raphael Hertzog (hert...@debian.org): > Hello, > > looking at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745732 > which has been languishing for two years, it looks like the pkg-fonts > team could need some help to maintain this package. Vasudev Kamath, with the help of discussions with other team members (at least those that are really active, not /me) is currently making good progress but the work is complicated by licensing issues. He's trying to clarify in debian/copyright, and be as precise as possible about the various licenses used by source files for fontforge. From what I witnedd in the pkg-fonts-devel mailing list, this is really big work and we're aware that this slows down the packaging of new versions. Still, I'm confident that it can be achieved and, anyway, more help in the team would be very welcomed. signature.asc Description: PGP signature
Re: Package version numbers
Quoting Raphael Hertzog (hert...@debian.org): On Wed, 16 Jan 2013, Christian PERRIER wrote: Quoting Jakub Wilk (jw...@debian.org): I would paint the bikeshed the following color: 0.8.51+dfsg1-0.1 Isn't that missing the fact that this is a t-p-u upload, which is indeed the start of a wheezy branch? So something we were naming +wheezyfoo in the past and which we now name +deb70u1. It's not really relevant because sid has already diverged and has a higher (upstream) version. So 0.8.51+dfsg1-0.1 is acceptable IMO. Indeed. And the theoretical question of what if sid hadn't diverged wrt upstream is silly as this is a native package. Steve, problem solved, then..:). We were bikeshedding a bit too much. Merci, Raphaël. signature.asc Description: Digital signature
Re: Package version numbers
Quoting Jakub Wilk (jw...@debian.org): * Stephen Kitt st...@sk2.org, 2013-01-15, 23:27: The version of calibre in Wheezy is 0.8.51+dfsg-1; what should the update's version be? I'm purposefully not mentioning our ideas (one of them is obvious from the exchanges in the bug report, but is in all likelihood incorrect). I would paint the bikeshed the following color: 0.8.51+dfsg1-0.1 Isn't that missing the fact that this is a t-p-u upload, which is indeed the start of a wheezy branch? So something we were naming +wheezyfoo in the past and which we now name +deb70u1. The main problem is indeed the combination of a t-p-u upload and an NMU of a Debian native package. signature.asc Description: Digital signature
Bug#694459: Ping about #694352 and the proposed sponsored package in #694459
Hello Bastien, You offered a sponsored upload to fix #694352 but Michael Gilbert's review is right and I'm afraid that no DD would upload the proposed package until Michael suggestions are applied (at least, I wouldn't until the previous maintainer names removal from README.Debian isn't fixed). Is there any chance that you work on another proposed upload? -- signature.asc Description: Digital signature
Bug#685635: RFS: fonts-pecita/3.4-1 - RFS bug 685635
Quoting pecita.net Archive Automatic Signing Key (packa...@pecita.net): Christian, I got a problem with debexpo. I deleted the package to be able to reload a new one but now I receive a 403 Forbidden first for the orig file then for all. Because the orig file is already on the server, I guess.. I never did that on the mentors upload queue, but the error message you get mentions using dcut(1): Good signature on /home/philippe/Packages/debian/fonts-pecita_3.4-2.dsc. Uploading to mentors-ftp (via ftp to mentors.debian.net): Uploading fonts-pecita_3.4-2.dsc: 553 Could not create file. Leaving existing fonts-pecita_3.4-2.dsc on the server and continuing NOTE: This existing file may have been previously uploaded partially. For official Debian upload queues, the dcut(1) utility can be used to remove this file, and after an acknowledgement mail is received in response to dcut, the upload can be re-initiated. Uploading fonts-pecita_3.4.orig.tar.bz2: 553 Could not create file. Leaving existing fonts-pecita_3.4.orig.tar.bz2 on the server and continuing NOTE: This existing file may have been previously uploaded partially. For official Debian upload queues, the dcut(1) utility can be used to remove this file, and after an acknowledgement mail is received in response to dcut, the upload can be re-initiated. Uploading fonts-pecita_3.4-2.debian.tar.gz: 553 Could not create file. You probably want to get the upload queue cleaned out, then re-upload (preferrably the -1 version). Alternatively, point me to the whole stuff (or send it to me as a big ZIP file) and I'll rebuild and upload. signature.asc Description: Digital signature
Bug#685635: RFS: fonts-pecita/3.4-1
Quoting pecita.net Archive Automatic Signing Key (packa...@pecita.net): Le dimanche 26 août 2012 à 18:18 +0200, Christian PERRIER a écrit : Quoting pecita.net Archive Automatic Signing Key (packa...@pecita.net): Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package fonts-pecita Can you give me the sponsoring bug number? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685635 OK, CC'ing the bug number now. Also, notice that Debian is in freeze, so this package will not enter wheezy as this is a new upstream version. Uploading to unstable is OK, but in case the package *currently in unstable* has a release critical bug, we'll have trouble updating it (that will need an upload to testing-proposed-updates). So, I would recommend uploading to experimental for now. Experimental is OK : the goal is to inform Debian of the last state of the font, with hide improvements and the addition of the Macedonian Alphabet ( http://pecita.eu/police-mk.php ). (However there is absolutely no chance that the font has a release critical bug!) You never know..:). That might be a packaging bug or whatever..:) So, if we go for experimental, you need to adapt debian/changelog a bit: fonts-pecita (3.4-1) unstable; urgency=low should become fonts-pecita (3.4-1) experimental; urgency=low Question, please! Does a Watch file automate the upgrade of the font ? In case yes, let me rebuild the package. No, no automatic update (too dangerous). It actually updates the package status in the package tracking system (http://packages.qa.debian.org/fonts-pecita) -- 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/20120826182149.gw5...@mykerinos.kheops.frmug.org
Bug#684106: Bug#682274: New LedgerSMB Debian package, v1.3.21-1
Quoting Robert James Clay (j...@rocasa.us): On Mon, 2012-08-06 at 22:11 -0400, Robert James Clay wrote: To access further information about this package, please visit the following URL: http://mentors.debian.net/package/ledgersmb Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/l/ledgersmb/ledgersmb_1.3.21-1.dsc Besides uploading the new package version to the Mentors site, I went ahead submitted a Request for Sponsor bug as well (#684106 [1]) because I don't know how busy you might be at the moment. If you can take care it, though, I'd appreciate it as you're more familiar with it than someone else might be. Just in case Raphaël can't upload, I can do it. But I'd prefer doing so as a backup only and keep Raphaël as main sponsor (because he is, IIRC, a user of LedgerSMB in hiw own business). As this is a new upstream version, a good argument (with patches, etc.) has to be prepared for the release team to have elements for their decision about allowing it in wheezy. I think a pre-approval by them would even be preferrable. signature.asc Description: Digital signature
Bug#667088: [Pkg-fonts-devel] Bug#667088: RFS: fonts-quattrocento/1.1-1 [ITP]
Quoting Bernhard Reiter (ock...@raz.or.at): Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org Yay, you got it right..:-) I added this to my TODO list. signature.asc Description: Digital signature
Bug#663885: [Pkg-fonts-devel] Bug#663885: RFS: googlefontdirectory-tools/20120309.1-1
Quoting Martin Erik Werner (martinerikwer...@gmail.com): Please upgrade to lintian 1.5.6, see my initial post for more info ;) Ahh, oops, overread that..:-) (well, my build chroot is supposed to be updated every day but the local mirror I use has indeed trouble nowadays : it not longer fitsin my server's disk space and I'm probably a bit outdated in these build chroots) signature.asc Description: Digital signature
Bug#663885: [Pkg-fonts-devel] Bug#663885: RFS: googlefontdirectory-tools/20120309.1-1
Quoting Martin Erik Werner (martinerikwer...@gmail.com): Package: sponsorship-requests Severity: normal X-Debbugs-CC: pkg-fonts-de...@lists.alioth.debian.org thanks Dear mentors and pkg-fontsers, I am looking for a sponsor for my updated package googlefontdirectory-tools. E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/bbox/vmet.pe) N: N:You used an interpreter for a script that is not in an essential N:package. In most cases, you will need to add a Dependency on the package N:that contains the interpreter. If the dependency is already present, N:please file a bug against Lintian with the details of your package so N:that its database can be updated. N: N:In some cases a weaker relationship, such as Suggests or Recommends, N:will be more appropriate. N: N:Severity: important, Certainty: possible N: N:Check: scripts, Type: binary N: E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/menusubset/menusubset-khmer.ff) E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/menusubset/menusubset-korean.ff) E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/menusubset/menusubset-kufi.ff) E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/menusubset/menusubset-naskh.ff) E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/menusubset/menusubset-thai.ff) E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/menusubset/menusubset-vietnamese.ff) E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/merge/merge.ff) E: googlefontdirectory-tools: missing-dep-for-interpreter fontforge = fontforge (usr/share/googlefontdirectory-tools/tools/ttf2sfd/ttf2sfd.ff) b These are probably not important scripts but, still, Suggests: fontforge would IMHO be appropriate. signature.asc Description: Digital signature
Re: Help updating debian/templates
Quoting Nick Leverton (n...@leverton.org): Hi, I want to add some additional examples to the debconf templates in my package nullmailer. The examples would only change config file entries (for the nullmailer/relayhost entry), and shouldn't need translating - they would be the same in all languages. I note that if I run debconf-updatepo, my updated template gets amended into all extant .po files, and they all get marked as fuzzy. Is this all I need to do, or do I have to notify anyone or do anything about the fuzziness ? I originally posted this to debian-mentors but then I realised that debian-i18n is perhaps more appropriate, so apologies for the multi-posting. Please CC me from -i18n as I'm not subscribed to it, thanks. It would really help if you could post the original templates file and the modified one so that we can give you advices abou tthe best course of actions. signature.asc Description: Digital signature
Re: proposed new pseudo-package 'debian-mentors' for handling sponsoring requests
Quoting Ansgar Burchardt (ans...@debian.org): SUMMARY === snip As someone who often sponsors packages (mostly related to packaging teams I'm part of, sometimes for l10n-related stuff, sometimes because someone I know just asked me about this and I fee like I have enough knowledge to decide about the package being OK to sponsor), I wholeheartedly welcome this proposal. It is obviously well designed and easy to follow. Maybe someone will find a minor detail to adapt here or there, but I see no reason to block in any way its adoption. Contragulations to everybody involved in the proposal design. That's really great job. signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: googlefontdirectory-tools
Quoting Martin Erik Werner (martinerikwer...@gmail.com): Hi, I am looking for a sponsor for my package googlefontdirectory-tools. Just checked, built, checked...and uploaded. Thanks for your work! signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: googlefontdirectory-tools
Quoting Martin Erik Werner (martinerikwer...@gmail.com): Hi, I am looking for a sponsor for my package googlefontdirectory-tools. I added this to my TODO list. As usual with /me, it might take some time to be processed (take time for builds, checks, etc.) but I have no other objection to this package to be uploaded in the archive. Not even package name changes suggestions..:-) signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] Sponsor for the Font Pecita
Quoting Maison en a Pecita (acquado...@gmail.com): TY Christian for the time that you spent on my package. I sent a correction, as follow... 1) Lintian My understanding of English let me looking these sentences as Chinese. I modified version and description. You can try to run lintian on your package lintian -i foo.changes In case you have doubt, feel free to ask for advice in private in French, as I understand you're French (or at least French speaker)which I happen to be too...:) 2) /usr/share/fonts/opentype/pecita: yes, true, done. 3) build-stamp: If you say! I suppressed it and hope the package is still instalable??? Not exactly. What I didn't understand the purpose of was: cd build; cp ../Pecita.otf ./ 4) I give the source on http://pecita.eu/f/Pecita.sfd but there is no connotation with the package. Could be interesting to include it in an upstream tarball (along with the OTF file, a copy of the SIL licence and maybe even a Makefile allowing to build the otf file from source with Fontforge). That's more a job that you can do it as upstream. I hope it suits you: je suis au taquet'. Do not ask me anything more :§ Another option could be focusing on your font design job and ask to the fontpackaging team to maintain the Debian (and therefore Ubuntu) package. We can quite easily do this..:-) I can try to spend some time on this after Christmas/New Year holidays. And /me also wonders how to say je suis au taquet in English, by the way..:) signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] Sponsor for the Font Pecita
Quoting Maison en a Pecita (acquado...@gmail.com): Hello. I am looking for a Sponsor for my font. A few comments: - you may want to fix the current lintian warnings: W: fonts-pecita source: native-package-with-dash-version W: fonts-pecita source: debian-rules-missing-recommended-target build-arch W: fonts-pecita source: debian-rules-missing-recommended-target build-indep W: fonts-pecita source: out-of-date-standards-version 3.8.4 (current is 3.9.2) E: fonts-pecita: helper-templates-in-copyright W: fonts-pecita: extended-description-line-too-long W: fonts-pecita: extended-description-line-too-long W: fonts-pecita: maintainer-script-empty prerm W: fonts-pecita: maintainer-script-empty preinst W: fonts-pecita: maintainer-script-empty postinst Most are minor but starting a package by being lintian-clean is a good habit to have..:-). Most of these are easy to fix. I would also recommend using /usr/share/fonts/opentype/pecita instead of /usr/share/fonts/opentype/fonts-pecita instead I also don't really understand the need for the following in debian/rules: build-stamp: configure-stamp dh_testdir mkdir build cd build; cp ../Pecita.otf ./ Indeed, this package is a very good candidate for having a one-liner dh7-style debian/rules. You may want to look at one of the many font packages maintained by the team. Apart from these technical concerns, the font seems really interesting. Do you intend to release the source code for it (I did not find how you designed it)? I think it is probably a very good case study for someone who would be interested in creating a font. Vraiment très intéressant..:-) signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: fonts-play
Quoting Martin Erik Werner (martinerikwer...@gmail.com): Dear mentors and pkg-fontsers, I am looking for a sponsor for my package fonts-play. The package is now ready for upload on my build machine (this is the verion you corrected after Paul Wise comments). Without objections, I'll upload it during the week-end. signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: fonts-play
(CC'ing you just in case, though I think you're subscribed to pkg-fonts-devel) Quoting Martin Erik Werner (martinerikwer...@gmail.com): Dear mentors and pkg-fontsers, I am looking for a sponsor for my package fonts-play. I added it to my TODO list as I'm now sponsoring most of the font packages maintained under the team's umbrella. Please feel free to ping me in case it falls under the pile...:) Interesting that you used git for packaging. I think it opens the opportunity for those in the team who would like to use it rather than SVN (which is used for other packages maintained by pkg-fonts), to switch to git. Help in importing the current SVN repo in git would be appreciated. Most font packages in pkg-fonts SVN use an svn-buildpackage style layout. signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: ttf-takao (NEW)
Quoting Jun Kobayashi (jk...@ubuntu.com): If OK, then feel free to provide us with your login on alioth.debian.org (of course, create one if you don't have one already). To answer another question of yours in this thread, the source and patches for otf-ipafont can be found in the pkg-fonts SVN tree. I've created my account jkbys-guest. I would be grateful if you add me to the pkg-fonts team. Done. Welcome on board signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: ttf-takao (NEW)
Quoting Jun Kobayashi (jk...@ubuntu.com): Thank you for your advice. I agree with the both. I'll read the documents linked from http://pkg-fonts.alioth.debian.org/. If OK, then feel free to provide us with your login on alioth.debian.org (of course, create one if you don't have one already). To answer another question of yours in this thread, the source and patches for otf-ipafont can be found in the pkg-fonts SVN tree. signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: ttf-takao (NEW)
Quoting Jun Kobayashi (jk...@ubuntu.com): Dear mentors, I am looking for a sponsor for my package ttf-takao. Apart from licensing comments that followed up, would you agree to maintain the font package under the pkg-fonts team umbrella. It basically means using our SVN to store the packaging tree (of course, you would be added as a team member) and optionnally add the team as Maintainer. The main point is that font packages are often similar and using similar packaging techniques as well as using the team ML as a convenient way to discuss about the packaging, is likely to benefit both parties (yourself by bringing the team's combined knowledge and the team by bringing more new blood in it..:-)) signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: otf-ipaexfont (NEW)
Quoting Hideki Yamane (henr...@debian.or.jp): Now I've uploaded fixed one, could you review it again? I haven't followed this very closely but is it OK to upload the fixed package now? I can do it (I guess that the previous pointer to the .dsc file is the right one) but prefer asking before doing it. As you may have noticed, my involvment in pkg-fonts has lowered slightly in the recent weeks after the rush in late 2009 (only temporary, no intent to give up on my side). signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: ttf-aoyagi-soseki (Japanese brush font package)
Quoting Asheesh Laroia (ashe...@asheesh.org): It builds these binary packages: ttf-aoyagi-soseki - Brush-style Japanese font I hope someone from the Debian Fonts Task Force picks this up! I'm swamped currently. Yep. I did put this in my pile of things to do. signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: ttf-aoyagi-kouzan-t -- Brush-style Japanese font
Hideki Yamane a écrit : Dear mentors, I am looking for a sponsor for my package ttf-aoyagi-kouzan-t. Uploaded. Congrats for that yet another great work. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [Pkg-fonts-devel] RFS: otf-yozvox-yozfont
Quoting Hideki Yamane (henr...@debian.or.jp): Dear mentors, I am looking for a sponsor for my package otf-yozvox-yozfont. I'll upload it (as part of the pkg-fonts team, where Yamane-san is doing great job). signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: ttf-sil-gentium (release-goal bug fix)
Quoting Nicolas Spalinger ([EMAIL PROTECTED]): [..] I will include your changes in the current pkg-fonts team-maintained packaging tomorrow. Theppitak's work is integrated in a updated package available on: http://mentors.debian.net/debian/pool/main/t/ttf-sil-gentium/ttf-sil-gentium_1.02-7.dsc (The work is also in our team svn). H: ttf-sil-gentium (20081126:1.02-7) unstable; urgency=low * preinst: Clear obsolete conffile. (Closes: #455109). (Thanks to Theppitak Karoonboonyanan) Missing blank line somewhere... signature.asc Description: Digital signature
Re: [Pkg-fonts-devel] RFS: ttf-rufscript
Quoting Andrew Starr-Bochicchio ([EMAIL PROTECTED]): Dear mentors, I am looking for a sponsor for my package ttf-rufscript. * Package name : ttf-rufscript Version : 010-1 Upstream Author : Hiran Venugopalan [EMAIL PROTECTED] * URL : http://hiran.in/blog/rufscript-font * License : GPL-3 + Font exception Section : x11 It builds these binary packages: ttf-rufscript - a handwriting based font for Latin characters The package appears to be lintian clean. The upload would fix these bugs: 502645 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/ttf-rufscript - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/ttf-rufscript/ttf-rufscript_010-1.dsc I would be glad if someone uploaded this package for me. Would you mind joining the pkg-fonts project on Alioth, the mailing list and include your package in the SVN there? Having all font packages being team-maintained i snot mandatory, far from that...but this is encouraged and even if the team is fairly loose, having such (often simple) packages team-maintained will help in long term... signature.asc Description: Digital signature
[TAF] po://ikiwiki/fr.po 51u
Quoting Christian Perrier ([EMAIL PROTECTED]): Le paquet Debian natif ikiwiki est incomplètement traduit en français. Jean-Luc semble indisponible. Cette traduction peut donc être reprise par quelqu'un d'autre. signature.asc Description: Digital signature
Re: Bangladesh Key-Signing completed - Debian Maintiner base can now be extended there.
Quoting salahuddin pasha ([EMAIL PROTECTED]): hello all i am salahuddin pasha (also known as salahuddin66) 19 male from Bangladesh, Dhaka interested both in --- 1. Bengali localisation 2. maintain apps (deb) for Debian. --- one of my dream was join in Debian group (officially) I think you really should join the debian-in-workers mailing list (http://lists.alioth.debian.org/mailman/listinfo/debian-in-workers) Here are gathered most of the people working on Indic languages support in Debian, including of course localization (Localization of Debian Installer in Bengali has started) Unless you already joined, of course..:-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
