request for removal of texmacs-extra-fonts
Hi all, Since texmacs 1.0.7.13, texmacs includes all fonts of texmacs-extra-fonts so texmacs-common sets Conflicts: texmacs-extra-fonts since Sep. 2011 and it seems there is no problem by now. So I think texmacs-extra-fonts is obsolete and should be removed. I find science-typesetting sets Recommends: texmacs-extra-fonts by mistake and I already filed a bug so I think there will be no dependency on texmacs-extra-fonts. I'm a maintainer of texmacs but not of texmacs-extra-fonts which is maintained by QA team. What is the best way to do in this case. Is this mail enough or something more is necessary? Thanks in advance. Best regards, 2012-8-2(Thu) -- Debian Developer - much more I18N of Debian Atsuhito Kohda Department of Math., Univ. of Tokushima -- 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/20120802.151157.409379923.ko...@pm.tokushima-u.ac.jp
Re: [Pkg-postgresql-public] postgresql-* package namespace (was: Re: Bug#683486: ITP: barman -- Backup and Recovery Manager for PostgreSQL)
Fwiw, I'm not saying packages must not use the postgresql namespace, I'd just leave it to the maintainer to decide. Martin Pitt schrieb: Hello Ansgar, Christoph, Christoph Berg [2012-08-01 21:12 +0200]: > The various postgresql-* packages are mostly plugins (PL/something) Right, postgresql-X.Y-foo are server-side plugins which are specific to a major PostgreSQL server version. They need to be versioned just like PostgreSQL itself for upgrades, parallel installability, etc. > which follow the example of postgresql-plperl-x.y (built from PG > core). For real applications like barman, that's not really > necessary. Where "real applications" == client-side PostgreSQL users, i. e. which only use libpq, not build against postgresql-server-dev-X.Y. Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Re: [Pkg-postgresql-public] postgresql-* package namespace (was: Re: Bug#683486: ITP: barman -- Backup and Recovery Manager for PostgreSQL)
Hello Ansgar, Christoph, Christoph Berg [2012-08-01 21:12 +0200]: > The various postgresql-* packages are mostly plugins (PL/something) Right, postgresql-X.Y-foo are server-side plugins which are specific to a major PostgreSQL server version. They need to be versioned just like PostgreSQL itself for upgrades, parallel installability, etc. > which follow the example of postgresql-plperl-x.y (built from PG > core). For real applications like barman, that's not really > necessary. Where "real applications" == client-side PostgreSQL users, i. e. which only use libpq, not build against postgresql-server-dev-X.Y. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.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/20120801204318.gc2...@piware.de
Re: [Pkg-postgresql-public] postgresql-* package namespace (was: Re: Bug#683486: ITP: barman -- Backup and Recovery Manager for PostgreSQL)
I usually prefer packages to use the upstream name so they are easy to find (think other distributions). The various postgresql-* packages are mostly plugins (PL/something) which follow the example of postgresql-plperl-x.y (built from PG core). For real applications like barman, that's not really necessary. Also, by all means, do not rename existing packages.
postgresql-* package namespace (was: Re: Bug#683486: ITP: barman -- Backup and Recovery Manager for PostgreSQL)
On 08/01/2012 11:18 AM, Roger Leigh wrote: > On Wed, Aug 01, 2012 at 09:56:56AM +0200, Marco Nenciarini wrote: >> >> * Package name: barman > > postgresql-barman would make it a bit easier for people to find. > Most of the other postgreql packages use the postgresql- namespace. The postgresql-* namespace doesn't seem to be used in a consistent way: we have packages like postgresql-9.1-debversion, but also packages such as postgresql-plperl-9.1. And then there is one package which uses a totally different scheme (libpgsql-9.1-asn1oid). It would be nice if all packages could use the same scheme, maybe starting with the packages for 9.2? As I have no preference myself, maybe the postgres maintainers could give their view? Ansgar -- 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/5018fcb8.2030...@debian.org
Re: Bug#683486: ITP: barman -- Backup and Recovery Manager for PostgreSQL
On Wed, Aug 01, 2012 at 09:56:56AM +0200, Marco Nenciarini wrote: > > * Package name: barman postgresql-barman would make it a bit easier for people to find. Most of the other postgreql packages use the postgresql- namespace. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- 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/20120801091825.go25...@codelibre.net
Bug#683486: ITP: barman -- Backup and Recovery Manager for PostgreSQL
Package: wnpp Severity: wishlist Owner: Marco Nenciarini * Package name: barman Version : 1.0.0 Upstream Author : 2ndQuadrant Italia (Devise.IT S.r.l.) * URL : http://www.pgbarman.org/ * License : GPL Programming Lang: Python Description : Backup and Recovery Manager for PostgreSQL Barman (backup and recovery manager) is an administration tool for disaster recovery of PostgreSQL servers written in Python. It allows to perform remote backups of multiple servers in business critical environments and help DBAs during the recovery phase. Barman's most wanted features include backup catalogs, retention policies, remote recovery, archiving and compression of WAL files and backups. Barman is written and maintained by PostgreSQL professionals 2ndQuadrant. -- 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/20120801075656.ga6...@greygoo.devise-it.lan
