Bug#799626: RFP: beancount -- command line double-entry bookkeeping system
Nicolas Dandrimont wrote: > * Martin Michlmayr[2018-03-30 17:14:49 +0200]: > > beancount 2.0 was released a few days ago so it's time to get this > > into Debian. > > Anyone interested in packaging it? It's Python code. > I've been meaning to look into this for a while, as I've been using > beancount in an org I'm treasurer of. > I'll put this in the python-team/applications group on > salsa. Comaintainers welcome! Any luck here? I didn't see anything on salsa yet, but maybe I missed it. Don't suppose you've looked at packaging fava as well? Cheers, aj
Bug#780840: ITP: python-beanbag -- Helper module for accessing REST APIs
Package: wnpp Severity: wishlist Owner: Anthony Towns a...@erisian.com.au * Package name: python-beanbag Version : 1.9.1 Upstream Author : Anthony Towns a...@erisian.com.au * URL : https://pypi.python.org/pypi/beanbag/ * License : MIT Programming Lang: Python Description : Helper module for accessing REST APIs BeanBag is a simple module that lets you access REST APIs in an easy way. See `http://beanbag.readthedocs.org/` for more information. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150320120715.32662.25496.reportbug@navy
Bug#435058: ITP: smolt -- Fedora hardware profiler
On Sun, Jul 29, 2007 at 08:25:58AM +0200, Mike Hommey wrote: On Sat, Jul 28, 2007 at 09:28:46PM -0400, Ricky Zhou [EMAIL PROTECTED] wrote: Package: wnpp Severity: wishlist Owner: Ricky Zhou [EMAIL PROTECTED] * Package name: smolt Version : 0.9.8.3 Upstream Author : Mike McGrath [EMAIL PROTECTED] * URL : https://hosted.fedoraproject.org/projects/smolt/ * License : GPL Programming Lang: Python Description : Fedora hardware profiler The Fedora hardware profiler is a server-client system that does a hardware scan against a machine and sends the results to a public Fedora Project turbogears server. The sends are anonymous and should not contain any private information other than the physical hardware information and basic OS info. What is the added value for Debian users of sending these informations *to Fedora* ? Modifying the package so it sends the data to a Debian server running the same/similar software to Fedora's sounds reasonable though. Not completely sure that there's much benefit to maintaining separate servers for Debian data and Fedora data -- but *reporting* the data separate would probably be a good thing if the proportion of Fedora users with smolt is significantly different to the proportion of Debian users with smolt. (That's because making a mistake on that score would be both easy if the data were combined, and lead to wrong comparisons between total Debian and Fedora users, to the detriment of whoever has the lower proportion of users running smolt, which would presumably be Debian) Integrating it with pop-con (or vice-versa) would be interesting. Cheers, aj signature.asc Description: Digital signature
Bug#327081: ITP: rpmstrap -- bootstrap a basic RPM-based system
On Wed, Sep 14, 2005 at 06:00:07PM +, Sam Hart wrote: Ok, I went back to the source of the problem. Back in Feb 2005 there was some development done in IRC between myself and another contributor. [...] I have since confronted him on this and he admits that the code was from an ancient version of debootstrap (his words) [...] So good, we're agreed that debootstrap code has made it's way into rpmstrap. The patch accounted for 23 lines of code and essentially stubbed out Well, I count some 70 odd lines that're pretty much an exact match to debootstrap from earlier this year, so I suspect that isn't all of it. Not all of this code remained in current rpmstrap svn, however that code which did remain has now been replaced. So, if your strategy is really going to be I shall do whatever it takes to avoid obeying debootstrap's license you'll need to keep looking to work out what the deal is with the rest of the code copied from debootstrap, and probably go to some effort to make sure that you've got a clean chain of development. I've no idea why you'd want to do that, when complying with debootstrap's license and being able to copy whatever you like is just a matter of including the copyright notice, but hey. Finally, even though my original design goal was to clone the interface to debootstrap to provide familiarity to rpmstrap's users, and even though saying that cloning such an interface is a bad thing What are you talking about? There's nothing bad about cloning things -- that's the whole _POINT_ of licensing things freely. would make projects such as GNU Nano invalid, I have gone ahead and changed /some/ of the interface simply because I don't have the time to squabble over such childish things. Well, you're spending a lot of time squabbling instead of just adding a copyright notice. If there is any further code found in rpmstrap or any other project I may be working on, it seems to me that a mature way to deal with it would be to contact me directly rather than attacking me in public. It seems odd that you're complaining that I mailed in public half a day after I sent you mail directly. Less odd that you're happy to be in -devel when you think you're right, and change your mind when you find you're wrong, but hey. Personally, I would've thought it'd be polite to say hey, we're creating this rpmstrap tool that's kinda like your debootstrap thing but for rpms, check it out! too. I am actually a very reasonable man, and if any mistake is found it will not have been out of malice. Colour me unimpressed. Color, dude. Make the whine your own. Cheers, aj signature.asc Description: Digital signature
Bug#327081: ITP: rpmstrap -- bootstrap a basic RPM-based system
On Mon, Sep 12, 2005 at 12:12:31PM -0500, Sam Hart wrote: To be completely honest with you, I've not looked much at the debootstrap code before now. I have tried to mimic debootstrap's interface without a doubt, but have only done so by *using* debootstrap rather than snooping in its code. It's not snooping to look at the code of a free software project. For what it's worth, rpmstrap as it is today is actually based on a tool developed in house at Progeny. This tool could only bootstrap Fedora Core 2 at a specific revision. Looking at that code now and comparing it to what I see inside of debootstrap, the only real similarities I see are that they both have functions common to /many/ other shell scripts (usage(), die(), warn(), trace()). Looking at rpmstrap-0.1, we see the following code for handling options: ] if [ $# != 0 ] ; then ] while true ; do ] case $1 in ] --help) ] usage ] exit 0 ] ;; ] ... ] esac ] done ] else ] usage_error You must specify a suite and a target. ] fi debootstrap uses the exact same code, except to say usage_err 1 NEEDSUITETARGET instead of usage_error and with two-space indentation. The usual way to parse arguments is with a `for a in $@' loop, or using getopt -- the above parsing algorithm has the bug that options can only appear at the beginning of the command line, eg. rpmstrap-0.1 uses the variable $JUST_PRINT_RPMS to track whether to dump the list of rpms to stdout or not; debootstrap uses $JUST_PRINT_DEBS. Compare the usage() functions: ] usage() ] { ] echo Usage: $PROGNAME [OPTION]... suite target [mirror] ] echo Bootstrap RPM-based systems. ] echo ] cat EOF ] --arch set the target architecture (use if no uname) ][ --arch x86_64 ] ] ] --download-onlydownload packages, but don't perform installation ] usage() ] { ] echo Usage: ${0##*/} [OPTION]... suite target [mirror [script]] ] echo Bootstrap Debian base system. ] echo ] cat EOF ] --arch set the target architecture (use if no dpkg) ][ --arch powerpc ] ] --download-onlydownload packages, but don't perform installation The code that handles the You must specify a suite and a target. error messages looks pretty familiar too, but I've changed it a few times and I didn't find an exact match at first glance. I will have to check the legacy on this tool used internally at Progeny to ensure nothing came from debootstrap, As opposed to use a license that means it could potentially be incorporated into debootstrap or give credit where it seems like it's due, considering 1) Identical command-line options: 2) Placing of suite scripts inside of a scripts/* directory: 3) Making common functions available to suite scripts: that you did seem to copy quite a bit from debootstrap anyway. For instance, debootstrap's copyright says: ] It was written from scratch for Debian by Anthony Towns [EMAIL PROTECTED] ] based loosely on the code for constructing base tarballs as part of the ] boot-floppies package. and I think you'll find, if you care, that debootstrap shares a lot less with the boot-floppies code than rpmstrap does with it. In comparison: $ find rpmstrap-0.{1,2,3,4,5} -type f | xargs grep debootstrap | wc -l 0 Even if you hadn't copied any code whatsoever, isn't a little acknowledgement appropriate? It's not as though debootstrap's license is particularly onerous. Cheers, aj signature.asc Description: Digital signature
Bug#327081: ITP: rpmstrap -- bootstrap a basic RPM-based system
On Tue, Sep 13, 2005 at 04:41:26AM +1000, Anthony Towns wrote: Looking at rpmstrap-0.1, we see the following code for handling options: Also copied was debootstrap's --arch and --include handling; even duplicating the bug where you have to say --arch i386 (with a space) and --include=foo,bar (with an =). There even seems to have been a bug introduced during the copying; debootstrap has: ] --include*) ] additional=$(echo $1 | cut -f2 -d=|tr , ) ] shift 1 ] ;; ] --exclude*) ] exclude=$(echo $1 | cut -f2 -d=|tr , ) ] shift 1 ] ;; Someone involved in rpmstrap-0.1 evidently decided using lowercase variables in some places was unacceptably inconsistent and changed that to: ] --include*) ] ADDITIONAL=$(echo $1 | cut -f2 -d=|tr , ) ] shift 1 ] ;; ] --exclude*) ] ADDITIONAL=$(echo $1 | cut -f2 -d=|tr , ) ] shift 1 ] ;; making --exclude work the same as --include, up until rpmstrap-0.4, where they were changed to INCLUDES and EXCLUDES instead. rpmstrap-0.1 set an UNPACK_TARBALL variable based on an --unpack-tarball using the same code as debootstrap; but UNPACK_TARBALL is never actually used; support for it is only implemented in rpmstrap-0.2. Cheers, aj signature.asc Description: Digital signature
Bug#327081: ITP: rpmstrap -- bootstrap a basic RPM-based system
On Wed, Sep 07, 2005 at 02:08:04PM +0200, Piotr Roszatycki wrote: * Package name: rpmstrap Version : 0.5 * URL : http://hackers.progeny.com/~sam/rpmstrap/ * License : GPL Description : bootstrap a basic RPM-based system rpmstrap is a tool for bootstrapping a basic RPM-based system. It is inspired by debootstrap, and allows you to build chroots and basic systems from RPM sources. Looking at the source it seems more based on than inspired by, particular to rpmstrap itself, though the functions and scripts/* files sure seem more derivative than just coincidently similar. If so, it's in violation of debootstrap's license (by not including debootstrap's copyright text), and it seems fairly rude to relicense it from debootstrap's BSD-ish license to GPLv2+, not to mention expunging my name and copyright notice from the source, and for that matter all references to debootstrap. Removing the copyright's a license violation, and presumably renders the program undistributable and unpackagable, afaics. At least Bastian Blank's cdebootstrap was written from scratch to justify its different license and lack of recognition. Colour me unimpressed. Cheers, aj signature.asc Description: Digital signature
Bug#236418: ITP: debootstrap-buildd -- Scripts to create chroots for building packages
On Fri, Mar 05, 2004 at 10:41:03PM -0800, Daniel Schepler wrote: * Package name: debootstrap-buildd Version : 0.1 Upstream Author : Daniel Schepler [EMAIL PROTECTED] * URL or Web page : * License : GPL Description : Scripts to create chroots for building packages This package contains custom debootstrap scripts which create chroots with (only) the build-essential packages installed. After creation, these chroots can be used for testing package builds (for example for correcness of Build-Depends), or for compiling backport versions of packages. . Instructions are included for using these scripts either directly or in conjunction with pbuilder. Why can't this be integrated into debootstrap proper? Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. Linux.conf.au 2004 -- Because we could. http://conf.linux.org.au/ -- Jan 12-17, 2004 signature.asc Description: Digital signature
Bug#236418: ITP: debootstrap-buildd -- Scripts to create chroots for building packages
On Fri, Mar 05, 2004 at 11:41:46PM -0800, Daniel Schepler wrote: Why can't this be integrated into debootstrap proper? It would also be nice to add a --buildd option to debootstrap to switch to using the buildd-* scripts by default. Hrm, I'd be more inclined towards a --variant buildd argument, that switches to using ${SCRIPT}.buildd instead, or so, I think. An API that's not too specific would probably be sensible given this doesn't need any _really_ close tying to debootstrap internals. Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. Linux.conf.au 2004 -- Because we could. http://conf.linux.org.au/ -- Jan 12-17, 2004
Bug#236418: ITP: debootstrap-buildd -- Scripts to create chroots for building packages
On Sat, Mar 06, 2004 at 03:52:35AM -0800, Daniel Schepler wrote: +if [ $VARIANT = .base ]; then + VARIANT= +fi Err, eww. I really dislike that. Rest seems fine at first glance. Please talk to Ryan about it, test it a bit, and then it should be time to do an NMU. You might like to retitle and reassign the bug to debootstrap, too. +SCRIPT=$DEBOOTSTRAP_DIR/scripts/$1$VARIANT I'd've done if [ $VARIANT != ]; then SCRIPT=${SCRIPT}.${VARIANT} fi personally. *shrug* +.IP \fB--variant=buildd\fP +Name of the bootstrap script variant to use. Currently, the only variants +supported are base (the default), and buildd, which installs the +build-essential packages into A variant isn't the default by def'n, I'd've thought. Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. Linux.conf.au 2004 -- Because we could. http://conf.linux.org.au/ -- Jan 12-17, 2004 signature.asc Description: Digital signature
Bug#190564: O: ipautofw
Package: wnpp Severity: normal Description: Utility to automatically add masquerade entries This program allows linux masquerading available in 2.0 series kernels to work with programs such as RealAudio which don't send out a packet on all ports they wish to receive on. . For 2.2 series kernels see ipmasqadm instead. Orphaned; I don't think this package is even useful anymore.
Bug#187407: ITP: qemu -- Userspace x86 (ia32) Linux emulator.
On Thu, Apr 03, 2003 at 08:45:07AM +0200, Paul Russell wrote: * Package name: qemu Version : 0.14 Upstream Author : Fabrice Bellard [EMAIL PROTECTED] * URL : http://www.some.org/ http://fabrice.bellard.free.fr/qemu/ seems to be a better URL than the So Others Might Eat program for Washington, D.C. Sounds cool. Do you have any idea how users will install i386 programs (like wine) on their powerpc boxes? (Presumably it's a similar issue to running i386 packages on ia64, which doesn't even need a processor emulator) Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. ``Dear Anthony Towns: [...] Congratulations -- you are now certified as a Red Hat Certified Engineer!''
Bug#187449: O: zope-worldpilot -- web based organizer and messenger built on zope
Package: wnpp Severity: normal X-Debbugs-Cc: Behan Webster [EMAIL PROTECTED] From Bug#151925: ] Date: Mon, 12 Aug 2002 07:42:17 -0400 ] From: Behan Webster [EMAIL PROTECTED] ] ] The problem is that I don't use worldpilot anymore. As a result it ] doesn't really get any of my limited time. I've been meaning to orphan ] it for a while now. Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. ``Dear Anthony Towns: [...] Congratulations -- you are now certified as a Red Hat Certified Engineer!''
Bug#184670: Is epic package non-free?
On Fri, Mar 14, 2003 at 10:15:23AM -0300, Gustavo Franco wrote: I was checking the epic package, because i've ITA on it now.After the check, i've some doubts about the license: http://lwn.net/1998/0611/ircii.html Michael Sandrof, Troy Rollo, and Matthew Green are putting the ircII code under a BSD-like license (without the advertising clause), retroactive to all versions of ircII, past and present. This action is to remove any doubt as to whether ircII is Open Source. Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ I don't speak for anyone save myself. GPG signed mail preferred. ``Dear Anthony Towns: [...] Congratulations -- you are now certified as a Red Hat Certified Engineer!'' pgpY2TT5KcjAi.pgp Description: PGP signature
Bug#134658: ITP: lsb -- Linux Standard Base 1.1 core support package
On Mon, Feb 18, 2002 at 06:50:01PM -0600, Chris Lawrence wrote: - LSB 1.1 specifies definitions for run levels 2-5 that correspond with most Red Hat-like distributions. Debian does not specify run levels 3-5, and RL 2 can theoretically encompass any of LSB 2-5. (LSB probably should implement init dependencies for facilities expected in run levels, rather than using run levels directly.) This was discussed on one of the LSB lists (-spec? -discuss? both?) back when the 1.0 spec came out; the conclusion was basically that Debian should just translate those runlevels into the Debian equivalents. That is, just because a script specifies runlevel 5 but not 2, doesn't mean it shouldn't be brought up in runlevel 3 on Debian if that's what's appropriate. [...] however, my gut feeling is that any LSB RL from 2-5 should be treated as 2-5 inclusive on Debian until Debian conforms (unlikely for woody) or LSB is amended to get rid of this silliness. There are also systems out there that don't use runlevels, or that have user defined runlevels that aren't remotely related to the numbers Red Hat uses, which the LSB ought to support. There may be other deviations from the spec; they are bugs and should be reported as such. (The aforementioned deviations are bugs, but probably wontfix for woody, or are bugs in the spec.) You should also mention that the uid for bin isn't 1 as the LSB specifies. Cheers, aj -- Anthony Towns [EMAIL PROTECTED] http://azure.humbug.org.au/~aj/ We came. We Saw. We Conferenced. http://linux.conf.au/ ``Debian: giving you the power to shoot yourself in each toe individually.'' -- with kudos to Greg Lehey
Bug#119258: O: ale-clone, ale-clone-cogliati
Package: wnpp Version: N/A; reported 2001-11-12 Severity: normal This has been renamed upstream to freecraft with a number of improvements. Someone should package that, and remove these packages from the archive. -- System Information Debian Release: testing/unstable Architecture: powerpc Kernel: Linux cyan 2.4.8-pre7-ben0 #2 SMP Sun Aug 12 23:24:14 EST 2001 ppc Locale: LANG=C, LC_CTYPE=C
Bug#94213: O: distributed-net-pproxy
Package: wnpp Severity: normal distributed-net-pproxy is the personal proxy for distributed.net clients. It's non-free and doesn't come with source.