Bug#672535: mysql-testsuite-5.5: child process mysql utilities picking up local config files causes test failure
Package: mysql-client-5.5
Version: 5.5.23-2
Severity: minor
Tags: upstream
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
I removed the Debian patches disabling various tests to
investigate those the test failures.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Five tests failed one of them being: main.plugin_auth
I reran that test and inspected the log file.
Based upon that I captured the output of
strace -f
/home/nicholas/debian/svn/pkg-mysql/mysql-5.5/branches/unstable/builddir/client//mysql_upgrade
--defaults-file=/home/nicholas/debian/svn/pkg-mysql/mysql-5.5/branches/unstable/builddir/mysql-test/var/my.cnf
The output is attached. It shows that mysql_upgrade forks a
mysqlcheck process and as far as mysql_upgrade goes everything is in
order. However inspection of the trace log coming from the
child process shows that it is reading locally stored config files
as opposed to test specific config files. Hence it is not surprising
that we get test failures.
This is the most juicy extract from the strace log:
[pid 16994] stat64("/usr/etc/my.cnf", 0xbfd4c290) = -1 ENOENT (No such
file or directory)
[pid 16994] stat64("/home/nicholas/.my.cnf", {st_mode=S_IFREG|0644,
st_size=100, ...}) = 0
[pid 16994] open("/home/nicholas/.my.cnf", O_RDONLY|O_LARGEFILE) = 4
Although I view this as essentially a minor build test failure, I
believe it could affect end users depending on how they are trying to
manage their config files.
*** End of the template - remove these lines ***
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages mysql-testsuite-5.5 depends on:
ii libc62.13-32
ii libgcc1 1:4.6.2-16
ii libstdc++6 4.6.2-16
ii mysql-client 5.5.23-2
ii mysql-client-5.5 [mysql-client] 5.5.23-2
ii mysql-server 5.5.23-2
mysql-testsuite-5.5 recommends no packages.
mysql-testsuite-5.5 suggests no packages.
-- no debconf information
execve("/home/nicholas/debian/svn/pkg-mysql/mysql-5.5/branches/unstable/builddir/client//mysql_upgrade", ["/home/nicholas/debian/svn/pkg-my"..., "--defaults-file=/home/nicholas/d"..., "--force"], [/* 32 vars */]) = 0
brk(0) = 0xb7f2
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb756f000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 4
fstat64(4, {st_mode=S_IFREG|0644, st_size=69800, ...}) = 0
mmap2(NULL, 69800, PROT_READ, MAP_PRIVATE, 4, 0) = 0xb755d000
close(4)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/libpthread.so.0", O_RDONLY) = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220L\0\0004\0\0\0"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0755, st_size=117009, ...}) = 0
mmap2(NULL, 98816, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0xb7544000
mmap2(0xb7559000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x14) = 0xb7559000
mmap2(0xb755b000, 4608, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb755b000
close(4)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/lib/i386-linux-gnu/libz.so.1", O_RDONLY) = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\32\0\0004\0\0\0"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0644, st_size=90220, ...}) = 0
mmap2(NULL, 92896, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0xb752d000
mmap2(0xb7543000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x15) = 0xb7543000
close(4)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/i386-linux-gnu/i686/cmov/librt.so.1", O_RDONLY) = 4
read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\30\0\0004\0\0\0"..., 512) = 512
fstat64(4, {st_mode=S_IFREG|0644, st_size=30684, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb752c000
mmap2(NULL, 33360, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 4, 0) = 0xb7523000
mmap2(0xb752a000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 4, 0x6) = 0xb752a000
close(4)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/lib/i386-linux-gnu/i686/c
Bug#672359: more info please
severity 672359 minor tag 672359 +confirmed +moreinfo retitle 672359 client scripts fail when /etc/mysql/conf.d is missing thanks Sir, In the narrowest sense I can confirm the bug. If I move the /etc/mysql/conf.d/ out of the way, then I get the error you do. However when I test installation or upgrade that directory gets created. Can you think how that directory came to not be there? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671115: [debian-mysql] Bug#671115: transition: mysql-5.5
I think those are defensible although I take the point that the changelog is misleading. For example we just stripped out a lot of stuff that used procps and the upstream move to cmake removed a lot of explicit build dependencies so it was natural to ask whether these are still required. I will look again at debian/rules but I think it is good to get rid of unnecessarty dependencies. On 08/05/12 10:15, Adam D. Barratt wrote: On 08.05.2012 10:04, Julien Cristau wrote: On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition At some point we need to transition from mysql-5.1 to mysql-5.5. We would like to do this before the freeze though we appreciate that time is now short. We arrived at this position as the Debian MySQL Team became increasingly understaffed. It is better now but not ideal. We certainly will get mysql-5.5 into unstable in the next few weeks. The question is can we migrate all the dependencies over and drop mysql-5.1 before the freeze? *sigh* apparently you uploaded this to sid without even waiting for an answer, so we now have an uncoordinated libmysqlclient SONAME bump on our hands... Also, these changes look very wrong: * Removed unnecessary build dependencies: - procps as it is required by cmake, cf. #96768 - zlib1g newer version required by cmake - libtool obsoleted by cmake - file required by debhelper If you need the packages as part of your build process, you need to be build-depending on them. There's a reason that policy explicitly mentions not relying on transitive dependencies. As far as I can see the upstream packages that are likely to require recompilation are: That's an awfully long list to be breaking without coordination. I'm not amused. Indeed. Regards, Adam ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa96b8b.7040...@periapt.co.uk
Bug#671115: [debian-mysql] Bug#671115: transition: mysql-5.5
I think those are defensible although I take the point that the changelog is misleading. For example we just stripped out a lot of stuff that used procps and the upstream move to cmake removed a lot of explicit build dependencies so it was natural to ask whether these are still required. I will look again at debian/rules but I think it is good to get rid of unnecessarty dependencies. On 08/05/12 10:15, Adam D. Barratt wrote: On 08.05.2012 10:04, Julien Cristau wrote: On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition At some point we need to transition from mysql-5.1 to mysql-5.5. We would like to do this before the freeze though we appreciate that time is now short. We arrived at this position as the Debian MySQL Team became increasingly understaffed. It is better now but not ideal. We certainly will get mysql-5.5 into unstable in the next few weeks. The question is can we migrate all the dependencies over and drop mysql-5.1 before the freeze? *sigh* apparently you uploaded this to sid without even waiting for an answer, so we now have an uncoordinated libmysqlclient SONAME bump on our hands... Also, these changes look very wrong: * Removed unnecessary build dependencies: - procps as it is required by cmake, cf. #96768 - zlib1g newer version required by cmake - libtool obsoleted by cmake - file required by debhelper If you need the packages as part of your build process, you need to be build-depending on them. There's a reason that policy explicitly mentions not relying on transitive dependencies. As far as I can see the upstream packages that are likely to require recompilation are: That's an awfully long list to be breaking without coordination. I'm not amused. Indeed. Regards, Adam ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671115: [debian-mysql] Bug#671115: transition: mysql-5.5
Julien, I am sorry. I got into a panic state over getting rid of mysql-5.1. In hindsight I can see that there were betters ways of getting the attention of the release team. I am trying to do the right thing. On 08/05/12 10:04, Julien Cristau wrote: On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote: *sigh* apparently you uploaded this to sid without even waiting for an answer, so we now have an uncoordinated libmysqlclient SONAME bump on our hands... That's an awfully long list to be breaking without coordination. I'm not amused. Cheers, Julien ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa96a6e.6070...@periapt.co.uk
Bug#671115: [debian-mysql] Bug#671115: transition: mysql-5.5
Julien, I am sorry. I got into a panic state over getting rid of mysql-5.1. In hindsight I can see that there were betters ways of getting the attention of the release team. I am trying to do the right thing. On 08/05/12 10:04, Julien Cristau wrote: On Tue, May 1, 2012 at 22:52:22 +0100, Nicholas Bamber wrote: *sigh* apparently you uploaded this to sid without even waiting for an answer, so we now have an uncoordinated libmysqlclient SONAME bump on our hands... That's an awfully long list to be breaking without coordination. I'm not amused. Cheers, Julien ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Accepted mysql-5.5 5.5.23-2 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 08 May 2012 05:59:09 +0100 Source: mysql-5.5 Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 mysql-server mysql-client mysql-testsuite-5.5 mysql-source-5.5 Architecture: source all i386 Version: 5.5.23-2 Distribution: unstable Urgency: low Maintainer: Debian MySQL Maintainers Changed-By: Nicholas Bamber Description: libmysqlclient-dev - MySQL database development files libmysqlclient18 - MySQL database client library libmysqld-dev - MySQL embedded database development files libmysqld-pic - PIC version of MySQL embedded server development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.5 - MySQL database client binaries mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.5 - MySQL database server binaries and system database setup mysql-server-core-5.5 - MySQL database server binaries mysql-source-5.5 - MySQL source mysql-testsuite-5.5 - MySQL testsuite Closes: 512964 666721 Changes: mysql-5.5 (5.5.23-2) unstable; urgency=low . * Stopped overriding the -j build parameter (Closes: #512964) * Stopped testing for /proc filesystem. It is no longer used for determining the number of CPUs. * Removed unnecessary build dependencies: - procps as it is required by cmake, cf. #96768 - zlib1g newer version required by cmake - libtool obsoleted by cmake - file required by debhelper * Migrated libmysqld-dev, libmysqld-pic, libmysqlclient18 to using dh_install rather than dh_movefiles * Changed /var/run to /run as required by Debian Policy 3.9.3 (9.1.1) * Raised standards version to 3.9.3 * Moved '-e' from shebang line to explicit 'set -e' as requested by lintian * Restored ha_example.so to mysql-server-5.5 but added Breaks/Replaces clauses (cf. LP: #912487) and (Closes: #666721) * Added additional Breaks/Replaces clauses for other clashes: - mysql-server-5.5 overwrites perror from mysql-client-5.1 - mysql-server-core-5.5 overwrites my_print_defaults from mysql-client-5.1 Checksums-Sha1: 186e30c0c6048913e37ad8b314226da9ffb4aa6e 2864 mysql-5.5_5.5.23-2.dsc 5040ddd9062877a01e5a8bb69825454af5214d52 299797 mysql-5.5_5.5.23-2.debian.tar.gz 4aee6c79f9b941eca27065ead7fbeb3a292cf0d8 71026 mysql-common_5.5.23-2_all.deb 661fda53d04b91102ce3eedfe57346b384e10fe8 68688 mysql-server_5.5.23-2_all.deb 34cf1e44c4811d0d975b586d65d9a0fb852e5e93 68562 mysql-client_5.5.23-2_all.deb ef9d6a9cfc7e37f1916459bc1d0b40d4d8e6dbdd 864230 libmysqlclient18_5.5.23-2_i386.deb 2919bb2e71b913b1d7b17d1a9dfaf376bb264fd9 4696052 libmysqld-pic_5.5.23-2_i386.deb 6b2870478765075aa639f988f166b2e59fe865ed 4693028 libmysqld-dev_5.5.23-2_i386.deb ba9defe2fb174f35da27507d9486a96366626946 1201828 libmysqlclient-dev_5.5.23-2_i386.deb 765f53be7a618f8826942bbc3a72fa3dac51ad61 9109104 mysql-client-5.5_5.5.23-2_i386.deb 4eb78beb73a2cfcf0f73e70e6a26f204c5eaee8c 5977924 mysql-server-core-5.5_5.5.23-2_i386.deb ed48057fc7c258bae7ca0f12cbbba2984a75aa45 8673822 mysql-server-5.5_5.5.23-2_i386.deb 34afeaa718a7bdf5470d718ca8dc76900d314505 8740316 mysql-testsuite-5.5_5.5.23-2_i386.deb a8b1b27f6c830d1980d9ae13542201a7d17b064e 28547768 mysql-source-5.5_5.5.23-2_i386.deb Checksums-Sha256: c67411810c77f982809c6a729d1f727d615b7a2fa40365f00f6aa8ead5eb14bc 2864 mysql-5.5_5.5.23-2.dsc 29246ffd849a3978429defbfce6e7b74e7188d3899799cfd641749be3ec43670 299797 mysql-5.5_5.5.23-2.debian.tar.gz 7c5fc9d944c2ac285d5c8184ae62176f66f2a7bbfd16ff7776a4700a49329fb0 71026 mysql-common_5.5.23-2_all.deb 5309559d9e6c9eebd9db7022d0547005b9edc12952582bd6893b9d303d5ddb27 68688 mysql-server_5.5.23-2_all.deb 605afc6f49e3e23f502601ddce60a954cb49ac0deb09ebeb018438fd9a3d825b 68562 mysql-client_5.5.23-2_all.deb 5dc6c2175b9caed42fb579c19d3a5785adc6c2e669dec53900253bb570e62f00 864230 libmysqlclient18_5.5.23-2_i386.deb 35863b96d0747d40d171a6c61ef238a33bf43eae889f086867eeff84b7a8d291 4696052 libmysqld-pic_5.5.23-2_i386.deb e6b82ad6d4a4ebbdc121921e67afb6d350031951c79c480df6ae2bfe51f242e9 4693028 libmysqld-dev_5.5.23-2_i386.deb d2302674a5f168174cf2b016ac1e47263c42c9a02d1f071615bba9364da647c7 1201828 libmysqlclient-dev_5.5.23-2_i386.deb ede419af5c036905942b38f56344f7426e00319644b8cb73fd89c18ae6b62b26 9109104 mysql-client-5.5_5.5.23-2_i386.deb f5aa9d3f1268cac57a998148fa332b2544adc92b8267f5822ce3d7c968307c5f 5977924 mysql-server-core-5.5_5.5.23-2_i386.deb 8f2ad4be0fbfd184ca6e84a904924199596f8cbaac1ede6e71f427e65180 8673822 mysql-server-5.5_5.5.23-2_i386.deb 853690bb356137ad48484edc938c26df46df5a602cbd0df49c99cadc80f28e97 8740316 mysql-testsuite-5.5_5.5.23-2_i386.deb ce3b3b2b668d2d641ec3677fe7277c5b27f59bfcb65b3672d7719bff63c4dfcf 28
Bug#666721: #666721
reopen 666721 nicho...@periapt.co.uk retitile 666721 file clash handled differently from ubuntu severity 666721 normal user pkg-mysql-ma...@lists.alioth.debian.org usertags 666721 ubuntu thanks Actually I realize that this was dealt with differently in Ubuntu - and there is probably an issue anyway. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666721: #666721
reopen 666721 nicho...@periapt.co.uk retitile 666721 file clash handled differently from ubuntu severity 666721 normal user pkg-mysql-ma...@lists.alioth.debian.org usertags 666721 ubuntu thanks Actually I realize that this was dealt with differently in Ubuntu - and there is probably an issue anyway. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670722: perl-base: IO::Socket::UNIX::hostpath dies on kFreeBSD
On 06/05/12 22:01, Dominic Hargreaves wrote: On Sun, May 06, 2012 at 05:26:45PM +0200, Robert Millan wrote: 2012/5/6 Steven Chamberlain: It looks to me like GNU/kFreeBSD uses the sys/un.h provided by eglibc, with a sockaddr_un different to FreeBSD's, so the test should rather be: # if defined(__linux__) || defined(__GLIBC__) Note that this is true for the declaration (which is matters here AFAICT) but it's not for the actual structure, see #645527. As for GNU/Hurd, my guess is that it doesn't have that header at all and skips the entire #ifdef I_SYS_UN block. So it shouldn't need to be considered here. Actually ISTR GNU/Hurd had zero-length sun_path too. CCing debian-hurd... Good point. The test does fail on hurd-i386 too. Dominic. It's not really an issue on Hurd as it is more of an OS limitation than a bug. http://lists.gnu.org/archive/html/bug-hurd/2011-12/msg0.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#670722: perl-base: IO::Socket::UNIX::hostpath dies on kFreeBSD
On 06/05/12 22:01, Dominic Hargreaves wrote: On Sun, May 06, 2012 at 05:26:45PM +0200, Robert Millan wrote: 2012/5/6 Steven Chamberlain: It looks to me like GNU/kFreeBSD uses the sys/un.h provided by eglibc, with a sockaddr_un different to FreeBSD's, so the test should rather be: # if defined(__linux__) || defined(__GLIBC__) Note that this is true for the declaration (which is matters here AFAICT) but it's not for the actual structure, see #645527. As for GNU/Hurd, my guess is that it doesn't have that header at all and skips the entire #ifdef I_SYS_UN block. So it shouldn't need to be considered here. Actually ISTR GNU/Hurd had zero-length sun_path too. CCing debian-hurd... Good point. The test does fail on hurd-i386 too. Dominic. It's not really an issue on Hurd as it is more of an OS limitation than a bug. http://lists.gnu.org/archive/html/bug-hurd/2011-12/msg0.html -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa6ecb1.4020...@periapt.co.uk
Re: Bug#670722: perl-base: IO::Socket::UNIX::hostpath dies on kFreeBSD
On 06/05/12 22:01, Dominic Hargreaves wrote: On Sun, May 06, 2012 at 05:26:45PM +0200, Robert Millan wrote: 2012/5/6 Steven Chamberlain: It looks to me like GNU/kFreeBSD uses the sys/un.h provided by eglibc, with a sockaddr_un different to FreeBSD's, so the test should rather be: # if defined(__linux__) || defined(__GLIBC__) Note that this is true for the declaration (which is matters here AFAICT) but it's not for the actual structure, see #645527. As for GNU/Hurd, my guess is that it doesn't have that header at all and skips the entire #ifdef I_SYS_UN block. So it shouldn't need to be considered here. Actually ISTR GNU/Hurd had zero-length sun_path too. CCing debian-hurd... Good point. The test does fail on hurd-i386 too. Dominic. It's not really an issue on Hurd as it is more of an OS limitation than a bug. http://lists.gnu.org/archive/html/bug-hurd/2011-12/msg0.html -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa6ecb1.4020...@periapt.co.uk
Bug#569930: HA
tag 569930 +moreinfo thanks Simon, You did not say what high availability system you are using. If it's not Debian or at least DFSG compliant system, then surely you would be more obliged to take it up with the vendor of the HA system rather than Debian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#419646: moreinfo
tag 419646 -help +moreinfo thanks Vince, The debconf question is asking you to check that the mysql user is set up locally. As such I don't see why start up ordering should be an issue - unless of course you have ignored that advice. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#537785: wontfix
tag 537785 +wontfix thanks Taking 671534 as a precedent this won't be changed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671534: [debian-mysql] Use case?
tag 671534 +confirmed thanks Well then if I or noone else can think of any more objections that is what will happen. There is one other SSL related bug so they should get looked at together - which will probably be after the package is lintian and piuparts clean. On 05/05/12 20:49, Clint Byrum wrote: Excerpts from Nicholas Bamber's message of Sat May 05 12:00:49 -0700 2012: On 05/05/12 19:51, Russ Allbery wrote: Nicholas Bamber writes: Although in general I am all for standardization, I am not actually clear about the use case here. The typical case to which you refer is a browser-like client talking to a webserver-like server using certificates checkable with external authorities. In the MySQL case both client and server must be using MySQL code at some level and the certificates are likely to be managed by an authority internal to the oganization. I don't really agree with your last assumption... or at least this isn't true of us at Stanford. We use commercial Comodo certificates for anything internal that isn't just test/dev (and increasingly for that), since we have a site-license for Comodo certificates and they're free. There's no reason not to, and using a CA that's already built into various software makes everything easier. (This is likely common for US universities that are part of Internet2, since Internet2 negotiated a general agreement with Comodo.) But even apart from that, suppose it is managed by an authority internal to the organization. The obvious thing to do with the certificate for that internal CA on a Debian system is to put it into /usr/local/share/ca-certificates and then let ca-certificates add it to all the other trusted CAs. That way, certificates issued by your internal CA will transparently work with anything on a Debian system that uses SSL, not just web browsers. We use that same /etc/ssl/certs infrastructure for our internal Usenet server, for the certificates for our LDAP servers, our SMTP servers, and so forth. (And indeed for LDAP and SMTP, even if you don't have free commercial certificates, it's usually a good idea to get commercial certificates so that you don't have to deal with the CA distribution hassle.) Also, it's worth mentioning that anyone can get free trusted certificates that will be verified by the /etc/ssl/certs infrastructure from cacert.org. I suppose the drawback to using /etc/ssl/certs by default is that people may not want to trust the commercial CA authorities by default, and there are some reasons to be concerned about that. But, there, I think the risk for MySQL in most ways in which it's used is probably lower than for the web browser, since the MySQL clients are more likely to be on controlled networks and therefore less likely to be prone to easy man-in-the-middle attacks. << fixed top post>> Russ, What if the location were configurable via debconf. (I have not checked if it is or not). The explanatory text could offer your choice as a possible location. I really dislike this idea. Debconf questions are for things that don't have sane defaults. Perhaps if this were *low* priority and the default was /etc/ssl/certs. IMO, if you are centrally managing your own CA certs, you are more likely to put them in /etc/ssl/certs than anywhere else. Why would we encourage divergence from a positive pattern like that? I think the idea is a good one, and would like to see it done at some point. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671534: Use case?
Russ, What if the location were configurable via debconf. (I have not checked if it is or not). The explanatory text could offer your choice as a possible location. On 05/05/12 19:51, Russ Allbery wrote: Nicholas Bamber writes: Although in general I am all for standardization, I am not actually clear about the use case here. The typical case to which you refer is a browser-like client talking to a webserver-like server using certificates checkable with external authorities. In the MySQL case both client and server must be using MySQL code at some level and the certificates are likely to be managed by an authority internal to the oganization. I don't really agree with your last assumption... or at least this isn't true of us at Stanford. We use commercial Comodo certificates for anything internal that isn't just test/dev (and increasingly for that), since we have a site-license for Comodo certificates and they're free. There's no reason not to, and using a CA that's already built into various software makes everything easier. (This is likely common for US universities that are part of Internet2, since Internet2 negotiated a general agreement with Comodo.) But even apart from that, suppose it is managed by an authority internal to the organization. The obvious thing to do with the certificate for that internal CA on a Debian system is to put it into /usr/local/share/ca-certificates and then let ca-certificates add it to all the other trusted CAs. That way, certificates issued by your internal CA will transparently work with anything on a Debian system that uses SSL, not just web browsers. We use that same /etc/ssl/certs infrastructure for our internal Usenet server, for the certificates for our LDAP servers, our SMTP servers, and so forth. (And indeed for LDAP and SMTP, even if you don't have free commercial certificates, it's usually a good idea to get commercial certificates so that you don't have to deal with the CA distribution hassle.) Also, it's worth mentioning that anyone can get free trusted certificates that will be verified by the /etc/ssl/certs infrastructure from cacert.org. I suppose the drawback to using /etc/ssl/certs by default is that people may not want to trust the commercial CA authorities by default, and there are some reasons to be concerned about that. But, there, I think the risk for MySQL in most ways in which it's used is probably lower than for the web browser, since the MySQL clients are more likely to be on controlled networks and therefore less likely to be prone to easy man-in-the-middle attacks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [debian-mysql] src:mysql-*: please consider using gcc-4.4 instead of gcc-4.5
Thorsten, I am not sure whether Clint regards anything as really important before we deploy mysql-5.5 to unstable - backporting the ubuntu modifications perhaps. However as far as I am concerned the only I need to do is figure out the appropriate subversion incantations. We have already raised a transition bug with the release team: #671115. Once it is in unstable we'll need to do a mass bug filing. On 05/05/12 18:44, Thorsten Glaser wrote: Nicholas Bamber dixit: Actually more specifically I don't see anywhere that mysql-5.5 (unlike mysql-5.1) is specifying the version for gcc. Ah okay, so the workaround is no longer needed there. (I only looked into 5.1 in more detail, as that's a build-dependency of php5, which is needed to build way too much stuff in the archive…) So it should just pick up the available version. Yes, indeed. (It is also only in experimental, so it does not concern us yet.) And I cannot ping crest.debian.net so I would not be able to test any customizations. Right. The currently only way is to run an Atari VM yourself: https://wiki.debian.org/Aranym/Quick Sorry about that, but some of the machines have hardware issues, from what I’ve heard from the porters, and… well, lack of time or manpower… bye, //mirabilos -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa56cd0.1020...@periapt.co.uk
Re: [debian-mysql] src:mysql-*: please consider using gcc-4.4 instead of gcc-4.5
Thorsten, Actually more specifically I don't see anywhere that mysql-5.5 (unlike mysql-5.1) is specifying the version for gcc. So it should just pick up the available version. And I cannot ping crest.debian.net so I would not be able to test any customizations. On 05/05/12 18:21, Nicholas Bamber wrote: Thorsten, I think it is possible to put in an architecture specific exception. However a little more background would is needed as to why we should make that effort. On 05/05/12 17:44, Thorsten Glaser wrote: Hi, since doko has said from the start that wheezy will not release with gcc-4.5 (only 4.4 and 4.6 and, it looks like, 4.7), it was never built for m68k. I had built mysql-5.1 with gcc-4.4 and g++-4.4 instead of -4.5, and just started to do the same with the current source package again but believe it too will build just fine. So please for as long as that workaround is still needed use gcc-4.4 and g++-4.4 instead of 4.5, at least on m68k, but probably on all architec- tures due to the above. Thanks, //mirabilos ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa5646d.2030...@periapt.co.uk
Re: [debian-mysql] src:mysql-*: please consider using gcc-4.4 instead of gcc-4.5
Thorsten, I think it is possible to put in an architecture specific exception. However a little more background would is needed as to why we should make that effort. On 05/05/12 17:44, Thorsten Glaser wrote: Hi, since doko has said from the start that wheezy will not release with gcc-4.5 (only 4.4 and 4.6 and, it looks like, 4.7), it was never built for m68k. I had built mysql-5.1 with gcc-4.4 and g++-4.4 instead of -4.5, and just started to do the same with the current source package again but believe it too will build just fine. So please for as long as that workaround is still needed use gcc-4.4 and g++-4.4 instead of 4.5, at least on m68k, but probably on all architec- tures due to the above. Thanks, //mirabilos -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa5619d@periapt.co.uk
Bug#671534: Use case?
Russ, Although in general I am all for standardization, I am not actually clear about the use case here. The typical case to which you refer is a browser-like client talking to a webserver-like server using certificates checkable with external authorities. In the MySQL case both client and server must be using MySQL code at some level and the certificates are likely to be managed by an authority internal to the oganization. Do these two cases really have very much in common? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#671534: reassign
If this is going to be fixed it will be in 5.5. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Accepted mysql-5.5 5.5.23-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 03 May 2012 18:03:34 +0100 Source: mysql-5.5 Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 mysql-server mysql-client mysql-testsuite-5.5 mysql-source-5.5 Architecture: source all i386 Version: 5.5.23-1 Distribution: experimental Urgency: low Maintainer: Debian MySQL Maintainers Changed-By: Nicholas Bamber Description: libmysqlclient-dev - MySQL database development files libmysqlclient18 - MySQL database client library libmysqld-dev - MySQL embedded database development files libmysqld-pic - PIC version of MySQL embedded server development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.5 - MySQL database client binaries mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.5 - MySQL database server binaries and system database setup mysql-server-core-5.5 - MySQL database server binaries mysql-source-5.5 - MySQL source mysql-testsuite-5.5 - MySQL testsuite Closes: 540153 666721 Changes: mysql-5.5 (5.5.23-1) experimental; urgency=low . * Added patch to test suite to accept socket paths less than 40 characters long (Closes: #540153) * Disabled some more tests including some reported by Olaf van der Speck * Removed ha_example.so from mysql-server-5.5 install (Closes: #666721) * New upstream release: unspecified security issues CVE-2012-1697, CVE-2012-1696 * Added patch to correct spelling mistakes: preceeding -> preceding Checksums-Sha1: 6a7f2142a44b90da30789f713832b61486a155bb 2961 mysql-5.5_5.5.23-1.dsc 4948239625f0c23f033cadce7f41c31a5725ca12 24485979 mysql-5.5_5.5.23.orig.tar.gz d18f9a52c449611edb20fd1a70f111a9ce4f8902 299540 mysql-5.5_5.5.23-1.debian.tar.gz 28cc6f019764bc2b259fb7c83137780e258a4945 70654 mysql-common_5.5.23-1_all.deb e7c21bb4c66d57490a0bec89c9f4558f4807172d 68310 mysql-server_5.5.23-1_all.deb a1cd6d45cbae0ccf141ef44846d0ea5c0fb09d42 68192 mysql-client_5.5.23-1_all.deb dca554fe2760c54aecf040ce4ca40fbfcd156071 863568 libmysqlclient18_5.5.23-1_i386.deb 65dd5887f53f5a01b624eddb4e7fab7298f503a6 4695072 libmysqld-pic_5.5.23-1_i386.deb d7aa77719ad2cbe16c26105380f96531460a832e 4691974 libmysqld-dev_5.5.23-1_i386.deb 17ede696b7a4539ba3753cd22c2b2d6012c9e239 1201394 libmysqlclient-dev_5.5.23-1_i386.deb fcb960e4a03451aed67cc5e0cc49ce1e64087e46 9109236 mysql-client-5.5_5.5.23-1_i386.deb bb6d523e808d93bc04c907ec4075a62d00a29d50 5977230 mysql-server-core-5.5_5.5.23-1_i386.deb d30c5f3080054f57765000e679ed372c74e02c28 8665102 mysql-server-5.5_5.5.23-1_i386.deb 6d1aff9ff56768da4212099d740a70796987b9ad 8740234 mysql-testsuite-5.5_5.5.23-1_i386.deb 16db97ca9d6cdf226818a3eb6b5432317ecbe25a 28563590 mysql-source-5.5_5.5.23-1_i386.deb Checksums-Sha256: 30e6a9eb9f99228572f74ea81472ba58f779f113f77e2c279c1409d311c57d1e 2961 mysql-5.5_5.5.23-1.dsc 20a6303e281ac7875997c6c5e34b1129a02d1fb3f886b8ccb2c7b958cd67746a 24485979 mysql-5.5_5.5.23.orig.tar.gz 938c786fe27e698187323355a46ac1fd9e08d8555e50cfd81237de031eb5a2dc 299540 mysql-5.5_5.5.23-1.debian.tar.gz 2c364fe14b9f549a4614555f80e7e5d734af9dbd61b6c511cf295d5ea54828cc 70654 mysql-common_5.5.23-1_all.deb 14f715e9b1a71747f7fb1ecf9c67437ae0827d3772090902c45be57a6bd4e448 68310 mysql-server_5.5.23-1_all.deb 25259e794de5bca6cf546bc226cd596d7ad19203224df6dcb6c4f279021757e6 68192 mysql-client_5.5.23-1_all.deb 41ca4173d7ae6b8ca338e56ddbb25d5c20623245f2beb1ed12131325adc4de5c 863568 libmysqlclient18_5.5.23-1_i386.deb 0670c195eb307105aec5f7014530ba5d490700099eb105c617d9783a3fd314ea 4695072 libmysqld-pic_5.5.23-1_i386.deb bbce2bc5e4d77accebb46ddd89eb43f1e8d760c26b158e5c24302d4438234a80 4691974 libmysqld-dev_5.5.23-1_i386.deb 9e5fdfa2d50bc0117398ea6571b69e5402d4b7d4665093c14423bf13f057f9bb 1201394 libmysqlclient-dev_5.5.23-1_i386.deb 27c83ddde55a77a3f5f31f2437d93f502e93066f4d2ba617155158bb8e1462f0 9109236 mysql-client-5.5_5.5.23-1_i386.deb ac5fe0ba655c15799f88227ab85597e5d680a130c44688b32804318dfb4b9311 5977230 mysql-server-core-5.5_5.5.23-1_i386.deb 280a2cd8cc0e16ee53c97d93a63b76be359a5d008783720b16e825001b33516e 8665102 mysql-server-5.5_5.5.23-1_i386.deb 40bffcd7349746b9862731c3788b466fec936c098fd7d3d81fef61b20ecab055 8740234 mysql-testsuite-5.5_5.5.23-1_i386.deb f8e13c5c351d67f77dffd438a05cac6694d3fe0ce588251ace705bbf30930db3 28563590 mysql-source-5.5_5.5.23-1_i386.deb Files: 85a8714b473a56740941ffa86f3325c5 2961 database optional mysql-5.5_5.5.23-1.dsc b614481967dc146c148027b598397b54 24485979 database optional mysql-5.5_5.5.23.orig.tar.gz 7a9438bd58871cd5a8f82ba89d7424c8 299540 database optional mysql-5.5_5.5.23-1.debian.tar.gz 0c2689dacb49ba4a66adbca0245fda2b 70654 database optional mysql-common_5.5.23-1_all.
Bug#669796: seriously
clone 669796 -1 retitle -1 please split apache2-dev severity -1 wishlist reassign -1 apache2-dev thanks P.S. It is slightly odd that to *build* a package containing a pure perl CGI script I should need to install an actual apache2 instance. If apache2-dev could be split so that dh_apche2 and the debhelper stuff were in a separate arch:all package that does NOT depend on apache2 that would be good I think. On 02/05/12 20:03, Nicholas Bamber wrote: Arno, I managed to upgrade smoothly (albeit noisily) in a clean chroot environment. I guess I shall have to develop in that. On 30/04/12 22:08, Nicholas Bamber wrote: clone 669796 -1 retitle -1 w3c-markup-validator: transition towards Apache 2.4 user debian-apa...@lists.debian.org usertags -1 apache24webapptransition thanks Okay I tried upgrading to the experimental release of apache and I failed. It seems to me the experimental release needs some piuparts testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: seriously
clone 669796 -1 retitle -1 please split apache2-dev severity -1 wishlist reassign -1 apache2-dev thanks P.S. It is slightly odd that to *build* a package containing a pure perl CGI script I should need to install an actual apache2 instance. If apache2-dev could be split so that dh_apche2 and the debhelper stuff were in a separate arch:all package that does NOT depend on apache2 that would be good I think. On 02/05/12 20:03, Nicholas Bamber wrote: Arno, I managed to upgrade smoothly (albeit noisily) in a clean chroot environment. I guess I shall have to develop in that. On 30/04/12 22:08, Nicholas Bamber wrote: clone 669796 -1 retitle -1 w3c-markup-validator: transition towards Apache 2.4 user debian-apache@lists.debian.org usertags -1 apache24webapptransition thanks Okay I tried upgrading to the experimental release of apache and I failed. It seems to me the experimental release needs some piuparts testing. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa1875e.5060...@periapt.co.uk
Bug#669796: seriously
Arno, I managed to upgrade smoothly (albeit noisily) in a clean chroot environment. I guess I shall have to develop in that. On 30/04/12 22:08, Nicholas Bamber wrote: clone 669796 -1 retitle -1 w3c-markup-validator: transition towards Apache 2.4 user debian-apa...@lists.debian.org usertags -1 apache24webapptransition thanks Okay I tried upgrading to the experimental release of apache and I failed. It seems to me the experimental release needs some piuparts testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: seriously
Arno, I managed to upgrade smoothly (albeit noisily) in a clean chroot environment. I guess I shall have to develop in that. On 30/04/12 22:08, Nicholas Bamber wrote: clone 669796 -1 retitle -1 w3c-markup-validator: transition towards Apache 2.4 user debian-apache@lists.debian.org usertags -1 apache24webapptransition thanks Okay I tried upgrading to the experimental release of apache and I failed. It seems to me the experimental release needs some piuparts testing. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa18514.7070...@periapt.co.uk
Bug#671115: transition: mysql-5.5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition At some point we need to transition from mysql-5.1 to mysql-5.5. We would like to do this before the freeze though we appreciate that time is now short. We arrived at this position as the Debian MySQL Team became increasingly understaffed. It is better now but not ideal. We certainly will get mysql-5.5 into unstable in the next few weeks. The question is can we migrate all the dependencies over and drop mysql-5.1 before the freeze? If that fails then we will be left supporting a version of MySQL that is not supported upstream. As far as I can see the upstream packages that are likely to require recompilation are: amarok aolserver4-nsmysql asterisk-mysql bacula-common-mysql bacula-director-mysql bacula-sd-mysql boinc-dev boinc-server-maker cacti-spine cl-sql-mysql collectd collectd-core convirt coop-computing-tools courier-authlib-mysql ctn cvm-mysql dbf2mysql dbmail-mysql dovecot-mysql dpm-copy-server-mysql dpm-name-server-mysql dpm-server-mysql dpm-srm-server-mysql dsyslog-module-mysql emboss emboss-lib exim4-daemon-heavy ezmlm-idx-mysql facturlinex2 flow-tools freeradius-mysql gambas2-gb-db-mysql gdal-bin gentle gmysqlcc gnash-ext-mysql gnokii-smsd-mysql gnunet-server grass gsql-mysql-engine htcheck hydra inspircd jabberd2 kannel kannel-dev kannel-extras kannel-sqlbox kexi kexi-plugin-mysql lcd4linux lfc-server-mysql libapache2-mod-auth-mysql libapache2-mod-log-sql-mysql libapache2-mod-musicindex libaprutil1-dbd-mysql libaprutil1-dev libdbd-mysql libdbd-mysql-perl libdspam7-drv-mysql libgda-4.0-mysql libgda-5.0-mysql libgdal1 libgdal1-1.7.0 libgdal1-dev libgdal-dev libgdal-perl libgdal-ruby1.8 libghc-hsql-mysql-dev libglpk0 libglpk0-dbg libgsmsd7 libkaya-mysql-dev liblua5.1-sql-mysql-2 libmailutils2 libmyodbc libnss-mysql-bg libpam-mysql libpocodatamysql12 libpocomysql9 libpocomysql9-dbg libpreludedb0 libqt3-mt-mysql libqt4-dev libqt4-sql-mysql libquickfix14 libquickfix-python10 librdf0-dev librdf-storage-mysql libreoffice-mysql-connector libsasl2-modules-sql libslicer3 libvtk5.8 libvtk5.9 libvtk5-dev libvtk-java lighttpd-mod-mysql-vhost lua-dbi-mysql lua-sql-mysql matita mediatomb-common motion muddleftpd mydumper mysql-navigator mysqltcl mysql-workbench mysqmail-courier-logger mysqmail-dovecot-logger mysqmail-postfix-logger mysqmail-pure-ftpd-logger nagios-plugins-standard ndoutils-nagios3-mysql neko netams netmrg nuauth-extra nuauth-log-mysql opendnssec-enforcer-mysql opennebula paraview pdns-backend-mysql pennmush-mysql perdition-mysql php5-mysql pike7.8-mysql pmacct postfix-gld postfix-mysql proftpd-mod-mysql pure-ftpd-mysql pvpgn python-gammu python-gammu-dbg python-mysqldb python-mysqldb-dbg python-vtk qsf ratbox-services-mysql r-cran-rmysql rsyslog-mysql ruby-dataobjects-mysql ruby-mysql sagan sbnc-mysql scilab-scimysql ser-mysql-module slicer slurm-llnl-basic-plugins snort-common-libraries snort-mysql sphinxsearch spl-mysql stardict-tools sysbench tango-accesscontrol tango-db tcl-vtk tntdb-mysql2 ulogd-mysql voms-mysql-plugin wzdftpd-back-mysql xbmc-bin yate-mysql zabbix-proxy-mysql zabbix-server-mysql zoneminder -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa05b16.8060...@periapt.co.uk
Bug#671115: transition: mysql-5.5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition At some point we need to transition from mysql-5.1 to mysql-5.5. We would like to do this before the freeze though we appreciate that time is now short. We arrived at this position as the Debian MySQL Team became increasingly understaffed. It is better now but not ideal. We certainly will get mysql-5.5 into unstable in the next few weeks. The question is can we migrate all the dependencies over and drop mysql-5.1 before the freeze? If that fails then we will be left supporting a version of MySQL that is not supported upstream. As far as I can see the upstream packages that are likely to require recompilation are: amarok aolserver4-nsmysql asterisk-mysql bacula-common-mysql bacula-director-mysql bacula-sd-mysql boinc-dev boinc-server-maker cacti-spine cl-sql-mysql collectd collectd-core convirt coop-computing-tools courier-authlib-mysql ctn cvm-mysql dbf2mysql dbmail-mysql dovecot-mysql dpm-copy-server-mysql dpm-name-server-mysql dpm-server-mysql dpm-srm-server-mysql dsyslog-module-mysql emboss emboss-lib exim4-daemon-heavy ezmlm-idx-mysql facturlinex2 flow-tools freeradius-mysql gambas2-gb-db-mysql gdal-bin gentle gmysqlcc gnash-ext-mysql gnokii-smsd-mysql gnunet-server grass gsql-mysql-engine htcheck hydra inspircd jabberd2 kannel kannel-dev kannel-extras kannel-sqlbox kexi kexi-plugin-mysql lcd4linux lfc-server-mysql libapache2-mod-auth-mysql libapache2-mod-log-sql-mysql libapache2-mod-musicindex libaprutil1-dbd-mysql libaprutil1-dev libdbd-mysql libdbd-mysql-perl libdspam7-drv-mysql libgda-4.0-mysql libgda-5.0-mysql libgdal1 libgdal1-1.7.0 libgdal1-dev libgdal-dev libgdal-perl libgdal-ruby1.8 libghc-hsql-mysql-dev libglpk0 libglpk0-dbg libgsmsd7 libkaya-mysql-dev liblua5.1-sql-mysql-2 libmailutils2 libmyodbc libnss-mysql-bg libpam-mysql libpocodatamysql12 libpocomysql9 libpocomysql9-dbg libpreludedb0 libqt3-mt-mysql libqt4-dev libqt4-sql-mysql libquickfix14 libquickfix-python10 librdf0-dev librdf-storage-mysql libreoffice-mysql-connector libsasl2-modules-sql libslicer3 libvtk5.8 libvtk5.9 libvtk5-dev libvtk-java lighttpd-mod-mysql-vhost lua-dbi-mysql lua-sql-mysql matita mediatomb-common motion muddleftpd mydumper mysql-navigator mysqltcl mysql-workbench mysqmail-courier-logger mysqmail-dovecot-logger mysqmail-postfix-logger mysqmail-pure-ftpd-logger nagios-plugins-standard ndoutils-nagios3-mysql neko netams netmrg nuauth-extra nuauth-log-mysql opendnssec-enforcer-mysql opennebula paraview pdns-backend-mysql pennmush-mysql perdition-mysql php5-mysql pike7.8-mysql pmacct postfix-gld postfix-mysql proftpd-mod-mysql pure-ftpd-mysql pvpgn python-gammu python-gammu-dbg python-mysqldb python-mysqldb-dbg python-vtk qsf ratbox-services-mysql r-cran-rmysql rsyslog-mysql ruby-dataobjects-mysql ruby-mysql sagan sbnc-mysql scilab-scimysql ser-mysql-module slicer slurm-llnl-basic-plugins snort-common-libraries snort-mysql sphinxsearch spl-mysql stardict-tools sysbench tango-accesscontrol tango-db tcl-vtk tntdb-mysql2 ulogd-mysql voms-mysql-plugin wzdftpd-back-mysql xbmc-bin yate-mysql zabbix-proxy-mysql zabbix-server-mysql zoneminder -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#590905: symbols files
As far as I can see the state of the art way of resolving bugs like this one is to use pkg-kde-tools (http://pkg-kde.alioth.debian.org/symbolfiles.html) to generate and maintain the a symbols file (http://wiki.debian.org/UsingSymbolsFiles). This is known not to work very well with C++ but the libmysqlclient-dev header files at least appear to be C. I am not quite sure how the static library fits into this either. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669796: seriously
On 01/05/12 13:04, Arno Töll wrote: Hi, On 30.04.2012 23:08, Nicholas Bamber wrote: Okay I tried upgrading to the experimental release of apache and I failed. It seems to me the experimental release needs some piuparts testing. could you be a bit more verbose? I am not aware of any serious problem. I was planning on tying to produce some piuparts output. If that fails I'll have to try and upgrade in a chroot and capture the output. I still have not recovered from the mess quite fully. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670976: override: mysql-5.5:database/optional
Package: ftp.debian.org Severity: normal PTS is showing a lot of override discrepancies for mysql-5.5 now. I am not sure if database is the correct alternative to misc for all of them but it is the most obvious and what the debs have now. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669796: seriously
clone 669796 -1 retitle -1 w3c-markup-validator: transition towards Apache 2.4 user debian-apa...@lists.debian.org usertags -1 apache24webapptransition thanks Okay I tried upgrading to the experimental release of apache and I failed. It seems to me the experimental release needs some piuparts testing. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
seriously
clone 669796 -1 retitle -1 w3c-markup-validator: transition towards Apache 2.4 user debian-apache@lists.debian.org usertags -1 apache24webapptransition thanks Okay I tried upgrading to the experimental release of apache and I failed. It seems to me the experimental release needs some piuparts testing. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9eff55.1010...@periapt.co.uk
Bug#670873: and also
reassign 670873 libmysqlclient-dev thanks So libdaemon_example.so should be in libmysqlclient-dev as well. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666721: nice to haves
clone 666721 -1 severity -1 wishlist retitle -1 example plugins should be source code thanks I have tracked this down to one file. This can be excluded from the mysql-server-5.5 install. I expect also to be able to confim and verify fixed in a squeeze chroot. I am also cloning this bug report into a wishlist bit. It seems to me plugin examples should: 1.) be in souce code form 2.) be in the libmysqlclient-dev package 3.) be self contained and self-documented 4.) come with flying pigs as standard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#666721: nice to haves
clone 666721 -1 severity -1 wishlist retitle -1 example plugins should be source code thanks I have tracked this down to one file. This can be excluded from the mysql-server-5.5 install. I expect also to be able to confim and verify fixed in a squeeze chroot. I am also cloning this bug report into a wishlist bit. It seems to me plugin examples should: 1.) be in souce code form 2.) be in the libmysqlclient-dev package 3.) be self contained and self-documented 4.) come with flying pigs as standard -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589103: hmm
Okay the idea works up to a point and I am beginning to find my way around the sources. However I realized I had a fundamental issue. The kernel image (8.1) did not match the source (8.3). I upgraded but now the machine will not boot. Good thing I don't use this machine for something serious. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Accepted mysql-5.5 5.5.20-1 (source all i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 28 Apr 2012 15:02:16 +0100 Source: mysql-5.5 Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 mysql-server mysql-client mysql-testsuite-5.5 mysql-source-5.5 Architecture: source all i386 Version: 5.5.20-1 Distribution: experimental Urgency: low Maintainer: Debian MySQL Maintainers Changed-By: Nicholas Bamber Description: libmysqlclient-dev - MySQL database development files libmysqlclient18 - MySQL database client library libmysqld-dev - MySQL embedded database development files libmysqld-pic - PIC version of MySQL embedded server development files mysql-client - MySQL database client (metapackage depending on the latest versio mysql-client-5.5 - MySQL database client binaries mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf mysql-server - MySQL database server (metapackage depending on the latest versio mysql-server-5.5 - MySQL database server binaries and system database setup mysql-server-core-5.5 - MySQL database server binaries mysql-source-5.5 - MySQL source mysql-testsuite-5.5 - MySQL testsuite Closes: 649484 651002 651003 659565 659566 660799 663354 Changes: mysql-5.5 (5.5.20-1) experimental; urgency=low . [ Guillaume Plessis ] * d/rules: Enabling ARCHIVE, BLACKHOLE, and FEDERATED engines. (Closes: #649484) * d/rules: Turn off embedded libedit/readline.(Closes: #659566) . [ Clint Byrum ] * New Upstream Release * d/copyright: rearranging to have standalone license paragraphs silencing lintian complaints about missing paragraphs. * d/mysql-client-5.5.files: add mysql_plugin * d/rules, d/control: 5.5.20 Fixes segfault on tests with gcc 4.6, change compiler back to system default. * Sync changes back from Ubuntu: * d/control: need to also break mysql-client-core-5.1 and mysql-server-core-5.1 as well so that apt knows not to remove mysql-server/mysql-client. * d/control: convert mysql-server back to a meta-package * d/control: convert mysql-client back to a meta-package as well. * d/patches/72_fix_standalone_tests.patch: fix testsuite so it will run all tests when run from system /usr/lib/mysql-testsuite directory. 5.1 is removed from the archive. * d/control: mysql-common includes configuration items that only work on mysql 5.5, so adding Breaks: for client and server 5.1. This will make mysql-server-5.1 and mysql-client-5.1 uninstallable which is actually desired. * d/patches/71_disable_rpl_tests.patch: disables this test until Ubuntu bug #894146 can be triaged. * d/mysql-client-5.5.files: add missing mysql_plugin * d/libmysqlcient18.files,libmysqlclient-dev.files,d/rules: re-add libmysqlclient_r. In hindsight, removing it was not a productive change. * d/libmysqlclient-dev.files: ship entire contents of include dir, some of these files are included internally by others in the main dir. * d/patches/70_mysql_va_list.patch: cherry pick patch from upstream bug tracker to fix ARM build failure. (LP: #700982) . [ Nicholas Bamber ] * Added myself to Uploaders * Added libssl-dev as a build dependency and patched main.openssl_1 test so that it works with that library (Closes: #660799) * Added patch to provide cmake options for GNU/Hurd (Closes: #651002) and tweaked debian/rules so that only 'make test' is run on Hurd. * Tweaked debian/rules to make build logs verbose (Closes: #651003) * Refreshed patches - and added a new patch to disable a further flurry of failing tests * Switched on native AIO in linux builds (Closes: #659565) * Numerous minor changes to improve lintian cleanliness (Closes: #663354) - Added dh_lintian lines to debian/rules to ensure that lintian overrides take effect and removed old commented out lines - Clarified Hurd procps dependency in debian/control - Rewrote short description of the libmysqld-pic package to be more accurate - Depersonalised long description of mysql-client - Removed dependencies relating to mysql-common-4.1 - Tightened Breaks clauses for mysql-common - Removed duplicate entry from Replaces clauses for mysql-server-core-5.5 - Rexpressed Conflicts clause as versioned dependency for mysql-testsuite-5.5 - Added DEP-5 header fields to two patches - Refreshed and commented all lintian overrides and added override concerning lack of upstream changelog to all packages - Cleaned up debian/copyright * upgraded to latest version of DEP-5 * encoding issues * out of date FSF address * Updated License short name from "PD" to "public-domain" * Converted to short form
Bug#666721: hmm
tag 666721 +confirmed severity 666721 severe severity 512964 wishlist severity 540153 normal thanks Yes there really does seem to be such a conflict. Putting in some clauses like Breaks: libmysqlclient-dev (<< 5.5) Replaces: libmysqlclient-dev (<< 5.5) to the mysql-server-5.5 stanza should techincally fix it. However I worry that there is a deeper issue here. It seems to me that there is an ha_example.so in both mysql-server-5.5 and libmysqlclient-dev (>> 5.5) albeit different directories. That seems wrong to me. How did the ha_example.so file get to be in mysql-server-5.5. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#540153: another patch
Whilst investigating this I found that all the tests in the oiginal report worked fine. The tests all run to completion. I did however have an issue getting the tests kicked off at all due to what looks like to me like a kfreebsd specific Perl bug. In order to get round this I have hacked around in our old friend My::Platform::check_socket_path_length. Patch attached. Author: Nicholas Bamber Debian-Bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540153 Subject: tests not getting started on kFreeBSD As per #670722 I found that the test socket created to test file name truncation was barfing even for the shortened form. Forwarded: no Last-Update: 2012-04-28 --- a/mysql-test/lib/My/Platform.pm +++ b/mysql-test/lib/My/Platform.pm @@ -113,6 +113,8 @@ # Similarly the path length is hidden. # See Debian bug #651002 return 0 if ($^O eq 'gnu'); + # See Debian bug #670722 - failing on kFreeBSD even after setting short path + return 0 if length $path < 40; require IO::Socket::UNIX;
Bug#670636: [debian-mysql] Bug#670636: Multiple security issues in April security release
Moritz, The Debian MySQL team is debating pushing mysql 5.5 into unstable (including the latest upstream releases), transitioning the dependencies and dropping mysql 5.1. As such you probably won't see any activity on mysql 5.1 at all unless it becomes clear that this plan is unfeasible for some reason. On 27/04/12 14:39, Moritz Muehlenhoff wrote: Package: mysql-5.1 Severity: grave Tags: security Multiple - and yet again unspecified :-/ - security issues have been fixed in the April Oracle security release: http://www.oracle.com/technetwork/topics/security/cpuapr2012-366314.html#AppendixMSQL Affecting 5.1 and 5.5 CVE-2012-1703 MySQL ServerMySQL Protocol Server Optimizer CVE-2012-0583 MySQL ServerMySQL Protocol MyISAM CVE-2012-1688 MySQL ServerMySQL Protocol Server DML CVE-2012-1690 MySQL ServerMySQL Protocol Server Optimizer Affecting 5.5 only: CVE-2012-1697 MySQL ServerMySQL Protocol Partition CVE-2012-1696 MySQL ServerMySQL Protocol Server Optimizer Cheers, Moritz ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670636: [debian-mysql] Bug#670636: Multiple security issues in April security release
Moritz, The Debian MySQL team is debating pushing mysql 5.5 into unstable (including the latest upstream releases), transitioning the dependencies and dropping mysql 5.1. As such you probably won't see any activity on mysql 5.1 at all unless it becomes clear that this plan is unfeasible for some reason. On 27/04/12 14:39, Moritz Muehlenhoff wrote: Package: mysql-5.1 Severity: grave Tags: security Multiple - and yet again unspecified :-/ - security issues have been fixed in the April Oracle security release: http://www.oracle.com/technetwork/topics/security/cpuapr2012-366314.html#AppendixMSQL Affecting 5.1 and 5.5 CVE-2012-1703 MySQL ServerMySQL Protocol Server Optimizer CVE-2012-0583 MySQL ServerMySQL Protocol MyISAM CVE-2012-1688 MySQL ServerMySQL Protocol Server DML CVE-2012-1690 MySQL ServerMySQL Protocol Server Optimizer Affecting 5.5 only: CVE-2012-1697 MySQL ServerMySQL Protocol Partition CVE-2012-1696 MySQL ServerMySQL Protocol Server Optimizer Cheers, Moritz ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670722: perl-base: IO::Socket::UNIX::hostpath dies on kFreeBSD
Package: perl-base
Version: 5.14.2-9
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
The attached script comes from the MySQL test quite.
* What exactly did you do (or not do) that was effective (or
ineffective)?
It returns "SUCCESS" on Linux and "FAIL" on kFreeBSD. This is irrespective
of the length of the file.
There is an error message thrown which is in results.txt.
FAILED
Bad arg length for Socket::unpack_sockaddr_un, length is 106, should be 110 at
/usr/lib/perl/5.14/Socket.pm line 278.
#!/usr/bin/perl
use IO::Socket::UNIX;
use File::Temp qw /tempdir/;
# Create a tempfile name with same length as "path"
my $tmpdir = tempdir( CLEANUP => 0);
my $testfile = $tmpdir . "/" . "x" x 3;
my $truncated = 0;
my $sock;
eval {
$sock= new IO::Socket::UNIX
(
Local => $testfile,
Listen => 1,
);
$truncated= 1; # Be negatvie
die "Could not create UNIX domain socket: $!" unless defined $sock;
die "UNIX domain socket path was truncated" unless ($testfile eq $sock->hostpath());
$truncated = 0;
};
print $truncated ? "FAILED\n" : "SUCCESS\n";
print "$@\n" if $@;
Bug#536266: not here
reassign 536266 mysql-5.1 thanks mysql-5.5 uses cmake not automake of any variety. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512964: [debian-mysql] Bug#512964: sympathy
On 27/04/12 20:31, Olaf van der Spek wrote: On Fri, Apr 27, 2012 at 12:01 AM, Nicholas Bamber wrote: I feel some sympathy with this bug report. I don't see for what reason we are overriding dpkg-buildpackage. I guess we could look at and clear MAKE_J if MAKEFLAGS has a -j option in it. That section would definitely need a comment as by then it would be getting complicated. What's the reason for the override? Why not drop it? As I said I have sympathy with the bug report and dropping it would simplify debian/rules. Obviously the reason for the override is to make the build go as fast as possbible, but "dpkg-buildpackage -jN" does almost the same. By the way "DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage" cuts out the testing phase which is quite useful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Accepted w3c-sgml-lib 1.2-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 27 Apr 2012 12:18:44 +0100 Source: w3c-sgml-lib Binary: w3c-sgml-lib Architecture: source all Version: 1.2-3 Distribution: unstable Urgency: high Maintainer: Nicholas Bamber Changed-By: Nicholas Bamber Description: w3c-sgml-lib - w3.org DTD and catalog files Closes: 615125 Changes: w3c-sgml-lib (1.2-3) unstable; urgency=high . * Split out w3c-dtd-xhtml again and added Conflicts clause (Closes: #615125) Checksums-Sha1: 911681fd5c7d614a3e58343a9a0701fbfafa69d7 1900 w3c-sgml-lib_1.2-3.dsc 474e16ec6061c51e34245de539687cb80a39bbbd 4769 w3c-sgml-lib_1.2-3.debian.tar.gz 6846700992a5fa66cbd2ff3b53262e72f2573f00 568168 w3c-sgml-lib_1.2-3_all.deb Checksums-Sha256: e26e716c6f37099ac5a0dd0b02f6a0ef4bfc78f1bd1dd56d424babb3556cb745 1900 w3c-sgml-lib_1.2-3.dsc ae7f43cb0533bef61b12e4ec38258ffcc84d2ba46cecdca1b45660eed73751fb 4769 w3c-sgml-lib_1.2-3.debian.tar.gz 5aa17b80badea3c3d4e3d8b367736734834155f4be36cfdf98828ebe968573d1 568168 w3c-sgml-lib_1.2-3_all.deb Files: 83afef221a65a892eae71f1d227933b1 1900 text optional w3c-sgml-lib_1.2-3.dsc 6da4ec9741410986f0c0a9da856ef5b5 4769 text optional w3c-sgml-lib_1.2-3.debian.tar.gz ee51ef831899e92c8cab164a04db2f28 568168 text optional w3c-sgml-lib_1.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPmoEhAAoJELbE2bY7/+c8gtMQAJveoz3qQ87sOK/ZYxmsHNQ2 hCTNKN9P5y4aZD0tWmTFpIpEAh+rrrw7izFrrCU/GCgBQbA+o7kmJAfW7PTWh53e OI0Y+qL/9CuVSN3XTLbUt5a+VIkW/XFQrH9siJ7LpevMOZDGORiRJLM3DowUPPut tRXw3yvNb+hlkixzMMR8MLodPHZbi/E7pPNJKFUX1ZVjCzCH+2c9Us7riIzVcgt+ wxRlCNSrMH8e0PKm2vOT1XTZHX4/mHlUgw38AaRW2yh8r4Uh743PwXBm8EfLckMz pmW2cmqpgdcft71xY5MZQjFlqIMCcHb++JlKenR/ZGafSNWXLimDUjK32ftKao4B 7rFFn2YMTEoWdT3Oo7kjyqnPhWizGSkBdtxZWisUVZ71zT1i5oSce0WSwUZpdk1P M5pbp7/wZSaUB1LCrWr438TXLs0vsaeHJV7Ji0RvXpxUmqR8P8ct1bbd+k+1cW8v RSV9R4RIZ29uIIuuc2FjMauM9NhkfoozUYRY0JhdpZKdg1QGmedTCQ9R5GLJoBvH 5yCkE8V2i2HBSri1uCZkX1XLU7TnZ/By9kzTd5i+BAvMM0MRPYtIy1slIfd9fId3 toSEI9v97QQBErfw+WMPP46XbV6Gxjy7RyePxfDhpkX52KuTnkQwXbbK7Eci09kN kKazjR13NHkDw0sGrjOP =DFvK -END PGP SIGNATURE- Accepted: w3c-sgml-lib_1.2-3.debian.tar.gz to main/w/w3c-sgml-lib/w3c-sgml-lib_1.2-3.debian.tar.gz w3c-sgml-lib_1.2-3.dsc to main/w/w3c-sgml-lib/w3c-sgml-lib_1.2-3.dsc w3c-sgml-lib_1.2-3_all.deb to main/w/w3c-sgml-lib/w3c-sgml-lib_1.2-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/e1snjue-0003tl...@franck.debian.org
Accepted w3c-dtd-xhtml 1.2-3 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 27 Apr 2012 12:15:27 +0100 Source: w3c-dtd-xhtml Binary: w3c-dtd-xhtml Architecture: source all Version: 1.2-3 Distribution: unstable Urgency: high Maintainer: Nicholas Bamber Changed-By: Nicholas Bamber Description: w3c-dtd-xhtml - W3C eXtensible HyperText Markup Language (XHTML) DTD Changes: w3c-dtd-xhtml (1.2-3) unstable; urgency=high . * Split out from w3c-sgml-lib again (cf. #615125) Checksums-Sha1: 9dc370583d2ee61d42b37b9b0066708a3cfbf5d4 1444 w3c-dtd-xhtml_1.2-3.dsc 6f40918c017caf101e74ead8e7ab1fc7cd62aaf2 990626 w3c-dtd-xhtml_1.2-3.tar.gz d1034c67e0ac3429b1b9d2a2bc97a8ac8ab159b8 92184 w3c-dtd-xhtml_1.2-3_all.deb Checksums-Sha256: d02cdda6a2491a97e8c02ed9488796aa36dd0c1e4ebcca54f3c7170ab05b51ac 1444 w3c-dtd-xhtml_1.2-3.dsc 0ac9425ceb82eadc0a2a97d17726168118144cba0d1a7b01a2a1555d1b3e6359 990626 w3c-dtd-xhtml_1.2-3.tar.gz d2052576ffdf7f838ec01ddae150f334d0e6bd68829e4d9c3f90fcfa54abf7dc 92184 w3c-dtd-xhtml_1.2-3_all.deb Files: e06b949a1ccf575e9e85d49fde79db16 1444 text optional w3c-dtd-xhtml_1.2-3.dsc 21de29b1d422a95d0c733ff93e248a15 990626 text optional w3c-dtd-xhtml_1.2-3.tar.gz eb773fe549f7e091a9df83e58840bc0d 92184 text optional w3c-dtd-xhtml_1.2-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPmoBuAAoJELbE2bY7/+c8imIQAOxpJZ8gYB2PjcRRoPwmLblk UevX6mqz2Pd3YVhR80nzvP+PXaFNVJe/Rvmg7PIHxZqmmUK+7oxBr4hk5sfVqwLn AUmPOT6VlZKOFE/LR4iexTwj1Clzi+qhxc+eSZRRRY1h6HV1U+QJQ/rHOWCmqopq GneUwdAxdWfi92yWaFmGIOFSjNK3G2KT9iuNUzFfsk6Dd05uAOeb/CC40knGqPEH kNrEO9vv+liOFrQyl0RJlH7p6a3j7rvFlsY9uoJrjEZBP4muxN53eGxXkyTTtim6 2WVMH7UAw0FgVSIfvfyn8WbkJC9kEbGUW1EjbYi7oN05K9Brx8TFnVPMKFMY12KH lfH5w2lW/j2gmc9ihPQGuy+MbjVc/89NYCVmf/EcWQUCjL2YUR6FhTlTTYzqvhOd Idl7HUK8WFdx7jd9cjSa7xT0iT29AftcfAue+p4Q9QAIse1x+qbtX+4Es7PdbdML 5uZUi2JzRVCJxTGwK5z9bPP29WWGXSmawHIIOKVg/eQE4bATBZhT1tgzMnGvnf3K qPTFYWIThBqcny8NweQGWDwJh0PylD1Hp5U5lZ2LFNWAsS1m+OYNFwbSwYC/2abO lU49e7I/2djpp1mBVtea4o48XoPjAm5nampGAvdrDFHvTFtfrhItxKR87xGxOyu9 z268Yc+GMe8QJ+E/eLrn =ThgE -END PGP SIGNATURE- Accepted: w3c-dtd-xhtml_1.2-3.dsc to main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.2-3.dsc w3c-dtd-xhtml_1.2-3.tar.gz to main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.2-3.tar.gz w3c-dtd-xhtml_1.2-3_all.deb to main/w/w3c-dtd-xhtml/w3c-dtd-xhtml_1.2-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/e1snju0-0003re...@franck.debian.org
Bug#394510: reassign
reassign 394510 libmysqlclient16 thanks I am sure that this bug report dies with mysql5.1. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
w3c stuff
Thanks for raising this bug on w3c-linkchecker. I was totally short on bug reports especially on packages beginning with "w". But anyway I reckon you might be able to squeeze in one more on w3c-markup-validator. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f9a3651.9090...@periapt.co.uk
Bug#669796: w3c stuff
Thanks for raising this bug on w3c-linkchecker. I was totally short on bug reports especially on packages beginning with "w". But anyway I reckon you might be able to squeeze in one more on w3c-markup-validator. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#512964: sympathy
I feel some sympathy with this bug report. I don't see for what reason we are overriding dpkg-buildpackage. I guess we could look at and clear MAKE_J if MAKEFLAGS has a -j option in it. That section would definitely need a comment as by then it would be getting complicated. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: [debian-mysql] mysql-5.1 or both mysql-5.5/1
On 26/04/12 08:38, Jonathan Aquilina wrote: To make your life easier Nicholas couldnt you pull the 5.5 packages from ubuntu and start transitioning using those packages? Jonathan, I am working on modernizing debian/rules and generally understanding the package and triaging etc. People who know Ubuntu better than I do are better placed to merge in those changes. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f99af71.9000...@periapt.co.uk
Re: [debian-mysql] mysql-5.1 or both mysql-5.5/1
Another approach is to hedge our bets a bit. 1.) complete nysql-5.5 going into unstable 2.) migrate dependents onto 5.5 (which AFAIK if it is just a rebuild is a job for the release team) and kick off the translation process. 3.) Then take a view on whether drop 5.1 or fix the RC bugs in 5.1 and have both. On 25/04/12 18:59, Clint Byrum wrote: Excerpts from Jonathan Aquilina's message of Wed Apr 25 09:23:31 -0700 2012: On 4/25/12 6:18 PM, Clint Byrum wrote: Excerpts from Jonathan Aquilina's message of Tue Apr 24 23:07:10 -0700 2012: I know I am not part of the team to make this final decision, but this is how I feel about the situation. This has a double edged sword given by the arguments below. A transition is going to have to happen at some point, and I think the biggest thing to consider is this. I had red some documentation, and 5.5 has had a bunch of performance enhancements done to the InnoDB engine. Also from some oracle devs that I have spoken to more performance enhancements are slated for 5.6. I am running a number of ubuntu servers, and I am actually considering installing 5.5 which would be nice to have in the repositories and eventually in a down stream ubuntu release. Its important to note that Ubuntu already did this transition. Ubuntu 12.04 (releasing tomorrow) ships with MySQL 5.5.22, and 5.1 has been dropped from future Ubuntu releases. So there is at least some precedent. The transition went rather smoothly. Most of the fixes done in Ubuntu packages were pushed back into Debian and have been applied to the Debian packages. 99% of the problem was packages with build-depends on libmysqlclient16-dev instead of libmysqlclient-dev. I would expect a rebuild transition to pickup the new version of libmysqlclient. There are a few things which directly recommend or suggest mysql-*-5.1, but those are, IMO, bugs, as the meta package is the only one that will always be around. Clint couldnt you just pull from downstream and make the necessary adaptations in regards to the packages for debian? In effect, I am downstream. I did most of the work in Ubuntu to complete the 5.5 transition, and pushed most of it back up to Debian maintainers as patches. As we got later in the 12.04 release cycle, I had less time to push things back through Debian. I also have been stalled out a bit in my DD application process, so I've been relying on sponsors. Luckily Nicholas has stepped up and can sponsor uploads for me. I fully intend to spend some time on getting the 5.5 packages up to date and in shape in experimental. Whether or not we can move them into unstable/testing, I don't know. ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f987a6a.5040...@periapt.co.uk
Accepted lsof 4.86+dfsg-1 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 25 Apr 2012 07:11:12 +0100 Source: lsof Binary: lsof Architecture: source i386 Version: 4.86+dfsg-1 Distribution: unstable Urgency: low Maintainer: Norbert Tretkowski Changed-By: Nicholas Bamber Description: lsof - Utility to list open files Closes: 520587 596393 Changes: lsof (4.86+dfsg-1) unstable; urgency=low . [ Nicholas Bamber ] * Imported into git.debian.org and documented procedures in README.source . [ Raoul Gunnar Borenius ] * New upstream release (Closes: #596393) and (Closes: #520587) * packaging is now done with plain debhelper. * updated debian/control (added Uploaders:, include upstream homepage, bumped standards version, etc.) * changed debian/copyright to latest format * added debian/patches/examples to correct path to perl interpreter * added debian/patches/manpage to add missing escape signs in manpage * added watch file and uscan helper files (repack.stub, repack.local) in preparation for downloading and dfsg-repackaging of the newest source. . [ Nicholas Bamber ] * New upstream release (4.86) and refreshed manpage patch * Added additional mirrors to watch file * Marked examples patch as not requiring forwarding * Removed obsolete debian/control clauses * Enabled all tests apart from the NFS based test * Passed '-n freebsd' to ./Configure on freebsd builds (cf. #589103) * Added main comment to debian/copyright explaining modifications to upstream tarball and added missing copyright stanzas Checksums-Sha1: 08511e204e955c4a366a307882a568c8c2d796d3 1917 lsof_4.86+dfsg-1.dsc 12920b1172bd24406b4f7c706a423b0b1fcb30b7 1035875 lsof_4.86+dfsg.orig.tar.gz 9fb896cdde16d961d1ca544b8198220c1ca31edc 17840 lsof_4.86+dfsg-1.debian.tar.gz 6e1ccbb971529eeeaa7bc1ac51359471b450e697 312394 lsof_4.86+dfsg-1_i386.deb Checksums-Sha256: 488456a8d2a922094d67aa039827911952b0eff77febf94594f69830964010b8 1917 lsof_4.86+dfsg-1.dsc bfee7fcd5d260514b9f2e7ea9293b12cfb3d6b681545b4dd37b660e60aef4149 1035875 lsof_4.86+dfsg.orig.tar.gz 5f4daf7a2761b0d03d23225f9b5f37e82aff3e951a7aa7fd56820579d8359772 17840 lsof_4.86+dfsg-1.debian.tar.gz 403e6ca51d8d9426b1288f130aedee2c819b18cd499cdb3932c1bc0ea5277c33 312394 lsof_4.86+dfsg-1_i386.deb Files: eec6024949d4ef006bf3442179b54567 1917 utils standard lsof_4.86+dfsg-1.dsc 23420509564a897b76055f9d84d19068 1035875 utils standard lsof_4.86+dfsg.orig.tar.gz 0119f55eb93509256f53eb416e3f2871 17840 utils standard lsof_4.86+dfsg-1.debian.tar.gz 54843ff7dc2d70f9d3c77be1501844f1 312394 utils standard lsof_4.86+dfsg-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPl5h9AAoJELbE2bY7/+c8TKkP/19uKhkqmutOHpJnjTn/75e4 0oi2obXYF4/dwMv20zlVRsGKb2ICfexeLLWz4mIum66v0iFBYeiufnAchFd3jnZn TzZ8RopLySkIj8V4OzAwuw0KElQAHTcVshH1eY1rVxPECmwCrBQvYBeoQ5RjphwV vruphvZsYo8U9kBFbpzzlXHGGR8a2IT6LBuqftlwupsHRO5bzLbZ4rNqLn4FBwxt mq+oKcvSo/uB4MRjCGuCfd/RFfzc7GPVFx43IolDOlWHXEXYApBjfYEsvyMz6V0N TsR5n+I0b0pTeuKxC3JXXVvw0I5ziw+Hrvf3Ovr6rlqAI2NfYkV7qlvVIPyh29cR +URcRu5zPbr1NH5CtVijdhANGP/h+wgAoVwkc6U6JbdeF2jWK9QCqarCicxoPz+h ZHIPRaksnkWOT588zG0DdIZ1PxxiSwUJscfQ7S1XM/5xDxLDpGeoHEOqLUIazmqL Wk3lX/w2y+LI/6aToB19nw1OjkapdyAePRIHYyWGiX+xwHfHb/TqdtwcDlis3ToP Ky4Wf1OrifGWMb8qxas988UfjFEh6AeKwfholjx7473bmcK9xZfbUXSv4tDa6Rfj jWmAKkCh7JL6vEEoGTJEjwU0s0i2IbVOJVxtvZwaq/ReCIxHvwTrXYgXbBAPPmq8 Eu4psrOX4m3DLUthcSA8 =TsqS -END PGP SIGNATURE- Accepted: lsof_4.86+dfsg-1.debian.tar.gz to main/l/lsof/lsof_4.86+dfsg-1.debian.tar.gz lsof_4.86+dfsg-1.dsc to main/l/lsof/lsof_4.86+dfsg-1.dsc lsof_4.86+dfsg-1_i386.deb to main/l/lsof/lsof_4.86+dfsg-1_i386.deb lsof_4.86+dfsg.orig.tar.gz to main/l/lsof/lsof_4.86+dfsg.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/e1smvmb-0006zo...@franck.debian.org
Bug#661575: lsof on Hurd
On 25/04/12 00:42, Samuel Thibault wrote: Roland McGrath, le Tue 24 Apr 2012 16:34:52 -0700, a écrit : Of course, but that doesn't change the actual issue: I don't think there is any interface to actually implement /proc/*/fd either. See msg.defs. That will give only ports to the fds. How to get back to actual file paths? Samuel That actually rings a bell from some other Hurd issue. Isn't there some bit of purest thinking that we have no right to assume that a file descripter actually implies a physical file, hence the question just cannot be asked. If that is so then the best Hurd might ever be able to offer lsof is the current /proc file system. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#661575: lsof on Hurd
On 25/04/12 00:42, Samuel Thibault wrote: Roland McGrath, le Tue 24 Apr 2012 16:34:52 -0700, a écrit : Of course, but that doesn't change the actual issue: I don't think there is any interface to actually implement /proc/*/fd either. See msg.defs. That will give only ports to the fds. How to get back to actual file paths? Samuel That actually rings a bell from some other Hurd issue. Isn't there some bit of purest thinking that we have no right to assume that a file descripter actually implies a physical file, hence the question just cannot be asked. If that is so then the best Hurd might ever be able to offer lsof is the current /proc file system. -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f973d17.9030...@periapt.co.uk
Bug#661575: lsof on Hurd
On 24/04/12 23:14, Samuel Thibault wrote: Nicholas Bamber, le Tue 24 Apr 2012 22:33:15 +0100, a écrit : There seems to be no support in the lsof code for the Hurd operating system. I cannot say I am surprised but it does I believe meet your criteria for support as it is readily available for download and installation as per http://www.debian.org/ports/hurd/ . I have copied the Debian Hurd mailing list as they are most likely to be able to provide patches and advice. Well, I don't think the Hurd already has interfaces for lsof to get any information. That would have to be added first... Samuel Samuel, AFAIK I think if the /proc filesystem had /proc/*/fd you'd be pretty much there. I guess I should have copied an upstream Hurd mailing list as well. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: lsof on Hurd
On 24/04/12 23:14, Samuel Thibault wrote: Nicholas Bamber, le Tue 24 Apr 2012 22:33:15 +0100, a écrit : There seems to be no support in the lsof code for the Hurd operating system. I cannot say I am surprised but it does I believe meet your criteria for support as it is readily available for download and installation as per http://www.debian.org/ports/hurd/ . I have copied the Debian Hurd mailing list as they are most likely to be able to provide patches and advice. Well, I don't think the Hurd already has interfaces for lsof to get any information. That would have to be added first... Samuel Samuel, AFAIK I think if the /proc filesystem had /proc/*/fd you'd be pretty much there. I guess I should have copied an upstream Hurd mailing list as well. -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f97264a.6000...@periapt.co.uk
lsof on Hurd
tag 661575 +help forwarded 661575 a...@purdue.edu thanks Abe, Thanks again for your work on lsof. There seems to be no support in the lsof code for the Hurd operating system. I cannot say I am surprised but it does I believe meet your criteria for support as it is readily available for download and installation as per http://www.debian.org/ports/hurd/ . I have copied the Debian Hurd mailing list as they are most likely to be able to provide patches and advice. Thanks. Nicholas -- To UNSUBSCRIBE, email to debian-hurd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f971c1b.70...@periapt.co.uk
Bug#661575: lsof on Hurd
tag 661575 +help forwarded 661575 a...@purdue.edu thanks Abe, Thanks again for your work on lsof. There seems to be no support in the lsof code for the Hurd operating system. I cannot say I am surprised but it does I believe meet your criteria for support as it is readily available for download and installation as per http://www.debian.org/ports/hurd/ . I have copied the Debian Hurd mailing list as they are most likely to be able to provide patches and advice. Thanks. Nicholas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
mysql-5.1 or both mysql-5.5/1
Release team, We are debating whether to a.) allow both mysql-5.1 and mysql-5.5 to go into wheezy or b.) whether to try and effect a transition to 5.5 Arguments for b.) - 1.) More effort (such as it is) is already going into mysql-5.5 2.) 5.1 will not be supported for much longer 3.) Being able to remove 5.1 will kill 4 RC bugs and save an overworked team time 4.) The distinction between the major versions is becoming artificial. [See comments from below] 5.) Consider the implications for Ubuntu etc. Arguments for a.) - 1.) 5.1 has been in testing for a long time 2.) 5.5 has not yet been released to testing 3.) When it is released to testing RC bugs will doubtless pop up all too late 4.) All the packages that depend on one of the libraries will have to be transitioned 5.) Someone will have to kick off the translation effort. Your input would be appreciated. On 24/04/12 19:03, Clint Byrum wrote: Excerpts from Olaf van der Spek's message of Tue Apr 24 02:35:39 -0700 2012: On Tue, Apr 24, 2012 at 7:59 AM, Nicholas Bamber wrote: I don't approach 5.1 with any sort of relish. However I think we have a duty to maintain it until the freeze as otherwise it will undermine Debian's release cycle. Or at the very least we ought to check with the release team. What's the plan for next stable? 5.1? 5.5? Both? I'd prefer to see MySQL 5.5 in wheezy, but if its too late for that transition, then I suppose we can't get that done. It would be a shame, because 5.5 is a much better release. As soon as MySQL 5.6 arrives, Oracle will start the process of deprecating 5.1 and stop providing security updates for it quite soon. They do not maintain 3 GA releases. Do you mean the source package would no longer be versioned or all the packages? I mean the source package. I find it very strange that it has been mysql-dfsg-5.0 mysql-dfsg-5.1 mysql-5.1 mysql-5.5 When it really should just have been mysql This makes things like packages.qa.debian.org work in a weird way, and also bugs in Ubuntu are source-package oriented so often bugs end up affecting 4 or 5 source packages which is confusing and cumbersome for no benefit that I can perceive. The binary packages are, I think, named and versioned appropriately and should remain that way. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f970b03.1040...@periapt.co.uk
Bug#589103: kfreebsd
So I have my approach sketched out in the "asparagus" branch of the code. I cannot test it however as asdfasdf.debian.net does not have any kfreebsd-source installed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#615125: okay
reopen 615125 severity 615125 grave thanks Joey, Okay. What I will do is put w3c-dtd-xhtml exactly back to how it was except for the Home page bug, a suitable changelog entry, a Conflicts clause and a 1.2-3 version number. w3c-dgml-lib will be put how it was just before I attempted merger -- i.e. will have a Conflicts clause with w3c-dtd-xhtml. Then once those are in testing I will raise a wishlist bug report against wdg-html-validator asking it try using w3c-sgml-lib or at least either. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, On 20/04/12 01:38, Joey Hess wrote: Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. w3c-sgml-lib 1.2-1 does provide/conflict/replace w3c-dtd-xhtml. Yes and it is not present in 1.2-2. Nor does w3c-sgml-lib exist in stable. So actually if we just let it go to testing everything would be fine. ;-) Seriously I will not do that unless you are happy with it and there are still backports and derivatives to worry about. Please could you run this test. Uninstall w3c-dtd-xhtml and all its dependents and reinstall wdg-html-validator with the latest chain. Does that have any issues for you? Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. See end of transcript in my previous mail. Sorry I was in too much of a hurry to see that before. Thanks. Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? update-xmlcatalog: error: entity already registered with a different value Entity : [delegatePublic publicIdStartString="-//W3C//ENTITIES Latin 1 for XHTML//EN"] Old value: [catalog="file:///etc/xml/w3c-sgml-lib.xml"] New value: [catalog="file:///etc/xml/w3c-dtd-xhtml.xml"] dpkg: error processing w3c-dtd-xhtml (--install): And in this state, no, validate does not work. For me the nightmare scenario is that I just have to give up and make w3c-sgml-lib and w3c-dtd-xhtml have mutual conflicts clauses because they define the same entities. I think the Debian policy implies that in that case both packages and all depeendencies should move to "extra" priority which I think would be dreadful. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f91d59c.2000...@periapt.co.uk
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, On 20/04/12 01:38, Joey Hess wrote: Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. w3c-sgml-lib 1.2-1 does provide/conflict/replace w3c-dtd-xhtml. Yes and it is not present in 1.2-2. Nor does w3c-sgml-lib exist in stable. So actually if we just let it go to testing everything would be fine. ;-) Seriously I will not do that unless you are happy with it and there are still backports and derivatives to worry about. Please could you run this test. Uninstall w3c-dtd-xhtml and all its dependents and reinstall wdg-html-validator with the latest chain. Does that have any issues for you? Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. See end of transcript in my previous mail. Sorry I was in too much of a hurry to see that before. Thanks. Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? update-xmlcatalog: error: entity already registered with a different value Entity : [delegatePublic publicIdStartString="-//W3C//ENTITIES Latin 1 for XHTML//EN"] Old value: [catalog="file:///etc/xml/w3c-sgml-lib.xml"] New value: [catalog="file:///etc/xml/w3c-dtd-xhtml.xml"] dpkg: error processing w3c-dtd-xhtml (--install): And in this state, no, validate does not work. For me the nightmare scenario is that I just have to give up and make w3c-sgml-lib and w3c-dtd-xhtml have mutual conflicts clauses because they define the same entities. I think the Debian policy implies that in that case both packages and all depeendencies should move to "extra" priority which I think would be dreadful. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f91d59c.2000...@periapt.co.uk
Bug#625262: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, On 20/04/12 01:38, Joey Hess wrote: Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. w3c-sgml-lib 1.2-1 does provide/conflict/replace w3c-dtd-xhtml. Yes and it is not present in 1.2-2. Nor does w3c-sgml-lib exist in stable. So actually if we just let it go to testing everything would be fine. ;-) Seriously I will not do that unless you are happy with it and there are still backports and derivatives to worry about. Please could you run this test. Uninstall w3c-dtd-xhtml and all its dependents and reinstall wdg-html-validator with the latest chain. Does that have any issues for you? Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. See end of transcript in my previous mail. Sorry I was in too much of a hurry to see that before. Thanks. Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? update-xmlcatalog: error: entity already registered with a different value Entity : [delegatePublic publicIdStartString="-//W3C//ENTITIES Latin 1 for XHTML//EN"] Old value: [catalog="file:///etc/xml/w3c-sgml-lib.xml"] New value: [catalog="file:///etc/xml/w3c-dtd-xhtml.xml"] dpkg: error processing w3c-dtd-xhtml (--install): And in this state, no, validate does not work. For me the nightmare scenario is that I just have to give up and make w3c-sgml-lib and w3c-dtd-xhtml have mutual conflicts clauses because they define the same entities. I think the Debian policy implies that in that case both packages and all depeendencies should move to "extra" priority which I think would be dreadful. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f91d59c.2000...@periapt.co.uk
Bug#615125: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, On 20/04/12 01:38, Joey Hess wrote: Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. w3c-sgml-lib 1.2-1 does provide/conflict/replace w3c-dtd-xhtml. Yes and it is not present in 1.2-2. Nor does w3c-sgml-lib exist in stable. So actually if we just let it go to testing everything would be fine. ;-) Seriously I will not do that unless you are happy with it and there are still backports and derivatives to worry about. Please could you run this test. Uninstall w3c-dtd-xhtml and all its dependents and reinstall wdg-html-validator with the latest chain. Does that have any issues for you? Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. See end of transcript in my previous mail. Sorry I was in too much of a hurry to see that before. Thanks. Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? update-xmlcatalog: error: entity already registered with a different value Entity : [delegatePublic publicIdStartString="-//W3C//ENTITIES Latin 1 for XHTML//EN"] Old value: [catalog="file:///etc/xml/w3c-sgml-lib.xml"] New value: [catalog="file:///etc/xml/w3c-dtd-xhtml.xml"] dpkg: error processing w3c-dtd-xhtml (--install): And in this state, no, validate does not work. For me the nightmare scenario is that I just have to give up and make w3c-sgml-lib and w3c-dtd-xhtml have mutual conflicts clauses because they define the same entities. I think the Debian policy implies that in that case both packages and all depeendencies should move to "extra" priority which I think would be dreadful. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#589103: lsof on Debian FreeBSD
Steven, Thanks for your quick response and efforts. Crucially when I poke around in /proc/self on asdfasdf.debian.net (or the Hurd exodar.debian.net for that matter) I can find no /proc/sef/fd directory. From what I understand that is crucial to a /proc-basd lsof. Please feel free to check in your experiments into the collab-maint repository but please could you do it on a "kfreebsd" branch. We could release it to the experiemntal distribution. On 20/04/12 03:23, Steven Chamberlain wrote: Hi! On 20/04/12 00:45, Nicholas Bamber wrote: 8.6Why can't Configure create lsof_owner.h for FreeBSD 6 and above? ... Lsof needs to access elements of that lockf_owner structure to determine if a lock belongs to the process that has a file open. The goal really is to keep userland tools out of kernel internals to produce better software; that's one of many good things I hope will come as a side effect out of the GNU/kFreeBSD effort. Since the 'freebsd' dialect of lsof has been relying on kernel internals for some time, I expect that code will be in pretty bad shape. You could try to get what you need from the kfreebsd source but I think it would be a bad idea. (A kernel with an incompatible definition might be booted at any time, and no dpkg dependency can help with that). However, if the 'linux' dialect does not depend on kernel source code I think that would make a better starting point. I tried just now with the freebsd/machine.h and Makefile, but replaced the symlinks to use dialect/linux code instead, except for node1/2 and zfs. That way I even managed to build something, which almost looks like it works: steven@kfreebsd-i386:~/lsof-4.81.dfsg.1+wtf$ ./lsof -c lsof COMMAND PID USER FD TYPEDEVICE SIZE NODE NAME lsof99812 steven cwdDIR 92,2340356138 72 15497 /home/steven/lsof-4.81.dfsg.1+wtf lsof99812 steven rtdDIR 0,71512 2 / lsof99812 steven txtREG 92,2340356138 145071 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof lsof99812 steven memREG 0,0 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof (path dev=92,-1954611158) lsof99812 steven memREG 0,0117963 /lib/i386-kfreebsd-gnu/ld-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0213682 /etc/ld.so.cache (path dev=0,71) lsof99812 steven memREG 0,0117953 /lib/libkvm.so.0 (path dev=0,71) lsof99812 steven memREG 0,0117809 /lib/i386-kfreebsd-gnu/i686/cmov/libc-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117827 /lib/i386-kfreebsd-gnu/libbsd.so.0.3.0 (path dev=0,71) lsof99812 steven memREG 0,0108648 /usr/lib/locale/locale-archive (path dev=164,284950746) lsof99812 steven memREG 0,0117898 /lib/i386-kfreebsd-gnu/i686/cmov/libnss_compat-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117829 /lib/i386-kfreebsd-gnu/i686/cmov/libnsl-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117834 /lib/i386-kfreebsd-gnu/i686/cmov/libnss_nis-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117838 /lib/i386-kfreebsd-gnu/i686/cmov/libnss_files-2.13.so (path dev=0,71) lsof99812 steven NOFD/proc/99812/fd (opendir: No such file or directory) lsof99813 steven cwdDIR 92,2340356138 72 15497 /home/steven/lsof-4.81.dfsg.1+wtf lsof99813 steven rtdDIR 0,71512 2 / lsof99813 steven txtREG 92,2340356138 145071 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof lsof99813 steven memREG 0,0 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof (path dev=92,-1954611158) lsof99813 steven memREG 0,0117963 /lib/i386-kfreebsd-gnu/ld-2.13.so (path dev=0,71) lsof99813 steven memREG 0,0213682 /etc/ld.so.cache (path dev=0,71) lsof99813 steven memREG 0,0117953 /lib/libkvm.so.0 (path dev=0,71) lsof99813 steven memREG 0,0117809 /lib/i386-kfreebsd-gnu/i686/cmov/libc-2.13.so (path dev=0,71) lsof99813 steven memREG 0,0117827 /lib/i386-kfreebsd-gnu/libbsd.so.0.3.0 (path dev=0,71) lsof99813 steven memREG 0,0108648 /usr/lib/locale/locale-archive (path dev=164,284950746) lsof99813 steven NOFD/proc/99813/fd (opendir: No such file or directory) Sadly though we're missing /proc/*/fd in linprocfs as you can see. :( No pipes, network or unix-style sockets can be listed either. So it's not very functional yet, but being able to build something is a start. To build this I had to change declarations in machine.h to turn off each bit of code
Bug#589103: lsof on Debian FreeBSD
Steven, Thanks for your quick response and efforts. Crucially when I poke around in /proc/self on asdfasdf.debian.net (or the Hurd exodar.debian.net for that matter) I can find no /proc/sef/fd directory. From what I understand that is crucial to a /proc-basd lsof. Please feel free to check in your experiments into the collab-maint repository but please could you do it on a "kfreebsd" branch. We could release it to the experiemntal distribution. On 20/04/12 03:23, Steven Chamberlain wrote: Hi! On 20/04/12 00:45, Nicholas Bamber wrote: 8.6Why can't Configure create lsof_owner.h for FreeBSD 6 and above? ... Lsof needs to access elements of that lockf_owner structure to determine if a lock belongs to the process that has a file open. The goal really is to keep userland tools out of kernel internals to produce better software; that's one of many good things I hope will come as a side effect out of the GNU/kFreeBSD effort. Since the 'freebsd' dialect of lsof has been relying on kernel internals for some time, I expect that code will be in pretty bad shape. You could try to get what you need from the kfreebsd source but I think it would be a bad idea. (A kernel with an incompatible definition might be booted at any time, and no dpkg dependency can help with that). However, if the 'linux' dialect does not depend on kernel source code I think that would make a better starting point. I tried just now with the freebsd/machine.h and Makefile, but replaced the symlinks to use dialect/linux code instead, except for node1/2 and zfs. That way I even managed to build something, which almost looks like it works: steven@kfreebsd-i386:~/lsof-4.81.dfsg.1+wtf$ ./lsof -c lsof COMMAND PID USER FD TYPEDEVICE SIZE NODE NAME lsof99812 steven cwdDIR 92,2340356138 72 15497 /home/steven/lsof-4.81.dfsg.1+wtf lsof99812 steven rtdDIR 0,71512 2 / lsof99812 steven txtREG 92,2340356138 145071 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof lsof99812 steven memREG 0,0 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof (path dev=92,-1954611158) lsof99812 steven memREG 0,0117963 /lib/i386-kfreebsd-gnu/ld-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0213682 /etc/ld.so.cache (path dev=0,71) lsof99812 steven memREG 0,0117953 /lib/libkvm.so.0 (path dev=0,71) lsof99812 steven memREG 0,0117809 /lib/i386-kfreebsd-gnu/i686/cmov/libc-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117827 /lib/i386-kfreebsd-gnu/libbsd.so.0.3.0 (path dev=0,71) lsof99812 steven memREG 0,0108648 /usr/lib/locale/locale-archive (path dev=164,284950746) lsof99812 steven memREG 0,0117898 /lib/i386-kfreebsd-gnu/i686/cmov/libnss_compat-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117829 /lib/i386-kfreebsd-gnu/i686/cmov/libnsl-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117834 /lib/i386-kfreebsd-gnu/i686/cmov/libnss_nis-2.13.so (path dev=0,71) lsof99812 steven memREG 0,0117838 /lib/i386-kfreebsd-gnu/i686/cmov/libnss_files-2.13.so (path dev=0,71) lsof99812 steven NOFD/proc/99812/fd (opendir: No such file or directory) lsof99813 steven cwdDIR 92,2340356138 72 15497 /home/steven/lsof-4.81.dfsg.1+wtf lsof99813 steven rtdDIR 0,71512 2 / lsof99813 steven txtREG 92,2340356138 145071 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof lsof99813 steven memREG 0,0 15837 /home/steven/lsof-4.81.dfsg.1+wtf/lsof (path dev=92,-1954611158) lsof99813 steven memREG 0,0117963 /lib/i386-kfreebsd-gnu/ld-2.13.so (path dev=0,71) lsof99813 steven memREG 0,0213682 /etc/ld.so.cache (path dev=0,71) lsof99813 steven memREG 0,0117953 /lib/libkvm.so.0 (path dev=0,71) lsof99813 steven memREG 0,0117809 /lib/i386-kfreebsd-gnu/i686/cmov/libc-2.13.so (path dev=0,71) lsof99813 steven memREG 0,0117827 /lib/i386-kfreebsd-gnu/libbsd.so.0.3.0 (path dev=0,71) lsof99813 steven memREG 0,0108648 /usr/lib/locale/locale-archive (path dev=164,284950746) lsof99813 steven NOFD/proc/99813/fd (opendir: No such file or directory) Sadly though we're missing /proc/*/fd in linprocfs as you can see. :( No pipes, network or unix-style sockets can be listed either. So it's not very functional yet, but being able to build something is a start. To build this I had to change declarations in machine.h to turn off each bit of code
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? On 20/04/12 00:51, Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90a94e.8000...@periapt.co.uk
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? On 20/04/12 00:51, Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90a94e.8000...@periapt.co.uk
Bug#625262: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? On 20/04/12 00:51, Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90a94e.8000...@periapt.co.uk
Bug#615125: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Also what happens when you force through the installation of w3c-dtd-xhtml version 1.2-2 and w3c-sgml-lib? Does wdg-html-validator behave itself for you then? On 20/04/12 00:51, Nicholas Bamber wrote: Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90a51f.4010...@periapt.co.uk
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90a51f.4010...@periapt.co.uk
lsof on Debian FreeBSD
tag 589103 +help thanks I have been looking at what it will take to build lsof on kfreebsd. Obviously the first step is passing '-n freebsd' to './Configure' as noted earlier on the bug report. You can see the current state of our work at Vcs-Git: git://git.debian.org/git/collab-maint/lsof.git Vcs-Browser: http://git.debian.org/?p=collab-maint/lsof.git However once that is done one hits the problem described in section 8.6 of the FAQ: > 8.6Why can't Configure create lsof_owner.h for FreeBSD 6 and above? > >Lsof may report: > >Creating ./lockf_owner.h from /usr/src/sys/kern/kern_lockf.c >FATAL ERROR: can't read /usr/src/sys/kern/kern_lockf.c >FATAL ERROR: ./lockf_owner.h creation failed (see 00FAQ) >or >Creating ./lockf_owner.h from /usr/src/sys/kern/kern_lockf.c >FATAL ERROR: ./lockf_owner.h creation failed (see 00FAQ) > >Those messages mean that lsof's Configure script failed to >create a local header file, ./lockf_owner.h, needed to use the >new kernel file locking code of some versions of FreeBSD 6 and >above. > >The changes that implement that new locking code alter the >lockf structure in and introduce a new structure, >lockf_entry, to that header file. When Configure detects the >presence of the lockf_entry definition in , it >tries to construct the local header file, ./lockf_owner.h. > >Configure has to do that because an unfortunate side effect of >the new kernel file locking code is that doesn't >contain the lockf_owner structure definition referenced in its >own lockf structure. Lsof needs to access elements of that >lockf_owner structure to determine if a lock belongs to the >process that has a file open. > >The missing lockf_owner structure definition is in the kernel >source file, typically /usr/src/sys/kern/kern_lockf.c. >Configure tries to extract the lockf_owner structure definition >from kern_lockf.c into lsof's local header file, ./lockf_owner.h. >If Configure can't do that, it reports: > >FATAL ERROR: ./lockf_owner.h creation failed > >If Configure can't even read kern_lockf.c, it first reports: > >FATAL ERROR: can't read /usr/src/sys/kern/kern_lockf.c > >The work-around for this problem is to update the FreeBSD >kernel /usr/src tree (e.g., do a CVSup or csup) on the system >where lsof is to be built and then do a "make buildworld" >followed by a "make installworld". > So the problem is to translate this into "Debian-speak". I think I see how to do this in principle but some of the details elude me. 1.) Declare a build dependency: kfreebsd-source[kfreebsd-any] 2.) Have a clause in the override_dh_auto_configure rule that checks for the kfreebsd OS and copies the compressed tarball to somewhere in the build space; uncompresses and untars it; and sets the FREEBSD_SYS environment variable accordingly. 3.) The kfreebsd-source copies will need to be cleaned up as part of the clean rule. The bit that I am most unclear about is how to tie up the Debian version for lsof, the kernerl version and how to pick the correct version of kfreebsd-source from the virtual package. I suppose one way to go is to make "lsof" a virtual package depending on "lsof-linux | lsof-kfreebsd | lsof-hurd". lsof-kfreebsd would itself be a virtual package depending on the real package "lsof-kfreebsd-OSVER". Can one evade the whole issue by forcing lsof on to use /proc? Maybe we should take that approach but discuss with upstream. -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90a3a4.4000...@periapt.co.uk
Bug#625262: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f90a51f.4010...@periapt.co.uk
Bug#615125: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Hmm well the old vesion of w3c-dtd-xhtml provided w3c-dtd-xhtml. This one does not. Still I see it showing up as a Provides in PTS. I am not sure if something needs to be done in some mysterious Debian server to resolve that but the 1.2-2 version of w3c-sgml-lib does NOT have a Provides clause. Please could you send me one or more HTML files that you would accept as an objective test as whether wdg-html-validator is working and what you expect as an output. Also please feel free to do something in the bugs world to stop this version going into testing whilst I investigate. On 20/04/12 00:35, Joey Hess wrote: Nicholas Bamber wrote: Please send me instructions for how it working fine and not afterwards because I tried to test it. w3c-sgml-lib provides/conflicts w3c-dtd-xhtml, and w3c-markup-validator depends on both packages, so this happens: joey@wren:~>validate index.html joey@wren:~>sudo apt-get install w3c-dtd-xhtml Reading package lists... Done Building dependency tree Reading state information... Done w3c-dtd-xhtml is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 332 not upgraded. joey@wren:~>sudo apt-get install w3c-sgml-lib Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: w3c-dtd-xhtml The following NEW packages will be installed: w3c-sgml-lib 0 upgraded, 1 newly installed, 1 to remove and 332 not upgraded. Need to get 616 kB of archives. After this operation, 3,834 kB of additional disk space will be used. Do you want to continue [Y/n]? y Get:1 http://mirror.bytemark.co.uk/debian/ unstable/main w3c-sgml-lib all 1.2-1 [616 kB] Fetched 616 kB in 0s (7,302 kB/s) dpkg: w3c-dtd-xhtml: dependency problems, but removing anyway as you requested: wdg-html-validator depends on w3c-dtd-xhtml. (Reading database ... 154372 files and directories currently installed.) Removing w3c-dtd-xhtml ... Selecting previously unselected package w3c-sgml-lib. (Reading database ... 154310 files and directories currently installed.) Unpacking w3c-sgml-lib (from .../w3c-sgml-lib_1.2-1_all.deb) ... Setting up w3c-sgml-lib (1.2-1) ... [master c4e89ec] committing changes in /etc after apt run Author: joey 10 files changed, 804 insertions(+), 84 deletions(-) create mode 100644 sgml/w3c-sgml-lib.cat delete mode 100644 xml/w3c-dtd-xhtml.xml rewrite xml/w3c-dtd-xhtml.xml.old (82%) create mode 100644 xml/w3c-sgml-lib.xml joey@wren:~>validate index.html *** Errors validating index.html: *** Error at line 2, character 53: cannot find "REC-xhtml1-20020801/xhtml1-strict.dtd"; tried "/usr/share/xml/xhtml/schema/dtd/1.0/REC-xhtml1-20020801/xhtml1-str ict.dtd", "/usr/local/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd", "/usr/share/sgml/REC-xhtml1-20020801/xhtml1-strict.dtd" Error at line 2, character 53: DTD did not contain element declaration for document type name Error at line 3, character 13: there is no attribute "XMLNS" Error at line 3, character 43: element "HTML" undefined Error at line 4, character 6: element "HEAD" undefined Error at line 5, character 7: element "TITLE" undefined Error at line 7, character 6: element "BODY" undefined Error at line 8, character 3: element "P" undefined Error at line 8, character 24: element "STRONG" undefined zsh: exit 9 validate index.html joey@wren:~>cat index.html http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml";> ikiwiki Ikiwiki is awiki compiler. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589103: lsof on Debian FreeBSD
tag 589103 +help thanks I have been looking at what it will take to build lsof on kfreebsd. Obviously the first step is passing '-n freebsd' to './Configure' as noted earlier on the bug report. You can see the current state of our work at Vcs-Git: git://git.debian.org/git/collab-maint/lsof.git Vcs-Browser: http://git.debian.org/?p=collab-maint/lsof.git However once that is done one hits the problem described in section 8.6 of the FAQ: > 8.6Why can't Configure create lsof_owner.h for FreeBSD 6 and above? > >Lsof may report: > >Creating ./lockf_owner.h from /usr/src/sys/kern/kern_lockf.c >FATAL ERROR: can't read /usr/src/sys/kern/kern_lockf.c >FATAL ERROR: ./lockf_owner.h creation failed (see 00FAQ) >or >Creating ./lockf_owner.h from /usr/src/sys/kern/kern_lockf.c >FATAL ERROR: ./lockf_owner.h creation failed (see 00FAQ) > >Those messages mean that lsof's Configure script failed to >create a local header file, ./lockf_owner.h, needed to use the >new kernel file locking code of some versions of FreeBSD 6 and >above. > >The changes that implement that new locking code alter the >lockf structure in and introduce a new structure, >lockf_entry, to that header file. When Configure detects the >presence of the lockf_entry definition in , it >tries to construct the local header file, ./lockf_owner.h. > >Configure has to do that because an unfortunate side effect of >the new kernel file locking code is that doesn't >contain the lockf_owner structure definition referenced in its >own lockf structure. Lsof needs to access elements of that >lockf_owner structure to determine if a lock belongs to the >process that has a file open. > >The missing lockf_owner structure definition is in the kernel >source file, typically /usr/src/sys/kern/kern_lockf.c. >Configure tries to extract the lockf_owner structure definition >from kern_lockf.c into lsof's local header file, ./lockf_owner.h. >If Configure can't do that, it reports: > >FATAL ERROR: ./lockf_owner.h creation failed > >If Configure can't even read kern_lockf.c, it first reports: > >FATAL ERROR: can't read /usr/src/sys/kern/kern_lockf.c > >The work-around for this problem is to update the FreeBSD >kernel /usr/src tree (e.g., do a CVSup or csup) on the system >where lsof is to be built and then do a "make buildworld" >followed by a "make installworld". > So the problem is to translate this into "Debian-speak". I think I see how to do this in principle but some of the details elude me. 1.) Declare a build dependency: kfreebsd-source[kfreebsd-any] 2.) Have a clause in the override_dh_auto_configure rule that checks for the kfreebsd OS and copies the compressed tarball to somewhere in the build space; uncompresses and untars it; and sets the FREEBSD_SYS environment variable accordingly. 3.) The kfreebsd-source copies will need to be cleaned up as part of the clean rule. The bit that I am most unclear about is how to tie up the Debian version for lsof, the kernerl version and how to pick the correct version of kfreebsd-source from the virtual package. I suppose one way to go is to make "lsof" a virtual package depending on "lsof-linux | lsof-kfreebsd | lsof-hurd". lsof-kfreebsd would itself be a virtual package depending on the real package "lsof-kfreebsd-OSVER". Can one evade the whole issue by forcing lsof on to use /proc? Maybe we should take that approach but discuss with upstream. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Please send me instructions for how it working fine and not afterwards because I tried to test it. On 19/04/12 22:46, Joey Hess wrote: Nicholas Bamber wrote: I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. It was working 100% fine before your change, and now it fails miserably. #669480 -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f909739.1070...@periapt.co.uk
Re: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Please send me instructions for how it working fine and not afterwards because I tried to test it. On 19/04/12 22:46, Joey Hess wrote: Nicholas Bamber wrote: I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. It was working 100% fine before your change, and now it fails miserably. #669480 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f909739.1070...@periapt.co.uk
Bug#615125: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Please send me instructions for how it working fine and not afterwards because I tried to test it. On 19/04/12 22:46, Joey Hess wrote: Nicholas Bamber wrote: I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. It was working 100% fine before your change, and now it fails miserably. #669480 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#625262: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
Joey, Please send me instructions for how it working fine and not afterwards because I tried to test it. On 19/04/12 22:46, Joey Hess wrote: Nicholas Bamber wrote: I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. It was working 100% fine before your change, and now it fails miserably. #669480 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f909739.1070...@periapt.co.uk
Bug#589103: hmm
These issues are exactly described in 8.6 of the FAQ. However the answer really rather applies to pure FreeBSD rather than Debian FreeBSD. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#302845: not a bug
tag 302845 +wontfix tag 297029 -moreinfo severity 297029 minor severity 441175 minor thanks The FAQ has a lot of discussion on these sort of issues. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#297029: not a bug
tag 297029 +wontfix thanks You should read the FAQ document. It has quite a lot of discussion of these sort of issues. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#441175: lsof / on sparc
tag 441175 +unreproducible thanks I cannot reproduce this. Output on a sparc machine atatched. periapt@smetana:~$ lsof / COMMAND PIDUSER FD TYPE DEVICE SIZE/OFFNODE NAME bash20006 periapt cwdDIR9,1 4096 572374 /home/periapt bash20006 periapt rtdDIR9,1 4096 2 / bash20006 periapt txtREG9,1848436 2976230 /bin/bash bash20006 periapt memREG9,1 26048 1150645 /usr/lib/gconv/gconv-modules.cache bash20006 periapt memREG9,1127837 3368772 /lib/libpthread-2.11.3.so bash20006 periapt memREG9,1 1244632 1474897 /usr/lib/libdb-4.6.so bash20006 periapt memREG9,1 20104 1476649 /usr/lib/libnss_db-2.2.3.so bash20006 periapt memREG9,1 51584 3368768 /lib/libnss_files-2.11.3.so bash20006 periapt memREG9,1 43368 3368769 /lib/libnss_nis-2.11.3.so bash20006 periapt memREG9,1 85768 3368781 /lib/libnsl-2.11.3.so bash20006 periapt memREG9,1 35192 3368775 /lib/libnss_compat-2.11.3.so bash20006 periapt memREG9,1 108801808 1494579 /usr/lib/locale/locale-archive bash20006 periapt memREG9,1 1501772 2829283 /lib/libc-2.11.3.so bash20006 periapt memREG9,1 18264 3368786 /lib/libdl-2.11.3.so bash20006 periapt memREG9,1252240 2829027 /lib/libncurses.so.5.7 bash20006 periapt memREG9,1152960 3368780 /lib/ld-2.11.3.so lsof20030 periapt cwdDIR9,1 4096 572374 /home/periapt lsof20030 periapt rtdDIR9,1 4096 2 / lsof20030 periapt txtREG9,1136136 1473413 /usr/bin/lsof lsof20030 periapt memREG9,1 108801808 1494579 /usr/lib/locale/locale-archive lsof20030 periapt memREG9,1 1501772 2829283 /lib/libc-2.11.3.so lsof20030 periapt memREG9,1152960 3368780 /lib/ld-2.11.3.so lsof20031 periapt cwdDIR9,1 4096 572374 /home/periapt lsof20031 periapt rtdDIR9,1 4096 2 / lsof20031 periapt txtREG9,1136136 1473413 /usr/bin/lsof lsof20031 periapt memREG9,1 108801808 1494579 /usr/lib/locale/locale-archive lsof20031 periapt memREG9,1 1501772 2829283 /lib/libc-2.11.3.so lsof20031 periapt memREG9,1152960 3368780 /lib/ld-2.11.3.so periapt@smetana:~$
Bug#597861: [debian-mysql] copyright file
tag 597861 +confirmed retitle 597861 need automated update for copyright thanks I personally would add 4.) Check that the debian/copyright is all good, DEP-5 and lintian clean. Note that I did an *exhaustive* rebuilding of the entire debian/copyright file when I first packaged 5.5. I have a patch for licensecheck2dep5 to make it build a copyright file more like the one that is there. I hope to get those into Debian at some point so we can use them to build dep5 (or whatever its called now) copyright files automatically. Yes I noticed it was in reasonable order. I do have some issues however. 1.) I mean to check #597861. 2.) lintian reports some issues with copyright 3.) we are on an old version of DEP-5. Upgrade is required as part of Debian Perl policy 3.9.3. 4.) I feel the need to check whether the public domain bits are expressed correctly. Until then, I hope to add some checking in debian/rules that will help us identify when licensecheck thinks there are any changes that we might need to make to debian/copyright. Seems like this would be a useful thing for all packages to have actually. Yes this would be very good. I have checked in some cleanups for the copyright. I believe these are quite likely to be one off's and that at least in principle Clint's automated rebuild of copyright would fix them. Given the possibility of automating management of this file, I did not see any reason to touch the substance of #597861. Instead I am broadening the scope. I am sure it does not need my pointing out that the copyright file needs to be a static file and its regeneration appears to depend on the internet to obtain the FLOSS exception. So putting it in debian/rules simply implies that is a convenient place rather than it should be pat of the build. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665012: CVE-2012-1570 not yet fixed in stable
On 15/04/12 16:18, Arne Wichmann wrote: Found: 665012 1.4.03-1.1 As far as I can see this is not yet fixed in stable. cu AW Arne, All the security issues are present in the stable release. I never got a reply from the security team to my last proposed upload though the security profile was slightly different then. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#665012: CVE-2012-1570 not yet fixed in stable
On 15/04/12 16:18, Arne Wichmann wrote: Found: 665012 1.4.03-1.1 As far as I can see this is not yet fixed in stable. cu AW Arne, All the security issues are present in the stable release. I never got a reply from the security team to my last proposed upload though the security profile was slightly different then. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Accepted librose-db-object-perl 1:0.798-1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Apr 2012 18:50:22 +0100 Source: librose-db-object-perl Binary: librose-db-object-perl Architecture: source all Version: 1:0.798-1 Distribution: unstable Urgency: low Maintainer: Debian Perl Group Changed-By: Nicholas Bamber Description: librose-db-object-perl - framework providing an extensible high-performance ORM Changes: librose-db-object-perl (1:0.798-1) unstable; urgency=low . * New upstream release * Raised standards version to 3.9.3 * Updated copyright Checksums-Sha1: 1e0f11da0cc79c2de34836f35e6cae95d777ca7f 2559 librose-db-object-perl_0.798-1.dsc 208a59b1de240c93a73f1ab9ffc94dbc9bae0bf4 554899 librose-db-object-perl_0.798.orig.tar.gz 5c70251da0f1281063562c62854df2bb92d995fb 3547 librose-db-object-perl_0.798-1.debian.tar.gz e9066c500a05dae119ffa052ff5594ea1be10545 641412 librose-db-object-perl_0.798-1_all.deb Checksums-Sha256: 4552825e2543c3be3116f06be54737710948cd33a5892ca260370acbcba3305f 2559 librose-db-object-perl_0.798-1.dsc 84e8e913546002db519f4723d61cd4bac9e3f4ac3dbb33a2254cac1b5f9d4d08 554899 librose-db-object-perl_0.798.orig.tar.gz 3578e7bc18cf9e74daf7ce8ac8c84ec75325e81a7ffa774a54df86626b950889 3547 librose-db-object-perl_0.798-1.debian.tar.gz 1f08fa627d404fbe94b9228294cffc48cde03e56e36bf2871fbddc79562afdd0 641412 librose-db-object-perl_0.798-1_all.deb Files: 30bfffd8c84b3e86a4d1ea7506a1b3fe 2559 perl optional librose-db-object-perl_0.798-1.dsc 4970d548822d883fa8e8ad5325ca93db 554899 perl optional librose-db-object-perl_0.798.orig.tar.gz a7d2dc55856f6b42ccc1bb15c356070d 3547 perl optional librose-db-object-perl_0.798-1.debian.tar.gz 91d23b47ca4b2d6efc7a2626e9f1f180 641412 perl optional librose-db-object-perl_0.798-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPiyFAAAoJELbE2bY7/+c8n3kP/3xilulk98ycF5DByANcO4bt oPnXSOcLKyPi5AHJJ4RJGJt/xIuN+VLcuZ0g0AntTgThFVhm/Dlxy0UXrOG1gFJ8 SDsJc5KKzP+VufPvHInAph5Hw7LUWTOvDSXqETa3bbWmQmPSGXIAy+c/CRbIcAEo 71Xk4swLCXo/OK6jTfCd4Rjz8zIhYXv1Dy8ApQgkXNgTjHRy/pskFf1o1FCUsOKN uFfdgO4wRJQ/Rtlr/d7u3ZD/hxCns8zD3/Q+ZmPLqpYaepydYw1rG/9BCxu6t7A5 PsmUsKCQbbTKXy8leyF8RQfibRGqOFmUPDHF+aWbJpjnfJKDE1LQoKNLAimmD/wY T8eYu5t/MKzPrMYgx6kLE9Q94v75sugfq30LpYzvIn6dPI6NznYQLvHstZGXmCYb 7AA4cyn4YKQDvysu/TTEvPYRE8DLuHI7acUYpldeYH4UsuZHkVKleaAxiUNwCnP8 xeIyFmobB5VUltipANLRpG7IKMohaSnxBYHwTGZGgh/4RN1WagnFxn7CahW5kYdV VZ8dgTCHuu/nd83LAz20qWmBC5b75CuRTXcyhPq+skXeen15A6MC3BLPzo0Mw/5r B0tBq5ocQQI/MGgIBicpRIp0aulKAY1Rb4tKyvGZIYAgH594pWTC8IDuqkxNVcTR 0FgApFDxfXnukvYpmD66 =0pIm -END PGP SIGNATURE- Accepted: librose-db-object-perl_0.798-1.debian.tar.gz to main/libr/librose-db-object-perl/librose-db-object-perl_0.798-1.debian.tar.gz librose-db-object-perl_0.798-1.dsc to main/libr/librose-db-object-perl/librose-db-object-perl_0.798-1.dsc librose-db-object-perl_0.798-1_all.deb to main/libr/librose-db-object-perl/librose-db-object-perl_0.798-1_all.deb librose-db-object-perl_0.798.orig.tar.gz to main/libr/librose-db-object-perl/librose-db-object-perl_0.798.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/e1sjvbw-0005hj...@franck.debian.org
Accepted maradns 2.0.06-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Apr 2012 13:08:35 +0100 Source: maradns Binary: maradns maradns-zoneserver maradns-deadwood duende maradns-docs Architecture: source i386 all Version: 2.0.06-2 Distribution: experimental Urgency: low Maintainer: Nicholas Bamber Changed-By: Nicholas Bamber Description: duende - logging daemonizer maradns- simple security-focused authoritative Domain Name Service server maradns-deadwood - simple security-focused recursive Domain Name Service server maradns-docs - upstream documentation for the MaraDNS Domain Name Service server maradns-zoneserver - complementary server process to TCP functions for MaraDNS Closes: 668329 Changes: maradns (2.0.06-2) experimental; urgency=low . * Fix typo in init scripts (Closes: #668329) Checksums-Sha1: de9f525c4f3555a8f2a9fe3d2ed2732f567ba119 2002 maradns_2.0.06-2.dsc 29e74f2e5dd6e141fad9345ba4933149e4ed5382 42121 maradns_2.0.06-2.debian.tar.gz 15161b5d6f7e8c37352230c50e34e3ec2fc0debd 388528 maradns_2.0.06-2_i386.deb 5fa8e955ecd46127d2fe6d12e91670a07a04aac9 178178 maradns-zoneserver_2.0.06-2_i386.deb 0688a6e5529e92834fee5a40a0311162b7b6bcd5 124740 maradns-deadwood_2.0.06-2_i386.deb 02600fe0255c8e43b81e60da96a82cdefa94fd43 70998 duende_2.0.06-2_i386.deb d77164bbc034a9159005dab6013c21395b4fbe32 200352 maradns-docs_2.0.06-2_all.deb Checksums-Sha256: c568fd17d32618087c472387eac7ecda7c7929d5c789d77f862907b17952ec32 2002 maradns_2.0.06-2.dsc a50d1f60c57ab3230f8d74440800b85d09b466da21451d4574d89082564c13d3 42121 maradns_2.0.06-2.debian.tar.gz ef0a42f3972f845c22034c005a3fefa82d47bf43c2cb77eba5c5d8a79b6d0457 388528 maradns_2.0.06-2_i386.deb a9bedff8bfd5b9dce0eea40c1a218ab27eda81bb11a3d7b7e85ac279be5f375c 178178 maradns-zoneserver_2.0.06-2_i386.deb b48dbc95fbe19a77bf9d4030582e194f88e61e1ebde57f9470fbe06b6cf13956 124740 maradns-deadwood_2.0.06-2_i386.deb 6eb81172700287ef7c490d185d9ef5bc1485afc75b2026418c4f3446de185501 70998 duende_2.0.06-2_i386.deb bcb58e59c7a37fdc46158907e019d7534c89655b4c6b040cc451b69fee31bd1a 200352 maradns-docs_2.0.06-2_all.deb Files: 39ee996ec0bccefa1c9f51e8ef347e58 2002 net extra maradns_2.0.06-2.dsc 710837c1b43edace667a1570d4240390 42121 net extra maradns_2.0.06-2.debian.tar.gz ba39def69fc082888507fa0ccfbc1ab7 388528 net extra maradns_2.0.06-2_i386.deb 63f2eaeb813671c1119a15668e40dd5e 178178 net extra maradns-zoneserver_2.0.06-2_i386.deb be682d8797b971da6d9a4a6f346df0bc 124740 net extra maradns-deadwood_2.0.06-2_i386.deb 3b35ea8b477c823e8205e2d5f23137da 70998 admin optional duende_2.0.06-2_i386.deb beb3de6563a1e180af086cb7d7648230 200352 doc extra maradns-docs_2.0.06-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPirtKAAoJELbE2bY7/+c8XdgP/jGktst5kkbRscmVGKvIRMf3 7GElKLOfIMGof965ZBEeadyazgIkVqCzWTrm2yHlJshd4y6/c37Nz9Gcxd0uowVN 6obae1wT3PYvBe0m/wmufmISdNTpd1vMz/kkYcf3KeweOkid/7YAhWq2utzoEY/4 QqiYpe5Yse3ROpoUdJx66kFKCCzL4ecCujNP8e5YS44E/BS+d9sqZsXoh+V9P0XE Hzm3fgokXkgpx68ZD0hZKQvOEsQYvw7o8c0DXK30xBF0IUdWWL67Q+upx1ur4oNj fqTDjQQlFqnVI/1rbHhfxlT6ca7gyX3JIo4w4Dv5pfGrlYzQvuCRiJp0KJ1uhokR LMky/rx9w2edHZ9L59HNn+Bm5acvuEzd3B49hl5psesubbmesAJxWs2Fe5MbftiF fY1AF7cJt4L4kifNYwoJLcvsFvze86p4gTSfjV6o3NctZTsjO0vKGEApN0dd4GlF rprN1oFe3QokHYLWJDOFgnW4N3sorqIO1v6m7AOX5A2z3rch4OuVw+LwjA4Ta3iR Gy3t8Ygfj2vpqUwvLbtzrgm5Sn7dQvTZDXcJl1RzoQ2nRhAYaQ9CiKjSA9mVgDBp 0aMPq9srqhU52y+Cpgnuicwbl4Nc/Zt7IP0SGCkl6XorhIA3U/CYjOVh5wDkGzAo egYn8r7NyzfhVFVSKfUb =hwLo -END PGP SIGNATURE- Accepted: duende_2.0.06-2_i386.deb to main/m/maradns/duende_2.0.06-2_i386.deb maradns-deadwood_2.0.06-2_i386.deb to main/m/maradns/maradns-deadwood_2.0.06-2_i386.deb maradns-docs_2.0.06-2_all.deb to main/m/maradns/maradns-docs_2.0.06-2_all.deb maradns-zoneserver_2.0.06-2_i386.deb to main/m/maradns/maradns-zoneserver_2.0.06-2_i386.deb maradns_2.0.06-2.debian.tar.gz to main/m/maradns/maradns_2.0.06-2.debian.tar.gz maradns_2.0.06-2.dsc to main/m/maradns/maradns_2.0.06-2.dsc maradns_2.0.06-2_i386.deb to main/m/maradns/maradns_2.0.06-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/e1sjoeu-0007bw...@franck.debian.org
Accepted maradns 1.4.12-2 (source i386 all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 15 Apr 2012 11:42:27 +0100 Source: maradns Binary: maradns maradns-zoneserver duende maradns-docs Architecture: source i386 all Version: 1.4.12-2 Distribution: unstable Urgency: low Maintainer: Nicholas Bamber Changed-By: Nicholas Bamber Description: duende - logging daemonizer maradns- simple security-focused Domain Name Service server maradns-docs - upstream documentation for the MaraDNS Domain Name Service server maradns-zoneserver - complementary server process to TCP functions for MaraDNS Closes: 668329 Changes: maradns (1.4.12-2) unstable; urgency=low . * Fix typo in init scripts (Closes: #668329) Checksums-Sha1: 763e17fe0c47ce8d0741758f753f6ad17256e6a2 1969 maradns_1.4.12-2.dsc fe60f9afa1d8172f9ca3756d9462bab94806645f 39831 maradns_1.4.12-2.debian.tar.gz bdd5bd8fc3ccda112a742f8ec3946936768f3d1e 413878 maradns_1.4.12-2_i386.deb 113af6c756f9108fbe7181c02f66df4fc56e4ded 176790 maradns-zoneserver_1.4.12-2_i386.deb b40628de62aa862c8088f4e7f9c55190849c7e69 69666 duende_1.4.12-2_i386.deb 1d2887eacb80a229a81179ec08ffcfaa4bc626dc 188090 maradns-docs_1.4.12-2_all.deb Checksums-Sha256: 4aea5631373b14886567227db4e220e45038eb7daf29404bec2c8b1eacff2d3d 1969 maradns_1.4.12-2.dsc ac160de58c295be40f3bcff9eb8f6aa3df15d0d8e826f9c63e9c59c7cf3e41ea 39831 maradns_1.4.12-2.debian.tar.gz fa766ca800982115d5a64e389b3e5d69ce12e7566f5f359d51d223430ff7f8aa 413878 maradns_1.4.12-2_i386.deb d2c7d05747eb1e4ca4af1cb2ef8fd0bcdd1c176e2302e4b69ee11b875abdce23 176790 maradns-zoneserver_1.4.12-2_i386.deb 3fdee2ec5dd92e112e65e2df714882c67f3162155ead0d266060e0fe350704d5 69666 duende_1.4.12-2_i386.deb 9d91c9fa1175ee67a34e4f3f8e5ce4200d619256a8582148bb7645715c94f403 188090 maradns-docs_1.4.12-2_all.deb Files: 5130b660fcd2a6f962443edeb2c808df 1969 net extra maradns_1.4.12-2.dsc 96c197d7231e939d75f6577d0c9e1dda 39831 net extra maradns_1.4.12-2.debian.tar.gz fc5cf0da33e914c02a6e63a0f0f424a0 413878 net extra maradns_1.4.12-2_i386.deb afdc9031452accdacacf4bfb4b53b7ad 176790 net extra maradns-zoneserver_1.4.12-2_i386.deb 7d31e3d99f357bed905ac0f0fc36fa9e 69666 admin optional duende_1.4.12-2_i386.deb 098edbc99c66a31108a9867e0281620f 188090 doc extra maradns-docs_1.4.12-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPirzlAAoJELbE2bY7/+c8OVkP/0bfaDT+Edx0WqPHLXBm5ii5 Ecdh/s0nMOPbYyWv1vvZiXRuYck0xI/tsKQ5KZmyqAL9JF4loBc0o94iujW8D6c/ nGClc+CLRtFB6lTnsX4JkL8wHErUOLTWQw/w4zBwrXSRb6zynIpJq+nD5f8YYNUf /sDTEuJzHJnlR3Ji4FVdCNcPv9s6x7aCuIpNn9z22qjsZpjWF/VxzuzvnZQfWozI DyDy836huOoXCAeCSqrsSxwsi4j7xNLxmvQbwJexTPbd5qIvIVdI3zEkXQNBlRKW +Y5AC8U8TXvpwgugLHNyt8Q24qblVGBgS/7MvG1ea+P9SMnQV7Ml5wuHgZX3FHrg yLYWL/um+BfF5zmDPtoW3TEoTCmtcBdcqzZs7yEWTRdTlMH6x6PNTRERPiMTYNnr /OZEI61Rp1Y9vEfgVeQpnGBAwt7KqGrahPvCMoR91KOsQ2Sp657R9vSKPxUnJNAe uCfC2V3+txYeMriSIMyqhaS+DseDhPm4opDDnn/J3Fhz4qioVfIio7dysvVZeOss DM7bsanjqJTBwtVeEjGEZkgoiHsCZqfzpx8AMrZnpqtUAw8717yzcKnZuzteecmC BxvGGB+1ddfPVkjSm4Q3+bfidGQpdIGd6xEpyZMgTiZKycpQc4yXV5PKKhRzSePG LlyremmTzXu5Sp/xLsm4 =NFjG -END PGP SIGNATURE- Accepted: duende_1.4.12-2_i386.deb to main/m/maradns/duende_1.4.12-2_i386.deb maradns-docs_1.4.12-2_all.deb to main/m/maradns/maradns-docs_1.4.12-2_all.deb maradns-zoneserver_1.4.12-2_i386.deb to main/m/maradns/maradns-zoneserver_1.4.12-2_i386.deb maradns_1.4.12-2.debian.tar.gz to main/m/maradns/maradns_1.4.12-2.debian.tar.gz maradns_1.4.12-2.dsc to main/m/maradns/maradns_1.4.12-2.dsc maradns_1.4.12-2_i386.deb to main/m/maradns/maradns_1.4.12-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/e1sjoeg-0007py...@franck.debian.org
Accepted w3c-sgml-lib 1.2-2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 14 Apr 2012 13:13:38 +0100 Source: w3c-sgml-lib Binary: w3c-sgml-lib w3c-dtd-xhtml Architecture: source all Version: 1.2-2 Distribution: unstable Urgency: low Maintainer: Nicholas Bamber Changed-By: Nicholas Bamber Description: w3c-dtd-xhtml - W3C eXtensible HyperText Markup Language (XHTML) DTD [deprecated] w3c-sgml-lib - w3.org DTD and catalog files Closes: 555118 615125 615360 662091 Changes: w3c-sgml-lib (1.2-2) unstable; urgency=low . * Moved to personal maintainership * Adopting proposals from Samuel Bronson for resolving conflicts with w3c-dtd-xhtml (Closes: #662091) - Removing broken links - Removed legacy support - Removed Provides clause for w3c-dtd-xhtml (Closes: #615125) - Moved directory to w3c-sgml-lib from xhtml - Added Breaks clauses for old w3c-markup-validator * Raised standards version to 3.9.3 - Updated debian/copyright * Raised compat level and debhelper version to 8 * Added debian/generate_catalog_stuff.pl to build rules to regnerate debian/xmlcatalogs * Merged in w3c-dtd-xhtml (Closes: #555118) - Home page field added (Closes: #615360) Checksums-Sha1: abc33ea194e1c0fb26e495a126a264f5252f4d64 1971 w3c-sgml-lib_1.2-2.dsc 3dbe74da2ffab676b337bfc3e87c49ee0ebf47d4 93238 w3c-sgml-lib_1.2-2.debian.tar.gz dc114b3f94646e0e047b4b9ef178f22f65639296 568166 w3c-sgml-lib_1.2-2_all.deb 7bee5334aa1a76faae84284ac8f097e626b94adf 9012 w3c-dtd-xhtml_1.2-2_all.deb Checksums-Sha256: 527f7853f631f8a00c86f56b9293f969f205cbf2aab37ab6edcc1fe30dd62209 1971 w3c-sgml-lib_1.2-2.dsc d972b02fe1dd145b8749af7720f8e3b0cb4b0f6d07d0b86e2fb21191a4f1dfca 93238 w3c-sgml-lib_1.2-2.debian.tar.gz cc7939aa8232c8c7ef658ab9c90d7fd3f96a0e0a5ba07af6ef1e43d326c11191 568166 w3c-sgml-lib_1.2-2_all.deb 94cb27ad4631db3caf38436fb13bd488a53cadf969d17ce290c76321b543ab36 9012 w3c-dtd-xhtml_1.2-2_all.deb Files: b833b6136e4533abf741330cdb5d7137 1971 text optional w3c-sgml-lib_1.2-2.dsc 36284912c87e38fdf2a43d0f528da145 93238 text optional w3c-sgml-lib_1.2-2.debian.tar.gz 86a071c0fbe78a16b10bf02c831ea8a0 568166 text optional w3c-sgml-lib_1.2-2_all.deb df381bd8627e2c669ab21fac6fcc022d 9012 text optional w3c-dtd-xhtml_1.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPiWpbAAoJELbE2bY7/+c81FgP/jpFq4jzKkcnzjsIFWjzN3UT IavRZmNqKRtAeg6VUF185OyVeRf0kBXh6KEUV1N1uCjwgnU+K26et6lwkxaRxy2T lKLR1QmjfnYNaaukYtYWOu8W+Eu3qZcUKBv4rp4Qp0R14dmLa3E1SQV+55rDOHdl FWM8Z5foJ+pIWkkZsqcWkbwfAyWkVoIU8AYrf8TjlKYrpmxpPkL9wNep4jubKeo7 uKQta7rPxSgtViXKece/qEH6SoR2A3KUo2GcoyXNUl8yPsHKEVeMjBq9RkET7hH1 54fL1YvU8NOUcNajJvT8KFzVtyqPColw9GD5flC6r5/703ID000Db3vnRe+Z+RL+ VvC8A+wIxwk3ZJ7aM/D/a5iMznGG6rf2FLDWpec8JV9jWR7+5IBGcjc1H/yTJDYX cda1D3sCa2I3jjFm9dUR76zooDok++j2icLMuyh1HGyxrCJqu/50a/ElO9O+zBWp umlrk+dW21OLOs2ZQVLX8mqdQQMOad0mfPUIkeuPe/y8nchBv1k4zZygLWOoikc/ BRT3+wo79TuYFX5ht6CiLPut/85s9wxngTrf8qo+Y5kyRofwFcNIc4lLTfMJUnds IQyNttWj42WMNW2UB5xAgC8tc5z0aa483H7HDh2NGi+/6tZ/XdMqhFINMfeNty8d 1LJBRLOE1cBv3H0+/27w =GnGY -END PGP SIGNATURE- Accepted: w3c-dtd-xhtml_1.2-2_all.deb to main/w/w3c-sgml-lib/w3c-dtd-xhtml_1.2-2_all.deb w3c-sgml-lib_1.2-2.debian.tar.gz to main/w/w3c-sgml-lib/w3c-sgml-lib_1.2-2.debian.tar.gz w3c-sgml-lib_1.2-2.dsc to main/w/w3c-sgml-lib/w3c-sgml-lib_1.2-2.dsc w3c-sgml-lib_1.2-2_all.deb to main/w/w3c-sgml-lib/w3c-sgml-lib_1.2-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/e1sj4iw-0005cx...@franck.debian.org
Accepted w3c-markup-validator 1.2+dfsg-6 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 14 Apr 2012 13:17:45 +0100 Source: w3c-markup-validator Binary: w3c-markup-validator Architecture: source all Version: 1.2+dfsg-6 Distribution: unstable Urgency: low Maintainer: Nicholas Bamber Changed-By: Nicholas Bamber Description: w3c-markup-validator - W3C Markup Validator Changes: w3c-markup-validator (1.2+dfsg-6) unstable; urgency=low . * Changed to new location of w3c-sgml-lib files Checksums-Sha1: 00c4d318ca95cb03863f0ab223037a88a399 2072 w3c-markup-validator_1.2+dfsg-6.dsc 9e146b3c2e83cad63e24ef9fcaeffbb7766f4892 24688 w3c-markup-validator_1.2+dfsg-6.debian.tar.gz 29f176442a345b9cbe123f398c63fe4d23c25bf0 2475718 w3c-markup-validator_1.2+dfsg-6_all.deb Checksums-Sha256: bf9a46884b82da97c72ae9631f4a24e9773aab529916272ea3c49b53c947d833 2072 w3c-markup-validator_1.2+dfsg-6.dsc c6973df428039c14a83b910aef17fdf7686bb1a48aaf4146ead16bb86fde8080 24688 w3c-markup-validator_1.2+dfsg-6.debian.tar.gz 20d6e648203985bbce6d80e228499fe47e6bd39338429310556e6cd052d46edc 2475718 w3c-markup-validator_1.2+dfsg-6_all.deb Files: 9f6052bfb60d894724baf1192ea852f6 2072 web optional w3c-markup-validator_1.2+dfsg-6.dsc ebc87b4f97f8e2985258733738fae3f1 24688 web optional w3c-markup-validator_1.2+dfsg-6.debian.tar.gz d0ae9a97deb34bec1f045e2c5bbedf85 2475718 web optional w3c-markup-validator_1.2+dfsg-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJPiYGbAAoJELbE2bY7/+c8O0UP/2cwbpQmp0wNeq4I6F2OoWfC bDaqXM8zwLPTFGx8HnSI92j4OrR9O/xR6JXw44PI6hbwsxrx9AY3MhhAMsEVgKK/ maum2ItCGx8STVQNiNNQRf4uw/3Hrohljby/+cPhIzRfcpQCT9GYLcNM50aujPI0 /jm6wBBKwHe8a6Vg+ZdUBvNEnmbSRLFlYyF/Xv9UnwzPcmD+BzlktvV1jnEQdK7p Dpb+JckBt34EL9SI39Qcaoe9jljghYKE+JlBbhtgwsCVP2UaT7wGbUb1DUwddZHu TMH+hzyKWz2neKa2OWCWXkJzLuy3lV4Z2OWeFeONxvesmtwykr0xGyjc9I78cHej iOH5F8NKTSW39KoMvRaL+4z8dx2AAuJQhm77abIR2aNBc69hpS/TslqCMqDCXahd cqlWUMxlx3vMLJI0topWr/yj+qzTwPR4xdcj0YEgzjFXrw54MEZXCfR2JpEpDR62 SOrDKh/PA49FIH4HV9+XMDWMfmyWPsl/0HB+UgKNGuRiYOtv3Gvop4yPG56lNLu1 9XJ4SNBiobTcbR16waF0x56bur8zZmtu/kNV1CWrJ0K2hQFijBdjkhK5yzKbakVg KSFol3B2Z3NGWXCtjFzS3L491eZ2QniN4BKNDgLZ/d666sa69iDNARLW7k10OE+Y FEZ55spVBhG9eITcQU97 =y0M2 -END PGP SIGNATURE- Accepted: w3c-markup-validator_1.2+dfsg-6.debian.tar.gz to main/w/w3c-markup-validator/w3c-markup-validator_1.2+dfsg-6.debian.tar.gz w3c-markup-validator_1.2+dfsg-6.dsc to main/w/w3c-markup-validator/w3c-markup-validator_1.2+dfsg-6.dsc w3c-markup-validator_1.2+dfsg-6_all.deb to main/w/w3c-markup-validator/w3c-markup-validator_1.2+dfsg-6_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/e1sj4if-00057v...@franck.debian.org
merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. That brings me to remind you how we got into this situation. w3c-sgml-lib and w3c-dtd-xhtml essentially do the same job and attempt to provide the same data. I packaged w3c-sgml-lib with that intention and it has a watch file pointing at the w3c website and in principle can be maintained without issues. w3c-dtd-xhtml on the other hand is orphaned, has not been touched in *eight* years and has no clear upstream. Of course I considered taking w3c-dtd-xhtml but its layout is not compatible with the W3C upstream source. It is now history that my first attempt at resolving the conflicts failed. This is my second attempt. Obviously it follows from this that if the merger goes through without issue I expect to tag all remaining bugs on w3c-dtd-xhtml as "will not fix" and raise wishlist bugs on any packages that depend on w3c-dtd-xhtml to adapt to using w3c-sgml-lib alone. This does not mean I will refuse to fix bugs in w3c-dtd-xhtml but it does mean that if I am going to make the effort you must make the effort of explaining why I should. If you are happy with the principle of merger but find any issues you can of course raise bugs in the normal way. If these are serious enough they will block these versions going into testing. In principle I have no objection to someone raising a "I am nervous about this." release critical bug to delay entry into testing, so long as: 1.) The bug report makes it clear that this is the nature of the bug. 2.) You provide some objective grounds for your nervousness - i.e. something that could be tested and fixed. 3.) The bug report is clear enough that it can be closed (or perhaps downgraded) in time for me to get vesions 1.3 into testing before the freeze if the concerns are not substantiated. If you have fundamental objections to the merger then I think it is incumbant on you to: 1.) Explain why two essentially duplicate packages, w3c-dtd-xhtml and w3c-sgml-lib, should exist in Debian indefinitely. 2.) Adopt and fix both w3c-dtd-xhtml and wdg-html-validator and earnestly work with me to resolve any conflicts. -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f897ea7.9090...@periapt.co.uk
merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. That brings me to remind you how we got into this situation. w3c-sgml-lib and w3c-dtd-xhtml essentially do the same job and attempt to provide the same data. I packaged w3c-sgml-lib with that intention and it has a watch file pointing at the w3c website and in principle can be maintained without issues. w3c-dtd-xhtml on the other hand is orphaned, has not been touched in *eight* years and has no clear upstream. Of course I considered taking w3c-dtd-xhtml but its layout is not compatible with the W3C upstream source. It is now history that my first attempt at resolving the conflicts failed. This is my second attempt. Obviously it follows from this that if the merger goes through without issue I expect to tag all remaining bugs on w3c-dtd-xhtml as "will not fix" and raise wishlist bugs on any packages that depend on w3c-dtd-xhtml to adapt to using w3c-sgml-lib alone. This does not mean I will refuse to fix bugs in w3c-dtd-xhtml but it does mean that if I am going to make the effort you must make the effort of explaining why I should. If you are happy with the principle of merger but find any issues you can of course raise bugs in the normal way. If these are serious enough they will block these versions going into testing. In principle I have no objection to someone raising a "I am nervous about this." release critical bug to delay entry into testing, so long as: 1.) The bug report makes it clear that this is the nature of the bug. 2.) You provide some objective grounds for your nervousness - i.e. something that could be tested and fixed. 3.) The bug report is clear enough that it can be closed (or perhaps downgraded) in time for me to get vesions 1.3 into testing before the freeze if the concerns are not substantiated. If you have fundamental objections to the merger then I think it is incumbant on you to: 1.) Explain why two essentially duplicate packages, w3c-dtd-xhtml and w3c-sgml-lib, should exist in Debian indefinitely. 2.) Adopt and fix both w3c-dtd-xhtml and wdg-html-validator and earnestly work with me to resolve any conflicts. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f897ea7.9090...@periapt.co.uk
Bug#625262: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. That brings me to remind you how we got into this situation. w3c-sgml-lib and w3c-dtd-xhtml essentially do the same job and attempt to provide the same data. I packaged w3c-sgml-lib with that intention and it has a watch file pointing at the w3c website and in principle can be maintained without issues. w3c-dtd-xhtml on the other hand is orphaned, has not been touched in *eight* years and has no clear upstream. Of course I considered taking w3c-dtd-xhtml but its layout is not compatible with the W3C upstream source. It is now history that my first attempt at resolving the conflicts failed. This is my second attempt. Obviously it follows from this that if the merger goes through without issue I expect to tag all remaining bugs on w3c-dtd-xhtml as "will not fix" and raise wishlist bugs on any packages that depend on w3c-dtd-xhtml to adapt to using w3c-sgml-lib alone. This does not mean I will refuse to fix bugs in w3c-dtd-xhtml but it does mean that if I am going to make the effort you must make the effort of explaining why I should. If you are happy with the principle of merger but find any issues you can of course raise bugs in the normal way. If these are serious enough they will block these versions going into testing. In principle I have no objection to someone raising a "I am nervous about this." release critical bug to delay entry into testing, so long as: 1.) The bug report makes it clear that this is the nature of the bug. 2.) You provide some objective grounds for your nervousness - i.e. something that could be tested and fixed. 3.) The bug report is clear enough that it can be closed (or perhaps downgraded) in time for me to get vesions 1.3 into testing before the freeze if the concerns are not substantiated. If you have fundamental objections to the merger then I think it is incumbant on you to: 1.) Explain why two essentially duplicate packages, w3c-dtd-xhtml and w3c-sgml-lib, should exist in Debian indefinitely. 2.) Adopt and fix both w3c-dtd-xhtml and wdg-html-validator and earnestly work with me to resolve any conflicts. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f897ea7.9090...@periapt.co.uk
Bug#615125: merging w3c-dtd-xhtml and w3c-sml-lib: ten days to object or find issues
I am just about to upload w3c-sgml-lib that also generates w3c-dtd-xhtml (which will depend on w3c-sgml-lib and consist of links). I have endeavoured to fix all conflicts and ensure that nsgmls, wdg-html-validator, w3c-markup-validator still work. I have to put a caveat on that. As far as I can see wdg-html-validator no longer works at all well. So I mean that my new versions do not make it worse. That brings me to remind you how we got into this situation. w3c-sgml-lib and w3c-dtd-xhtml essentially do the same job and attempt to provide the same data. I packaged w3c-sgml-lib with that intention and it has a watch file pointing at the w3c website and in principle can be maintained without issues. w3c-dtd-xhtml on the other hand is orphaned, has not been touched in *eight* years and has no clear upstream. Of course I considered taking w3c-dtd-xhtml but its layout is not compatible with the W3C upstream source. It is now history that my first attempt at resolving the conflicts failed. This is my second attempt. Obviously it follows from this that if the merger goes through without issue I expect to tag all remaining bugs on w3c-dtd-xhtml as "will not fix" and raise wishlist bugs on any packages that depend on w3c-dtd-xhtml to adapt to using w3c-sgml-lib alone. This does not mean I will refuse to fix bugs in w3c-dtd-xhtml but it does mean that if I am going to make the effort you must make the effort of explaining why I should. If you are happy with the principle of merger but find any issues you can of course raise bugs in the normal way. If these are serious enough they will block these versions going into testing. In principle I have no objection to someone raising a "I am nervous about this." release critical bug to delay entry into testing, so long as: 1.) The bug report makes it clear that this is the nature of the bug. 2.) You provide some objective grounds for your nervousness - i.e. something that could be tested and fixed. 3.) The bug report is clear enough that it can be closed (or perhaps downgraded) in time for me to get vesions 1.3 into testing before the freeze if the concerns are not substantiated. If you have fundamental objections to the merger then I think it is incumbant on you to: 1.) Explain why two essentially duplicate packages, w3c-dtd-xhtml and w3c-sgml-lib, should exist in Debian indefinitely. 2.) Adopt and fix both w3c-dtd-xhtml and wdg-html-validator and earnestly work with me to resolve any conflicts. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
