Re: your mail
Re: Gurpreet Singh Grewal in <[EMAIL PROTECTED]> > I would like to help by whatever programming help I can give and > wwould be glad if someone > mentored me for a while and helped me become a hacker . Have a look at http://www.debian.org/devel/join/ for ways of getting started. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFC: webxml
Re: Martín Ferrari in <[EMAIL PROTECTED]> > I have a package ready, but before filing an ITP, I would like to have > feedback on this. Webxml is a QT editor for tomcat's web.xml files, it > seems to work OK and can be very handy, specially when you're not > familiar with that kind of configuration files. The drawback is that > upstream doesn't seem very active (last release on March, 2003). Would > it be useful to the project? * Do *you* use it (and find it useful)? * Do you know of others that use it? * Are there alternatives? (in/outside Debian) Please don't package something just for the sake of it. Otherwise, go ahead, any software that is useful for you is probably useful for someone else. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: [RFS] grace6: An XY plotting tool
Re: Torsten Werner in <[EMAIL PROTECTED]> > DO NOT DO THAT AGAIN! > > RFH does not mean, that the package is not maintained. You should have > coordinated the upload with the current maintainer - at least the ITA > mail should be send some days/weeks *before* the upload. It would have helped if you had filed one common RFA(H?) for grace and grace6 together, or at least have mentioned a cross-ref somewhere. > Ionut is the future maintainer who has coordinated with me. Ionut, > please send your own ITA mail to the bug report mentioned above. We will > discuss privately how to fix the problem. I'm sorry if I broke transition plans there. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Willing to adopt a few orphaned packages
Re: Stan Vasilyev in <[EMAIL PROTECTED]> > >I think the question is: "If I create a package of this, will someone > >sponsor Hi, just go ahead an create updated packages. Ask for a sponsor here; I'm willing to sponsor uploads of adopted packages, especially if people do care about the packages they do adopt. > That's exactly what I had in mind. I would like to know if it's > reasonable for me to adopt some of the packages I listed. I could just > go ahead and start packaging all of them but I fear that most of them > are going to get rejected and thrown away from Debian. I want to > concentrate on those packages that matter. Please don't package/adopt stuff just for the sake of it. But if you use the packages yourself, please go ahead. If you feel you don't want to take over all of them, you can still prepare one-time "QA uploads" to solve some bugs and let the packages still be QA-(non?)-maintained. The later is equally useful. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS aldo - A morse code trainer
Re: Giuseppe Martino in <[EMAIL PROTECTED]> > >But what's more important. The build failed here: > > > >configure: error: cannot find install-sh or install.sh in config > >./config > >make: *** [config.status] Error 1 > > The problem is a missed Build-Depends aboud automake1.9. The proper way to fix that is to ship a bootstrapped .tar.bz2. Your tarball does not build: $ ./configure configure: error: cannot find install-sh or install.sh in config ./config $ sh bootstrap configure.ac: installing `config/install-sh' configure.ac: installing `config/mkinstalldirs' configure.ac: installing `config/missing' Makefile.am: installing `./COPYING' Makefile.am: installing `./INSTALL' libaudiostream/Makefile.am: installing `config/depcomp' $ ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes [...] Please provide an updated upstream tarball. This will allow you to drop the build-dependency on the autotools, which is considered evil by most people anyway. Oh, and please ship real files in the tarball: lrwxrwxrwx 1 cb cb 31 2005-09-12 13:29 COPYING -> /usr/share/automake-1.9/COPYING lrwxrwxrwx 1 cb cb 31 2005-09-12 13:29 INSTALL -> /usr/share/automake-1.9/INSTALL (Yes, having 1003951 copies of the GPL on your filesystem is a waste of space, but that's the way it works.) Re: Giuseppe Martino in <[EMAIL PROTECTED]> > > I have two things to say about this: > > - debian/ should not be in the orig.tar.gz, but only in the diff.gz. See > > [1]. The .orig.tar.gz should be identical to the upstream tarball (re-bz2-ipped in your case). > Fixed package on: http://dakordhost.homelinux.org/~denever/aldo_debian Host down. Consider using mentors.debian.net or something like that if your home machine isn't up 24/24. The last CW course I held lies now several years back, but still a point from a teacher's view: starting with "e,i,s,h,t,m,o" is not the optimal thing. Start with characters that are more distinct. I don't have my old instructions here, but the characters were mixed, even with some numbers in between, iirc. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS aldo - A morse code trainer
Re: Bas Wijnen in <[EMAIL PROTECTED]> > > Please provide an updated upstream tarball. > > > > This will allow you to drop the build-dependency on the autotools, > > which is considered evil by most people anyway. > > Huh? Looking at the output of bootstrap, it runs the autotools. Or do you > mean it should be run before packaging the tarball? The upstream tarball on savannah is broken, it should be updated. (The point of the autotools is that they enable building on as many machines as possible, including those that do not have the autotools installed.) > In any case, I strongly disagree that build-depending on autotools is wrong. > The autotools were created to make platform-independant building possible on > platforms with no special programs (such as the autotools) installed. > However, if they _are_ available, then it's a good idea to regenerate all the > files, because old versions of the autotools can have bugs (and it makes sure > that the source files such as Makefile.am are actually the versions which > produced the Makefile). It's a good idea to use the output from the newest > autotools if possible, and on a Debian system that is easily possible, namely > by build-depending on them. It's a matter of taste. I prefer a bootstrapped tarball, because re-bootstraping on the autobuilders can cause all kinds of funny build failures that weren't there otherwise. (And in most cases it's a waste of build time.) > > Oh, and please ship real files in the tarball: > > > > lrwxrwxrwx 1 cb cb 31 2005-09-12 13:29 COPYING -> > > /usr/share/automake-1.9/COPYING > > lrwxrwxrwx 1 cb cb 31 2005-09-12 13:29 INSTALL -> > > /usr/share/automake-1.9/INSTALL > > I agree that real files should be shipped in the tarball. However, to make > sure the diff doesn't get too large, remove such files in the "clean" target > (in debian/rules). If there are real files in the tarball, they shouldn't be in the diff.gz anyway. > > The .orig.tar.gz should be identical to the upstream tarball > > (re-bz2-ipped in your case). > > It should, but as far as I understood it he was himself upstream, so he can > change the upstream tarball. :-) If I understood it wrongly, he should urge > his upstream to remove it, and just use it like this in the mean time. He is upstream, and that's why the tarball should be fixed. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: willing to adopt a few orphaned packages
Re: Stan Vasilyev in <[EMAIL PROTECTED]> > I am looking for a sponsor for a series of packages I adopted and rebuilt: > > bbsload (new upstream version) > bbappconf (same version, fixed some documentation) > bbpager (same version, fixed some documentation) > > Coming soon: > mindterm, ksocrat, uncc and maybe more > > All packages are available at my personal web server (hosted on my home > computer) > > http://stanvasilyev.homelinux.com/debian/ > > There are also auctiongallery and wlassistant that I have been packaging > for a while but nobody uploaded them yet. I would appreciate if someone > would look into that. wlassistant is already in Ubuntu, it would make > sense for it to be in Debian as well. > > On a side I have a question about copyright file in the packages that I > adopted. There is a place in the file where it says this package was > debianized by ... on ... Should I keep the original creator of the > Debian package or can I put my own name and date? No, don't do that. Keep the original version. If you want to, you can add something like "the current maintainer is ...", but this is not required. Please revert that. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: xmms-musepack - input plugin for playing mpc music files.
Re: Patryk Cisek in <[EMAIL PROTECTED]> > Name: xmms-musepack > Version: 1.2 > Section: sound > License: BSD > RFP -> ITP: 241287 > Upstram home page:http://musepack.net debian/copyright: [...] | License: | Copyright (c) The Regents of the University of California. | All rights reserved. I'm sure this is wrong :) Apart from that, no source file includes a (C) statement. You might want to ask upstream to include that in the next release. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS aldo - A morse code trainer
Re: Giuseppe Martino in <[EMAIL PROTECTED]> > On Mon, Sep 12, 2005 at 01:44:14PM +0200, Christoph Berg wrote: > > The proper way to fix that is to ship a bootstrapped .tar.bz2. > > Ok, I replaced every link with a copy of its normal file > (`config/install-sh' `config/mkinstalldirs' `config/missing' `./COPYING' & > Co.) Ok, it does compile now. (But have a look at Joost's suggestion anyway for next time.) > > The last CW course I held lies now several years back, but still a > > point from a teacher's view: starting with "e,i,s,h,t,m,o" is not the > > optimal thing. Start with characters that are more distinct. I don't > > have my old instructions here, but the characters were mixed, even > > with some numbers in between, iirc. > > Well there are a lot of morse learning methods. > Aldo implement also Koch method. > Would you describe your method? I can code its in aldo. > Futher I'm working on a programmable aldo (I'm going to use GUILE) > so everybody could implement his method with a GUILE-Scheme script. The difference was basically the order in which letters where added to the alphabet. You should probably make that user-configurable. I've had a look at the package: * please use a real name in the changelog (lintian: W: aldo source: changelog-should-mention-nmu) * your Build-Depends look overly restricted. (Why >= x.y for all packages?) libc6-dev is listed twice. (lintian will complain about libc6-dev when you fix that). * Description: - the license/operating system does not really matter here - the Koch method could use an explanation - on the other hand, "read from file" explains itself - "With this exercise you can train receiving randomly generated callsigns. * debian/copyright lists only you, but some files have "improved : Bob Harrington" - did he contribute much, i.e. does have a copyright on that files himself? NB, how does aldo compare to the other morse programs (apt-cache search morse) in Debian? Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: update of squashfs-tools package
Re: Frédéric BOITEUX in <[EMAIL PROTECTED]>
> > According to the bts, there's only a RFH, not an O. Did he forget to do
> > this?
>
> I don't know if he has really orphaned it, but in the fact, he don't have time
> to maintain it and didn't found another DD to help him, only some outside
> Debian's
> interested people like me...
It isn't orphaned, he only wants help ("RFH"). Judging from that Piotr
didn't really react to your NMU in March, there's probably a chance
that he lets you adopt the package anyway.
> > package, you can retitle it to ITA (but discuss this with him before doing
> > it).
> I'll try to recontact him to clarify his position...
Asking him can't hurt :)
> > Also write a comment in the bug report about the situation, explicitly
> > saying
> > it shouldn't be removed, because you want to adopt it.
> I already added a comment asking for the bug reporter to check if it's
> already present
> in the Sid (now Sarge) version, but I didn't had any answer since some
> months...
It does compile now, the changelog should have closed the bug if the
patch was applied.
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
Re: Renaming the package and other things
Re: Nelson A. de Oliveira in <[EMAIL PROTECTED]> > I am planning to rename the source package to "biofox" only, instead > mozilla-firefox-biofox. Why? The user won't see the source package name change. It's only extra hassle for you and the ftp-masters. If you really want, rename the binary package only. NB, how does upstream call the package/program/tarball? Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: plans -- web calendar
Re: Craig Small in <[EMAIL PROTECTED]> > > > IMO, the description should be about the application, it shouldn't > > > be a comparative. > > > > Agreed. I'd say rather that enough information about the application > > should be included so that the reader can make their own comparison. > > You can do both. If your package has feature "flaming unicycles" while > package foo does not, just mention that feature, but no need to mention > that foo doesn't have it. > > Putting it another way. You are a user and you want a web calendar > thingy? Which package satisfies your requirements better? Obviously > there is only so much a package description can do. The good thing about Debian is choice. The bad thing about Debian is choice. I always like it very much when a package description says "this package supports A (but not B), whereas the bla package supports B (and only an outdated version of A)". Given 3 packages A, B, and C, and A says that "it supports blubb, which B does not", I usually prefer A over B and C, whatever the value of "blubb" is ;-) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: [RFS] qterm: BBS client for X Window System written in Qt
Re: LI Daobing in <[EMAIL PROTECTED]> > I need a uploader for the new version of qterm. it's not lintian and > linda clean(without-manpages). I have uploaded it to mentors[1], and > submit it at sponsors. Why not write a manpage? There are tools that automate that. (And if you do not like roff, you can still use pod, etc.) Nit-picking about the packaging: * 1.log does not seem useful. * debian/rules: DEB_AUTO_UPDATE_DEBIAN_CONTROL := yes This sucks, the generated control file is ugly as hell (it does build-depend on build-essential, etc.). Please fix that. * debian/copyright probably needs newer copyright years. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: [RFS] qterm: BBS client for X Window System written in Qt
Re: LI Daobing in <[EMAIL PROTECTED]> > a manpage for a gui program without argument supporting is useless, > and many one do not write manpages[1] > > [1] http://lintian.debian.org/reports/Tbinary-without-manpage.html Citing linitian warnings as an excuse not to fix bugs is certainly strange. > > * debian/rules: > > DEB_AUTO_UPDATE_DEBIAN_CONTROL := yes > > This sucks, the generated control file is ugly as hell (it does > > build-depend on build-essential, etc.). Please fix that. > I don't agree, at least it works. No it doesn't. It makes backporting unnecessarily hard, among other things. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: ITP: libpam-require -- PAM module to allow and/or deny particular users and/or groups
Re: Timo Weingärtner in <[EMAIL PROTECTED]> > pam_group is good, exactly what I need. A few weeks ago I searched for such a > module and only found this one. > > Shall we close this ITP? Yes, as there's a better alternative already in Debian. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Bug#329996: ITP: xmms-oggre -- ogg disk output plugin for XMMS
Re: Ryan Schultz in <[EMAIL PROTECTED]> > * Package name: xmms-oggre > Version : 0.3 > Upstream Author : Lars Siebold <[EMAIL PROTECTED]> > * URL : http://sourceforge.net/projects/my-xmms-plugs/ > * License : GPL > Description : ogg disk output plugin for XMMS I'll sponsor that one. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Maintainer is mailing list vs NMU
Re: Norbert Preining in <[EMAIL PROTECTED]> > > Add yourself to the Uploaders field. > > http://www.debian.org/doc/developers-reference/ch-pkgs.en.html#s-collaborative-maint > > Can I do this when I am not a DD till now, ie don't have a @debian.org > email? Think of "Uploaders:" as "Co-Maintainers:". Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: aptsh
Re: Marcin Wrochniak in <[EMAIL PROTECTED]> > Aptsh is an application similar to apt-shell from Conectiva's apt4rpm > - it is a shell-like frontend to Apt's command line tools, with > features that let users work faster: command completion (which de > facto works like bash-completion, with one exception: it's certainly > faster, since it's made in C++ and uses libapt-pkg directly), command > queues, history etc. What does it do besides command completion? Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: lprof -- Hardware Color Profiler
Re: Oleksandr Moskalenko in <[EMAIL PROTECTED]> > Package: lprof Uploaded. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Sponsors and the Uploaders field (was: RFS: dict-freedict ...)
Re: Thaddeus H. Black in <[EMAIL PROTECTED]> > Pierre Machard wrote: > > Do not worry if I set my name as uploader, so that it's easy for me to > > track packages I am sponsoring. The PTS does perfectly suit this, and you can even subscribe to a package before it is in the archive. There is no need to add yourself to Uploaders unless you really want to co-maintain the package. > On debian-project[1], Jonas Smedegaard wrote: > > Here's what I want (if anyone is interested - so far I have only > > experied hostility when I offer my weird non-sponsoring help to > > outsiders wanting packages into Debian): > > > > A requirement that the Maintainer field always either matches an entry > > in the Debian keyring or the email ends in "@debian.org" (so that > > group-maintained packages at Alioth - where at least one in each group > > must be a DD - is also allowed). > > > > A requirement that latest changelog entry must match the person signing > > the package for upload to the archive. > > If every Debian sponsor were required to do what Pierre suggests, would > it solve the problem Jonas raises? I guess yes. Apart from that the Debian keyring contains keys, not email addresses. (Yes, there are userids on the keys...) > (The question is not really meant to propose a new policy. It is just a > question, to help me to understand the issue better.) I fail to see why where that proposal would help. (If you want to know the actual uploader, check the signature on the .dsc.) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: fbgetty
Re: Sylvain LE GALL in <[EMAIL PROTECTED]> > I am looking for a sponsor to fbgetty. This package has been orphaned > and i want to take his maintainance. > > I have prepared a package, that can be found here: > http://sylvain.le-gall.net/debian-public Please fix your ServerName (or post URLs that do not require redirects because the trailing slash is missing). > The package seems almost lintian clean (2 warnings about outdated > config.sub/config.guess which are patched during the build, so it should > not generate any real errors). Any reason not to put the correct version in the .diff.gz? Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Sponsors and the Uploaders field (was: RFS: dict-freedict ...)
Re: Matthew Palmer in <[EMAIL PROTECTED]> > The primary reason I've seen expressed for desire to be added to the > Uploaders field is so that the sponsor can get a quick summary of a > sponsored package's state from the excellent developer.php script on > qa.debian.org. I've noticed that being able to do a "subscription" in > developer.php is a requested feature, but I can't see a way to do that yet. I'm working on it. Jeroen committed a first patch on Sunday, which makes the internal backend data more handy. There is no nice interface yet, but you can already put &packages=bla+foo+bar at the end of the URL and it will display additional packages. Suggestions on how to make that persistent are welcome. We already set a cookie, so we can extend that, but we probably don't want the additional packages to show up on every page you view (e.g. when clicking on the maintainer link on the PTS pages), so it has to be associated with "your" page (whatever that means). Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Please take a look over aspell-ro_0.50-2-1
Re: Eddy Petrişor in <[EMAIL PROTECTED]> > Could somebody take a look over it and tell me if I need to make any > changes before I list it on sponsors.d.n ? changelog: remove the [ ] part get an ITP and insert it here control: old Standards-Version you might want to use the new "Archticture: all" packaging variant, see for example #319675, otherwise you need to Provides: aspell6-dictionary copyright: you miss the (c) copyright line(s) you miss the license rules: way too much whitespace Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: rkward
Re: Thomas Friedrichsmeier in <[EMAIL PROTECTED]> > I don't really have the ambition to become a new maintainer, but if that's > what's needed, I might consider going through this. I'm a debian user, and a > software developer, and what I'm really trying to do, is get one of my > projects into debian. Hi Thomas, maintainer != (Debian) developer. If you maintain the package, and find someone who uploads it, you are the maintainer. If you go through the NM (confusingly, "new maintainer") process, you'll become a developer. But that's not necessary for a few packages. > Homepage: http://rkward.sourceforge.net > Downloads: http://sourceforge.net/project/showfiles.php?group_id=50231 > CVS instructions: http://sourceforge.net/cvs/?group_id=50231 > > I have already debianized the package (as you can see in downloads, and CVS), > and it seems to work ok. Of course I'm not sure, I did everything right. There is no source package (.dsc, .diff.gz, .orig.tar.gz). > Could you please advise me on what steps to take to get this package into > debian? http://people.debian.org/~mpalmer/debian-mentors_FAQ.html Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: How long are transition packages kept?
Re: Peter S Galbraith in <[EMAIL PROTECTED]> > How many releases do we keep transition packages? > > For example, debview was a real package in oldstage and is a transition > package in stable that depends on debian-el. Can I remove the > transition package now? Or must I wait after the next release? You can remove the transition package now; upgrades skipping a stable release are not supported. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: pcsx -- Sony PlayStation emulator
Re: Ryan Schultz in <[EMAIL PROTECTED]> > I believe all of the code in PCSX is DFSG-free, after research (see the ITP > bug #137355 for more info). Are there free games for PCSX? Otherwise it should probably go into contrib. (Like scummvm prior to 0.5.1-2 [1] and probably other interpreters/engines.) [1] http://packages.debian.org/changelogs/pool/main/s/scummvm/scummvm_0.7.1-3/changelog#versionversion0.5.1-2 Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: PGP and GPG keys...
Re: Adeodato Simó in <[EMAIL PROTECTED]>
> Perhaps if you post your keyid somebody can take a look and tell you
> whether it's fine or not?
The "official" test is:
GPGOPTS=" -q --no-options --no-default-keyring --no-auto-check-trustdb
--keyring $DESTDIR/nm.gpg --trust-model always"
echo "Let's test if its a version 4 or greater key"
VERSION=$(gpg ${GPGOPTS} --with-colons --with-fingerprint --list-keys 0x$KEYID
| awk -F : '$1 == "fpr" {print length($10)}')
if [ $VERSION -eq 32 ]; then
echo "Warning: It looks like this key is an Version 3 GPG key. This is
bad."
echo "This is not accepted for the NM ID Step. Please doublecheck and
then"
echo "get your applicant to send you a correct key if this is script
isnt wrong."
else
echo "Key is ok"
fi
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
Re: Problem in Debian Quality Assurance ?
Re: Jose Carlos do Nascimento in <[EMAIL PROTECTED]> > version=2 > opts=dversionmangle=s/\./-/ \ > http://www.phpconcept.net/pclzip/ > \.\./download.php.file=pclzip-([\d\-]+)\.tgz.* > > but in Debian Quality Assurance, versions are wrong showed. > > http://qa.debian.org/developer.php?login=debian%40psabs.com.br > http://dehs.alioth.debian.org/maintainer.php?name=libphp-pclzip The latest Upstream version seems to be 2.4 (2-4 in the filename), and both pages say 2-4. I guess dehs doesn't support dversionmangle; developer.php just takes the dehs output and displays it. (I have been thinking about sanitizing the dehs stuff, I find the output utterly confusing.) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Problem in Debian Quality Assurance ?
Re: Jose Carlos do Nascimento in <[EMAIL PROTECTED]> > I think that "Debian Quality Assurance" run "uscan". developer.php just wgets a DB file from dehs.alioth.d.o, you have to check their code. (I guess they are using some custom thing; uscan is not particularly well scriptable/parsable.) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS: august -- Tcl/Tk HTML editor
Re: Mario Iseli in <[EMAIL PROTECTED]> > I have now overworked my package - it doesn't contain mistakes anymore. > Would be nice if someone is interested in sponsoring! Hi, some comments: * the upstream URL in debian/copyright "may still be available for registration" * since there's no new .orig.tar.gz, it doesn't make sense to update the copyright to "Copyright (C) 1999-2005" * the .diff.gz contains debhelper cruft (august.postinst.debhelper, august.postrm.debhelper, files) * why did you remove README.Debian? * the other changes to debian/docs are also undocumented Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Creating a randomized cron entry
Re: Florian Weimer in <[EMAIL PROTECTED]> > I'd like to create a cron entry which is run once a day, at some > random time. This is necessary because the cron entry will result in > a request over the network, and I want to avoid that all hosts in a > time zone pound the server at the same time. I guess it is ok if you create a fixed entry for a machine, and the different entries on different machines will then do the load balancing. Just pick two random numbers and put them in /etc/cron.d/. Keep in mind that Debian users usually expect that daily cronjobs will still be run if the machine is down at night and anacron is installed. You might want to add an additional @reboot job. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Rationale behind script-not-executable lintian warning
Re: Bas Wijnen in <[EMAIL PROTECTED]> > I haven't seen anything in policy either, but I can't see any use for having a > shebang line without execute permissions. Can you give an example? Sometimes that's the easiest way to trick $EDITOR to get the syntax hilighting right (and it's portable between different $EDITORs). Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: dpkg-source and ignore everything outside of debian/
Re: Alejandro Exojo in <[EMAIL PROTECTED]> > I'm trying to generate a diff.gz in which only the debian/ directory is > included. filterdiff -z -i '*/debian/*' Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: dh_installmenu does not call update-menus --remove in postrm
Re: Michael Stilkerich in <[EMAIL PROTECTED]> > Is there any special reason why dh_installmenu does not call update-menu with > the --remove option upon package removal? Should I add the command to the > script myself? If you already have a prerm script, make sure it contains the #DEBHELPER# line. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Please tell if you found a sponsor
Re: Aníbal Monsalve Salazar 2006-08-31 <[EMAIL PROTECTED]> > >>See http://merkel.debian.org/~myon/sponsorstats/ > > The packages Charles is referring to are listed at: > > http://qa.debian.org/developer.php?login=debian-med-packaging%40lists.alioth.debian.org My script handles packages where the maintainer is a list address (iirc it just looks for @lists) specially, since it cannot tell who actually changed the package [1]. The alternative would be to treat all uploads for such packages as sponsored uploads which is worse imho. [1] it gets all data from projectb which knows the Maintainer, but neither Uploaders nor Changed-By from the .changes file. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Sponsoring gcc-h8300-hms
Re: Michael Tautschnig 2006-10-25 <[EMAIL PROTECTED]> > Furthermore, I'd like to add some notes: Probably brickos and the Lego > Mindstorms Kit is the only use of this and related packages. As such I wonder > whether it is worth trying to upgrade to binutils 2.16.x and gcc-4.x, because > this very outdated version of binutils and gcc just works for this very > special > application. As seen on [1], brickos (still) doesn't build on amd64. It looks like a porting problem in binutils, so that might be fixed by upgrading. [1] http://buildd.debian.org/build.php?pkg=brickos Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: postgres extensions and postgres multi-version support
Re: Florian Rothmaier 2014-01-21 <52de8102.8040...@ari.uni-heidelberg.de> > Currently, my "debian/control" has the following structure: > > Source: q3c > ... > > Package: postgresql-8.4-q3c > ... > > Package: postgresql-9.0-q3c > ... > > Package: postgresql-9.1-q3c > ... > > > While looking at other postgres extensions (e.g. "ip4r", "postgis", > "prefix"), I noted that in all cases, the extension is built for one > specific postgres version only, e.g. > > "postgresql-9.1-postgis" for the "postgis" source package or > "postgresql-9.3-prefix" for the "prefix" source package in jessie, > > so what I'm doing does not seem to be common practice. > > Hence my question is: does it make sense to use "pg_buildext" for the > multi-version support of postgres, or will this do more harm than good > and should therefore be dropped? Hi Florian, pg_buildext makes sense indeed, but you are missing one bit here, debian/control is regenerated from debian/control.in at "clean" time. This will rewrite the control file to include the supported PostgreSQL versions only. Have a look at any package build-depending on postgresql-server-dev-all to see how it works. Let me know if you have further questions. Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: postgres extensions and postgres multi-version support
Re: Florian Rothmaier 2014-01-24 <52e2acbf.1090...@ari.uni-heidelberg.de>
> It should be mentioned that my "debian/rules" is still based on an
> outdated version of "pg_buildext" from
> "postgresql-server-dev-all" (129). So the next step will be to use v152
> of this script which includes the "loop()" function and supports the
> entry "all" in "debian/pgversions".
The non-loop variant you have now is actually preferable over loop,
provided things actually work. Did you try if "make install" (or
pg_buildext install) puts things in the right location? If so, you
could get rid of debian/*.{install,docs,dirs}.
(For the docs, a nice workaround is to use
override_dh_installdocs:
dh_installdocs --all README.q3c
As many pieces of software are not VPATH-ready, it may well be that
using "pg_buildext loop" will make it easier to get everything
working, though... (I should finally document that mode in the
manpage.)
> Could you imagine to sponsor my package or would you say it should
> rather be maintained by the Debian Science maintainers? From my point of
> view, it's worth to have the postgres extension "q3c" packaged just for
> itself but it's also true that "q3c" is a dependency of a piece of
> astronomical software I seek to package in the near future.
It doesn't really matter where it is hosted or who is in the
Maintainer field - I can sponsor it, which doesn't mean the science
people couldn't be taking care of future versions.
Christoph
--
c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
Re: postgres extensions and postgres multi-version support
Re: Florian Rothmaier 2014-01-29 <52e94292.7000...@ari.uni-heidelberg.de> > If I look at other extension packages, e.g. > http://packages.debian.org/de/jessie/amd64/postgresql-9.3-ip4r/filelist > I can see that "README..gz" always goes to > "/usr/share/doc/postgresql--/". > > Your hint, the workaround > > override_dh_installdocs: > dh_installdocs --all README.q3c > > would do the job, but then I would have to patch Upstream's makefile > again to avoid the installation of README.q3c to two different places, > right? It's probably easier to include "rm debian/*/usr/share...*/README.q3c" in override_dh_installdocs. (Not entirely nice either, but works.) > P.S.: I haven't yet pushed my recent changes to the remote git repo on > alioth. Don't worry, I haven't been looking ;) Christoph -- c...@df7cb.de | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: RFS : Slune and dependencies
Re: RFS : Slune and dependencies [Duck <[EMAIL PROTECTED]>, Sat, Aug 09, 2003 at 06:36:53PM +0200, <[EMAIL PROTECTED]>] > My gnupg key has already been signed. I can't find it on the keyservers. Maybe you could also include your real name in your mails. Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgppH4KqC9lLg.pgp Description: PGP signature
Re: FAQ for debian-mentors
Re: Re: FAQ for debian-mentors [Joe Nahmias <[EMAIL PROTECTED]>, Thu, Sep 04, 2003 at 10:49:09AM -0400, <[EMAIL PROTECTED]>] > 4) Same section, there should be a step 3.5 which says something > like: "Upload the source package to machine for public review, > mentors.debian.net provides a service that is useful for this purpose". You have to stress that people actually upload the _source_ package. If not told, they tend to provide i386 binaries. Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgp1RdhrvqCbg.pgp Description: PGP signature
Re: FAQ for debian-mentors
Re: Re: FAQ for debian-mentors [Matthew Palmer <[EMAIL PROTECTED]>, Mon, Sep 08, 2003 at 02:19:26PM +1000, <[EMAIL PROTECTED]>] > > You have to stress that people actually upload the _source_ package. If > > not told, they tend to provide i386 binaries. > > Is "all of the files (.orig.tar.gz, diff, changes, dsc, and binary > package(s)) relating to your package" not strong enough? I would have > thought it would have been clear enough. Just writing "source package" > would be less informative, IMHO. This way, at least, there's half a chance > that people will notice that they're missing some files... I wrote that mail when I saw the -mentors posting [1]. The page page pointed to there contains only i386 binary packages (on a side note, I think these should be architecture all packages). I then went to the Mentors FAQ, searched for "source" and found nothing. Upon close inspection, your statement is clear, but I'd change it: > # Provide a publically accessible place where all of the files > (.orig.tar.gz, diff, changes, dsc, and binary package(s)) relating to > your package can be downloaded from. # Provide a publically accessible place where all of the files relating to your package can be downloaded from, that is both the source package (.orig.tar.gz, .diff, and .dsc files) and binary packages along with .changes files. [1] http://lists.debian.org/debian-mentors/2003/debian-mentors-200309/msg00056.html Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgpJu9oUADKIK.pgp Description: PGP signature
Re: fvwm-themes gets better
Re: fvwm-themes gets better [Andrei Mitrofanow <[EMAIL PROTECTED]>, Tue, Sep 09, 2003 at 12:27:53AM +0200, <[EMAIL PROTECTED]>] > nobody interestet to fvwm-themes? > > http://smilebef.homelinux.org/~smilebef/ If you want a sponsor, you probably have to provide source packages, not only i386 binaries. (I'm wondering if this shouldn't be an architecture "all" package anyway.) See also: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgppOh25NtTd3.pgp Description: PGP signature
Re: Bug#210243: ITP: xspringies -- Interactive 2D mass/spring simulation system for X
Re: Re: Bug#210243: ITP: xspringies -- Interactive 2D mass/spring simulation system for X [Steve Kemp <[EMAIL PROTECTED]>, Mon, Sep 15, 2003 at 04:21:39PM +0100, <[EMAIL PROTECTED]>] > > $PATH is almost always trusted; the exception is setuid programs which > > should sanitize PATH. xspringies is not setuid, is it? > > It is not setuid/setgid no, but I still think it's best to not trust > the PATH - sure it's not critical, but it's a good think "just in > case". I like to use $PATH with ~/bin at the beginning to allow me to put wrappers around programs. For example I could have a shell script ~/bin/gzip that calls the real gzip after doing some stuff: $!/bin/sh echo "Compressing $1" >> ~/log/gzip.log exec /usr/bin/gzip "$@" It doesn't make much sense in this example, but I'd find it rather annoying if packages would have hardcoded paths compiled in. Some weeks ago there was a discussion whether mutt should call /usr/bin/gpg rather than gpg because "gpg was security critical". I have a ~/bin/gpg that calls a agent-enabled version of gpg, which makes perfectly sense. Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de/ Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgpQwUm9rKUHv.pgp Description: PGP signature
Re: Spellcheck
Re: Spellcheck [Barbara Green <[EMAIL PROTECTED]>, Tue, Sep 16, 2003 at 09:14:25AM -0400, <[EMAIL PROTECTED]>] > When I am beeing told to open registration key I can't open.My number is > #MIIG-54408834. Hello, I'm afraid we can't help you there. Can you be more specific which program you are talking about? It probably isn't part of Debian GNU/Linux, so you will have to send your question to the author of that software. More info about Debian can be found at www.debian.org. Christoph Berg -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de/ Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgpEHahhbJnC5.pgp Description: PGP signature
Re: Special requirements for scripts in /etc/rcS.d?
Re: Bob Proulx in <[EMAIL PROTECTED]>
> perl -e 'printf("%o\n",(stat($ARGV[0]))[2]);' /tmp # print mode in octal
> 41777
>
> My only question now is where did that '4' come from in the mode? But
> the last four digits always seem to be correct.
stat(2):
S_IFDIR 004 directory
Christoph
--
Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de/
Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944
signature.asc
Description: Digital signature
Re: no subject
Re: Aaron MartineZ Kill All Windows in <[EMAIL PROTECTED]> > Hey there people my name is Aaron Martinez i being working with Debian > for like 2 to 3 years seriously hard i will like to maintance a packaged > for eggdrops or Bitchx since i'm a developer on Bitchx i will like to > help Debian in any kind of ways so if any of you guys can sponsor me you > guys wouldn't not be sorry thank you for reading this email Hi, apt-cache policy eggdrop 1.6.17-2 0 700 http://ftp.de.debian.org sarge/main Packages apt-cache policy bitchx 1:1.0-0c19.20030512-2 0 700 http://ftp.de.debian.org sarge/main Packages both are already packaged for Debian, so you will either have to ask the maintainers if they want to co-maintain it with you or find other stuff to package. Oh, and please learn to use interpunctation :-) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: compilers that self compile
Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]> > >* how packages like those go in the repository for the first time? > > By ignoring build-depends while in some way you've made your system to > actually be able to build the package. I.e., you've for example > bootstrapped the compiler. Then you install it locally, and build your > package again, this time the normal way, and you upload it. After it's > in the archive, it's rebuildable by itself. Of course, the bootstrapping has to be done for each architecture again. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: no subject
Re: Aaron MartineZ Kill All Windows in <[EMAIL PROTECTED]> > Hey there people my name is Aaron Martinez i being working with Debian > for like 2 to 3 years seriously hard i will like to maintance a packaged > for eggdrops or Bitchx since i'm a developer on Bitchx i will like to > help Debian in any kind of ways so if any of you guys can sponsor me you > guys wouldn't not be sorry thank you for reading this email Hi, apt-cache policy eggdrop 1.6.17-2 0 700 http://ftp.de.debian.org sarge/main Packages apt-cache policy bitchx 1:1.0-0c19.20030512-2 0 700 http://ftp.de.debian.org sarge/main Packages both are already packaged for Debian, so you will either have to ask the maintainers if they want to co-maintain it with you or find other stuff to package. Oh, and please learn to use interpunctation :-) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: compilers that self compile
Re: Jeroen van Wolffelaar in <[EMAIL PROTECTED]> > >* how packages like those go in the repository for the first time? > > By ignoring build-depends while in some way you've made your system to > actually be able to build the package. I.e., you've for example > bootstrapped the compiler. Then you install it locally, and build your > package again, this time the normal way, and you upload it. After it's > in the archive, it's rebuildable by itself. Of course, the bootstrapping has to be done for each architecture again. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Strange problem, symlinks and parent dirs
Re: Fabio Tranchitella in <[EMAIL PROTECTED]> > $ ln -s dir1/dir2 dir2 > $ cd dir2 > $ pwd > /home/kobold/dir2 > $ mv file .. > > The file is moved into /home/kobold/dir1 instead of /home/kobold > Is this right? IMHO it's confusing for the user. If pwd returns > "/home/kobold/dir2", .. should be resolved as "/home/kobold". Sure. ".." is resolved by the kernel which doesn't care about the "name" of your pwd. It just moves the file to the physical .. directory, i.e. doesn't go the symlinks back. That's why I have the following in by .bashrc: | alias pwd='/bin/pwd;builtin pwd' tcsh(1) has a "symlinks" option which tries to fix this, but that doesn't work in all cases. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: source NMU for jmon (approved by maintainer)
Re: Steve Langasek in <[EMAIL PROTECTED]> > Regardless of the maintainer's comments, DDs should not sponsor NMUs; it is > the responsibility of the uploading developer to personally verify the > correctness of the changes in an NMU, and it is incorrect to upload changes > in an NMU that have not first been forwarded to the BTS, therefore it's > simpler if you upload any patches to the BTS and ask someone to do an NMU > for the bug, rather than asking someone to upload based on packages that > you've prepared separately. I'd expect any sponsored upload to be checked by the sponsoring DD, be it uploads for packages I (as a non-DD) maintain, for NMUs, or for QA uploads. Preparing a (source) package and asking for a sponsor is merely to ease the uploading DD's task, who will rebuild the binary package anyway in most cases. (And if it's a proper NMU, there will be a patch in the BTS anyway.) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: "Cannot represent change" error upon PNG file addition
Re: Nick Lewycky in <[EMAIL PROTECTED]>
> >--- /usr/bin/dpkg-source2004-11-11 21:15:52.0 +0100
> >+++ /home/ifi/bin/dpkg-source 2004-12-08 14:45:00.0 +0100
> >@@ -406,7 +406,7 @@
> >$ENV{'LC_ALL'}= 'C';
> >$ENV{'LANG'}= 'C';
> >$ENV{'TZ'}= 'UTC0';
> >-exec('diff','-u',
> >+exec('diff','-au',
>
> That's terrifying. I just tried diff -a on two PNG files and it worked
> just fine. But will it always work?
This breaks your package for all people that are not using a patched
dpkg-source. They can't unpack/pack it. Don't do it.
Christoph
--
[EMAIL PROTECTED] | http://www.df7cb.de/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian Health/watch files
Re: Roland Gruber in <[EMAIL PROTECTED]> > >ftp://ftp2.sf.net//<2_first_letters>// > > so the problem might be that I use HTTP in my watch line? I'd always use http in favour of ftp. ftp is obsolete. For sf.net, use the following page to watch (works for every project that has released any files): http://prdownloads.sourceforge.net/lam/ > I will file a bug at the Alioth project. Maybe this will make things > clearer. I don't know about the details, but dehs lagged behind for some of my packages, too. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Debian Health/watch files
Re: Luk Claes in <[EMAIL PROTECTED]> > | http://prdownloads.sourceforge.net/lam/ > > The problem is that this kind of URLs > (http://prdownloads.sourceforge.net) do not work with dehs. Of course you have to tack the filename with the () pattern to the end. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: About x.org and other packages
Re: Rafael Fernández López in <[EMAIL PROTECTED]> > I'm looking for a package that I like to keep it care of. You have to find one yourself. For example, browse the WNPP bug list (if you are really interested in Debian, you know what this is) to see if there's something interesting. > I've some questions, of course for being a newbie Debian maintainer > (because I'm an "advanced?" Debian user), I'm not going to take care of > x.org, but I'd like to see it into official Debian repositories instead > of our XFree86, x.org is more powerful and It improves in many ways > compatibility. So I was wondering if someone is going to bring it to > Debian. X.org will eventually be part of Debian, but only after Sarge. > I've read how I can reach the Debian maintainer role, and I've some > questions. I've to write here for the package that I want to maintain, > true?, then I should be helped by another maintainer to learn how to > build packages the best way, right? To start, read the newmaint-guide. > I think I got the most important points about how to be a Debian > maintainer and I dream with a "[EMAIL PROTECTED]" email address, hehe. *bzzt* this is a sure way *not* to get one ;-) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: filing bugs against my own package
Re: Jereme Corrado in <[EMAIL PROTECTED]> > I have been fixing some upstream bugs that I discovered in one of the > packages I maintain. I plan to package a new version with these fixes > soon but I am waiting for upstream as they may release shortly, and > include these fixes. Should I file bugs against my package in the > interim, closing them once my sponsor uploads a package with a fix? I'd file the bugs only if they are so severe that you would expect that a user could file them in the time until the next upload. Or you apply your bugfixes to the current package and upload that before the next release. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Versioning prereleases
Re: Adeodato Simó in <[EMAIL PROTECTED]> > Given the above premise, 5.0-betaX, 5.0-preX, 5.0.0 is a possibility. > I use this for amarok. Or use 5.0-rel, which sorts after -beta and -pre. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Looking for an advocate
Re: Shachar Shemesh in <[EMAIL PROTECTED]> > As someone who has only recently tried to scale the "new developer" > documentation, I can tell you that there is room for improvement. I have > been going over those docs several times in the past few days, and each > time I find myself lost in front of a page full of links embedded inside > text, looking for the right doc I know is there, because I read it in > the past. Speaking as someone who recently passed the NM queue (I'm waiting for DAM approval), I can say that the best way to get used to all stuff is to just use it. I've been using Debian for several years now, and have been hanging around in Debian-related IRC channels where you just see all sorts of packaging stuff/buildd failures/policy issues/bug reports/whatever all day, so after some time you just "know" it. When I finally decided to apply for NM, I already had some half a dozend packages in the archive and didn't have to read many documents since I either knew the answer myself or knew where to look. (There's the policy, the developers reference, and a handful of HOWTOs that I either stumbled over previously or were found by Google quickly.) I'm not saying that there's no room for improvement, but the newmaint-guide should give enough head start that everything else will just become a "less $right_filename" over the time after you've created your first package. After all, Debian is so complex that you can't expect to learn "everything" by reading a handfull of documents in a short time. > [...] Frankly, I can empathize with his mistake. After all, I clean > forgot to to file an ITP in the BTS for wnpp for my package... > > P.S. > For those so versed in the jargon soup that the last sentence did not > sound strange to them, it was supposed to be ironic (despite being > factually true). It didn't sound strange, but I know what you mean nonetheless ;) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: What does RFS mean?
Re: Hugo Vanwoerkom in <[EMAIL PROTECTED]> > Another question: there are certainly enough of them on this list, but > are they answered? E.g. a note by a Debian Developer "Yes I will sponsor?" I guess that in most cases a reply is also sent to the list, i.e. if there is none, no sponsor was found. It's more effective to ask people you know directly to sponsor, e.g. on IRC. (This isn't meant to stop you from asking here, it's just to rectify the assumption that every sponsor request eventually gets handled automatically.) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: CYBOI looking for Sponsor
Re: Christian Heller in <[EMAIL PROTECTED]> > we are looking for a sponsor for our CYBOI package. > I've already sent an ITP roughly describing it (see below). > Our project members would be glad to see the package in Debian soon :-) It helps if you post a URL to the package here. See also http://people.debian.org/~mpalmer/debian-mentors_FAQ.html. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: localized manpages to package or manpages-
Re: Michelle Konzack in <[EMAIL PROTECTED]> > curently i am working on some manpages and po files > for german. Specials for "katoob". > > I like to know whether I should put the german manpage > into the "katoob" package or into "manpages-de". Into katoob. manpages-de should contain translations of manpages of general interest (see the 'manpages' package). If katoob users really don't want it there, they can still use localepurge. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Program without source code
Re: Nelson A. de Oliveira in <[EMAIL PROTECTED]> > Is it allowed to release a package that don't have the source codes > available? > For example, program XYZ just have a binary of it, but no source code. No one will prevent you from releasing it. It can't go into Debian though, because it won't be free software. (And it can't go into non-free either, since it would be impossible to fix bugs in the program.) Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Open ITP without apparent work on it
Re: Matthew Palmer in <[EMAIL PROTECTED]> > Make a note in the ITP that you are keenly interested in seeing Open Xchange > in Debian, and offer to help the initial ITP filer in any way, noting that > if you don't hear anything, you'll commence packaging it yourself. If that > doesn't get a response in a few days, just go ahead and do it. Don't forget to Cc: the ITP submitter, messages sent to [EMAIL PROTECTED] don't get forwarded to the bug submitter. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Open ITP without apparent work on it
Re: Frank Küster in <[EMAIL PROTECTED]> > Isn't there an "owner" tag for WNPP bugs? Then Shachar could set > himself as the owner. This won't get you the messages forwarded either. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Open ITP without apparent work on it
Re: Willi Mann in <[EMAIL PROTECTED]> > What's your definition of "owner"? http://www.debian.org/Bugs/server-control -> owner Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Revision control systems and Debian packages
Re: Jamie Jones in <[EMAIL PROTECTED]> > Can anybody suggest some good revision control systems for maintaining > Debian packages. I'm about to outgrow using RCS on the debian directory > and wanted to get an idea of what other maintainers are using for their > packages. svn-buildpackage. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: A question...
Re: [EMAIL PROTECTED] in <[EMAIL PROTECTED]> > i want to join Debian as a developer . > and i want be debian developer. > i mean to say that i want to join Debian organization as a permanet > job/Employee so can any one tell me that what is the procedure , so i will > follow that procedure. Hi, Debian is not an employer. Read http://www.debian.org/devel/join/. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: how to contact dh-make-perl developpers ?
Re: Marc Chantreux in <[EMAIL PROTECTED]> > I wrote a patch for dh-make-perl that ease its use by adding some > warnings. I wrote a mail to the maintainer but have no answer. File a wishlist bug against dh-make-perl requesting the inclusion of your patch. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Volk wird nur zum zahlen gebraucht!
Re: René van Bevern in <[EMAIL PROTECTED]> > > I think merely marking the list "subscribers only" would do the job better. > > It would also leave most of the spam out of it. > > This would prevent non-scubscribers from posting here and reading answers > via the list archives or a usenet gateway like GMANE. http://lists.debian.org/whitelist/ | whitelist mailing list | Generic whitelist | This is a special pseudo-mailing list to which people can subscribe to | prove they are not spammers. | | This allows one to avoid the restrictions imposed on non-subscriber | posts to other mailing lists, in particular the mailing lists that | allow posts only from subscribers. Christoph -- [EMAIL PROTECTED] | http://www.df7cb.de/ signature.asc Description: Digital signature
Re: Modification on the installer: "Debian software selection"
Re: Njes Nilsen in <[EMAIL PROTECTED]>
> What I want is to edit the installation so the user get another option
> here, which will install some given packages.
> I've read some of the information about how to hack the installer on the
> debian wiki page, but can't find any information about how to do this.
The dialog you saw is from tasksel, which takes the "Task:" field in
the packages list.
| grep-available -FTask mail -sPackage
If you want to add own package collection, it's probably the easiest
to build a meta package that depends on the different packages.
("equivs" might help there.) I'm not sure if it's possible to add
tasks to tasksel without changing the package control files or
Packages.gz.
Christoph
PS: I'm missing the good ol' "unix server" task from woody...
--
[EMAIL PROTECTED] | http://www.df7cb.de/
signature.asc
Description: Digital signature
Re: RFS : Slune and dependencies
Re: RFS : Slune and dependencies [Duck <[EMAIL PROTECTED]>, Sat, Aug 09, 2003 at 06:36:53PM +0200, <[EMAIL PROTECTED]>] > My gnupg key has already been signed. I can't find it on the keyservers. Maybe you could also include your real name in your mails. Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgp0.pgp Description: PGP signature
Re: FAQ for debian-mentors
Re: Re: FAQ for debian-mentors [Joe Nahmias <[EMAIL PROTECTED]>, Thu, Sep 04, 2003 at 10:49:09AM -0400, <[EMAIL PROTECTED]>] > 4) Same section, there should be a step 3.5 which says something > like: "Upload the source package to machine for public review, > mentors.debian.net provides a service that is useful for this purpose". You have to stress that people actually upload the _source_ package. If not told, they tend to provide i386 binaries. Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgp0.pgp Description: PGP signature
Re: FAQ for debian-mentors
Re: Re: FAQ for debian-mentors [Matthew Palmer <[EMAIL PROTECTED]>, Mon, Sep 08, 2003 at 02:19:26PM +1000, <[EMAIL PROTECTED]>] > > You have to stress that people actually upload the _source_ package. If > > not told, they tend to provide i386 binaries. > > Is "all of the files (.orig.tar.gz, diff, changes, dsc, and binary > package(s)) relating to your package" not strong enough? I would have > thought it would have been clear enough. Just writing "source package" > would be less informative, IMHO. This way, at least, there's half a chance > that people will notice that they're missing some files... I wrote that mail when I saw the -mentors posting [1]. The page page pointed to there contains only i386 binary packages (on a side note, I think these should be architecture all packages). I then went to the Mentors FAQ, searched for "source" and found nothing. Upon close inspection, your statement is clear, but I'd change it: > # Provide a publically accessible place where all of the files > (.orig.tar.gz, diff, changes, dsc, and binary package(s)) relating to > your package can be downloaded from. # Provide a publically accessible place where all of the files relating to your package can be downloaded from, that is both the source package (.orig.tar.gz, .diff, and .dsc files) and binary packages along with .changes files. [1] http://lists.debian.org/debian-mentors/2003/debian-mentors-200309/msg00056.html Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgp0.pgp Description: PGP signature
Re: fvwm-themes gets better
Re: fvwm-themes gets better [Andrei Mitrofanow <[EMAIL PROTECTED]>, Tue, Sep 09, 2003 at 12:27:53AM +0200, <[EMAIL PROTECTED]>] > nobody interestet to fvwm-themes? > > http://smilebef.homelinux.org/~smilebef/ If you want a sponsor, you probably have to provide source packages, not only i386 binaries. (I'm wondering if this shouldn't be an architecture "all" package anyway.) See also: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgp0.pgp Description: PGP signature
Re: Bug#210243: ITP: xspringies -- Interactive 2D mass/spring simulation system for X
Re: Re: Bug#210243: ITP: xspringies -- Interactive 2D mass/spring simulation system for X [Steve Kemp <[EMAIL PROTECTED]>, Mon, Sep 15, 2003 at 04:21:39PM +0100, <[EMAIL PROTECTED]>] > > $PATH is almost always trusted; the exception is setuid programs which > > should sanitize PATH. xspringies is not setuid, is it? > > It is not setuid/setgid no, but I still think it's best to not trust > the PATH - sure it's not critical, but it's a good think "just in > case". I like to use $PATH with ~/bin at the beginning to allow me to put wrappers around programs. For example I could have a shell script ~/bin/gzip that calls the real gzip after doing some stuff: $!/bin/sh echo "Compressing $1" >> ~/log/gzip.log exec /usr/bin/gzip "$@" It doesn't make much sense in this example, but I'd find it rather annoying if packages would have hardcoded paths compiled in. Some weeks ago there was a discussion whether mutt should call /usr/bin/gpg rather than gpg because "gpg was security critical". I have a ~/bin/gpg that calls a agent-enabled version of gpg, which makes perfectly sense. Christoph -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de/ Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgp0.pgp Description: PGP signature
Re: Spellcheck
Re: Spellcheck [Barbara Green <[EMAIL PROTECTED]>, Tue, Sep 16, 2003 at 09:14:25AM -0400, <[EMAIL PROTECTED]>] > When I am beeing told to open registration key I can't open.My number is > #MIIG-54408834. Hello, I'm afraid we can't help you there. Can you be more specific which program you are talking about? It probably isn't part of Debian GNU/Linux, so you will have to send your question to the author of that software. More info about Debian can be found at www.debian.org. Christoph Berg -- Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de/ Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944 pgp0.pgp Description: PGP signature
Re: Special requirements for scripts in /etc/rcS.d?
Re: Bob Proulx in <[EMAIL PROTECTED]>
> perl -e 'printf("%o\n",(stat($ARGV[0]))[2]);' /tmp # print mode in octal
> 41777
>
> My only question now is where did that '4' come from in the mode? But
> the last four digits always seem to be correct.
stat(2):
S_IFDIR 004 directory
Christoph
--
Christoph Berg <[EMAIL PROTECTED]>, http://www.df7cb.de/
Wohnheim D, 2405, Universität des Saarlandes, 0681/9657944
signature.asc
Description: Digital signature
Re: Lame Makefile problem
On Tue, Apr 15, 2003 at 06:38:27AM -0300, Leo Costela Antunes wrote: > I'm setting CFLAGS to -g in case the DEBUG build option is set but then > running > $(MAKE) CFLAGS=$(CFLAGS) > inside the build target results in overridden variables. > From what I could find, the Makefile uses CFLAGS internally to store > pkg-config output. Is there a way to tell Make to append to the CFLAGS > variable? In the Makefile, try "CFLAGS += -your_options". Also, you can try "CFLAGS=$(CFLAGS) $(MAKE)" instead, as this will less-rigidly override the settings inside the Makefile. Christoph -- Christoph Berg <[EMAIL PROTECTED]>, 0681/9657944 http://rw4.cs.uni-sb.de/~cb/ Universität des Saarlandes, Compiler Design Lab pgpJJ6WoTcCmK.pgp Description: PGP signature
Re: Mannaging non well-known port in inetd.conf/services
On Mon, Apr 28, 2003 at 01:17:28AM -0400, Jaldhar H. Vyas wrote: > > Of course there is. It's called "register your port with the maintainer of > > the /etc/services file". > > ...who is Anthony Towns ([EMAIL PROTECTED]) the maintainer of netbase. But > this is really only for "well-known ports" and I don't think either webmin > or zabbix count. Why can't we have packages register ports in /etc/services like they add new users to /etc/passwd? The problem is of course that the UIDs in /etc/passwd don't have to be fix for a given package, but TCP ports have to. But then, you can add more than one name per port. It just looks much better if "netstat -a" shows names instead of numbers. If there's more than one package for a port, the user could decide which one he prefers more. (cf. /etc/alternatives/*) Christoph -- Christoph Berg <[EMAIL PROTECTED]>, 0681/9657944 http://rw4.cs.uni-sb.de/~cb/ Universität des Saarlandes, Compiler Design Lab pgpCkKAS3wfRE.pgp Description: PGP signature
Re: Advice needed for packaging sigcperl library and SigC perl module
Re: Advice needed for packaging sigcperl library and SigC perl module [Michael Koch <[EMAIL PROTECTED]>, Wed, May 14, 2003 at 03:36:08PM +0200, <[EMAIL PROTECTED]>] > - libsigcperl-0.2 (the helper library) > - libsigcperl-dev (the development files) > - libsigc-perl (its a binary perl module) Why not libsigc-perl-0.2 and libsigc-perl-dev to be consistent? ^^ Christoph -- Christoph Berg <[EMAIL PROTECTED]>, 0681/9657944 http://rw4.cs.uni-sb.de/~cb/ Universität des Saarlandes, Compiler Design Lab pgpHUgNcGRrzC.pgp Description: PGP signature
Re: Becoming a Debian Maintainer - and behavior of DDs
[tl;dr: Richard is disappointed that I didn't advocate him for DM, while I did advocate other team members shortly after.] Hi Richard, Re: Richard B Winters 2016-06-22 <204e2c0e01254a766699d615036d2...@mail.mmogp.com> > During that time I worked with Christoph Berg, he advised not to play with > repository structure too > much - and asked that I didn't do more than I had to to get the stack working > again. I didn't recommend any particular repository structure. What I did recommend was not to bikeshed about that, stop discussing the layout, and start the real work. > Ferenc disregards all my work and makes his own repository on github (instead > of contributing to > the team repository) so that he can structure branches how he wants and move > to DEP-14 (I was never > opposed to that, but its exactly what Christoph asked me not to do when I > suggested it based off of > conversations I had with Ferenc) - and after Christoph states that he doesn't > care for > bike-shedding and had been working with me already on some of the packages > along with Adrian; he > reneged with regard to Ferenc's new repository (which was now missing all of > my changelog entries > which cataloged my contributions to the package, the very thing I didn't do - > but which Ferenc > complained about himself). It was suboptimal that Feri's changes were often staged elsewhere, but this was communicated, and I think now everything relevant is on git.debian.org. > Yes, after Debconf Christoph's whole demeanor towards me changed; He > blatantly started uploading > each and every one of Ferenc's packages, 'mindfully' attempting to accept the > ruby packages I > worked on - I'm guessing to try to make me feel better and shut me up. And > all he had to offer was Sorry if uploading your packages was wrong. Would it have been better to not do anything? At that point, corosync and pacemaker were the next packages in the stack that needed to be done. "Your" pcs and crmsh packages were due after that. That was the reason for the ordering. > a 'Sorry if your changelog entries got removed'. Sure I was still in the > uploaders field or > whatever, but the changes I made to code were no longer noted. I don't fancy changelog bikeshedding. All your changes made it into the next package, though possibly after re-re-rebasing them through whatnot git operations, the changelogs were a mess. I'd care more about getting the problems fixed. > I had also asked Christoph to advocate me as a maintainer 6-8 months prior to > now, which was > already almost a year after I had started working with the Debian-HA > packages. He told me he'd > consider it after the stack was done. He advocated for Ferenc very shortly > after Debconf, far > before the stack is complete (it still isnt complete even) - only a month or > two later. Now, months > after that, Christoph is advocating Ferenc as a DD. Richard I'm sorry to have to say that: You were not ready to be advocated for DM, while Ferenc was. I like mumbled something like "later" when you asked me about it. I should have been more explicit about this. > If you cannot tell, this is a play of favoritism, and isn't right. Christoph > was setting him up > with history (by only uploading his work and ignoring mine and others) so he > could exaggerate his > contributions and quickly help him to promote to DD. In his advocacy for > Ferenc, Christoph makes it > appear as if Ferenc did all that work himself - though he most certainly did > not. Countless months > did Adrian and I work on those softwares in the stack, and I feel that I at > least am being slapped > in the face. Adrian - however - was advocated by Christoph very near the same > time as Ferenc. I've never said anywhere that Ferenc did all work there. I did say though that he did excellent work. That's a fine difference. > I continued to discuss this with Myon and he goes as far as to type 'stop > yelling', 'I'm more than > happy to have you on the team but...' Almost as if he's threatening to remove > me from Alioth and > kick me off the team if I pursue this. Meanwhile, the only all-caps words in > IRC were from > Christoph (Myon). I'll post our conversation from today [1], but please note > that I do get he doesnt > _have_ to advocate me - not as a DM or DD. But playing favorites and lying is > not really - in my > mind - the thing a DD (or any Debian Contributor) should be doing. The all caps part was when you insisted that you were removed from the Uploaders fields and wouldn't listen to me trying to tell you that this was just wrong. You have been in the Uploaders fields of all relevant packages all the time. Christoph signature.asc Description: PGP signature
Bug#904269: RFS: rurple-ng/0.5+16-2, only packaging updates
Re: Thomas Koch 2018-07-22 <153227007588.243719.10944164547288454279.report...@thk1.roam.corp.google.com> > Alternatively, one can download the package with dget using this command: > > dget -x > https://mentors.debian.net/debian/pool/main/r/rurple-ng/rurple-ng_0.5+16-2.dsc Hi Thomas, the package on mentors uses a tarball that differs from the one in the archive. (But the package seems to build fine with the archive one.) > Changes since the last upload: > > * also build and ship the html manual The "build" entry in debian/clean is bogus: dh clean --with python2 dh_clean rm: cannot remove './build': Is a directory dh_clean: rm -f -- debian/rurple-ng.substvars ./build debian/files returned exit code 1 Could you fix that? (You can just put "rm -rf build" into the override_dh_auto_clean target you already have.) Christoph signature.asc Description: PGP signature
Bug#904269: RFS: rurple-ng/0.5+16-2, only packaging updates
Re: tho...@koch.ro 2018-07-29 <538053082.16587.1532857614...@office.mailbox.org> > thank you for taking a look. I fixed the clean step by adding a slash after > "build" in d/clean. I remember I was happy when I saw this finally working: > https://bugs.debian.org/511048 Oh cool, I had not seen that yet. > I uploaded the package again to mentors, this time with the orig tarball > that's already in the archive. Just uploaded the package. Thanks! Christoph signature.asc Description: PGP signature
Bug#953547: RFS: libusb3380/0.0.1+git20190125.c83d1e9-1 [ITP] -- USB3380 abstraction layer for libusb: development
Hi Sepi, there's a missing copyright attribution: ./cmake_modules/Findlibusb-1.0.cmake: # Adapted from cmake-modules Google Code project # # Copyright (c) 2006 Andreas Schneider # # (Changes for libusb) Copyright (c) 2008 Kyle Machulis # # Redistribution and use is allowed according to the terms of the New BSD license. # # CMake-Modules Project New BSD License # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions are met: # # * Redistributions of source code must retain the above copyright notice, this # list of conditions and the following disclaimer. # # * Redistributions in binary form must reproduce the above copyright notice, # this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # # * Neither the name of the CMake-Modules Project nor the names of its # contributors may be used to endorse or promote products derived from this # software without specific prior written permission. # # THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED # WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE # DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR # ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES # (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; # LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON This looks like the lib should be linked with pthreads: dpkg-shlibdeps: warning: symbol pthread_setname_np used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries dpkg-shlibdeps: warning: symbol sem_destroy used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries dpkg-shlibdeps: warning: symbol sem_post used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries dpkg-shlibdeps: warning: symbol pthread_join used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries dpkg-shlibdeps: warning: symbol pthread_sigmask used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries dpkg-shlibdeps: warning: symbol pthread_create used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries dpkg-shlibdeps: warning: symbol sem_init used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries dpkg-shlibdeps: warning: symbol sem_wait used by debian/libusb3380-0/usr/lib/x86_64-linux-gnu/libusb3380.so.0.0.1 found in none of the libraries /usr/lib/x86_64-linux-gnu/libpthread.so:00011370 T sem_close /usr/lib/x86_64-linux-gnu/libpthread.so:00010b60 T sem_destroy@@GLIBC_2.2.5 /usr/lib/x86_64-linux-gnu/libpthread.so:000115a0 T sem_getvalue@@GLIBC_2.2.5 /usr/lib/x86_64-linux-gnu/libpthread.so:00010b20 T sem_init@@GLIBC_2.2.5 /usr/lib/x86_64-linux-gnu/libpthread.so:00010e60 T sem_open /usr/lib/x86_64-linux-gnu/libpthread.so:000119c0 T sem_post@@GLIBC_2.2.5 /usr/lib/x86_64-linux-gnu/libpthread.so:00011950 T sem_timedwait /usr/lib/x86_64-linux-gnu/libpthread.so:00011780 T sem_trywait@@GLIBC_2.2.5 /usr/lib/x86_64-linux-gnu/libpthread.so:00011470 T sem_unlink /usr/lib/x86_64-linux-gnu/libpthread.so:00011740 T sem_wait@@GLIBC_2.2.5 (Not sure this is the correct solution, though.) The rest is fine and good to go I think. Christoph
Bug#954076: closing 954076
close 954076 thanks -- Mit freundlichen GrüÃen, Christoph Berg -- Senior Berater, Tel.: +49 2166 9901 187 credativ GmbH, HRB Mönchengladbach 12080, USt-ID-Nummer: DE204566209 Trompeterallee 108, 41189 Mönchengladbach Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer Unser Umgang mit personenbezogenen Daten unterliegt folgenden Bestimmungen: https://www.credativ.de/datenschutz
Bug#954186: RFS: libxtrxdsp/0.0.1+git20190830.eec2864-2 -- Library of DSP functions, developed for XTRX SDR
Re: Sepi Gair 2020-03-18 <370975eaac3fc60a4dc57cb13d003dc9ac47d78b.ca...@email.cz> > * Package name: libxtrxdsp >Version : 0.0.1+git20190830.eec2864-2 Hi Sepi, I suggest we wait with this upload until the -1 version has passed NEW. Christoph
Bug#956619: closing 956619
close 956619 thanks
Bug#962542: RFS: pat/0.9.0+dfsg.1-1 [ITP] -- Winlink client for sending and receiving radio mail
Hi Taowa, some comments on the package: The list of Depends is borked, I don't think you need any of the go packages at runtime as everything is statically linked. Why is libax25 there? It should be pulled in via shlibdeps, not explicitly. The description doesn't mention anything about hamradio, so an occasional reader might think this is something to be used over the internet. After reading it several times, looking at the pat homepage, and the winlink wikipedia article, I'm still not sure what the role of pat is. Could you add a sentence or two how it interfaces with the rest of the winlink network? Do I need to have a working ax25 modem or any of the other (radio?) protocols? Are there any programs in Debian that the package should recommend/suggest to get the radio interface working? The pat-configure(1) manpage is very confusing, it took me several minutes to figure out that the command to be invoked is actually "pat configure" with a space. Please fix the synopsis to make that clear. Likewise, I think the comment on debian/pat.lintian-overrides is confusing, I don't have any idea why you are citing that policy section there. It might help to put "pat configure" into quotes. It looked more like bad grammar than what you really wanted to say. I think the override comment should be, along with a full pattern: # "pat configure" has a separate manpage pat: manpage-without-executable /usr/share/man/man1/pat-configure.1.gz (recheck the full warning, I made it up here.) What's that bindata_assetfs.go binary blob? Should that also better be excluded with building the orig tarball? 73, Christoph DF7CB
Bug#970618: RFS: wwl/1.3+db-3 [QA] -- Calculates distance and azimuth between two Maidenhead locators
Re: Francisco Vilmar Cardoso Ruviaro > wwl (1.3+db-3) unstable; urgency=medium > > * QA upload. > * Set Debian QA Group as maintainer. (see #970369) Hi Francisco, I'd like to keep the package in the hamradio team, there is little reason to set the QA group as maintainer just because one of the uploaders is stepping down. Re: Francisco Vilmar Cardoso Ruviaro > Hi Tobias, > > thanks for creating https://salsa.debian.org/debian/wwl, > I pushed it into the repository. The package repository is https://salsa.debian.org/debian-hamradio-team/wwl, could you rebase your changes on that repo? Thanks, Christoph
