Re: Firmware poll
On Tue, 29 Aug 2006 05:37:23 -0500, Ron Johnson wrote: > [ x ] Choice 5: Ship *BLOBs* (does *not* mean closed-source > drivers like nvidia) that can be legally > redistributed, do not ship BLOBs that can > not be legally redistributed. > > Yes, I know BLOBs are, well, binary, but they do *not* run on the > system's CPU. They run on "little" CPUs on PCI cards, in USB > devices, etc, etc, etc. Morally, it is the same as a FSF/GNU > devotee running a machine that has ROMs and Flash EEPROMs on the > mobo, on high-performance NICs, etc. I disagree, or I am not understanding the difference between the two. FSF/GNU devotees would much prefer to use a free BIOS[0] or EEPROM code if they had a choice imho. [0] http://www.fsf.org/campaigns/free-bios.html -- Chris Lamb, Cambs, UK GPG: 0x634F9A20 Q. Why is top posting bad? A. Because it breaks the logical sequence of discussion signature.asc Description: PGP signature
Re: Media players in Debian (was: new mplayer)
On Fri, 22 Sep 2006 13:03:44 +0200, Steinar H. Gunderson wrote: > I've heard these claims (“player X should be more than good enough, > what do you need mplayer for these days?”) for at least the last five > years Not, "This cannot be played on record^Hmedia player X" ? Tortoise -- Chris Lamb, Cambs, UK WWW: http://chris-lamb.co.uk Q. Why is top posting bad? GPG: 0x634F9A20 A. Because it breaks the logical sequence of discussion signature.asc Description: PGP signature
Bug#536732: ITP: libfiu -- userspace fault injection framework
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: libfiu Version : 0.11 Upstream Author : Alberto Bertogli * URL : http://blitiri.com.ar/p/libfiu/ * License : Buena Onda License Agreement (BOLA), essentially "public domain". Same as darcsweb. Programming Lang: C / Python Description : userspace fault injection framework libfiu is a C library for userspace fault injection via LD_PRELOAD. It provides functions to mark "points of failure" inside your code and functionality to enable/disable the failure of those points when executing it. It also comes with some tools that can be used to perform fault injection in the POSIX API without having to modify the application's source code, which can help to test failure handling code in an easy and reproducible way. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Debian, universal operating system?
Javier Fernandez-Sanguino wrote: > > First of all, let's make it clear, Debian is not THE universal > > operating system. I mean it is definitely not the one and only OS. > > As said in the talk @ Debconf: this is just a slogan. Agreed. IMHO, it is one of those phrases (along with "Our priority is our users") that actually means extremely little in practice, except for generating lots of hot air with nobody agreeing. I don't see what we will gain from further discussion in this thread. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Virt-what support for VirtualBox?
Mark Allums wrote: > That looks like Virt-what does not detect VirtualBox. Is it likely to > be added in the future? Your question is better redirected at the Fedora-virt mailing list; they develop this software, not us: http://www.redhat.com/mailman/listinfo/fedora-virt Alternatively, you could try the #virt channel on OFTC. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: How to check why a package is in contrib
Cyril Brulebois wrote: > I would guess that one might expect a reason in changelog, first upload > to contrib, and copyright file. Also check http://nonfree.alioth.debian.org/ Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: DEP-5: an example parser, choice of syntax for Files:
Benjamin Drung wrote: > You can get rid of those './' by replacing . with *: > > find * -path 'debian/*' That's not entirely equivalent; shells do not expand globs to include files beginning with "." by default. Jon, I would suggest using os.walk and fnmatch - it will cover this issue and will remove the requirement to execute a subprocess. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Lintian based autorejects
Stefano Zacchiroli wrote: > Can you please consider changing the above naming? FWIW the actual reject messages are very clear and do not use these terms (which I've changed in Git anyway, pending merge). Thanks. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Mozilla renames: is Debian the only one?
Pierre THIERRY wrote: > If not, which ones? + http://www.gnewsense.org/ ? -- Chris Lamb, Cambridgeshire, UK GPG: 0x634F9A20 signature.asc Description: PGP signature
Re: [EMAIL PROTECTED] Package
Charles Plessy wrote: > as said in another mail, [EMAIL PROTECTED] is definitely non-free. Hovever, > if Debian would become an "authorized distributor", the licence would be > suitable for non-free. What about Debian derivatives? /Lamby -- Chris Lamb, Leamington Spa, UK GPG: 0x634F9A20 signature.asc Description: PGP signature
Bug#495148: ITP: reviewboard -- Web-based code review tool
Package: wnpp Severity: wishlist Owner: Chris Lamb <[EMAIL PROTECTED]> * Package name: reviewboard Version : 1.0~svn Upstream Authors: Review Board Developers <[EMAIL PROTECTED]> * URL : http://www.review-board.org/ * License : MIT Programming Lang: Python Description : Web-based code review tool Review Board is a web-based tool designed to help projects and companies keep track of pending code changes and make code reviews much less painful and time-consuming. It currently has support to SVN, CVS, Perforce, Git, Bazaar, and Mercurial repositories. Regards, -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 signature.asc Description: PGP signature
Re: Hardware compatibility test: draft proposal
Wouter Verhelst wrote: > As I mentioned in my blog[1], I kindof like the suggestion that Bdale > came up with during Debconf that we write a hardware compatibility test > of sorts that hardware vendors could run on their own hardware I think this is a great idea, and I generally agree with your decisions and assumptions. > - Scripts should not just test for availability of hardware. Instead, > they should test the actual functionality; e.g., tests for a network > interface should be done by trying to DHCP off that interface, X.org > drivers should try to start X and ask for input using a graphical > dialog, and tests for a hard disk should be done by trying to read > some data from the disk. I think this the most important paragraph of all. What I think is missing is some really concrete info on just how various hardware items would be tested. For example, in the case of ethernet adaptors, I feel that simply successfully DHCP-ing on an interface is really not an acceptable test. As an example, Etch's kernel contains various modules (such as sky2) that "kinda" work on today's hardware - whilst the driver would probably pass a DHCP test, the actual performance or reliability of the device is completely inadequate. Wireless devices would pose an even more difficult problem, as support for the various encryption modes that the device supports tend to be developed at different times, etc. (I'm fairly confident these comments have parallels with other hardware categories, I just give networking examples that most readers might be able to relate to) Whilst I am aware that a testsuite could never be 100% conclusive (and I'm sure you are aware too) my underlying enquiry here is trying to work out what level of confidence you are aiming for. (Hm, this didn't mean to be so negative..) > - A Debian Live image will be provided that will install the > 'debian-hct' package plus all packages that say 'Provides: > hardware-compatibility-test' plus all their dependencies. This will be > the hardware compatibility test that we can give to vendors. Please let me know if you would like any help with Live image foo. Regards, -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 signature.asc Description: PGP signature
Bug#500391: ITP: python-django-debug-toolbar -- Embedded debugging toolbar for Django projects
Package: wnpp Severity: wishlist Owner: Chris Lamb <[EMAIL PROTECTED]> * Package name: python-django-debug-toolbar Upstream Author : Rob Hudson <[EMAIL PROTECTED]> * URL : http://github.com/robhudson/django-debug-toolbar * License : BSD Programming Lang: Python Description : Embedded debugging toolbar for Django projects The Django Debug Toolbar is a plug-in Django application that displays a set of panels which conveys information about the current request at the top of the rendered page. It can show: * Total time taken to process request * Request variables, including GET, POST, cookie, and session information. * All SQL queries performed during response creation and processing, including timing and 'EXPLAIN' output for each query in conjunction with the total time spent performing SQL queries. If python-pygments is installed, the SQL syntax is highlighted. * Current Django version * HTTP headers * Total requests, time, hits and misses of the cache. * Which templates were rendered the context provided to each template. Regards, -- ,''`. : :' : Chris Lamb `. `'` [EMAIL PROTECTED] `- signature.asc Description: PGP signature
Re: Sidux?
Lucas Nussbaum wrote: > Are there opportunities to collaborate with them on some things? There already have been; Sidux's liveCD used to be built by the Debian Live CD creation tools - they contributed patches, ideas and support to live-helper until they reimplemented it in Python. Can't remember what they did with live-initramfs though. Regards, -- ,''`. : :' : Chris Lamb `. `'` [EMAIL PROTECTED] `- signature.asc Description: PGP signature
Re: Bug Sprint - Oct 25 to Oct 30 - Register and eat cookies
Josselin Mouette wrote: > we are currently very close to release lenny which is most likely going > to be absolutely awesome. > > However, there are currently around 100 RC bugs remaining Apologies if this has already been brought up. Using the number RC bugs that a present in lenny and sid is--in my opinion--a rather misleading metric of bugs that require attention for lenny. This isn't just semantics; one obvious set of bugs that are missed here are bugs that are only present in the upstream version correspending to the version in lenny. We clearly care about these bugs. Another example is that a fix that was uploaded to unstable and unblocked for migration to lenny but it subsequently FTBFS on some arch. Here, even if an explicit FTBFS bug is filed, it will only affects the version in sid and will thus does not appear when applying the bydist=both predicate. I've found bugs in this category require considerably more work than others, not only because they are typically indicative of a more serious problem, but also because they require some syncing with -release and the use of non-mainstream architectures. Regards, -- ,''`. : :' : Chris Lamb `. `'` [EMAIL PROTECTED] `- signature.asc Description: PGP signature
Bug#504237: ITP: haskell-diff -- Haskell O(ND) diff algorithm library
Package: wnpp
Severity: wishlist
Owner: Chris Lamb <[EMAIL PROTECTED]>
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: haskell-diff
Version : 0.1.2
Upstream Author : Sterling Clover <[EMAIL PROTECTED]>
* URL: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/Diff
* License : BSD3
Programming Lang: Haskell
Description : Haskell O(ND) diff algorithm library
This is a Haskell library providing an implementation of the O(ND) diff
algorithm described in "An O(ND) Difference Algorithm and Its Variations"
(1986) by Eugene W. Myers. It is O(mn) in space. Whilst the algorithm is
the same one used by standared Unix diff, the assumption is that users of
this library will want to diff over interesting things or perform
interesting tasks with the results.
This library is being packaged as a (new) dependency of the 'geordi' package.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [EMAIL PROTECTED]
`-
signature.asc
Description: PGP signature
Bug#504799: ITP: fabric -- Simple Pythonic remote deployment tool
Package: wnpp
Severity: wishlist
Owner: Chris Lamb <[EMAIL PROTECTED]>
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: fabric
Version : 0.0.9
Upstream Author : Christian Vest Hansen <[EMAIL PROTECTED]>
* URL : http://www.nongnu.org/fab/
* License : GPL-2
Programming Lang: Python
Description : Simple Pythonic remote deployment tool
Fabric is designed to upload files and run shell commands on a number of
servers in parallel or serially. These commands are grouped in tasks
(which are regular Python functions) and specified in a 'fabfile.'
It is similar to Capistrano, except it's implemented in Python and
doesn't expect you to be deploying Rails applications.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [EMAIL PROTECTED]
`-
signature.asc
Description: PGP signature
Bug#506310: ITP: python-django-dmigrations -- Simple migrations tool for Django
Package: wnpp
Severity: wishlist
Owner: Chris Lamb <[EMAIL PROTECTED]>
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: python-django-dmigrations
Version : 0.3.1
Upstream Authors: Simon Willison and Tomasz Wegrzanowski
* URL : http://code.google.com/p/dmigrations/
* License : BSD
Programming Lang: Python
Description : Simple migrations tool for Django
dmigrations offers a simple but flexible way of managing changes to the
database in your Django projects. It is a replacement for Django's
built in syncdb command.
With dmigrations, every change to your database (including the creation
of your initial tables) is bundled up in a migration. Migrations are
Python files that live in a migrations directory and can be applied and
un-applied (reverted) in sequence.
dmigrations aims to be compatible with workflows involving distributed
revision control.
This package will eventually obsolete the python-django-evolution
package in experimental).
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [EMAIL PROTECTED]
`-
signature.asc
Description: PGP signature
Bug#508035: ITP: python-django-treebeard -- Efficient implementations of tree data structures for Django
Package: wnpp Severity: wishlist Owner: Chris Lamb <[EMAIL PROTECTED]> X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-django-treebeard Version : 1.1 Upstream Author : Gustavo Picon <[EMAIL PROTECTED]> * URL : http://code.google.com/p/django-treebeard * License : Apache License 2.0 Programming Lang: Python Description : Efficient implementations of tree data structures for Django Django Treebeard is a library that implements efficient data structures for storing hierachical data in a database using the Django web development framework. It currently includes 3 different tree implementations: adjacency list, materialized path and nested sets. Each one has it's own strength and weaknesses but share the same API, so it’s easy to switch between them. Regards, -- ,''`. : :' : Chris Lamb `. `'` [EMAIL PROTECTED] `- signature.asc Description: PGP signature
Bug#511111: ITP: bustle -- D-Bus activity visualiser
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: bustle Version : 0.1 Upstream Author : Will Thompson * URL : http://resiak.livejournal.com/59590.html / http://people.collabora.co.uk/~wjt/bustle/releases/ * License : LGPL-2.1+ and GPL-2+ Programming Lang: Haskell/C Description : D-Bus activity visualiser Bustle is a tool to chart and provide timing information of D-Bus calls for profiling and debugging purposes. It is intended to replace reading the cryptic output of dbus-monitor. Calls are displayed using Message Sequence Charts, a succinct way of representing entities and interactions over time. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Bug#511543: ITP: python-django-lint -- Static analysis tool for Django projects and applications
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-django-lint Version : 0.1 Upstream Author : Chris Lamb http://chris-lamb.co.uk/projects/django-lint * License : GPL-3+ Programming Lang: Python Description : Static analysis tool for Django projects and applications Django Lint is a tool that statically analyses projects and applications that use the Django web development framework. It checks and reports on common programming errors and bad code smells including: * Nullable "CharField" fields * Usage of brittle Django features such as "auto_now_add" * Unspecified recommended options in settings.py, such as an empty 'ADMINS' * (plus many more) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Bug#511548: ITP: simile-timeline -- JavaScript library for web-based interactive timelines
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: simile-timeline (libjs-simile-timeline) Version : 2.2.0 Upstream Author : Chris Lamb http://simile.mit.edu/timeline/ * License : BSD Programming Lang: JavaScript Description : JavaScript library for web-based interactive timelines Timeline is a DHTML-based AJAX-based widget for visualizing time-based events. It uses the "slippy page" concept in a similar way to Google Maps, allowing the user to pan the timeline by dragging the page horizontally. Each timeline can consist of multiple "bands", each with a configurable scale, which can provide useful context when displaying a large number of items. Created timelines can be populated directly via XML or JSON. (Debian users will recognise this library from http://timeline.debian.net/. I plan to maintain this library within pkg-javascript.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Bug#438753: ITP: md5deep -- Recursing file hash calculator
Giovanni Mascellani wrote: > This utility is similar to the famous md5sum, but has the ability to > recurse into subdirectories when calculating hashes for many files. Could this not go into moreutils? It seems a shame to create a new package for something that could be trivially implemented in one line of shell. /Lamby -- Chris Lamb, Cambridgeshire, UKGPG: 0x634F9A20 signature.asc Description: PGP signature
Re: etch ftp-mirror broken?
Henning Glawe wrote: > seems like something went wrong during the etch 4.0r1 update on the ftp > mirrors: the old etch kernel packages got removed from the archive, but are > still referenced in the package lists. This has already been reported as #455089. Regards, /Lamby [0] http://bugs.debian.org/455089 -- Chris Lamb, UK [EMAIL PROTECTED] GPG: 0x634F9A20 signature.asc Description: PGP signature
Bug#577107: ITP: gunicorn -- Event-based HTTP/WSGI server
Package: wnpp
Severity: wishlist
Owner: Chris Lamb
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: gunicorn
Upstream Author : Benoit Chesneau
* URL : http://www.gunicorn.org/
* License : MIT
Programming Lang: Python
Description : Event-based HTTP/WSGI server
Green Unicorn (gunicorn) is an HTTP/WSGI server designed to serve fast
clients or sleepy applications. That is to say; behind a buffering
front-end server such as nginx or lighttpd.
.
* Optional support for Eventlet and Gevent to provide asynchronous
long-polling ("Comet") connections.
* Process management: Gunicorn reaps and restarts workers that die.
* Easy integration with Django and Paster compatible applications
(Pylons, TurboGears 2,etc
* Load balancing via pre-fork and a shared socket
* Graceful worker process restarts
* Upgrading without losing connections
* Decode chunked transfers on-the-fly, allowing upload progress
notifications or stream-based protocols over HTTP
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
Orphaning some packages
-devel,
I have less time for packaging work these days, especially for packages
I have no personal or work connection to. Therefore, I am orphaning a
bunch of packages.
Even though I have some time available at Debconf, I'm orphaning these
now so that the adopter can make use the Debconf time instead going
forward.
On each of the RFAs I have added notes where I thought it made sense. If
you have any specific questions, please address to the corresponding RFA
bug.
#590772 libgc -- conservative garbage collector for C
#590773 reinteract -- Worksheet-based graphical Python shell
#590774 robocode -- Java programming game based on battle tanks
#590775 reviewboard -- Web-based code review tool
#590776 python-django-djblets -- Re-usable components for Django
projects
#590777 pyke -- Prolog-inspired Python logic programming
toolkit
#590778 trac-spamfilter -- Spam-prevention plugin for Trac
#590779 udptunnel -- Tunnel UDP packets over a TCP connection
#590780 relational -- Educational tool for relational algebra
#590781 decoratortools -- version-agnostic decorators support for
Python
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
Bug#518700: ITP: redis -- Persistent key-value database with network interface
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: redis Version : 1.0~beta5 Upstream Author : Salvatore Sanfilippo * URL : http://code.google.com/p/redis/ * License : GPL-2, MIT and 2-clause BSD Programming Lang: C (plus Python, Ruby and Erlang) Description : Persistent key-value database with network interface Redis is a key-value database in a similar vein to memcache but the dataset is non-volatile. Redis additionally provides native support for atomically manipulating and querying data structures such as lists and sets. The dataset is stored entirely in memory and periodically flushed to disk. Python, Ruby and Erlang bindings will also be packaged from the same source package. This package will be uploaded to experimental until 1.0. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Bug#519290: ITP: libphash -- Perceptual hashing library
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: libphash Version : 0.4 Upstream Author : Evan Klinger David Starkweather * URL : http://www.phash.org/ * License : GPL-3 Programming Lang: C++ Description : Perceptual hashing library Unlike cryptographic hash functions which rely on an avalanche effect of changes in input leading to drastic changes in the output, perceptual hashes are "close" to one another if the inputs are visually or auditorily similar. Perceptual hashes have applications in searching, identifying potential copyright infringement, locating duplicates, etc. - since a fingerprint of a file is usually less than 1% of the original media file's size, the fingerprint can be stored in a database and used for semantic searching, such as finding all images that look like another. pHash implements several perceptual hashing algorithms and provides a C++ API to use those functions in your own programs. (There's a demo on http://phash.org/demo/ if readers of this bug report are interested). Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Bug#521349: ITP: python-django-extensions -- Useful extensions for Django projects
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: python-django-extensions Upstream Author : Michael Trier * URL : http://code.google.com/p/django-command-extensions/ * License : MIT Programming Lang: Python Description : Useful extensions for Django projects This is a collection of useful third-party tools for projects that use the Django web development framework. It provides the management commands: * runserver_plus - a "runserver" that uses the interactive Werkzeug debugger * runprofileserver - starts runserver with profiling tools enabled * shell_plus - similar to the built-in "shell" but autoloads all models * graph_models - creates a GraphViz dot file of your model arrangement * describe_form - generate template form definitions for a model * export_emails - export the addresses of your users in many formats * print_user_for_session - print the user information from a session key * create_jobs/runjob/runjobs - manage scheduled maintenance jobs * (plus many more) python-django-extensions also includes a number of custom fields and abstract models, including ones that manage created and updated times automatically. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Bug#521435: ITP: reinteract -- Worksheet-based graphical Python shell
Package: wnpp
Severity: wishlist
Owner: Chris Lamb
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: reinteract
Upstream Author : Owen Taylor
* URL : http://www.reinteract.org/
* License : BSD
Programming Lang: Python (GTK, Matplotlib)
Description : Worksheet-based graphical Python shell
Reinteract is a tool for interactive experimentation with Python
oriented around "worksheets" containing Python code combined with the
results of that code, formatted as text or graphical plots. Unlike a
traditional shell, you can go back and edit previously entered
statements, and the results will update.
Amongst other things, Reinteract is suitable for experimentation with
the Python language and for data analysis using NumPy and SciPy.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
Bug#524232: ITP: swordfish - High level key-value database with a RESTful HTTP interface
Package: wnpp
Severity: wishlist
Owner: Chris Lamb
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: swordfish
Version : 0.1
Upstream Author : Chris Lamb
* URL : http://chris-lamb.co.uk/projects/swordfish
* License : GPL-3+ (server), BSD (client)
Programming Lang: C / Python
Description : High level key-value database with a RESTful HTTP
interface
Swordfish is a persistent database which uses JavaScript Object Notation
(JSON) over HTTP. It was designed to complement a relational database
used in modern web applications by providing a means to denormalise
(and thus avoid) computationally expensive JOIN operations.
To this end, Swordfish's primary data structure is a dictionary with
ordered keys and provides functionality for atomically manipulating and
querying these structures, including set-based operations such as
intersection and difference.
Swordfish also provides a QuerySet-like API for projects using the
Django web development framework.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
Bug#527951: ITP: haskell-editline -- Haskell bindings to the BSD editline library (libedit)
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: haskell-editline Version : 0.2.1.0 Upstream Author : Judah Jacobson * URL: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/editline * License : BSD3 Programming Lang: Haskell Description : Haskell bindings to the BSD editline library (libedit) This package contains bindings to the BSD editline library. It provides a basic interface to the editline API for reading lines of input from the user. Additionally, a readline compatibility module is included which provides a subset of the functions from the readline package. It would have been preferable to package readline, but there are some problems with determining the Copyright of the user. See http://markmail.org/message/jd7at5izjmltzgqo for more details. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Bug#529192: ITP: debian-timeline -- Web-based timeline of the Debian GNU/Linux project
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: debian-timeline Version : 1 Upstream Author : Chris Lamb * URL : http://timeline.debian.net/ * License : Public domain Programming Lang: Javascript Description : Web-based timeline of the Debian GNU/Linux project The Debian Project timeline is a HTML and Javascript-based interactive timeline of the Debian GNU/Linux project. It includes the dates of: * All Debian releases, including point releases and freeze windows * Infrastructure changes * Conferences and bug-squashing parties * General resolution and DPL votes * Important releases of Debian-specific and third-party software * Curiosa items such as anniversaries and bug number milestones * (and more) This package will contain a local copy of the timeline currently available at <http://timeline.debian.net/>, providing end-users with something to show off at conferences (etc.) and to provide a real package to file bug reports against. By the way, if anyone was previously put off contributing by the dumb syntax, please note that it changed to a more familiar 822-based syntax. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Bug#529192: ITP: debian-timeline -- Web-based timeline of the Debian GNU/Linux project
Daniel Moerner wrote: > Are you considering using the version to better reflect when the package > was last updated? [..] > do it by the date when you fetch an updated timeline from the website and > upload it .. then it's just a (more-visible) duplication of the date in the changelog. (I sense a slight confusion in your question; the website and the package are generated from the same repository) > or to make the version reflect the most current Debian revision in the > timeline (e.g. 5.0.1 now). I fear it would change too often to make that worthwhile. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Re: Packaging the nusoap PHP lib instead of embedded copies ?
Neil Williams wrote:
> A better approach:
[..]
> You have searched for paths that end with nusoap.php in suite sid, all
> sections, and all architectures. Found 7 results. FilePackages
An even better approach in the long term would be to add a Lintian check
that flags up this common code copy.
However, doing so would be dependent on a proper package existing - Olivier,
please go ahead and package it.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
signature.asc
Description: PGP signature
Bug#738289: O: cakephp -- MVC rapid application development framework for PHP
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
Hi,
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: cakephp
Section: web
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~)
Standards-Version: 3.9.2
Homepage: http://www.cakephp.org/
Vcs-Git: git://github.com/lamby/pkg-cakephp.git
Vcs-Browser: https://github.com/lamby/pkg-cakephp
Package: cakephp
Architecture: all
Depends: ${misc:Depends}, php5
Recommends: cakephp-scripts
Suggests: cakephp-instaweb, php5-mysql
Conflicts: cakephp1.2
Replaces: cakephp1.2
Description: MVC rapid application development framework for PHP
CakePHP is a flexible model-view-controller rapid application development
framework for PHP inspired by Ruby on Rails.
.
CakePHP makes developing applications swiftly and with the least amount of
hassle:
.
* compatibility with PHP4 and PHP5
* integrated CRUD for database interaction and simplified queries
including scaffolding
* request dispatcher with good looking, custom URLs
* fast and flexible templating (PHP syntax, with helpers)
* useful core features (access control lists, AJAX integration, etc.)
* works from any website subdirectory
Package: cakephp-scripts
Architecture: all
Depends: ${misc:Depends}, cakephp (>= ${source:Version}), php5-cli
Conflicts: cakephp1.2-scripts
Replaces: cakephp1.2-scripts
Description: MVC rapid application development framework for PHP (scripts)
CakePHP is a flexible model-view-controller rapid application development
framework for PHP inspired by Ruby on Rails.
.
This package contains the bake.php and acl.php scripts for creating (or
"baking") CakePHP applications and modifying Access Control Lists.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140208233430.07d35...@sakaki.chris-lamb.co.uk
Bug#738291: O: codespeak-lib -- Advanced Python development support library
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: codespeak-lib
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~), python-all (>= 2.6.6-3~),
python3-all (>= 3.1.2-6~), python-setuptools, python3-setuptools
Standards-Version: 3.9.3 Homepage: https://bitbucket.org/hpk42/py
XS-Testsuite: autopkgtest
X-Python3-Version: >= 3.2
Vcs-Git: git://github.com/lamby/pkg-codespeak-lib.git
Vcs-Browser: https://github.com/lamby/pkg-codespeak-lib
Package: python3-py
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends}, python3-pkg-resources
Suggests: subversion, python-pytest, python-pytest-xdist
Description: Advanced Python development support library
The Codespeak py lib aims at supporting a decent Python development
process addressing deployment, versioning and documentation perspectives.
It includes: .
* py.path: path abstractions over local and Subversion files
* py.code: dynamic code compile and traceback printing support
.
This package provides the Python3 modules.
Package: python-py
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, python-pkg-resources
Replaces: python-codespeak-lib (<< 1.2.1-3)
Breaks: python-codespeak-lib (<< 1.2.1-3)
Provides: ${python:Provides}, python-codespeak-lib
Suggests: subversion, python-pytest, python-pytest-xdist
Description: Advanced Python development support library
The Codespeak py lib aims at supporting a decent Python development
process addressing deployment, versioning and documentation perspectives.
It includes: .
* py.path: path abstractions over local and Subversion files
* py.code: dynamic code compile and traceback printing support
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140208235003.7bc31...@sakaki.chris-lamb.co.uk
Bug#738292: O: fabric -- Simple Pythonic remote deployment tool
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: fabric
Section: net
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~), python-all (>= 2.6.6-3~)
Build-Depends-Indep: python-setuptools, python-sphinx, python-paramiko
Standards-Version: 3.9.3
Vcs-Git: git://github.com/lamby/pkg-fabric.git
Vcs-Browser: https://github.com/lamby/pkg-fabric
Homepage: http://fabfile.org/
Package: fabric
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, python-paramiko (>= 1.6),
python-pkg-resources, python-nose Suggests: libjs-jquery
Description: Simple Pythonic remote deployment tool
Fabric is designed to upload files and run shell commands on a number of
servers in parallel or serially. These commands are grouped in tasks
(which are regular Python functions) and specified in a 'fabfile.'
.
It is similar to Capistrano, except it's implemented in Python and doesn't
expect you to be deploying Rails applications.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140208235104.6798e...@sakaki.chris-lamb.co.uk
Bug#738293: O: giftrans -- Convert any GIF file into a GIF89a
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: giftrans
Section: graphics
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~)
Standards-Version: 3.9.2
Vcs-Git: git://github.com/lamby/pkg-giftrans.git
Vcs-Browser: https://github.com/lamby/pkg-giftrans
Package: giftrans
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, x11-common
Description: Convert any GIF file into a GIF89a
Allows for setting a specific transparent or background color of GIF
images as well as changing colors, adding or removing comments. Also
provides the ability to analyze GIF contents.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140208235202.3504f...@sakaki.chris-lamb.co.uk
Bug#738298: O: pdfrw -- PDF file manipulation library
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: pdfrw
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~)
Build-Depends-Indep: python-support, python-setuptools
Standards-Version: 3.9.2
Homepage: http://code.google.com/p/pdfrw/
Vcs-Git: git://github.com/lamby/pkg-pdfrw.git
Vcs-Browser: https://github.com/lamby/pkg-pdfrw
Package: python-pdfrw
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, python-reportlab
Replaces: pdfrw
Provides: pdfrw
Conflicts: pdfrw
Description: PDF file manipulation library
pdfrw can read and write PDF files, and can also be used to read in PDFs
which can then be used inside reportlab.
.
pdfrw tries to be agnostic about the contents of PDF files, and support
them as containers, but to do useful work, something a little higher-level
is required. It supports the following:
.
* PDF pages. pdfrw knows enough to find the pages in PDF files you read
in, and to write a set of pages back out to a new PDF file.
* Form XObjects. pdfrw can take any page or rectangle on a page, and
convert it to a Form XObject, suitable for use inside another PDF file
* reportlab objects. pdfrw can recursively create a set of reportlab
objects from its internal object format. This allows, for example, Form
XObjects to be used inside reportlab.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209000555.5f238...@sakaki.chris-lamb.co.uk
Bug#738297: O: mtpfs -- FUSE filesystem for Media Transfer Protocol devices
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained, and
I do not own any MTP devices anymore.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control:
Source: mtpfs
Section: utils
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7), libmtp-dev (>= 1.0.3), autotools-dev,
libfuse-dev, libmad0-dev, libid3tag0-dev, libglib2.0-dev
Standards-Version: 3.9.2 Vcs-Git: git://github.com/lamby/pkg-mtpfs.git
Vcs-Browser: https://github.com/lamby/pkg-mtpfs
Homepage: http://www.adebenham.com/mtpfs/
Package: mtpfs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, fuse
Description: FUSE filesystem for Media Transfer Protocol devices
MTPfs is a FUSE filesystem that supports reading and writing from MTP
(Media Transfer Protocol) devices, such as MP3 players, video players or
digital cameras.
.
In addition to revealing media files on the connected device, MTPfs
exposes a virtual directory called "/Playlists" which contains the
device's playlists as m3u files.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209000510.0db4d...@sakaki.chris-lamb.co.uk
Bug#738296: O: jasmin-sable -- Java class (.class) file assembler
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: jasmin-sable
Section: devel
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~), quilt, ant
Build-Depends-Indep: cup (>= 0.11a+20060608), default-jdk
Standards-Version: 3.9.2
Homepage: http://jasmin.sourceforge.net/
Vcs-Git: git://github.com/lamby/pkg-jasmin-sable.git
Vcs-Browser: https://github.com/lamby/pkg-jasmin-sable
Package: jasmin-sable
Architecture: all
Depends: default-jre | java2-runtime, cup (>= 0.11a+20060608),
${misc:Depends} Description: Java class (.class) file assembler
Jasmin is a Java ASseMbler INterface. It takes ASCII descriptions of Java
classes, written in the Java Virtual Machine instruction set in an
assembler-like syntax.
.
Jasmin converts these input files into binary Java class files (.class)
suitable for executing on an Java Virtual Machine.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209000401.16e70...@sakaki.chris-lamb.co.uk
Bug#738299: O: python-django-debug-toolbar -- Embedded debugging toolbar for Django projects
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: python-django-debug-toolbar
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 9), python, dh-python, python-setuptools
Standards-Version: 3.9.5
Homepage: https://github.com/django-debug-toolbar/django-debug-toolbar
Vcs-Git: git://github.com/lamby/pkg-python-django-debug-toolbar.git
Vcs-Browser: https://github.com/lamby/pkg-python-django-debug-toolbar
Package: python-django-debug-toolbar
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, libjs-jquery,
libjs-jquery-cookie Recommends: python-pygments
Description: Embedded debugging toolbar for Django projects
The Django Debug Toolbar is a plug-in Django application that displays a
set of panels which conveys information about the current request at the
top of the rendered page. It can show:
.
* Total time taken to process request
* Request variables, including GET, POST, cookie, and session
information.
* All SQL queries performed during response creation and processing,
including timing and 'EXPLAIN' output for each query in conjunction
with the total time spent performing SQL queries. If python-pygments is
installed, the SQL syntax is highlighted.
* Current Django version
* HTTP headers
* Total requests, time, hits and misses of the cache.
* Which templates were rendered the context provided to each template.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209000753.19698...@sakaki.chris-lamb.co.uk
Bug#738302: O: reinteract -- Worksheet-based graphical Python shell
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: reinteract
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.1), python-support
Standards-Version: 3.9.2
Homepage: http://www.reinteract.org/
Vcs-Git: git://github.com/lamby/pkg-reinteract.git
Vcs-Browser: https://github.com/lamby/pkg-reinteract
Package: reinteract
Architecture: all
Depends: ${python:Depends}, ${misc:Depends}, python-gtk2, python-matplotlib
Recommends: sox
Description: Worksheet-based graphical Python shell
Reinteract is a tool for interactive experimentation with Python
oriented around "worksheets" containing Python code combined with the
results of that code, formatted as text or graphical plots. Unlike a
traditional shell, you can go back and edit previously entered
statements, and the results will update.
.
Amongst other things, Reinteract is suitable for experimentation with
the Python language and for data analysis using NumPy and SciPy.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209001136.7ec62...@sakaki.chris-lamb.co.uk
Bug#738301: O: python-xmlrunner -- Python test runner that produces machine-readable results
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: python-xmlrunner
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~), python-support, python-setuptools
Standards-Version: 3.9.2
Homepage: https://github.com/danielfm/unittest-xml-reporting
Vcs-Git: git://github.com/lamby/pkg-python-xmlrunner.git
Vcs-Browser: https://github.com/lamby/pkg-python-xmlrunner
Package: python-xmlrunner
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}
Description: Python test runner that produces machine-readable results
unittest-xml-reporting is a Python "unittest" test runner that saves test
results to machine-readble XML files that can be consumed by a wide range
of development tools such as build systems, IDEs and continuous integration
servers (such as Hudson/Jenkins).
.
It also includes an adaptor so that it can be used in conjunction with the
Django web development framework.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209001052.597b2...@sakaki.chris-lamb.co.uk
Bug#738300: O: python-django-treebeard -- Efficient implementations of tree data structures for Django
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: python-django-treebeard
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~)
Build-Depends-Indep: python-support, python-sphinx, python-django,
graphviz, python-setuptools Standards-Version: 3.9.4
Vcs-Git: git://github.com/lamby/pkg-python-django-treebeard.git
Vcs-Browser: https://github.com/lamby/pkg-python-django-treebeard
Homepage: https://tabo.pe/projects/django-treebeard/
Package: python-django-treebeard
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, python-django (>= 1.0)
Description: Efficient implementations of tree data structures for Django
Django Treebeard is a library that implements efficient data structures
for storing hierachical data in a database using the Django web development
framework.
.
It currently includes 3 different tree implementations: adjacency list,
materialized path and nested sets. Each one has it's own strengths and
weaknesses but share the same API, so it’s easy to switch between them.
Package: python-django-treebeard-doc
Architecture: all
Section: doc
Depends: ${misc:Depends}, libjs-jquery
Description: Efficient implementations of tree data structures for Django
(documentation) Django Treebeard is a library that implements efficient
data structures for storing hierachical data in a database using the
Django web development framework.
.
It currently includes 3 different tree implementations: adjacency list,
materialized path and nested sets. Each one has it's own strengths and
weaknesses but share the same API, so it’s easy to switch between them.
.
This package contains the documentation in searchable HTML format.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209000950.080b7...@sakaki.chris-lamb.co.uk
Bug#738305: O: swi-prolog-doc -- Documentation for SWI-Prolog interpreter and XPCE
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: swi-prolog-doc
Section: doc
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7)
Standards-Version: 3.9.2
Vcs-Git: git://github.com/lamby/pkg-swi-prolog-doc.git
Vcs-Browser: https://github.com/lamby/pkg-swi-prolog-doc
Homepage: http://www.swi-prolog.org
Package: swi-prolog-doc
Architecture: all
Depends: ${misc:Depends}
Description: Documentation for SWI-Prolog interpreter and XPCE
SWI-Prolog is a Prolog implementation based on a subset of the WAM.
It is accompanied by XPCE, a symbolic programming environment for
user interfaces.
.
This package contains the documentation in PDF and HTML format for
SWI-Prolog and XPCE/Prolog.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209001946.1f083...@sakaki.chris-lamb.co.uk
Bug#738304: O: rst2pdf -- ReportLab-based reStructuredText to PDF renderer
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: rst2pdf
Section: utils
Priority: optional
Maintainer: Debian QA Group
Build-Depends-Indep: python-support, python-setuptools
Build-Depends: debhelper (>= 7.0.50~)
Standards-Version: 3.9.4
Homepage: http://code.google.com/p/rst2pdf/
Vcs-Git: git://github.com/lamby/pkg-rst2pdf.git
Vcs-Browser: https://github.com/lamby/pkg-rst2pdf
Package: rst2pdf
Architecture: all
Depends: ${python:Depends}, ${misc:Depends}, python-pkg-resources,
python-docutils, python-reportlab, python-simplejson, python-setuptools,
python-pygments, python-pdfrw (>= 0.1) Suggests: python-uniconvertor,
python-imaging, python-sphinx, python-matplotlib, python-aafigure
Description: ReportLab-based reStructuredText to PDF renderer The usual
way of creating PDF files from reStructuredText is by going through LaTeX.
This tool provides an alternative by producing PDF directly using the
ReportLab library.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209001801.0ae0e...@sakaki.chris-lamb.co.uk
Bug#738303: O: robocode -- Java programming game based on battle tanks
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
If you take over this package, please note that upstream have been making it
rather difficult to Debianise more recent upstream versions.
Source: robocode
Section: games
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7), quilt, ant
Build-Depends-Indep: java-gcj-compat-dev, imagemagick, default-jdk-doc,
libbcel-java Standards-Version: 3.9.2
Homepage: http://robocode.sf.net/
Vcs-Git: git://github.com/lamby/pkg-robocode.git
Vcs-Browser: https://github.com/lamby/pkg-robocode
Package: robocode
Architecture: all
Depends: ${misc:Depends}, openjdk-6-jre | java2-runtime, libbcel-java
Recommends: java2-compiler | openjdk-6-jdk | java-gcj-compat-dev
Suggests: robocode-doc
Description: Java programming game based on battle tanks
Robocode is a Java programming game where the goal is to develop a robot
battle tank to battle against other tanks. The robot battles are running
in real-time and on-screen. The motto of Robocode is: Build the best,
destroy the rest!
Package: robocode-doc
Architecture: all
Depends: ${misc:Depends}
Suggests: robocode
Section: doc
Description: Java programming game based on battle tanks (documentation)
Robocode is a Java programming game where the goal is to develop a robot
battle tank to battle against other tanks. The robot battles are running
in real-time and on-screen. The motto of Robocode is: Build the best,
destroy the rest!
.
This package contains Javadoc HTML documentation.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209001727.4075f...@sakaki.chris-lamb.co.uk
Bug#738306: O: trac-spamfilter -- Spam-prevention plugin for Trac
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: trac-spamfilter
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~)
Build-Depends-Indep: python-support, python-setuptools
Standards-Version: 3.9.2
Vcs-Git: git://github.com/lamby/pkg-trac-spamfilter.git
Vcs-Browser: https://github.com/lamby/pkg-trac-spamfilter
Homepage: http://trac.edgewall.org/wiki/SpamFilter
Package: trac-spamfilter
Architecture: all
Depends: ${python:Depends}, ${misc:Depends}, trac (>= 0.10),
python-pkg-resources Recommends: python-dnspython (>= 1.3.5), spambayes
Description: Spam-prevention plugin for Trac
This plugin attempts to reject contributions to Trac environments that
contain spam. It can use the following techniques:
.
* Regular expressions
* Akismet web service
* IP throttling
* IP blacklisting (requires python-dnspython package)
* Bayesian filtering (requires spambayes package)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209002036.0b0ad...@sakaki.chris-lamb.co.uk
Bug#738307: O: pyprotocols -- Open Protocols and Component Adaptation for Python
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: pyprotocols
Section: python
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~), quilt, python-setuptools,
python-all-dev, python-support Standards-Version: 3.9.2
Homepage: http://peak.telecommunity.com/PyProtocols.html
Vcs-Git: git://github.com/lamby/pkg-pyprotocols.git
Vcs-Browser: https://github.com/lamby/pkg-pyprotocols
Package: python-protocols
Architecture: any
Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends},
python-decoratortools (>= 1.3) XB-Python-Version: ${python:Versions}
Description: Open Protocols and Component Adaptation for Python
Do you hate having to write lots of if-then logic to test what type
something is? Wouldn't it be nice if you could just declare "I want this
object to have this behavior" and magically convert whatever value you
have, to the type you need? PyProtocols lets you do just that, cleanly,
quickly, and robustly -- even with built-in types or other people's
classes. .
PyProtocols extends the PEP 246 adapt() function with a new "declaration
API" that lets you easily define your own protocols and adapters, and
declare what adapters should be used to adapt what types, objects, or
protocols. In addition to its own Interface type, PyProtocols can also use
Twisted and Zope's Interface types too. (Of course, since Twisted and Zope
interfaces aren't as flexible, only a subset of the PyProtocols API works
with them. Specific limitations are listed in the documentation.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209003309.57b7a...@sakaki.chris-lamb.co.uk
Bug#738308: O: bustle -- D-Bus activity visualiser
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
(I can't seem to upload a new version to change the Maintainer: - needs some
slight updating for the latest Haskell platform and my Haskell is incredibly
rusty these days..)
Source: bustle
Section: devel
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50), ghc (>= 6.10), pkg-config,
libdbus-1-dev, libglib2.0-dev, libghc-mtl-dev, libghc-cairo-dev,
libghc-gtk-dev, libghc-parsec3-dev, libghc-glade-dev Standards-Version:
3.9.2 Homepage: http://willthompson.co.uk/bustle/ Vcs-Git:
git://github.com/lamby/pkg-bustle.git Vcs-Browser:
https://github.com/lamby/pkg-bustle
Package: bustle
Architecture: any
Depends: ${misc:Depends}, ${shlibs:Depends}
Suggests: graphviz
Description: D-Bus activity visualiser
Bustle is a tool to chart and provide timing information of D-Bus
calls for profiling and debugging purposes. It is intended to replace
reading the cryptic output of dbus-monitor.
.
Calls are displayed using Message Sequence Charts, a succinct way of
representing entities and interactions over time. It can also output
data in Graphviz format.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140209004640.61c53...@sakaki.chris-lamb.co.uk
Bug#638862: ITP: pdfrw -- PDF file manipulation library.
Package: wnpp Severity: wishlist Owner: Chris Lamb X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: pdfrw Upstream Author : Patrick Maupin * URL : http://code.google.com/p/pdfrw/ * License : MIT Programming Lang: Python Description : PDF file manipulation library. pdfrw is a basic PDF file manipulation library. [It is being packaged as rst2pdf currently ships an embedded code copy of this library and intrigeri would like to package something requiring it too - see #638507.] Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org `- signature.asc Description: PGP signature
Raising the severity of reproduciblity issues to "important"
Hi -devel, The reproducible-builds team are currently contributing patches with "wishlist" severity. This is because it is not currently possible to build reproducible packages within sid itself - we maintain a separate repository whilst our changes to the toolchain are pending review and consultation. Filing these bugs with a higher severity -- which would require developers to use this repository to fully test any modifications -- would be unacceptable. However, based on an informal survey at DebConf (and to reflect the feeling towards software reproducibility in the free software community in general) unless there are strong objections I intend to raise the severity of these wishlist issues to "important" once the toolchain changes to dpkg and debhelper land in sid. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Raising the severity of reproduciblity issues to "important"
> Quoting Holger: "This is a lie" (pointing to a graph that was being > shown on the screen). The current figures we are handling right now > refer to a modified build environment (i.e. sid + the special > sources.list line from alioth). I do not intend to change anything until these changes have landed in sid. > Also, we should better categorize the reasons why packages do not > build reproducibly. We currently have 158 distinct categories of issues, each with a brief description of the issue and their current status such as a link to a BTS or upstream patch, or simply initial ideas on how to start fixing them. Is there anything else that we could be doing that you think would help here? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Uncoordinated upload of the rustified librsvg
Dear Jonathan, > >Debian's Dictionary is in a weird order; "Thank You" is right next to > >the definition of "Entitlement" > > Sorry this wasn't a helpful message. (I'm a little behind on this thread alas but I just wanted to thank you for following up with this retraction.) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: I resigned in 2004
Dear Mattia, > My reply indeed had quite a grumpy tone, and I realized only after > sending it, of course. I need to get into the habit of asking somebody > else to review my emails when they treat such matters. Thank you for not only pausing for this self-reflection but for subsequently sharing it so candidly on-list. However, I must take slight issue with some of the ways you expressed yourself in your follow-up. On the one hand, people should indeed "just click those damn buttons" and it's unfortunate that Willy chose to use the language he did, but I would be surprised if there were no topics or issues for you (including outside of the free software world) where reacting in a ungentlemanly manner is likely given some history or context. I'm also fairly confident you would agree that the fact that people are not emotionless and predictable robots brings some much-needed colour to this world, despite the tragic irony in that it can bring both pain and pleasure to others. Without wish to delve too much into the specifics, dismissing and characterising a Developer's regrettable departure from the Project as a childish "rage quit" appears to lack suitable empathy and understanding for a fellow human being, yet alone a former colleague. More concerning, though, might be the casual suggestion that someone who reacts to "some simple emails should seek professional psychological counselling", specifically in its implication that someone who feels overly agitated from the reader's point of view is by-definition mentally unstable and even has overtones of blaming the victim. I am certain that the abrupt response you received also engendered strong feelings in yourself so what was written in the heat of the moment was partially understandable, but I'm sure that you might wish to consider modifying or even retracting some of the statements or connotations that were made in the above light. I hope that this episode has not deterred you from your indefatigable work in the MIA team and that you, like me, have only the very best wishes for your former confederate in his current endeavours. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: I resigned in 2004
[replying directly] Mattia Rizzolo wrote: > […] for some reason always involving some German DD, even worse if > there are multiple ones […] https://i.imgur.com/PoWwX7m.png Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: I resigned in 2004
Chris Lamb wrote: > [replying directly] Or not! Enjoy our sub-conversation, -devel. :) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Iptables on Sid
Ian Jackson wrote:
> Daniel Pimentel writes ("Iptables on Sid"):
>
> > I'd like to report a posible bug:
[..]
> Please see this page about how to report a bug:
Actually, I believe this to be already filed as:
https://bugs.debian.org/914074
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Re: Our build system may be broken: /bin vs /usr/bin
Hi Dimitri, > […] e.g. using reproducible builds infra to do "build in > --no-merged-usr, rebuild in --merged-usr, result should be the same" > either as a one-off, or on the ongoing basis. So, as mentioned on: https://reproducible-builds.org/blog/posts/185/ … Simon McVittie has actually patched our testing framework to vary this and this is now live. https://bugs.debian.org/901473#33 (There is some further discussion on this bug.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Bug#914135: distribution-and-changes-mismatch not emitted when it should be
tags 914135 + moreinfo thanks Hi Rebecca, > > libnfs (2.0.0-1~exp1) experimental; urgency=medium [..] > > Is this something that may be notified by lintian?> > In theory, > https://lintian.debian.org/tags/distribution-and-changes-mismatch.html , > but since it didn't trigger on libnfs, it would appear to be broken. ^^^ I do note that there was a mismatch for this specific upload, ie: https://tracker.debian.org/news/946971/accepted-libnfs-200-1exp1-source-amd64-into-unstable-unstable/ … but what is the evidence for Lintian not seeing this? The maintainer could have uploaded anyway and/or they had an old version of Lintian, etc. If you are wondering why it does not appear on: https://lintian.debian.org/tags/distribution-and-changes-mismatch.html ... that is because that requires the .changes file to be around, whilst lintian.debian.org processes source packages (ie. that particular webpage is pretty useless). Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Our build system may be broken: /bin vs /usr/bin
Hi Dirk, > | > … Simon McVittie has actually patched our testing framework to vary > | > this and this is now live. > | > > | > https://bugs.debian.org/901473#33 […] > Are we sure this is fixed? It might have taken a while for various build chroots to update so I would be wary of inferring too much, if anything, by comparing timestamps. It would, of course, also take a while to "get around" our somewhat expansive archive... Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Our build system may be broken: /bin vs /usr/bin
[pruning CC] Dirk, > Other than forcing builds through the system is there another way for me to > check in, say, a week or two? Not entirely sure what you mean here. You can certainly reschedule builds at will, but in terms of "checking-in" a fortnight from now… set a date in your calendar? ;) Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: NEW and RC bugs (Re: julia_1.0.0-1_amd64.changes REJECTED)
Ian Jackson wrote:
>[..] Compared to REJECT mails:
>
> - Discussions in the BTS are more transparent
> - Discussions in the BTS are better organised
> - Discussions in the BTS can have wider participation
> - Discussions in the BTS are better archived
> - Discussions in the BTS have better metadata
This would be a fairly-accurate precis of my position.
Indeed, I tend to ACCEPT whilst filing a bug at the same time with
varying degrees of severity through RC-level (#910031, #910656),
normal (#911532) and wishlist (#910029, #910330), etc. etc.
> I have no problem with auto-REJECTs, which are generally
> either for really serious problems, or can be overridden.
On that note, please suggest additions to the auto-REJECT list as
MRs against dak. It is likely missing many useful tags that have
been added since it was last refreshed.
(As an aside, some tags cannnot be overridden but that's not quite
on-topic here…)
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Re: Bug#881896: RFP: src -- Simple Revision Control, single-file and single-user version tracking
retitle 881896 ITP: src -- Simple Revision Control, single-file and single-user version tracking thanks [Adding debian-devel@lists.debian.org to CC] Hi Mike et al., > Package: wnpp > Severity: wishlist > > * Package name: src > Version : 1.17 Just reviewing this in NEW and was briefly uneasy about a package with this name entering the package namespace. For example, given: $ apt-get source src … and that there are also many places in Debian where we would be using nomenclature such as: src:src … to refer to this package, this is obviously somewhat confusing out of context. There would also be binary packages that would be called "src" (!) which, less problematically, would exist alongside packages such as "linux-source" and "uwsgi-src" etc. Is there a prefix, suffix or even an alternative name that upstream use to avoid this? If not, we may have to invent one here. Thoughts welcome. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: possible conflict over the /usr/bin/ia namespace
[Adding ftpmas...@debian.org to CC] Hi Antoine et al., > So anyways - irl will upload a new package now, presumably -2 or more, > so i think << 0.242+git20151019-2~ is fine. I just went to process this package in NEW but this new upload does not appear to have happened yet. Is that correct? Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Bug#909550: possible conflict over the /usr/bin/ia namespace
Antoine Beaupré wrote: > >From what I can tell, both were: > > https://tracker.debian.org/news/989684/accepted-python-duckduckgo2-0242git20151019-2-source-amd64-into-unstable/ Neat, thanks. I've just processed python-internetarchive 1.8.1-1 in NEW. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Bits from the DPL (December 2018)
Hi Nikolaus,
> > * Followed-up on progress regarding potential new "Member Benefits"
> >[9] and ensured that some previously-promised reports for events
> >funded by Debian ended up appearing on Planet [10].
> >
> >I also provided solicited (!) advice to a few other developers on
> >conference booths and suitable/alternative conferences they may
> >wish to attend instead.
>
> Is there something missing here? Attend instead of what, and how does
> that relate to member benefits?
I don't believe anything is missing; these are two standalone
sentences on different topics. ("X conference? Thought about Y
conference instead?")
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Re: Nix and non-standard-toplevel-dir
Hi Kai, > I have filled an ITP for the Nix package-manager [1]. As it happens, I did some work on this in early 2017: https://salsa.debian.org/lamby/pkg-nix .. but I ran out of bandwidth to persue it. I believe others on this list took up the challenge too. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Conflicting lintian warnings when using debian/tests/control.autodep8 or debian/tests/control
Ondrej, > > Any idea what to do (except overriding one of the lintian > > warnings)? > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918621 Merged & uploaded to unstable in lintian 2.5.120; thanks. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Upload new version to new-queue?
Hi Thomas, > What happens if I upload a new version of a package while a previous one > is still waiting for review in the new queue? It will "do the right thing". Due to dak performing a suitable sort, the most-recent version will be reviewed by the FTP masters. Go ahead and upload. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Use of FATE (FFmpeg Automated Testing Envionment) data?
W. Martin Borgert wrote: > I can easily add the small number of needed files to debian/fate- > suite/, but I'm not even sure about the license of the files. Dumb question: have you tried consulting upstream? Getting a definitive statement from them on the licensing of these files would probably be most helpful and possibly even required here, as well as assisting potential future users of this test data. (Naturally, downloading them during the build would not be acceptable, but I wonder what the consensus would be on the ethics of downloading "contrib"-like data during autopkgtests?) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Use of FATE (FFmpeg Automated Testing Envionment) data?
W. Martin Borgert wrote: > > Naturally, downloading them during the build would not be > > acceptable, but I wonder what the consensus would be on the ethics > > of downloading "contrib"-like data during autopkgtests? > > It's also a practical matter: Can I run autopkgtests, when my > computer is disconnected from the internet? Can I run them, if > their server is down? Will they always serve exactly the same > files or will I have to deal with random test results? Indeed, this would definitely be a vastly inferior fallback option. As someone who has encountered these issues countless times via the Reproducible Builds effort, I might have assumed these highly-salient practical concerns as a given and focused on the free software question. (However, on the practical side, I believe the "flaky" Restriction could, potentially, be suitable.) > Maybe we don't need a huge amount of test data, i.e. not the > full set that is used by upstream. A small subset might be > sufficient for at least some packages. In my case, it's only > 3.3 MiB. Noted, but it is not the size that is the concern, but rather the licensing. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: ITP: fossology -- FOSSology is an open source license compliance software system and toolkit.
[Adding 924...@bugs.debian.org to CC] Gaurav Mishra wrote: > Package: wnpp > Severity: wishlist > Owner: Gaurav Mishra For debian-devel, this got filed as: https://bugs.debian.org/924659 Guarav, just a friendly note to say that you CC'd debian-devel explicitly when filing this bug instead of using the X-Debbugs-CC mechanism. See: https://www.debian.org/Bugs/Reporting … specifically the "Sending copies of bug reports to other addresses" section for the rationale here. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#926470: RFP: annocheck -- analyse an application's compilation
Package: wnpp Severity: wishlist Owner: la...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: annocheck * URL : https://sourceware.org/git/?p=annobin.git * License : GPL3 Programming Lang: C Description : Analyse an application's compilation >From annocheck(1) The annocheck program can analyse programs and report information about them. It is designed to be modular, with a set of self- contained tools providing the checking functionality. Currently the following tools are implemented: The annocheck program is able to scan inside rpm files and libraries. It will automatically recurse into any directories that are specified on the command line. In addition annocheck knows how to find debug information held in separate debug files, and it will search for these whenever it needs the resources that they contain. New tools can be added to the annocheck framework by creating a new source file and including it in the Makefile used to build annocheck. The modular nature of annocheck means that nothing else needs to be updated. New tools must fill out a "struct checker" structure (defined in annocheck.h) and they must define a constructor function that calls "annocheck_add_checker" to register their presence at program start-up. The annocheck program supports some generic command line options that are used regardless of which tools are enabled. This RFP was prompted by the following wishlist request against diffoscope: https://salsa.debian.org/reproducible-builds/diffoscope/issues/51 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: Bits from /me: Difficulties in Deep Learning Framework Packaging
Adrian Bunk wrote: > How many percent of the paid GSoC and Outreachy student workers > continue unpaid afterwards and become a DM or DD? > > My impression is that GSoC does not have a high quota, > and Outreachy is a complete failure. Curious that you have that perception. I don't have hard data but I can immediately think of at least five folks. And that's not counting myself. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Bits from /me: Difficulties in Deep Learning Framework Packaging
Adrian Bunk wrote: > > Curious that you have that perception. I don't have hard data but I > > can immediately think of at least five folks. > > > > And that's not counting myself. > > GSoC or Outreachy? I don't really track in my head the origin outreach programme of these new friends of mine, sorry. > And 6 out of how many? No idea. As others have pointed out, it feels like the ball is not in my court to provide hard data to disprove your impressions. To blindly continue in a purely anecdotal manner, since I posted I could recall at least two more and was even told IRL about another two in an entirely-spontaneous conversation last night. Furthermore, the silent implication that this is the primary or even the sole metric for these initiatives success does not sit right to me, not least because a number you might find unacceptably low might say more about Debian's attitude or welcoming atmosphere rather than a judgement of the programmes themselves... As an aside, you may need to reassure or correct me but I must say I find myself somewhat uneasy at the tenor and manner in which you are "just asking questions" in this thread. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Introducting Debian Trends: historical graphs about Debian packaging practices, and "packages smells"
Lucas Nussbaum wrote: > […] in my lintian fork […] I got around to releasing Lintian 2.13.0 to unstable earlier today including your suggested changes (so hopefully you can drop your fork for the time being). Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Survey: git packaging practices / repository format
Dear Ian,
> Can you please look through the table below and see if I have covered
> everything you do ?
>
> In particular:
> - have I missed a git repository and history layout
> - have I missed a primary tool that should be mentioned
> - are any of the details wrong for workflows that you use ?
[…]
I am genuinely not being snarky here nor the "logical fallacy spotter"
pub bore, but don't forget that not everybody can follow debian-devel
and thus there may be some blind spots or observation bias at work in
the results.
Best of luck with the survey, naturally, I look forward to the outcome.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
Re: Debian, so ugly and unwieldy!
Adam Borowski wrote: > This is about GUI appearance and ergonomy. > > I'll concentrate at XFCE, as I consider GNOME3's UI a lost cause, thus I'd > find it hard to bring constructive arguments there. > > I also hate with a passion so-called "UX designers". Those are folks who > created Windows 8's Metro tiles, lightgray-on-white "Material Design" flat > unmarked controls, and so on. They work from a Mac while not having to > actually use what they produce. I empathise, understand and agree with many of the concerns that you raised in your message. It is therefore particularly tragic that you chose to open your remarks and suggestions in such a manner. Expressing distain for the status quo and then compounding that by passing judgement on the people who may be in the very position to improve it seems, at best, unlikely to achieve our shared aims. It furthermore frames any discussion in an unnecessarily negative light, filtering responses to those who are willing to engage and contribute to the conversation on combative terms, ensuring a systematic observation bias in the outcome. As others have mentioned, I hope that Debian remains a project that makes it evermore welcoming to individuals who can advance our aims and we were able to continue to discuss sensitive topics in a collective and constructive manner. In that light, I would gently ask that all well-meaning and sincere proposals to our lists make pains to avoid all possibility of being accused of the aforementioned sins. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Debian, so ugly and unwieldy!
Adam Borowski wrote: > > As others have mentioned, I hope that Debian remains a project that > > makes it evermore welcoming to individuals > > Yeah but one of our core values is "we do not hide problems". I'd rather > lash out and voice my gripes _with actionable ideas_ than to stay silent to > avoid hurting someone's ego. We share the same goal, I merely want to point out that your confrontational approach to discussing this issue is counterproductive in that will alienate or otherwise push away the people with the technical skills to remedy it. > And I'd also prefer to avoid pushing my way in a back alley, thus I'm asking > for ideas and consensus before filing bugs. It is a slip on your part to represent my practical suggestions for achieving our mutual aims in any way as an attempt on my part to suppress what you can say. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Improving Reimburse workflow? (Re: Suspending Offer to Reimburse Expenses for Attending Future Bug Squashing Parties)
Carsten Schoenert wrote:
> So a wild guess, why isn't it possible to create a webui which is
> guiding me through a reimbursement request and also make it possible to
> collect all the requests to the persons which have to agree or disagree
> on the calls?
I acknowledge that Sam has requested this topic moves to -project and
would agree with that assessment.
However, if this thread is actually restarted there I would ask that
any discussion attempts to first identify and actually confirm
problems with the current systems from the stakeholders involved,
rather than jumping to conclusions or implementation concerns.
Post-mortems of failed engineering projects are replete with examples
of planning, designing and even coding pushing ahead without listening
to and ultimately empathising with the people who will actually be
using the software. I am sure many readers of this list will painfully
familiar with this phenomenon.
Indeed, making "wild guesses" about their concerns can easily come
across as presumptious or even condescending; when one casually
assumes the users' concerns, it tends to trivialise and minimise their
real-life experiences and opinions.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
Re: scratch buildds
Adam Borowski wrote: > Thus, what would you guys say about a new distribution, "scratch"? It would > be a kind of extra-experimental that doesn't put its build results anywhere > persistent. Throwing away built .debs would be ok, keeping just logs. Perhaps I'm missing something but would introducing more architectures to the salsa.debian.org continuous integrations runners not serve mostly the same purpose? The developer's workflow would simply be to push a commit and it would be built and tested automatically. This approach would also appear to cover more use-cases, require less DSA attention ,and even allow non-DD/DMs to utilise the service too. (I would concede that this would essentially require adopting a salsa and Git-based packaging scheme, however.) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: The Difference between debcheckout and dgit and what they try to accomplish
Hi Enrico, > This reminds me of something that popped up in a dinner discussion a few > days ago: mandate documenting workflow in debian/README.source no matter > what, and allow to symlink that file to a repository in > /usr/share/doc/somewhere/ as we do for common licenses. I do like the symlink part of this idea as it could mostly address the "boy who cried wolf"-like boilerplate concerns that I raised in 2009 about previous potential overuses of README.source, although in this particular case with respect to quilt patches: https://bugs.debian.org/543417 (*silently cringes at past-lamby's usage of the hackneyed "considered harmful" suffix*) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Programs contain ads - acceptable for packaging for Debian?
Jason Crain wrote: > > Such ads is displayed only when users have Internet connection, and there is > > no way to patch ZZZ in order to remove ads (or we have to buy "pro" version > > which doesn't contain ads and adds more features). > > If it's free software, meaning it is freely modifiable and > redistributable, how is there no "no way to patch ZZZ in order to remove > ads"? Indeed, and I fully +1 all the other sentiments regarding privacy & network access etc., only sardonically adding that such advertisement are typically unspeakably unsightly and surely have no place in our distribution on those grounds alone. However, as a refinement — or perhaps to get the last remaining "extra credit" in this thread which appears to be reaching consensus — note that there are some licenses that ask you to redistribute changed copies under a different name. Thus depending on your definition of what ZZZ "is" (as well as how pedantic you are feeling at the time) there are indeed "soft" ways of having such a "no way to patch ZZZ" clause that «prima facie» appears to be non-free. Most notably from a Debian point of view would be: https://en.wikipedia.org/wiki/LaTeX_Project_Public_License#Unique_features_of_the_license Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Error when running dh_dwz (actually an error when running dwz(1))
Hi Boyuan, > I don't have much experience of dealing with debugging symbols so any hints > would be appreciated. I would also be interested in this from my "Lintian hat" of: https://bugs.debian.org/931632#35 Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Detecting (upcoming) problems using automatic tests
[adding jak@ to CC as requested; no need to CC me, however...] Hi Julian, > I was just thinking that adding deprecation warnings and stuff > to software is "nice", but the problem with warnings is that they > tend to not break tests. I'm guessing you have a particular package or use-case in mind that sparked this idea — could you share? That might help make this abstract concept a little more concrete. I'm also assuming that you meant for this to be wider than just GCC so, for example, making -Werror global wouldn't be sufficient as it wouldn't catch, say, warnings from pure-Python packages. > I feel like it would be nice to come up with a standard environment > variable to turn warnings into errors, so we can ensure issues are > fixed and the warnings are actually useful. Hm, although perhaps DEB_BUILD_OPTIONS is the prefered place for this kind of toggle rather than an environment variable? Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: Detecting (upcoming) problems using automatic tests
Hi Simon,
> > Hm, although perhaps DEB_BUILD_OPTIONS is the prefered place for this
> > kind of toggle rather than an environment variable?
>
> We already have "nocheck" to disable tests, and IMO the default should be
> to run tests if we can.
Unless I am grossly misunderstanding him, Julian's suggestion was for
an optional and orthogonal boolean of some description that turns
warnings into errors, rather than a proposal to cease execution of
tests by default.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
Re: Is it the job of Lintian to push an agenda?
Jérémy Lal wrote:
> "Is it the job of Lintian to push an agenda?"
> is a good question, and it would be nice to get a general answer,
> separately from the technical issue about sysvinit scripts.
Difficulties are always inherent in shipping any opinionated linter to
people with a wide spectrum of motivations and ideas. Furthermore, if
it becomes pervasive then there is not only a risk of its output being
followed without attention, when interpreted as a kind of de-facto
policy there is an additional a danger of it being beaten from a
plowshare back into a sword on contentious issues.
As the first line of defense to the above, Lintian reflects the
positions taken and espoused in our official Policy and should [0]
always defer to that esteemed text.
It therefore follows that if the Debian Policy decrees a certain
direction and Lintian mirrors that then in the rare cases of dissent
or disagreement the right and proper course of action is to re-raise
it via Policy and its various appeal processes. If that is not
possible then that is a regrettable state of affairs, but Lintian is
not the venue to stage one's passive-aggressive proxy war on
controversial and highly-charged issues within Debian and its
maintainers have neither the strength, stomach nor spoons for such
maneuevers.
As Sean implies in an adjacent message, all of the above is compounded
by there being a number of recommendations that are considered to be
good practice by most [1] but are not part of Policy (and most should
or can never be). Lintian's various severity levels ("E:", "W:", "I:",
etc), as well as responding to cordial and reasonable requests to
adjust these do allow it to address, albeit extremely clumsily, the
extremely wide spectrum involved here.
As a postscript, it seems like the term "agenda" was a regrettable
choice for this thread given that it carries an implication of
underhanded and dishonest motives. As I am certain that would never be
the intention of my dear colleagues, to avoid any possible
misinterpretations for the remainder of my message I have adopted
alternative terms instead.
[0] Or, if you may excuse an RFC2119 pun, "MUST"...
[1] Feel free to dilute to taste with similar terms.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
Re: Is it the job of Lintian to push an agenda?
Theodore Ts'o wrote: > P.S. I'm going to be adding an override in e2fsprogs for > package-supports-alternative-init-but-no-init.d-script because it > has false positives Regardless of the specifics of this particular package if Lintian could feasibly not emit this false-positive, would it surely not be more sensible to get this fixed there instead? That would not only be a cleaner solution than an override (which you would likely just have to remove later...) it would be a general kindness in that it could potentially save countless other developers undergoing the same manual process as you. > It most *definitely* is not certain. Again, this sounds like something trivially addressed in Lintian itself, or perhaps even by not reading too much into this apparently entirely-adjunct advisory classification that is, after all, not central to Lintian's operation. Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: default firewall utility changes for Debian 11 bullseye
Raphael Hertzog wrote:
> The other desktop firewall that I know is "ufw" but it doesn't seem to
> have any momentum behind it.
It is curious you mention a lack of momentum; in my experience, it is
the most commonly recommended firewall on various support-adjacent
sites around the internet. (Perhaps due to it's Ubuntu/Canonical
associations and authorship.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
Re: default firewall utility changes for Debian 11 bullseye
Jamie Strandboge wrote: > Again, I'm biased, but ufw supports IPv6. It's also been on the default server > and desktop install of Ubuntu for 9+ years. ufw functions well for bastion > hosts, less so for routers (though it has some facility there). It also has a first-class Ansible module which (given a flood of firewall options around when I needed to pick something in haste around the time of the stretch release…) was actually the deciding factor for me: https://docs.ansible.com/ansible/latest/modules/ufw_module.html Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Bug#932470: O: adminer -- web-based database administration tool
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-devel@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see its Vcs-Git entry.
The binary packages are:
Package: adminer
Architecture: all
Depends:
libapache2-mod-php | php-cgi | php-fpm | php,
php-mysql | php-sqlite3 | php-pgsql,
${misc:Depends},
Recommends:
php-cli,
php-mysql,
php-pgsql,
php-sqlite3,
Suggests:
default-mysql-server | virtual-mysql-server | postgresql | sqlite3,
Description: Web-based database administration tool
Adminer (formerly phpMinAdmin) is a full-featured database management tool
written in PHP. Conversely to phpMyAdmin, it is a light weight application
with these priorities in order: security, user experience, performance,
feature set and size.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
Re: file(1) now with seccomp support enabled
[Adding rb-gene...@lists.reproducible-builds.org to CC]
Hi Christoph,
> Overall, I'm just asking to keep an eye on possible breakage, also
> check the kernel log.
I noticed that there were a number of recent regressions in previously
reproducible Java packages being tested by the Reproducible Builds
project's CI platform which I could identify as being caused by our
strip-nondeterminism tool.
However, as there was a very recent change to some strip-nondeterminism
code that uses "monkey patching" I was predisposed to believe that was
the cause, but it eventually turned out to be the call to file(1)
missing a --no-sandbox parameter (where supported / appropriate).
It did not even occur to check my kernel log as you suggest — it was
only when quickly hacking in a:
override_dh_strip_non_determinism:
strace -eexecve -f dh_strip_nondeterminism
… to my test package that I figured the file(1) process was being
killed (without returning any output) with SIGCHLD that things were
perhaps lower-level in nature. This has been resolved in strip-
nondeterminism 1.3.0, uploaded this afternoon.
This mail is not a request for anything, but rather a general heads-up
for you and a way of "keyword stuffing" various terms the above
paragraphs into search indexes for the benefit of others looking for
perhaps-obscure issue like this in the future. It is also an implicit
thanks for pushing security hardening features. :)
Best wishes,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
Bug#945524: RFP: container-diff -- Diff Docker containers
Package: wnpp Severity: wishlist Owner: la...@debian.org X-Debbugs-CC: debian-devel@lists.debian.org * Package name: container-diff * URL : https://github.com/GoogleContainerTools/container-diff * License : Apache-2.0 Programming Lang: Go Description : Diff Docker containers >From upstream's website: container-diff is a tool for analyzing and comparing container images. It can examine images along several different criteria including: * Docker Image History * Image file system * Image size * APT packages * RPM packages * pip packages * npm packages These analyses can be performed on a single image, or a diff can be performed on two images to compare. The tool can help users better understand what is changing inside their images, and give them a better look at what their images contain. This RFP was prompted by the following wishlist request against diffoscope: https://salsa.debian.org/reproducible-builds/diffoscope/issues/39 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Re: lintian: please downgrade mailing-list-obsolete-in-debian-infrastructure warning
tags 958666 + pending thanks Holger Levsen wrote: > definitly, yes, filing this bug now. As mentioned elsewhere, this was already fixed yesterday in fd8ee67d. -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org 🍥 chris-lamb.co.uk `-
Re: ITP: django-setuptest -- simple test suite enabling Django app testing via setup.py
Hi, > ITP: django-setuptest -- simple test suite enabling Django app testing via > setup.py Do note that upstream is a little--err--slow, and doesn't even support the version of Django that's currently in sid: https://github.com/praekelt/django-setuptest/pull/26 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#838416: ITP: roughtime -- Secure time synchronisation
Package: wnpp
Severity: wishlist
Owner: Chris Lamb
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: roughtime
Upstream Author : Google, Inc.
* URL : https://roughtime.googlesource.com/roughtime
* License : Apache 2.0
Programming Lang: Go
Description : Secure time synchronisation
Roughtime is a protocol that aims to achieve rough time synchronisation
in a secure way that doesn't depend on any particular time server, and
in such a way that, if a time server does misbehave, clients end up with
cryptographic proof of it.
-- <https://roughtime.googlesource.com/roughtime>
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Finding all "my" duplicate material on dedup.debian.net?
Hi -devel & Helmet, I recently discovered <https://dedup.debian.net/>. First, thanks to Helmut for setting this up. I've just removed some duplicates in a package [0] with symlinks, but I was wondering if I am missing a page or feature where I can see all "my" offenses against duplicated content, preferably ordered by (for example) the number of bytes duplicated? Seeing the worst offenders in the Debian archive would also be fascinating. [0] https://dedup.debian.net/compare/redis-tools/redis-server Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
