Re: Notice with dbconfig-common
Hi Nicolas, On Sun, Nov 20, 2011 at 10:59:22PM +0100, Nicolas wrote: The message is : NOTICE: CREATE TABLE / PRIMARY KEY will create an implicit index ... I understand the message but I don't know how to fix it. For postgreSQL point of view it doesn't seems to be a problem and tables are created. Thanks in advance for any help. I suggest you take this to the dbconfig-common-devel list on alioth. It could be a bug in dbconfig-common, or in the packaging. So I suggest when you take it to the list, you include a link to the source pacakge, as well as console output during installation, after you export dbc_debug=1. sean -- 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/2022091244.ga29...@cobija.connexer.com
Re: Two groups of users, one distro in the middle
On Tue, Nov 15, 2011 at 03:33:02PM +0100, Gergely Nagy wrote: Furthermore, packages in Debian are - to the best of my knowledge - adapted already to use /usr/bin/nodejs, packages outside can still work unmodified, if the user makes a simple symlink. Document this, and all's well. I don't think the symlink is even necessary, and is probably a bad idea in case the other package providing node was installed. instead, ship the binary in /usr/lib/nodejs/node (or similar), and instruct users that if they need upstream compatibility, to simply export PATH=/usr/lib/nodejs:$PATH and problem solved, right? sean -- 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/2015152833.ga21...@cobija.connexer.com
Re: libpopt
Hiya, On Sat, Nov 05, 2011 at 07:00:58PM +0800, Paul Wise wrote: On Sat, Nov 5, 2011 at 6:45 PM, Elimar Riesebieter wrote: we have many packages which are build against popt. Some of them have included a bundled (inlined) verion of popt. But they are using Debian's libopt-dev like pkg-config. Sounds like a bunch of bugs to be filed and info to be added to the security team's embedded code copies document: Because it wasn't entirely clear here, I don't think it is a bug that the source packages contain actually the the code; it's only a bug if they actually use it in the building process. I don't think it's at all useful to contact upstreams about embedded copies of code, as long as it's possible to specify a systme-wide version at build-time. Everybody wins that way. Sean -- 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/2005120427.ga27...@cobija.connexer.com
Accepted php5 5.3.8.0-1 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 27 Oct 2011 17:17:02 +0200 Source: php5 Binary: php5 php5-common libapache2-mod-php5 libapache2-mod-php5filter php5-cgi php5-cli php5-fpm php5-dev php5-dbg php-pear php5-curl php5-enchant php5-gd php5-gmp php5-imap php5-interbase php5-intl php5-ldap php5-mcrypt php5-mysql php5-odbc php5-pgsql php5-pspell php5-recode php5-snmp php5-sqlite php5-sybase php5-tidy php5-xmlrpc php5-xsl Architecture: source amd64 all Version: 5.3.8.0-1 Distribution: unstable Urgency: low Maintainer: Debian PHP Maintainers pkg-php-ma...@lists.alioth.debian.org Changed-By: Sean Finney sean...@debian.org Description: libapache2-mod-php5 - server-side, HTML-embedded scripting language (Apache 2 module) libapache2-mod-php5filter - server-side, HTML-embedded scripting language (apache 2 filter mo php-pear - PEAR - PHP Extension and Application Repository php5 - server-side, HTML-embedded scripting language (metapackage) php5-cgi - server-side, HTML-embedded scripting language (CGI binary) php5-cli - command-line interpreter for the php5 scripting language php5-common - Common files for packages built from the php5 source php5-curl - CURL module for php5 php5-dbg - Debug symbols for PHP5 php5-dev - Files for PHP5 module development php5-enchant - Enchant module for php5 php5-fpm - server-side, HTML-embedded scripting language (FPM-CGI binary) php5-gd- GD module for php5 php5-gmp - GMP module for php5 php5-imap - IMAP module for php5 php5-interbase - interbase/firebird module for php5 php5-intl - internationalisation module for php5 php5-ldap - LDAP module for php5 php5-mcrypt - MCrypt module for php5 php5-mysql - MySQL module for php5 php5-odbc - ODBC module for php5 php5-pgsql - PostgreSQL module for php5 php5-pspell - pspell module for php5 php5-recode - recode module for php5 php5-snmp - SNMP module for php5 php5-sqlite - SQLite module for php5 php5-sybase - Sybase / MS SQL Server module for php5 php5-tidy - tidy module for php5 php5-xmlrpc - XML-RPC module for php5 php5-xsl - XSL module for php5 Changes: php5 (5.3.8.0-1) unstable; urgency=low . * Re-re-imported upstream version 5.3.8, as a new sourceful update, in order to prevent the package from remaining as a native package. Checksums-Sha1: 920b83d87a42718b94f0be34c225175003bfad4d 3544 php5_5.3.8.0-1.dsc 0ad1bcbfed0142d1722ec203e26cb10ef524c704 14789551 php5_5.3.8.0.orig.tar.gz 5692673f1713d4df6f79500c172b47e6830b299d 191392 php5_5.3.8.0-1.diff.gz 460c225c4acd4eea4b9f02ae50411a3edd22bccc 557674 php5-common_5.3.8.0-1_amd64.deb fd3fc6f1379870896d78fe79e252cb7d2b353f65 3066130 libapache2-mod-php5_5.3.8.0-1_amd64.deb 487c83cb9ad0db0795b25642367ec1a8982172b1 3064796 libapache2-mod-php5filter_5.3.8.0-1_amd64.deb 4e9c8621d483364732bd17b99b0c5bb200fe6fa5 5958146 php5-cgi_5.3.8.0-1_amd64.deb 2d419de30a56f8736fefa75bdd48715f80ce9de4 2974950 php5-cli_5.3.8.0-1_amd64.deb ee03145c01a493aed76b2af0262d955a968b63f4 3013580 php5-fpm_5.3.8.0-1_amd64.deb b6fcb4ad503d364040d4f4f5cbc8fdb0c2731126 412088 php5-dev_5.3.8.0-1_amd64.deb d62900dc587918f8d763ca0be1e2ffe12a2b5a97 12890646 php5-dbg_5.3.8.0-1_amd64.deb 69710d8cd1c2608be3b7a326498d86180faab66a 27548 php5-curl_5.3.8.0-1_amd64.deb 63e65441bfc82b5d3ab1680f853f2b54e1976d77 9138 php5-enchant_5.3.8.0-1_amd64.deb 4d0c767b84efef9c8c89a4ef811ce7a71d34512f 39444 php5-gd_5.3.8.0-1_amd64.deb 7f16da306a6a457902d8f5db626607fbe76b44cc 16660 php5-gmp_5.3.8.0-1_amd64.deb 514edfe90d056fe35b8f5f62d07fc4b983dd6b26 35122 php5-imap_5.3.8.0-1_amd64.deb e743cbba8b15031873757f39aa4c5164fb60fc2c 49246 php5-interbase_5.3.8.0-1_amd64.deb a610905dc57b6c41e6a6c537173d730f3329cdc2 60864 php5-intl_5.3.8.0-1_amd64.deb e991960062ef146447981ee67151dafe27ee9a88 19798 php5-ldap_5.3.8.0-1_amd64.deb a7519626057179dcad544a287db89b400f8dfa3b 15322 php5-mcrypt_5.3.8.0-1_amd64.deb 7fc9c4b83df165ce47b35d5b439109f638e3629b 78162 php5-mysql_5.3.8.0-1_amd64.deb 10b0562b2423d1a291aeba95ab56e8fe39cae163 36244 php5-odbc_5.3.8.0-1_amd64.deb c3cc25de0285ec7a8c4f38e35abfd1972c4b6fcf 59730 php5-pgsql_5.3.8.0-1_amd64.deb 36bdffd882adfbeb0c4b3aa8cbc6fb0828648f19 8430 php5-pspell_5.3.8.0-1_amd64.deb fa3f7690a69d771ad8c802f9bcc58b379b325dd4 4354 php5-recode_5.3.8.0-1_amd64.deb a4607e82da9f54bf1bfbcde96b465a4f9ce1ba70 11166 php5-snmp_5.3.8.0-1_amd64.deb 4603e7c2389c714589560c8aa9f945dc12357815 56634 php5-sqlite_5.3.8.0-1_amd64.deb 8b732d56ed8823e2d66f7df8965592e8979ee0b2 26950 php5-sybase_5.3.8.0-1_amd64.deb 7c2cd941b6b5cccf36334b6356a95e4d54cdbc7f 18496 php5-tidy_5.3.8.0-1_amd64.deb 411b8309ed54a26342b52cb6fa22214457745b1d 35356 php5-xmlrpc_5.3.8.0-1_amd64.deb b628b465713332bc1268189db8c25cd3b444dcad 13718 php5-xsl_5.3.8.0-1_amd64.deb d251802705ff238ebaaf1c81a11d3b6047a46dcd 1058 php5_5.3.8.0-1_all.deb 1adf1490ab2b2f7ed4cb908878278f927191d0ae 370802 php-pear_5.3.8.0-1_all.deb Checksums-Sha256
Re: Announcing derivatives patches and call for help and feedback
hiya, On Tue, Oct 25, 2011 at 03:50:07PM +0800, Paul Wise wrote: For the presentation side of things I am thinking one approach might be to move UbuntuDiff[8] to the QA infrastructure, generalise it and enhance it for this purpose. This will necessarily include mechanisms to mark patches as having been dealt with or ignorable. I think it's also worth some consideration about if/how it could be integrated with the Debian patch-tracker service (or perhaps supercede said service if it made more sense). Without thinking super hard on it it seems like it could have some nice effects on cross-distro participation by giving an extra incentive to share/markup patches, and to a lesser extent even the same source packages. Just thought I'd throw that in there anyway... sean -- 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/20111025085844.ga16...@cobija.connexer.com
Accepted compiz 0.8.4-5 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 25 Oct 2011 20:50:05 +0200 Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-gnome compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all amd64 Version: 0.8.4-5 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz - OpenGL window and compositing manager compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files Closes: 554114 617763 631129 639681 Changes: compiz (0.8.4-5) unstable; urgency=low . [ Sean Finney ] * Update gbp.conf for new debian-wheezy branch * Rebuild of the package should fix remaining libmetacity-private issues. (Closes: #617763) * Add dependency on libcompizconfig0 to compiz metapackage. Thanks to Patricio Rojo s...@wasabi.das.uchile.cl (Closes: #631129) . [ Michael Biebl ] * Link against all necessary libraries. (Closes: #639681, #554114) Thanks: Loïc Minier loic.min...@ubuntu.com Checksums-Sha1: 2b91a4c4773e7261576d47c9404e16406157603f 2353 compiz_0.8.4-5.dsc d3ebafd12b7a9e304b4de763eaa7b73b1f063774 30768 compiz_0.8.4-5.diff.gz cdc1cdedf45190633df756e6c59aceea7787c18e 29810 compiz_0.8.4-5_all.deb f149e4050299a2f32b04ec4aed279f8da54898e8 1103938 compiz-core_0.8.4-5_amd64.deb 6082f39000de0e93b5cd1c79696dc7f0534c0dff 58892 compiz-dev_0.8.4-5_amd64.deb e8b2346f94e4339b320e224de14f6b522eb91421 92394 compiz-gtk_0.8.4-5_amd64.deb c3ea3d1a1c1e3eac8da9b4972024ad0601caaad0 100496 compiz-kde_0.8.4-5_amd64.deb 8246cc35a62c926dc89d46d7290d4bea8251b6ad 41476 compiz-gnome_0.8.4-5_amd64.deb 9a98127715bb176ab4d4cae4bfbd5888f4f69bfc 538338 compiz-plugins_0.8.4-5_amd64.deb fb74a81c5924c29322321acd41410b96b092e51e 49998 libdecoration0_0.8.4-5_amd64.deb 8750defbfbff5b55a8e0d44b789c3cca9e85c39b 38174 libdecoration0-dev_0.8.4-5_amd64.deb Checksums-Sha256: 9797efa16a087ef633a6abe94fb2f1caead75b15c56676b52d884c4e23de55e2 2353 compiz_0.8.4-5.dsc 3fa8979b2155c00ffd70a0e4bc7e4a1395c3e475a5e12f294bdfd99daf9ab093 30768 compiz_0.8.4-5.diff.gz e70377614501f5b3cf127c624cd3bb60ec6fc7c0c245bea86c7d3d69a4a728cc 29810 compiz_0.8.4-5_all.deb 3dc294fe861340662bce47be52d7b9833d308fb98d4149420699033d66eabc38 1103938 compiz-core_0.8.4-5_amd64.deb aee2b0c5f97c22176fbb8ca10866dd48a69578a7846155030be5299a5312b1c3 58892 compiz-dev_0.8.4-5_amd64.deb f247b0d7a2831a4c08d4b25342b03a8cf57dd462d0e1451604061aab4ec9bd0a 92394 compiz-gtk_0.8.4-5_amd64.deb 5dabe0517f4f9d1c9ad7ba2aed97b9c7bc8bbf28ed7488a25c4911815df94f73 100496 compiz-kde_0.8.4-5_amd64.deb f013a88dc81c238a703394d643473ca6bfd275445999f4760a82bbdbaf5b05ba 41476 compiz-gnome_0.8.4-5_amd64.deb 139b5b2ff569242b27fafc1b146e5128b3ddd04929226f7924de25528f1e78e4 538338 compiz-plugins_0.8.4-5_amd64.deb b54268abfe73a5db3f46532a99adda2446f53281dd755196532ce2f9e346bcb0 49998 libdecoration0_0.8.4-5_amd64.deb d8309b8b4d73f8504c0c9f5c8a1fc9a86b434c400f8c8386699eb185b712de0e 38174 libdecoration0-dev_0.8.4-5_amd64.deb Files: 20f3988c6d726702f853e0c8063548dd 2353 x11 optional compiz_0.8.4-5.dsc 82250c2ac556d65d75c7bcd8325cfb1e 30768 x11 optional compiz_0.8.4-5.diff.gz ccbda5a26ad87c81b0570ae87261acc5 29810 x11 optional compiz_0.8.4-5_all.deb e7f4059e62e3de53966c9dfb6eda8873 1103938 x11 optional compiz-core_0.8.4-5_amd64.deb 67d146ddeba13b2a3b5c9c7051018c91 58892 x11 optional compiz-dev_0.8.4-5_amd64.deb 497f367ea21fd7f6f1a169b1f0436c75 92394 x11 optional compiz-gtk_0.8.4-5_amd64.deb 106464e5149c471a3b1971681fa0fed8 100496 x11 optional compiz-kde_0.8.4-5_amd64.deb a4573e0a1f1774bf9e0429dec0ce2835 41476 x11 optional compiz-gnome_0.8.4-5_amd64.deb 5def1ad722e0504d9dd0e4f3d3f6d67f 538338 x11 optional compiz-plugins_0.8.4-5_amd64.deb ed9e8b47f9b93b684ec6c746f477d560 49998 x11 optional libdecoration0_0.8.4-5_amd64.deb b2db4cca12daf7b8b9332708baa43bae 38174 libdevel optional libdecoration0-dev_0.8.4-5_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk6nDrcACgkQynjLPm522B0mIQCdG2BJOibnUhpibl1I4wFMCR4L 5+AAn2znfuSBfEgs7fyMD7d9vT3og9Mm =2SYq -END PGP SIGNATURE- Accepted: compiz-core_0.8.4-5_amd64.deb to main/c/compiz/compiz-core_0.8.4-5_amd64.deb compiz-dev_0.8.4-5_amd64.deb to main/c/compiz/compiz-dev_0.8.4-5_amd64.deb compiz-gnome_0.8.4-5_amd64.deb to main/c/compiz/compiz-gnome_0.8.4-5_amd64.deb compiz-gtk_0.8.4-5_amd64.deb to main/c/compiz
Re: load of apache module for a package
hi olivier, On Mon, Sep 19, 2011 at 10:38:22AM +0200, olivier sallou wrote: Hi, I need some apache modules for a package. Should I use a2enmod in postinst script, or, is there any debhelper/deb file way to do it? i don't know of any helper utilities for this, so you might need to do this yourself. i would suggest only doing it for new installs though, and not upgrades, so that you do not give the admin a bad surprise by re-enabling the module if they have manually disabled it. sean -- -- 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/20110919085337.ga12...@cobija.connexer.com
Re: how to handle *.ucf files in /etc/apache2/conf.d?
On Fri, Sep 16, 2011 at 08:38:37AM +0200, Heiko Schlittermann wrote: a) having apache to ignore *.ucf* generally b) just change in /etc/apache2/apache2.conf include conf.d/ into include conf.d/*.conf and ask all packages placing files there to use the .conf extension? I personally have been wishing for (b) for several years, but haven't wanted it bad enough to go kick the hornets' nest :) sean -- 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/20110916122619.ga28...@cobija.connexer.com
Re: Mistake in postrm preventing functioning of newer package (stable/testing/unstable)
On Fri, Sep 09, 2011 at 11:37:41AM +0200, David Paleino wrote: I just wanted to (try to) fix it for the biggest number of people possible. Maybe I'll just leave stable as-is, and try the solution I described within testing/unstable :/ Another option, as awful as it sounds, is to nuke (or surgically modify) the postrm script of the old package from the preinst of the new package. You would need to support that until the current stable was rotated out through oldstable. Yes, awful. But I've seen it done before... sean -- 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/20110909104211.ga18...@cobija.connexer.com
Re: How to close bug #620550?
On Mon, Aug 08, 2011 at 01:58:27PM +0100, Ian Jackson wrote: Keith Lawson writes (How to close bug #620550?): 2. Unless someone knows why PHP is using qdbm, it should IMO be switched back to gdbm. This is not RC I think. I refer you, good sir, to the fine changelog for reference: php5 (5.1.6-4) unstable; urgency=high [sean finney] * no longer build against GPL'd gdbm library (closes: #390452). -- 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/20110808143140.ga25...@cobija.connexer.com
Accepted xmlrpc-c 1.16.33-3 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 07 Jul 2011 22:09:34 +0200 Source: xmlrpc-c Binary: libxmlrpc-c++4-dev libxmlrpc-c++4 libxmlrpc-c3-dev libxmlrpc-core-c3-dev libxmlrpc-core-c3 xmlrpc-api-utils Architecture: source i386 Version: 1.16.33-3 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: libxmlrpc-c++4 - A lightweight RPC library based on XML and HTTP [C++ libraries] libxmlrpc-c++4-dev - A lightweight RPC library based on XML and HTTP [C++ libraries] libxmlrpc-c3-dev - A lightweight RPC library based on XML and HTTP [C libraries] libxmlrpc-core-c3 - A lightweight RPC library based on XML and HTTP [C libraries] libxmlrpc-core-c3-dev - A lightweight RPC library based on XML and HTTP [C libraries] xmlrpc-api-utils - Generate C++ wrapper classes for XML-RPC servers Closes: 614937 Changes: xmlrpc-c (1.16.33-3) unstable; urgency=low . * Add patch to fix FTBFS on hurd-i386. Thanks to Pino Toscano toscano.p...@tiscali.it (Closes: #614937) * ACK NMU for #560942. Thanks, Moritz. * Replace Suggests: xml-rpc-api2cpp/xml-rpc-api2txt with xmlrpc-api-utils * Update gbp.conf to indicate we are using pristine-tar in the git repo Checksums-Sha1: e11381296a6301044ae8747d5bcb48ae40e8d52b 1176 xmlrpc-c_1.16.33-3.dsc cf4664ec5c453bddc273f6651a915a16c81b231a 8711 xmlrpc-c_1.16.33-3.diff.gz df2fb3e31e6e0094bb5841d8ddce3d8b38129bb7 186136 libxmlrpc-c++4-dev_1.16.33-3_i386.deb 1b5eddbb866d5325359c13b6e6e7ce901a856b3d 148858 libxmlrpc-c++4_1.16.33-3_i386.deb 82ad7c3cb57660a304a0e9032d7ee26ef6123025 6724 libxmlrpc-c3-dev_1.16.33-3_i386.deb 0ad0dfb027664a88b39ee31589b5b3f9ccc3af74 274816 libxmlrpc-core-c3-dev_1.16.33-3_i386.deb 4bc5da29312bdb067859d9ea4d21c399ac13c666 179618 libxmlrpc-core-c3_1.16.33-3_i386.deb ae980e0a8f2ecbc7d0ca1348c979334453022e6c 31992 xmlrpc-api-utils_1.16.33-3_i386.deb Checksums-Sha256: 8f511e80f076f57b11aa1bdce5378fd508b73a2d85ec84555dcf3e6611084915 1176 xmlrpc-c_1.16.33-3.dsc be732aae87facff96075c1f2b8e0d4ffcb6dd04f13ec6c1b2193d9ed02e3d183 8711 xmlrpc-c_1.16.33-3.diff.gz ce036f87477e7014e61ded76744411ebe593d94a76fa7e280c8bdc7dc742a89f 186136 libxmlrpc-c++4-dev_1.16.33-3_i386.deb 37d3b832634276dfaf5850a2223cd84b5b009a273cfee60a9d246b6a366870bd 148858 libxmlrpc-c++4_1.16.33-3_i386.deb e5e73fd95006cc5f5328e961a86692259388363c20fff3f2f2900795a26ca52b 6724 libxmlrpc-c3-dev_1.16.33-3_i386.deb c69843dac7c6aa830c050fa1b3b2723d1190981dc67ac6b99cb360a13c634634 274816 libxmlrpc-core-c3-dev_1.16.33-3_i386.deb 522a6e43c41ccb8b986d85116428811f1ae2ddf300a02f035b33c2d4cb861f3c 179618 libxmlrpc-core-c3_1.16.33-3_i386.deb 0f036c108525e9cc9b347713f18fcfff9583dae9e7e8cc2765c0aa1f6bef2574 31992 xmlrpc-api-utils_1.16.33-3_i386.deb Files: 768b66c41f19c15c5cd7bb945522708d 1176 libs optional xmlrpc-c_1.16.33-3.dsc 0e5ba65b966bed596902aa70fa2bb491 8711 libs optional xmlrpc-c_1.16.33-3.diff.gz ef2bbb89814f87dc4e58ad5956e4b14a 186136 libdevel optional libxmlrpc-c++4-dev_1.16.33-3_i386.deb 77ecf333ba6033ac1620776ceed81ae0 148858 libs optional libxmlrpc-c++4_1.16.33-3_i386.deb 2a9089d7f73cb1aaa3cec6119bc45695 6724 libdevel optional libxmlrpc-c3-dev_1.16.33-3_i386.deb 948b5fb3536b5482fee02b6508390a9e 274816 libdevel optional libxmlrpc-core-c3-dev_1.16.33-3_i386.deb b294757e5b750c7d6d2458e89944b995 179618 libs optional libxmlrpc-core-c3_1.16.33-3_i386.deb ebd058fc34566b3dfbe29ae3859cc90c 31992 devel optional xmlrpc-api-utils_1.16.33-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk4WEzUACgkQynjLPm522B0ZywCdGeE4Y5sqIBSRNbhKG82Ctk+W 8UAAn1op3N3o2f1/445cXwuG5g833+D7 =PeLI -END PGP SIGNATURE- Accepted: libxmlrpc-c++4-dev_1.16.33-3_i386.deb to main/x/xmlrpc-c/libxmlrpc-c++4-dev_1.16.33-3_i386.deb libxmlrpc-c++4_1.16.33-3_i386.deb to main/x/xmlrpc-c/libxmlrpc-c++4_1.16.33-3_i386.deb libxmlrpc-c3-dev_1.16.33-3_i386.deb to main/x/xmlrpc-c/libxmlrpc-c3-dev_1.16.33-3_i386.deb libxmlrpc-core-c3-dev_1.16.33-3_i386.deb to main/x/xmlrpc-c/libxmlrpc-core-c3-dev_1.16.33-3_i386.deb libxmlrpc-core-c3_1.16.33-3_i386.deb to main/x/xmlrpc-c/libxmlrpc-core-c3_1.16.33-3_i386.deb xmlrpc-api-utils_1.16.33-3_i386.deb to main/x/xmlrpc-c/xmlrpc-api-utils_1.16.33-3_i386.deb xmlrpc-c_1.16.33-3.diff.gz to main/x/xmlrpc-c/xmlrpc-c_1.16.33-3.diff.gz xmlrpc-c_1.16.33-3.dsc to main/x/xmlrpc-c/xmlrpc-c_1.16.33-3.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1qevwh-6n...@franck.debian.org
Re: Behaviour of dpkg-source with 3.0 (quilt) and VCS and automatic patches
On Wed, Jun 01, 2011 at 02:39:42PM +0200, Goswin von Brederlow wrote: And note that as maintainer or for the VCS copy you can allways configure debian/soruce/local-options to unapply patches if you so desire. This is something i've been doing quite happily and I think it is a pretty decent compromise for the user/maintainer use cases. If you're building from the VCS there may be a difference in behavior, but if you build a downloaded source package (or even a source package generated from the VCS), the behavior is consistant. sean -- 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/20110601142659.gb...@cobija.connexer.com
Re: bug reporting workflow is outdated
On Mon, May 23, 2011 at 01:47:22AM +0200, Goswin von Brederlow wrote: I suggest that we can make an HTTP based bug reporting method. The only advantage of this would be for systems that firewall outgoing mail conections but allow http or have a http proxy but no smarthost. and that's a pretty big advantage. requiring that submissions be done only via SMTP seems a bit silly and self-limiting if you ask me. HTTP would be able to provide a super-set of the features of SMTP submission, would not prevent SMTP submission from remaining as an option, and is more likely to work in diverse environments. sean -- 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/20110523071056.ga17...@cobija.connexer.com
Re: A concrete proposal for rolling implementation
Hi Teodor/Bruce, On Mon, May 09, 2011 at 05:48:25PM +0300, Teodor MICU wrote: I've been disappointed at first to read that so many approve this rolling implementation that in fact is just c-u-t, constantly usable testing [1]! Outside of the freeze period it doesn't really matter and one can say rolling==cut. On Mon, May 09, 2011 at 11:36:04AM -0600, Bruce Sass wrote: On May 9, 2011 08:48:25 am Teodor MICU wrote: To conclude, unstable-next suite (or some other name [2]) is a requirement for rolling [3]. ...unless the nature of experimental is changed, and its current function replaced with PPA's? DEP-10 is focused entirely on how we can avoid and/or circumvent the freeze process (for things not concerning the next stable release), which is helpful by itself but also a key part of a working rolling release, I'd say. I'm trying to cover most of the ideas discussed in the previous mega-thread for how this could be done, including both of the unstable-updates and the PPA's approach, and maybe a couple more. I'm still putting meat onto the document but in the next couple days I'll bring it back on list for a more thorough discussion. So please keep any ideas you have about either of these approaches readily available :) sean -- 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/20110510055244.ga21...@cobija.connexer.com
Re: glibc: causes segfault in Xorg
Hi, On Wed, May 04, 2011 at 10:56:27PM -0500, Steve M. Robbins wrote: And furthermore, even if Debian chooses to fix this, upstreams will be forced to eventually cater to the default glibc behavior for every other libc distro out there that does not have their own fix (and non-libc OS's where this behavior already exists), That's fine: let others be the guinea pigs, then introduce the optimized memcpy later when the rest of the world has adapted. I hope the glibc maintainer does not share this view, then. If we were in the midst of preparing a release, I'd agree and argue that such a change shouldn't happen, because of the risk of regression, but otherwise the whole point of testing/unstable is to find these types of things and get them fixed before the next release. so gains would be potentially limited. For me, having a working system would be a great gain! As would be with getting the buggy applications fixed. My guess is that the glibc upstream would side for the latter of these two, and I don't think it's unreasonable that the debian maintainer might decide to follow suit, since the buggy applications will be (eventually) caught and fixed. That said, regressions do suck, especially when they take the form of heisenbugs. But one could easily hack something LD_PRELOAD'able check for stuff like this without forcing a global change. Sounds interesting. What do you have in mind? The same types of hacks used to find other nonstandard or undefined behavior (à la valgrind). Simply override the problematic function with your own via an LD_PRELOAD'd shared library. Proof of concept: me@host:~/debug-memcpy$ ./test_memcpy before: hhh after: hhh me@host:~/debug-memcpy$ env LD_PRELOAD=./memcpy.so ./test_memcpy before: hhh Error: memcpy used on overlapping regions Aborted me@host:~/debug-memcpy$ env MEMCPY=warn LD_PRELOAD=./memcpy.so ./test_memcpy before: hhh Warning: memcpy used on overlapping regions after: hhh me@host:~/debug-memcpy$ env MEMCPY=safe LD_PRELOAD=./memcpy.so ./test_memcpy before: hhh after: hhh The first case above illustrates the undefined behavior which might crash, the remaining two show using an LD_PRELOADED version of memcpy with the checks to override the behavior. I put a tarball up on http://seanius.net/tmp/debug-memcpy.tgz if you want to check it out, it's maybe a dozen lines of actual code. Note that I haven't tested the bounds checking corner cases for 100% accuracy. If you were running something super critical on testing, like a mars rover or a robot that does brain surgery, you could install this system-wide and hack the default action, and then you get your stability back. Otherwise, I'd think taking the default glibc behavior and using something like this as one of several debugging tools when the heisenbugs pop up would be pretty reasonable. Maybe valgrind already does checks like this, but if not, I imagine that it wouldn't be too hard to add the same check there. sean -- -- 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/20110505075603.ga6...@cobija.connexer.com
Re: glibc: causes segfault in Xorg
On Wed, May 04, 2011 at 12:29:50PM +0200, Julien BLACHE wrote: Steve M. Robbins st...@sumost.ca wrote: Hi, I'm with Linus on this: let's just revert to the old behaviour. A tiny amount of clock cycles saved isn't worth the instability. Tiny amount?! The optimized memcpy() variants that break shitty code bring a 4 to 5x speedup on the processors they've been written for! And furthermore, even if Debian chooses to fix this, upstreams will be forced to eventually cater to the default glibc behavior for every other libc distro out there that does not have their own fix (and non-libc OS's where this behavior already exists), so gains would be potentially limited. That said, regressions do suck, especially when they take the form of heisenbugs. But one could easily hack something LD_PRELOAD'able check for stuff like this without forcing a global change. my 0.02 $LC_MONETARY anyway, sean -- 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/20110504113415.gb2...@cobija.connexer.com
Re: A concrete proposal for rolling implementation
Hiya, On Wed, May 04, 2011 at 10:25:35PM +0200, Stefano Zacchiroli wrote: On Wed, May 04, 2011 at 02:24:12PM +0200, Josselin Mouette wrote: What to do during freezes - If we want to do something different though, there is a simple recipe: allow packages to be picked up from unstable, but also from experimental. Yes, absolutely. This seems straightforward, elegant, and useful as it encourages maintainer to push their changes to the Debian archive and make them visible and testable to rolling users, even when unstable is de facto closed. It's an excellent idea. Some of the initial feedback that I've gotten about DEP-10 (in particular some brainstorming on IRC with Carsten Hey) is pointing at ideas along these lines, and I hope to flush them out in a bit more detail RSN. But I think it's particularly exciting that these two ideas (rolling, and dealing with freezes) might not conflict with each other, and perhaps complement one another. One issue that would need to be addressed with experimental is that opening a migration route anywhere out of experimental might come as an unpleasant surprise to some, since there's a standing expectation that it's a pseudo-suite where we can put stuff that we don't necessarily want to try out in unstable. Not an insurmountable problem (either we change that or introduce yet another psuedo-suite for this purpose), but worth note anyway. sean -- 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/20110504214045.ga4...@cobija.connexer.com
Re: Debian rolling: tentative summary
Hi Lucas, I appreciate your effort to try and sum things up. However, I'd like to raise the point that the discussion was about more than just having a rolling and user-oriented testing release. The feedback that started (or at least helped springboard) this massive thread was that when we're releasing, everything else grinds to a halt, maybe it doesn't need to, followed by pondering whether there was a better way to manage this. My initial proposal apparently smelled a bit like rolling, which got out people from both the pro- and con- rolling camps, and unfortunately it seems that a good deal of the discussion ended up splintering off in that direction. While rolling may be one[1] way of addressing the freeze blockage, it's most likely not the only way to do so. Over the weekend I took out a DEP to try and examine this underlying issue from a few different angles, including ideas that are rolling-like as well as aproaches that may be less so. sean [1] or, several, really, since there isn't just a single concrete rolling implementation being proposed. -- 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/20110503113858.ga28...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
Hi Carsten, A bit late on responding to your mails, but... On Mon, May 02, 2011 at 01:56:14AM +0200, Carsten Hey wrote: So if we tell users to use this repository, we're going to have some users (I upgrade my servers to testing during the freeze and I would enable it if it was generally advised for beta-testers). The libpam-mount example was not a 100% fit because it went through testing-security and not through t-p-a. The segfaulting package migrated to testing on the 28th of November 2008. Just five months earlier the Testing Security team announced[1] on d-d-a that they provide nearly full security support (the kernel was missing at this time). I'd say it's a very good fit for describing the type of problem; even if it was t-s vs t-p-u, it's the same problem in terms of testing coverage. Especially with software that's used in a wide variety of configurations and environments, even what is seen as thorough review/testing on the part of the maintainer could miss stuff like this. I doubt that generally advising to add t-p-a would significantly work out better than the testing-security announcement. I'm thinking more and more that if we did do the branch testing approach, it would need to be in tandem with changes to default installation settings, release upgrade procedures, etc, to get more people on board by default. That said, I also think your discussion/suggestions regarding unstable-p-u are really good. While it may not necessarily solve the rolling needs, it could solve the non-release standstill issue by providing something more useful than experimental. As you might or might not know, I took out DEP-10 over the weekend, to explore different ways that we could parallelize the release management, and plan to explore the details/problems/benefits of both of these ideas (branch testing / unstable-p-u). It would be awesome if I could get some feedback/help from you along these lines. sean -- 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/20110503120855.gb28...@cobija.connexer.com
Re: Debian rolling: tentative summary
Hi Lucas, On Tue, May 03, 2011 at 02:59:04PM +0200, Lucas Nussbaum wrote: I think that one of the conclusions of the discussion from the last few days is that the freeze blockage has very good features that many of us are not willing to give up, like the ability to focus the DDs on working on stable releases. I do not think there was any such consensus. There were people who voiced valid concerns about this, and I believe there were also people who provided counter arguments. I do not recall any kind of consensus, or even choosing camps on this issue beyond that, just that the thread drifted away in another direction. ISTR even seeing some hard data[1] floating around about a declining number distinct contributions as the freeze progressed, which would weigh pretty heavily against any argument about focusing DD's[2]. DEP-10, while being otherwise lacking in content, does describe this problem pretty well[3] as motivation for exploring changes to the release process. And beyond that, how does the exact same argument *not* apply to rolling regarding DD time/focus? Anyway, if you want to focus solely on the rolling related stuff, that's fine. I don't really have a vested opinion on it one way or another, I just felt that your summary didn't have a full view of everything discussed in this massive thread. sean [1] I don't recall if it was in the thread or on IRC, but the data was taken from -changes/BTS statistics during the release process. [2] That is to say, having a restriction that you can only do foo, especially in a volunteer project doesn't necessarily guarantee that significantly more people will help with doing foo than would otherwise. [3] http://dep.debian.net/deps/dep10/ -- 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/20110503172100.gb30...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
Hi Ste(ve|fano), On Sun, May 01, 2011 at 12:02:47PM -0700, Steve Langasek wrote: On Sun, May 01, 2011 at 04:17:10PM +0200, Stefano Zacchiroli wrote: JFYI, Sean and Raphael have taken DEP number 10 They have? I haven't seen mail to debian-project about this, which is what http://dep.debian.net/deps/dep0/ requires? (The chance of a collision here is quite small of course, but I'm still confused how they have taken this number without following the procedure.) Mea culpa. I did not realize there was an official procedure for this, as I found and followed the howto[1] link from the main page on dep.d.n. I figured that it would be better to have some content in there before making any kind of announcement. I'll drop a line to -project as well as put something in the howto referencing the DEP-0 procedure. sean [1] http://dep.debian.net/depdn-howto/ -- 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/20110501212118.ga23...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
On Sun, May 01, 2011 at 11:17:21PM +0200, Pierre Habouzit wrote: The problem is, you need to entry points, one for testing as we know it, one for rolling. snip So basically you split our users in two non overlapping sets, meaning that you divide coverage and tests. How come is that in the distribution interest?! I think it's not, I think it's resource squandering. Yes, and it *will* split up users into two camps, just like any parallel system of development would. I don't think that's necessarily bad, since some users/developers would want to be split because of diverging interests anyway. The question is, can it be done in such a way as to keep the level of attention and QA that we want to have on the candidate releases while we're preparing them. I completely agree that it's a non-starter if we can't address that. So please, what is so useful and important that we wast our precious resources here, have two inconciliable Debians at once? Because users want it doesn't fly. I couldn't care less, I'm interested about *why* they want it, not the mere fact that they do. Because when you know why they want it, maybe there will be better answers that don't make releasing even more brittle and burn even more people out. As the release process drags on, non-release related activity decreases, which I'm suggesting has a detrimental effect on the project (including the *next* stable release to a certain extent) for a number of reasons previously outlined. If the union of people who are interested in using and/or contributing to the respective parts (stable prep vs unstable) is considerably larger than the intersection, then to me it makes a lot of sense to explore whether there's a better way we can serve both groups at the same time. sean -- 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/20110501224521.gc23...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
Hi! (accumulated replies FTW) On Fri, Apr 29, 2011 at 11:20:31PM +0200, Andreas Barth wrote: * unstable always feeds to testing * release N == testing, until the freeze. You know that we had once frozen, and have given up since as that didn't scale even back then? I think it has already been pointed out at some point that it's not a complete analog. Specifically (AIUI), way back then, frozen was basically a snapshot of unstable, with all the bugs problems, etc. Indeed, it was a large part of the motivation for having testing in the first place. What most of the proposals here are suggesting is that we have something similar, but based off of a testing snapshot instead. This concept needs double or tripple man power from what we currently have. That's the show-stopper. I don't totally agree with that estimate but as I've pointed out before it *will* be more work, just lke maintaining two branches in a VCS instead of one would be. Additionally, the proposal would suggest that: * much of the extra work could be done by the package maintainers themselves. * much of the additional overhead could be automated/scripted. Whether it actually *could* is of course another question, but that's why it's part of a hypothesis. On Fri, Apr 29, 2011 at 11:48:53PM +0200, Andreas Barth wrote: On the other hand, the entry barier into the release team isn't too high. If someone is willing to work e.g. only on encouraging packages fixing important bugs to testing faster, please get in contact with one of the release managers (or me), and we can certainly arrange something in the interesst of all. But just making more mess in testing for PR reasons doesn't sound like a good idea to me. I don't think it's for PR reasons. It's because currently, when Debian is in the middle of forming it's rock-solid stable release, EVERYTHING ELSE slows down too. When AJT introduced testing he referred to it as a sludgey alternative to frozen, but when the entire project is sludgey for extended periods of time, it affects the number of fun and innovative things happening in Debian. I'm a big proponent of the when it's ready camp, but also think we could come up with a way that lowers the collateral damage to other parts of the project. On Fri, Apr 29, 2011 at 11:22:54PM +0200, Andreas Barth wrote: I don't think the plan is straightforward, but just not working. It's easy to write down things that other people need to do - but that won't work. Please show the man power necessary to get your plan implemented - otherwise, all is moot. As I've said before, I'm willing to do more than throw popcorn from the armchair here :) My biggest hesitation for rolling up my sleeves and getting right at it is that I wasn't sure whether it would fall on deaf ears and be a collossal waste of time. And note that I'm not pinning waste of time to accept/reject for the proposal--I think this is a very intresting experiment, and regardless of the outcome we'd probaly walk away with some new ideas/tools/questions. To kinda put my money where my mouth is, I'd be willing to sign up as some kind of release assistant, helping with the current release processes while working on this proposal. On Fri, Apr 29, 2011 at 06:50:04PM -0400, Michael Gilbert wrote: Actions speak a whole lot loader than words and design by committee is unlikely to get you anywhere. And a GR (as mentioned in your blog So, really what I'm saying is just go for it. Prove that its something worthwhile so the project has a basis for adopting it. I think the best way forward at this point is something along those lines. I'll take out a DEP for starters, so we can have authoritative place with a project plan (i.e. not scattered across ML's and blog posts). sean -- -- 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/20110430072644.ga15...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
Hi Andreas, On Sat, Apr 30, 2011 at 08:29:22PM +0200, Andreas Barth wrote: But one can't expect that it's enough to say great idea, but someone else will do it. If someone wants to setup rolling.d.n, fine. I'm happy to help setting up britney, release foo, whatever. But someone has to take responsibility, and not just make it a fire and forget thing. In case I wasn't totally clear, or it got lost in the noise, etc, in 20110430072644.ga15...@cobija.connexer.com I tried to (again) make it clear that I actually am going to chip in on this. Raphaël has also said that he'd be able to help up the services (which is good, because I'm totally unfamiliar with most of them). I also volunteered to join up as an assistant/lackey with the release team under the *current* process, since that would be good for me to get some first-hand experience, and hey, some extra free labor for you guys :) I think the goal would be to set something up, show that it works for all the strange/difficult transitions/corner-casees, demo the whole process with some fake releases, etc. And even better, since the whole point is to have a system that works with an unfrozen testing, we will have a real live unstable/testing that will be paying no attention to our efforts, so we shoudl get a very good idea of how fast things would diverge, and how difficult cross-porting/cherry-picking/etc would be. If someone wants to setup rolling.d.n, do it. If not, then don't. But that's it. I think this will happen in some short time. Gonna put a little more time/effort into the proposal first though (DEP-10, coming soon to a dep.debian.net near you). sean -- 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/20110430195557.ga17...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
Hi Neil, On Sat, Apr 30, 2011 at 08:48:24PM +0100, Neil McGovern wrote: Indeed. Personally, I believe it would also be unreasonable to ask DDs, and indeed the release, security, and FTP teams to support testing and rolling. Especially before it has been proven to be negligible extra effort. Indeed. I'd hope that we could put something together that people would *want* to adopt. I totally get that the RM team is skeptical. A complete aside: I have yet to see DEPs being anything but a structured way to bikeshed. However, if you wish to go down this route, feel free. This does bring me full circle back to the start of my mail - if you want to push this, that's fine. But please don't try and make extra work for others. While just about any technical discussion on -devel will have its tangents and its non sequitors, I think we *have* had some good stuff come out of the DEP's, so I disagree there. For example, DEP-3 and DEP-5 have (indeed, after quite a bit of bikeshedding) resulted in some nice pseudo-standards that are gaining increasing traction/usage. And even the DEP's that are REJECTED will stand as documentation of something that someone tried once, and maybe didn't work out for some reason, and could serve as a basis for ideas later on, which is an order of magnitude better than an infrequently recurring ML thread where everyone forgots all the gotchas and details from the last time it was discussed n months ago. sean -- 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/20110430201149.gb17...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
Hi guys, On Wed, Apr 27, 2011 at 08:23:33PM +, Philipp Kern wrote: * RM's can still choose to migrate packages from (not frozen) testing as long as it's practical to do so. * When deps/transitions/etc prevent testing migration, release N proposed updates is used for one-off bin-NMU's and/or sourceful backports. So this requires people to coordinate and finish transitions in parallel to a massive load of patch review. And even better we can't even cherry-pick from unstable or testing anymore because it got broken through transitions. binNMUs It does introduce problems, yes, but any parallel solution will. However I think having a release N p-u available for maintainer uploads will also make it easier to distribute the load away from the RM's and back to the maintainers. are even more fun because then your version in release N proposed updates is higher than what's in new testing, which means that it should be propagated from p-u to testing which breaks because it would miss the libraries for which it got binNMUed in the first place. Which means in turn that you need to binNMU into release N p-u and binNMU again with a higher version into testing. Ugly, yes, but I don't think it would be impossible to abstract away any new manual overhead with some scripting (i.e. have a script that prepares both binNMU's) We would also probaly want to have some kinda early-warning system to catch cases where manual RM/maintainer error has introduced this versioning problem, but that ought not to be too difficult to put together. The whole thing only seems doable if you add a *lot* more people to the relevant points in the process. (And yes, new testing would require transition hand-holding from unstable to it as usual.) I agree that it's more work (as any parallel development will be), but I do think that (a) we ought to be able to reduce overhead significantly, and (b) we would make it easier for package maintainers to support the release *and* get their shiny stuff in unstable. On Thu, Apr 28, 2011 at 10:48:26AM +0100, Simon McVittie wrote: On Thu, 28 Apr 2011 at 11:29:28 +0200, Raphael Hertzog wrote: - at freeze time, instead of freezing rolling, we make a snapshot of rolling (I call it testing) and this is where we do the work left to make it ready for release So your testing is essentially the pre-2000 frozen distribution [1], and your rolling is basically the current testing without the need to freeze? If that's the case, calling the distributions unstable/testing/frozen/stable might make everyone less confused :-) I think that's what I was getting at as well, though I've been trying to use these ugly-but-more-clear quoted terms. On Thu, Apr 28, 2011 at 10:43:02AM +, Philipp Kern wrote: As said forcing is rarely used. It's still the tool to get the next release done, as Adam said. Those two goals, given that the next release ought to be usable, aren't conflicting that much. Freezing testing and having current software in unstable and testing are conflicting somewhat with the current tools, though. (And indeed it's about getting the old frozen back and uploading there directly. And regarding your I'd help with transitions, we'd also need people who do the uploads to release p-u together with casing the builds for it.) About getting frozen back in place: I want to emphasize that this is something that would be very easy to start playing with, since it doesn't put any requirements on how the rest of debian should work. We could actually dry-run entire release cycles, leaving testing running as it is, develop better tools for dealing with some of the more burdensome problems, etc. When done, lift off and nuke the branched releases and autobuilders from orbit. lather, rinse, repeat. and regarding the uploads: Like I suggested above I think you'll get a lot (not all, sure, but a lot) of that for free from the maintainers themselves, since there is a clear and encouraged way to do so. On Thu, Apr 28, 2011 at 02:55:31PM +0200, Raphael Hertzog wrote: Good. I just want to point out that frozen built on top on rolling (which is what we're proposing here) is different from frozen built on top of unstable (which is what we had before the introduction of testing). Or more clearly: frozen built on top of the next release, after it is snapshotted/branched, you mean, right? On Thu, 28 Apr 2011, Philipp Kern wrote: We just need to be clear that it's on a best-effort basis and that if there are conflicts between supporting stable and supporting rolling, stable will have the priority. Yes. And I'd like to say I'm not against leaving the option open for the RM's to take action in testing/unstable during a release if it's deemed necessary, but that we could have another way that we could use in preference to that--leaving it as more of an exceptional option rather than the default. On Thu, Apr 28, 2011 at 03:52:28PM
Re: Bits from the Release Team - Kicking off Wheezy
Hi Mehdi, On Wed, Apr 27, 2011 at 05:58:46PM +0200, Mehdi Dogguy wrote: Funny… reading your recent blogpost, you seem to not understand yet what you want to put into Rolling (and how). So, how can we comment on something that's not set or clearly described yet? Make a plan first, ask for questions later, please. There are certainly some ideas flowing here and there… but I can't find a document that describes clearly what that suite is! I can try and more clearly describe what *I* was proposing, though I'm not sure that it 100% matches up with what others have been discussing concerning CUT and rolling. To try to lower any ambiguity I'll do my best at avoiding using those terms and instead stick with more straightforward and boring terms: * unstable always feeds to testing * release N == testing, until the freeze. * when freezing for release N * testing is pointed at release N+1, and no longer automatically feeds release N. * a new RM controlled release N proposed updates area is opened, which feeds into release N. * packages migrate from this area to release N in a manner similar to how unstable would feed into testing during previous freezes (i.e. soft-freeze, hard-freeze, etc, __entirely at the discretion of RM's__). * this area would autobuild only with itself and release N build-deps. * RM's can still choose to migrate packages from (not frozen) testing as long as it's practical to do so. * When deps/transitions/etc prevent testing migration, release N proposed updates is used for one-off bin-NMU's and/or sourceful backports. * at release time for release N * remaining packages in release N proposed updates are either migrated to release N or deleted. * release N proposed updates is basically s-p-u at this point What I see as the benefits of this: * no more freezes, or periods where the fun new things slow down. * releases can happen faster if we want them to, because release N+1 has been moving along all the time. * no major earth-shaking changes to how the rest of the project works Attempting to be self-critical, the problems that I see with this approach: * developer share is splintered, some people might not be as interested in helping prepare release N and focus only on unstable, or vice versa. this is a given with any paralellizing solution though. * user/tester share is splintered. likewise a given. most important would be having enough people testing release N proposed updates. * parallel process means some (hopefully minimizable) overhead for the RM's But I'd think that we could work past these problems. Of course I'm not entirely objective so others may disagree or there may be further shortcomings. For example: What would be Rolling's content right after a release? (comparing to testing, which starts from the stable just released). I guess you cannot merge because testng will be lagging behind a bit. You cannot just get what's in testing and restart from fresh, because there might be users that won't like it. If you continue, there will be no relation with testing anymore. The two suites will have their own set of problems, I guess. I think the above should clarify this. So maybe that could be taken as a starting point for further discussion? sean -- 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/20110427175332.ga14...@cobija.connexer.com
Re: network-manager as default? No!
Hi, On Fri, Apr 15, 2011 at 10:03:40AM +0100, Jon Dowland wrote: For the record, this was (at least) bugs #432322 and #439917, and I'm extremely pleased that the issues have been resolved. Well done and thank you to all involved. AIUI they weren't resolved, but the scope of the problem was significantly minimized, which is important to note. I.e. in testing/unstable wired ethernet connections are no longer bounced during upgrade/removal. (again AIUI) In the remaining use cases network connections *are* bounced, but in the postinst rather than preinst/postinst, which lowers the chance of Bad Things happening to your network-based upgrades. And AFAIK such connections are still torn down during package removal. Could those thread participants who have gripes from their last NM experience many years ago please confirm that their gripes still apply before continuing with the discussion? (I'll assume that the slightly-less-than-polite[1] nature of this request is directed at others, but will field the question anyway) I use NM on a daily basis, and am somewhere between generally and very happy with the experience in the scope that I use it. I don't have anecdotal complaints as much as I see some potentially big problems with having NM be a _default_for_all_installs_. Plus, I haven't seen (even after asking) what the benefit is that outweighs these problems: * n-m does not support the same level of variety in network configurations, which is a regression for some subset of server environments. * any bouncing of network connections during package install/upgrade/removal is still a regression/risk even if limited in scope. * glib isn't the best library on top of which to build such a critical system level service[2] * it would result in a size/complexity growth to the standard installation. * it would require changes in long-standing practices if ifup, ifdown, and /e/n/i are no longer the preferred way to handle network configuration[3]. * requiring dbus, last I checked, would increase the likelihood of upgrades requiring manual intervention and/or reboot[4]. Allowing for but you can always uninstall this and install ifupdown is fine[5], except, why should the admin have to do so in the first place, as opposed to if you really want network-manager on your server you can install it? I'm not trying to be knee-jerk obstructionist[6] here. If we decide that we have good reasons to have a stateful network configuration daemon in every install by default, so be it, it's not my call anyway. But the implementation of *this* stateful network configuration daemon leaves a bit to be desired and I'm still waiting on what the rationale is for *why* we want to have it in the first place, hence my voicing of concerns. BR Sean [1] Gripe isn't really a constructive way to describe what could be valid and potentially significant issues. [2] the glib allocation behavior being one example. [3] this also would affect *packages* using ifup/etc or the /e/n/if-*.d/* hooks [4] that'd be #495257 which is a whole other can of worms, and I assume most admins would rather we keep servers out of that when possible. [5] though if you happen to be installing debian on a remote device that has a connection other than wired-ethernet, you suddenly have problems getting rid of NM without locking yourself out. [6] nor a get off my lawn u damn kids, learn to RTFM type either. -- 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/20110415111923.ga28...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
(throttled the conversation back a bit, hoping that someone from the release team might take the time to chime in) On Wed, Apr 13, 2011 at 02:21:38PM +0200, Raphael Hertzog wrote: In the way I had thought of things, rolling == testing. That's to say that nextstable branches off the main line of development, gets it's own staging area for updates, and the testing/unstable duo function just as they did before. So from what I see we would need the nextstable-testing area, plugged into the autobuild system, and an independant instance of the release infrastructure as a starting point. Is the nexstable staging area the same as release-proposed-updates in your view ? basically, yes, though the doors would be open earlier and a bit wider for allowing stuff into it, and additional constraints might be put in place for migrating packages out of it into nextstable. Or would there be a britney moving stuff from your staging area to nextstable ? yes, that too. basically, anything built in the nexstable-tseting/-p-u area would not automatically migrate into nextstable without the same types of criteria checks that are in place for the unstable/testing route. Yeah, it would be great to have some feedback from RT team members. I *bump* :) sean -- 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/20110415115656.ga29...@cobija.connexer.com
Re: Bits from the Release Team - Kicking off Wheezy
Hi Raphaël, On Wed, Apr 13, 2011 at 08:50:04AM +0200, Raphael Hertzog wrote: On Sun, 10 Apr 2011, sean finney wrote: My suggestion/feedback would be that we find a way where releases aren't managed so linearly, and can be be handled in a more parallel manner without such disruptive stoppage in unstable. +1 I also mentionned this in my feedback mail (although much more quickly/shortly). I've been mulling this idea over quite a bit, but with all the CUT discussions I've been hesitant to bring it up because it's sort of taking things in a different direction. Why are you thinking this? On the contrary, this is something that was suggested to implement the rolling distribution. I would very much like to form a group of developers ready to put some work towards this goal. And I would be glad if you could be part of it. I was only 50% at the last DebConf and missed the CUT BoF, but thought reading blogposts etc afterwards that people weren't as focused on the branch out stable approach that I'm talking about, and rather were more interested in stuff like snapshot testing, alternative testing from unstable, etc). But I could be mistaken. * create new release * instead of freeze, branch testing to new release * testing is now release+1 and continues to be fed by unstable[1] * use release-proposed-updates for uploader-targeted changes earlier than usual. * -release team can use $tool[2] to merge/cherry-pick collecitons of source packages (rebuild+version bump) and/or binary packages (no change). While I think this is the long-term goal, it might be more sensible to start with rolling and testing in parallel. And I also think it requires us to become involved in release matters and to develop new tools to streamline the process. In the way I had thought of things, rolling == testing. That's to say that nextstable branches off the main line of development, gets it's own staging area for updates, and the testing/unstable duo function just as they did before. So from what I see we would need the nextstable-testing area, plugged into the autobuild system, and an independant instance of the release infrastructure as a starting point. But either way, i agree tools and processes would need to be hammered out well in advance, to show that the idea works in practice as well as principle. But one of the benefits I see for how I'm proposing things is that since it doesn't involve any fundamental changes in how the rest of the project works[1]. It would be very easy to do several dry run/mock releases where we improve tools/processes and explore the problem further. I guess the real concern here is whether there's enough person-power to handle the extra work/overhead. And also whether release-proposed-updates is workable earlier in the cycle as the release manager like to pick updates from unstable because it gives some good prior-testing that release-proposed-updates might not provide. They shouldd still be able to pull from testing/unstable as well, until it gets to the point that their own freeze criteria prevents them from migrating in packages. So that's the same as before. But being parallel and all, the delta (and thus likelihood of such conflicts) will by design grow faster and earlier than it currently does. Thus the exceptional case of needing -p-u becomes less exceptional. So any potential solution would need to address making that easier to manage as well as ensuring that there's sufficient people using the p-u/nextstable-testing area. I don't think I've heard anything back from anyone who's actually on the release team regarding this, but if they were at least non-comittedly open to the idea, I'd be willing to throw my hat into the ring to help put something together. sean [1] maybe modulo solving the problem of getting better test coverage on the nextstable-testing area, if we can't find a good solution for that, which I'd hope we could. -- 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/20110413080643.ga18...@cobija.connexer.com
Re: network-manager as default? No!
On Mon, Apr 04, 2011 at 11:56:23AM +0100, Jon Dowland wrote: On Sun, Apr 03, 2011 at 07:22:47PM +0300, Faidon Liambotis wrote: It also can't do VLANs (.1q), bridges, bonds and all possible permutations of the above. I'd speculate that it also wouldn't be able to do things like 1k (or more) interfaces. It also doesn't support hooks to be able to do more advanced setups, such as multihoming, policy routing, QoS, etc. Is it necessary for the distribution's *default* network-management solution to handle all of these? If it could be easily substituted for another solution that was better suited to tasks which a majority of users will not use, then surely that is fine. (although I'd like to get NM and bridging working more nicely personally, I consider this more of a feature bug than an RC one) Except that it'd also be a regression from what's possible on current default server installs, since it already works. And any regression should be countered by strong motivation for why it's important to throw the baby out with the bathwater, and hopefully some plans for going and finding the baby later on. Did i miss the part where somebody explained what the user benefit of having network-manager on a server was? (apart from then it's the same as your desktop[1], anyway). sean [1] although it isn't, unless you're installing gnome on your server, but then you're installing a desktop not a server, and you'd get it by default anyway, and then what's the point? -- 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/20110413091127.ga19...@cobija.connexer.com
Re: Bug#621833: System users: removing them
Hi Lars, On Tue, Apr 12, 2011 at 06:41:10PM +0100, Lars Wirzenius wrote: But shouldn't we say they _must_ lock package-specific system users and groups when the package is removed ? I think that's a good idea. Steve Langasek in the bug (#621833) and others agree, so I think there's a strong consensus on that. I don't think I'd agree there, at least without also addressing: * It also needs to limit the scope to locally defined users (i.e. not fail when it is unable to lock an NIS/LDAP/etc account). * There needs to be a way to explicitly do that with adduser or a similar tool[1][2][3][4]. Also, we haven't discussed what should be done in the case of a user account possibly shared between different packages, where any one of them may create it and 1..N of them might be installed. For example, nagios/nrpe comes to mind, or maybe parallel installed postgres versions and related tools. Alternatively, if we strictly interpret what Ian suggested to not include such packages, we should state that and/or give alternate instructions for this case. I second your original proposal though, that packages must not delete system users that they have created. I don't think anyone had objections to that, and the question is whether things should be taken further. sean [1] Assuming it must be done with one tool, it should also state lock users with $thiscommand $theseoptions, and depend on $thisversion of the tool in question if the tool needs to be updated. [2] And if $theseoptions are not specifically for the local only case, we need a way to tell the difference between a locking failed error and a user is remote error. [3] Or maybe instead of using a tool we have something like declarative users, where we state policy and farm it off to dpkg to implement? [4] Whoa, footnotespam ftw, sorry. -- 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/20110412193147.ga15...@cobija.connexer.com
Re: Best practice for cleaning autotools-generated files?
On Wed, 2011-03-16 at 16:36 +, Ian Jackson wrote: Then, you need a way to patch them. There is lots of software where you need to patch configure.ac and/or Makefile.am That's fine, you patch the input, rerun the autofoobar stuff, and then build the source package with diff. If you're using a patch queue system, or a vcs, you arrange for the autogenerated autofoobar output changes to be committed along with the corresponding input change. and then you end up with either (a) masses of changes to upstream files in your local branch which will cause merge conflicts (and aesthetically, ew, yuck.) or (b) a patch in your patch queue which will very likely not apply in the next upstream release. If you do it with the patch system (quilt or even plain dpkg), before building the package source, you cannot ensure that files are patched in the right order. What do you mean in the right order ? autofoo stuff examines timestamps on various files, so it's possible that if configure gets patched before configure.ac, and AM_MAINTAINER_MODE is set to a specific value, that ./configure ends up wanting to regenerate ./configure at build time. double fail. So Makefile rules can then re-run auto* tools at build time and you lost the benefit you want to have. Makefile rules should not rerun auto* stuff at build time. they will if AM_MAINTAINER_MODE is being used, in some cases. sean signature.asc Description: This is a digitally signed message part
Re: Best practice for cleaning autotools-generated files?
On Tue, Mar 15, 2011 at 10:29:57PM +, Marcin Owsiany wrote: * maintain a whitelist of distributed files, and rm everything else (apart from the debian directory) in the clean target. Since I use (or plan to use) git-buildpackage, I don't have a tarball which could serve as an authoritative whitelist. Thus an additional whitelist refresh step would be required every time I merge the upstream branch into the debian branch. That's bad. Furthermore, a whitelist approach would mercilessly elliminate all files on a clean, so one would have to be really careful not to leave unchecked but precious files in the source tree at any time... :-/ while i've heard that the latest dh/cdbs can do this automatically for you, in a few packages that I maintain where they're still running dh 5, i keep an AUTOFOO_CRUFT variable in debian rules, and have a small amount of code in the corresponding build and clean areas to preserve and unpreserve these files. Example: http://git.debian.org/?p=pkg-xorg/app/compiz.git;a=blob;f=debian/rules;h=530ff40f4e5228a6207d9d6d5a0f8a68acecc0b9;hb=a481aecfeea68adea9d0579059c8eb3a746fcd44 it's not perfect, but seems to do the trick. note that this is not a list of everythign autofoo creates/modifies, but rather a list of everythign that make distclean fails to remove/restore. It tends to gather files over time and some of them might no longer apply in later upstream releases, though there's no harm done apart from maybe a couple wasted cp operations. On Tue, Mar 15, 2011 at 10:55:54PM +, Neil Williams wrote: Other tools, like svn-buildpackage, don't have this problem, via the mergeWithUpstream support and/or a ../tarballs/ directory. Not perfect but it works. no, they do have this problem but most people just choose to ignore it until it causes an FTBFS. If you build with mergeWithUpstream there is the same likelihood that cruft gets left around, it just doesn't dirty your working directory/checkout. You can still run into problems if someone downloads the source package from a mirror and tries to a build/clean/build. I think CMake makes a better job of native packages which need autotools-type hand-holding, so I may port to that instead. IIRC CMake for the most part generates its cruft in a nukable subdirectory, which makes cleanup significantly simpler. Building direct from VCS is a nice idea but sometimes, it just isn't worth the pain - let the build system build the tarball and package from the tarball. It's just easier. Or just change the build system and/or the tool. IYHO anyway -- I and I'm sure others would probably beg to differ :) sean -- 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/20110316085426.ga12...@cobija.connexer.com
Re: Setting file capabilites of files shipped in binary packages
On Mon, Mar 14, 2011 at 01:17:02PM +, Ben Hutchings wrote: No, I don't think there's a way to do that programmatically. You would just have to try capset and then chmod u+s. instead of chmod, you would actually want something that checked/respected dpkg-statoverride, rather than hard-coding the permissions. there unfortunately is no equivalent for capabilities that i know of. I'd say this would be something that would be best handled either by extending dpkg-statoverride, or dpkg itself (i.e. declaritive style), though in the meantime trying to set the capabilities and failing gracefully in the case that it's not supported seems reasonable. On Mon, Mar 14, 2011 at 02:56:25PM +0100, Olaf van der Spek wrote: Shouldn't this be done via DH instead of duplicating this code into lots of postinsts? Eventually, sure, but no reason to jump the gun while $this is still rather undefined. sean -- 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/20110314143655.ga5...@cobija.connexer.com
Accepted compiz 0.9.2.1+git20110226.f059fae9-3 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Mar 2011 19:50:37 +0100 Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-gnome compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all i386 Version: 0.9.2.1+git20110226.f059fae9-3 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz - OpenGL window and compositing manager - metapackage compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files Changes: compiz (0.9.2.1+git20110226.f059fae9-3) experimental; urgency=low . * Add Conflicts/Replaces to reflect some shifting of files from 0.8.x Checksums-Sha1: ec3f1127ff854a27539764b810af72d0ee55d787 2408 compiz_0.9.2.1+git20110226.f059fae9-3.dsc 3fb8b821235c2c5e0e6d80df89c0c17b520a3db9 31110 compiz_0.9.2.1+git20110226.f059fae9-3.debian.tar.gz 2ad20ffb5083956efa495b645a61b85cbc300e26 30248 compiz_0.9.2.1+git20110226.f059fae9-3_all.deb b16ddde1a28a59562b1f25260cd81842929789fe 1161290 compiz-core_0.9.2.1+git20110226.f059fae9-3_i386.deb 3ccfe780f62ed4a1dde7d967ff1eb51a8aa7b6ea 89308 compiz-dev_0.9.2.1+git20110226.f059fae9-3_i386.deb c2ee0915d7bb2a29a8084bc21e9ccb5d5240eba1 330346 compiz-gtk_0.9.2.1+git20110226.f059fae9-3_i386.deb be653e7c13ee86e2d40751c808a1f44ed25a1701 98634 compiz-kde_0.9.2.1+git20110226.f059fae9-3_i386.deb dae310f0c3b79291fbe0cedfcb792223f526920d 37086 compiz-gnome_0.9.2.1+git20110226.f059fae9-3_i386.deb 6599705d02575ca7d0666a0a3c214ea5a4a774e1 1101074 compiz-plugins_0.9.2.1+git20110226.f059fae9-3_i386.deb 08f8a2a593f16e712d2ec062eb8a17ba118fbb78 50400 libdecoration0_0.9.2.1+git20110226.f059fae9-3_i386.deb a546cd7dfc27d330f87855da03609e66109d6313 39864 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-3_i386.deb Checksums-Sha256: eeb265c7bdf2ff60180af3a0be000989f9ec0721c3e0418ded960a6f03aafebc 2408 compiz_0.9.2.1+git20110226.f059fae9-3.dsc 37cfe224d6a7bb304ac2b334940f2aa6dc4a8e0d089c5eca72ee62e4076c7905 31110 compiz_0.9.2.1+git20110226.f059fae9-3.debian.tar.gz f4525c5d063ca019c7a1f17ba7d01dcece26e4827b65a1044eb28952f00fa245 30248 compiz_0.9.2.1+git20110226.f059fae9-3_all.deb 9bc7f0417d3b9f31b29609c3294aa04c44c46f9834d095ea7d9b0cf222101222 1161290 compiz-core_0.9.2.1+git20110226.f059fae9-3_i386.deb 23a6d51ae4005426f87a6fda18678f4ef3f888aab65d6b698e18e04b2a07cd80 89308 compiz-dev_0.9.2.1+git20110226.f059fae9-3_i386.deb 7a9a07756dfd0877bb11bfc8d4e9b358bbef68f6c6d1105dfcb2726d7cc26cba 330346 compiz-gtk_0.9.2.1+git20110226.f059fae9-3_i386.deb 9b00c284e68290f4a25860f4a7632d0c6c4dbb7bb080ca1d49eaec8a2447aad2 98634 compiz-kde_0.9.2.1+git20110226.f059fae9-3_i386.deb 30dd1e2b13b10f228eafc5fc43674d3b4946e196fa56f93f5a55def46ea669dd 37086 compiz-gnome_0.9.2.1+git20110226.f059fae9-3_i386.deb a6c3e2786762306c824a213e82b8aa2e9228ec33cd7e13cf1dd090261a508c6c 1101074 compiz-plugins_0.9.2.1+git20110226.f059fae9-3_i386.deb a9fb3314ab7f1c9088960bfef1558880d89c8db375294c6e463da874bbd81e03 50400 libdecoration0_0.9.2.1+git20110226.f059fae9-3_i386.deb 2ebdcb3c76a1f137d2ddc43dcd6c4ebcd80062406dc3a5f099e735ea90c2bb45 39864 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-3_i386.deb Files: 7a6d0d7ca5eb4e0248e2e7ea209576fd 2408 x11 optional compiz_0.9.2.1+git20110226.f059fae9-3.dsc e0ede9f7582551202acafb20ddb90f7a 31110 x11 optional compiz_0.9.2.1+git20110226.f059fae9-3.debian.tar.gz d31e5bbdefe51f3f9b57cb256cf04e29 30248 x11 optional compiz_0.9.2.1+git20110226.f059fae9-3_all.deb a82c0e054787d4e1a9d3db9ac60ea98e 1161290 x11 optional compiz-core_0.9.2.1+git20110226.f059fae9-3_i386.deb 6aebe7b70e7224ec101913b38b05d26b 89308 x11 optional compiz-dev_0.9.2.1+git20110226.f059fae9-3_i386.deb 02b9b980a298b6c15ab2dc631a26dc24 330346 x11 optional compiz-gtk_0.9.2.1+git20110226.f059fae9-3_i386.deb a541469834d9c1efa67f77a2fc53d9de 98634 x11 optional compiz-kde_0.9.2.1+git20110226.f059fae9-3_i386.deb 2c94bc7cbd1131ad42baea4bf6fc59df 37086 x11 optional compiz-gnome_0.9.2.1+git20110226.f059fae9-3_i386.deb 555e7c5a5421ada09de651459565105c 1101074 x11 optional compiz-plugins_0.9.2.1+git20110226.f059fae9-3_i386.deb ec51ab038c1937fe31bd58d92512bf85 50400 x11 optional libdecoration0_0.9.2.1+git20110226.f059fae9-3_i386.deb 9febd3a414e5a74b9a3fefc4ee74e7b7 39864 libdevel optional libdecoration0-dev_0.9.2.1+git20110226.f059fae9-3_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux
Accepted compizconfig-backend-gconf 0.9.2.1+git20110226.g861a1d4-2 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 07 Mar 2011 21:29:43 +0100
Source: compizconfig-backend-gconf
Binary: compizconfig-backend-gconf
Architecture: source i386
Version: 0.9.2.1+git20110226.g861a1d4-2
Distribution: experimental
Urgency: low
Maintainer: Debian X Strike Force debia...@lists.debian.org
Changed-By: Sean Finney sean...@debian.org
Description:
compizconfig-backend-gconf - Compiz Fusion configuration system - gconf backend
Changes:
compizconfig-backend-gconf (0.9.2.1+git20110226.g861a1d4-2) experimental;
urgency=low
.
* Add a Depends compiz-core-abiversion-${coreabiversion}
Checksums-Sha1:
7d029c9e881998b73da0ba4d1fbc2ad22b690484 1692
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.dsc
7077b17d2bd2729e474a355664053b9dd700ac4d 2626
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.debian.tar.gz
4676f049f9fff7614073ffd4d1b604f46b4385f5 16638
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2_i386.deb
Checksums-Sha256:
2aba98335ff0e3e659365d6c95cbc51bf0c1af46ab611f60662cd0995cdec7fd 1692
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.dsc
47c2a8a1c47e3ed67c233db29e1035b1dac883d2fa3402b80656871be37e3072 2626
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.debian.tar.gz
796a66fc1df9c612682737532c7c041626554d604ea1ad26148f967dae1e5256 16638
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2_i386.deb
Files:
9f2534986e58cd69bb42187f406f71f7 1692 x11 extra
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.dsc
97002cce112fcafe14d49e050fc08628 2626 x11 extra
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.debian.tar.gz
e02818085aaebaf2dceed3991651b196 16638 x11 extra
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk11QPwACgkQynjLPm522B2XBACcCPeqbBe8pbQ2aAZSfH+URZFK
Hh8An30HiJXJ6xvgk+1S8v9btdE2OS96
=ogPL
-END PGP SIGNATURE-
Accepted:
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.debian.tar.gz
to
main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.debian.tar.gz
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.dsc
to
main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2.dsc
compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2_i386.deb
to
main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-2_i386.deb
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1pwhvu-0002uo...@franck.debian.org
Accepted compizconfig-backend-kconfig 0.9.2.1+git20110227.770eb464-2 (source i386)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 07 Mar 2011 21:37:38 +0100
Source: compizconfig-backend-kconfig
Binary: compizconfig-backend-kconfig
Architecture: source i386
Version: 0.9.2.1+git20110227.770eb464-2
Distribution: experimental
Urgency: low
Maintainer: Debian X Strike Force debia...@lists.debian.org
Changed-By: Sean Finney sean...@debian.org
Description:
compizconfig-backend-kconfig - Compiz Fusion configuration system - kconfig
backend
Changes:
compizconfig-backend-kconfig (0.9.2.1+git20110227.770eb464-2) experimental;
urgency=low
.
* Add a Depends compiz-core-abiversion-${coreabiversion}
* This package was conflicting with... itself? Fixed.
Checksums-Sha1:
2124cdfdce9163dbe78d8a5e983dba9c10f6ecfa 1675
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.dsc
54efa251f29ba550fc4aefe8610a8bb99ac1d47c 3039
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.debian.tar.gz
3faf127b4d36fac8cf70cd9b699bb4c106f1e3e8 32160
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2_i386.deb
Checksums-Sha256:
52d12acf26433c63c07f41a173576d9a17d63d524f6f95731e0f7f473376c058 1675
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.dsc
20cb4212f68a31911851010c852b32884deef40bca9131b8baad306c05d3f1b1 3039
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.debian.tar.gz
6d47dd6a8f2948b96f0bedfe4bb292e7bb4a52ea3d384276bd7cc24670153126 32160
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2_i386.deb
Files:
60656ec03354e5b9a1393250ef00300d 1675 x11 extra
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.dsc
80c15e509f708822d96ebe76891f03f7 3039 x11 extra
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.debian.tar.gz
fbf5a71aed421213f17f7b7368624b1a 32160 x11 extra
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2_i386.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk11QvoACgkQynjLPm522B2bWACfRxAglGIL2U3crGN9ONP8zHr6
Jv8AoIFFiufEaXnER7gDbeQ42BhQPNsr
=0gWG
-END PGP SIGNATURE-
Accepted:
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.debian.tar.gz
to
main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.debian.tar.gz
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.dsc
to
main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2.dsc
compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2_i386.deb
to
main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-2_i386.deb
--
To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1pwhw6-0002y9...@franck.debian.org
Accepted compiz 0.9.2.1+git20110226.f059fae9-4 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 07 Mar 2011 20:45:51 + Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-gnome compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all i386 Version: 0.9.2.1+git20110226.f059fae9-4 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz - OpenGL window and compositing manager - metapackage compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files Changes: compiz (0.9.2.1+git20110226.f059fae9-4) experimental; urgency=low . * compiz-plugins needs a Depends libdecoration0 (= 0.9.0) Checksums-Sha1: 3eb07a7fb6433805ed803a61f76f5293864e17af 2408 compiz_0.9.2.1+git20110226.f059fae9-4.dsc 160bfe5076984fb3017409d4b2d620af29a6ad3e 31166 compiz_0.9.2.1+git20110226.f059fae9-4.debian.tar.gz 7aed8298f4b4cc1629e994020803b711b0fc4aea 30274 compiz_0.9.2.1+git20110226.f059fae9-4_all.deb 467505c2197389dd22a11550516ba443065b0ff3 1161408 compiz-core_0.9.2.1+git20110226.f059fae9-4_i386.deb f946c984af23dc85818d3b951ae918da46557a3e 89346 compiz-dev_0.9.2.1+git20110226.f059fae9-4_i386.deb ba904f38cb86764017dfa142c831741c4e1e 330400 compiz-gtk_0.9.2.1+git20110226.f059fae9-4_i386.deb 756738fae29ed8af5964781c639fa40aa8afe690 98652 compiz-kde_0.9.2.1+git20110226.f059fae9-4_i386.deb ccc7252ac5e4dcb9bc56584b6ed98e8605b7595d 37112 compiz-gnome_0.9.2.1+git20110226.f059fae9-4_i386.deb 5784777d71260355b466279c69a93848b5039d9b 1101084 compiz-plugins_0.9.2.1+git20110226.f059fae9-4_i386.deb 2cc9a57e6a83e6a460a859436513fd757015e505 50428 libdecoration0_0.9.2.1+git20110226.f059fae9-4_i386.deb 518fa7fa13c1ee70c7e5e253cd154b546a07babd 39878 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-4_i386.deb Checksums-Sha256: f93426d3fb7e2be36c96428fb8299017807f92db66e6e9588676c08db13f00ea 2408 compiz_0.9.2.1+git20110226.f059fae9-4.dsc 227eeac48d4221fcdd662cb130466c15da1a8e9221f309ff2c603fd017871346 31166 compiz_0.9.2.1+git20110226.f059fae9-4.debian.tar.gz 6a14f81b029f8ddcfcef199820bf8cb79518c8139e5caf7c983ac4a95b8bfa87 30274 compiz_0.9.2.1+git20110226.f059fae9-4_all.deb 8505b7ce4740aaa78da43507ce6b68803192a67a068442ce2f084be2d928f82f 1161408 compiz-core_0.9.2.1+git20110226.f059fae9-4_i386.deb 5fe1fb4dd4a2f0186e14ce670876c0797f1f2de8d636dd7cddd87162c06fabcb 89346 compiz-dev_0.9.2.1+git20110226.f059fae9-4_i386.deb d461b096cee0a86ea4aebe32e5f764eebb3d497525a09b36b1e8436c9b0ed433 330400 compiz-gtk_0.9.2.1+git20110226.f059fae9-4_i386.deb 5d4fc9194f8dbfd304f084f1500c37c9c0f4ff634e1593b1bd4a6d1e820c4e6c 98652 compiz-kde_0.9.2.1+git20110226.f059fae9-4_i386.deb 7c841ada77fffca66e828b7d1e9dcfa040b0ae675b3f6cc0022e7cc067aa5fd0 37112 compiz-gnome_0.9.2.1+git20110226.f059fae9-4_i386.deb 5466a5f8e1cabfb3992b0853f390def6e2b350f8623c9947f6c8eced8c095ed4 1101084 compiz-plugins_0.9.2.1+git20110226.f059fae9-4_i386.deb 2fd88db185549ac3827a50ba56dc54ff37c8b66db2cf8608134364191c6adc6c 50428 libdecoration0_0.9.2.1+git20110226.f059fae9-4_i386.deb 312003b6d3935933ea72dda3e25cb75b307dbc882d8fe19ae17538e4cfce1498 39878 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-4_i386.deb Files: 3969bf3b115b3659c00082c02938a319 2408 x11 optional compiz_0.9.2.1+git20110226.f059fae9-4.dsc d09e77eeed69f56dc55956329fa74116 31166 x11 optional compiz_0.9.2.1+git20110226.f059fae9-4.debian.tar.gz b297d7508fe3e8edd628f505292e7647 30274 x11 optional compiz_0.9.2.1+git20110226.f059fae9-4_all.deb d2d2233ef00590c9bd65f298ce663da7 1161408 x11 optional compiz-core_0.9.2.1+git20110226.f059fae9-4_i386.deb 4800ff8d95b2d483f497e5304fdcd03a 89346 x11 optional compiz-dev_0.9.2.1+git20110226.f059fae9-4_i386.deb dd1384be79c32db5dcac5f0b43941342 330400 x11 optional compiz-gtk_0.9.2.1+git20110226.f059fae9-4_i386.deb 859ab113b8f516f6962a426742274e9c 98652 x11 optional compiz-kde_0.9.2.1+git20110226.f059fae9-4_i386.deb b7031016279a1511224c9cd33e2b6733 37112 x11 optional compiz-gnome_0.9.2.1+git20110226.f059fae9-4_i386.deb 61dc3e0aa0c1daf9f300b558dc1da08f 1101084 x11 optional compiz-plugins_0.9.2.1+git20110226.f059fae9-4_i386.deb eecc5f6827e252e9908459ed73ece4a1 50428 x11 optional libdecoration0_0.9.2.1+git20110226.f059fae9-4_i386.deb 8d155f0b7c6c9df47a69c4bfaae19f1c 39878 libdevel optional libdecoration0-dev_0.9.2.1+git20110226.f059fae9-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux
Accepted compiz 0.9.2.1+git20110226.f059fae9-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Mar 2011 13:53:30 + Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-gnome compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all i386 Version: 0.9.2.1+git20110226.f059fae9-2 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz - OpenGL window and compositing manager - metapackage compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files Changes: compiz (0.9.2.1+git20110226.f059fae9-2) experimental; urgency=low . * Add a Depends on libglibmm-2.4-dev to compiz-dev Checksums-Sha1: cbb29e0b716c287975083dd67117c82759a9a90d 2408 compiz_0.9.2.1+git20110226.f059fae9-2.dsc 12b43498915015f158ff326975c21c4281d55809 30955 compiz_0.9.2.1+git20110226.f059fae9-2.debian.tar.gz 4660b077f05af82fdb23ae02fe2995ca773e1fcf 30200 compiz_0.9.2.1+git20110226.f059fae9-2_all.deb 595fd12d33ffbc32257f1035fb79d39d7d554238 1161160 compiz-core_0.9.2.1+git20110226.f059fae9-2_i386.deb 70d086650a0bada9445563bb0665d0d270c70e2f 89280 compiz-dev_0.9.2.1+git20110226.f059fae9-2_i386.deb c3cec0ca5711e74060f71e325a148e598d944b44 330314 compiz-gtk_0.9.2.1+git20110226.f059fae9-2_i386.deb 8912ff51d6e52dd062c9bf55046a66d60b878434 98590 compiz-kde_0.9.2.1+git20110226.f059fae9-2_i386.deb b6e3ba155dfa5f242fa32e1e8d716d817905ef3f 37042 compiz-gnome_0.9.2.1+git20110226.f059fae9-2_i386.deb 33a71088be75cd819f53d9640092238cd24b2346 1101054 compiz-plugins_0.9.2.1+git20110226.f059fae9-2_i386.deb 6346cd4ef6cc18f4a60d6e9520dbda908f928def 50358 libdecoration0_0.9.2.1+git20110226.f059fae9-2_i386.deb 66dd3b088fc193f794f05d313f7dbbad0bb565bd 39808 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-2_i386.deb Checksums-Sha256: 66cf41649eecaa1a92cec4304479b7e49e87f23130e89de83e0891e460077387 2408 compiz_0.9.2.1+git20110226.f059fae9-2.dsc ef7b08dc2dd7a74c4ff700e347799688b1e57438982d6e09734b3471d6915bb7 30955 compiz_0.9.2.1+git20110226.f059fae9-2.debian.tar.gz fbaa1be4b11aa47d7bba4f0137cbf66585da13bf791c97f10b357c6efc0e2fec 30200 compiz_0.9.2.1+git20110226.f059fae9-2_all.deb ccbeb4bf07749757a44cea0ea96f2aeda55d1798960ff5c2dd8d457d26c210ac 1161160 compiz-core_0.9.2.1+git20110226.f059fae9-2_i386.deb 29aa53fd36b028e8fb7936d4ca189d0505d83b7391597a70e743eb998ed6549a 89280 compiz-dev_0.9.2.1+git20110226.f059fae9-2_i386.deb 784ed264b059749b77fe7dd1b71ba40ae59770b4bbfe52eb561e7db98092b4d1 330314 compiz-gtk_0.9.2.1+git20110226.f059fae9-2_i386.deb 42834737160addc5cd79e914f1f8e96349ecaadae36248077ed677e30e7d7b5d 98590 compiz-kde_0.9.2.1+git20110226.f059fae9-2_i386.deb eb946451b6a5ad75b95ea5ff5fcb2d9cb5ab3bb94140021a0ccd32035dfd4b65 37042 compiz-gnome_0.9.2.1+git20110226.f059fae9-2_i386.deb b66ff71dadadc00f6353e83556221f6c88d80ecd96d0ab6101fb3379571ab30b 1101054 compiz-plugins_0.9.2.1+git20110226.f059fae9-2_i386.deb fb95b97acd754b0e52f37f91a0762411bad306e323bd99f46a2673bfd98ddcbb 50358 libdecoration0_0.9.2.1+git20110226.f059fae9-2_i386.deb 7cd4919ce473e923cb329eda5d147a1512f2a190f8f5928c37c11e4f490e800a 39808 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-2_i386.deb Files: 4142584483d686424d9ad4fd1419ce65 2408 x11 optional compiz_0.9.2.1+git20110226.f059fae9-2.dsc 4092bd0973451ca8d79f9639ab1093e6 30955 x11 optional compiz_0.9.2.1+git20110226.f059fae9-2.debian.tar.gz 22074542c3ecdb446a8b0f927d4d8654 30200 x11 optional compiz_0.9.2.1+git20110226.f059fae9-2_all.deb e012cc3a0acb3006e54b9efaa127f266 1161160 x11 optional compiz-core_0.9.2.1+git20110226.f059fae9-2_i386.deb b7a006bdda5095513874ca0757d9a854 89280 x11 optional compiz-dev_0.9.2.1+git20110226.f059fae9-2_i386.deb 0091ad01b1c5d067fd6eaa6eaa19386b 330314 x11 optional compiz-gtk_0.9.2.1+git20110226.f059fae9-2_i386.deb 77246a2f8865b67b633800131e2b0332 98590 x11 optional compiz-kde_0.9.2.1+git20110226.f059fae9-2_i386.deb 3efb07416524122ff7d0fea87836efb4 37042 x11 optional compiz-gnome_0.9.2.1+git20110226.f059fae9-2_i386.deb db8365f0c658a29f5dd6c0c714e13a63 1101054 x11 optional compiz-plugins_0.9.2.1+git20110226.f059fae9-2_i386.deb bc44f4f6346c15117a7d4a54f25fef5f 50358 x11 optional libdecoration0_0.9.2.1+git20110226.f059fae9-2_i386.deb 37bd7d8f1d4acf74c189a72624725383 39808 libdevel optional libdecoration0-dev_0.9.2.1+git20110226.f059fae9-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux
Accepted compiz-fusion-plugins-extra 0.9.2.1+git20110224.e621355c-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 05 Mar 2011 10:54:09 +0100 Source: compiz-fusion-plugins-extra Binary: compiz-fusion-plugins-extra Architecture: source i386 Version: 0.9.2.1+git20110224.e621355c-2 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-extra - Compiz Fusion plugins - extra collection Changes: compiz-fusion-plugins-extra (0.9.2.1+git20110224.e621355c-2) experimental; urgency=low . * Fix an FTBFS by adding a Build-Dep on libglibmm-2.4-dev Checksums-Sha1: 98815055712e373e7a0daa441980c98666b42e45 1872 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.dsc 6c10ae5044120b3f820106d801ee57fe9125bde8 4375 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.debian.tar.gz 0e5a49d452cfaddd3ce6459ea450f57b72c0a87d 3045776 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2_i386.deb Checksums-Sha256: 5e70afb7034ddb1f74ee393552121d848dc3ffb16566b4e99df03e8fb92a97f5 1872 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.dsc 63373628cc310ff02ce87edac33025f5d94fb05fb312bf323791c6b4cd04cfaa 4375 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.debian.tar.gz 0610515c776b2f034845eafbb009020849e2073116d1728efb2fe7517422c028 3045776 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2_i386.deb Files: 45dfeac7b44a5651bd027282e218b47c 1872 x11 extra compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.dsc 9847e79537c363d172aceadfc563b779 4375 x11 extra compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.debian.tar.gz b4dd963988868f72e7821b0e81ac3d9f 3045776 x11 extra compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1yCZIACgkQynjLPm522B1mxwCbBrTF1KsCtb/U/1EnMNEzHqXA vSsAniH9VQHYV8YgMz8W/ezPoYZCxHTf =TKcP -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.debian.tar.gz to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.debian.tar.gz compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.dsc to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2.dsc compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2_i386.deb to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-2_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pvoxv-00087o...@franck.debian.org
Accepted compiz-fusion-plugins-unsupported 0.9.2.1+git20110224.4d704607-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 05 Mar 2011 11:47:28 + Source: compiz-fusion-plugins-unsupported Binary: compiz-fusion-plugins-unsupported Architecture: source i386 Version: 0.9.2.1+git20110224.4d704607-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-unsupported - Compiz Fusion plugins - unsupported collection Changes: compiz-fusion-plugins-unsupported (0.9.2.1+git20110224.4d704607-1) experimental; urgency=low . [ Janos Guljas ] * New upstream release. * Bump standards to 3.9.1. * Switch to dpkg format 3.0 (quilt) * Rewrite debian/rules to use debhelper 7. * Removed debian/install file. * Updated debian/watch file. . [ Sean Finney ] * Add common 3.0 format local-options * Add Build-Dep on libglibmm-2.4-dev * Update copyright information Checksums-Sha1: 2a438bbbe5a6a1e865022184c157a875f8716b3e 1973 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.dsc 4be808db0ab017107c4483536f862df61be8c1ee 1029764 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607.orig.tar.gz dc2997162e2a88528f927a777684aeb90381ff52 4507 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.debian.tar.gz 9ad7284b846aef220d08e40e6b9cba8c0cc15695 481328 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1_i386.deb Checksums-Sha256: ee01968873a85539f12d6b9ebfe47a34241bc17ba1fa0559d1077d66c7e78225 1973 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.dsc c99f7647282ab90a45b0674eea77ec965cf42ce19d4645fc0b65a8be399287fa 1029764 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607.orig.tar.gz 1976724b98b37023ed459b9b7fcaca118ff9339f031ec9a5e7c13b194323673e 4507 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.debian.tar.gz b81c0846f5a91ee8132e707cc9bfade9680dfe38e0e59d799d9b6bcaa2b8c986 481328 compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1_i386.deb Files: 13496a2ff461ee9d61660fcff51b4312 1973 x11 extra compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.dsc 41b73f1be16f15506b2ab1320da4ca39 1029764 x11 extra compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607.orig.tar.gz c7a94a869631f0514ceb75bbb75537fc 4507 x11 extra compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.debian.tar.gz be2f094d4b1e28bfbea06e55c5357029 481328 x11 extra compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1yI64ACgkQynjLPm522B2c0wCfR5XSpFZQ3C4E6IyTUTcgmZOC 9uIAoIPLVw/+b/EsM1lNg03bfjU0yBBk =zNll -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.debian.tar.gz to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.debian.tar.gz compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.dsc to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1.dsc compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1_i386.deb to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607-1_i386.deb compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607.orig.tar.gz to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.9.2.1+git20110224.4d704607.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pvzjc-0008ey...@franck.debian.org
Accepted compizconfig-python 0.9.2.1+git20110224.5ccb653e-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 05 Mar 2011 23:22:44 + Source: compizconfig-python Binary: python-compizconfig Architecture: source i386 Version: 0.9.2.1+git20110224.5ccb653e-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: python-compizconfig - Compizconfig bindings for Python Changes: compizconfig-python (0.9.2.1+git20110224.5ccb653e-1) experimental; urgency=low . [ Janos Guljas ] * New upstream release. * Bump standards to 3.9.1. * Switch to dpkg format 3.0 (quilt) * Rewrite debian/rules to use debhelper 7. * Add debian/watch file. * Add patch * 01-fix-extension-dir.patch - Remove Makefile so dh_python2 can install extension in a right place . [ Sean Finney ] * Add common 3.0 local options Checksums-Sha1: c8ad1877894a02b1514bdececf43cd75853715a6 1639 compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.dsc be2e4c8a94f72348d205d4a4d66466e546fac640 16921 compizconfig-python_0.9.2.1+git20110224.5ccb653e.orig.tar.gz 43a0c0a0ce4120ea115b6d22c161d18da82e92af 2741 compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.debian.tar.gz 90152a29bad86e5e899542271453c1f3813af54e 43810 python-compizconfig_0.9.2.1+git20110224.5ccb653e-1_i386.deb Checksums-Sha256: 53ca6430f1416eac90f0e9fa7f8d1187b2aa9ab4c9e01cdb825bf19f3fe804f9 1639 compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.dsc 1faa57cb2e19a81253bfd73a418070f93d0cbaeabb0f9ef77d43d4145a97d367 16921 compizconfig-python_0.9.2.1+git20110224.5ccb653e.orig.tar.gz 1624a890a8dd0d044a9d5b57bb9a1cdc60bd5c3fc63c934ca354db2f073ad999 2741 compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.debian.tar.gz e4d9f906ee2da45a0a0ec48499c3e2f533d2c2e4fd38741021a72ed3e0c25f1f 43810 python-compizconfig_0.9.2.1+git20110224.5ccb653e-1_i386.deb Files: 09b459922aeb5bfcfba16bcb3e9bf43f 1639 python extra compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.dsc e9af04443191c75b9d55b5cffe819ee2 16921 python extra compizconfig-python_0.9.2.1+git20110224.5ccb653e.orig.tar.gz b155adbf1d10543bd87c19e05f63bdaa 2741 python extra compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.debian.tar.gz d75706d4e1e11c2bf73dadfc8ab222b9 43810 python extra python-compizconfig_0.9.2.1+git20110224.5ccb653e-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1yx2YACgkQynjLPm522B2AoACdG6O2lGp+Hj7PwEZYZuxD085T +/8An3kOFewC6uXcUeYZJFcVBv7aYtYB =Nhg+ -END PGP SIGNATURE- Accepted: compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.debian.tar.gz to main/c/compizconfig-python/compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.debian.tar.gz compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.dsc to main/c/compizconfig-python/compizconfig-python_0.9.2.1+git20110224.5ccb653e-1.dsc compizconfig-python_0.9.2.1+git20110224.5ccb653e.orig.tar.gz to main/c/compizconfig-python/compizconfig-python_0.9.2.1+git20110224.5ccb653e.orig.tar.gz python-compizconfig_0.9.2.1+git20110224.5ccb653e-1_i386.deb to main/c/compizconfig-python/python-compizconfig_0.9.2.1+git20110224.5ccb653e-1_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pw1bk-v8...@franck.debian.org
Accepted ccsm 0.9.2.1+git20110224.cb1268cb-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 06 Mar 2011 00:36:36 + Source: ccsm Binary: compizconfig-settings-manager Architecture: source all Version: 0.9.2.1+git20110224.cb1268cb-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-settings-manager - Compizconfig Settings Manager Changes: ccsm (0.9.2.1+git20110224.cb1268cb-1) experimental; urgency=low . [ Janos Guljas ] * New upstream release. * Bump standards to 3.9.1. * Switch to dpkg format 3.0 (quilt) * Changed compizconfig-settings-manager architecture to all. * Rewrite debian/rules to use debhelper 7. * Removed debian/install file. * Updated debian/watch file. * Add patch * 01-fix-extension-dir.patch - Remove Makefile so dh_python2 can install extension in a right place . [ Sean Finney ] * Add common 3.0 source format options * Remove local changes snuck into packaging by dpkg-source 3.0 * Explicitly remove ccsm.desktop during clean * New patch to remove invalid Compiz category from ccsm.desktop * Fix mis-named md.po - mnk.po * Remove leftover installed_files file during clean Checksums-Sha1: 3d2bca8a1d65ab1a7bc62091adf618af8a9ce6f9 1407 ccsm_0.9.2.1+git20110224.cb1268cb-1.dsc 6e37fe8a2a8b41be5418e2cd923b681a908230b4 1197512 ccsm_0.9.2.1+git20110224.cb1268cb.orig.tar.gz 8e24ea9cd2ee1f94a9adec5778b245011b695d00 4664 ccsm_0.9.2.1+git20110224.cb1268cb-1.debian.tar.gz 1f0c97237c84e5436e061e6fc69b9b937f970765 1225380 compizconfig-settings-manager_0.9.2.1+git20110224.cb1268cb-1_all.deb Checksums-Sha256: d081395c34a40be3a712acc059c5595d60e9cebc44063071a6d2abc2a77e1a19 1407 ccsm_0.9.2.1+git20110224.cb1268cb-1.dsc a0a6217af14c5d6db47433323d065429c6ff0d8761e840d4089eeb75184a2636 1197512 ccsm_0.9.2.1+git20110224.cb1268cb.orig.tar.gz abf55a97ffb55ee731ce2090f357ec4b5f91194f41b35bc665f08945d8056d61 4664 ccsm_0.9.2.1+git20110224.cb1268cb-1.debian.tar.gz 3de26eeb17ab1b83dd17f64fad44b5aece2135dcc0d55d64f6b971bc898f2616 1225380 compizconfig-settings-manager_0.9.2.1+git20110224.cb1268cb-1_all.deb Files: e89fc6136f456fd2b2591bf88283b4d2 1407 x11 extra ccsm_0.9.2.1+git20110224.cb1268cb-1.dsc af99e4ba1c73daf95e7d569bb9b3d521 1197512 x11 extra ccsm_0.9.2.1+git20110224.cb1268cb.orig.tar.gz b20d59d23b663d81678dcacf72826b6c 4664 x11 extra ccsm_0.9.2.1+git20110224.cb1268cb-1.debian.tar.gz d07fc89fe229fa104b40deff700c9954 1225380 x11 extra compizconfig-settings-manager_0.9.2.1+git20110224.cb1268cb-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1y2GUACgkQynjLPm522B0AgwCeKE0v7yyTQYICifzRO2IGF299 inEAoIUEh2zRDtRBbAb/FC8EV19tdvEV =fC6d -END PGP SIGNATURE- Accepted: ccsm_0.9.2.1+git20110224.cb1268cb-1.debian.tar.gz to main/c/ccsm/ccsm_0.9.2.1+git20110224.cb1268cb-1.debian.tar.gz ccsm_0.9.2.1+git20110224.cb1268cb-1.dsc to main/c/ccsm/ccsm_0.9.2.1+git20110224.cb1268cb-1.dsc ccsm_0.9.2.1+git20110224.cb1268cb.orig.tar.gz to main/c/ccsm/ccsm_0.9.2.1+git20110224.cb1268cb.orig.tar.gz compizconfig-settings-manager_0.9.2.1+git20110224.cb1268cb-1_all.deb to main/c/ccsm/compizconfig-settings-manager_0.9.2.1+git20110224.cb1268cb-1_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pw28v-00071q...@franck.debian.org
Accepted compiz-fusion-plugins-main 0.9.2.1+git20110224.g4a6783f-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 Mar 2011 07:02:19 + Source: compiz-fusion-plugins-main Binary: compiz-fusion-plugins-main Architecture: source i386 Version: 0.9.2.1+git20110224.g4a6783f-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-main - Compiz Fusion plugins - main collection Changes: compiz-fusion-plugins-main (0.9.2.1+git20110224.g4a6783f-1) experimental; urgency=low . [ Janos Guljas ] * New upstream release. * Bump standards to 3.9.1. * Switch to dpkg format 3.0 (quilt) * Rewrite debian/rules to use debhelper 7. * Removed debian/install file. * Updated debian/watch file. * Synchronize ubuntu patches from 0.9.2.1-0ubuntu2. * 06_bug326995.patch - Change default reflection scale value from 0.75 to 1.0. Anything else is unphysical * 08_disable_desktop_vpswitch.patch - Disable switching between desktop with mousewheel over desktop background as this option is too easily launched by mistake . [ Sean Finney ] * commit standard local-options for compiz packages * Update copyright info in debian/copyright Checksums-Sha1: c23b3a3e49271cefa4199b92720fc407197c8cd2 1852 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.dsc 47cc0e3ff979c183c33f2b2b691796fa73d73e8e 452815 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f.orig.tar.gz e19abcb31f31a74d5971a85e35ecebed0df00f48 5590 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.debian.tar.gz 5df81a71547c9e2e6dccf0b23e9fcaa2ed0464de 1362648 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1_i386.deb Checksums-Sha256: c93f706e8e51bf0d2a57b2bb866b5efeaea8c975ea6a7633236e40d96102740d 1852 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.dsc eaf63ce3b418b090a2a957d1f22dc9fc1d7a4088a67c7ba31d0abc42d06df39d 452815 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f.orig.tar.gz 90aabc88dfa276ad899fe6d0d68eb8b59e1d1730c0a690214b4fbdc269ac3130 5590 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.debian.tar.gz bf9fd30c764ba1e144dcbf47162da9d0b5c7b812326a49325b4b55dc1c59 1362648 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1_i386.deb Files: 1fe4168c3afdd876dc8ce563a193bdd4 1852 x11 extra compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.dsc 168cbf515adde03bbf10f501fc9693a7 452815 x11 extra compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f.orig.tar.gz c735b4dbb63d8e72f5b6a71379f8a1c0 5590 x11 extra compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.debian.tar.gz 798aeb3e0db50cb6838bc83a959df3b0 1362648 x11 extra compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1wj2MACgkQynjLPm522B1DmgCfY5OQxKtth/cBuy3MIEIGZHe2 4/4AnAjoO1kvnEuxqOR4z1hEntyAY9IL =LXHd -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.debian.tar.gz to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.debian.tar.gz compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.dsc to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1.dsc compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1_i386.deb to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-1_i386.deb compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f.orig.tar.gz to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pvznm-0008ii...@franck.debian.org
Accepted compiz-fusion-plugins-main 0.9.2.1+git20110224.g4a6783f-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 Mar 2011 22:35:10 + Source: compiz-fusion-plugins-main Binary: compiz-fusion-plugins-main Architecture: source i386 Version: 0.9.2.1+git20110224.g4a6783f-2 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-main - Compiz Fusion plugins - main collection Changes: compiz-fusion-plugins-main (0.9.2.1+git20110224.g4a6783f-2) experimental; urgency=low . * Fix FTBFS by adding Build-Dep on libglibmm-2.4-dev Checksums-Sha1: 23c7455b5ea4dfa1f8474c473b830184965fa9b8 1871 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.dsc 112e664dac38c2d70e577579f5dd9343c001683d 5725 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.debian.tar.gz d2d1f8fd7b02e325d893dfe8fbc7f0d6dc66a7ab 1362708 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2_i386.deb Checksums-Sha256: d8569fdefea3d9b788aaf472e5a7c0573d0ffc36991f0f5e39b9e06dfebc9e7e 1871 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.dsc 09af6c8c9ca6067be893b67fd2a1d87598a49bdf58ded1a0da08b4beadd3fb83 5725 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.debian.tar.gz bedfcf2b6747d8d4b0f0715d30e90160b97db61c129a9a75fe71f72862562863 1362708 compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2_i386.deb Files: b7029f3d7c88ed1656f6a16f258061dd 1871 x11 extra compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.dsc b268ef2c09eb0f1c4ee86abc234daa69 5725 x11 extra compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.debian.tar.gz 36f4a2d6ff8bc13ea590be292c2ff624 1362708 x11 extra compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1xa7EACgkQynjLPm522B14FQCdFjZZb9z5RNdox3ZVOuIJypLy GIIAnRdwgDuNV9BtQgil/Xh1kAcfplMv =3K6n -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.debian.tar.gz to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.debian.tar.gz compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.dsc to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2.dsc compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2_i386.deb to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.9.2.1+git20110224.g4a6783f-2_i386.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pve0k-5c...@franck.debian.org
Accepted compiz-fusion-plugins-extra 0.9.2.1+git20110224.e621355c-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 04 Mar 2011 23:33:21 + Source: compiz-fusion-plugins-extra Binary: compiz-fusion-plugins-extra Architecture: source i386 Version: 0.9.2.1+git20110224.e621355c-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-extra - Compiz Fusion plugins - extra collection Changes: compiz-fusion-plugins-extra (0.9.2.1+git20110224.e621355c-1) experimental; urgency=low . [ Janos Guljas ] * New upstream release. * Bump standards to 3.9.1. * Switch to dpkg format 3.0 (quilt) * Rewrite debian/rules to use debhelper 7. * Removed debian/install file. * Updated debian/watch file. Checksums-Sha1: 1dcd3646f39ba657d14dc2089d53cb4715822a67 1853 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.dsc 5172ca4ffe24b05af71f21dc3247231b92b5c902 2265866 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c.orig.tar.gz a2de5fb5596b56ad24fc842199db1c9bd5c7ecf1 4338 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.debian.tar.gz 46c2d1faff52c181560f352eff2d12834e42faed 3045782 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1_i386.deb Checksums-Sha256: 1e3117a64287c71a40c0c854f3d3ad94289ac6e67924c11f1220268de3031c39 1853 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.dsc b41384d6b71a4c08ff8ad8fa3f68e7e0d83e5204e3e5d239977a6fdf1100dc45 2265866 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c.orig.tar.gz 15910eefcbfe9a24738254fe92f092e76116916f3e4e90073fe9b093c0e41b40 4338 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.debian.tar.gz 684a5c534633d509eb1c87b4e19855d3b0ff2af69311a520fdcc1803cedfffd1 3045782 compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1_i386.deb Files: 64d3eec2c86fc2a67a75ab6d8a30aa27 1853 x11 extra compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.dsc 361bdc852a032103431039e150fa90df 2265866 x11 extra compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c.orig.tar.gz c24d939a7685790087b7a7f106cdb266 4338 x11 extra compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.debian.tar.gz ac24a9c61c2dc075e68f74e7f597218b 3045782 x11 extra compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1xd44ACgkQynjLPm522B2iqgCfZuQxx51UFA7wWg9s+EtteanY sVEAnjf4f3Plad7U8TvM4T4+hhIp8WMz =xVg1 -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.debian.tar.gz to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.debian.tar.gz compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.dsc to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1.dsc compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1_i386.deb to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c-1_i386.deb compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c.orig.tar.gz to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.9.2.1+git20110224.e621355c.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pveid-0005rc...@franck.debian.org
Re: enable/disable flags in /etc/default
On Thu, 2011-03-03 at 10:37 +0100, Tollef Fog Heen wrote: | Is there any reason against using a debconf script that asks if the | daemon should be started at boot time (or on which runlevels)? That | way you can easily modify the configuration with dpkg-reconfigure and | benefit from the debconf frontends. If you use a configuration management framework you probably don't care that much about debconf, since the debconfiscation of packages is fairly spotty and doesn't really lend itself to more complex setup. Imagine having a full nagios or munin configuration done through debconf and then imagine the preseed needed for that. Compare that with just dumping a configuration file somewhere. yes, but a proper debconfization should respect/reflect configuration files, so there shouldn't be need for any pre-seeding beyond having the files in place before installing :) Hooking update-rc.d into debconf is probably not the worst idea in the world, except update-rc.d is supposed to be run non-interactively and I think it's the wrong place in the stack to configure that functionaliy. i think it'd have to be a level higher, something kind of like dbconfig-common for initscripts. sean signature.asc Description: This is a digitally signed message part
Re: Lintian check for missing desktop files?
On Thu, 2011-03-03 at 23:01 +0100, Christoph Egger wrote: Sune Vuorela nos...@vuorela.dk writes: (isn't it only icewm and ratpoison and blackbox we might 'lose' by simply killing the debian menu) Last time I checked fluxbox and awesome where both debian menu only as well. instead of letting the tail wag the dog then with menu2desktop, wouldn't it be better to cater to these WM's/DE's by providing a desktop2menu? Still would feel like adding more layers where they should be removed though... signature.asc Description: This is a digitally signed message part
Re: enable/disable flags in /etc/default
On Tue, Mar 01, 2011 at 08:30:24PM +0100, Olaf van der Spek wrote: time the package is upgraded. i mean, it's not even that great for maintainer scripts, as evidenced by the total inconsistency for how developers are managing enabling/disabling of their services. Isn't that handled by DH for simple cases? i don't think the simple cases are the problems here. the problems arise on the maintainer side when they want to do anything different from the standard boilerplate dh stuff, like for example conditionally enable/disable a service. i actually attempted to do this The Right Way once with nsca, and it was really hard and involved lots of querying of invoke-rc.d. On Tue, Mar 01, 2011 at 11:58:44PM +0100, Stig Sandbeck Mathisen wrote: The short term issue is figuring out if the current practice of DONT_DISABLE_ENABLEMENT=false and friends in /etc/default is something we want to keep doing. i would guess that the numbers are already overwhelmingly in favor of abandoning this practice, if it were reasonably easy and straightforward to do. The long term issue is having a toolset, for the end user, for starting and stopping services, enabling and disabling services when booting, installing and upgrading, and setting a global policy for what the initial status of an installed service should be. i'd agree with Russ that doing this sooner rather than later would actually accelerate the abandonment of the practice.. that is i don't think most people are doing it because they think this is how it should be done, but rather i can't find a better way to do it. A RHEL service can be started manually, but will not be started at system boot unless explicitly configured to do so with chkconfig. and in our case it's renaming a symlink with sysv init, but i find it extremely irritating that we can't just provide a damn wrapper for that on out of the box installs so debian works like every other linux system out there with a reasonably sane chkconfig and/or service interface. On Tue, Mar 01, 2011 at 09:24:52PM -0600, Raphael Geissert wrote: Olaf van der Spek wrote: So what *is* the proper UI? Interesting that everyone talks about update-rc.d but it appears that nobody has read its documentation: A common system administration error is to delete the links with snip That means: # mv /etc/rc2.d/S??apache2 /etc/rc2.d/K00apache2 # insserv # this bit is not documented, it seems And that's it, apache2 won't be started on runlevel 2. and that's pretty much how it works on every other linux/unix like (sysv anyway, modulo changing some paths) system out there, at least under the hood. ...but that's not an interface, that's an implementation detail. a very much nonzero number of people are very confused when coming to debian because the tools that they've come to learn and use on other linux systems aren't present, and when they google or ask on support channels they're given a mixture of sometimes conflicting answers. i spoke with steve briefly on irc this morning and he mentioned that there were some (perhaps-unpublished?) notes from the DebConf BoF on init systems, does anyone still have a copy of those? is there any other central place where this stuff is being discussed? sean -- -- 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/20110302092127.gb27...@cobija.connexer.com
Re: enable/disable flags in /etc/default
hi zack, On Wed, Mar 02, 2011 at 09:41:18AM +0100, Stefano Zacchiroli wrote: without telling which those several tools are. According to this thread, the recommended tool among them is mv (in the hope that the sysadm knows by heart that they have to run insserv afterwards). there's a few packages that provide the same or similar kind of functionality, like sysv-rc-conf, bum, and rcconf. but none of these are anything remotely standard in terms of what people would be used to seeing, they'd have to find the package names and install them and learn how to use them, etc (and it may be that even with said utilities that they still have to run insserv, d'oh)... sean -- 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/20110302093138.gc27...@cobija.connexer.com
Re: enable/disable flags in /etc/default
On Tue, 2011-03-01 at 17:19 +0100, Olaf van der Spek wrote: So what *is* the proper UI? The sensible abstraction for this is 'service' - but it doesn't appear that service has support for enable/disable yet :( Do other distro's use service for this? actually i think chkconfig is more common than service for enabling/disabling. What's the reason update-rc.d is limited to maintainer scripts? well, for starters the interface sucks from a sysadmin point of view compared to stuff like chkconfig/service. i also think that there's (a perhaps shrunken, haven't checked in a while) set of things that you just can't do with update-rc.d, without having the changes lost the next time the package is upgraded. i mean, it's not even that great for maintainer scripts, as evidenced by the total inconsistency for how developers are managing enabling/disabling of their services. imho i think we need to step back and re-think the entire way we're currently handling init scripts, both from the packaging point of view and from the end-user/admin point of view. i think someone tried to start something like this up long ago[1] but it never picked up steam. maybe now that we have two new different init systems at the gates and also people wanting to have continued support of traditional sysv/file-rc, we should consider trying to revitalize that discussion? sean [1] this would be the initscripts-ng alioth project signature.asc Description: This is a digitally signed message part
Re: Potential memory leaks reported by Valgrind against some frequently used commands
On Tue, Mar 01, 2011 at 08:38:42PM -0600, Ron Johnson wrote: On 03/01/2011 06:19 AM, ximalaya wrote: BTW, I ever tried on Redhat Linux 9, no such problem. This is the interesting part. Is RH keeping their patches, or are upstream and other distros just not determining them worthwhile? given that RH9 is like what, 10 years old, i'd think that it's just as likely that the utilities just weren't leaky at the time. sean -- 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/20110302064339.ga27...@cobija.connexer.com
Accepted libcompizconfig 0.9.2.1+git20110226.78a7cc8c-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Feb 2011 09:36:37 + Source: libcompizconfig Binary: libcompizconfig-dev libcompizconfig0 Architecture: source i386 Version: 0.9.2.1+git20110226.78a7cc8c-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: libcompizconfig-dev - Configuration settings library for compiz-fusion - development fi libcompizconfig0 - Configuration settings library for compiz-fusion Changes: libcompizconfig (0.9.2.1+git20110226.78a7cc8c-1) experimental; urgency=low . * Incorporate Janos Guljas' compiz packaging work, thanks! Checksums-Sha1: bfb0fa10f4cec2e329d65ed702ae04ebc63fb085 1630 libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.dsc 5787180bb0a6123ed739b66e447b1605382b95f2 68671 libcompizconfig_0.9.2.1+git20110226.78a7cc8c.orig.tar.gz d83ce8dd96edb1b8cbb9ab50ac7e6a9c696212d3 4673 libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.debian.tar.gz d8d31f13c435759f2d0a289924e4b751a0810eba 13860 libcompizconfig-dev_0.9.2.1+git20110226.78a7cc8c-1_i386.deb f70f1ca0dcfa85698e89342b6e75667f337080bd 126362 libcompizconfig0_0.9.2.1+git20110226.78a7cc8c-1_i386.deb Checksums-Sha256: 97e8d3650ccd50d196648bcb69d39036117163b20429aa91e9ee110b1f1934ce 1630 libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.dsc 644257a24dce0600eab325166ddd2b890978e49c10a271e57c14efcf273fc8e8 68671 libcompizconfig_0.9.2.1+git20110226.78a7cc8c.orig.tar.gz 897daa2224da697cc299a8d929fa5a11f13a1efcf025253884069f246c9803c6 4673 libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.debian.tar.gz f10bacd0df60c178fd39c377743921e895ef3863c530c8ac884b6491bf85a84e 13860 libcompizconfig-dev_0.9.2.1+git20110226.78a7cc8c-1_i386.deb 067135ae70ca3a6fe6497a22f3b441b77f587e1a4af2013b9bb81fd677547079 126362 libcompizconfig0_0.9.2.1+git20110226.78a7cc8c-1_i386.deb Files: d921411272b168da5d56da726883cd69 1630 libs extra libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.dsc 5fa4834ea623f6e8c45212f21f888c25 68671 libs extra libcompizconfig_0.9.2.1+git20110226.78a7cc8c.orig.tar.gz 6248486b66fa214d0e523331beb6933b 4673 libs extra libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.debian.tar.gz 3eaf8c7ff0b49e04e2e407009d33bb07 13860 libdevel extra libcompizconfig-dev_0.9.2.1+git20110226.78a7cc8c-1_i386.deb 962ce33ab06d348941cceec7af675752 126362 libs extra libcompizconfig0_0.9.2.1+git20110226.78a7cc8c-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1qHsUACgkQynjLPm522B3H7wCcD5mCec+xBYoh2+Sbi+2LErH6 8wAAn2vimMnxoSIdcnQRd+gEx0VZhxYy =9LGn -END PGP SIGNATURE- Accepted: libcompizconfig-dev_0.9.2.1+git20110226.78a7cc8c-1_i386.deb to main/libc/libcompizconfig/libcompizconfig-dev_0.9.2.1+git20110226.78a7cc8c-1_i386.deb libcompizconfig0_0.9.2.1+git20110226.78a7cc8c-1_i386.deb to main/libc/libcompizconfig/libcompizconfig0_0.9.2.1+git20110226.78a7cc8c-1_i386.deb libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.debian.tar.gz to main/libc/libcompizconfig/libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.debian.tar.gz libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.dsc to main/libc/libcompizconfig/libcompizconfig_0.9.2.1+git20110226.78a7cc8c-1.dsc libcompizconfig_0.9.2.1+git20110226.78a7cc8c.orig.tar.gz to main/libc/libcompizconfig/libcompizconfig_0.9.2.1+git20110226.78a7cc8c.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ptdia-0001j7...@franck.debian.org
Accepted compizconfig-backend-gconf 0.9.2.1+git20110226.g861a1d4-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Feb 2011 10:28:35 + Source: compizconfig-backend-gconf Binary: compizconfig-backend-gconf Architecture: source i386 Version: 0.9.2.1+git20110226.g861a1d4-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-backend-gconf - Compiz Fusion configuration system - gconf backend Changes: compizconfig-backend-gconf (0.9.2.1+git20110226.g861a1d4-1) experimental; urgency=low . * Incorporate Janos Guljas' compiz packaging work, thanks! Checksums-Sha1: b12fdb0e2a2d355b55b2917897fc45217062b408 1692 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.dsc a2a3a888f2f54148094aeea352f00b0e97b0f154 20540 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4.orig.tar.gz 0bd8f474791b4c9c6aa1ffbd900fc368047de55c 2567 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.debian.tar.gz e11fd924bd0284a7a48c7c83e7368784c9ae4774 16582 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1_i386.deb Checksums-Sha256: 7e33ae8bb4bec63cf7c167cbb7f8353584cf6aeb8c20146862c4351fe58db0be 1692 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.dsc 21f3c35545ed003154ac83df7c63ddceb7ceec3ad7c2a94df67b09b6557ef427 20540 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4.orig.tar.gz ad31f35c5cdc95a071bfeec20bb1d7023d1d606345a508c7ce67bf882b43ae61 2567 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.debian.tar.gz 747d72cda399ef49e8c4ed858aa902fc5a518c598c0a3a8a177b6382bf3f66f9 16582 compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1_i386.deb Files: 88d63174ecc90b1307a073167bef5ee2 1692 x11 extra compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.dsc 678ad865695b982ab38fa7c368b2e2af 20540 x11 extra compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4.orig.tar.gz f386097310998d71c2f9cf86510e99bb 2567 x11 extra compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.debian.tar.gz afd8af58182bf424cc61d34b43b38e0a 16582 x11 extra compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1qKnMACgkQynjLPm522B2fxwCggJtSRD4KRs+7bdz1sL7pklUd 1ToAnj87J8VnEQZ7xY0FK16O48qFwsYJ =XxX6 -END PGP SIGNATURE- Accepted: compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.debian.tar.gz to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.debian.tar.gz compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.dsc to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1.dsc compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1_i386.deb to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4-1_i386.deb compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4.orig.tar.gz to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.9.2.1+git20110226.g861a1d4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pteep-0002a1...@franck.debian.org
Accepted compizconfig-backend-kconfig 0.9.2.1+git20110227.770eb464-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 27 Feb 2011 16:59:06 +0100 Source: compizconfig-backend-kconfig Binary: compizconfig-backend-kconfig Architecture: source i386 Version: 0.9.2.1+git20110227.770eb464-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-backend-kconfig - Compiz Fusion configuration system - kconfig backend Changes: compizconfig-backend-kconfig (0.9.2.1+git20110227.770eb464-1) experimental; urgency=low . * /o\ Brown paper bag upload. * Fix package names in debian/control * Fix references to -kconfig4 in debian/changelog Checksums-Sha1: bba0b013389684e34eaf5b80b0e80626981c56d6 1675 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.dsc 0cb2754f088f6f2549db0df1d649d5001e41561e 22266 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464.orig.tar.gz ff6ceb4c302c2fd7027cf0b42da33295718e7018 2980 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.debian.tar.gz e8cd86685ab65a96ebcd9e4c6a09592ef5e1f4d3 32066 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1_i386.deb Checksums-Sha256: 47d7d4a0e1b8b25a1e9076fdcdbb231c561803547b615e47b76bab7f2c046a57 1675 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.dsc 70b9214579df341b2d84aee39bf786aa24a18ec6a900e53fab3735ab4240c25d 22266 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464.orig.tar.gz d12968a3244fa27ac4eaba03c005ca760a85ace099a7557f13f164b75e93aac1 2980 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.debian.tar.gz 06f77e1648417980293c11eb2681ba616291471aa1c94fb0751985de9b31bff0 32066 compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1_i386.deb Files: 1d1a3977a16d3582d4e1877e80dcd7f9 1675 x11 extra compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.dsc 4044f6ca95404040c9fb20267f17d64e 22266 x11 extra compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464.orig.tar.gz 32ae452bf125e8f898602ff57007b87a 2980 x11 extra compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.debian.tar.gz acba534a27f4f3404f29ca252dbc0c6f 32066 x11 extra compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1qfPEACgkQynjLPm522B2MgACfWIw+kEN35pF/r/cl0YB3+VUt HNMAn0W+j/rCMiRZobwTN5ttyxR2BBm6 =04XE -END PGP SIGNATURE- Accepted: compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.debian.tar.gz to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.debian.tar.gz compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.dsc to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1.dsc compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1_i386.deb to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464-1_i386.deb compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464.orig.tar.gz to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.9.2.1+git20110227.770eb464.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ptjlz-da...@franck.debian.org
Re: Bug#612752: Bind fails to start if $OPENSSL_CONF is set
On Sat, 2011-02-26 at 14:32 +0100, Michael Banck wrote: The right way to do this is, IMNSHO, what systemd does and just have init handle starting and stopping the job. That ensures there's no inconsistency between boot-time starting and starting later by hand. Right, but it makes sense to support this in SSD (if possible) until we get there. There's a pretty high risk of regression with that though, isn't there? I imagine that some nonzero number of init scripts use exported variables to influence the daemons that they start (yes, they could be fixed, but since this would just be a temporary solution to begin with...) sean signature.asc Description: This is a digitally signed message part
Re: enable/disable flags in /etc/default
On Sat, 2011-02-26 at 21:44 +0100, Tollef Fog Heen wrote: I'd like us to decide on a policy about enable/disable flags in /etc/default in general. Either all daemons should have them or no daemons should have them, and if we have them, I think we should have the value in the default file should be standardised. Personally, I'd rather we didn't have them, as this is supposed to be controlled by the rcN.d links and if that interface is too hard for people we should fix that rather than invent multiple ways of disabling daemons, but the current mess is, well, a mess. +1 I think the existence of this FOO_ENABLED stuff is symptomatic of the fact that update-rc.d, at least by itself, isn't sufficient for the needs of packagers (let alone end-users, who often end up wrongly thinking that this is the tool they are supposed to use to enable/disable init scripts) sean signature.asc Description: This is a digitally signed message part
Accepted compiz 0.9.2.1+git20110226.f059fae9-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 26 Feb 2011 15:21:34 +0100 Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-gnome compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all i386 Version: 0.9.2.1+git20110226.f059fae9-1 Distribution: experimental Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz - OpenGL window and compositing manager - metapackage compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files Changes: compiz (0.9.2.1+git20110226.f059fae9-1) experimental; urgency=low . [ Sean Finney ] * Incorporate Janos Guljas' compiz packaging work, thanks! Checksums-Sha1: 5528567009e24b9749c0ccac4ef157dcd8dae537 2408 compiz_0.9.2.1+git20110226.f059fae9-1.dsc 8124e881c0c0959ed6f9f4015cc9b477ed7b9495 1446465 compiz_0.9.2.1+git20110226.f059fae9.orig.tar.gz b2654da80d4f6560635d888bcd6a5826c4d30a92 30913 compiz_0.9.2.1+git20110226.f059fae9-1.debian.tar.gz 2e6c27844f25815c2a2f024e928207b939b7b3b1 30168 compiz_0.9.2.1+git20110226.f059fae9-1_all.deb 2cc98b81fe4cdb0d4db501d698cf3f0ef82172d3 1161098 compiz-core_0.9.2.1+git20110226.f059fae9-1_i386.deb d4b4379b872de52fde3d8cc4660647d2f8020652 89204 compiz-dev_0.9.2.1+git20110226.f059fae9-1_i386.deb 8ceef38471e453ba386ac7d080c40d5990266295 330266 compiz-gtk_0.9.2.1+git20110226.f059fae9-1_i386.deb 47c9c876c5ed022669ef8328159345b79166ac29 98548 compiz-kde_0.9.2.1+git20110226.f059fae9-1_i386.deb aa85d1ada8480311308e1035f1dde2bd9a80281b 37006 compiz-gnome_0.9.2.1+git20110226.f059fae9-1_i386.deb 0d7745c23ed6659f34737d684bb97efd99c5127d 1101000 compiz-plugins_0.9.2.1+git20110226.f059fae9-1_i386.deb 6534bbba94b6e5d26cdb14c82a8ec2a09a2e11c4 50300 libdecoration0_0.9.2.1+git20110226.f059fae9-1_i386.deb 61524b6f38a3181a0e265adf9601ff8370ddc380 39762 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-1_i386.deb Checksums-Sha256: f1fef949940d01618185a612debd9f0c435a42b2fdaed5a28e7b9f9962fe191c 2408 compiz_0.9.2.1+git20110226.f059fae9-1.dsc 5f220678b05f1859c5df251e400084e39da7c0b9a12c3ba85b7cad2fd3dd5513 1446465 compiz_0.9.2.1+git20110226.f059fae9.orig.tar.gz 68cfa1000b6fd616c1df31df8f3b5da520da117f35fe7801de74788ab23c905e 30913 compiz_0.9.2.1+git20110226.f059fae9-1.debian.tar.gz c84e55203a17aa17ab96f43a5b834816608ed1f5466208882eefe064931a8222 30168 compiz_0.9.2.1+git20110226.f059fae9-1_all.deb 1960d8de6c1ac5e964aacdd37286ddbf69528de2803643f38d3903b2d5648db4 1161098 compiz-core_0.9.2.1+git20110226.f059fae9-1_i386.deb fbf8652f7607b3422ec1e36b407709d38d78dfdd4b10f23f6ea0b76c3c0952a0 89204 compiz-dev_0.9.2.1+git20110226.f059fae9-1_i386.deb cb418e465d4884d72f62e975877d6968703e7131d921e15570fd85e71a2d5cb4 330266 compiz-gtk_0.9.2.1+git20110226.f059fae9-1_i386.deb caa507b595ddd45f4f48c32413b5acd43f9a637bfa0847549b56542ace511065 98548 compiz-kde_0.9.2.1+git20110226.f059fae9-1_i386.deb 580a95652380578bf32cce8d420345c8c2bc32e6c8e4f91fe7bb7b1455b8711a 37006 compiz-gnome_0.9.2.1+git20110226.f059fae9-1_i386.deb 7ded9c8ccb5c6f658be25dccf7fe1ae0f68c58be4a52351c0fa6c93a8100254c 1101000 compiz-plugins_0.9.2.1+git20110226.f059fae9-1_i386.deb b187dd91eae3ff6c728b6695a7b033e0859b680797df32f52526b03a1232ecb6 50300 libdecoration0_0.9.2.1+git20110226.f059fae9-1_i386.deb 2b0064e23024aef2da312972177b78147571cf4d7340e7b68dd85b9e03b31d5c 39762 libdecoration0-dev_0.9.2.1+git20110226.f059fae9-1_i386.deb Files: 10ab8b59e3a698cbfb5240d0b6254703 2408 x11 optional compiz_0.9.2.1+git20110226.f059fae9-1.dsc 57e7964cd6f07ef7dc4c10c24749a1f0 1446465 x11 optional compiz_0.9.2.1+git20110226.f059fae9.orig.tar.gz 18904337ef8453fd5642f5b5efe1605d 30913 x11 optional compiz_0.9.2.1+git20110226.f059fae9-1.debian.tar.gz 3c33d1ce4ddc3b1cbb3f4616496cb29c 30168 x11 optional compiz_0.9.2.1+git20110226.f059fae9-1_all.deb 0e87d77d01fc34e1707708c720f5d61f 1161098 x11 optional compiz-core_0.9.2.1+git20110226.f059fae9-1_i386.deb 8eb03acb3886909b2f63c32fe00e3938 89204 x11 optional compiz-dev_0.9.2.1+git20110226.f059fae9-1_i386.deb 2a431cd7335d5e7e2bac421a9beb1e64 330266 x11 optional compiz-gtk_0.9.2.1+git20110226.f059fae9-1_i386.deb a321015f15609e9accc3235ca5d564f8 98548 x11 optional compiz-kde_0.9.2.1+git20110226.f059fae9-1_i386.deb b377ceac7f6bfcdbb1815955fc4ac545 37006 x11 optional compiz-gnome_0.9.2.1+git20110226.f059fae9-1_i386.deb 587f0ed4411982a4e1bad588caf31664 1101000 x11 optional compiz
Re: [php-maint] Bug#614413: re buildd's resolver and package's build deps
hi, On Mon, 2011-02-21 at 19:42 -0600, Raphael Geissert wrote: I disagree here. Alternatives in build-* relationships *are* mentioned by policy. In fact, there's even an example in section 7.1. There's also no stated guarantee *anywhere* (including release policy) that the package's build deps should be consistent, much less the result. Also, alternatives have been used ever since I joined the project for making backporting easier. Requiring stricter build-deps also affects that use case. for the record, full ACK on raphael's statements (maybe the PHP packages could use a bit of cleanup there post-squeeze-release though, but that'd be severity: wishlist). After thinking about it for a while, my opinion is that if anyone wants consistency to be guaranteed (e.g. in php's case that a rebuild doesn't end up linking php to libdb4.6 instead of libdb4.8) it should be handled on buildd/release team's side. The build deps as provided by the source package are valid. and we need *some* kind of predictable way to determine how they're resolved for specifically that reason. in the case of libdb, this is actually pretty significant because other libdb-linking apps link to php stuff (like, say, apache + apr + libapache-mod-php5), and we want everything using the same version. i would assume that first given should be default should be reasonable enough, and on the rare chance that something breaks, we get it handled with a binNMU or subsequent upload. i think the backport branching argument from roger is valid in the hypothetical sense, but i think there's a number of maintainers who support backporting only to the point that someone else is doing it and all they have to do is add some alternate build-deps, and they probably wouldn't bother otherwise. in the case of php, for example, i would hurl expletives at anyone who suggested that we start supporting yet another branch (and subsequently ask them if they were interested in joining pkg-php, muwahaha) backwards-compatible can also mean forwards-compatible too, which i suppose might make a package binNMU'able in some kind of transition where it would otherwise be needing a sourceful upload. anyway, just my 0.02 $LC_MONETARY fwiw :) sean signature.asc Description: This is a digitally signed message part
Accepted xmlrpc-c 1.16.33-2 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 20 Feb 2011 12:51:45 +0100 Source: xmlrpc-c Binary: libxmlrpc-c++4-dev libxmlrpc-c++4 libxmlrpc-c3-dev libxmlrpc-core-c3-dev libxmlrpc-core-c3 xmlrpc-api-utils Architecture: source i386 Version: 1.16.33-2 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: libxmlrpc-c++4 - A lightweight RPC library based on XML and HTTP [C++ libraries] libxmlrpc-c++4-dev - A lightweight RPC library based on XML and HTTP [C++ libraries] libxmlrpc-c3-dev - A lightweight RPC library based on XML and HTTP [C libraries] libxmlrpc-core-c3 - A lightweight RPC library based on XML and HTTP [C libraries] libxmlrpc-core-c3-dev - A lightweight RPC library based on XML and HTTP [C libraries] xmlrpc-api-utils - Generate C++ wrapper classes for XML-RPC servers Changes: xmlrpc-c (1.16.33-2) unstable; urgency=low . * Revert Remove kfreebsd patch, incorporated upstream * Update kfreebsd patch for latest upstream build system changes. Checksums-Sha1: 89c2959e18e6cbaa0a0be8b2494736a69d012549 1176 xmlrpc-c_1.16.33-2.dsc 12cbb2b397434de0efc3aa88edbe4b720a522482 8435 xmlrpc-c_1.16.33-2.diff.gz 0063a933ba04d41438898626f26a275e92a8a783 184748 libxmlrpc-c++4-dev_1.16.33-2_i386.deb d94e22e3b09efa19a0114d82d107a218a93e2f61 151114 libxmlrpc-c++4_1.16.33-2_i386.deb acd2f2ddaf1e156b7c57ab5b952d9372cdbacbc8 6458 libxmlrpc-c3-dev_1.16.33-2_i386.deb 7c0e5ee935fab171c407e2a31f03f1298bc7eaa2 261236 libxmlrpc-core-c3-dev_1.16.33-2_i386.deb cf47f4851f67b49a3d238fa79ea216c1f5246d25 165586 libxmlrpc-core-c3_1.16.33-2_i386.deb 274119f3432dd9135eb0e1d946b6c04e80887868 32940 xmlrpc-api-utils_1.16.33-2_i386.deb Checksums-Sha256: 25852ced8101247023ee225e89df94ca4214df6225a2b37488f65f3159ea33bf 1176 xmlrpc-c_1.16.33-2.dsc d79970a90d905dd922b25ce560b887af804431b588708b8e933ed7db19c7c49c 8435 xmlrpc-c_1.16.33-2.diff.gz c07814aa639f86e2166d2576588347d3d58d8e16d868a7fe71f7d74af513c06d 184748 libxmlrpc-c++4-dev_1.16.33-2_i386.deb 7f1af4619cec7802ff38ab51729f2a7fae7ccdec6839d4f5ef285e7245809e43 151114 libxmlrpc-c++4_1.16.33-2_i386.deb e586b9164e597600968365ffaf73510f3665533d2af021e96a1bcf5fd1706f41 6458 libxmlrpc-c3-dev_1.16.33-2_i386.deb 5a773f384d992723e69863f8795e07dafdf5f6d8f6d5058ad0925427d4393438 261236 libxmlrpc-core-c3-dev_1.16.33-2_i386.deb 05eb7118aee8c60f050f77192a2d7a03a41cd70b2dc429602719f1499c4e1f7f 165586 libxmlrpc-core-c3_1.16.33-2_i386.deb 4c2d45e11fec44245ed4c2c5b96250a438b06399fa145ebee95a2277ec7ad2bf 32940 xmlrpc-api-utils_1.16.33-2_i386.deb Files: 7a03ba963c8bce656673537285125e51 1176 libs optional xmlrpc-c_1.16.33-2.dsc 808f11e6562254c6af6dac184e8cef6c 8435 libs optional xmlrpc-c_1.16.33-2.diff.gz 7a120bf4a0f8a4f4401867a400b54617 184748 libdevel optional libxmlrpc-c++4-dev_1.16.33-2_i386.deb 63daefcb39b2fad387359d92ed9b 151114 libs optional libxmlrpc-c++4_1.16.33-2_i386.deb 7854517a54d1274d85d4cdbbaa2c8539 6458 libdevel optional libxmlrpc-c3-dev_1.16.33-2_i386.deb 0f1950faedf5f149918d806745d2e582 261236 libdevel optional libxmlrpc-core-c3-dev_1.16.33-2_i386.deb 1530b1432f26ff9a255aa238083c6f89 165586 libs optional libxmlrpc-core-c3_1.16.33-2_i386.deb c7f3df9ad3c473834fdaa24bd032c831 32940 devel optional xmlrpc-api-utils_1.16.33-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1hAr4ACgkQynjLPm522B2RWgCeM7I8Erfns8eTm9QlFZJPl6/a pOwAn3ukjgAVpTduoW7i6hgCD/fIwEzZ =bNKF -END PGP SIGNATURE- Accepted: libxmlrpc-c++4-dev_1.16.33-2_i386.deb to main/x/xmlrpc-c/libxmlrpc-c++4-dev_1.16.33-2_i386.deb libxmlrpc-c++4_1.16.33-2_i386.deb to main/x/xmlrpc-c/libxmlrpc-c++4_1.16.33-2_i386.deb libxmlrpc-c3-dev_1.16.33-2_i386.deb to main/x/xmlrpc-c/libxmlrpc-c3-dev_1.16.33-2_i386.deb libxmlrpc-core-c3-dev_1.16.33-2_i386.deb to main/x/xmlrpc-c/libxmlrpc-core-c3-dev_1.16.33-2_i386.deb libxmlrpc-core-c3_1.16.33-2_i386.deb to main/x/xmlrpc-c/libxmlrpc-core-c3_1.16.33-2_i386.deb xmlrpc-api-utils_1.16.33-2_i386.deb to main/x/xmlrpc-c/xmlrpc-api-utils_1.16.33-2_i386.deb xmlrpc-c_1.16.33-2.diff.gz to main/x/xmlrpc-c/xmlrpc-c_1.16.33-2.diff.gz xmlrpc-c_1.16.33-2.dsc to main/x/xmlrpc-c/xmlrpc-c_1.16.33-2.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pr8vn-mu...@franck.debian.org
Accepted cacti 0.8.7g-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 20 Feb 2011 15:33:58 +0100 Source: cacti Binary: cacti Architecture: source all Version: 0.8.7g-2 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: cacti - Frontend to rrdtool for monitoring systems and services Closes: 606062 Changes: cacti (0.8.7g-2) unstable; urgency=low . * import 2 new official upstream patches * Cherry-pick upstream fix for ping output parsing (Closes: #606062). * Lintian: - Update Standards-Version to 3.9.1 (no changes necessary) - Bump versioned Build-Dep on debhelper to = 5 - Update config and postrm maintainer scripts to run with set -e - Remove un-needed chmodding of php files in debian/rules - Ensure the non-php files in the scripts dir are executable - Update debconf template description to remove question from text. - Selectively fix executable permissions on some files in the cli dir - Include a README.source mentioning quilt * Update debconf choices and default value for webserver configuration * Update all debian/po files after changing debconf template Checksums-Sha1: 8102bb511c647c8fd5229a12782fb85a98e4b4be 1109 cacti_0.8.7g-2.dsc ed408b8999a67227b4764f4fdc8612ca9461fdb7 44969 cacti_0.8.7g-2.diff.gz d10cf0caab7fe71730129a4bde39fe367c9d0cf9 2085194 cacti_0.8.7g-2_all.deb Checksums-Sha256: fcc251fd145164d5a8f440eb67c91a16ac74e8371d310955cafd46e7f8ccbcfe 1109 cacti_0.8.7g-2.dsc 77be70a33ca1afcd2af5116ca49d96661220560c89617302faf7c0fcb8c05ef0 44969 cacti_0.8.7g-2.diff.gz 300cc81c949cfa86e62ccdb31aac5a50a4311b3746ef95e91dee0a759c2e313e 2085194 cacti_0.8.7g-2_all.deb Files: ae64cc76f324eb94de4c1f38ea9068f0 1109 web extra cacti_0.8.7g-2.dsc dcacd54368728065eaca6c0c9baff6b6 44969 web extra cacti_0.8.7g-2.diff.gz e168401298815c892869111a49777bbc 2085194 web extra cacti_0.8.7g-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1hKjwACgkQynjLPm522B1y7QCdEwEJ7U8UsHfCp5ZoIvw4M+Rj pU8AmwRwMt59GrKcO+pqQJsx4OjAJyYE =4tk1 -END PGP SIGNATURE- Accepted: cacti_0.8.7g-2.diff.gz to main/c/cacti/cacti_0.8.7g-2.diff.gz cacti_0.8.7g-2.dsc to main/c/cacti/cacti_0.8.7g-2.dsc cacti_0.8.7g-2_all.deb to main/c/cacti/cacti_0.8.7g-2_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pre4o-0001q6...@franck.debian.org
Accepted xmlrpc-c 1.16.33-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 19 Feb 2011 18:03:30 + Source: xmlrpc-c Binary: libxmlrpc-c++4-dev libxmlrpc-c++4 libxmlrpc-c3-dev libxmlrpc-core-c3-dev libxmlrpc-core-c3 xmlrpc-api-utils Architecture: source i386 Version: 1.16.33-1 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: libxmlrpc-c++4 - A lightweight RPC library based on XML and HTTP [C++ libraries] libxmlrpc-c++4-dev - A lightweight RPC library based on XML and HTTP [C++ libraries] libxmlrpc-c3-dev - A lightweight RPC library based on XML and HTTP [C libraries] libxmlrpc-core-c3 - A lightweight RPC library based on XML and HTTP [C libraries] libxmlrpc-core-c3-dev - A lightweight RPC library based on XML and HTTP [C libraries] xmlrpc-api-utils - Generate C++ wrapper classes for XML-RPC servers Closes: 524540 558972 565785 575560 Changes: xmlrpc-c (1.16.33-1) unstable; urgency=low . * New upstream release! (Closes: #558972, #524540, #575560). * Fix FTBFS on kfreebsd-* (originally included a new patch, but was subsequently fixed upstream, it seems) (Closes: #565785). * Split out library packages to deal with the SONAME changes. - libxmlrpc-core-c3: C libraries (unchanged SONAME) - libxmlrpc-c++4 (changed SONAME) * Include transitional packages for the dev packages to make a smooth path for binNMU's, but not the lib packages themselves, to avoid breaking existing packages. * Install files with --fail-missing in debian/rules to keep a closer eye on SONAME changes in the future. * Move the separately packaged api utilities into a single package * Move homepage information to policy-recommended Homepage field * Update Standards-Version to 3.9.1 * Set build-dependency on debhelper to = 5, as it should be Checksums-Sha1: c39bdc19b646df642da771c1d3a17f4ffe0a8d2e 1176 xmlrpc-c_1.16.33-1.dsc 9e0c638933ea67354fc6fda96e73fc61ee0b7e16 725130 xmlrpc-c_1.16.33.orig.tar.gz 59c0481d15dfd323695175ee2929ed3c66ffc956 7952 xmlrpc-c_1.16.33-1.diff.gz 8051909a225bf023474bddc0b447b30de779cfd0 184638 libxmlrpc-c++4-dev_1.16.33-1_i386.deb 23d019771657c1e2970ccef3cd93b4f24d93d49a 151026 libxmlrpc-c++4_1.16.33-1_i386.deb 1d9b143c0f65e2f1c7e008d147f9cb9969ca5c3e 6378 libxmlrpc-c3-dev_1.16.33-1_i386.deb 19fdd4cdcf171375c9af85a93e10e9f2acf8a7a3 261116 libxmlrpc-core-c3-dev_1.16.33-1_i386.deb 503990c7489c628b3b88343cd4654842e791d60e 165490 libxmlrpc-core-c3_1.16.33-1_i386.deb 2ec6dd9e1c47390ad07a9a2790234d87b05d0d39 32852 xmlrpc-api-utils_1.16.33-1_i386.deb Checksums-Sha256: 1051071bce027c02925af9b035e7a6bebbcd44246a9cbbd4c20f0a57dfe24cd5 1176 xmlrpc-c_1.16.33-1.dsc ebc388535d7d178f8225a7538898c671fc99e678975142dc141ee67440089447 725130 xmlrpc-c_1.16.33.orig.tar.gz 4344fd9625229556e32a81fbc9c1c8ddb39f9e06bddcdf6eaabbe6e44c46 7952 xmlrpc-c_1.16.33-1.diff.gz ddc00a5c115df4017d378cb10faf1b78685b40fd3fdf99de3c8107e440bfd821 184638 libxmlrpc-c++4-dev_1.16.33-1_i386.deb 37f87085a316bb02d7a8078d500c1589ac4a084b258b08db885b1741468eac16 151026 libxmlrpc-c++4_1.16.33-1_i386.deb c7553a0fc8973f8a6bbea9e79ff006c879e5cc3347585cd6eef5dbd11ff02788 6378 libxmlrpc-c3-dev_1.16.33-1_i386.deb 1a917b8d2a6e72c2cc4445687d553e7eb9d433cb782613663719ee1c8dff0882 261116 libxmlrpc-core-c3-dev_1.16.33-1_i386.deb 253222e7a7b01e37784fc7c377da19b98faacf811dd00737e0830c910f283e24 165490 libxmlrpc-core-c3_1.16.33-1_i386.deb 63e309d86cc943fb0ab42806828ac1b871217407c81c2c51d5388c62d8d3b86d 32852 xmlrpc-api-utils_1.16.33-1_i386.deb Files: 6233b834247c3465f0e51b99385f45e6 1176 libs optional xmlrpc-c_1.16.33-1.dsc 85bc381b970551389a80956c352e8d23 725130 libs optional xmlrpc-c_1.16.33.orig.tar.gz ebefc1c3413f3de0ed95eb141d48f12a 7952 libs optional xmlrpc-c_1.16.33-1.diff.gz 8f9abb9916cc1f06f2ddaf2f4f522d7c 184638 libdevel optional libxmlrpc-c++4-dev_1.16.33-1_i386.deb 62c91abe5dc393be05f4bc596be001c2 151026 libs optional libxmlrpc-c++4_1.16.33-1_i386.deb 11aa3e6a44e79cc62fa6ae7dbc585c53 6378 libdevel optional libxmlrpc-c3-dev_1.16.33-1_i386.deb 0cf36d23508e06dc4cee521e83a5ec0a 261116 libdevel optional libxmlrpc-core-c3-dev_1.16.33-1_i386.deb b5b621ecc039f81f0b9e30748dd63536 165490 libs optional libxmlrpc-core-c3_1.16.33-1_i386.deb e48091760707daa90c16a311a311aa15 32852 devel optional xmlrpc-api-utils_1.16.33-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk1gBukACgkQynjLPm522B3Y4wCfTnid2UC9dNYmpVLIKoFiV+pZ t0UAn2zOAJkvGfB4MjY+E6dGo0tHVgps =D3sP -END PGP SIGNATURE- Accepted: libxmlrpc-c++4-dev_1.16.33-1_i386.deb to main/x/xmlrpc-c/libxmlrpc-c++4-dev_1.16.33-1_i386.deb libxmlrpc-c++4_1.16.33-1_i386.deb to main/x/xmlrpc-c/libxmlrpc-c++4_1.16.33-1_i386.deb libxmlrpc-c3-dev_1.16.33-1_i386.deb to main/x/xmlrpc-c/libxmlrpc-c3-dev_1.16.33-1_i386.deb libxmlrpc-core-c3-dev_1.16.33-1_i386.deb to main/x/xmlrpc-c
Bug#613857: RFA: cacti + cacti-spine
Package: wnpp Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Due largely to the fact that I'm no longer using cacti on a regular basis, I think cacti and spine should get a new maintainer. Both packages are relatively up to date and in decent shape, and the upstream authors are responsive and pleasant to work with. I'm also open to starting up an alioth project for co-maintenance, and can sponsor/review uploads for a while if there's interested people who are not (though preferably are interested in becoming) uploading developers. Sean -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk1demoACgkQynjLPm522B1ETgCfYbs7VRKu4tCyKj8B9W8pYxUJ 4msAn0e0m/HqoCAIlAkIQyTTTIeNanwx =c2E4 -END PGP SIGNATURE- -- 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/20110217194347.29062.34035.reportbug@minnika
Accepted dbconfig-common 1.8.47 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 13 Feb 2011 13:48:57 + Source: dbconfig-common Binary: dbconfig-common Architecture: source all Version: 1.8.47 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: dbconfig-common - common framework for packaging database applications Closes: 475417 576533 591849 599374 608500 611820 Changes: dbconfig-common (1.8.47) unstable; urgency=low . * make _dbc_find_upgrades set -u safe * Fix version sorting logic bug on upgrade files in postinst. Thanks to Ghislain Mokolomboka mghisl...@dvidea.com (Closes: #611820) * Use defaults-file instead of defaults-extra-file when calling mysql. Thanks to Glennie Vignarajah glen...@glennie.fr (Closes: #576533) * Source dpkg/common (conditionally) in preinst before calling dbc_logline. Thanks to Klaus Zerwes kzer...@web.de (Closes: #608500) * Fix for dbc_mysql_createdb_encoding is missing. Thanks to Jérémy Lal kapo...@melix.org (Closes: #599374) * updates to (fi) debconf translations. Thanks to Esko Arajärvi e...@iki.fi (Closes: #475417) * updates to (de) debconf translations. Thanks to Raphael Bossek boss...@debian.org (Closes: #591849) Checksums-Sha1: 576eda5e163732fc81f7de22c947fdb94f1ccd5b 999 dbconfig-common_1.8.47.dsc e473bb86ffc748ad5530e8c0d6ee3aac7771e145 364476 dbconfig-common_1.8.47.tar.gz b83718f5c94642a5360170488de011887be70aa6 473862 dbconfig-common_1.8.47_all.deb Checksums-Sha256: 4cd5e65a4b241dde1a7615d86d2bf3e263f867871605bef84b1f9ca641028c22 999 dbconfig-common_1.8.47.dsc de4d944508f2de5de7425483489b9213d1be5dad9e048fda0fe3935c67b8b225 364476 dbconfig-common_1.8.47.tar.gz 309ab77780ee0c34819fba291577b248d0a0a87ebf119842b4fa3366685b657d 473862 dbconfig-common_1.8.47_all.deb Files: 08c8e9e06a82dd25a5792cc832300ae9 999 admin optional dbconfig-common_1.8.47.dsc 1ec86559fe8db342b07a80c684161931 364476 admin optional dbconfig-common_1.8.47.tar.gz 397c83b981031c2e72c05c3bf5c699df 473862 admin optional dbconfig-common_1.8.47_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk1X8DEACgkQynjLPm522B0fHgCaAuge8r1OSSUZdni3wirI02C9 2HYAoIlAxUcsarsKdeZQzF0FzgWHW8WZ =25iK -END PGP SIGNATURE- Accepted: dbconfig-common_1.8.47.dsc to main/d/dbconfig-common/dbconfig-common_1.8.47.dsc dbconfig-common_1.8.47.tar.gz to main/d/dbconfig-common/dbconfig-common_1.8.47.tar.gz dbconfig-common_1.8.47_all.deb to main/d/dbconfig-common/dbconfig-common_1.8.47_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1podhe-0001ad...@franck.debian.org
Accepted cacti-spine 0.8.7g-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 13 Feb 2011 22:05:45 + Source: cacti-spine Binary: cacti-spine Architecture: source i386 Version: 0.8.7g-1 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: cacti-spine - Multi-Threading poller for cacti Changes: cacti-spine (0.8.7g-1) unstable; urgency=low . * Imported Upstream version 0.8.7g * Add pristine-tar configuration hint to debian/gbp.conf * Remove 3 obsolete patches incorporated into latest upstream release * Include official patch unified_issues.patch * Refresh autofoo and upstream cruft lists for new release's files * Lintian: - Add a README.source - Bump Build-Depends on debhelper to = 5 (what it should have been) - Bump Standards-Version to 3.9.1 (no changes necessary) Checksums-Sha1: 2b5c4cb6fdc1c7c06795972507d420b2a03dc06e 1201 cacti-spine_0.8.7g-1.dsc 6f08f2f7734527a08afa5fc071dfaa5b1dbb0a57 592801 cacti-spine_0.8.7g.orig.tar.gz 58189e86b50bebcfce298e0a1c90197970797586 16096 cacti-spine_0.8.7g-1.diff.gz 699b2fa81ef40edb9c2af59f879099e3dd303f5b 53726 cacti-spine_0.8.7g-1_i386.deb Checksums-Sha256: 5a58c35f9793ce7f089474d7d94ba255d1fa16f256143cda62d3810452fefd99 1201 cacti-spine_0.8.7g-1.dsc 2735fbc1fc38d31651009d0a8d6ea121b29403d6020b13ba245ab4f3e0f6d561 592801 cacti-spine_0.8.7g.orig.tar.gz f1f71c4e7271475f9b8a3250873def828691bfec5a7e76fa7a0190c5cb8f2d32 16096 cacti-spine_0.8.7g-1.diff.gz 31cbe89a416bebe6bc541cf41e11c1dc964c5210899e7ab2e108b0c11d7aa558 53726 cacti-spine_0.8.7g-1_i386.deb Files: 7b84cdafc846ca850b33ecbfb6d039fe 1201 web extra cacti-spine_0.8.7g-1.dsc 22c2b1986c880b9c587876c18d5c3f9f 592801 web extra cacti-spine_0.8.7g.orig.tar.gz 39cdafaa3610a707ee5c422eefd3e265 16096 web extra cacti-spine_0.8.7g-1.diff.gz 462c8b061842ded56591622cd8897384 53726 web extra cacti-spine_0.8.7g-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk1YzXQACgkQynjLPm522B2DwwCfbTr6xTh8BwVMdFfJ0H+WG3BM upcAn0+vkW6tmbZ+fcBR+7A1uBcsCAnh =YgDJ -END PGP SIGNATURE- Accepted: cacti-spine_0.8.7g-1.diff.gz to main/c/cacti-spine/cacti-spine_0.8.7g-1.diff.gz cacti-spine_0.8.7g-1.dsc to main/c/cacti-spine/cacti-spine_0.8.7g-1.dsc cacti-spine_0.8.7g-1_i386.deb to main/c/cacti-spine/cacti-spine_0.8.7g-1_i386.deb cacti-spine_0.8.7g.orig.tar.gz to main/c/cacti-spine/cacti-spine_0.8.7g.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1posdd-0005jl...@franck.debian.org
Re: git-buildpackage branch names
hi jérémy, On Fri, Feb 11, 2011 at 09:46:13AM +0100, Jérémy Lal wrote: What's the best way to name gbp branches ? I thought of something like : 2.0 1.0.x mastermaster-1.0.x upstream upstream-1.0.x pristine-tar pristine-tar-1.0.x is there some common practice ? personally, i don't use master or references to specific upstream versions at all in the branching, and use something like the following: debian-experimental/upstream-experimental debian-sid/upstream-sid debian-squeeze/upstream-squeeze (etc). the pkg-php php.git would be a good example of that. i find this system is generally intuitive and trouble free, as long as you don't end up needing to support multiple versions of the software in the *same* release. fyi about git-buildpackage: you can put the branch names and any other release-specific stuff in ./debian/gbp.conf, on the respective debianized branch, which means you can have different configurations on a per-branch basis, and don't need to pass all those pesky options to gbp every time you run it :) sean -- 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/20110211093303.ga3...@cobija.connexer.com
Re: Removing dbconfig support ?
hi there, (for future reference dbconfig-common-de...@lists.alioth.debian.org is probably the proper place for this type of discussion). On Mon, Dec 06, 2010 at 11:31:22AM +0100, Pierre Chifflier wrote: Since the package is using dbconfig since a few versions, I'm now facing an upgrade problem before I can upload 0.78.1. For the moment, I'm thinking about removing dbconfig-common support and let all the configuration happen in the PHP scripts but I can't tell the consequences on previous installations. What is the best (not problematic) solution ? Any idea / help will be appreciated. one alternative i would suggest exploring is keeping dbconfig-common for the database/database-user creation (and maybe initial SQL bootstrap), and leave the upgrade task to the application if the app provides better support for that. for example, this is what is done in the cacti package, which also has some fairly complicated/robust upgrade tasks between versions. sean signature.asc Description: Digital signature
how to best handle this library update?
the package in question is xmlrpc-c, which provides among other things libxmlrpc-c3. this package contains runtime libraries for c and c++ applications. it has a fairly small (6, from a quick look) set of reverse dependencies. in the version in testing/unstable, these c/c++ libraries shared the same soname, though in hindsight this seems to have been more coincidence than design intention. in more recent versions of the upstream software, the c++ abi has been broken and the soname has correctly been incremented to refelct this. however the soname in the c libraries remains the same as the abi has not been broken there. so my question is, what is the most sane way to deal with this in the packaging, esp. with respect to their reverse dependencies? if it were also an abi break for the c libraries this would have been a bit easier as i could have split both libraries into new packages and there wouldn't be any breakage of the rdeps since the old library packages would remain in place. but since this isn't the case, the rdeps would see their needed libraries (the c++, old abi) vanish. i have the following ideas: 1) split out the c++ libraries, make the c++ library conflict with the older version of libxmlrpc-c3 (conflicting files) make the -dev package depend on both libraries, and hope that a half dozen binNMU's fix the problem quickly enough. 2) do (1) but also fake an abi break in the c libraries, renaming this package as well (i could leave the SONAME the same though, right? allowing the old libraries to stay while the transition takes place. 3) do no splitting for now, but rename the package to reflect the SONAME change (i.e. libxmlrpc-c6) and save the splitting for some other time. other ideas or comments of the above would be welcome... sean -- signature.asc Description: Digital signature
Re: Atlas proposal [and 1 more messages]
On Wed, Aug 25, 2010 at 06:46:18PM +0100, Ian Jackson wrote: Goswin von Brederlow writes (Re: Atlas proposal [and 1 more messages]): Just dumping the compiled files into /usr/lib/ I find quite unacceptable too. No, it is absolutely fine and it is what atlas-auto should do. It is a simple matter for its postinst and postrm to deal with these files explicitly. Plenty of other programs fiddle explicitly with files in /usr in their maintainer scripts. There is absolutely nothing wrong with that. /usr/lib is not special in this respect. as an admin i'd be very annoyed by that behavior, because there's no way for me to know what package the file came from then, or whether it was my own accidental actions that led to it (i.e. a make install gone wrong somewhere, etc), and no way to do checksum verifications. to me it seems that somewhere under /var/lib or /var/cache would be more appropriate... and just to throw something out there, there is an /etc/ld.so.conf.d directory, so the package could drop a file in there pointing at wherever the libraries were placed. sean signature.asc Description: Digital signature
Accepted cacti 0.8.7g-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 17 Aug 2010 22:22:02 +0200 Source: cacti Binary: cacti Architecture: source all Version: 0.8.7g-1 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: cacti - Frontend to rrdtool for monitoring systems and services Closes: 578909 592465 593203 Changes: cacti (0.8.7g-1) unstable; urgency=low . * New upstream release (Closes: #592465). * Update context in 05_no-adodb.patch to remove fuzz. * Remove official patches from previous release. * Remove 563955_undefined_index_local_data_id.patch, incorporated upstream. * Remove CVE-2010-2092.patch, incorporated upstream. * Import new batch of official upstream patches. * Update apache configuration to work in FastCGI deployments (Closes: #593203). - thanks to Thijs Kinkhorst th...@uvt.nl (Closes: #578909). Checksums-Sha1: 1e9503bc4cb4b306dd2401dbed1c837f51404b87 1113 cacti_0.8.7g-1.dsc a5a710653e158b1bc950de0a1e2c60ee364bf782 2236916 cacti_0.8.7g.orig.tar.gz d7691ebc2c73f12e82846228f8c10c11e034b9ec 40913 cacti_0.8.7g-1.diff.gz da9c8be754da608c41bfb38313cb1bb39475b566 2088372 cacti_0.8.7g-1_all.deb Checksums-Sha256: 7fb9e01a18e551170444b1e37bc5b6536cd472de9d0b507a073b2abcbdcd0b7c 1113 cacti_0.8.7g-1.dsc d09b3bf54f51bd42b2db0a62521cf6e408716978f75d6509ec56027c49c44585 2236916 cacti_0.8.7g.orig.tar.gz ad5c46fee9638305765933a04aebdce9a7e0525efcff00be01376e5cd547 40913 cacti_0.8.7g-1.diff.gz b28947304bf385e37b092cf39beda23d40c0226000b4e8f3e1a3f4be2282b394 2088372 cacti_0.8.7g-1_all.deb Files: d0dea1489f915ec4e108b49bc46dc01f 1113 web extra cacti_0.8.7g-1.dsc 268421cb1a58d3444f7ecbddb4c4b016 2236916 web extra cacti_0.8.7g.orig.tar.gz f1d4ddaf6c39d8631204d7947044c04f 40913 web extra cacti_0.8.7g-1.diff.gz 37ac481d47faaa08815367661bd95754 2088372 web extra cacti_0.8.7g-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkxq9BoACgkQynjLPm522B2PiACghtXwGB5YoYyyzC9+WzuMsLcv qOUAn2d27J/1SdfT06HHU8tqM67xwRfL =/BX7 -END PGP SIGNATURE- Accepted: cacti_0.8.7g-1.diff.gz to main/c/cacti/cacti_0.8.7g-1.diff.gz cacti_0.8.7g-1.dsc to main/c/cacti/cacti_0.8.7g-1.dsc cacti_0.8.7g-1_all.deb to main/c/cacti/cacti_0.8.7g-1_all.deb cacti_0.8.7g.orig.tar.gz to main/c/cacti/cacti_0.8.7g.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1olt46-0003bo...@franck.debian.org
Accepted cacti 0.8.7e-4 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 11 Jun 2010 21:08:02 + Source: cacti Binary: cacti Architecture: source all Version: 0.8.7e-4 Distribution: unstable Urgency: high Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: cacti - Frontend to rrdtool for monitoring systems and services Closes: 582691 Changes: cacti (0.8.7e-4) unstable; urgency=high . * Forward-port fix for CVE-2010-2092 from stable package (Closes: #582691) Checksums-Sha1: d51a68aaa1ee6ac526cc88806ecc4bdfa14c4ed6 1113 cacti_0.8.7e-4.dsc 915eed8bad812f208d95a47f5d044a2d8616b0ba 43472 cacti_0.8.7e-4.diff.gz 572e882682e309ea05ff5617ac9e7cfc4bb8c96b 2091656 cacti_0.8.7e-4_all.deb Checksums-Sha256: d03a807ff6eabe213e283ca9f2a3132ba26af66da53e5e2b3beb3aafbf91205f 1113 cacti_0.8.7e-4.dsc c5efd579412d3787a19513b51c57fa00fedb548972860cf40cae0f16705579a5 43472 cacti_0.8.7e-4.diff.gz a1e9b8de37dd5ef20db3d5d4061c7c390e822027066264ac3fa52669ceb6e3bd 2091656 cacti_0.8.7e-4_all.deb Files: 6140a88d6096208feef52d959077e7a0 1113 web extra cacti_0.8.7e-4.dsc 2a908a11c79ce3b2b9877ee29cc45744 43472 web extra cacti_0.8.7e-4.diff.gz ce9a9e2384748221090a78deaaa4a57e 2091656 web extra cacti_0.8.7e-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkwSppUACgkQynjLPm522B0A4gCdGJ2oICpnbeKXCed+zoYdMNPp MxwAn2c5cu9g/51z0xTckkk5MkqBPwyy =+JfS -END PGP SIGNATURE- Accepted: cacti_0.8.7e-4.diff.gz to main/c/cacti/cacti_0.8.7e-4.diff.gz cacti_0.8.7e-4.dsc to main/c/cacti/cacti_0.8.7e-4.dsc cacti_0.8.7e-4_all.deb to main/c/cacti/cacti_0.8.7e-4_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1on9j4-0004io...@ries.debian.org
Re: Re (2): lilo removal in squeeze / new lilo upstream
hi, this should all be prefaced with the disclaimer that i'm not actually using lilo at the moment, but i thought i'd throw in something due to some of the comments/posturing that i've been seeing here. On Mon, Jun 07, 2010 at 01:44:05AM +0400, William Pitcock wrote: Have fun. When you have a release that actually has merit, it can be reconsidered for inclusion in Debian. In the meantime, the original plan continues. actually, i don't think you have any say about what software can and can not be in debian, that is the sole privilege of ftp-master. your options are (a) to claim you still want to maintain the package and continue to do so, or (b) ask for its removal by ftp-master. given your comments here i think if you were to claim (a) there would be a decent case for someone to take to the tech-ctte. ftp-master, if they're aware of this argument, may just say why not orphan it instead?. but regardless, if someone else is interested they can just follow that removal with a new upload using their name as Maintainer, and then again it's up to ftp-master to accept or deny it. given that there may be an active upstream and maintainer, and the software is otherwise DFSG-compatible, i don't see why they would deny such a new upload. of course, it would be a lot nicer if you could just hand over the reins of the current package to those who have been asking for them, to avoid some un-needed overhead... sean ~ signature.asc Description: Digital signature
Re: correctly using other packages in postrm
On Mon, May 31, 2010 at 09:02:50PM -0700, Steve Langasek wrote: Hmm, what's the risk of changing it? I guess if dependencies are allowed to be purged when a package depending on them is removed-but-not-purged, dbconfig-common could obliterate config files that the depending package expects to still have around. Is that the concern? one of them, yeah. if dbc were to guarantee that it left no cruft behind, it would have to purge all the files it registered in proxy for packages when it was purged as well (which also means this would need to be tracked, which it isn't atm), but i don't feel confident enough without looking to know whether that would cause a problem in the depending packages' maintainer scripts. likewise, if dbc started purging these files as part of the postrm hook for the depending package, i'd be concerned that if this code was duplicated in the postrm script that it would result in a failure if it were run a a second time (i.e. the maintainer script already dealt with the file or tried to deal with it after calling the hook). it could be that they're both non-issues (now that i check, ucf seems to be fine with puring a config file that isn't registered, for example), but i'd want to do some kind of audit and loose testing to know for sure before i instabug a large number of packages. sean signature.asc Description: Digital signature
Re: Anounce of a secure repo for debian
On Mon, May 31, 2010 at 05:43:25PM +0200, Hilko Bengen wrote: You can find this repository at ftp://ftp.ethgen.de/pub/debian-security (deb ftp://ftp.ethgen.de/pub/debian-security sid unofficial-secured). To avoid confusion, please call your repository debian-security-ng. or perhaps debian-security-imho would be even better. sean signature.asc Description: Digital signature
Re: correctly using other packages in postrm
hi, On Mon, May 31, 2010 at 12:24:48PM -0700, Steve Langasek wrote: Does dbconfig-common know about all of these config files? I think it's the responsibility of dbconfig-common to track them, and remove them on purge. That way if your package is purged while dbconfig-common is installed, the config file is removed, and if dbconfig-common is removed before purge, a dpkg --purge dbconfig-common can still clean it up. i think in hindsight that's the way it *should* have been, but the documentation has suggested the contrary for long enough that i'm hesitant to break things, at least this late into the release cycle. sean signature.asc Description: Digital signature
Re: Archive area for clamz (Amazon MP3 downloader)
On Sun, May 30, 2010 at 09:40:48PM +, brian m. carlson wrote: The difference is that those tools provide a reasonable level of functionality with free data. Weather information is in the public domain because there's no originality to it. Most programs that display lyrics or album covers are music players, and there is free music (available in our archive, no less) that they can usefully play. so should amavis and spamassassin go to contrib because there aren't any documented DFSG-free virus and spam going through our mailservers? better yet, tell me which item in the DFSG says that a program can't be Free unless all the purpose or data handled by the software is also Free. hint: there isn't one. in fact, DFSG #6 (No discrimination against fields of endeavor) could even be applied to the exact opposite argument. ftp-master has the final say in what goes into the archive, but this really sounds like an over-zealous misinterpretation of the DFSG. i'd hope that this were a miscommunication and/or not the position of the entire team, because otherwise it would take a GR to overturn their position. sean signature.asc Description: Digital signature
Accepted cacti 0.8.7e-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 24 Apr 2010 17:54:20 +0200 Source: cacti Binary: cacti Architecture: source all Version: 0.8.7e-3 Distribution: unstable Urgency: high Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: cacti - Frontend to rrdtool for monitoring systems and services Closes: 578909 Changes: cacti (0.8.7e-3) unstable; urgency=high . * Import upstream fix for SQL injection vulnerability (no CVE assigned yet) - thanks to Thijs Kinkhorst th...@uvt.nl (Closes: #578909). Checksums-Sha1: 587a00b63bf43569d395cae2f89ba68b44565da9 1105 cacti_0.8.7e-3.dsc cbbf92a696e5840f1d250b6fbd3c9507ec333ef4 43070 cacti_0.8.7e-3.diff.gz f32921330007b7b3056aab33991729f30bc78aac 2090786 cacti_0.8.7e-3_all.deb Checksums-Sha256: 0e57455f338634e049e1181d2504eda44408b43c49639d48430275b0b07e 1105 cacti_0.8.7e-3.dsc 1cc97a6a7769341c5df3d828934f86345beefedfe18a6bdb0df273a473cc0c78 43070 cacti_0.8.7e-3.diff.gz ca0914488a2375b0eb1e1bb78a67d793192c78cbfc29a1d5a5d32e6925da511c 2090786 cacti_0.8.7e-3_all.deb Files: 469fad8cd95a2dceb227ede5c2193367 1105 web extra cacti_0.8.7e-3.dsc 4da387774e1e301bcae20f5e0a9e33a4 43070 web extra cacti_0.8.7e-3.diff.gz b742fc29018e301ecb52de84853077f4 2090786 web extra cacti_0.8.7e-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFL0y3HynjLPm522B0RAtP8AJ0Zvg7aMFFwj4qchbt3qhUrzbm90gCeNREN XjEcxwlaeHeXvWtEXKpLH5k= =oVT2 -END PGP SIGNATURE- Accepted: cacti_0.8.7e-3.diff.gz to main/c/cacti/cacti_0.8.7e-3.diff.gz cacti_0.8.7e-3.dsc to main/c/cacti/cacti_0.8.7e-3.dsc cacti_0.8.7e-3_all.deb to main/c/cacti/cacti_0.8.7e-3_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1o5jgb-0007ii...@ries.debian.org
Accepted dbconfig-common 1.8.46 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 28 Mar 2010 17:14:26 +0200 Source: dbconfig-common Binary: dbconfig-common Architecture: source all Version: 1.8.46 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: dbconfig-common - common framework for packaging database applications Closes: 546246 573069 Changes: dbconfig-common (1.8.46) unstable; urgency=low . * Fix error removing postgres databases and users (Closes: #573069) - thanks to J.M.Roth jmroth+deb...@iip.lu * Numerous fixes to unit test internals. * New unit tests covering some of the pgsql support. * Various misc fixes to pgsql support found by said unit tests :) * Fix pgsql createdb code to use template0 when encoding is specified - thanks to John Goerzen jgoer...@complete.org (Closes: #546246) * A few quotation and unset shell variable related fixes in mysql support found by updated unit tests. * Fix zsh support with unit tests * Remove test/tmp directory in debian/rules clean target Checksums-Sha1: d7b2c13f3e5e7ba3b63310ce847607467ea30dea 991 dbconfig-common_1.8.46.dsc 13be463c5f54dcc8e9391e964888aa353b1fa20d 357534 dbconfig-common_1.8.46.tar.gz cfad944992c45f14918aaa5867298947cb2acbb3 474034 dbconfig-common_1.8.46_all.deb Checksums-Sha256: 15b5d44732b00a84bfa2f4ed6030f70f63a208c59a6538d679fc9a128aff11c6 991 dbconfig-common_1.8.46.dsc f5ead9b421cbfa5e779cc94d43e109102824bd1feea9822f95080071c049c158 357534 dbconfig-common_1.8.46.tar.gz aa3803a4928ba2cd5510eaad306f76d05dc4c9a394498ce3b69f720388d369bb 474034 dbconfig-common_1.8.46_all.deb Files: ed89b8ad4a43446efe19c0f4bfe32f51 991 admin optional dbconfig-common_1.8.46.dsc 8371aed3d627c21b984387b4a3a4c150 357534 admin optional dbconfig-common_1.8.46.tar.gz f5afee048a88044168a0b87e4ecc70e8 474034 admin optional dbconfig-common_1.8.46_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLr3WYynjLPm522B0RAnhoAJ9ciq2Vx/paohmNVNffeFMVQS4uPwCfQhCq TuSywH5xsqo0fjLGnKdUwQs= =9emo -END PGP SIGNATURE- Accepted: dbconfig-common_1.8.46.dsc to main/d/dbconfig-common/dbconfig-common_1.8.46.dsc dbconfig-common_1.8.46.tar.gz to main/d/dbconfig-common/dbconfig-common_1.8.46.tar.gz dbconfig-common_1.8.46_all.deb to main/d/dbconfig-common/dbconfig-common_1.8.46_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ny4c5-0004k4...@ries.debian.org
Accepted dbconfig-common 1.8.45 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 23 Feb 2010 21:45:36 +0100 Source: dbconfig-common Binary: dbconfig-common Architecture: source all Version: 1.8.45 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: dbconfig-common - common framework for packaging database applications Closes: 443279 525371 542381 569139 Changes: dbconfig-common (1.8.45) unstable; urgency=low . * Change behavior for automated installs when no local database is available (Closes: #542381) * Make sure the admin always sees the purge database? question - thanks to Brett Profitt brett.prof...@gmail.com (Closes: #525371). * Remove original fix for #542381, as the second fix is better. * Bump debhelper compatibility level to 5 * Update lintian overrides * Update Standards-Version to 3.8.4 (no changes needed) * Use the upgrade prompt for migrating from non-dbc versions. (Closes: #569139) * Fix overzealous error checking which causes some settings not to migrate (Closes: #443279). Checksums-Sha1: 05e2045219a22aa2610864acf5d098c845a947e8 991 dbconfig-common_1.8.45.dsc b938631d9b31a53890d4059518c8de7e2041e65c 358680 dbconfig-common_1.8.45.tar.gz 135ff2872190c7319b2396976b8aeeb7a9d06733 475630 dbconfig-common_1.8.45_all.deb Checksums-Sha256: 6e4642ddb98046d9dfdfb80f1d8ae78e1a9c4a5c6fc45b47b669349fe93f7e9d 991 dbconfig-common_1.8.45.dsc e8218fa4212f7b79c63a9d40fa46170cf02ee6fe11d14b9b0797a30d03c678b9 358680 dbconfig-common_1.8.45.tar.gz 8796247d8d5c0c1bfe9af29dac66adc32e8f9cf36d8f8b0df657d312c32c8fcb 475630 dbconfig-common_1.8.45_all.deb Files: c8aaac43ab88fff3624fd1c7a98cce87 991 admin optional dbconfig-common_1.8.45.dsc 71be89b1ecfc09de32cacc5d2cffbc0c 358680 admin optional dbconfig-common_1.8.45.tar.gz a2c1ce74d2e5c11fb613911dedfd59d0 475630 admin optional dbconfig-common_1.8.45_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLhD7CynjLPm522B0RAl11AJ0QFDLUwhwQuN8OGNoDe+aIJiiIdwCfWDYC f23mTtAytUTsZs25h7841UY= =h8xp -END PGP SIGNATURE- Accepted: dbconfig-common_1.8.45.dsc to main/d/dbconfig-common/dbconfig-common_1.8.45.dsc dbconfig-common_1.8.45.tar.gz to main/d/dbconfig-common/dbconfig-common_1.8.45.tar.gz dbconfig-common_1.8.45_all.deb to main/d/dbconfig-common/dbconfig-common_1.8.45_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1nk2qr-00087k...@ries.debian.org
Re: Flag images
On Wed, Feb 17, 2010 at 08:53:56AM +0100, Yves-Alexis Perez wrote: On lun., 2010-02-15 at 12:03 -0800, Don Armstrong wrote: Flags are a poor representation of a particular language, and language selection is better handled using locales and content-negotiation anyway. [There are many examples where a country speaks many languages, and examples where multiple countries have the same language, but different dialects.] But flags (as an image) /are/ a quick way to identify a locale. Sometime they don't exactly overlap, thus the above problem, but they are still useful. Maybe not in content-negotiation, but for example to switch between locales easily, to switch keyboard mapping, to ask for some content different from the current locales, etc. And fwiw major software vendors have managed to overcome this trepidation and include flag icons for such purposes. I for one would love to get little flag icons back for displaying my keyboard layouts, as it's visually much quicker/easier to identify than looking for a two/three character piece of text on my task bar. sean signature.asc Description: Digital signature
Re: Downgrading a package to get it into upcoming release
On Wed, Feb 17, 2010 at 09:24:30AM +0100, Raphael Hertzog wrote: On Tue, 16 Feb 2010, Antonin Kral wrote: Epochs as well as +reverted will definitely work but looks a bit too hackish to me. Epochs have been designed precisely for this. It's not hackish... but they are somewhat ugly and some users do not understand them. imho epochs are intended for dealing with new versions that don't sort properly compared to previous versions, not for forcing users to downgrade their packages to a previous version, which could cause data loss and other non-fun stuff. sean signature.asc Description: Digital signature
Re: Downgrading a package to get it into upcoming release
hi, On Tue, Feb 16, 2010 at 12:10:16PM -0500, Asheesh Laroia wrote: You could use epochs to make the old version have a newer version number according to dpkg. I don't know how distasteful that is, though. it also might be a bit disruptive for those who have already installed the newer version of this package, don't know if you care about that. if you do, a suggestion: * keep the current development version in unstable * report an RC bug against the development version to keep it from testing, and ask the release team to boot it from testing if it's already there. * upload a new stable version to unstable, using a different naming scheme for source and binary packages, complete with the respective conflicts/replaces/provides etc. (i.e. Binary: mongodb-1.2) * once debian has released squeeze, upload transitional packages to force users to migrate to the development version. sean signature.asc Description: Digital signature
Accepted dbconfig-common 1.8.44 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 15 Feb 2010 22:09:21 +0100 Source: dbconfig-common Binary: dbconfig-common Architecture: source all Version: 1.8.44 Distribution: unstable Urgency: high Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: dbconfig-common - common framework for packaging database applications Closes: 567402 Changes: dbconfig-common (1.8.44) unstable; urgency=high . * Fix bashism in dpkg/config. (Closes: #567402) - thanks to Sylvain Le Gall gil...@debian.org * Bashism causes install failures, so urgency bumped. Checksums-Sha1: 23c45b7d28d17a3bcc1807b5ffd4fd01525be0c9 995 dbconfig-common_1.8.44.dsc 560b24f0818cb616e94de587a7fe43b397884ef9 355739 dbconfig-common_1.8.44.tar.gz c8d661b8192d7e23e2069549c9ca87a2da9d4ee2 473776 dbconfig-common_1.8.44_all.deb Checksums-Sha256: e3d1851dbb19412678385dac37d1c9ff6f4391391ecb1b009fcb93bcb71c41c3 995 dbconfig-common_1.8.44.dsc d62b07efaa71ba8416dd40cb6cf83496cb4ba56e785f6e4960f2319aa53068cc 355739 dbconfig-common_1.8.44.tar.gz 48da368c04a007ce8074572e94b3c18aa16a96a34e8be94baa6dc5a407ecb893 473776 dbconfig-common_1.8.44_all.deb Files: 9aad59ecaf3329849ed461b76925ebeb 995 admin optional dbconfig-common_1.8.44.dsc 2c21fa44a97649defc6cc2adc16c8ee9 355739 admin optional dbconfig-common_1.8.44.tar.gz 512d22dc42a53b4b4c644d779038b172 473776 admin optional dbconfig-common_1.8.44_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLebnlynjLPm522B0RArlsAJ97lTL7fn+kYU1mZ9w3NOgPDF0NFwCeIqtQ pwPebkZIeMY8XmgVyOzTX6s= =enyD -END PGP SIGNATURE- Accepted: dbconfig-common_1.8.44.dsc to main/d/dbconfig-common/dbconfig-common_1.8.44.dsc dbconfig-common_1.8.44.tar.gz to main/d/dbconfig-common/dbconfig-common_1.8.44.tar.gz dbconfig-common_1.8.44_all.deb to main/d/dbconfig-common/dbconfig-common_1.8.44_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1nh8pq-0003k2...@ries.debian.org
Re: JPEG 8 transition
On Sun, Feb 14, 2010 at 10:18:28AM +0100, Bill Allombert wrote: The first step is to fix packages that Depend on 'libjpeg62-dev'. They should Depend on 'libjpeg-dev' instead. Please do not make them Depend on 'libjpeg8-dev', or 'libjpeg-dev|libjpeg62-dev' or 'libjpeg-dev|libjpeg8-dev' or other combinaisons since this is useless and can only cause problem is the future. what about people wanting to support lenny backports? afaict libjpeg-dev is a virtual package in lenny, and thus we'd need libjpeg-dev|libjpeg62-dev. sean signature.asc Description: Digital signature
Accepted compizconfig-python 0.8.4-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Feb 2010 22:05:05 +0100 Source: compizconfig-python Binary: python-compizconfig Architecture: source amd64 Version: 0.8.4-2 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: python-compizconfig - Compizconfig bindings for python Changes: compizconfig-python (0.8.4-2) unstable; urgency=low . * Update Build-Depends against compiz-dev to = 0.8.4 for ABI bump. Checksums-Sha1: db8521426dcba8720706992067ef02ab78c68d78 1467 compizconfig-python_0.8.4-2.dsc 811f3c11ff3d477de9309663484d272bbd851143 3010 compizconfig-python_0.8.4-2.diff.gz 61305b5ff07146e7f72b0ac43105890633485b07 93334 python-compizconfig_0.8.4-2_amd64.deb Checksums-Sha256: eb08227e8254a6f8ac61733bcd0ebfa04c4bfa1eb4171f42a6c120fdf7470bd7 1467 compizconfig-python_0.8.4-2.dsc 40042a2a48bb7438c28b30d70481075e19573fdc43068f3f7673943f7cded147 3010 compizconfig-python_0.8.4-2.diff.gz 968ecd4ec94e327f7eeeb9395b978e13902a591ded818f7224f3cab0289c9286 93334 python-compizconfig_0.8.4-2_amd64.deb Files: aeb330f32538e1796bc28c34b03c3a74 1467 x11 extra compizconfig-python_0.8.4-2.dsc 136646e480af3f71857b3219402bebee 3010 x11 extra compizconfig-python_0.8.4-2.diff.gz e442a4c908d604de0c72e80149399de3 93334 x11 extra python-compizconfig_0.8.4-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdmQZynjLPm522B0RAs+WAJ9nwH/6BVeGxxfQ/U4t/IIITZfq+gCeJr7h xPNXc6cC9TZHRn6uHydedpg= =8y+A -END PGP SIGNATURE- Accepted: compizconfig-python_0.8.4-2.diff.gz to main/c/compizconfig-python/compizconfig-python_0.8.4-2.diff.gz compizconfig-python_0.8.4-2.dsc to main/c/compizconfig-python/compizconfig-python_0.8.4-2.dsc python-compizconfig_0.8.4-2_amd64.deb to main/c/compizconfig-python/python-compizconfig_0.8.4-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compiz-fusion-plugins-extra 0.8.4-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Feb 2010 21:58:40 +0100 Source: compiz-fusion-plugins-extra Binary: compiz-fusion-plugins-extra Architecture: source amd64 Version: 0.8.4-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-extra - Compiz Fusion plugins - extra collection Changes: compiz-fusion-plugins-extra (0.8.4-1) unstable; urgency=low . * New upstream release. * Update Build-Depends against compiz-dev to = 0.8.4 for ABI bump. Checksums-Sha1: be245f8fc6ac62de7f29734b1080d3e07ac772fd 1496 compiz-fusion-plugins-extra_0.8.4-1.dsc ba0ce6c2963e03e00f418d58e39370cdffe50817 3653817 compiz-fusion-plugins-extra_0.8.4.orig.tar.gz c33ef014b2064d348d803b4a26430dcaafb33503 4210 compiz-fusion-plugins-extra_0.8.4-1.diff.gz 392b94d6218d6a96943d34428dcb5df25cd366e9 3329806 compiz-fusion-plugins-extra_0.8.4-1_amd64.deb Checksums-Sha256: ad7929125e27be44a609f9b188eb845dd5aa0d8a8f1db926740751ebcaca 1496 compiz-fusion-plugins-extra_0.8.4-1.dsc afa3d4655f204ddbcdc5574ff1081fb744f83848cc2622aca78692eb1726ba4a 3653817 compiz-fusion-plugins-extra_0.8.4.orig.tar.gz 20aee075a2af75d6e6367bfda9232e17a6488b9c4116641027cb4cd072f914b1 4210 compiz-fusion-plugins-extra_0.8.4-1.diff.gz 1da7b14b041924ba6482ba58fd37d85802149f424171615c3bc29261919868f7 3329806 compiz-fusion-plugins-extra_0.8.4-1_amd64.deb Files: 61f5caaca2d202ff972bf97d4ed3678b 1496 x11 extra compiz-fusion-plugins-extra_0.8.4-1.dsc 9ea047c63ffa413f8cdd648d63fc37e2 3653817 x11 extra compiz-fusion-plugins-extra_0.8.4.orig.tar.gz 336612a7919a29ef3d1037aaed8b9d6d 4210 x11 extra compiz-fusion-plugins-extra_0.8.4-1.diff.gz 1509f40cd2615d46b544ebd2354b5c9b 3329806 x11 extra compiz-fusion-plugins-extra_0.8.4-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdUdTynjLPm522B0RAoNkAJ4+jNfa2DaG/jwt2CvxqbVr4/QCDACeJIvq IYAA9kkQbmc0OcMQ6TnW2ew= =0fDU -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-extra_0.8.4-1.diff.gz to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.4-1.diff.gz compiz-fusion-plugins-extra_0.8.4-1.dsc to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.4-1.dsc compiz-fusion-plugins-extra_0.8.4-1_amd64.deb to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.4-1_amd64.deb compiz-fusion-plugins-extra_0.8.4.orig.tar.gz to main/c/compiz-fusion-plugins-extra/compiz-fusion-plugins-extra_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compiz-fusion-plugins-unsupported 0.8.4-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 12 Feb 2010 16:03:06 +0100 Source: compiz-fusion-plugins-unsupported Binary: compiz-fusion-plugins-unsupported Architecture: source amd64 Version: 0.8.4-2 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-unsupported - Compiz Fusion plugins - unsupported collection Changes: compiz-fusion-plugins-unsupported (0.8.4-2) unstable; urgency=low . * Add extra install rules for new svg files in 0.8.4. * Incorporate quilt into the build system. * New patch upstream_git_set-include-order.patch backported from upstream git to fix FTBFS on systems with an older -unsupported package installed. . compiz-fusion-plugins-unsupported (0.8.4-1) unstable; urgency=low . * New upstream release. * Update Build-Depends against compiz-dev to = 0.8.4 for ABI bump. Checksums-Sha1: 9c9b0ddb9467732e6446e2bdc4a09c95c7c8cf7f 1580 compiz-fusion-plugins-unsupported_0.8.4-2.dsc 344590b331c35eaa866ea4aff98dd6cc53fbd038 1442746 compiz-fusion-plugins-unsupported_0.8.4.orig.tar.gz 3cc7453a85884d39e2c919883caf329d9eb9b80a 3728 compiz-fusion-plugins-unsupported_0.8.4-2.diff.gz dd02162ea94b5b2b6058ede82fbcecbd9dfd773b 1494802 compiz-fusion-plugins-unsupported_0.8.4-2_amd64.deb Checksums-Sha256: 2722e6d820b16cde1cb250bf2522e4b5795d58f50b58bab745adf595bf4c8393 1580 compiz-fusion-plugins-unsupported_0.8.4-2.dsc 627e88f0c9bce108de33193f9bf03412da5155e1ea0ea405eb23b58d2e731be8 1442746 compiz-fusion-plugins-unsupported_0.8.4.orig.tar.gz 47041c353c8abf709232e4ec275565a98375a2cc4229bcba3850144aede40a00 3728 compiz-fusion-plugins-unsupported_0.8.4-2.diff.gz 397190ce6f3d00445042f2fae5496cff14c9aa403421e7366711540944255140 1494802 compiz-fusion-plugins-unsupported_0.8.4-2_amd64.deb Files: 589f6dc20fd2c43e00d5c6cd760dbebf 1580 x11 extra compiz-fusion-plugins-unsupported_0.8.4-2.dsc a591dc0f5e517cc99c96137faab42e00 1442746 x11 extra compiz-fusion-plugins-unsupported_0.8.4.orig.tar.gz aa3b4829cb65545f66e66aa72bcaa667 3728 x11 extra compiz-fusion-plugins-unsupported_0.8.4-2.diff.gz a9d3ff5624cd8ff814a3e3fda83fe0a0 1494802 x11 extra compiz-fusion-plugins-unsupported_0.8.4-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD4DBQFLdW4dynjLPm522B0RAoVHAJdQtiY4+cWw5zfSSXd7NtX96oqyAJ9idsIX aYd0hY3HflO18/RC5V2r9A== =mKo4 -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-unsupported_0.8.4-2.diff.gz to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.4-2.diff.gz compiz-fusion-plugins-unsupported_0.8.4-2.dsc to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.4-2.dsc compiz-fusion-plugins-unsupported_0.8.4-2_amd64.deb to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.4-2_amd64.deb compiz-fusion-plugins-unsupported_0.8.4.orig.tar.gz to main/c/compiz-fusion-plugins-unsupported/compiz-fusion-plugins-unsupported_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted ccsm 0.8.4-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Feb 2010 17:46:32 +0100 Source: ccsm Binary: compizconfig-settings-manager Architecture: source amd64 Version: 0.8.4-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-settings-manager - Compizconfig Settings Manager Closes: 547810 Changes: ccsm (0.8.4-1) unstable; urgency=low . * New upstream release. * Make the package ready for Python 2.6; thanks to Josselin Mouette for the report and Sandro Tosi for the patch (Closes: #547810). Checksums-Sha1: 7d7be0fb2d5481199340514e6dc555c706dea6ba 1170 ccsm_0.8.4-1.dsc ad4ec120bbc76145ef67d1063c447c6a10eadc3a 623830 ccsm_0.8.4.orig.tar.gz ef4029842425b8660dbf897c00bca34b53ec1622 4200 ccsm_0.8.4-1.diff.gz 5fdf315e2f2500ebdaee4dfbfb2dab8c32b9a61b 643854 compizconfig-settings-manager_0.8.4-1_amd64.deb Checksums-Sha256: 2c6cbb7eda5e68c22c54015e3e592cd25231db188a75850eebe9c282e3903e9c 1170 ccsm_0.8.4-1.dsc 2cc16cb01b3279ac3bd61ea76536fdaf041512c85254973f991a6fef447100b2 623830 ccsm_0.8.4.orig.tar.gz ca0a97d3dff194664ba0bc6d8282c89c4660c2af0c11cacf3e49a0e25d8427e2 4200 ccsm_0.8.4-1.diff.gz c88581ace6ee8ede7b7f1a23867d351cf2c47ffceff02abff7e0d696095c334c 643854 compizconfig-settings-manager_0.8.4-1_amd64.deb Files: b3a12866afccd3600761321cf05a516b 1170 x11 extra ccsm_0.8.4-1.dsc 94c23254cee06e6f1f85ef8240726275 623830 x11 extra ccsm_0.8.4.orig.tar.gz c8ed82b8e86ae5fe87a9b74b7851cf73 4200 x11 extra ccsm_0.8.4-1.diff.gz 003b675d176fdc966a8b284c1cf2b97f 643854 x11 extra compizconfig-settings-manager_0.8.4-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdaCPynjLPm522B0RApHnAJwLrhNDabYlD3FB2iaH5Tg4Agf+agCfe+Fq xVxDbwftFZN/WQ16TzgAFBI= =c+Ze -END PGP SIGNATURE- Accepted: ccsm_0.8.4-1.diff.gz to main/c/ccsm/ccsm_0.8.4-1.diff.gz ccsm_0.8.4-1.dsc to main/c/ccsm/ccsm_0.8.4-1.dsc ccsm_0.8.4.orig.tar.gz to main/c/ccsm/ccsm_0.8.4.orig.tar.gz compizconfig-settings-manager_0.8.4-1_amd64.deb to main/c/ccsm/compizconfig-settings-manager_0.8.4-1_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compizconfig-backend-kconfig 0.8.4-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 12 Feb 2010 19:29:15 +0100 Source: compizconfig-backend-kconfig Binary: compizconfig-backend-kconfig Architecture: source amd64 Version: 0.8.4-2 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-backend-kconfig - Compiz Fusion configuration system - kconfig backend Changes: compizconfig-backend-kconfig (0.8.4-2) unstable; urgency=low . * Add lintian override for the private libraries with defined rpath . compizconfig-backend-kconfig (0.8.4-1) unstable; urgency=low . * New upstream release. * Update Build-Depends against compiz-dev to = 0.8.4 for ABI bump. * Remove patch force-link-against-lX11.patch, fixed upstream. Checksums-Sha1: e30aeb29e71ce39f7fd6a2ae3777b7208c364a75 1301 compizconfig-backend-kconfig_0.8.4-2.dsc 3a7cb440117327f34e260e4a6624028b50273d38 22002 compizconfig-backend-kconfig_0.8.4.orig.tar.gz 73b3bc447aa83aac06a7a197778c4242032204bb 2511 compizconfig-backend-kconfig_0.8.4-2.diff.gz 7681eb53fbee08569f3be50b92295f8292a7435a 34148 compizconfig-backend-kconfig_0.8.4-2_amd64.deb Checksums-Sha256: 39086beb1a72542df772d2db1e41928833e20c2a227bbb6143e9d152700b1e1a 1301 compizconfig-backend-kconfig_0.8.4-2.dsc 0eb0afe05716e5a515735ca3d7e92bae2c75902d26dc4f223890327ef9960c2b 22002 compizconfig-backend-kconfig_0.8.4.orig.tar.gz c55195c40da514e03ee284c2f18d80dc43c1a6d8ce0c114993d2fad2f52f9262 2511 compizconfig-backend-kconfig_0.8.4-2.diff.gz ef696d2211f8ae74094a9bba9fe5338186bfd47cab6884a216bb41806a4dea24 34148 compizconfig-backend-kconfig_0.8.4-2_amd64.deb Files: 27dfd0fd9ea30483e4dc53c32e827c79 1301 x11 extra compizconfig-backend-kconfig_0.8.4-2.dsc b97601eda888f0397232f6e6604b182a 22002 x11 extra compizconfig-backend-kconfig_0.8.4.orig.tar.gz 7b24c17cd8530ca22bede66f825c66e3 2511 x11 extra compizconfig-backend-kconfig_0.8.4-2.diff.gz addfa03f40c3e63cf6167aa24d1449b3 34148 x11 extra compizconfig-backend-kconfig_0.8.4-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdZ9cynjLPm522B0RAmVKAJ98ZaZsYqIXCll5U8W0KbyWtK/XkACeJ+rO yVhtmrUPtZEbaFzrj6g+XAo= =T9Fu -END PGP SIGNATURE- Accepted: compizconfig-backend-kconfig_0.8.4-2.diff.gz to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.4-2.diff.gz compizconfig-backend-kconfig_0.8.4-2.dsc to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.4-2.dsc compizconfig-backend-kconfig_0.8.4-2_amd64.deb to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.4-2_amd64.deb compizconfig-backend-kconfig_0.8.4.orig.tar.gz to main/c/compizconfig-backend-kconfig/compizconfig-backend-kconfig_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compiz 0.8.4-2 (source all amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Feb 2010 23:08:16 +0100 Source: compiz Binary: compiz compiz-core compiz-dev compiz-gtk compiz-kde compiz-gnome compiz-plugins libdecoration0 libdecoration0-dev Architecture: source all amd64 Version: 0.8.4-2 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz - OpenGL window and compositing manager compiz-core - OpenGL window and compositing manager compiz-dev - OpenGL window and compositing manager - development files compiz-gnome - OpenGL window and compositing manager - GNOME window decorator compiz-gtk - OpenGL window and compositing manager - Gtk window decorator compiz-kde - OpenGL window and compositing manager - KDE window decorator compiz-plugins - OpenGL window and compositing manager - plugins libdecoration0 - Compiz window decoration library libdecoration0-dev - Compiz window decoration library - development files Closes: 562027 562438 Changes: compiz (0.8.4-2) unstable; urgency=low . * Bump the dh_makeshlibs call to (= 0.8.4) . compiz (0.8.4-1) unstable; urgency=low . * New upstream release. . [ Sean Finney ] * Fix FTBFS: gconf/gconf-client.h: No such file or directory - thanks to Sebastian Harl tok...@debian.org (Closes: #562027, #562438) * Add compiz-decorator symlink for compatibility with ubuntu systems. * Make all patches DEP-3 formatted. * No longer keep the ubuntu patches logically separated from ours * Enable 010-disable-child-window-clipping.patch, as there's an ABI bump. Also, massage the patch a little so that it applies cleanly. * Synchronize ubuntu patches from 0.8.4-0ubuntu10 * 015_draw_dock_shadows_on_desktop.patch: - change decoration plugin to draw dock shadows only on the desktop window instead of on top of all other windows * 016_call_glxwaitx_before_drawing.patch: - Call glXWaitX before we start drawing to make sure X is done handling rendering calls. Suggested by Michel Dänzer to ensure we don't have any rendering glitches. * 017_always_unredirect_screensaver_on_nvidia.patch: - always unredirect gnome-screensaver when using nvidia, workaround for LP #160264 while still disabling unredirect fullscreen windows for nvidia users * 020_fix_focus.patch: - give back the focus to the previous focused window (LP: #455900) * 030_from_git_crash_fix_multiscreen.patch: - merge commit 24dea72a395071b533dcf66b2eef37b20522cbba to fix crash with wobbly windows in a multi screen setup * 031_from_git_fix_gnome_keybindings.patch: - fix gnome keybindings (terminal key) * 060_move_checks_to_compiz.patch: - add all relevant checks from compiz-manager to compiz itself Compiz already checks for almost everything it needs so there is no need to check twice. * 061_KWD_stubs.patch (updated locally to remove fuzz): - Horrible hack to define empty stubs for some new pure virtual functions in KWD::Window, to fix FTBFS. * The following patches have been updated to cleanly apply: * 014-fix-gtk-window-decorator-no-argb-crash.patch * 015_optional-fbo.patch * ubuntu/010-disable-child-window-clipping.patch * ubuntu/013-add-cursor-theme-support.patch * ubuntu/018_use_metacity_settings.patch * ubuntu/029_default_options * ubuntu/035_ignore_workspaces * ubuntu/037_fullscreen_stacking_fixes.patch * ubuntu/049-damage-report-non-empty.patch * ubuntu/050_stacking.patch * Transition from compiz-manager to compiz binary for /usr/bin/compiz * Remove all patches to the embedded compiz-manager script * 028_compiz_manager_blacklist * 029_compiz_manager_decoration.patch * 029_compiz_manager_nvidia_settings.patch * 030_compiz_manager_multi_display * 031_compiz_manager_extra_blacklist_support * 032_compiz_manager_add_gnomecompat * 033_compiz_manager_xdg_dirs * 042-compiz-manager-default-plugin * 046_compiz_manager_second_screen.patch Checksums-Sha1: 8a2088b92e9a9c88fffedef25f8131e9bb9d797c 2045 compiz_0.8.4-2.dsc 9da2fa118a6c7b832755e16a7aa49ef1afa58c6a 1383316 compiz_0.8.4.orig.tar.gz 8f871c90cd9edaf31fc5c78ca9c6cdddc20f5611 29003 compiz_0.8.4-2.diff.gz ab7f078985eb634a2ff1661cee1279ee582ef363 29326 compiz_0.8.4-2_all.deb d790c9e59198678384cd748e21c3e3e49ba0c9ec 1101144 compiz-core_0.8.4-2_amd64.deb 678da4f8863daf2f6b8b2fb6ef29c27460882b7b 57176 compiz-dev_0.8.4-2_amd64.deb 9e87cb0ca1566b6f81716cf397ccdccf98dbc011 91248 compiz-gtk_0.8.4-2_amd64.deb 84b4c8008fc269afb00af43f8e4e49378cf7ad89 101962 compiz-kde_0.8.4-2_amd64.deb b00be8fdd1a80fd12e93704f9c91ef8a3b1b878b 41140 compiz-gnome_0.8.4-2_amd64.deb bf8024a4ab78f0b9752f5abbb90977a235effca2 533184 compiz-plugins_0.8.4-2_amd64.deb
Accepted compiz-fusion-bcop 0.8.4-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 04 Feb 2010 18:04:13 +0100 Source: compiz-fusion-bcop Binary: compiz-fusion-bcop Architecture: source all Version: 0.8.4-1 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-bcop - Compiz Fusion option code generator Changes: compiz-fusion-bcop (0.8.4-1) unstable; urgency=low . * New upstream release Checksums-Sha1: db37decce973c39b15e1ecf7f73f6e839860b8fc 1093 compiz-fusion-bcop_0.8.4-1.dsc ba4af52434176da5a9b8186bb787627d46d1d09c 17803 compiz-fusion-bcop_0.8.4.orig.tar.gz 2f73ac42f184bd8e806f9654017519e2d99d0cc3 2082 compiz-fusion-bcop_0.8.4-1.diff.gz df924b25e30e0058b0b37ac555e6e3cbd0103fea 9124 compiz-fusion-bcop_0.8.4-1_all.deb Checksums-Sha256: 4a251b5c654b477329fec01888e7db63de6479f8f2c77ad0c57d3a0e7210298e 1093 compiz-fusion-bcop_0.8.4-1.dsc 72873384678563a59fb47422b67a534a960e31b87f6d6941846ae2f2b477b067 17803 compiz-fusion-bcop_0.8.4.orig.tar.gz 4a023ccd7754ddcc0830c4df24afcf79db73891b78582b9860098c04c14bc4b5 2082 compiz-fusion-bcop_0.8.4-1.diff.gz be7b7cc0a5c2ae43e6a88734e743611bea4e02f93e011db61306faee0bddaea1 9124 compiz-fusion-bcop_0.8.4-1_all.deb Files: a731eee5071a7994dc8fd1a8064f4fc6 1093 x11 extra compiz-fusion-bcop_0.8.4-1.dsc b02112d32f5aef87ce5eb64e10bce23c 17803 x11 extra compiz-fusion-bcop_0.8.4.orig.tar.gz 77cdf4e597954811233a9ca132807c5c 2082 x11 extra compiz-fusion-bcop_0.8.4-1.diff.gz 290edbcd6925f22263570d9f795cb636 9124 x11 extra compiz-fusion-bcop_0.8.4-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdI/AynjLPm522B0RAh/TAJ93WlQ8k9Fx7LIQtEtgakGeXqeT+QCeOnoE T7+zK8dvojKCfpZHPUahDUg= =kWoZ -END PGP SIGNATURE- Accepted: compiz-fusion-bcop_0.8.4-1.diff.gz to main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.4-1.diff.gz compiz-fusion-bcop_0.8.4-1.dsc to main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.4-1.dsc compiz-fusion-bcop_0.8.4-1_all.deb to main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.4-1_all.deb compiz-fusion-bcop_0.8.4.orig.tar.gz to main/c/compiz-fusion-bcop/compiz-fusion-bcop_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compizconfig-backend-gconf 0.8.4-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Feb 2010 21:52:41 +0100 Source: compizconfig-backend-gconf Binary: compizconfig-backend-gconf Architecture: source amd64 Version: 0.8.4-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compizconfig-backend-gconf - Compiz Fusion configuration system - gconf backend Changes: compizconfig-backend-gconf (0.8.4-1) unstable; urgency=low . * New upstream release. . [ Sean Finney ] * Update Build-Depends against compiz-dev to = 0.8.4 for ABI bump. . [ Loïc Minier ] * Add Vcs-Git-* control headers Checksums-Sha1: a3c552a0bc387270fb6697a555fef74c24d97c7e 1472 compizconfig-backend-gconf_0.8.4-1.dsc 863019b9c12ad9b4351af06e5ea14421d9d4ae94 20980 compizconfig-backend-gconf_0.8.4.orig.tar.gz 341ae318e09d6bedd770ff60ada0c6f64dd2 2329 compizconfig-backend-gconf_0.8.4-1.diff.gz 538e307957625bbe492d35d95ba6bdac9c4f874b 18074 compizconfig-backend-gconf_0.8.4-1_amd64.deb Checksums-Sha256: 699c56a240695fa12ad3cd71fc2af2528c000234d2242eb22d93e5041688132d 1472 compizconfig-backend-gconf_0.8.4-1.dsc a84949c3b4897d4c328605f4a093adfe8fd323e9fb4171193217c7504fd8891c 20980 compizconfig-backend-gconf_0.8.4.orig.tar.gz 8d844bceab5798d64bbf84e6d7dc4126f6127aefd6393eb1c51e8fa6cd650faf 2329 compizconfig-backend-gconf_0.8.4-1.diff.gz 1b5429e7fd8c420d16c505388dce58b0411df3c59a9965ed1d5e95c4e77b0f5b 18074 compizconfig-backend-gconf_0.8.4-1_amd64.deb Files: 86940ad6a15ef737a4a48c52f9b95424 1472 x11 extra compizconfig-backend-gconf_0.8.4-1.dsc c868b420d79654989bc1bf86197959ab 20980 x11 extra compizconfig-backend-gconf_0.8.4.orig.tar.gz 8801db2d6edc32b21f21961e16b36acf 2329 x11 extra compizconfig-backend-gconf_0.8.4-1.diff.gz 11caa537cb57642abadbc46af2b785a0 18074 x11 extra compizconfig-backend-gconf_0.8.4-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdI/uynjLPm522B0RAs4TAJ980j82czIb9p/+jOXlpYSGwMmvZwCfa4wW gaeauFvhErseaFx8lpm4NMg= =J4oF -END PGP SIGNATURE- Accepted: compizconfig-backend-gconf_0.8.4-1.diff.gz to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.4-1.diff.gz compizconfig-backend-gconf_0.8.4-1.dsc to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.4-1.dsc compizconfig-backend-gconf_0.8.4-1_amd64.deb to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.4-1_amd64.deb compizconfig-backend-gconf_0.8.4.orig.tar.gz to main/c/compizconfig-backend-gconf/compizconfig-backend-gconf_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted libcompizconfig 0.8.4-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Feb 2010 20:33:19 +0100 Source: libcompizconfig Binary: libcompizconfig-dev libcompizconfig0 Architecture: source amd64 Version: 0.8.4-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: libcompizconfig-dev - Configuration settings library for compiz-fusion - development fi libcompizconfig0 - Configuration settings library for compiz-fusion Closes: 531797 Changes: libcompizconfig (0.8.4-1) unstable; urgency=low . * New upstream release. - Includes fix for basic_string::_S_construct NULL not valid. (Closes: #531797) * Update Build-Depends against compiz-dev to 0.8.4-1 for ABI bump. Checksums-Sha1: b603fc0ac70e89bd50452a8c705f371594a5167d 1380 libcompizconfig_0.8.4-1.dsc d2a3a312f3e17a6294e00fd7fadfb87e8c9eb248 70419 libcompizconfig_0.8.4.orig.tar.gz a2e22105436021285a829b5b2f9540aff6f27109 3892 libcompizconfig_0.8.4-1.diff.gz 5e530210b11ea20adbfe44bee0b174bb8f886ccf 130076 libcompizconfig-dev_0.8.4-1_amd64.deb f46d0c2773a46530ed2f402ea71c720929e85877 121192 libcompizconfig0_0.8.4-1_amd64.deb Checksums-Sha256: 184f825f24ba26e65d69d43cd3d2280282b9cf9f7e2cfd8ea317b25688c653c4 1380 libcompizconfig_0.8.4-1.dsc 57ce03be346b7ab88d1831639a5f9ef94c3bfe4ba9621c6dfb1c6857ad64f4f4 70419 libcompizconfig_0.8.4.orig.tar.gz af95123bc1ae13692f6750d4bdb5d6a063a12466d32d9e885d8063f4360f4799 3892 libcompizconfig_0.8.4-1.diff.gz 19e6dd3cd26f8cb1e246e107871cdfa2b0f4f7cf3856ad4a514d3b9486352242 130076 libcompizconfig-dev_0.8.4-1_amd64.deb 6271676442b1628fc99f3b04c112748995daa9f4eaa345a9e365cf2d734a9bd2 121192 libcompizconfig0_0.8.4-1_amd64.deb Files: a1c1e628d2b11f58661c3126e50e5924 1380 libs extra libcompizconfig_0.8.4-1.dsc 41cf29a4a2f79ef48c211c9142daad25 70419 libs extra libcompizconfig_0.8.4.orig.tar.gz 15f28694f3db21f80c0a2be610c9003b 3892 libs extra libcompizconfig_0.8.4-1.diff.gz 8c6dcded616cd8490e012c1a100179bc 130076 libdevel extra libcompizconfig-dev_0.8.4-1_amd64.deb c2f7a9ffec492a5f02d6fb7db79d62e9 121192 libs extra libcompizconfig0_0.8.4-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdI+iynjLPm522B0RAqbuAJ96JybWvD63Kw0h5PSXFGQlK1mKcgCdGW5A z1rGTa5KLvCZPZUqeP/XkfI= =BhIH -END PGP SIGNATURE- Accepted: libcompizconfig-dev_0.8.4-1_amd64.deb to main/libc/libcompizconfig/libcompizconfig-dev_0.8.4-1_amd64.deb libcompizconfig0_0.8.4-1_amd64.deb to main/libc/libcompizconfig/libcompizconfig0_0.8.4-1_amd64.deb libcompizconfig_0.8.4-1.diff.gz to main/libc/libcompizconfig/libcompizconfig_0.8.4-1.diff.gz libcompizconfig_0.8.4-1.dsc to main/libc/libcompizconfig/libcompizconfig_0.8.4-1.dsc libcompizconfig_0.8.4.orig.tar.gz to main/libc/libcompizconfig/libcompizconfig_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted compiz-fusion-plugins-main 0.8.4-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 11 Feb 2010 21:56:57 +0100 Source: compiz-fusion-plugins-main Binary: compiz-fusion-plugins-main Architecture: source amd64 Version: 0.8.4-1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: compiz-fusion-plugins-main - Compiz Fusion plugins - main collection Closes: 561565 Changes: compiz-fusion-plugins-main (0.8.4-1) unstable; urgency=low . * New upstream release. - Fixes crash with empty titles and thumbnail previews (Closes: #561565). Thanks: Klaus Knopper * Update Build-Depends against compiz-dev to = 0.8.4 for ABI bump. * Remove nvidia-workaround.patch, incorporated upstream. * Import 10-fix_plasma_previews.patch from ubuntu Checksums-Sha1: f9007e00b76e6b1b37508c37bc8390617b77 1483 compiz-fusion-plugins-main_0.8.4-1.dsc 2871b19232b990720e6679e2acf018585c043cd7 1532562 compiz-fusion-plugins-main_0.8.4.orig.tar.gz 8bd451dda54e4d68d9a6b8fc1b7e7adaaa8229af 3577 compiz-fusion-plugins-main_0.8.4-1.diff.gz 59df789f0b518f42316a49a07ebdb6686b3585bf 1966396 compiz-fusion-plugins-main_0.8.4-1_amd64.deb Checksums-Sha256: 601639ee586767dc1d2494ef343aaa7a4ebe0b474e6c77ce3d25e7e786c0ecc9 1483 compiz-fusion-plugins-main_0.8.4-1.dsc 1b436279021788b963293216359c5df2912994dac5df0055fafacf0588015e49 1532562 compiz-fusion-plugins-main_0.8.4.orig.tar.gz 2809915fc7c891b638123c71c038ec42f8b46f7e7e78790048b6f0129d5578aa 3577 compiz-fusion-plugins-main_0.8.4-1.diff.gz 826d08240f5121be7db6adf25e3690fa1e348f0c47ffae3705c95144b7e56c44 1966396 compiz-fusion-plugins-main_0.8.4-1_amd64.deb Files: a6dadd69ce5babfbefd598a5f45fae49 1483 x11 extra compiz-fusion-plugins-main_0.8.4-1.dsc a24ac479499e0775cdf02cfee62427d4 1532562 x11 extra compiz-fusion-plugins-main_0.8.4.orig.tar.gz 506e6a4db87bf7e630f67bd8d9f13372 3577 x11 extra compiz-fusion-plugins-main_0.8.4-1.diff.gz cf3f4dfb62008b3c65241aa7404af6fd 1966396 x11 extra compiz-fusion-plugins-main_0.8.4-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLdPyfynjLPm522B0RAk1oAJ9sd89xUjNvqZS9kz5ktKKlbgT0owCePIQp sr95rErF/7lVME0rkCCcjyI= =Rgv4 -END PGP SIGNATURE- Accepted: compiz-fusion-plugins-main_0.8.4-1.diff.gz to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.4-1.diff.gz compiz-fusion-plugins-main_0.8.4-1.dsc to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.4-1.dsc compiz-fusion-plugins-main_0.8.4-1_amd64.deb to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.4-1_amd64.deb compiz-fusion-plugins-main_0.8.4.orig.tar.gz to main/c/compiz-fusion-plugins-main/compiz-fusion-plugins-main_0.8.4.orig.tar.gz -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: git and quilt
hi! On Wed, Feb 03, 2010 at 04:25:40PM -0600, Matt Zagrabelny wrote: Allbery [1] regarding git and Debian packaging. I am wondering if those who use git to manage their source package development are also using the debian/patches mechanism for modifying the upstream tarball. i use git+gbp+quilt in a number of my packages. i'm not convinced it's necessarily the *best* system out there, but it keeps the overhead pretty simple compared to using more complicated workflows à la topgit, while still meeting my own requirements for per-release branches etc. i've heard that gbp has recently introduced some new tools for working with patch queues, but i haven't had the time to look much more into them. in the meantime i'm dropping the patches into a quilt series. backporting upstream fixes is a bit nicer this way as well, as you can can do stuff like git show commit | quilt import -P upstream_commit.patch -[1] sean [1] if there are conflicts it's a bit trickier, then i usually resolve the cherry-pick, commit it, do the above for the resolved commit, and rebase the resolved commit from the history. signature.asc Description: Digital signature
Accepted compizconfig-python 0.8.4-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 03 Feb 2010 11:14:16 +0100 Source: compizconfig-python Binary: python-compizconfig Architecture: source amd64 Version: 0.8.4-1 Distribution: unstable Urgency: medium Maintainer: Debian X Strike Force debia...@lists.debian.org Changed-By: Sean Finney sean...@debian.org Description: python-compizconfig - Compizconfig bindings for python Closes: 567105 Changes: compizconfig-python (0.8.4-1) unstable; urgency=medium . * New upstream release. . [ Sean Finney ] * Use python-support for managing python extensions (Closes: #567105) - Thanks: Kumar Appaiah * RC bugfix, bumped severity. Checksums-Sha1: bcfe0a8fdf10a3d6db4988ec4d63318c1cbc9bd4 1467 compizconfig-python_0.8.4-1.dsc 9c1c69e26f4a6c0766ffb4ca90addf607a421d06 17509 compizconfig-python_0.8.4.orig.tar.gz 23416d32abe4e7497465847ec11448d8e8951462 2972 compizconfig-python_0.8.4-1.diff.gz 51d6d20bb62be45eee3a074853e65217c083fa39 93286 python-compizconfig_0.8.4-1_amd64.deb Checksums-Sha256: 21386280b35f44c5b711fbdc6dce32c3ef387fa484330a2e77c567e4dceb63cf 1467 compizconfig-python_0.8.4-1.dsc badde2ba69de41df731e2d77ad07df62254a9835571f13bf4a33c35ebe50432e 17509 compizconfig-python_0.8.4.orig.tar.gz fcdc5fe16dfeb460dc3f2242bb9ae6981ab6aa1255f905a314065f8985a82a9a 2972 compizconfig-python_0.8.4-1.diff.gz 4f7406c274f5ebd3d7037d0d73cfce6e1db7060bab318daeb6a042fd257a3bc0 93286 python-compizconfig_0.8.4-1_amd64.deb Files: 474c723d17410cf3e3f5e6f89a32f407 1467 x11 extra compizconfig-python_0.8.4-1.dsc f9008bd27835da3f7047430d5ecbe030 17509 x11 extra compizconfig-python_0.8.4.orig.tar.gz 569619bb5085ed5aac0404112bcbf81e 2972 x11 extra compizconfig-python_0.8.4-1.diff.gz a49d522c2ad00819e86cbb7ba7322036 93286 x11 extra python-compizconfig_0.8.4-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLaWHeynjLPm522B0RAuB6AJsEKFSt0DJCLVvlmW3Zf4iNTfULuQCgiE3z pjjX7UiV9gzFcLn5Rngaajw= =xLzC -END PGP SIGNATURE- Accepted: compizconfig-python_0.8.4-1.diff.gz to main/c/compizconfig-python/compizconfig-python_0.8.4-1.diff.gz compizconfig-python_0.8.4-1.dsc to main/c/compizconfig-python/compizconfig-python_0.8.4-1.dsc compizconfig-python_0.8.4.orig.tar.gz to main/c/compizconfig-python/compizconfig-python_0.8.4.orig.tar.gz python-compizconfig_0.8.4-1_amd64.deb to main/c/compizconfig-python/python-compizconfig_0.8.4-1_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted cacti 0.8.7e-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 24 Jan 2010 21:39:46 +0100 Source: cacti Binary: cacti Architecture: source all Version: 0.8.7e-2 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: cacti - Frontend to rrdtool for monitoring systems and services Closes: 548447 561477 563955 Changes: cacti (0.8.7e-2) unstable; urgency=low . * Import 2 new official patches from upstream * Italian debconf translation - thanks to Alessandro De Zorzi l...@nonlontano.it (Closes: #548447) * Fix for Undefined index: local_data_id in graphs_new.php - new debian patch 563955_undefined_index_local_data_id.patch - thanks to Teodor MICU mteo...@gmail.com (Closes: #563955) * Fix for must not RE-add /etc/apache2/conf.d/cacti.conf link on upgrade - thanks to Patrick Schoenfeld schoenf...@debian.org (Closes: #561477) * Bump debhelper compatibility level to 5 Checksums-Sha1: d64f126303b48c24e287620e3798fa98fe51fbcf 1105 cacti_0.8.7e-2.dsc bfc88298e149f1762a59a69c57d6455ff7f8ab44 42806 cacti_0.8.7e-2.diff.gz 5a342da499277a83541b10d14bd15e6cffc76396 2090752 cacti_0.8.7e-2_all.deb Checksums-Sha256: f032feb006552a6091429249d50ebe6a4e00cfcec945bca849f764a57c6868fe 1105 cacti_0.8.7e-2.dsc 21433c40ebe67ef1c99f848a29bf2a0a9a6f91ce73491ca3e4989cecaaf2cb34 42806 cacti_0.8.7e-2.diff.gz 77cda3b1d97d9ba4b13b027e476fc1f0f06f23c84a567d8678de8ae8a538aff6 2090752 cacti_0.8.7e-2_all.deb Files: 5ce00f3729ce21b772c32402017cfcb3 1105 web extra cacti_0.8.7e-2.dsc 50541354c4461f935c06ef18667cb12e 42806 web extra cacti_0.8.7e-2.diff.gz d59dcb2fb442362616e1b4db20e71dbd 2090752 web extra cacti_0.8.7e-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLXLKOynjLPm522B0RAjmxAJ4739sbGqpLm6OSbk9OE6j3aa6e1gCcCFrV uGgZUbh5cwdam++y+sIvjSs= =aAoa -END PGP SIGNATURE- Accepted: cacti_0.8.7e-2.diff.gz to main/c/cacti/cacti_0.8.7e-2.diff.gz cacti_0.8.7e-2.dsc to main/c/cacti/cacti_0.8.7e-2.dsc cacti_0.8.7e-2_all.deb to main/c/cacti/cacti_0.8.7e-2_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted cacti-spine 0.8.7e-2 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 24 Jan 2010 14:44:32 +0100 Source: cacti-spine Binary: cacti-spine Architecture: source amd64 Version: 0.8.7e-2 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: cacti-spine - Multi-Threading poller for cacti Closes: 529653 535637 543184 552462 559380 Changes: cacti-spine (0.8.7e-2) unstable; urgency=low . * Remove obsolete and unused debconf/gettext files (Closes: #529653, #535637, #543184, #552462, #559380) Checksums-Sha1: 4d4057f1c00748250b22fa7df2bbbf786812eb86 1197 cacti-spine_0.8.7e-2.dsc d271012a4805520c868db186d549240d03dff83e 13822 cacti-spine_0.8.7e-2.diff.gz f4d91173a8fe43bef5ef427f6a33e78edc0b1db8 53874 cacti-spine_0.8.7e-2_amd64.deb Checksums-Sha256: ad8e8cba475e61b7588a2932e55ad8660efb3abdd02908d00a009e3f633f4f64 1197 cacti-spine_0.8.7e-2.dsc 75e3b6c6bb05ad280ac00a9dad8d23373b2e33e6bc159179ebb15645b6be8997 13822 cacti-spine_0.8.7e-2.diff.gz b5b9c7eb873960f64ce1ab9dc43b72c594168816441d2030b5a10a2f33d3 53874 cacti-spine_0.8.7e-2_amd64.deb Files: c458f4d5b9340a84c0b669ef6a72b58c 1197 web extra cacti-spine_0.8.7e-2.dsc 33e5d1773d06e2e9d83418760ddc6b38 13822 web extra cacti-spine_0.8.7e-2.diff.gz b550124340c40647ca2f443488be2527 53874 web extra cacti-spine_0.8.7e-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLXLNDynjLPm522B0RAggkAJ9rxrPkE1WnRO3Pu/7t6sWcexDlmgCfdTVv 3Q5shjC5ipQH6/qM0aK99Lg= =1pFo -END PGP SIGNATURE- Accepted: cacti-spine_0.8.7e-2.diff.gz to main/c/cacti-spine/cacti-spine_0.8.7e-2.diff.gz cacti-spine_0.8.7e-2.dsc to main/c/cacti-spine/cacti-spine_0.8.7e-2.dsc cacti-spine_0.8.7e-2_amd64.deb to main/c/cacti-spine/cacti-spine_0.8.7e-2_amd64.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted dbconfig-common 1.8.42 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 23 Jan 2010 20:00:11 +0100 Source: dbconfig-common Binary: dbconfig-common Architecture: source all Version: 1.8.42 Distribution: unstable Urgency: low Maintainer: Sean Finney sean...@debian.org Changed-By: Sean Finney sean...@debian.org Description: dbconfig-common - common framework for packaging database applications Closes: 514346 525201 525548 529316 529365 529963 542381 561937 563907 Changes: dbconfig-common (1.8.42) unstable; urgency=low . * Register all internal ucf-managed files with ucfr (Closes: #514346) * Manage global config file /etc/dbconfig-common/config with ucf * Fix an incorrect bug reference in the previous upload's changelog entry * New Japanese debconf translations. (Closes: #525201, #561937) - thanks to Hideki Yamane (Debian-JP) henr...@debian.or.jp * Updated spanish debconf translations (Closes: #525548) - thanks to Javier Fernández-Sanguino Peña * Prevent remove/reinstall from seeming to be an upgrade (Closes: #529365) - thanks to Florian Grandel * Clarify documentation regarding paths for update code (Closes: #529963) - thanks to Kiss Gabor * Fix documented path for removal SQL (Closes: #563907) - thanks to Thijs Kinkhorst th...@debian.org * Fix for fails to install in noninteractive mode (Closes: #542381) - thanks to Thijs Kinkhorst th...@uvt.nl * Fix french translation for deconfiguration dialog really unclear (Closes: #529316) - thanks to Olivier Berger olivier.ber...@it-sudparis.eu Checksums-Sha1: 9648d7f47cc85385510c432da1cfb7de6ca0ff5c 995 dbconfig-common_1.8.42.dsc 980feb5500545f11dbb0d6edc0775ba3e346c844 355578 dbconfig-common_1.8.42.tar.gz 0411faedd6c9ca0f1deb70a1d4b34a9aefa77a82 473684 dbconfig-common_1.8.42_all.deb Checksums-Sha256: 485c9baa8d6eeb52bb99e82cb6c653e9b74daa7697db1a4ff5051d334325c1ba 995 dbconfig-common_1.8.42.dsc 9b018cdc82e6a0e407f3bb2cb9194f1df3c2cd07f4fb5b9ddad84c1bafa82266 355578 dbconfig-common_1.8.42.tar.gz 669e0a43c7487f15e6e44ee5f0355b568e8dfa423d8e9246d721251a491bb732 473684 dbconfig-common_1.8.42_all.deb Files: cc606aa85de721171004eddcbdd4b8ae 995 admin optional dbconfig-common_1.8.42.dsc 34f80019b7aa4b1dad317f80a3d8756b 355578 admin optional dbconfig-common_1.8.42.tar.gz acccdb4e6315f00b748258dc0b6c1c5a 473684 admin optional dbconfig-common_1.8.42_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFLW01qynjLPm522B0RAoqvAJ9FXQqEdzCFolnWEzNHb6vAhf8EKgCdGVQy Zf/F7xCIterW256qiW0bgGs= =Xq8C -END PGP SIGNATURE- Accepted: dbconfig-common_1.8.42.dsc to main/d/dbconfig-common/dbconfig-common_1.8.42.dsc dbconfig-common_1.8.42.tar.gz to main/d/dbconfig-common/dbconfig-common_1.8.42.tar.gz dbconfig-common_1.8.42_all.deb to main/d/dbconfig-common/dbconfig-common_1.8.42_all.deb -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
