Re: O:html2text
Hi, Before doing the NMU, have you contacted Eugene, the current maintainer? Thanks for heads-up, Thomas. I have created a package fixing the build error relating to hardening support http://mentors.debian.net/debian/pool/main/h/html2text/html2text_1.3.2a-16.1.dsc I am not sure if I really want to adopt this package, but this fixes some issues and cleaning of the package and of course the issue I mentioned above. I can't upload it, since I am not a DM but if anybody wants to check it out and upload it, then you are free to do so. This package was once labeled as RFH, so I intended to help, but it seems to be up for adoption at the moment Thanks for caring. As was pointed out, proposed changes are indeed too big and diversified for NMU. The package indeeds needs new maintainer, so feel free to adopt it, they you are free to make these and other changes if you want. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux userspace developer, Debian Developer -- 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/20130512160824.GB26830@debian-w500.Elisa
Bug#692923: RFS: chrony/1.24-3.2 [RC, NMU]
Hi Joachim, On 2012-11-10 22:10, Joachim Wiedorn wrote: chrony (1.24-3.2) testing-proposed-updates; urgency=medium * Non-maintainer upload. * Fix: Remove obsolete test of kernel version (rtc_linux.c) to run for kernel versions 3.0 and higher. Nowadays all kernel versions have RTC support (solves #642209 for version 1.24). Closes: #642209 -- Joachim Wiedorn ad_deb...@joonet.de Sat, 10 Nov 2012 19:19:19 +0100 Thank you for caring for RC bugs. Just like Timo said, this patch doesn't fix this (RC) problem. Fix would be: either apply the same idea (#if 0) to sys_linux.c or backport the upstream patch [1]. Please prepare the new upload with tested fix, new version string and proper Closes, and someone will surely upload it. [1] http://git.tuxfamily.org/chrony/chrony.git/?p=chrony/chrony.git;a=blobdiff;f=sys_linux.c;h=24f027c3b58663d290a59c36f09c31ba9e8c0c1f;hp=441e6e42c63868f621975c4c6ebf6f7e58c768fa;hb=ec7d302a6ca9e7974a05d338267b40491a1d7abb;hpb=8cc7ebffa91152d94b86247106e3fafe49600fc9 -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux userspace developer, Debian Developer -- 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/20121114170827.GA22915@r500-debian
Re: modifications by sponsors
Hi, On 2012-07-11 11:34, Bart Martens wrote: I have the following questions about sponsorship. I would like to welcome answers from sponsors and from people maintaining packages via sponsorship. Is it OK that a sponsor adds modifications to a sponsored package ? Is it OK that a sponsor adds him/herself to Uploaders ? My answers are currently no and no, but there may be different opinions. My answers are no, never and no unless sponsor maintains the package. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux developer, Debian Developer -- 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/20120711144626.GA7554@r500-debian
Bug#678594: RFS: driftnet/0.1.6+cvs20040426-1 [ITA] [RC] (second try: documented upstream repackaging and updated man file)
Hi David, On 2012-06-29 01:01, david.sephi...@gmail.com wrote: Sorry, Im not English native. No big problem, neither am I. [...] My intention is take over the development of driftnet but I tried to contact Chris Lightfoot, the upstream author, and I notice that he dead some years ago. About this situation, I have a question: If i create a new fork (that i want to develop and maintain), can it be uploaded to the debian archive as if it were the original driftnet package ? I don't have a strong opinion about that, but I think we can follow the libc example: source package name to be changed to the name of the fork but binary package name to be the same. This was the question for the future, for now I can upload your currently proposed changes. Note, if you choose me as sponsor, I require bumping Debian revision after each package review (if there any changes, of course). Ok, the next upload that fixes the two points discused above will be driftnet/0.1.6+cvs20040426-2. Good. Another point which I now noticed is that you want to lowercase the short description: s/Picks out/picks out/. So, please fix that, add Vcs-* headers, fix changelog corrections above and I'll upload the package. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux developer, Debian Developer -- 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/20120629085943.GB6941@r500-debian
Bug#678594: RFS: driftnet/0.1.6+cvs20040426-1 [ITA] [RC] (second try: documented upstream repackaging and updated man file)
Hi, On 2012-06-29 14:24, david.sephi...@gmail.com wrote: Good. Another point which I now noticed is that you want to lowercase the short description: s/Picks out/picks out/. So, please fix that, add Vcs-* headers, fix changelog corrections above and I'll upload the package. OK, thanks for point out the typos :) driftnet/0.1.6+cvs20040426-2 uploaded, you can find it at: http://mentors.debian.net/debian/pool/main/d/driftnet/driftnet_0.1.6+cvs20040426-2.dsc First, under 'bumping revision' I meant leaving previous -1 changelog entry intact (except of grammatic fixes), and starting new -2 entry, with mentioning latest changes you did (Vcs-* and lowercasing short description). Think of it as you'd prepare a new version for official Debian archive. My view is 'don't ever rewrite the history, except of fixing non-normative things like indentation or typos or grammar fixes'. Note, again, above are my preferences, other people may prefer other schemes. Secondly, Vcs-* should point to your packaging (Git, as I understood) repository, not upstream. Or is your packaging repository not public? Then don't add any Vcs-* fields for now. Since you uploaded -2 already, I now want -3. Leave your original -1 changes (only apply grammar fixes to them) under -1, make new -3 changelog entry, and document all your changes which you made after my review in it (probably it'd nice to mention that you applied some fixes to the previous changelog entry). Because the next mayor change I will implement is to add ipv6 support (currently I have patch for it but Im still testing and working on it) and I dont want to piss off the Chris work, Im thinking about to rename the fork 'drfitnet6'. About that I have a pair of questions: - Can i maintain the current version numbering of the original driftnet package and start working in the fork from it ? This is not for Debian or me to decide, but I personally think you can use whatever version scheme you want. - Can debian provide with git repositories in that I can host the package and the upstream code ? Since upcoming upstream code is not specific to Debian, I'd maintain it at some neutral shared service, such as Github or Bitbucket. As for Debian packaging, you can use Alioth [1], or alternatively just keep it at the same service where upstream code will be located. [1] http://alioth.debian.org/ -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux developer, Debian Developer -- 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/20120629135027.GF6941@r500-debian
Bug#678594: RFS: driftnet/0.1.6+cvs20040426-1 [ITA] [RC] (second try: documented upstream repackaging and updated man file)
On 2012-06-29 16:11, david.sephi...@gmail.com wrote: And whats for the -2 entry ? Since there is nothing to put into, just don't add it. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux developer, Debian Developer -- 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/20120629142149.GG6941@r500-debian
Bug#678594: RFS: driftnet/0.1.6+cvs20040426-1 [ITA] [RC] (second try: documented upstream repackaging and updated man file)
Hi David, On 2012-06-28 14:43, david.sephi...@gmail.com wrote: Dear mentors, I am looking for a sponsor for my package driftnet [...] * Imported Upstream version 0.1.6+cvs20040426 * New maintainer (closes: #616451) * Fix memstr() implementation non-working on 64bit systems (closes: #677623) * Make driftnet read from pcap file (closes: #647949) * Replace libpng12-dev build-dep with libpng-dev (closes: #662304) * Update standards version 3.9.3 * Update debhelper version 9.0 * Switch to dpkg-source 3.0 (quilt) format * Do not delete temporary files in adjunct mode as especified in help * Fix ifndef hidding needed values for non-gtk operation * Prevent backtrace due to unneccessary xfree on tmpdir * Update man file Your changes look fine as for me (module corrections above, s/hidding/hiding/, s/especified/specified/, s/non-working/to work/). Two questions: 1) Where is the Git repository which is mentioned a couple of times in your packaging? You probably want to to add Vcs-* headers to debian/control. 2) The package looks very old. Are you new upstream for it? Or did you find some newer fork which will use as base? Or do you intend just to maintain latest upstream CVS snapshot? Note, if you choose me as sponsor, I require bumping Debian revision after each package review (if there any changes, of course). -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++ GNU/Linux developer, Debian Developer -- 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/20120628134810.GA6941@r500-debian
[done] Re: RFS: pidgin-privacy-please
Hi Stefan, On 2012-05-15 17:40, Stefan Ott wrote: I am looking for a sponsor for my package pidgin-privacy-please. * Package name : pidgin-privacy-please Version : 0.7.1-1 Upstream Author : Stefan Ott * URL : http://pidgin-privacy-please.googlecode.com/ * License : GNU GPLv3 Section : net Uploaded. You can contact me directly for future updates of this particular package. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20120515172352.GC21506@r500-debian
[done] Re: RFS: unetbootin (New upstream release)
Hi, On 2012-01-29 02:02, Muneeb Shaikh wrote: http://mentors.debian.net/debian/pool/main/u/unetbootin/unetbootin_568-1.dsc Uploaded. The Git repository is at: http://git.debian.org/?p=collab-maint/unetbootin.git;a=summary Btw, it doesn't work for me right now. P.S. You can me directly for subsequent upload requests. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20120129104130.GC900@r500-debian
Re: RFS: boot-repair
Hello, [ I don't intend to upload this package ] On 2011-12-30 11:14, yannubu...@gmail.com wrote: and i read that Canonical plans to integrate it into Ubuntu 12.04 CD (i think deadline is mid-January) Why Debian as project should care about deadlines of some commercial companies? Quick solution: upload these 5 packages separately (Lintian clean): http://mentors.debian.net/package/boot-repair http://mentors.debian.net/package/clean http://mentors.debian.net/package/clean-gui http://mentors.debian.net/package/clean-ubiquity http://mentors.debian.net/package/os-uninstaller [...] Instead of writing about external companies and number of users, consider writing more interesting information in RFSes, such as what this software actually does. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20120102112629.GA31514@r500-debian
[done] Re: RFS: mmpong (updated package)
Hello, On 2011-12-11 17:03, Stephen M. Webb wrote: I am looking for a sponsor for my update of the package mmpong. This change updates the packaging standards-version and fixes a FTBFS bug (#624144). [...] http://mentors.debian.net/debian/pool/main/m/mmpong/mmpong_0.9.1-2.dsc Uploaded. In the next upload you might like to add yourself to Uploaders and restore debian/patches/01_share.dpatch by converting it to the quilt patch. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20111217103212.GC9936@r500-debian
Re: RFS: unetbootin
Hello Arno, On 2011-12-10 20:00, Arno Töll wrote: On 10.12.2011 19:19, Eugene V. Lyubimkin wrote: This is generally not a valid reason. For example, this makes it impossible to build the package on the system which has debhelper v7 installed, for no reason. Well, given that this requirement is fulfilled in Squeeze as is, and even newer backports are available to both, Squeeze and Lenny - despite of reaching end of life very soon for the latter that's not a strong argument. Yet this a regression, despite it's tiny size. It is perfectly fine for me if you require debhelper 7 as a personal requirement to sponsor packages No, I'm fine with debhelper v6 or v8 or whatever else remotely sane, given it's actually used for something. The change in question bumped the version without changing debian/rules and debian/compat. That's useless, isn't it? but I disagree with you if you claim that there would be no reason to use debhelper 8 at all. I didn't say so, see above. I fail to see why we would need to keep compatibility forever, if there is newer, better stuff available where some legacy problems can be avoided entirely or worked around (that's what debhelper's compat level is for, after all). If your package does not fail to build when using a modern, recommended compatibility level, why not use it? While I don't propose to use the same compatibility level forever, that sounds like oh nice, my package builds correctly with new shiny g++ 4.6, let's bump a build-dependency. Even if it builds fine with, say, g++ 4.2. One more example: -8- $ cupt depends akregator | grep libc6 Depends: libc6 (= 2.1.3) -8- Lenny has libc6 2.7. The idea of compatibility levels is to keep compatibility with old crap which is known to be broken. Not the other way around. Huh? So, packages which had a debhelper compat level of 7 in some Lenny/Squeeze development time were fine because 7 was the recommended compat level but they suddenly became old crap which is known to be broken now? For more background about that principle please refer to [1] [1] http://lists.debian.org/debian-mentors/2011/07/msg00194.html Oh, thanks for the link. I agree with the whole initial mail. Plus, let me quote Joey Hess [2] from that thread: | and | v8 This is the recommended mode of operation. | | This qualification is there mostly to avoid people using v9 before it's | complete; the only non-recommended compat levels are v4 and below, | which are deprecated. | | As a point of comparison, the compat histogram for packages I | co-maintain is: | | 124 7 | 65 | 38 | 24 | 19 | 16 [2] http://lists.debian.org/debian-mentors/2011/07/msg00228.html -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20111211101141.GA3174@r500-debian
[done] RFS: unetbootin
Hi Muneeb, On 2011-12-11 05:16, Muneeb Shaikh wrote: Okay, According to the suggestion I have reverted back the change as it's not required. [...] http://mentors.debian.net/debian/pool/main/u/unetbootin/unetbootin_565-3.dsc The Git repository is at: http://git.debian.org/?p=collab-maint/unetbootin.git;a=summary Uploaded. Thanks. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20111211105706.GB3174@r500-debian
bumping debhelper build-depends/compat (was: Re: RFS: unetbootin)
Hello, On 2011-12-11 16:21, Arno Töll wrote: Debhelper's compatibility level is an orthogonal approach. It's a promise that your build procedures do _not_ break when using certain features. If you are building a package with debhelper 8.9.something installed which has, say, debhelper compat 4, debhelper disables certain features, behaviors and so on it would use or enforce otherwise. [...] Right. Hence, I advertise people to use debhelper compat 8 in source packages where a package is known to work in that compatibility level. It does not mean Hey, my package needs debhelper 8.x, but My package is known to work with debhelper 8. [...] That's something I fine with, though didn't see such packages. But 'bumping a version in build-depends without bumping debian/compat and without using specific features in debian/rules' is another case. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20111211175904.GC3174@r500-debian
Re: RFS: unetbootin
Hi Muneeb, On 2011-12-08 03:50, Muneeb Shaikh wrote: dget -x http://mentors.debian.net/debian/pool/main/u/unetbootin/unetbootin_565-1.dsc 1) you bumped debhelper build-dependency version from 7 to 8, why? Also, changes like this should be always documented in debian/changelog. 2) you removed a build-dependency version of libqt4-dev (which was = 4.2). That's fine, but should me mentioned in the debian/changelog, preferrably with a short explanation why it should be safe. The Git repository us at: http://git.debian.org/?p=collab-maint/unetbootin.git;a=summary By the way, it's good you use a repository, but it's not good you merged all your debian/ changes into a single commit which is not easier to review than a .dsc. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20111210095304.GA6928@r500-debian
Re: RFS: unetbootin
On 2011-12-10 18:54, Muneeb Shaikh wrote: 1) you bumped debhelper build-dependency version from 7 to 8, why? Also, changes like this should be always documented in debian/changelog. Actually it's not required right away, but from future perspective I changed that. This is generally not a valid reason. For example, this makes it impossible to build the package on the system which has debhelper v7 installed, for no reason. In the changelog of 565-2 you wrote: Bumped debhelper version to 8 which should be required in future. Required by whom? In what future? I don't get what did you meant. Please explain (here in the list discussion). Or, alternatively, just revert this change. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20111210181916.GA10871@r500-debian
[done] Re: RFS: unetbootin
On 2011-11-20 05:58, Muneeb Shaikh wrote: Point noted. I have bumped the debian revision, it's now 563-2. Uploaded. Thank you for the contribution. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/2020090720.GA13146@r500-debian
Re: RFS: unetbootin
Hi Muneeb, Here's my review: 1) debian/changelog should include the entry for already uploaded version 555-1; 2) you switched to a source format '3.0 (quilt)' but didn't mention this in the debian/changelog. I will upload the package if you fix these two. Note: I want a bumped Debian revision after an every review for packages that I sponsor. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/2019165436.GH21037@r500-debian
Re: News about the mentors.debian.net transition to upgraded software
On 2011-08-14 07:37, Andrew Starr-Bochicchio wrote: That seems like a very bad design decision for a site dedicate to the iterative process of review then. I've always been told (and it has been repeatedly mentioned on this very list) that packages should only bump their version numbers for versions that actually entered the official archives. For the record, there are sponsors who prefer different review versioning process. This also was discussed some time ago on this list. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110814115108.GA28637@r500-debian
Re: [done] RFS: libbs2b
On 2011-07-30 19:58, Stephen Kitt wrote:
On Tue, 26 Jul 2011 15:35:40 +0300, Eugene V. Lyubimkin jac...@debian.org
wrote:
One minor detail (for the next upload) I didn't notice before: there is
no substitution variable '{misc:Pre-Depends}', so you can remove that
Pre-Depends line of libbs2b0 altogether.
Actually there is, in particular for multiarch support...
Hm, thanks, I stand corrected.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer
--
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/20110808151431.GB18108@r500-debian
[done] RFS: libbs2b
Hi Andrew,
On 2011-07-25 13:48, Andrew Gainer wrote:
Alright, thanks for the clarification. I've bumped each package to
*-2, added changelog entries, and uploaded again.
I just uploaded it to the Debian's NEW queue. Thank you for the
contribution to Debian.
One minor detail (for the next upload) I didn't notice before: there is
no substitution variable '{misc:Pre-Depends}', so you can remove that
Pre-Depends line of libbs2b0 altogether.
You can send requests regarding bs2b packages directly to me for next
uploads.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer
--
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/20110726123540.GA28201@r500-debian
Re: RFS: libbs2b and bs2b-ladspa
Hi Andrew, [ I prefer to have a bumped package version after an each review ] My review: --- libbs2b --- 1) there is definitely something wrong with remove_win32_build_instruction patch, its size is more than 2 MiB and it includes some autotools stuff; 2) Vcs-* fields point to LADSPA plugin repository; 3) debian/copyright: 3.1) there is no m4/pkg.m4 source file; 3.2) build-aux/* copyright years should be at least 1996-2010; 3.3) aclocal.m4, */Makefile.in: is automatically generated, does not need the entry; 3.4) configure: copyright years should be 1992-2010. I didn't yet attempt to build it because of 1). --- bs2b-ladspa --- 1) it can be uploaded only after libbs2b is accepted to the archive; 2) debian/copyright: 2.1) s!Files: *!Files: src/plugin.c! ; 2.2) spurious 'Copyright 2009 Boris Mikhaylov' (copy leftover?); 2.3) same (or about the same) corrections as in libbs2b's debian/copyright. Didn't attempt to build as well because of 1). -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110725094126.GA32055@r500-debian
Re: RFS: libbs2b and bs2b-ladspa
Hi, On 2011-07-25 12:46, Andrew Gainer wrote: Eugene V. Lyubimkin jac...@debian.org wrote: [ I prefer to have a bumped package version after an each review ] Other mentors have preferred that I use the VCS for keeping track of pre-release changes and leave the changelog clean, with only the Initial release (Closes: #ITP) entry. As a relative neophyte to the Debian packaging-and-policy world, I'm not sure what the best way to approach this is. Can you clarify this? Yes. Different sponsors prefer different ways to deal with pre-release changes, I believe there's no single best way. I want bumped after each review (and with a usual changelog between) versions for packages I intend to sponsor. Of course, if you have another sponsor(s) in the mind, just ignore this. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110725173318.GA10925@r500-debian
Re: How to make a meta package unremovable?
Hi, On 2011-06-13 12:56, David Kalnischkies wrote: With my APT hat on i can tell you that APT (and friends) currently have no option to forbid the removal of packages without other side-effects. Please refrain from uncondionally stating something about friends' functionality. Libcupt actually has the possibility to prevent the removal of any package without any other side-effects, though it is not available from the console front-end. I don't think this will help the topic starter, but I don't want to see false statements unanswered. What could be done is tweaking resolver scoring points, but honestly: that is black-magic [...] it has side-effects for other packages with this priority [...] For completeness, the points above are also applicable not for all friends. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110613163415.GA4458@r500-debian
[uploaded] Re: RFS: mangler (2nd try)
On 2011-05-08 00:44, Vincent Cheng wrote:
4) debian/control: please lowercase first letters in short descriptions.
Fixed for the libventrilo packages. However, mangler's description
starts off with Ventrilo, which is a name, so I think it should remain
capitalized.
Ok.
6) dpkg-shlibdeps report a number of overlinked libraries, you might want
to pass --as-needed to a linker.
[...]
Partly fixed. dpkg-shlibdeps now throws out 4 warnings instead of
about a dozen. However, if I remove the packages in build-depends that
dpkg-shlibdeps complains about and re-build, I get the following
output during the ./configure step:
[...]
So I reverted my changes. Anyways, at the moment, the only packages I
have in my build-depends are debhelper, autotools-dev, and the list of
packages given here [1].
Fine, 4 is certainly better than a dozen.
I uploaded the package (it isn't picked up by Debian machinery yet
though, some temporary problem there), it will go throught NEW queue.
Thanks for the contribution to Debian! You may contact me directly for
the future updates of this package.
I also didn't say in my previous mail that I highly prefer bumping Debian
revision after each review, so there are no two different trees under
the same Debian version ever.
And, some suggestions for the future uploads:
1) -dev packages don't need ${shlibs:Depends}, it can be removed
2) as libventrilo3/codec-test were removed, the section in debian/copyright
about some of files under that directory can be removed as well.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer
--
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/20110508102938.GA28901@r500-debian
Re: RFS: mangler (2nd try)
[ dropped pkg-voip@ from CC ] Here's my review: Overall the package is prepared well, thumbs up. Nevertheless: 1) The tarball contains directories 'android' and 'iphone'. Repack an upstream tarball and remove them totally. I don't think anybody would want check them for redistributability. 2) The source of files src/manglerui.h and icons/mangler-icons.h is unclear to me. Both look like machine-generated. Are they? If yes, how would one re-create them? 3) Some of libventrilo3/codec-test/* are without copyright notices, which is suspicious. Are they used in Debian package? If not, better remove them too. 4) debian/control: please lowercase first letters in short descriptions. 5) debian/libventrilo-dev.install: don't install .la-file (http://wiki.debian.org/ReleaseGoals/LAFileRemoval). 6) dpkg-shlibdeps report a number of overlinked libraries, you might want to pass --as-needed to a linker. I'll upload this package once/if at least the points 1-3 and 5 are addressed. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110507171124.GA19137@r500-debian
ITR (in 7 days): RFS: mangler (2nd try)
On 2011-05-01 04:15, Vincent Cheng wrote: * Package name: mangler Version : 1.2.2-1 Upstream Author : Eric Connell econn...@mangler.org Daniel Sloof an...@mangler.org * URL : http://www.mangler.org/ * License : GPL-2, GPL-3, LGPL-2.1 Programming Lang: C, C++ I will review this package in a week if no one steps before. @ pkg-voip people: please tell if you want this package to be under pkg-voip umbrella or there are reasons why mangler should not be packaged for Debian. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110501180359.GA25723@r500-debian
Re: RFS: libmk4-2 new version with quilt
Hi, On 2011-03-10 10:20, Bastien ROUCARIES wrote: ping ? I agree with Sune: this is better be done as a patch to akregator's sources. I don't want to upload a new package for that. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110310194415.GA9934@r500-debian
Re: RFS: libmk4-2
Hi Bastien, On 2011-02-24 15:07, Bastien ROUCARIES wrote: Version : 2.4.9.7-1 It builds these binary packages: libmk4-2 - MetaKit embeddable database -- shared libraries libmk4-2-dbg - debugging symbols for libmk4 libmk4-2-dev - MetaKit embeddable database -- development files I think it would be better to use same description style for libmk4-2-dbg, e.g. MetaKit embeddable database -- debug symbols My motivation for maintaining this package is: - I have a boring bugs on akregator that is akregator use metakit embeded on it 613522. - I have corrected and submitted a patch for fixing this bug on metakit upstream (return an exception of corrupted file) - Plan to fix akregator Do you intend to maintain this library in Debian if/after this fix for akregator is uploaded? Please note I have used last version on svn as base, because upstream will not release new version for fixing these kind of bugs. This is a worrying thing. They did the last release on June 2007. They consider it stable despite (presumably) long-known crash bug. Looks like an abandonware. Do they have any bugzilla? Will they fix (other) severe bugs if there will be any? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/20110224172200.GA26620@r500-debian
Re: RFS: buildbot
David Paleino wrote: On Tue, 24 Aug 2010 22:53:28 +0800, Paul Wise wrote: On Tue, Aug 24, 2010 at 3:59 AM, Andriy Senkovych jolly_ro...@itblog.org.ua wrote: I am looking for a sponsor for my package buildbot. ... buildbot-master - a system to automate the compile/test cycle buildbot-slave - a system to automate the compile/test cycle Since we are now in a freeze period, splitting the package up is not appropriate, nor is a new upstream version that is not-preapproved by the release team. Why? Testing is the one frozen, not unstable. And testing-proposed-updates is there for a specific reason, if needed :) To not interfere with current transitions and freeze exceptions. The freeze announcement also mentions it. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: Possible trimming of build dependencies
Osamu Aoki wrote:
Hi,
On Sun, May 16, 2010 at 09:43:22PM +0300, George Danchev wrote:
...
Ahem, I see, mistakes happen, thus clean chroots (and note to myself: clean
apt caches;-) are to be used for such tweaking. In fact, other packages'
{Build-}dependencies change over time, it is pretty common since new
versions
are uploaded, improvements are introduced, etc, so we always check when we
need to. To be honest, xmlto's own dependencies (in Debian unstable) look
sane
to me, so you might be witnessed some transient inefficiency which has been
subsequently corrected lately.
Another issue is dependency behavior difference between pure apt-get and
interactive deselect/aptitude. The default of the latter pulls in
recommends.
Apt-get pulls Recommends by default since Lenny.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer
signature.asc
Description: OpenPGP digital signature
Re: Breaks or Conflicts?
Thibaut Paumard wrote: So, the _real_ relationship is: the conjunction (B(old) + C(new)) breaks A and A-doc (to a point where A-doc ends-up deconfigured). Very clearly, C (new) must declare a Conflicts or a Breaks against B ( new). But which one is the good choice? Conflicts should be declared only in case of file conflicts. If, as I see, it's the case of 'doesn't work with' then use Breaks. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/4bbb4240.9000...@gmail.com
Re: Breaks or Conflicts?
Thibaut Paumard wrote: In my case, due to the triggers mechanisms, bad things will happen _during the dpkg run_ if dpkg launches the trigger when the files of B and C are present (even if B is deconfigured). Is this something that is possible, or will dpkg make sure B is upgraded before triggering update-A-doc? I get the impression the right thing to do would be to deconfigure _A-doc_ until B has been upgraded... This looks quite complicated to me. But as you mentioned 'update-A-doc', I guess it's a manual-written script? Can you just fix it in C so it performs necessary checks and does the right thing regardless of B is present (even partly) or not? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/4bbb480b.7020...@gmail.com
Re: Breaks or Conflicts?
Thibaut Paumard wrote: update-A-doc (actually update-yorickdoc) uses A (=yorick). The point is that A is broken when both B(old) and C(new) are present. I could fix update-yorickdoc to detect breakage of yorick, not do anything and return successfully, but that is certainly wrong: if update-yorickdoc fails, it should report failure. Now I got your point better. Well, Conflicts in this case will probably work better in practice, but in theory even Conflicts cannot guarantee you that all B files will be deleted before/during the unpack of C. Triggers may be run within the unpack stage, and the files of conflicting packages may be present during the whole stage (see policy §6.6.2 and §6.6.13). Personally I think it's a bug in dpkg, but apparently noone cares. To place yourself to a safe side you will have to rework your packaging somehow. Maybe, place the trigger script to another package, or double it between packages even so it works at least one time. Also, I'd suggest you to write your question to dpkg maintainers also. There is a possibility I may be wrong in assumptions above or there are some hidden restrictions for running triggers, that are not mentioned in policy. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- 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/4bbb590a.6040...@gmail.com
Re: RFS: aaphoto
Hi Horvath, Horvath Andras wrote: Dear mentors, I am looking for a sponsor for my package aaphoto. * Package name: aaphoto Version : 0.36-1 Upstream Author : Andras Horvath h...@log69.com (same as maintainer) * URL : http://log69.com/aaphoto_en.html * License : GPLv3 Section : graphics It builds these binary packages: aaphoto- Auto Adjust Photo Without pretending to be interested in this package, the short description does not seems useful. You have 64 characters, use them to describe the program better. Plus, if I were you, I'd post the several sentences what unique features this package have after the standard RFS template. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: Building pdf from odt files noninteractively?
Paul Gevers wrote: Some time ago I tried unoconv for my package, but it had issues as can be seen in the bts: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491456#102 Do you know a way to get it done? (I have to look into jodconverter). Yes, I saw this bug as well, but worked around it by issuing unoconv several times, so it successfully started the listener on 2nd or 3rd time, but this is indeed unreliable. I cannot say something about jodconverter, I used it many years ago when it was not yet packaged into official archive and don't remember details. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: debian/watch
Jaromír Mikeš wrote: Hello mentors, I trying monitor lv2-c++-tools source on http://mirror.lihnidos.org/GNU/savannah/ll-plugins/. Having watch file like this: version=3 http://download.savannah.gnu.org/releases/ll-plugins/lv2-c++-tools-(.*)\.tar\.bz2 maybe, 'c\+\+-tools'? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: RFS: xwax (try 3)
Hi Mitchell, Mitchell Smith wrote: Hi Eugene, Thank you for the helpful feedback. I have made your recommended changes to my package and uploaded it to mentors.debian.net for further review. Good work. Uploaded, the package will have to go through 'NEW' queue. Feel free to contact me privately for next uploads of 'xwax' package. Also, 'lintian -ivI' outputs 3 very minor issues with the package, they don't worth delaying the first upload as for me, but please resolve them in the next upload. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: RFS: ffprobe (2nd try)
Hello Alessio, Alessio Treglia wrote: Dear mentors, I am looking for a sponsor for my package ffprobe. Why do you copy scripts from tools/ to debian during build? You can install them directly from tools. As long as you package svn snapshot, you should include svn revision number in the package name, the date is not enough, like '0-svn20091022+r89' or '0-svn89', and update get-orig-source target accordingly. Also, I'd suggest to demote dependencies on 'perl' and 'libstatistics-descriptive-perl' to Recommends and state in the long description that they are needed for provided perl scripts. Otherwise package looks good, fix above and I'll upload it. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: RFS: xwax (try 3)
Hello Mitchell, Mitchell Smith wrote: Dear mentors, I am looking for a sponsor for my package xwax. debian/control: Lowercase first letter of the short description. Upgrade Standards-Version to latest, 3.8.3. The long description should be indented by one space, not four. debian/copyright: You should include copyright year (2009) to the 'Copyright' section. debian/README: The package 'mpg123' is now available from Debian main, revert the diversion from upstream regarding mpg321. debian/xwax.1: Update xwax version from 0.5 to 0.6. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: Building pdf from odt files noninteractively?
Felipe Sateler wrote: I have a source package that has pdf documentation, which is generated with openoffice.org. Is it possible to generate said pdf without user interacion (that is, for autobuilding in the buildds)? Or maybe I can just ship the also-included pdf files? AFAICS, the license is not violated. Try unoconv or jodconverter. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: RFS: aqemu (3rd try)
Hi Ignace, Ignace Mouzannar wrote: Dear mentors, I am looking for a sponsor for my package aqemu. * Package name: aqemu Version : 0.7.2-1 Upstream Author : Andrey Rijov rd...@users.sourceforge.net * URL : http://aqemu.sourceforge.net/ * License : GPL Section : x11 It builds these binary packages: aqemu - Qt4 front-end for QEMU and KVM Before looking at the package, there is already a Qt4 front-end in Debian repositories - it's 'qtemu' package. What are the advantages of aqemu over qtemu? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: RFS: libvc (updated package)
Hello Tony, Tony Palma wrote: Dear mentors, I am looking for a sponsor for the new version 003.dfsg.1-12 of my package libvc. You adopted the package, but didn't make any valuable changes (you changed maintainer mail address and bumped standards version), and this doesn't worth a new upload IMO. The current Debian package contains several more-than-year-old patches, did you contact the upstream author to include them? The build process run ./configure twice, consider fixing it. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: RFS: abr2gbr (updated package)
Hello Alice, Alice Ferrazzi wrote: Dear mentors, I am looking for a sponsor for the new version 1.0.3-1 of my package abr2gbr. Here's my review: - I didn't see 1.0.3 version on upstream site; - debian/compat: 'dpkg-source: warning: file abr2gbr-1.0.3/debian/compat has no final newline (either original or modified version)' complaint during the build, you may want to fix it; - consider manual adding of '-O2' option when compiling the binary (and suggest upstream to do it); - consider lowercasing the first letter of the short description, as suggested by developers reverence; - debian/changelog: entries (at least for 1.0.3-1) are very short and should be advanced, I came to package and haven't understood what things you changed in the last version (developers reverence contains a paragraph how to write good changelogs); - debian/rules: you should clean the rules by removing commented entries and unneeded (e.g. dh_installexamples) debhelper commands, you also may consider just using debhelper v7 minimal rules file (see examples in dh(1)). -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: RFS: ocropus (updated package)
Hello Jeffrey, Jeffrey Ratcliffe wrote: Dear mentors, I am looking for a sponsor for the new version 0.3.1-1 of my package ocropus. Here's my review: - debian/copyright: you don't need list the files with the same license but with different copyright years into the different clauses, just merge them; - (at least) many ext/lua/*.c files don't have any license clause, so they are non-redistributable; - move 'dirs' to 'ocropus-data.dirs'; - there are lintian warnings. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer signature.asc Description: OpenPGP digital signature
Re: Replacing an essential package
Jonathan Nieder wrote: Please do not CC the APT team on follow-ups --- it looks like APT already does the right thing here (sorry for the noise!). I wrote: The xz-utils package in experimental Conflicts/Replaces/Provides the pseudo-essential package lzma. I think this should be fine, since installing it only involves overwriting the lzma package rather than removing it. [...] Am I misunderstanding policy here? I was. Using Conflicts disallows files from xz-utils and lzma from coexisting even during an upgrade, making an upgrade impossible. What I meant to achieve is accomplished with Replaces/Provides without the Conflicts. Once xz-utils has written over all the files of lzma, lzma would be marked as uninstalled, so normally the two packages would not be installed at once. But how to ensure all the files of lzma are overwritten, when newer versions could always add more files? I worry because it might be confusing to a system administrator to see the lzma package installed when most of its important files are provided by another package. Such an administrator might blame bugs in xz-utils on the lzma package. Advice? Seems slightly ugly, but 'Breaks: lzma' may help. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
Re: Specifying ia32-libs in control when on a 64 bit Debian/Ubuntu?
Ignacio Valdes wrote:
Hi all,
I have a deb package that requires ia32-libs to run on a 64-bit
Debian/Ubuntu, otherwise it works without it on i386. I have tried in
the control file:
Depends: ia32-libs [amd64]
But that doesn't seem valid. How does one specify ia32-libs should be
a dependency when on 64 bit?
Shouldn't it be put automatically on amd64 arch by ${shlibs:Depends}?
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Maintainer
signature.asc
Description: OpenPGP digital signature
Re: Specifying ia32-libs in control when on a 64 bit Debian/Ubuntu?
Ignacio Valdes wrote: Unfortunately this is a package of a package that does not use deb done by someone else so I have to do the thinking for it. If ia32-libs is not present on a 64 bit system the install simply fails with an unrelated error message. I would rather not have two separate packages for i386 and amd64 if I can do the dependencies with logic only. -- IV Only the install fails, so the application within a package won't linked with any 32-bit lib? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
Re: RFS: xmms2 (updated package)
Benjamin Drung wrote: P: xmms2 source: direct-changes-in-diff-but-no-patch-system .gitignore and 5 more As written before, we use git to track patches. Most of these changes are cherry-picked. IANADD, but this is hardly excuse to this issue, as for me. Users and developers shouldn't need internet access to your git repo and cloning it to apply/exclude some patch or correct one of them, or even see what patches were applied. You can move .gitignore and other VCS stuff to another branch and generate, for example, nice quilt patches for package, can't you? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
Re: RFS: masqmail (updated package)
markus schnalke wrote: [2009-05-24 23:11] markus schnalke mei...@marmaro.de I am looking for a sponsor for the new version 0.2.21-6 of my package masqmail. I would be glad if someone uploaded this package for me. Now, someone did ... but how can I find out, who? The mail from mentors does not contain a name and I found no upload logs or a similar source. Look at your qa.debian.org maintainer page, put the mouse cursor to last source uploaded and see the Debian login of the uploader in the hint. -- 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
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
RFS: cupt (new package)
Dear mentors, I am looking for a sponsor for my package cupt. * Package name: cupt Version : 0.1.0 Upstream Author : Eugene V. Lyubimkin * URL : http://wiki.github.com/jackyf/cupt * License : Artistic | GPLv3+ Section : perl It builds these binary packages: cupt - alternative front-end for dpkg -- console interface libcupt-perl - alternative front-end for dpkg -- Perl modules From cupt's long description: This package provides a console interface to Cupt library, which is a re-implementation of libapt-pkg C++ library using Perl. The aim is to produce more strict, more robust, less buggy front-end than APT. . Cupt uses the same APT infrastructure, e.g. index files, deb cache archive files, configuration files. It understands some of widely used APT options. . Some features: - strict full-case resolver; - command-line and APT-like option name checker; - case-sensitive search; - pinning by source package name; - pinning by package groups using shell-like patterns; - configurable 'depends' and 'rdepends' subcommands; - 'satisfy' subcommand. . Its interface is mostly like apt-get/aptitude console interface. The package is to be lintian -ivI clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/cupt - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/cupt/cupt_0.1.0.dsc I would be glad if someone uploaded this package for me. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
RFS: bindfs (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.8.3-1 of my package bindfs. It builds these binary packages: bindfs - mirrors or overlays a local directory with altered permissions The package is lintian -ivI clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/bindfs - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/bindfs/bindfs_1.8.3-1.dsc I would be glad if someone uploaded this package for me. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
Re: [jack-mixer]bin/sh: no: command not found
Grammostola Rosea wrote: GCONF_CONFIG_SOURCE= no --makefile-install-rule ^ This space should be removed. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
How to proceed with old uninstallable versions of package?
Hello mentors, I have a package named unetbootin, which is useful and installable only on i386 and amd64 arches (it Depends on syslinux, which is also available only on i386 and amd64). However, old versions of package had 'any' in the 'Architecture' field, but as long as unetbootin depends on syslinux, package had not propagated to testing because of uninstallability on these arches. I have uploaded a new version with correct 'Architecture' field, but current testing status reports old versions built for other arches, and current version failed to build. This also prevents migration. What should I do? -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
Re: debian/symbols
Hello Thorsten, Thorsten Alteholz wrote: Hi, I need some advice on using the debian/symbols-file. The package libctl3 needs a symbols file, so I added something like: libctl.so.3 libtcl3 #MINVER# ^^^ ^^^ BTW, about last lintian complaint: 'libctl' and 'libtcl': one of them has a typo probably. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Maintainer signature.asc Description: OpenPGP digital signature
Re: Listing dependencies with specific versions
Andy Hawkins wrote:
Hi all,
I'm in the process of building my first package. Most of the dependencies
generated by ${shlibs:Depends} are fine for the package, but I need to force
the version of one particular component.
So I've put
Depends: ${shlibs:Depends}, ${misc:Depends}, libflac++6(=1.2.1)
in the 'control' file. This causes Lintian to issue a warning:
package-has-a-duplicate-relation depends: libflac++6, libflac++6 (= 1.2.1)
According to the man dpkg-gencontrol, just place 'libflac++6(=1.2.1)' before
the '${shlibs:Depends}', and dpkg-control with throw away less strong
dependency.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
Ukrainian C++ Developer, Debian APT contributor
signature.asc
Description: OpenPGP digital signature
Re: Question about bug hunting
Sandro Tosi wrote: Hello Laurent, On Tue, Dec 2, 2008 at 21:11, Laurent Guignard [EMAIL PROTECTED] wrote: Is there any means to know if someone work on a bug from RC bug ? rc-alert or popbugs show all RC bugs of our packages but if someone is already on, it isn't necessary to work to solve the bug. Are all works in progress referenced somewhere ? Well, generally no, like any other bugs. Sometimes (in particular it's used during bug squashing parties), the one who's working on the bug claim it, using bts claim bug number, and you can see on [1] it a bug is claimed or not (is this information available somewhere else?). [1] http://bts.turmzimmer.net/ I also think it would be a good addition to display such info in the BTS bug page, as BTS is now missing something like 'assigned' tag/info. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com Ukrainian C++ developer, Debian APT contributor signature.asc Description: OpenPGP digital signature
RFS: qprint (new package)
Dear mentors, I am looking for a sponsor for my package qprint. * Package name: qprint Version : 1.0.dfsg.2-1 Upstream Author : John Walker (http://www.fourmilab.ch/) * URL : http://www.fourmilab.ch/webtools/qprint/ * License : Public Domain Section : utils It builds these binary packages: qprint - encoder and decoder for quoted-printable encoding qprint-doc - qprint quoted-printable encoder/decoder (documentation) It seems we have no such a tool in current Debian archive. I was needed to fetch content from broken e-mail recently, and this tool became my friend. The package is lintian -ivI clean. The upload would fix these bugs: 506461 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/q/qprint - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/q/qprint/qprint_1.0.dfsg.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com Ukrainian C++ developer, Debian APT contributor signature.asc Description: OpenPGP digital signature
[DONE] Re: RFS: unetbootin
Thanks for attention, I've found the sponsor. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com Ukrainian C++ Developer, Debian APT contributor signature.asc Description: OpenPGP digital signature
RFS: unetbootin
Dear mentors, I am looking for a sponsor for my package unetbootin. * Package name: unetbootin Version : 301-1 Upstream Author : Geza Kovacs [EMAIL PROTECTED] * URL : sf.net/projects/unetbootin * License : GPLv2+ Section : utils It builds these binary packages: unetbootin - installer of Linux/BSD distributions to a partition or USB drive unetbootin-translations - translations for unetbootin distribution installer The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/u/unetbootin - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/u/unetbootin/unetbootin_301-1.dsc I would be glad if someone uploaded this package for me. -- Eugene V. Lyubimkin aka JackYF Ukrainian C++ developer, Debian APT contributor signature.asc Description: OpenPGP digital signature
Re: RFS: neotool
IANADD Heikki Mäntysaari wrote: I am looking for a sponsor for my package neotool. [snip] It builds these binary packages: neotool- Util to manage Openmoko smartphones [snip] I would suggest utility to manage Openmoko smartphones (start with small letter and use 'utility' rather than 'util'). -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: question
Dionysis Kalofonos wrote: Dear mentors, i have a program that i want to compile, but i miss the file 'curl-config' and so the process stops with an error. My questions is. How can i find the package the provides the above file (it can be more than one)? dpkg -S apt-file search -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Re: help, error with debian/tmp
ivan wrote: Hello all Please, help me, what i do wrong? I try build debian package, but see error: [EMAIL PROTECTED]:/data/soft/pkg/astral/libastral-0.4% dpkg-buildpackage ... install -s libastral.so /data/soft/pkg/astral/libastral-0.4/debian/tmp/usr/lib/ install: указанная цель `/data/soft/pkg/astral/libastral-0.4/debian/tmp/usr/lib/' не является каталогом: Нет такого файла или каталога [snip] IANADD Have you debian/dirs file, with usr/lib entry in it? -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: help, error with debian/tmp
ivan wrote:
On Sunday 05 October 2008 12:40:29 Eugene V. Lyubimkin wrote:
ivan wrote:
On Sunday 05 October 2008 11:10:54 Eugene V. Lyubimkin wrote:
Have you debian/dirs file, with usr/lib entry in it?
Yes debian/dirs file contents 2 strings:
usr/lib
usr/include
Ah, sorry, didn't see it.
Then simply mkdir usr/lib subdirectory in debian/tmp, it seems that
dh_installdirs don't create it, its aim to create all needed subdirectories
in package install dirs, not tmp. It's my assuming, it may be wrong.
Hmmm, wery strange...
I find in Dh_Lib.pm code:
elsif (compat(1) $package eq $dh{MAINPACKAGE}) {
# This is for back-compatibility with the debian/tmp tradition.
return debian/tmp;
}
and may build package when write in debian/compat 1, but write
dh_builddeb: Compatibility levels before 4 are deprecated.
You should not build package with compat 5 nowadays.
why default make file generate:
install: build
..
# Add here commands to install the package into debian/tmp
$(MAKE) DESTDIR=$(CURDIR)/debian/tmp install
install to debian/tmp ?
I guess because most 'install' targets create needed subdirectories themselves.
--
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.
signature.asc
Description: OpenPGP digital signature
Re: help, error with debian/tmp
ivan wrote: On Sunday 05 October 2008 11:10:54 Eugene V. Lyubimkin wrote: Have you debian/dirs file, with usr/lib entry in it? Yes debian/dirs file contents 2 strings: usr/lib usr/include Ah, sorry, didn't see it. Then simply mkdir usr/lib subdirectory in debian/tmp, it seems that dh_installdirs don't create it, its aim to create all needed subdirectories in package install dirs, not tmp. It's my assuming, it may be wrong. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: help, error with debian/tmp
ivan wrote: On Sunday 05 October 2008 13:59:54 Eugene V. Lyubimkin wrote: and may build package when write in debian/compat 1, but write dh_builddeb: Compatibility levels before 4 are deprecated. You should not build package with compat 5 nowadays. I understand this, i only try it. why default make file generate: install: build .. # Add here commands to install the package into debian/tmp $(MAKE) DESTDIR=$(CURDIR)/debian/tmp install install to debian/tmp ? I guess because most 'install' targets create needed subdirectories themselves. And what do file debian/dirs if it not work? Installs dirs in case there is only one binary package. Otherwise package.dirs are needed. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: Packaging a library
IANADD Leopold Palomo Avellaneda wrote: Hi, I'm packing a library (not yet an ITP, just learning) and I'm having some doubts about it. [snip] Also, my second question is about to create a dbg package. Upstream has some --enable-debug that is a -DDEBUG. Looking on the source I have seen some std outs with this define. Looking others packages, I have understood that you create the package normally, and you add dh_strip --dbg-package= line to put the striped symbols in that package. This is correct? is it worsewhile to generate that package? Yes, it is correct. It's plus to you if you generate this package and for users who want (at some time) to debug it. And my last question is examples. Upstream has a directory with some examples, but they are not installed (noinst_PROGRAMS), so, should I to patch sources to install them? Or simply, do I copy the files? If you can copy the files manually without patching the sources - copy them in install target. General rule is avoiding patching the upstream files whenever possible. -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
[DONE] Re: RFS: swapspace (adopted and updated package)
Eugene V. Lyubimkin wrote: Dear mentors, I am looking for a sponsor for the new version 1.10-4 of my package swapspace. I've found a sponsor. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: Compilation options.
Alessio Giovanni Baroni wrote: Hi to all, a base question: when one compile a package, often are enabled the debug and low level optimiziation. For Debian, how must I to do it? -g/none -O1/-O2/-O3 ? Thanks. IANADD For C/C++ programs, you may use CFLAGS shell variable, provided by dpkg-buildpackage, which also handles noopt option in DEB_BUILD_OPTIONS automatically. -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Re: debian/control best practices
Carlos Eduardo Sotelo Pinto wrote: Hi mentors I have a question, I am packaginf sitebar package wichis on mentorsdebian.net, and have gotten a suggestion, but it got confused me in one way, debian developeres reference talks about debian control best practices and I understand that ( and one more person say me the same ) that synposys must be on lower cases http://www.debian.org/doc/developers-reference/best-pkging-practices.html#bpp-pkg-synopsis package-name is a synopsis. but all the packages that I have seen was on this way Package-name is a synopsis. The first leeter is on uppercase what is the right? IANADD Developers Reference and lowercase. -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
RFS: swapspace (adopted and updated package)
Dear mentors, I am looking for a sponsor for the new version 1.10-4 of my package swapspace. It builds these binary packages: swapspace - dynamic swap space manager The package is lintian -ivI-clean. The upload would fix these bugs: 499116 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/swapspace - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/swapspace/swapspace_1.10-4.dsc I would be glad if someone uploaded this package for me. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
deb/debian suffixes in packages
Hi -mentors! I failed to find the correct meaning of deb/debian suffixes in some version strings of packages in Debian archive. Are they stand for seriously modified code? I found 292 examples in Debian unstable. (aptitude search ?version(deb) --display-format=%p - %V --disable-columns | wc -l) -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Re: deb/debian suffixes in packages
David Paleino wrote: On Tue, 16 Sep 2008 18:14:04 +0300, Eugene V. Lyubimkin wrote: [snip] I failed to find the correct meaning of deb/debian suffixes in some version strings of packages in Debian archive. Are they stand for seriously modified code? I found 292 examples in Debian unstable. (aptitude search ?version(deb) --display-format=%p - %V --disable-columns | wc -l) Usually, these prefixes are mostly used: debian ds dfsg $vcs (i.e. svn, bzr, cvs, ...) The first two usually mean that the original tarball has ben repacked not for license issues: stale files, build-generated files, .svn/CVS/.bzr/$vcs directories, [..] dfsg is appended when the original tarball is repacked with the removal of files which cannot be distributed by Debian, or, at maintainer's choice, non-free files (i.e. suitable for non-free), but not absolutely needed by the program itself so, instead of making the whole package non-free, just those bits are dropped, and the whole package con go to main/contrib. $vcs is added when... well, when it's a snapshot from a repository :) Thank you for answer. May be, it's reasonable to add this info (after formatting) to devreference? -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Re: deb/debian suffixes in packages
Al Nikolov wrote: Eugene V. Lyubimkin wrote: Thank you for answer. May be, it's reasonable to add this info (after formatting) to devreference? I believe it's not a policy but a somewhat common used practice. You are free to use *any* revision suffixes in your packages because revisions itself have only one (pure technical) meaning: they are one part of vesrion numbering scheme. Not more, not less. Shouldn't devreference describe common used practices? It's not a policy, after all. -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Re: Quilt and patches directory
Andreas Schildbach wrote: Is there any way to tell quilt about the debian package structure? The way it works, it always looks in the current directory for the patches and .pc directories. What I'd like it to do is find the debian directory in the parent hierarchy and put/search for its patches directories there. IANADD I just operate within top level directory using relative path to all files. Quilt works well for me. Is it acceptable for you? -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: RFS: bindfs (bugfix upload, pre-approved by release team)
George Danchev wrote: On Sunday 31 August 2008 20:50:57 Eugene V. Lyubimkin wrote: --cut-- Ok. Done, re-uploaded. http://mentors.debian.net/debian/pool/main/b/bindfs/bindfs_1.8-1.dsc Uploaded. Thanks and sorry for the delay. Please, consider reading that announcement [1] when you request release team to unblock. Basically you don't need to include the full diff, they will regenerate it from the uploaded package, but include the last changelog entry instead. [1] http://lists.debian.org/debian-devel-announce/2008/09/msg0.html Yes, I've read this, but I had requested freeze exception before the upload, how the release team can fetch diff from unexisting upload? :) In any case, thanks for work and upload. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
RFS: exiftags (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.01-3 of my package exiftags. My previous sponsor, Anibal Monsalve Salazar, seems to be busy for more than week, so I am seeking for uploader or new usual sponsor for this package. It builds these binary packages: exiftags - Utility to read Exif tags from a digital camera JPEG file The package appears to be lintian clean. The upload would fix these bugs: 496032 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/e/exiftags - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/e/exiftags/exiftags_1.01-3.dsc I would be glad if someone uploaded this package for me. Kind regards -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
RFS: bindfs (bugfix upload, pre-approved by release team)
Hi -mentors! I am looking for a uploader for the new version 1.8-1 of my package bindfs. My usual sponsor for this package, Kapil Hari Paranjape, seems to be busy now. I want for pre-approved by release team upload of new version 1.8-1 of package to reach testing ASAP, so I am seeking for uploader. It builds these binary packages: bindfs - mirrors or overlays a local directory with altered permissions The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/b/bindfs - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/b/bindfs/bindfs_1.8-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: PGP signature signature.asc Description: OpenPGP digital signature
Re: RFS: bindfs (bugfix upload, pre-approved by release team)
George Danchev wrote: On Sunday 31 August 2008 08:30:03 Eugene V. Lyubimkin wrote: Hi -mentors! I am looking for a uploader for the new version 1.8-1 of my package bindfs. My usual sponsor for this package, Kapil Hari Paranjape, seems to be busy now. I want for pre-approved by release team upload of new version 1.8-1 of package to reach testing ASAP, so I am seeking for uploader. It builds these binary packages: bindfs - mirrors or overlays a local directory with altered permissions Okay, I found the release team reaction along with the diff. Could you please remove quilt from build-depends since it is unneeded, and I will sponsor. This change is safe for me, but for release team? This change will also lead to change debian/rules not to use 'patch' and 'unpatch' targets. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: RFS: exiftags (updated package)
George Danchev wrote: On Sunday 31 August 2008 08:24:13 Eugene V. Lyubimkin wrote: Dear mentors, I am looking for a sponsor for the new version 1.01-3 of my package exiftags. My previous sponsor, Anibal Monsalve Salazar, seems to be busy for more than week, so I am seeking for uploader or new usual sponsor for this package. Ok, thanks for fixing an RC. Builds fine per autobuilders (dpkg-buildpackage -B), but fails to build with fakeroot debian/rules binary (as per policy), probalby because of missing binary-arch and binary-indep targets ? Try to fix it, or I'll have a look more closer look tonight... of course sponsors with more time are welcome to beat me on that line ;-) Builds fine in my pbuilder. binary-arch and binary-indep are defined by debhelper v7. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: RFS: exiftags (updated package)
George Danchev wrote: On Sunday 31 August 2008 10:00:44 Eugene V. Lyubimkin wrote: George Danchev wrote: Ok, thanks for fixing an RC. Builds fine per autobuilders (dpkg-buildpackage -B), but fails to build with fakeroot debian/rules binary (as per policy), probalby because of missing binary-arch and binary-indep targets ? Try to fix it, or I'll have a look more closer look tonight... of course sponsors with more time are welcome to beat me on that line ;-) Builds fine in my pbuilder. binary-arch and binary-indep are defined by debhelper v7. Eugene, this is not enough, your `binary-arch' should build a binary package to a given architecture, but it fails because it does not depend on `build' target (where policy 4.9. says it should), thus `patch' target was also not being called as well. To fix that you should add: binary-arch: build install George, I might missed something. Both 'dpkg-buildpackage -b' and 'dpkg-buildpackage -B' work, in both cases patches are applied and binary packages are built correctly. Where do you got the error? -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: RFS: bindfs (bugfix upload, pre-approved by release team)
George Danchev wrote: On Sunday 31 August 2008 09:49:05 Eugene V. Lyubimkin wrote: George Danchev wrote: On Sunday 31 August 2008 08:30:03 Eugene V. Lyubimkin wrote: Hi -mentors! I am looking for a uploader for the new version 1.8-1 of my package bindfs. [snip] It builds these binary packages: bindfs - mirrors or overlays a local directory with altered permissions Okay, I found the release team reaction along with the diff. Could you please remove quilt from build-depends since it is unneeded, and I will sponsor. This change is safe for me, but for release team? This change will also lead to change debian/rules not to use 'patch' and 'unpatch' targets. Yes, it is safe; quilt has no business here as a build-dependency wasting autobuilders and other builders time to install and deinstall. Worst, that might leave a worrisome impression to the reader of any patches not being applied by accident. For the protocol, please, complete that and show them the diff, and CC: to me. Thanks. Ok. Done, re-uploaded. http://mentors.debian.net/debian/pool/main/b/bindfs/bindfs_1.8-1.dsc -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: RFS: exiftags (updated package)
George Danchev wrote: On Sunday 31 August 2008 20:25:57 Eugene V. Lyubimkin wrote: George Danchev wrote: On Sunday 31 August 2008 10:00:44 Eugene V. Lyubimkin wrote: George Danchev wrote: Ok, thanks for fixing an RC. Builds fine per autobuilders (dpkg-buildpackage -B), but fails to build with fakeroot debian/rules binary (as per policy), probalby because of missing binary-arch and binary-indep targets ? Try to fix it, or I'll have a look more closer look tonight... of course sponsors with more time are welcome to beat me on that line ;-) Builds fine in my pbuilder. binary-arch and binary-indep are defined by debhelper v7. Eugene, this is not enough, your `binary-arch' should build a binary package to a given architecture, but it fails because it does not depend on `build' target (where policy 4.9. says it should), thus `patch' target was also not being called as well. To fix that you should add: binary-arch: build install George, I might missed something. Both 'dpkg-buildpackage -b' and 'dpkg-buildpackage -B' work, in both cases patches are applied and binary packages are built correctly. Where do you got the error? ... you are relying on dpkg-buildpackage to call `build' for you. `build' resp. `patch' were not called as in: $ fakeroot debian/rules binary [cut build log] Ok, thanks, I finally understood you. Fixed, re-uploaded to mentors.d.o. http://mentors.debian.net/debian/pool/main/e/exiftags/exiftags_1.01-3.dsc. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: RFS: daptup (new package, 3rd try)
Ben Finney wrote:
Eugene V. Lyubimkin [EMAIL PROTECTED] writes:
It builds these binary packages:
daptup - see changes in new upgradeable lists after aptitude update
The package synopsis should be an appositive clause as described in
URL:http://www.debian.org/doc/developers-reference/ch-best-pkging-practices#s-bpp-pkg-synopsis.
Essentially this means the synopsis should make sense when inserted
into the template packagename is {the,a,an} synopsis.
A possible improved synopsis might be:
reporter of changes in list of available packages from repositories
Other improvements are certainly possible.
Thanks for this correction. Done as how you suggested and re-uploaded:
http://mentors.debian.net/debian/pool/main/d/daptup/daptup_0.4.0-2.dsc
--
Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer.
signature.asc
Description: OpenPGP digital signature
RFS: daptup (new package, 3rd try)
Dear mentors, I am looking for a sponsor for my package daptup. * Package name: daptup Version : 0.4-1 Upstream Author : Eugene V. Lyubimkin * URL : http://sf.net/projects/daptup * License : GPLv3 Section : admin It builds these binary packages: daptup - see changes in new upgradeable lists after aptitude update Daptup runs aptitude update inside and then outputs three lists: - packages came to archive with this update; - new upgradeable packages; - changes in watched packages (not installed, such packages have to be specified in configuration file). The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/daptup - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/daptup/daptup_0.4-1.dsc -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: ftp-masters
Stanislav Maslovski wrote: If a package has been uploaded to NEW, but has not been yet approved or rejected by ftp-masters, and if this package has a mistake that is better to be corrected before the package gets into unstable, then what is the official procedure of doing such correction? IANADD As I know, just simply upload new revision of package. It will go into NEW too, and ftp-masters will approve or reject latest upload of package -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
Re: RFS: qmmp
Ben Finney wrote: Eugene V. Lyubimkin [EMAIL PROTECTED] writes: It builds these binary packages: libqmmp-dev - development files for libqmmp libqmmp-misc - plugins and auxiliary libraries for qmmp libqmmp0 - library that provides core functionality of qmmp libqmmpui-dev - development files for libqmmpui libqmmpui0 - library that provides user interface of qmmp qmmp - xmms-like audio player with support of many formats These synopses don't actually describe much. What does XMMS-like mean here? Can you say what that is in a synopsis without referring to a package the reader might not be familiar with? Of the form: audio player that frotzes and spangulates where frotzes and spangulates are the description of what you mean by XMMS-like, so that I don't need to know what XMMS is to understand. Ok, changed to feature-rich audio player with support of many formats. Nothing special, just audio player with many features. The libqmmp library synopses are inconsistent, and don't do much except refer to qmmp, which isn't much help. How about: qmmp audio player runtime library development files qmmp audio player plugins and auxiliary libraries qmmp audio player runtime library qmmp audio player user interface development files qmmp audio player user interface library Much the same principles apply to the full description: it's good to have an identical qmmp is an audio player that frotzes and spangulates section in the description of every one of these packages, leaving the rest of the description to say what makes this package unique compared to the others. Done as how you suggested. Reuploaded: http://mentors.debian.net/debian/pool/main/q/qmmp/qmmp_0.2.0-1.dsc Thanks for look! -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
RFS: qmmp
Dear mentors, I am looking for a sponsor for my package qmmp. * Package name: qmmp Version : 0.2.0-1 Upstream Author : Ilya Kotov [EMAIL PROTECTED] * URL : http://qmmp.ylsoftware.com/ * License : GPLv2+ Section : sound It builds these binary packages: libqmmp-dev - development files for libqmmp libqmmp-misc - plugins and auxiliary libraries for qmmp libqmmp0 - library that provides core functionality of qmmp libqmmpui-dev - development files for libqmmpui libqmmpui0 - library that provides user interface of qmmp qmmp - xmms-like audio player with support of many formats This package can be the replacement of xmms or audacious for Qt or KDE users. The package appears to be lintian clean. The upload would fix these bugs: 492106 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/q/qmmp - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/q/qmmp/qmmp_0.2.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
Re: Newbie Help - Ruby on Rails packaging questions.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Hurt wrote: OK, I am attempting to package up redmine and need some general pointers. I'm going through the New Maintainers Guide tutorial and have run into a few things that I need clarification on. 1) Is there any type of automated way to extract license info from a series of files? I am using a simple grep to do my heavy lifting but it seems pretty crude; has no one built anything better? 2) redmine itself is under GPL-2 but there are some files in the archive under various other license (MIT, LGPL, Ruby) and some files have no license at all. How do I represent this information in the debian/copyright file? Listing each file and it's license individually would be overwhelming. What is the best practice here? 3) The step-by-step tutorial in the DNMG tells the story of packaging software that is buildable (i.e. has source code). Since my software is built on RoR it doesn't really build anything. Is there a better tutorial on how to package these types of things (Perl scripts, RoR, Python programs, etc.)? Thanx! Richard 1) licensecheck program from devscripts package 3) Debian policy has links to special Perl policy and others - -- Eugene V. Lyubimkin aka JackYF -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkiEj80ACgkQchorMMFUmYxmbACgr1noMrrnOkZtHv3LHD+R1I2p Z6sAnj5exVfub0RXmu5dTfpLSGjygpic =faSV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[DONE] RFS: html2text.
Vincent Bernat kindly sponsored the package. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
RFS: libconfig (NMU, fixed release-goal bug)
Dear mentors, I am looking for a sponsor for the new version 0.1.5+nmu1 of package libconfig. It builds these binary packages: libconfig0 - Configuration file parser library libconfig0-dev - Development files for the config library The upload would fix these bugs: 484400 (bashism) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libconfig - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libconfig/libconfig_0.1.5+nmu1.dsc I'd be glad if someone uploaded this NMU. Moreover, has anyone an interest of sponsoring this package? Now it have ancient Standards, ancient upload, and wrongly is native package. I think I can fix most of the issues in 1 or 2 days. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: OpenPGP digital signature
RFS: libconfig (NMU, fixed release-goal bug)
The upload would fix these bugs: 484400 (bashism) The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libconfig - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libconfig/libconfig_0.1.5+nmu1.dsc I'd be glad if someone uploaded this NMU. Moreover, has anyone an interest of sponsoring this package? Now it have ancient Standards, ancient upload, and wrongly is native package. I think I can fix most of the issues in 1 or 2 days. -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. signature.asc Description: PGP signature signature.asc Description: OpenPGP digital signature
Re: How to not break dependant packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 IANADD Sean McE wrote: On Thu, 17 Jul 2008 15:30:08 +0200 Thibaut Paumard [EMAIL PROTECTED] wrote: I guess you are running unstable: you have to expect those glitches. It should not happen in testing or stable. It should not happen in unstable very often either: apparently it's only for new upstream versions of claws-mail. I'm running testing. IMHO, In this case maintainer is quite wrong, because it is not allowed in testing to break any packages in testing. My suggestion is to put 'Conflicts: claws-mail-plugins-extra ( upstream-version)' to 'claws-mail' package. Am I wrong? - -- Eugene V. Lyubimkin aka JackYF -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkh/U8QACgkQchorMMFUmYzNvQCfcO565D2q8gEVQA1kHIoLah/h f18AnAykc1qm/sawmIFfME1CuANfoksw =ShEr -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Changing of behavior: How to tell the user?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Tscharner wrote: Dear Mentors, I'm the maintainer of the CVSNT package. This is a better replacement for CVS and just like CVS it can work as server or client. One of the enhancements (on the server side) was replacing the old directory based file locks with a so-called lock server, which handled all the locking on a per file basis. What I did until now was to start this cvslockd daemon in an init script regardless whether the user used CVSNT as client or server. In the next few weeks should now come out a new version upstream and I updated my package, fixed the bugs and I also want to prevent that cvslockd is started every time. So I created a configuration file /etc/defaults/cvsnt where an environment variable defines whether or not the daemon gets started. I figured that there are probably more client users than server users and set the default to no longer start cvslockd. My questions: 1) Is this change of behavior desirable/do-able? 2) Is /etc/default/cvsnt the right place to turn on/off the daemon at all? 3) How shall I inform the server users that they know that they have to configure the file to get the lock daemon started again? TIA and best regards Andreas for 3) - may be, Debian.NEWS and/or debconf message in postinst? - -- Eugene V. Lyubimkin aka JackYF -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkh/YesACgkQchorMMFUmYw3egCeKr2kyaAt5JMohn2W5bCiySzs ph0AnRpiZsqDU2cTMm40J/oJ38zPWtCz =5Ufe -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to not break dependant packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hubert Chathi wrote: Stefan Potyra wrote: Hi, On Thursday 17 July 2008 15:15:25 Sean McE wrote: On current packaging there is no way to express the dependency on upstream version only, [...] actually, there is: Depends: foo (= 1.2.1), foo ( 1.2.1+) This wouldn't work for binNMU'ed packages (in which case, foo might have version number like 1.2.1+b1). Maybe foo ( 1.2.1++) might work. Why not foo ( 1.2.2) then? - -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIf5ZNchorMMFUmYwRAhXAAJ9nEZKHKymmQr04B8bWuV8vwSR8zwCfer6O vlb+e7R4LCizLp9CCPwIL+U= =4Iwz -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to detect an upgrade from an older version of a package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Goirand wrote: Hi, I want to make an update to libapache-mod-log-sql that needs some maintenances in it's SQL databases if we need to upgrade. Namely, it needs some table structure upgrades. I know many hacks to know that I'm upgrading (like doing dpkg -l, etc.), but what is the correct/policy way to know from what version my package is upgrading, so my postinst can run smoothly? Thomas Goirand IANADD. Policy 6.6.3 says If the package is being upgraded, call: new-preinst upgrade old-version Is it what you are seeking? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkh7TwEACgkQchorMMFUmYycHgCeL+5NcXoAwmX3Rgfaifk5Hk+g JmsAoK0vZo2RIMjBOF+iyYkqGb3EezIR =QZHh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to detect an upgrade from an older version of a package
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas Goirand wrote: Eugene V. Lyubimkin wrote: IANADD. Policy 6.6.3 says If the package is being upgraded, call: new-preinst upgrade old-version Is it what you are seeking? That wont give me the version number from which I'm upgrading from, will it? Thomas old-version is the version which package is upgraded from, isn't it? :) - -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIe6zrchorMMFUmYwRAtNTAKCS83jaPtzQ/c6KfYl1E2iSOpWF+ACfVWbg jTCuGxhRiyZLH9zdGozsy4w= =iBFG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: html2text (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear mentors, I am looking for a sponsor for the new version 1.3.2a-4 of my package html2text. It builds these binary packages: html2text - advanced HTML to text converter The package is lintian -ivI clean. The upload would fix these bugs: 255511, 342727, 367555, 381184, 388583, 486760 The package can be found on mentors.debian.net: - - URL: http://mentors.debian.net/debian/pool/main/h/html2text - - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - - dget http://mentors.debian.net/debian/pool/main/h/html2text/html2text_1.3.2a-4.dsc I would be glad if someone uploaded this package for me. Kind regards Eugene V. Lyubimkin - -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIeh0+chorMMFUmYwRApLwAKCK1Ab1ea+Nnk0IOA1I3cAZqamCsgCfRTAh IAZA7d62aBCD2KresxzhEgw= =aOYy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: atmailopen (2nd attempt - updated description)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 IANADD Giuseppe Iuculano wrote: I am looking for a sponsor for my package atmailopen. * Package name: atmailopen Version : 1.01-1 Upstream Author : @Mail [EMAIL PROTECTED] * URL : http://www.atmail.org/ * License : Apache License Version 2.0 Section : web Description: elegant and intuitive ajax webmail client written in php [snip] Kind regards Giuseppe Iuculano Debian developers reference suggest not no put written in language into one-line descriptions - it is useless for users to know what language the program written in. - -- Eugene V. Lyubimkin aka JackYF, Ukrainian C++ developer. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQFIb0WxchorMMFUmYwRAkQXAJdzZVYwW+3egBfWvwbD5Sz7JK5hAKCgzyOY 6w4tUciscvnND4uB/X7Oiw== =Yyk/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
