debian/0000775000000000000000000000000012173573274007203 5ustar debian/patches/0000775000000000000000000000000012173573306010626 5ustar debian/patches/series0000664000000000000000000000005512173573306012043 0ustar debian-changes-1.1.2-1 10_desktop-file.patch debian/patches/debian-changes-1.1.2-10000664000000000000000000002633111555617052014201 0ustar Description: Upstream changes introduced in version 1.1.2-1 This patch has been created by dpkg-source during the package build. Here's the last changelog entry, hopefully it gives details on why those changes were made: . hasciicam (1.1.2-1) unstable; urgency=low . * New upstream release * Added dependency to ftplib-dev . The person named in the Author field signed this changelog entry. Author: Denis Roio --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: Origin: , Bug: Bug-Debian: http://bugs.debian.org/ Bug-Ubuntu: https://launchpad.net/bugs/ Forwarded: Reviewed-By: Last-Update: --- hasciicam-1.1.2.orig/INSTALL +++ hasciicam-1.1.2/INSTALL @@ -1,13 +1,19 @@ -Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software -Foundation, Inc. +Installation Instructions +************************* - This file is free documentation; the Free Software Foundation gives +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005, +2006, 2007 Free Software Foundation, Inc. + +This file is free documentation; the Free Software Foundation gives unlimited permission to copy, distribute and modify it. Basic Installation ================== - These are generic installation instructions. +Briefly, the shell commands `./configure; make; make install' should +configure, build, and install this package. The following +more-detailed instructions are generic; see the `README' file for +instructions specific to this package. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses @@ -20,9 +26,9 @@ debugging `configure'). It can also use an optional file (typically called `config.cache' and enabled with `--cache-file=config.cache' or simply `-C') that saves -the results of its tests to speed up reconfiguring. (Caching is +the results of its tests to speed up reconfiguring. Caching is disabled by default to prevent problems with accidental use of stale -cache files.) +cache files. If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail @@ -32,20 +38,17 @@ some point `config.cache' contains resul may remove or edit it. The file `configure.ac' (or `configure.in') is used to create -`configure' by a program called `autoconf'. You only need -`configure.ac' if you want to change it or regenerate `configure' using -a newer version of `autoconf'. +`configure' by a program called `autoconf'. You need `configure.ac' if +you want to change it or regenerate `configure' using a newer version +of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type - `./configure' to configure the package for your system. If you're - using `csh' on an old version of System V, you might need to type - `sh ./configure' instead to prevent `csh' from trying to execute - `configure' itself. + `./configure' to configure the package for your system. - Running `configure' takes awhile. While running, it prints some - messages telling which features it is checking for. + Running `configure' might take a while. While running, it prints + some messages telling which features it is checking for. 2. Type `make' to compile the package. @@ -64,54 +67,55 @@ The simplest way to compile this package all sorts of other programs in order to regenerate files that came with the distribution. + 6. Often, you can also type `make uninstall' to remove the installed + files again. + Compilers and Options ===================== - Some systems require unusual options for compilation or linking that -the `configure' script does not know about. Run `./configure --help' -for details on some of the pertinent environment variables. +Some systems require unusual options for compilation or linking that the +`configure' script does not know about. Run `./configure --help' for +details on some of the pertinent environment variables. You can give `configure' initial values for configuration parameters by setting variables in the command line or in the environment. Here is an example: - ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix + ./configure CC=c99 CFLAGS=-g LIBS=-lposix *Note Defining Variables::, for more details. Compiling For Multiple Architectures ==================================== - You can compile the package for more than one kind of computer at the +You can compile the package for more than one kind of computer at the same time, by placing the object files for each architecture in their -own directory. To do this, you must use a version of `make' that -supports the `VPATH' variable, such as GNU `make'. `cd' to the +own directory. To do this, you can use GNU `make'. `cd' to the directory where you want the object files and executables to go and run the `configure' script. `configure' automatically checks for the source code in the directory that `configure' is in and in `..'. - If you have to use a `make' that does not support the `VPATH' -variable, you have to compile the package for one architecture at a -time in the source code directory. After you have installed the -package for one architecture, use `make distclean' before reconfiguring -for another architecture. + With a non-GNU `make', it is safer to compile the package for one +architecture at a time in the source code directory. After you have +installed the package for one architecture, use `make distclean' before +reconfiguring for another architecture. Installation Names ================== - By default, `make install' will install the package's files in -`/usr/local/bin', `/usr/local/man', etc. You can specify an -installation prefix other than `/usr/local' by giving `configure' the -option `--prefix=PATH'. +By default, `make install' installs the package's commands under +`/usr/local/bin', include files under `/usr/local/include', etc. You +can specify an installation prefix other than `/usr/local' by giving +`configure' the option `--prefix=PREFIX'. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you -give `configure' the option `--exec-prefix=PATH', the package will use -PATH as the prefix for installing programs and libraries. -Documentation and other data files will still use the regular prefix. +pass the option `--exec-prefix=PREFIX' to `configure', the package uses +PREFIX as the prefix for installing programs and libraries. +Documentation and other data files still use the regular prefix. In addition, if you use an unusual directory layout you can give -options like `--bindir=PATH' to specify different values for particular +options like `--bindir=DIR' to specify different values for particular kinds of files. Run `configure --help' for a list of the directories you can set and what kinds of files go in them. @@ -122,7 +126,7 @@ option `--program-prefix=PREFIX' or `--p Optional Features ================= - Some packages pay attention to `--enable-FEATURE' options to +Some packages pay attention to `--enable-FEATURE' options to `configure', where FEATURE indicates an optional part of the package. They may also pay attention to `--with-PACKAGE' options, where PACKAGE is something like `gnu-as' or `x' (for the X Window System). The @@ -137,11 +141,11 @@ you can use the `configure' options `--x Specifying the System Type ========================== - There may be some features `configure' cannot figure out -automatically, but needs to determine by the type of machine the package -will run on. Usually, assuming the package is built to be run on the -_same_ architectures, `configure' can figure that out, but if it prints -a message saying it cannot guess the machine type, give it the +There may be some features `configure' cannot figure out automatically, +but needs to determine by the type of machine the package will run on. +Usually, assuming the package is built to be run on the _same_ +architectures, `configure' can figure that out, but if it prints a +message saying it cannot guess the machine type, give it the `--build=TYPE' option. TYPE can either be a short name for the system type, such as `sun4', or a canonical name which has the form: @@ -156,7 +160,7 @@ where SYSTEM can have one of these forms need to know the machine type. If you are _building_ compiler tools for cross-compiling, you should -use the `--target=TYPE' option to select the type of system they will +use the option `--target=TYPE' to select the type of system they will produce code for. If you want to _use_ a cross compiler, that generates code for a @@ -167,9 +171,9 @@ eventually be run) with `--host=TYPE'. Sharing Defaults ================ - If you want to set default values for `configure' scripts to share, -you can create a site shell script called `config.site' that gives -default values for variables like `CC', `cache_file', and `prefix'. +If you want to set default values for `configure' scripts to share, you +can create a site shell script called `config.site' that gives default +values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. @@ -178,7 +182,7 @@ A warning: not all `configure' scripts l Defining Variables ================== - Variables not defined in a site shell script can be set in the +Variables not defined in a site shell script can be set in the environment passed to `configure'. However, some packages may run configure again during the build, and the customized values of these variables may be lost. In order to avoid this problem, you should set @@ -186,14 +190,18 @@ them in the `configure' command line, us ./configure CC=/usr/local2/bin/gcc -will cause the specified gcc to be used as the C compiler (unless it is +causes the specified `gcc' to be used as the C compiler (unless it is overridden in the site shell script). +Unfortunately, this technique does not work for `CONFIG_SHELL' due to +an Autoconf bug. Until the bug is fixed you can use this workaround: + + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash + `configure' Invocation ====================== - `configure' recognizes the following options to control how it -operates. +`configure' recognizes the following options to control how it operates. `--help' `-h' --- hasciicam-1.1.2.orig/.gbp.conf +++ hasciicam-1.1.2/.gbp.conf @@ -6,7 +6,7 @@ # the default clean command: #cleaner = debuild clean # the default branch for upstream sources: -upstream-branch = debian-orig0 +upstream-branch = upstream # the default branch for the debian patch: debian-branch = debian0 # the default tag formats used: debian/patches/10_desktop-file.patch0000664000000000000000000000070312173573344014537 0ustar Description: Don't include extension for icon. Author: Andreas Moog Bug-Ubuntu: https://bugs.launchpad.net/bugs/1198969 --- hasciicam-1.1.2.orig/share/hasciicam.desktop +++ hasciicam-1.1.2/share/hasciicam.desktop @@ -5,7 +5,7 @@ GenericName=HasciiCam Comment=(h)ascii for the masses! Exec=hasciicam %U TryExec=hasciicam -Icon=hasciicam.png +Icon=hasciicam Terminal=false Categories=AudioVideo; X-AppInstall-Package=hasciicam debian/control0000664000000000000000000000206712173573373010613 0ustar Source: hasciicam Section: graphics Priority: optional Maintainer: Ubuntu Developers XSBC-Original-Maintainer: Luca Bigliardi Uploaders: Denis Roio , Filippo Giunchedi DM-Upload-Allowed: yes Vcs-Git: git://code.dyne.org/hasciicam.git Vcs-Browser: http://code.dyne.org/?r=hasciicam Homepage: http://ascii.dyne.org/ Build-Depends: cdbs, debhelper (>> 5.0.0), libaa1-dev, ftplib-dev Standards-Version: 3.9.1 Package: hasciicam Architecture: any Depends: ${shlibs:Depends}, ${misc:Depends} Description: (h)ascii for the masses: live video as text Hasciicam makes it possible to have live ASCII video on the web. It captures video from a tv card and renders it into ascii, formatting the output into an html page with a refresh tag or in a live ASCII window or in a simple text file as well, giving the possibility to anybody that has a bttv card, a Linux box and a cheap modem line to show a live ASCII video feed that can be browsable without any need for plugin, java etc. debian/source/0000775000000000000000000000000011555541675010506 5ustar debian/source/format0000664000000000000000000000001411555541675011714 0ustar 3.0 (quilt) debian/docs0000664000000000000000000000002411555541675010055 0ustar AUTHORS NEWS README debian/rules0000775000000000000000000000023311555541675010264 0ustar #!/usr/bin/make -f include /usr/share/cdbs/1/rules/buildcore.mk include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk debian/compat0000664000000000000000000000000211555541675010404 0ustar 5 debian/menu0000664000000000000000000000021011555541675010066 0ustar ?package(hasciicam):command="hasciicam" needs="X11" \ section="Applications/Video" title="HasciiCam" hints="Live video in text" debian/changelog0000664000000000000000000000727312173573274011066 0ustar hasciicam (1.1.2-1ubuntu1) saucy; urgency=low * debian/patches/10_desktop-file.patch: Fix invalid desktop file, don't include extension for icons. (LP: #1198969) -- Andreas Moog Tue, 23 Jul 2013 23:33:04 +0200 hasciicam (1.1.2-1) unstable; urgency=low * New upstream release * Added dependency to ftplib-dev -- Denis Roio Tue, 26 Apr 2011 15:09:32 +0200 hasciicam (1.1.1-1) unstable; urgency=low * New upstream release (Closes: #621966). -- Denis Roio Fri, 04 Mar 2011 21:50:21 +0100 hasciicam (1.1-1) unstable; urgency=low * New upstream release * Package format upgraded to 3.0 (quilt) * Desktop menu entry -- Denis Roio Thu, 03 Mar 2011 15:45:53 +0100 hasciicam (1.0-1) unstable; urgency=low [ Luca Bigliardi ] * New upstream release (Closes: #278912). * Add myself as Maintainer and jaromil and filippo in 'Uploaders:'. * Switch to cdbs. * Change menu section. * Bump debian/compat to 5. * Bump Standards-Version to 3.8.0.1. [ Filippo Giunchedi ] * Change of maintainer with permission from Christian * Add DM-Upload-Allowed: yes * Add ${misc:Depends} to debian/control * Acknowledge NMU (Closes: #292231) -- Filippo Giunchedi Thu, 22 Jan 2009 23:12:40 +0100 hasciicam (0.9.1-2.1) unstable; urgency=low * Non-maintainer upload to fix RC bug * The manual page hasciicam.1 is also licensed under GFDL without invariant sections. Add a note about this in debian/copyright (Closes: #292231). Point to common-licenses GFDL copy. -- Vincent Bernat Wed, 06 Aug 2008 07:27:18 +0200 hasciicam (0.9.1-2) unstable; urgency=low * Ack to close NMU fixed bugs: - nonfree man page (Closes: #292231) - aalib transition (Closes: #320885) * Enhanced short description (Closes: #283717, #344208) -- Christian Surchi Sun, 23 Jul 2006 22:57:23 +0200 hasciicam (0.9.1-1.3) unstable; urgency=low * Non-maintainer upload. * Update hasciicam.1 from upstream, which uses GFDL with no invariant sections now. (Closes: #292231). * Bump Standards-Version to 3.7.2 (no changes required). * Bump debian/compat to 4. * Fix FSF address in debian/copyright. -- Pierre Habouzit Mon, 5 Jun 2006 13:00:53 +0200 hasciicam (0.9.1-1.2) unstable; urgency=low * NMU * Recompile to allow for the aalib transition (closes: #320885) - Change Build-Depends: to libaa1-dev -- Don Armstrong Sun, 25 Sep 2005 17:22:49 -0700 hasciicam (0.9.1-1.1) unstable; urgency=low * NMU * Added complete GFDL text to debian/copyright and correct license location to hasciicam.1 (closes: #292231) -- Paul Brossier Fri, 4 Feb 2005 18:00:41 +0000 hasciicam (0.9.1-1) unstable; urgency=low * New upstream version (Closes:#208544) * Standard Version to 3.6.1 * Now updated config.* files are in upstream package -- Christian Surchi Sat, 27 Dec 2003 15:50:19 +0100 hasciicam (0.9-3) unstable; urgency=low * Fixed conflicting definitions in hasciicam.c (Closes:#143499) * Removed "emacsisms" in debian/changelog * Standard-Version from 3.5.5 to 3.5.8 * No DH_COMPAT in debian/rules, moved to debian/compat -- Christian Surchi Mon, 2 Jun 2003 17:41:47 +0200 hasciicam (0.9-2) unstable; urgency=low * Updated config.{guess,sub} (Closes:#120758) * Fixed typo in description (Closes:#124729) -- Christian Surchi Thu, 28 Feb 2002 21:54:03 +0100 hasciicam (0.9-1) unstable; urgency=low * Initial Release (Closes:#95632) -- Christian Surchi Sun, 18 Nov 2001 19:47:14 -0500 debian/watch0000664000000000000000000000025011555541675010234 0ustar version = 3 # Package mantained by upstream developer # wishing there would be a way to watch git repos? # however our ftp is on ftp://ftp.dyne.org/hasciicam/releases debian/copyright0000664000000000000000000000100211555544077011131 0ustar This package was debianized by Christian Surchi on Sun, 18 Nov 2001 19:47:14 -0500. It was downloaded from http://ascii.dyne.org Upstream Author: Denis Roio (jaromil) Copyright: (c) 2000-2011 Jaromil Hasciicam license is GPL, which, on Debian systems, is available at: /usr/share/common-licenses/GPL. The hasciicam manpage is distributed under the terms of the GNU Free Documentation License, which, on Debian systems, is available at: /usr/share/common-licenses/GFDL