Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'
On 01/11/15 18:07, Dominique Dumont wrote: On Sunday 01 November 2015 18:59:25 Jonas Smedegaard wrote: Jonas, do you agree with this proposal ? If you mean to *not* apply filter when user has explicitly instructed what files to work on (by use of regex), then I am in favor. Could you provide some example of licensecheck command that use a regex ? (I want to make sure that we understand each other) All the best For the record license-reconcile uses licnesecheck in two ways: 1.) everything in a directory recursively. 2.) specific files. Also this discussion should really be taking place against devscripts. So this bug should be cloned onto that.
Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'
I have had another think and I would like to make the folloiwng points. 1.) license-reconcile is an experimental package and not at all critical to Debian. Unlike decscripts so something is a really wrong if a bug in license-reconcile affects devscripts. 2.) I think what Steve meant to do was clone #801609, retitle and reassign the clone to devscripts. That's reasonable as there may well be more work to do. 3.) As it is supposed to work, license-reconcile is not wholly dependent on licensecheck. That said I think one filter is probably obsolete now that licensecheck has been improved. 4.) The core thing I wish to avoid is licnese-reconcile development and licensecheck development being tied together in anyway. That of course means licensecheck will continue to cause problems for license-reconcile but as long as those problems are not gratuitous I see no issue. On 31/10/15 19:41, Dominique Dumont wrote: On Friday 30 October 2015 10:58:55 Steve Langasek wrote: But I'm also marking this as affects: devscripts, because I find it surprising that the new licensecheck output includes a line for sample.png, when the file was explicitly reported as unparseable. It doesn't seem desirable to me that licensecheck would list files in its output that are definitely not going to have embedded license/copyright information and whose copyright information must be listed elsewhere. Perhaps we want to make sure the new behavior for licensecheck is settled before patching license-reconcile. For what it's worth this change of behavior was requested in #794282 [1]. Jonas explicitly requested licensecheck to parse binary files. This broke 'cme update dpkg-copyright', which led to #797562 [2] . To alleviate the issue, I added a -t option to licensecheck to skip binary files. After re-reading the whole saga, I think this situation can be improved. I'll discuss with Jonas to nail down the requirements for a better solution. All the best [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794282 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797562
Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'
I am working on this in license-reconcile. However I really don't see how this could affect devscripts. devscripts is a core package, license-reconcile is no such thing, On 30/10/15 17:58, Steve Langasek wrote: Control: affects -1 devscripts We are seeing this same failure in Ubuntu following the update of devscripts to 2.15.9. The change causing the failure is that licensecheck -r no longer filters based on filenames, instead filtering only on mime types; and so instead of returning copyright results only for t/data/example/base.h, it returns results for all files (base.h, debian/copyright, debian/changelog, base, sample.png). $ licensecheck --no-conf --recursive t/data/example 2>/dev/null t/data/example/base.h: GPL (v2) t/data/example/debian/copyright: *No copyright* GPL (v1 or later) t/data/example/debian/changelog: *No copyright* UNKNOWN t/data/example/base: GPL (v2) t/data/example/sample.png: *No copyright* UNKNOWN $ Compare the earlier behavior: $ licensecheck --no-conf --recursive t/data/example t/data/example/base.h: GPL (v2) $ This is a behavior change that license-reconcile will need to adapt its testsuite to. But I'm also marking this as affects: devscripts, because I find it surprising that the new licensecheck output includes a line for sample.png, when the file was explicitly reported as unparseable. It doesn't seem desirable to me that licensecheck would list files in its output that are definitely not going to have embedded license/copyright information and whose copyright information must be listed elsewhere. Perhaps we want to make sure the new behavior for licensecheck is settled before patching license-reconcile.
Bug#801609: license-reconcile: FTBFS: cannot parse file 't/data/example/sample.png'
Looking at https://www.debian.org/Bugs/server-control#affects you are implying that the bug in license-reconcile impacts licensecheck. How is that possible? Noone in devscripts should care (at the moment at least) if licensecheck was removed from Debian entirely. On 30/10/15 19:37, Steve Langasek wrote: On Fri, Oct 30, 2015 at 07:36:11PM +, Nicholas Bamber wrote: I am working on this in license-reconcile. However I really don't see how this could affect devscripts. devscripts is a core package, license-reconcile is no such thing, I thought my reasoning was rather clear: But I'm also marking this as affects: devscripts, because I find it surprising that the new licensecheck output includes a line for sample.png, when the file was explicitly reported as unparseable. It doesn't seem desirable to me that licensecheck would list files in its output that are definitely not going to have embedded license/copyright information and whose copyright information must be listed elsewhere. Perhaps we want to make sure the new behavior for licensecheck is settled before patching license-reconcile.
Bug#777930: ksh
owner 777930 nicho...@periapt.co.uk thanks The upload was rejected but I will try again.
Bug#777930: nmu on the 10 day delayed queue
I have uploaded the patched version on the 10 day delayed queue.
Bug#752724: bashdb
Oleksandr, Are you interested in fixing the RC bugs in bashdb? I've had a look and I think I could give it a go. it mainly seems to need updating to the latest pstream version.
Bug#692871: mysql-5.5
found 692871 5.5.24+dfsg-9 tag 692871 +patch thanks This is clearly not introduced in 5.5.28+dfsg-1 and I am marking it as such. I'd like to get 5.5.28++dfsg-1 into testing before looking at this. ANd then I would like to check what we can close as a result of fixing this. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636158: maradns: Debian default config is not robust to user change + upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Debian Release Team, Please could I have a stay of execution on maradns? I am somewhat overwhelmed with stuff at the moment but I am steadily working my way through it (including the Debian stuff). And the maradns RC bug came fairly late in the whole release cycle. I would also accept an NMU if one turns up. On 23/10/12 17:42, gregor herrmann wrote: On Wed, 26 Sep 2012 17:59:17 +0200, gregor herrmann wrote: Find attached a quick patch which seems to work (as in: create /etc/maradns/mararc on a new install and leave it alone for upgrades). Of course the template could be put somewhere else, and the nested conditions in the postinst written differently. Hi Nicholas, I noticed that maradns is on the Release Team's removal candidate list: https://lists.debian.org/debian-devel/2012/10/msg00373.html Are you going to upload a fix before Friday (or to contact them) or can I help in any way? Cheers, gregor -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQia0+AAoJELbE2bY7/+c8SMsP/0J1L8VbJZcsJ6VXw7d14hp0 dSEyxzxlXU3LZcV7k1A7DATd8Ut9Fg2uDCs4l1X9qkz4oVkBy4OqLL5UIRl7Bb0x XfkcygoZwvYcDgHiA04mSeo1ILXq6DVVisy5aGM72Nhoaiasbok14LTW/El5qSy6 PdcE63yT/vJ3B5ZSBSEmoSTI1SA1hRijwTCZtq49qcWsUa+DqA3IKoMhKXA/VmaK 1xhpPDA7A//o12FQuenY4jDgK/qCRyj390OqT1cobJa1EU6PUyYAWlNudShhN04L IfW3XhdF8jiuSddGo4FVclmdc66a5A0w3Gr3PELDHACoDnxyd/ZCOEEF7jt+dQr7 Tzy4H6o+y1iy35p6uuTgz4zyQ/xMwxc0H6Y5SwFsw7lHnxm461bNJdbv9xnBsgHI Mr2wGVdvJ7PgLxugvKfLQU9ay77mjpMY1iKSYuY3pcm2bVydA6ajE39xg8seJSLz 6t6SDF71V796RWgs8C6RxUZ/iPprFvBQJsREA4d9otlL6lQ/p8Ex/EmHbcZCeAbC U6Kf7km7a5xt153O02MhorPC/AY/OIwViHcHU4Yz2JeeXtE2I5Js4flrg9l9yK0U M0SvdhByDcFoDnLhlMek1vwcfD1NdUujGy6uZi0oV5BpdpDvpC0eFQJS4c0UMb1H WecPVO6LsfN/6gCw98ZN =3re5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636158: maradns: Debian default config is not robust to user change + upgrade
On 25/10/12 22:35, Niels Thykier wrote: On 2012-10-25 23:21, Nicholas Bamber wrote: Dear Debian Release Team, Please could I have a stay of execution on maradns? I am somewhat overwhelmed with stuff at the moment but I am steadily working my way through it (including the Debian stuff). And the maradns RC bug came fairly late in the whole release cycle. I would also accept an NMU if one turns up. [...] Certainly. I have taken maradns off the list for now. Would an extra week enough? ~Niels Thanks. I'll probably being looking at it from Monday. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687485: update
On 10/10/12 23:27, Nicholas Bamber wrote: The patch did not compile as expected. I've been bogged down with other packages. However I expect to have another go next week and look at fixing the compilation errors. I find it hard to feel in a hurry as I am in doubt whether the patch will be accepted in the end anyway. I have fixed the compilation issue. One of the bits of the patches that needed manually adjusted was not correct. Now it compiles but a test fails. Looking at the failure it is probably the same issue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687485: update
The patch did not compile as expected. I've been bogged down with other packages. However I expect to have another go next week and look at fixing the compilation errors. I find it hard to feel in a hurry as I am in doubt whether the patch will be accepted in the end anyway. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689107: w3c-linkchecker
Piuparts issues have turned up for real now. http://piuparts.debian.org/sid/fail/w3c-linkchecker_4.81-5.log I'm not clear how I missed this but the cause is clear enough from reading the ucf man page. ucf --purge does not actually delete the file. I'll need to remove /etc/w3c/ if it's empty. Really it looks like a good idea to standardize the directory as well, but probably not now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688736: w3c-linkchecker: modifies conffiles (policy 10.7.3): /etc/w3c/checklink.conf
On 26/09/12 07:35, Ivan Shmakov wrote:
Russ Allbery r...@debian.org writes:
Ivan Shmakov oneing...@gmail.com writes:
What bothers me more, however, is that the ${CFG_TMP} filename bears
an utterly generic “.tmp” suffix, and should, for one reason or
another, such a filename exist at the time .postinst is run, we're
going to silently overwrite it.
Thus, my preference would be to use mktemp(1), e. g.:
+CFG_TMP=$(mktemp -- /etc/w3c/.checklink.conf.)
TIA.
Another standard approach here is to use .dpkg-new, which is used by
dpkg for conffiles for a similar purpose and which local
administrators are therefore used to seeing if it gets left behind
for some reason.
Indeed.
I am generally happy with the patch (and the dpkg-new suggestion) on
inspection. However I feel slightly queezy about the db_version stuff.
It seems likely to be harmless. However I can find only the briefest of
documentation about it. It can return an error which presumably should
be checked. I can't find anything in Policy saying it should be used or
any recommendations on why it is advisable.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688736: w3c-linkchecker: modifies conffiles (policy 10.7.3): /etc/w3c/checklink.conf
tag 688736 +patch thanks Hideki, Thanks for the patch. I'll be happy to apply and acknowledge the patch. I am however concerned that the it appears the version of piuparts which generates these reports is not yet in sid, and I would like to hold off working on it until it is. There is also the small matter that some work was already pending on this package but which cannot go into Wheezy. So that will have to be moved into a git branch. On 25/09/12 23:28, Hideki Yamane wrote: tags 688736 patch thanks Hi, I've created patch for this bug, piuparts clean one. It seems to be good for me, please check it. Thanks. ___ pkg-perl-maintainers mailing list pkg-perl-maintain...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-perl-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687485: mysql-5.5: CVE-2012-4414
On 21/09/12 12:32, Nicholas Bamber wrote: On 20/09/12 22:33, Moritz Muehlenhoff wrote: On Wed, Sep 19, 2012 at 07:07:23PM +0100, Nicholas Bamber wrote: I am looking at this bug. However the patch involves 45 files. 17 of these are test files. From what I have seen so far they do not apply cleanly. Presumably they are meant for 5.5.27 rather than 5.5.24. I have yet to form a judgement on quite how intractable adapting the patch is going to be. Due to the intransparent nature of mysql security updates we will need to follow the 5.5.x releases for stable-security anyway. As such I don't see a reason not to upload 5.5.27 during the freeze as well. Cheers, Moritz Dear Release Team, Are you okay with the following plan? 1.) I check that the maraiadb_patch.diff really does apply cleanly against 5.5.27. 2.) I upload 5.5.24+dfsg-9 with the other pending fixes. (*diff.txt attached). 3.) I then upload 5.5.27+dfsg-1 including the mariadb_patch,diff - or if oracle have by then released 5.5.28, 5.5.28+dfsg. Actually it applies no more cleanly against 5.5.27 then 5.5.24. So I intend to fix the other wheezy worthy stuff and then review. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687485: mysql-5.5: CVE-2012-4414
I am looking at this bug. However the patch involves 45 files. 17 of these are test files. From what I have seen so far they do not apply cleanly. Presumably they are meant for 5.5.27 rather than 5.5.24. I have yet to form a judgement on quite how intractable adapting the patch is going to be. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#687485: mysql-5.5: CVE-2012-4414
On 19/09/12 19:07, Nicholas Bamber wrote: I am looking at this bug. However the patch involves 45 files. 17 of these are test files. From what I have seen so far they do not apply cleanly. Presumably they are meant for 5.5.27 rather than 5.5.24. I have yet to form a judgement on quite how intractable adapting the patch is going to be. The results of a dry run are attached. Script started on Wed 19 Sep 2012 19:27:43 BST ]0;nicholas@beaumont: ~/debian/svn/pkg-mysql/mysql-5.5/branches/wheezynicholas@beaumont:~/debian/svn/pkg-mysql/mysql-5.5/branches/wheezy$ patch --dry-run -p0 ~/debian/notes/MySQL/mariadb_patch.diff patching file client/mysqlbinlog.cc Hunk #1 FAILED at 743. 1 out of 1 hunk FAILED -- saving rejects to file client/mysqlbinlog.cc.rej patching file include/my_sys.h Hunk #1 FAILED at 627. Hunk #2 succeeded at 744 (offset -7 lines). 1 out of 2 hunks FAILED -- saving rejects to file include/my_sys.h.rej can't find file to patch at input line 38 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- | |=== modified file 'mysql-test/r/mysqlbinlog-innodb.result' |--- mysql-test/r/mysqlbinlog-innodb.result 2011-10-19 19:45:18 + |+++ mysql-test/r/mysqlbinlog-innodb.result 2012-08-24 13:29:01 + -- File to patch: Skip this patch? [y] Skipping patch. 2 out of 2 hunks ignored patching file mysql-test/r/mysqlbinlog.result Hunk #7 FAILED at 427. Hunk #8 FAILED at 445. Hunk #12 succeeded at 826 (offset 1 line). 2 out of 12 hunks FAILED -- saving rejects to file mysql-test/r/mysqlbinlog.result.rej patching file mysql-test/r/mysqlbinlog2.result patching file mysql-test/r/mysqlbinlog_row.result patching file mysql-test/r/mysqlbinlog_row_innodb.result patching file mysql-test/r/mysqlbinlog_row_myisam.result patching file mysql-test/r/mysqlbinlog_row_trans.result patching file mysql-test/r/user_var-binlog.result patching file mysql-test/suite/binlog/r/binlog_base64_flag.result can't find file to patch at input line 623 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- | |=== modified file 'mysql-test/suite/binlog/r/binlog_row_mysqlbinlog_options.result' |--- mysql-test/suite/binlog/r/binlog_row_mysqlbinlog_options.result 2011-10-19 19:45:18 + |+++ mysql-test/suite/binlog/r/binlog_row_mysqlbinlog_options.result 2012-08-24 13:29:01 + -- File to patch: Skip this patch? [y] Skipping patch. 6 out of 6 hunks ignored patching file mysql-test/suite/binlog/r/binlog_stm_ctype_ucs.result patching file mysql-test/suite/binlog/r/binlog_stm_mix_innodb_myisam.result can't find file to patch at input line 716 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- | |=== modified file 'mysql-test/suite/rpl/r/rpl_hrtime.result' |--- mysql-test/suite/rpl/r/rpl_hrtime.result 2011-10-19 19:45:18 + |+++ mysql-test/suite/rpl/r/rpl_hrtime.result 2012-08-24 13:29:01 + -- File to patch: Skip this patch? [y] Skipping patch. 1 out of 1 hunk ignored patching file mysql-test/suite/rpl/r/rpl_mdev382.result patching file mysql-test/suite/rpl/r/rpl_row_mysqlbinlog.result patching file mysql-test/suite/rpl/r/rpl_sp.result patching file mysql-test/suite/rpl/t/rpl_mdev382.test patching file mysys/mf_iocache2.c patching file sql/ha_ndbcluster_binlog.cc Hunk #1 succeeded at 1296 (offset 1 line). Hunk #2 succeeded at 1307 (offset 1 line). patching file sql/item.cc Hunk #1 FAILED at 992. 1 out of 1 hunk FAILED -- saving rejects to file sql/item.cc.rej patching file sql/item.h Hunk #1 FAILED at 656. 1 out of 1 hunk FAILED -- saving rejects to file sql/item.h.rej patching file sql/item_func.cc Hunk #1 succeeded at 5257 (offset -186 lines). patching file sql/item_func.h Hunk #1 succeeded at 1574 (offset -96 lines). patching file sql/log.cc Hunk #1 FAILED at 52. Hunk #2 succeeded at 2020 with fuzz 2 (offset -53 lines). Hunk #3 succeeded at 2043 with fuzz 2 (offset -53 lines). 1 out of 3 hunks FAILED -- saving rejects to file sql/log.cc.rej patching file sql/log_event.cc Hunk #1 succeeded at 45 (offset -1 lines). Hunk #2 succeeded at 427 (offset -45 lines). Hunk #3 succeeded at 879 (offset -47 lines). Hunk #4 succeeded at 888 (offset -47 lines). Hunk #5 succeeded at 903 (offset -47 lines). Hunk #6 succeeded at 2158 (offset -291 lines). Hunk #7 succeeded at 2995 (offset -335 lines). Hunk #8 succeeded at 3637 (offset -368 lines). Hunk #9 succeeded at 4286 (offset -495 lines). Hunk #10 succeeded at 4848 (offset -497 lines). Hunk #11 succeeded at 4870 (offset -497 lines). Hunk #12 succeeded at 5048 (offset -497 lines). Hunk #13 succeeded at 5263 (offset -500 lines). Hunk #14 succeeded at 5412 (offset -505 lines). Hunk #15 succeeded at 5510 (offset -532 lines). Hunk #16 FAILED at 6139. Hunk #17 succeeded at 5824 (offset -550 lines). Hunk #18 succeeded at 6038
Bug#672616: gforth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Peterm So the bad news is that the build daemons got in a mess. The good news is that at least one FTP person thinks this will clear in about 24 hours and then the build daemons will start building gforth. If that fails I guess you'll have to remove the build dependency on gforth and have some horrendous patch of the regenerated versions of those files. On 10/09/12 22:25, Nicholas Bamber wrote: Peter, I started looking at gforth again. I'll let you know. On 07/09/12 22:45, Peter Pentchev wrote: On Fri, Sep 07, 2012 at 10:36:04PM +0100, Nicholas Bamber wrote: Peter, If noone else does I will certainly endeavour to get this into wheezy. I probably won't get round to until later next week which gives the others a chance if they have more time. By the way I didn't get the email which is I guess another thing I'll have to look at. Thank you! Yes, it is quite possible that something went wrong with my sending the e-mail; I hope this one gets through better. G'luck, Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQT5hxAAoJELbE2bY7/+c8448QANW2g/6OBGVJLYFFZBGU96i6 MSK5D1eCdCnjdQoquMAHgeG48dbkqm3UgUBpO9841yQhi/aPi0oFhtQV21jC6WCK +M37NibGCKeqUsEk2NSpBM7c+4rFWp23lF8BrixBn/WythbtYem15cuiJasnDx8g 2o77CPo5vBpbR05DRZrQDBMX32xvlxvGNYb3jCO/nFw42j5Cf2QTWudK3K9Bshmy Hoasf7yTd9Aaax6FGTOzt4JqPnhZrcjlXB/B51Gtfrc4wRbZHmNUOtW+Li+THhRV bX8nJAfc/XRm5XmMtg6HJdgw6Bk/l3Jr308lWn5zEFe11KzaJ5px0C9FBQLZjyE8 K1Juh5Gy9DgzJ2L9cl6Yxp6g/s9EUrFAs8kjCgRftrzp6iv/jgpj7hhO9iNaXMYK vxlvTZjBhE9nKXJdtRfYiOV+TqEAcYklrXZv8gspV63BmFWXXN+g5Urnf5D6yun0 MHdXqAMy13PinJBpiqbH0dMtiLcKCcVNugmib5OGjNHf8gQjlV9qDVW6cR9qr2gP C1SuZDLi9EQUBlqjey0KCDTabo1TUxsRS6UUeaMeKHDpjSs9mWeFqEDP62RWn4rS j0fu41z4frhNtleW78mlnEisCO0jbnXSTO+lZDkwz3bGBE+kLiUEUp0EiLyGLZzR ZJOal0C0hb8IiNXhKzLu =v4iy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672616: gforth
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Peter, I started looking at gforth again. I'll let you know. On 07/09/12 22:45, Peter Pentchev wrote: On Fri, Sep 07, 2012 at 10:36:04PM +0100, Nicholas Bamber wrote: Peter, If noone else does I will certainly endeavour to get this into wheezy. I probably won't get round to until later next week which gives the others a chance if they have more time. By the way I didn't get the email which is I guess another thing I'll have to look at. Thank you! Yes, it is quite possible that something went wrong with my sending the e-mail; I hope this one gets through better. G'luck, Peter -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQTlq6AAoJELbE2bY7/+c8FHAQAM22TpMN1t6ehCqL3XSfmAW0 7t3SdEg92z5Q28BxwzBDaT6NRtNKCysnxyX9IK5DJMMSl8nPcxwz/zaGIx9xWAK+ SpEdS3z5MOi3voj9wl/HEKjXvT5ffHBICTPOf9vERij7X2/DdK6OH7gfmeCmCTjg Q3SH9v23hQZtXr8FOc45pAhy3rgGYjmrxq6d58TAyo/Itd3jxeh/GEQiY1tKWokv rYE/XLWHioSiRA2ynNcX1fhpvnbazlWpF4EyOLq/P/Eqx8a1MWMaa+T3uFwBRKba ZMFxnxkpRnj3wsrcGRBTNjEq6IH/UyeilKQqvLkmNO+aaMeLGIvxdz+FN2hh0QUz 0F5paHM0QxG/a7PzdGVfCuRk1GKS2AHlC24U+oiquwT7EdlpIW4FWyL3foLIw5Ag OBC478MO+JnAgj5/2BLns+qoeB/ybIwwV8akvhSCH7JYEnPnGFC46pRrfV/TOM00 +uq0A7KJqhd1jEBEPeqIr1dd+mRYSkVHwSpsnqbMZCqPodZ/J8Ut6lzWfBJcfc0+ 6Mgr5mQJ0etQQAZL1G2DN1Q5CBXORYmpSuRsN5dRk7HOeFb24Ax2L9AufWSyAb97 uiIO4BEb7vRKzaWleFtvutAFsu8edOagYeDxIbFyRFWECB29lKoGrsRYUyGdlGsS nKGMcf573C+qrAEMLa/w =9MCK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672616: gforth
Peter, If noone else does I will certainly endeavour to get this into wheezy. I probably won't get round to until later next week which gives the others a chance if they have more time. By the way I didn't get the email which is I guess another thing I'll have to look at. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685865: thoughts
severity 685865 normal tag +wontfix -upstream thanks Andre, I've finally managed to read through the bug report after having a difficult week or two. I would like to begin by reconstructing what happened with your upgrade as indicated by term.log. 1.) From line 1180 to 1219 we see mysql-5.5 being unpacked 2.) From line 1264 to 1286 the actual installation happened and was successful. 3.) From line 1332 it starts to purge mysql-server-5.5. (Why it should do that is I think the principle mystery. And why a purge and not a remove?) 4.) Consequently at line 1333 it tries to stop the server. Unfortunately it fails. This could be a bug but since I don't understand why it is being removed in the first place I don't see it as an important one. 5.) At line 1339 it tries to start the server even though the stop process clearly returned a failure and also even though it is apparently trying to remove the package. 6.) At line 1340 it tries to remove mysql-workbench presumably because it has decided to remove mysql. 7.) At line 1342 we get the glorious declaration dpkg: mysql-client-5.5: dependency problems, but removing anyway as you requested: 8.) At line 1345 it removes mysql-client-5.5. 9.) At line 1357 it reinstalls mysql-client-5.5. 10.) At line 1383 it tries again to install mysql-server-5.5. So first of all it tries again to stop the server which again fails. 11.) From line 1393 it starts to get in a real mess. There is already a mysqld process running which has a lock on the ./ibdata files and so on. 12.) By line 1717 the mysqld process has given up trying to register the InnoDB engine. So now it becomes clear that the innodb comments are symptons and not the root cause. So it strongly seems to me that the questions that first need to be answered are what did your package manager software think it was doing? Until someone can demonstrate this problem using just apt or at least explain why it tried to remove the mysql software after and as part of an upgrade I am downgrading and marking it will not fix. I await further information. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685865: [debian-mysql] Bug#685865: mysql-server-5.5: Upgarding STILL..!! doesn't work, init script can't start/stop server...
tag 685865 +moreinfo thanks Some questions that occur are: 1.) What version are you upgrading from? 2.) Have you tried using apt rather than synaptic? (So yes I better have a play with synaptic but I cannot just now). 3.) Can you try breaking down the process so we can pinpoint more exactly where the issue is. Remove the reverse dependency packages for a start, stopping the server manually and so on. 4.) I assume you can start/stop the server normally? 5.) Looking at the attached files it seems that you are upgrading from a version where innodb is a plugin and that the errors appear to be in that area, to one where it is built in. Any relevant information would appreciated. 6.) The phrase STILL..!! seems to imply something. However I am missing that implication. Please elaborate. On 25/08/12 16:29, Andre Verwijs wrote: Package: mysql-server-5.5 Version: 5.5.24+dfsg-7 Severity: critical Tags: upstream Justification: breaks unrelated software Upgarding STILL..!! doesn't work, init script can't start/stop server when upgrading to newer version... -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mysql-server-5.5 depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.46 ii initscripts2.88dsf-22.1 ii libc6 2.13-35 ii libdbi-perl1.622-1 ii libgcc11:4.7.1-2 ii libstdc++6 4.7.1-2 ii lsb-base 4.1+Debian7 iu mysql-client-5.5 5.5.24+dfsg-7 ii mysql-common 5.5.24+dfsg-7 ii mysql-server-core-5.5 5.5.24+dfsg-7 ii passwd 1:4.1.5.1-1 ii perl 5.14.2-12 ii psmisc 22.19-1 Versions of packages mysql-server-5.5 recommends: ii bsd-mailx [mailx] 8.1.2-0.2006cvs-1 ii libhtml-template-perl 2.91-1 Versions of packages mysql-server-5.5 suggests: pn tinycanone -- debconf information: mysql-server/error_setting_password: mysql-server-5.5/postrm_remove_databases: false mysql-server-5.5/start_on_boot: true mysql-server-5.5/nis_warning: mysql-server-5.5/really_downgrade: false mysql-server/password_mismatch: mysql-server/no_upgrade_when_using_ndb: ___ 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#685072: dropping severity
severity 685072 normal tag -confirmed +unreproducible thanks I have been unable to reproduce this consistently. When I did it was a different message from what was originally reported. I have tried going back in time with snapshots.debian.org and I cannot reproduce it. It occurs to me that my issue may have been caused by bypassing apt-get to quickly test something. I should probably stop doing that. And if this is so difficult to reproduce at least it is unlikely to be serious. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685072: stuck
I was investigating this further. After doing a general upgrade I can no longer reproduce this. I have tried recreating the situation in a schroot but failed. Amy more information would be appreciated. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685072: confirmed
tag 685072 -moreinfo -unreproducible +confirmed thanks I can confirm this now. The steps to reproduce (on a sid machine) are: 1.) Download the 5.5.24+dfsg-5 binaries from snapshot.debian.org into a directory 2.) su 3.) Establish the original context 'dpkg -B -i *.deb' 4.) either 'apt-get install mysql-server-5.5' or more seriously 'apt-get upgrade' An easy work around is 'apt-get install -f' before step 4. However clearly this needs to be fixed. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685072: upgrade issues
tag 685072 +unreproducible +moreinfo thanks I have not managed to reproduce this. I have tried piuparts in three ways and a direct -6 to -7 upgrade. I have not had time to do a -5 to -7 upgrade as I did not have the -5 debs lying around. I probably won't have time for a day or two to get them from snapshot.debian.org. However I cannot see any obvious reason why this should make a difference. Just casting around for ideas the only thing I can think of at the moment is can you upgrade from -5 to -7 via -6? You should be able to do that easily for the next week with the following steps: 1.) change the source to testing in /etc/apt/sources.list 2.) apt-get update 3.) apt-get install mysql-server-5.5 4.) change the source back to sid 5.) apt-get update 6.) apt-get install mysql-server-5.5 Another thing that puzzled me is: 1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not fully installed or removed. why are so few packages upgraded? I'm guessing that what is required to trigger this is some sequence of partial upgrades rather than a straightforward apt-get upgrade. If so I doubt that this would warrant the severity I put in earlier. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675005: downgrading
severity 675005 important thanks I don't see why this situation is any different from the maintainer being MIA. He did not reply to an earlier email so from my point of view he is. Hence I am downgrading the bug report. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682210: Mysql-5.5
Moritz, Do you still see any reason to keep this bug report open? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682232: #682232
severity 682232 important thanks Antti-Juhani, Thanks for your cooperation. Since you have managed to recover I feel fully justified in downgrading to important. The information you have sent from the logs is very good, but so far no different from any other innodb corruption. Since innodb became the default storage engine in version 5.5 , one possible theory that occurs to me is that the following happened: 1.) There had been in the past some temporary experiment with innodb. 2.) After that experiment some innodb files lay lying around. 3.) During the upgrade these old innodb files got in the way. If you think that might have happened, that might give us some scenarios from which we could try to get a reproducible bug. If you still have the old innodb files, I believe there are some tools for reading them which might be interesting. Lastly I suppose you could try the following: 1.) Install mysql-5.1 in a clean squeeze environment. 2.) import a logical dump of your database. 3.) upgrade to 5.5. If that reproduces the error then I think we'd be onto something. Sorry but I've run out of ideas for now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682232: [debian-mysql] Bug#682232: mysql-server-5.5: Fails to upgrade squeeze - wheezy, does not start
-- Configuration Files: /etc/logcheck/ignore.d.paranoid/mysql-server-5_5 [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.paranoid/mysql-server-5_5' /etc/logcheck/ignore.d.server/mysql-server-5_5 [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.server/mysql-server-5_5' /etc/logcheck/ignore.d.workstation/mysql-server-5_5 [Errno 13] Permission denied: u'/etc/logcheck/ignore.d.workstation/mysql-server-5_5' -- debconf information: mysql-server/error_setting_password: mysql-server-5.5/postrm_remove_databases: false mysql-server-5.5/nis_warning: mysql-server-5.5/really_downgrade: false mysql-server-5.5/start_on_boot: true mysql-server/password_mismatch: mysql-server/no_upgrade_when_using_ndb: Antti-Juhani, Have you tried fixing the permission errors? After that relevant sections from syslog please. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679437: I'm about to upload an NMU to fix the copyright issue
Phillip, I only just realized you have picked it up again. Sorry. I should have subscribed to the package before working on it. I am sure you can do a better job than me. How you want to play it is up to you. However I think the best way of keeping brewtarget in wheezy is for me to bring the NMU forward as fast as possible and hopefully the release team would accept it in wheezy. That way you have more time to make the next release and you can throw away or incorporate my changes as you wish. On 14/07/12 08:41, Nicholas Bamber wrote: Phillip, If the copyright issues as per #679437 are not sorted out, brewtarget would most likely get removed from Debian which would be a shame. I have prepared a non-maintainer upload which should fix them but you can always do so yourself. The debdiff is attached. However this gives the misleading impression that the offending images have not been removed. I assume debdiff is treating them as zero-length files. So I include tardiffs as well. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679437: I'm about to upload an NMU to fix the copyright issue
Phillip, Certainly you should continue with your upload to mentors. I have to say if you want tme to upload a full revision I would normally insist on getting it totally lintian clean which might be too much for the release team at this stage. On 14/07/12 16:14, Philip Lee wrote: Nicholas, Thanks for the help. I was actually just preparing a new package (1.2.5) and uploading to mentors to fix not only this bug, but also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679350 which is an intermittent segfault. Should I continue on this path (it will be completely ready in another hour), or should I let you take care of it? On Sat, Jul 14, 2012 at 10:00 AM, Nicholas Bamber nicho...@periapt.co.uk mailto:nicho...@periapt.co.uk wrote: Phillip, I only just realized you have picked it up again. Sorry. I should have subscribed to the package before working on it. I am sure you can do a better job than me. How you want to play it is up to you. However I think the best way of keeping brewtarget in wheezy is for me to bring the NMU forward as fast as possible and hopefully the release team would accept it in wheezy. That way you have more time to make the next release and you can throw away or incorporate my changes as you wish. On 14/07/12 08:41, Nicholas Bamber wrote: Phillip, If the copyright issues as per #679437 are not sorted out, brewtarget would most likely get removed from Debian which would be a shame. I have prepared a non-maintainer upload which should fix them but you can always do so yourself. The debdiff is attached. However this gives the misleading impression that the offending images have not been removed. I assume debdiff is treating them as zero-length files. So I include tardiffs as well. -- Philip G. Lee rocketman...@gmail.com mailto:rocketman...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627174: sd
I've raised #627174 to request this package's removal. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679350: brewtarget
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/07/12 01:44, Cyril Brulebois wrote: Hello, Nicholas Bamber nicho...@periapt.co.uk (03/07/2012): I cannot reproduce the crash but there is a patch if someone can. Else can this bug be downgraded to important. I was thinking of raising an NMU but I'm not sure if I feel comfortable for just one bug. And of course I have copied the maintainer. I'm not sure why you Cc'd the release team when replying. If you need any action from us, please say so. From a very quick glance, it doesn't look like there's anything needed from our side. Mraw, KiBi. Cyril, The best I can do with brewtarget is rewrite the copyright file and move it to non-free. The package clearly aspires to be free but I cannot acheive that. And I cannot reproduce the crash failure. So it would only be worth my while trying to fix the copyright issue if the release team are willing for the crash bug to be downgraded. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP+oRLAAoJELbE2bY7/+c8yBsQAOk172mKqJVE0+1fb0XbBhYm B38bfb+NoMgv2bXDW7V9F+QY4/chcTXDIrXgEtG1FKNiYZeuxQCJF/zNHTwICvGY uB6QU0Q445J/xJWR0pDoHRXO4Zz7thHWNY4rAJ5q1V4hn6UwKk/Be+ZTB9K0cSj/ 5w3xTxjcDZACNvQBOEqny/As2GzPnio+PgbSlTzlhmrLRUL3WRjLe/I2yRDZBSfX tAYetqbaTWnQxW4rCK3N7UEs/HydONuOWhLOg4VcY6Pu9MhGotGNJdhUAExkyYIW DY/tqX6fW5GbqKQGScxJ/PdaKh7SkcR8ZUyoKk1SoFKWsrbx+A2NvApHfWmX91MD sZI3ruLeTzwmCddQg0te/FLRp0j/5XLrl3braJtiklZevorrifg8IXr1mqQKN1G9 XEfg55vu6UHWu/+2dEd4fYmuLVBKamD1J/6L5Rar6lTQ48wSebFRaVxkHhHq/oCm U5KKHYZdO0HN9N62DbJ7eqeQshGdELuhnTALd1tIB7tNYXn0DrKgU7T8yuK0QxFN oDADJBXI7s/1FSeejvNooI5a+V/5wszetRJCp9HkbkABiZvhtZPLAB7Z19i0K72F uSL7Gv+sHu3is1wGC4f2Q7I54li3ebpvjpVmK3PJyXtnmltG9quTGWeqHw9c986t FdVBVtBBNrXj0DNTJAl+ =xrBk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665296: Please consider tagging wheezy-ignore #665296
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 665296 debhelper
thanks
On 09/07/12 01:41, Cyril Brulebois wrote:
Nicholas Bamber nicho...@periapt.co.uk (03/07/2012):
This is one I raised and people are asking me to upgrade the w3c
stuff which requires fixing it. It probably just requires a
slight application of xargs, but the XML world in Debian is
pretty dead and quite a lot is going on already and XML is not my
top focus. So altogether I would rather look at this once I am
sure it is no going into wheezy. Please advise.
From a quick look at it, one could think of: - either improving
debhelper's autoscript() so that it detects a sed line which would
be too long and deal with it. - or switch {ADD,DEL}_{PACKAGE_ROOT}
from scalars to lists, and iterate over the contents manually,
without invoking autoscript().
(The latter is about dh_installxmlcatalogs, looks more fragile,
and is probably more work than improving debhelper once and for
all.)
Cc-ing debhelper maintainer(s) accordingly.
IOW, replying to the original request: I'm pretty sure it's
fixable before the wheezy release, doesn't look like a bug that
should be wheezy-ignored.
Mraw, KiBi.
Cyril,
Sorry I did not look in more detail at this earlier. Tristan Hill
s...@saticed.me.uk suggested another plausible solution - writing
the sed insructions to a temporary file and passing the file to sed
via the -f argument.
Anyway it definitely looks to me like the bug should be fixed in
debhelper rather than xml-core. So I am reassigning it.
Since this prevents upgrading at least one package I would stick by
the severity, but unless you're willing to let upgrades for
w3c-sgml-lib and w3c-markup-validator through I am not aware of any
rush to fix it. That's why I thought a wheezy-ignore tag was
appropriate.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP+z1eAAoJELbE2bY7/+c8OqYQAMfklMjARPRS7+ZfmdFlorCm
N14b7zE85XMYCTx+8sN4foDxCYtt/0XffM2Ma+BOlRQH/4EaMo5ky8D+3huvy1EU
zrkyqM3xEi//MixpodYzpdUHI4+9ZV/+OpKpWhZtwSkhGb+iH0EKO6AVU36T+Mak
L7j35cVfDngAM3WVreE/PaGy2BBkx12dP/k5UhO+wdzwc5mETRN24giBNHy//6iP
M/TssuWqvYaoViGvcrVxHvLOd+jIDIN/YrLemwrPmEKv/nsZl96ateij+1ZseSdX
UqFT/g6IrPdoAlJs40Z9fso/z8FpUOtzdu4OYw72Y/niSCdWAVOG+C8l6/xJuqnG
AXUNJdVeZu/f40H9DA3brJ3XA2qvXrobTIKRPq9NCk0EEwQXAIFXxKgw0SVAgFOi
sJkFPf2NAAieADYrpxMZ7MLnYBvQpsJH9vYskAF+7eQEm3Rx0rY/O2BsGhRnb3ec
D+FQzvQc7akdg1uTlYUlDj93MbKLvahBOaUm3XAVdK6iW4cbp2p1v1HA1gT9CpHP
iTzvREp0kOA0fUocwgidA8/NoYzNHedKhk3XEz9RGI4Lp5UJgaph35W5BYGf+F4a
JAlTr7uIQBhHclqkOdA8DrwmrvCD9bcHqcrLt2N1mL4Bgva1pSJBcmif2lo5jbq8
sD8wT0LfmPzRbZtIpVCA
=qkYd
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665296: Please consider tagging wheezy-ignore #665296
This is one I raised and people are asking me to upgrade the w3c stuff which requires fixing it. It probably just requires a slight application of xargs, but the XML world in Debian is pretty dead and quite a lot is going on already and XML is not my top focus. So altogether I would rather look at this once I am sure it is no going into wheezy. Please advise. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673541: mysql-5.5
Peter, So yes the file is distributable. Can we close the bug then? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677328: surely this should be wheezy-ignore
The broken packages have been removed from arm* testing. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675005: RC bugs
Zak, I see you have three RC bugs and at least one upload prepared. Would you like my sponsorship for the three RC bugs? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679437: brewtarget
tags 679350 +moreinfo +unreproducible thanks I cannot reproduce the crash but there is a patch if someone can. Else can this bug be downgraded to important. I was thinking of raising an NMU but I'm not sure if I feel comfortable for just one bug. And of course I have copied the maintainer. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#679350: brewtarget
Brian, I tried to reproduce this but failed. Could you send an strace or core dump? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677328: rmysql
Dirk, Given the approaching freeze do you think we could raise a ticket to have rmysql removed on arm*? Or do you think you can get it fixed in the next day or two? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650060: NMU
Javier, I have just uploaded a 2-day NMU based upon Gregor's patch to fix the snort FTBS. It it works Gregor is owed any credit. If it causes an issues send the blame my way. And of course you still have two days to intervene. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650060: NMU
On 22/06/12 22:43, Javier Fernandez-Sanguino wrote: Thanks for the NMU, I did not have time this week to make an upload myself. Regards Javier PS: If I have time I might make an upload soon with the same changes, in order to acknowledge the NMU Javier, I could actually bring the NMU forward if you're happy with it. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650060: NMU
On 22/06/12 23:05, Nicholas Bamber wrote: On 22/06/12 22:43, Javier Fernandez-Sanguino wrote: Thanks for the NMU, I did not have time this week to make an upload myself. Regards Javier PS: If I have time I might make an upload soon with the same changes, in order to acknowledge the NMU Javier, I could actually bring the NMU forward if you're happy with it. Actually at the request of the release team, I have dusted off the magic text book, drawn the appropriate diagram in chalk on the office floor and attempted to get the dcut command correct without accidentally summoning Cthuhlu. Still waiting to see if I succeeded. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675836: suggested fix
On 20/06/12 22:50, Steven Chamberlain wrote: You still didn't address that in your reply. Steven, You seem to have three issues: 1.) feature based tests rather than platform based tests. I totally get the desirability of this. It means new OS 's or improvements to OS's get picked up automatically. My issue was that this does not work in *this* case. Furthermore I was ignorant of certain specifics - which is why I was widely circulating the NMU - and so improperly cautious. 2.) a proper audit trail and making Hurd accountable for the actual issue Again I totally get this. 3.) You seem to see it fit to willfully cause an FTBS on Hurd, to make a point. I don't get that. Any point you might make would be lost in all the other Hurd FTBS's. Surely it is much better to do something positive. So I have raised a bug: #678358 to address the underlying issue. I will clone this bug to a follow up bug blocked by #678358. I will check the source code of the other packages that I am aware might have this issue and do the same if I find anything. I will not delay any more with this NMU and my proposed patch will * use #if defined(AF_LINK) !defined(__GNU__) in both places as that is as close to a feature check as we can get * Have a comment explaining the issues in both the code and the patch header. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675836: suggested fix
On 21/06/12 11:14, Steven Chamberlain wrote:
On 21/06/12 08:57, Nicholas Bamber wrote:
3.) You seem to see it fit to willfully cause an FTBS on Hurd, to make a
point.
To willfully allow an existing FTBFS on GNU/Hurd, to become a more
explanatory FTBFS, which would someday go away and keep the intended
functionality once the cause had been resolved in its build-deps.
So I have raised a bug: #678358 to address the underlying issue.
Yes that was the nice thing to do here, thanks.
* use #if defined(AF_LINK) !defined(__GNU__) in both places as that
is as close to a feature check as we can get
I'm fine with that, as it would be consistent, and it addresses the most
important point which was the original test for (k)FreeBSD being too
specific.
Regards,
Jamie,
I have uploaded an NMU with a 2-day delay. The final diff is attached.
Given such a long and protracted discussion I hope you appreciate the
fix and incorporate it into your code as soon as possible. But of course
if you have an issue with it you can still intervene.
diff -Nru pmacct-0.14.0/debian/changelog pmacct-0.14.0/debian/changelog
--- pmacct-0.14.0/debian/changelog 2012-05-24 08:11:21.0 +0100
+++ pmacct-0.14.0/debian/changelog 2012-06-21 12:39:45.0 +0100
@@ -1,3 +1,11 @@
+pmacct (0.14.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Added patch to handle AF_LINK on hurd and kfreebsd
+platforms (Closes: #675836)
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Thu, 21 Jun 2012 12:39:40 +0100
+
pmacct (0.14.0-1) unstable; urgency=low
* New upstream release
diff -Nru pmacct-0.14.0/debian/control pmacct-0.14.0/debian/control
--- pmacct-0.14.0/debian/control2012-02-10 02:33:51.0 +
+++ pmacct-0.14.0/debian/control2012-06-21 11:43:56.0 +0100
@@ -2,7 +2,7 @@
Section: net
Priority: optional
Maintainer: Jamie Wilkinson j...@debian.org
-Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev
+Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev, kfreebsd-kernel-headers[kfreebsd-any]
Standards-Version: 3.8.3
Package: pmacct
diff -Nru pmacct-0.14.0/debian/patches/af_link.patch
pmacct-0.14.0/debian/patches/af_link.patch
--- pmacct-0.14.0/debian/patches/af_link.patch 1970-01-01 01:00:00.0
+0100
+++ pmacct-0.14.0/debian/patches/af_link.patch 2012-06-21 11:54:28.0
+0100
@@ -0,0 +1,32 @@
+Author: Nicholas Bamber nicho...@periapt.co.uk
+Subject: Problems with the sockaddr_dl structure
+ The first issue is that on kfreebsd platforms,
+ where AF_LINK is legitimately defined, the definition
+ of sockaddr_dl is in net/if_dl.h which the upstream source
+ does not #include. The second issue is that Hurd also
+ defines AF_LINK but does not actually implement
+ that functionality - #678358. Bug #678375 was raised
+ to clear this up when it is sorted out in Hurd.
+Bug-Debian: http://bugs.debian.org/675836
+Last-Update: 2012-06-21
+--- a/src/isis/sockunion.c
b/src/isis/sockunion.c
+@@ -27,6 +27,18 @@
+ #include prefix.h
+ #include sockunion.h
+
++/* As per #678358, Hurd defines AF_LINK but does not
++ * provide the functionality. When that bug is fixed
++ * These three lines could be removed and #678375 closed.
++ */
++#ifdef __GNU__
++#undef AF_LINK
++#endif
++
++#ifdef AF_LINK
++#include net/if_dl.h
++#endif
++
+ const char *
+ inet_sutop (union sockunion *su, char *str)
+ {
diff -Nru pmacct-0.14.0/debian/patches/series
pmacct-0.14.0/debian/patches/series
--- pmacct-0.14.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ pmacct-0.14.0/debian/patches/series 2012-06-21 11:31:02.0 +0100
@@ -0,0 +1 @@
+af_link.patch
Bug#677114: #debian-science
Conversation regarding this. 10:05:58) periapt: Hi (10:06:50) periapt: sylvestre_: #677114 ? (10:09:30) sylvestre_: it is on my todolist (10:13:07) periapt: sylvestre_: Excellent. Do I take it you have not had a chance to look at yet? (10:14:04) sylvestre_: I don't understand your question (10:19:38) periapt: sylvestre_: Sorry. I am groping for the politest way of getting an idea where we are on it. (10:40:56) sylvestre_: ok :) (10:41:00) sylvestre_: Not far for now (10:43:59) sylvestre_: I will probably disable the arch (10:44:08) sylvestre_: It is likely to be a problem in Scilab itself (10:54:46) periapt: sylvestre_: Thanks. That's very helpful. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675836: suggested fix
Jamie,
I have a proposed fix as attached. It's built, signed and ready to go.
If you have intentions to fix it yourself please reply and do so
promptly. I'll run my fix past a few people for feedback but after that
I'll upload with a 2-day delay.
diff -Nru pmacct-0.14.0/debian/changelog pmacct-0.14.0/debian/changelog
--- pmacct-0.14.0/debian/changelog 2012-06-20 11:15:49.0 +0100
+++ pmacct-0.14.0/debian/changelog 2012-05-24 08:11:21.0 +0100
@@ -1,10 +1,3 @@
-pmacct (0.14.0-1.1) unstable; urgency=low
-
- * Non-maintainer upload.
- * Added special include of net/if_dl.h on kfreebsd (Closes: #675836)
-
- -- Nicholas Bamber nicho...@periapt.co.uk Wed, 20 Jun 2012 11:15:42 +0100
-
pmacct (0.14.0-1) unstable; urgency=low
* New upstream release
diff -Nru pmacct-0.14.0/debian/control pmacct-0.14.0/debian/control
--- pmacct-0.14.0/debian/control2012-06-20 10:37:48.0 +0100
+++ pmacct-0.14.0/debian/control2012-02-10 02:33:51.0 +
@@ -2,8 +2,7 @@
Section: net
Priority: optional
Maintainer: Jamie Wilkinson j...@debian.org
-Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev,
- kfreebsd-kernel-headers[kfreebsd-any]
+Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev
Standards-Version: 3.8.3
Package: pmacct
diff -Nru pmacct-0.14.0/debian/patches/kfreebsd.patch
pmacct-0.14.0/debian/patches/kfreebsd.patch
--- pmacct-0.14.0/debian/patches/kfreebsd.patch 2012-06-20 11:15:27.0
+0100
+++ pmacct-0.14.0/debian/patches/kfreebsd.patch 1970-01-01 01:00:00.0
+0100
@@ -1,17 +0,0 @@
-Author: Nicholas Bamber nicho...@periapt.co.uk
-Subject: FTBS on kfreebsd
-Last-Update: 2012-06-20
-Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675836
a/src/isis/sockunion.c
-+++ b/src/isis/sockunion.c
-@@ -27,6 +27,10 @@
- #include prefix.h
- #include sockunion.h
-
-+#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
-+#include net/if_dl.h
-+#endif
-+
- const char *
- inet_sutop (union sockunion *su, char *str)
- {
diff -Nru pmacct-0.14.0/debian/patches/series
pmacct-0.14.0/debian/patches/series
--- pmacct-0.14.0/debian/patches/series 2012-06-20 10:44:37.0 +0100
+++ pmacct-0.14.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-kfreebsd.patch
Bug#675836: suggested fix
On 20/06/12 11:56, Nicholas Bamber wrote:
Jamie,
I have a proposed fix as attached. It's built, signed and ready to go.
If you have intentions to fix it yourself please reply and do so
promptly. I'll run my fix past a few people for feedback but after that
I'll upload with a 2-day delay.
Hmm, it seems I got the debdiff the wrong way round. Resent.
diff -Nru pmacct-0.14.0/debian/changelog pmacct-0.14.0/debian/changelog
--- pmacct-0.14.0/debian/changelog 2012-05-24 08:11:21.0 +0100
+++ pmacct-0.14.0/debian/changelog 2012-06-20 11:15:49.0 +0100
@@ -1,3 +1,10 @@
+pmacct (0.14.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Added special include of net/if_dl.h on kfreebsd (Closes: #675836)
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Wed, 20 Jun 2012 11:15:42 +0100
+
pmacct (0.14.0-1) unstable; urgency=low
* New upstream release
diff -Nru pmacct-0.14.0/debian/control pmacct-0.14.0/debian/control
--- pmacct-0.14.0/debian/control2012-02-10 02:33:51.0 +
+++ pmacct-0.14.0/debian/control2012-06-20 10:37:48.0 +0100
@@ -2,7 +2,8 @@
Section: net
Priority: optional
Maintainer: Jamie Wilkinson j...@debian.org
-Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev
+Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev,
+ kfreebsd-kernel-headers[kfreebsd-any]
Standards-Version: 3.8.3
Package: pmacct
diff -Nru pmacct-0.14.0/debian/patches/kfreebsd.patch
pmacct-0.14.0/debian/patches/kfreebsd.patch
--- pmacct-0.14.0/debian/patches/kfreebsd.patch 1970-01-01 01:00:00.0
+0100
+++ pmacct-0.14.0/debian/patches/kfreebsd.patch 2012-06-20 11:15:27.0
+0100
@@ -0,0 +1,17 @@
+Author: Nicholas Bamber nicho...@periapt.co.uk
+Subject: FTBS on kfreebsd
+Last-Update: 2012-06-20
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675836
+--- a/src/isis/sockunion.c
b/src/isis/sockunion.c
+@@ -27,6 +27,10 @@
+ #include prefix.h
+ #include sockunion.h
+
++#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
++#include net/if_dl.h
++#endif
++
+ const char *
+ inet_sutop (union sockunion *su, char *str)
+ {
diff -Nru pmacct-0.14.0/debian/patches/series
pmacct-0.14.0/debian/patches/series
--- pmacct-0.14.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ pmacct-0.14.0/debian/patches/series 2012-06-20 10:44:37.0 +0100
@@ -0,0 +1 @@
+kfreebsd.patch
Bug#675836: suggested fix
On 20/06/12 12:27, Steven Chamberlain wrote: On 20/06/12 11:56, Nicholas Bamber wrote: I have a proposed fix as attached. It's built, signed and ready to go. If you have intentions to fix it yourself please reply and do so promptly. I'll run my fix past a few people for feedback but after that I'll upload with a 2-day delay. Thanks for this. It looks okay and seems it would fix the FTBFS. However... I'm wondering if a more generic test could be used instead of FreeBSD || FreeBSD_kernel. Other BSD's would need this header too for the sockaddr_dl definition[1]. And it looks like GNU/Hurd was failing on this same code so it possibly has (or should have) the same. [1] http://fxr.watson.org/fxr/trackident?v=FREEBSD9;i=sockaddr_dl [2] https://buildd.debian.org/status/fetch.php?pkg=pmacctarch=hurd-i386ver=0.14.0-1stamp=1339115492 What about using AF_LINK as a test of whether to include this header? It looks to me like it would work. This way we'd be helping out GNU/Hurd at the same time, the fix would be more appropriate for upstream and it helps with future portability. Thanks again, Regards, Steven, Sorry I didn't notice the FTBS on hurd as I was concentrating on the red. I guess I should have trusted the bug report title more. However I am confused at what your are proposing. For a start I cannot find a net/if_dl.h file on Hurd. Secondly I am not clear if using AF_LINK as a conditional is a good idea. Surely that would change the code on Linux, which is surely not what we want to do. Also googling for Hurd and sockaddr_dl has not so far turned up anything useful. What bugs such as #636510 and #256669 do suggest is that AF_LINK is a bad indicator of the presence of sockaddr_dl. Maybe the solution is to furher guard the #ifdef AF_LINK bits by requiring that the OS not be Hurd. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675836: suggested fix
Jamie,
Based upon the feedback I have received (including #debian-hurd) I am
attaching a new debdiff. Unless I get any more feedback I'll probably
upload it tomorrow with a 2-day delay.
diff -Nru pmacct-0.14.0/debian/changelog pmacct-0.14.0/debian/changelog
--- pmacct-0.14.0/debian/changelog 2012-05-24 08:11:21.0 +0100
+++ pmacct-0.14.0/debian/changelog 2012-06-20 14:29:08.0 +0100
@@ -1,3 +1,11 @@
+pmacct (0.14.0-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Added special include of net/if_dl.h on kfreebsd
+and disabled AF_LINK support on Hurd (Closes: #675836)
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Wed, 20 Jun 2012 11:15:42 +0100
+
pmacct (0.14.0-1) unstable; urgency=low
* New upstream release
diff -Nru pmacct-0.14.0/debian/control pmacct-0.14.0/debian/control
--- pmacct-0.14.0/debian/control2012-02-10 02:33:51.0 +
+++ pmacct-0.14.0/debian/control2012-06-20 10:37:48.0 +0100
@@ -2,7 +2,8 @@
Section: net
Priority: optional
Maintainer: Jamie Wilkinson j...@debian.org
-Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev
+Build-Depends: debhelper (= 7), zlib1g-dev, libpcap-dev, libpq-dev,
libmysqlclient-dev, libsqlite3-dev,
+ kfreebsd-kernel-headers[kfreebsd-any]
Standards-Version: 3.8.3
Package: pmacct
diff -Nru pmacct-0.14.0/debian/patches/kfreebsd.patch
pmacct-0.14.0/debian/patches/kfreebsd.patch
--- pmacct-0.14.0/debian/patches/kfreebsd.patch 1970-01-01 01:00:00.0
+0100
+++ pmacct-0.14.0/debian/patches/kfreebsd.patch 2012-06-20 14:34:08.0
+0100
@@ -0,0 +1,26 @@
+Author: Nicholas Bamber nicho...@periapt.co.uk
+Subject: FTBS on kfreebsd
+Last-Update: 2012-06-20
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675836
+--- a/src/isis/sockunion.c
b/src/isis/sockunion.c
+@@ -27,6 +27,10 @@
+ #include prefix.h
+ #include sockunion.h
+
++#if defined(__FreeBSD__) || defined(__FreeBSD_kernel__)
++#include net/if_dl.h
++#endif
++
+ const char *
+ inet_sutop (union sockunion *su, char *str)
+ {
+@@ -619,7 +623,7 @@
+ break;
+ #endif /* ENABLE_IPV6 */
+
+-#ifdef AF_LINK
++#if defined(AF_LINK) !defined(__GNU__)
+ case AF_LINK:
+ {
+ struct sockaddr_dl *sdl;
diff -Nru pmacct-0.14.0/debian/patches/series
pmacct-0.14.0/debian/patches/series
--- pmacct-0.14.0/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ pmacct-0.14.0/debian/patches/series 2012-06-20 10:44:37.0 +0100
@@ -0,0 +1 @@
+kfreebsd.patch
Bug#675836: suggested fix
On 20/06/12 22:04, Steven Chamberlain wrote: On 20/06/12 15:59, Nicholas Bamber wrote: Based upon the feedback I have received (including #debian-hurd) I am attaching a new debdiff. This debdiff doesn't address the main point of my original mail: sockaddr_dl and net/if_dl.h are not (k)FreeBSD-specific, so a test for FreeBSD || FreeBSD_kernel would not be appropriate. It might work but would only replace one portability issue with another. The new test for AF_LINK !GNU looks even worse to me. Does GNU/Hurd _really_ define AF_LINK and yet not provide a net/if_dl.h with a definition for sockaddr_dl? Regards, Steven, As I understood it you wanted the build to fail on Hurd so everyone would know there was an AF_LINK/sockaddr_dl bug on Hurd. I am not convinced that that is the right tack to take. I discussed the more general AF_LINK/sockaddr_dl issue with Pino today, and he's going to follow up on. But for now I'm just trying to get this package to build in a sane - if not ideal - way. I'm still open to arguments of course especially from the maintainer. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609537: reassigning
retitle 677222 log_slow_queries deprecated reassign 609537 mysql-server severity important tag 609537 +patch thanks Are/Marko, I am sorry that this has not been fixed (or even really looked at). I see no reason why it should have been magically fixed in the migration to 5.5 and 5.1 is going away so I am reassigning it. I am downgrading the severity to important because really the risks of looking at outway the potential benefits this close to the freeze. We do however have a plan. We're a going get mysql working with piuparts and then have a good hard look at all of the init and maintenance scripts. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676817: systemd and dovecot
Jaldhar, We really need to get dovecot compiled on the non-linux platforms to progress with the mysql migration. The systemd dependency puzzles me somewhat as systemd is not available on non-linux platforms and dovecot has previously compiled on those platforms. So at the very least the systemd dependency should be systemd[linux]. Also it would surely be prudent if the --with-systemdsystemunitdir=auto \ argument to configure were only set on linux platforms. However, whilst I don't know anything about systemd, this still looks like a little broken. I am puzzled that the dependency is on systemd and not libsystemd-daemon-dev. After all the libsystemd-daemon-dev package contains the /usr/include/systemd/sd-daemon.h file which is included by some dovecot source files. I could raise an NMU to fix these issues but some advice from the systemd people would be appreciated. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676817: systemd and dovecot
On 17/06/12 07:58, Nicholas Bamber wrote: Jaldhar, We really need to get dovecot compiled on the non-linux platforms to progress with the mysql migration. The systemd dependency puzzles me somewhat as systemd is not available on non-linux platforms and dovecot has previously compiled on those platforms. So at the very least the systemd dependency should be systemd[linux]. Also it would surely be prudent if the --with-systemdsystemunitdir=auto \ argument to configure were only set on linux platforms. However, whilst I don't know anything about systemd, this still looks like a little broken. I am puzzled that the dependency is on systemd and not libsystemd-daemon-dev. After all the libsystemd-daemon-dev package contains the /usr/include/systemd/sd-daemon.h file which is included by some dovecot source files. I could raise an NMU to fix these issues but some advice from the systemd people would be appreciated. Oh I should not have implied that it previously compiled on Hurd. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676817: systemd and dovecot
Tollef, Thanks for the response. What about the libsystemd-daemon-dev package? Is that required (on Linux)? On 17/06/12 09:02, Tollef Fog Heen wrote: ]] Nicholas Bamber However, whilst I don't know anything about systemd, this still looks like a little broken. I am puzzled that the dependency is on systemd and not libsystemd-daemon-dev. After all the libsystemd-daemon-dev package contains the /usr/include/systemd/sd-daemon.h file which is included by some dovecot source files. It might be for the systemd.pc file, which is shipped in systemd itself. The reason for this is I don't see a point in having a systemd-dev package that only contains this file, when installing systemd doesn't actually hurt or change your system any more than any other random non-daemon package. I think it's fairly obvious this build-dependency only makes sense on Linux, yes. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676817: systemd and dovecot
Tollef, I would be very grateful if you could have a look. Andreas Barth has basically repeated the point I made in the third paragraph of my original post. Nothing you have said is really reassuring me. You talk about how a package needs something to make socket activation to work and sd-daemon.h is a way to do that. Well that file is available in libsystemd-daemon-dev, and the current package as a dependency on systemd rather than libsystemd-daemon-dev. It might be right but it does not feel right. On 17/06/12 09:52, Tollef Fog Heen wrote: ]] Nicholas Bamber Tollef, Thanks for the response. What about the libsystemd-daemon-dev package? Is that required (on Linux)? I don't know in detail why dovecot build-deps on systemd, but I believe it's for the socket activation. It can either include sd-daemon.[ch] in the source tree, in which case no build-dependency is needed, or it can use the files from the systemd tree, in which case the dependency is needed. I don't know which of those solutions dovecot has chosen. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676817: systemd and dovecot
Tollef, Thanks for your responses. Based upon them I wail upload an NMU with a 2 day delay doing nothing more than limiting the systemd changes to linux. I would not normally feel comfortable with such a short delay but in this case ny proposed changes should be self-evident and uncontroversial. On 17/06/12 11:26, Tollef Fog Heen wrote: ]] Nicholas Bamber Hi, I would be most grateful if you quoted the way is usually done on email lists. I would be very grateful if you could have a look. Andreas Barth has basically repeated the point I made in the third paragraph of my original post. Yes, and you're both mistaken. systemd is not a normal daemon package, it does not start any daemons, nor replace init merely by being installed. Installing systemd onto a system is about as intrusive to the system as a whole as installing nvi. Nothing you have said is really reassuring me. You talk about how a package needs something to make socket activation to work and sd-daemon.h is a way to do that. Well that file is available in libsystemd-daemon-dev, and the current package as a dependency on systemd rather than libsystemd-daemon-dev. It might be right but it does not feel right. I would suggest you ask the dovecot maintainer why he build-depends on systemd rather than libsystemd-daemon-dev if it is in fact for the reasons I listed. I gave a suggestion as to why he would do so, as well as a reason for why systemd.pc is not in its own package, but as I am not the maintainer of dovecot and there's no way for me to actually know, short of asking, which you can just as easily do yourself. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676817: systemd and dovecot
Jaldhar assures me he is working on an upload so obviously I'm not. However I got quite far double checking a few builds (attached diff) and I found that there seems to be an issue with sqlite3. I had better investigate that. checking for sqlite3_open in -lsqlite3... yes checking sqlite3.h usability... no checking sqlite3.h presence... yes configure: WARNING: sqlite3.h: present but cannot be compiled configure: WARNING: sqlite3.h: check for missing prerequisite headers? configure: WARNING: sqlite3.h: see the Autoconf documentation configure: WARNING: sqlite3.h: section Present But Cannot Be Compiled configure: WARNING: sqlite3.h: proceeding with the compiler's result configure: WARNING: ## -- ## configure: WARNING: ## Report this to dove...@dovecot.org ## configure: WARNING: ## -- ## checking for sqlite3.h... no configure: error: Can't build with SQLite support: sqlite3.h not found make: *** [config-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package I: unmounting /var/cache/pbuilder/ccache filesystem I: unmounting dev filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /var/cache/pbuilder/build//13737 and its subdirectories On 17/06/12 12:15, Nicholas Bamber wrote: Tollef, Thanks for your responses. Based upon them I wail upload an NMU with a 2 day delay doing nothing more than limiting the systemd changes to linux. I would not normally feel comfortable with such a short delay but in this case ny proposed changes should be self-evident and uncontroversial. On 17/06/12 11:26, Tollef Fog Heen wrote: ]] Nicholas Bamber Hi, I would be most grateful if you quoted the way is usually done on email lists. I would be very grateful if you could have a look. Andreas Barth has basically repeated the point I made in the third paragraph of my original post. Yes, and you're both mistaken. systemd is not a normal daemon package, it does not start any daemons, nor replace init merely by being installed. Installing systemd onto a system is about as intrusive to the system as a whole as installing nvi. Nothing you have said is really reassuring me. You talk about how a package needs something to make socket activation to work and sd-daemon.h is a way to do that. Well that file is available in libsystemd-daemon-dev, and the current package as a dependency on systemd rather than libsystemd-daemon-dev. It might be right but it does not feel right. I would suggest you ask the dovecot maintainer why he build-depends on systemd rather than libsystemd-daemon-dev if it is in fact for the reasons I listed. I gave a suggestion as to why he would do so, as well as a reason for why systemd.pc is not in its own package, but as I am not the maintainer of dovecot and there's no way for me to actually know, short of asking, which you can just as easily do yourself. diff -Nru dovecot-2.1.7/debian/changelog dovecot-2.1.7/debian/changelog --- dovecot-2.1.7/debian/changelog 2012-05-30 21:29:05.0 +0100 +++ dovecot-2.1.7/debian/changelog 2012-06-17 12:17:55.0 +0100 @@ -1,3 +1,10 @@ +dovecot (1:2.1.7-1.1) UNRELEASED; urgency=low + + * Non-maintainer upload. + * Restrict systemd canges to linux (Closes: #676817) + + -- Nicholas Bamber nicholas@chilcott.periapt Sun, 17 Jun 2012 12:16:22 +0100 + dovecot (1:2.1.7-1) unstable; urgency=low * [7668742] Imported upstream 2.1.7 (Closes: #663243) diff -Nru dovecot-2.1.7/debian/control dovecot-2.1.7/debian/control --- dovecot-2.1.7/debian/control 2012-05-30 21:29:05.0 +0100 +++ dovecot-2.1.7/debian/control 2012-06-17 13:52:48.0 +0100 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Dovecot Maintainers jaldhar-dove...@debian.org Uploaders: Jaldhar H. Vyas jald...@debian.org, Fabio Tranchitella kob...@debian.org, Joel Johnson mrj...@lixil.net, Marco Nenciarini mnen...@debian.org -Build-Depends: debhelper (= 7.2.3~), dpkg-dev (= 1.16.1), pkg-config, libssl-dev, libpam0g-dev, libldap2-dev, libpq-dev, libmysqlclient-dev, libsqlite3-dev, libsasl2-dev, zlib1g-dev, libkrb5-dev, drac-dev (= 1.12-5), libbz2-dev, libdb-dev, libcurl4-gnutls-dev, libexpat-dev, systemd +Build-Depends: debhelper (= 7.2.3~), dpkg-dev (= 1.16.1), pkg-config, libssl-dev, libpam0g-dev, libldap2-dev, libpq-dev, libmysqlclient-dev, libsqlite3-dev, libsasl2-dev, zlib1g-dev, libkrb5-dev, drac-dev (= 1.12-5), libbz2-dev, libdb-dev, libcurl4-gnutls-dev, libexpat-dev, systemd[linux-any] Standards-Version: 3.9.3 Homepage: http://dovecot.org/ Vcs-Git: git://git.debian.org/git/collab-maint/dovecot.git diff -Nru dovecot-2.1.7/debian/rules dovecot-2.1.7/debian/rules --- dovecot-2.1.7/debian/rules 2012-05-30 21:29:05.0 +0100 +++ dovecot-2.1.7/debian/rules 2012-06-17 12:40:55.0 +0100 @@ -11,6 +11,11 @@ # from having
Bug#677057: [debian-mysql] Bug#677057: mysql-client-5.1: uninstallable because mysql-common Breaks: mysql-client-5.1 ( 5.5)
I suppose I had better look at that. On 16/06/12 20:20, Julien Cristau wrote: On Sat, Jun 16, 2012 at 21:14:33 +0200, Andreas Beckmann wrote: On 2012-06-11 13:48, Julien Cristau wrote: during a test with piuparts I noticed your package is no longer installable: Not a bug, and expected. mysql-5.1 is going away. Is there a chance to get the mysql-*-5.1 packages removed manually while the old libmysqlclient* remains to complete the mysql transition? You can upload a new mysql-5.1 source that only builds the lib if you want. 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677328: FTBS on armel,armhf
Package: rmysql Version: 0.9-3-1+b1 Severity: serious The binNMUs against mysql-5.5 failed on armel,armhf. I will reply later with URLs to the build logs. -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677328: [b-d][abel] rmysql (sid)
Peter, I get a slightly different error from the build daemons and it looks like some build dependencies are missing. Please could you install xauth in the same chroot. On 13/06/12 11:05, Peter Palfrader wrote: . On Wed, 13 Jun 2012, Nicholas Bamber wrote: block 671115 by 677328 thanks The affected build logs are https://buildd.debian.org/status/fetch.php?pkg=rmysqlarch=armelver=0.9-3-1%2Bb1stamp=1339297682 and https://buildd.debian.org/status/fetch.php?pkg=rmysqlarch=armhfver=0.9-3-1%2Bb1stamp=1339280141 . -- To unsubscribe, contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677328: [b-d][abel] rmysql (sid)
Dirk, I really have no idea. I cannot reproduce the failures seen in the build logs. Instead I got the xauth failure. I would try building in the sid chroot on abel and see what you find. And as far as I can see xauth cannot possibly explain the errors in the build logs. On 13/06/12 20:36, Dirk Eddelbuettel wrote: On 13 June 2012 at 11:14, Nicholas Bamber wrote: | Peter, | I get a slightly different error from the build daemons and it looks | like some build dependencies are missing. Please could you install xauth | in the same chroot. I still have various r-cran-* packages failing on armel and armhf -- and they all build everywhere else. Are you saying that xauth may be at the cause of this? Dirk | On 13/06/12 11:05, Peter Palfrader wrote: | . | | On Wed, 13 Jun 2012, Nicholas Bamber wrote: | | block 671115 by 677328 | thanks | | The affected build logs are | https://buildd.debian.org/status/fetch.php?pkg=rmysqlarch=armelver=0.9-3-1%2Bb1stamp=1339297682 | and | https://buildd.debian.org/status/fetch.php?pkg=rmysqlarch=armhfver=0.9-3-1%2Bb1stamp=1339280141 | . | | | -- | To unsubscribe, contact listmas...@lists.debian.org | | | | | -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677018: [debian-mysql] Bug#677018: Bug#677018: more information
Thijs, No we are planning to remove 5.1 before wheezy is released. I just fear the timescale is not soon enough. On 12/06/12 10:02, Thijs Kinkhorst wrote: Hi Nicholas, I seem to recall that this bug is fixed in 5.5.24 which actually is in testing. The migration is not yet complete and probably still has a week or two to go at the least. But does that change your calculations at all. Yes, 5.5 seems fixed in both sid and wheezy. As for 5.1, although our specific builds are not currently vulnerable this can not be guaranteed if they are rebuilt in different circumstances. Will 5.1 be in wheezy or will it be removed soon? If it's going to stay around please upload 5.1.63 a.s.a.p. Cheers, Thijs ___ 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#677199: w3c-dtd-xhtml: please rebuild to fix your copy of #477751
Helmut, I think I should be able to persuade myself to do an upload of this little package. On 01/06/12 14:52, Helmut Grohne wrote: Source: w3c-dtd-xhtml Severity: serious Dear maintainer(s) of w3c-dtd-xhtml, TL;DR: Please upload a new version of this package closing this bug. Problem ~~~ Your package uses the dh_installcatalogs helper from debhelper. This helper added code to the postinst that unconditionally overwrites files in /etc which is a policy violation. The corresponding bug #477751 is now solved in debhelper. Nevertheless the code overwriting files in /etc is still present in a binary package built from this source package, so your package needs a rebuild. Unfortunately the binary package in question is Architecture: all, so a binNMU is not enough. How to solve This bug tracks the progress of the rebuild and should be closed by any upload of this package. Before building, please ensure that your debhelper version is at least 9.20120528 which should be the case if you are running sid. Is my package really/still affected? Any binary package using the dh_installcatalogs helper will add a versioned dependency on sgml-base. If the depended upon version is at least 1.26+nmu2, your package is not affected. In that case, just close this bug. If you have any further questions concerning this issue, please don't hesitate to contact me. Thanks for your help Helmut -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677018: [debian-mysql] Bug#677018: more information
I believe Clint is updating squeeze just to be safe. We will be updating wheezy just to be safe. Most likely both updates would have happened anyway. On 12/06/12 17:10, Henri Salo wrote: On Tue, Jun 12, 2012 at 08:57:28AM +0100, Nicholas Bamber wrote: Henri, I seem to recall that this bug is fixed in 5.5.24 which actually is in testing. The migration is not yet complete and probably still has a week or two to go at the least. But does that change your calculations at all. What do you mean by calculations? Please close the bug if it is handled. At least running the oneliner in Debian squeeze MySQL-server using the client-package squeeze is not affected. - Henri Salo -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677114: scilab-scimysql: FTBS on armhf, mips, powerpc, s390, sparc
Package: scilab-scimysql Version: 0.1.1-3 Severity: serious Justification: Policy 2.1 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? The package was binNMU'ed as part of the mysqlclient transition. Here is a sample log file. https://buildd.debian.org/status/fetch.php?pkg=scilab-scimysqlarch=powerpcver=0.1.1-3%2Bb1stamp=1339264256 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676595: sphinxsearch
I am about to upload on a 5-day delay the attached patch for this bug.
If you would rather fix it yourself you will know what to do.
diff -Nru sphinxsearch-2.0.4/debian/changelog
sphinxsearch-2.0.4/debian/changelog
--- sphinxsearch-2.0.4/debian/changelog 2012-04-20 03:50:21.0 +0100
+++ sphinxsearch-2.0.4/debian/changelog 2012-06-11 21:32:01.0 +0100
@@ -1,3 +1,10 @@
+sphinxsearch (2.0.4-1.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Removed hard-coded dependency on libmysqlclient16 (Closes: #676595)
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Mon, 11 Jun 2012 20:31:53 +
+
sphinxsearch (2.0.4-1) unstable; urgency=low
* New upstream release.
diff -Nru sphinxsearch-2.0.4/debian/control sphinxsearch-2.0.4/debian/control
--- sphinxsearch-2.0.4/debian/control 2012-04-20 03:50:06.0 +0100
+++ sphinxsearch-2.0.4/debian/control 2012-06-11 21:34:39.0 +0100
@@ -7,7 +7,7 @@
Package: sphinxsearch
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libmysqlclient16, adduser
+Depends: ${shlibs:Depends}, ${misc:Depends}, adduser
Description: Fast standalone full-text SQL search engine
Sphinx is a standalone full text search engine, meant to provide fast,
size-efficient and relevant fulltext search functions to other applications.
Bug#673260: muddleftpd FTBS
Joerg,
I have put a 5-day delayed NMU to fix this FTBS. If you want to fix it
yourself you will know what to do. The source diff is attached.
diff -u muddleftpd-1.3.13.1/debian/control muddleftpd-1.3.13.1/debian/control
--- muddleftpd-1.3.13.1/debian/control
+++ muddleftpd-1.3.13.1/debian/control
@@ -3,7 +3,7 @@
Priority: extra
Maintainer: Joerg Jaspert jo...@debian.org
Standards-Version: 3.6.1
-Build-Depends: debhelper (= 4.0.2), libpam0g-dev, texinfo, libcap-dev
[!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libmysqlclient15-dev
+Build-Depends: debhelper (= 4.0.2), libpam0g-dev, texinfo, libcap-dev
[!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386], libmysqlclient-dev, dh-autoreconf
Package: muddleftpd
Provides: ftp-server
diff -u muddleftpd-1.3.13.1/debian/changelog
muddleftpd-1.3.13.1/debian/changelog
--- muddleftpd-1.3.13.1/debian/changelog
+++ muddleftpd-1.3.13.1/debian/changelog
@@ -1,3 +1,11 @@
+muddleftpd (1.3.13.1-4.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Backported changes from Ubuntu to enable rebuild against
+mysql-5.5 (Closes: #673260)
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Sun, 10 Jun 2012 11:18:08 +
+
muddleftpd (1.3.13.1-4.2) unstable; urgency=low
* Non-maintainer upload to solve release goal.
diff -u muddleftpd-1.3.13.1/debian/rules muddleftpd-1.3.13.1/debian/rules
--- muddleftpd-1.3.13.1/debian/rules
+++ muddleftpd-1.3.13.1/debian/rules
@@ -17,12 +17,16 @@
TOPDIR := $(shell pwd)
t = ${TOPDIR}/debian/muddleftpd
+DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
+
configure: configure-stamp
configure-stamp:
dh_testdir
+ dh_autoreconf
CFLAGS='$(CFLAGS)' ./configure --prefix=/usr
--mandir='$${prefix}/share/man' \
- --infodir='$${prefix}/share/info' --with-authsmb --with-authmud
--with-authmysql
+ --infodir='$${prefix}/share/info' --with-authsmb --with-authmud
--with-authmysql \
+ --with-mysql-lib=lib/$(DEB_HOST_MULTIARCH)
touch configure-stamp
build: configure-stamp build-stamp
@@ -37,6 +41,7 @@
rm -f build-stamp configure-stamp
-$(MAKE) distclean
+ dh_autoreconf_clean
dh_clean
install: build
only in patch2:
unchanged:
--- muddleftpd-1.3.13.1.orig/configure.ac
+++ muddleftpd-1.3.13.1/configure.ac
@@ -190,6 +190,10 @@
fi
# MYSQL module
+AC_ARG_WITH(mysql-lib,AC_HELP_STRING([--with-mysql-lib=DIR],[Directory under
prefix to search for mysql libraries]),
+[ mysql_lib=$withval ],
+[ mysql_lib= ])
+
AC_ARG_WITH(authmysql,
AC_HELP_STRING([--with-authmysql=DIR], [creates MySQL authentication
module, optionally specifies the DIR of mysql files]),
[authmysql=$withval],
only in patch2:
unchanged:
--- muddleftpd-1.3.13.1.orig/modules/auth/authlibmysql/configure.ac
+++ muddleftpd-1.3.13.1/modules/auth/authlibmysql/configure.ac
@@ -38,6 +38,10 @@
exit
])
+AC_ARG_WITH(mysql-lib,AC_HELP_STRING([--with-mysql-lib=DIR],[Directory under
prefix to search for mysql libraries]),
+[ mysql_lib=$withval ],
+[ mysql_lib= ])
+
AC_ARG_WITH(authmysql,
AC_HELP_STRING([--with-authmysql=DIR],[Create MySQL authentication module,
optionally specify dir of mysql files]),
[ with_mysql=$withval ],
@@ -79,7 +83,7 @@
fi
else
-for i in lib lib/mysql; do
+for i in $mysql_lib lib lib/mysql; do
str=$MYSQL_DIR/$i/libmysqlclient.*
for j in `echo $str`; do
if test -r $j; then
Bug#676560: [debian-mysql] Bug#676560: mysql-5.5: Serious system breakage as a result of using /run
Roger, It looks like we do create /run. So we have no option but to back out the change. On 08/06/12 15:28, Roger Leigh wrote: severity 676560 critical thanks (It breaks upgrading of the entire system.) On Thu, Jun 07, 2012 at 07:40:29PM +0100, Roger Leigh wrote: You have two options: 1) Revert to using /var/run 2) Add a versioned dependency as described in the above reference This does not include working out how to undo the damage you have caused, if this is safe or possible. You must additionally make sure that you do not provide the /run directory in your package, or create it. Both these actions will break squeeze upgrades. Thanks, Roger -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#676539: [debian-mysql] Bug#676539: mysql-server-5.5: migration from /var/run/mysqld to /run/mysqld incomplete
Greg, As it happens someone else raised the same bug at about the same time. I happened to come across yours first. The issue is fairly obvious if one thinks about it and it should not really have been missed. On 07/06/12 23:22, Greg Alexander wrote: Hi - Thanks for looking into this. The mysql script caused the creation of a new /run from scratch without consideration for the old /var/run, which does not honor the contract specified in: http://wiki.debian.org/ReleaseGoals/RunDirectory There it is specified that /var/run is an alias for /run, but the mysql upgrade process did not cause that result. Sorry, I'm a little snippy. Upgrade compatibility is a minor obsession of mine, and the reason that I use Debian (and look down on most other OSes). I'll delete the sarcastic paragraph and jump straight to the punchline. I am running initscripts-2.87dsf-6 (2009 - quite modern, in fact). The modern mysql packages appear to have an undeclared dependency upon initscripts-2.88dsf-13.3. Or in other words, quoting from that ReleaseGoals/RunDirectory document: Before wheezy, a versioned depends upon initscripts (= 2.88dsf-13.3) will be required to ensure the presence of a functional /run. Since wheezy is not even released yet, and since 17 other packages do still have declared dependencies on initscripts= 2.88dsf-13.3, I assume that is still in effect... Probably you guys just weren't aware that the /run transition is newer than any LSB document, so the lsb-base dependency doesn't do anything for us here. Cheers, - Greg evidence that this is causing a problem. On a standard recent Debian system /var/run will be a symlink to /run. In fact I could not even see Debian On Thu, Jun 07, 2012 at 10:25:10PM +0100, Nicholas Bamber wrote: severity 676539 minor tag 676539 +moreinfo thanks Greg, Thanks for pointing out the incompletenesses in our migration. They will be acted on if substantiated. I am downgrading the severity because I could not see any actual evidence that this is causing a problem. On a standard recent Debian system /var/run will be a symlink to /run. In fact I could not even see any evidence that this is true. What I think happened is that since /etc/mysql/debian.cnf already existed, the mysql-server-5.5 postinst script had no reason to create it afresh. As for the change it may well (or not) be a pointless change but it is recommended by section 9.1.4 of the latest version of the Debian policy. The lintian tool attempts to find and report on violations. As for libdbd-mysql-perl that is a separate package. If it was an issue it would require a separate bug report. I had a look through both the upstream and packaging code and I could not see anywhere where the MySQL socket file location is defaulted or hardcoded. I think it should be picked up from the libmysqlclient18 package (which is part the mysql-5.5 package). However libdbd-mysql-perl has not yet been binNMU'ed so that would be why that is picking up the old location. If you have any more information please let me know. Otherwise can I close the ticket? On 07/06/12 18:10, Greg Alexander wrote: Package: mysql-server-5.5 Version: 5.5.24+dfsg-2 Severity: important Dear Maintainer, Upon upgrading to mysql-server-5.5, I find that /var/run/mysqld has been needlessly renamed to /run/mysqld. Pointless renaming is considered harmful! You forgot to update a few things when you performed this pointless operation. /etc/mysql/debian.cnf continues to reference /var/run/mysqld. The perl DBI package continues to reference /var/run/mysqld. The need to enumerate the innumerable potential dependencies on the mysqld socket location can be ameliorated through the use of symlinks. Add this to the postrm file: ln -s /run/mysqld /var/run/mysqld But in fact, you could have avoided this whole problem in the first place by not pointlessly renaming /var/run to /run. In the future, try not to break things for no reason. We have symlinks for a reason. Any unix admin who needs /var/run to live in a special location can achieve this effect using mount or ln already. There is no need to render every mysql-dependent configuration file suspect to achieve this end. If the person who decided to rename /var/run/mysqld to /run/mysqld should happen to read this thread, I beg you to please consider swearing off future contribution to open source projects. You are simply not cool enough for my club. - Greg -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32.22 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages mysql-server-5.5 depends on: ii adduser3.102 ii debconf [debconf-2.0] 1.5.40 ii libc6 2.13-10 ii libdbi-perl1.621-1 ii libgcc1
Bug#675836: Processed: blocker
Jamie, It simply means that it has not built against the new mysql on all archirectures yet. It does not imply that it is mysql related. On 04/06/12 02:24, Jamie Wilkinson wrote: I don't understand, how is this ftbfs blocking the mysql transition? I can't read your mind; please try to overcommunicate in your bug updates in the future. On 4 June 2012 07:33, Debian Bug Tracking System ow...@bugs.debian.org mailto:ow...@bugs.debian.org wrote: Processing commands for cont...@bugs.debian.org mailto:cont...@bugs.debian.org: block 671115 by 675836 Bug #671115 [release.debian.org http://release.debian.org] transition: mysql-5.5 671115 was blocked by: 674328 673528 667428 673263 650058 660686 674122 649955 651110 674309 672714 650060 666331 672619 672950 672716 673264 651317 674210 673262 640818 672765 661422 673260 673183 673161 649638 668232 673153 672824 672621 672816 672207 672588 671115 was blocking: 672928 Added blocking bug(s) of 671115: 675836 End of message, stopping processing here. Please contact me if you need assistance. -- 671115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671115 Debian Bug Tracking System Contact ow...@bugs.debian.org mailto:ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-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
I had a look at it. It looked like it was going to be pretty had to cherry pick the relevant updates. On 03/06/12 20:33, Arne Wichmann wrote: begin quotation from Moritz Mühlenhoff (in20120416154357.GA4565@pisco.westfalen.local): On Mon, Apr 16, 2012 at 12:43:40AM +0100, Nicholas Bamber wrote: 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. This issue doesn't warrant a DSA. You can fix it through a stable point update instead. So, is there a chance to see a fix to this in a stable point update? cu AW -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660686: versioned symbols
Julien, The patch was not as bad as I thought. 00022340 gDF .text 01b5 libmysqlclient_18 my_connect http://anonscm.debian.org/viewvc/pkg-mysql/mysql-5.5/branches/unstable/debian/patches/versioned_symbols.patch?view=markup http://anonscm.debian.org/viewvc/pkg-mysql/mysql-5.5/branches/unstable/debian/rules?r1=2127r2=2131 http://anonscm.debian.org/viewvc/pkg-mysql/mysql-5.5/branches/unstable/debian/changelog?r1=2128r2=2131 But I still need to port this into what we have for wheezy/testing/sid and it looks like I need some more tweaks for #672359 and possibly a Break against amarok ( 2.5.0-2). -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675304: reassigning
reassign 675304 amarok thanks I am much clearer about this now. This bug is clearly a duplicate of #672207. That said I think we could have instead of changing language= /usr/share/mysql/english to lc-messages-dir = /usr/share/mysql changed it to loose-lc-messages-dir = /usr/share/mysql/ # This option is deprecated and will be removed in a later version language= /usr/share/mysql/english This would have maintained backwards compatibility and removed the need for the Breaks clauses. However it is also clear that an application with an embedded MySQL server, like amarok, should avoiding making use of system wide MySQL config files to insulate itself not just to changes in the Debian packaging but also changes that the DBA makes to the MySQL configuration. amarok seems to have done this now. I am trying to draw wider lessons from this, but for now I am reassigning this report to amarok, with the expectation that one of more of the following will happen: 1.) The bug will be merged into #672207 effectively closing it. 2.) That it will be reassigned to a request to have amarok aged so that the user can upgrade his amarok. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675304: [debian-mysql] reassigning
Clint, See http://dev.mysql.com/doc/refman/5.5/en/option-modifiers.html and search for --loose. On 01/06/12 22:50, Clint Byrum wrote: Excerpts from Nicholas Bamber's message of 2012-06-01 02:17:01 -0700: reassign 675304 amarok thanks I am much clearer about this now. This bug is clearly a duplicate of #672207. That said I think we could have instead of changing language= /usr/share/mysql/english to lc-messages-dir = /usr/share/mysql changed it to loose-lc-messages-dir = /usr/share/mysql/ # This option is deprecated and will be removed in a later version language= /usr/share/mysql/english I'm not sure how this is going to work. loose-lc-messages-dir is still going to be unrecognized by any 5.1 based mysqld. Unless this is some undocumented field that I am not aware of. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#675304: amarok
Modestas, I would be very grateful if you could advise us on this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675304 I presume what has happpened is that the user is on testing and did an apt-get upgrade. Because of the current state of affairs his mysql got upgraded and not his amarok. I don't quite see why that should cause his amarok to fail - an explanation would be appreciated. Should we be asking for the amarok 2.5.0-3 to be rushed through to testing? Should we put a breaks clause to make late mysql incompatible with early versions of amarok - though I really don't want to do that as it would be unworkable in the long term. Also beyond following the proper transition procedures is there something we could be doing to avoid these situations? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#283173: w3c-sgml-lib vs w3-dtd-mathml
Vincnet, Maathieu,
Maybe after the freeze we should discuss making a clean up a release
goal for wheezy+1. It would be a rather small release goal, but it might
not happen otherwise.
On 26/05/12 03:32, Vincent Lefevre wrote:
On 2012-05-25 21:05:52 +0100, Nicholas Bamber wrote:
I am not sure what about w3c-dtd-mathml. However there is a long history
between w3c-dtd-xhtml and w3c-sgml-lib so I will assume it was a typo and
you meant w3c-dtd-xhtml.
There was no typo. I wrote w3c-dtd-xhtml.
No you can't remove w3c-dtd-xhtml. Many , many more people depend on it
currently than w3c-sgml-lib. Look at the popcorn ratings.
I don't see why w3-dtd-mathml should be treated differently from
w3c-dtd-xhtml. Why would there be a conflict between w3c-sgml-lib
and w3-dtd-mathml, but not between w3c-sgml-lib and w3c-dtd-xhtml?
Note that like w3-dtd-mathml, w3c-dtd-xhtml provides entity files
that are also in w3c-sgml-lib. So, if w3c-sgml-lib and
{w3-dtd-mathml and/or w3c-dtd-xhtml} are installed at the same
time, things can go wrong because the catalog can reference the
same id (or prefix) to two different places at the same time.
That said they are totally trying to do the same thing. They even - check
the copyroght file - have the same upstream. The difference is that
w3c-sgml-lib has a working watch file and leaves the upstream largely
untouched, whereas w3c-dtd-xhtml is just a random jumble of files vaguely
associated with the W3C.
I have tried twice to make w3c-sgml-lib a drop in replacement for
w3c-dtd-xhtml and failed. As I see it the only way forward is to make the
reverse dependencies of w3c-dtd-xhtml depend instead on w3c-sgml-lib. Then
w3c-dtd-xhtml can be dropped. There is no way that should be attempted this
side of the freeze.
OK.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#283173: w3c-sgml-lib vs w3-dtd-mathml
Firstly please don't get hung up on the name. w3c-sgml-lib is packaging the sgml-lib tarball from the w3c. I am not sure what about w3c-dtd-mathml. However there is a long history between w3c-dtd-xhtml and w3c-sgml-lib so I will assume it was a typo and you meant w3c-dtd-xhtml. No you can't remove w3c-dtd-xhtml. Many , many more people depend on it currently than w3c-sgml-lib. Look at the popcorn ratings. That said they are totally trying to do the same thing. They even - check the copyroght file - have the same upstream. The difference is that w3c-sgml-lib has a working watch file and leaves the upstream largely untouched, whereas w3c-dtd-xhtml is just a random jumble of files vaguely associated with the W3C. I have tried twice to make w3c-sgml-lib a drop in replacement for w3c-dtd-xhtml and failed. As I see it the only way forward is to make the reverse dependencies of w3c-dtd-xhtml depend instead on w3c-sgml-lib. Then w3c-dtd-xhtml can be dropped. There is no way that should be attempted this side of the freeze. However if the point of w3c-sgml-lib is that it can be easily kept uptodate, the irony is that at the moment I cannot because of #665296. That bug looks trviial to fix, but quite frankly I am exhausted at the moment. Guys, thanks for your interest and may the open source be with you. On 25/05/12 10:41, Vincent Lefevre wrote: On 2012-05-25 10:47:55 +0200, Mathieu Malaterre wrote: I am getting confused with the packaging of w3c-sgml-lib. Should it replaces w3-dtd-mathml ? This would be confusing for the user, because w3-dtd-mathml is mainly XML (that's why the contents are under /usr/share/xml), possibly with SGML compatibility, while the name of w3c-sgml-lib suggests that it's about SGML only. A name w3c-xml-sgml-lib might be better. And what about the status of w3c-dtd-xhtml? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674122: [debian-mysql] Fwd: Re: Bug#674122: otrs2: fails to upgrade from squeeze: Can't create table 'otrs2.#sql-1712_71
block 671115 by 674122 thanks Patrick, Some ideas. Not sure how the application works so not sure which is most liekly to be deoable. * There is a --default-storage-engine=type start up option. If you let the standard mysql scripts manage the mysqld process that one might not work. * It should be possible to convert that option into an option entry in the my.cnf file. You should also be able to own your own my.cnf fragment in say /etc/mysql/conf.d/otrs2 . * If you only need to enforce the default engine in upgrade scripts (or the creation of tables is confined in some other way) then this SQL would do it: set default_storage_engine = 'MyISAM'; However that will only persist as long as that connection. * Again you can use this SQL: set global default_storage_engine = 'MyISAM'; However that only takes effect on the next (and all subsequent connections) and requires super user privileges and will not survive a bounce. On 25/05/12 21:13, Patrick Matthäi wrote: Hi Sean, Debian-MySQL team and the rest of the world first thanks to the MySQL team and sean for doing a good job with mysql and dbconfig-common But now we have got a critical issue with upgrades from Squeeze to Wheezy, where I need some help.. The situation is: a) otrs2, like many other packages in Squeeze, are using MyISAM as storage engine as default b) With mysql-5.5 the default storage engine has been changed from MyISAM to InnoDB, which is IMHO (with my administrator hat on) a realy good decision c) .. but applications like otrs2 using MyISAM may fail with it :( If we would install otrs2 with the current sid development all tables are created with the InnoDB database engine, it would be successful but the ticket fulltextsearch would fail There are no errors and side effects if a user upgrades his otrs2 installation from Squeeze to current wheezy/testing (with mysql-5.1), since CREATE TABLE statements will create MyISAM tables (upstream didn't hardcoded the engine) Upgrading from a Squeeze installation to current sid with mysql-5.5 will create a few new tables, with the InnoDB format and after that setting some attributes will fail, as reported in #674122 .. So I want to ask if there is some nice and quick workaround for such issues, I don't think that otrs2 will be the only DBMS application with 5.1 - 5.5 upgrade issues. Patching every upgrade and install script of dbconfig-common to hardcode MyISAM (in this case) is IMHO a big bunch of work, maybe you have got better ideas or there is already an implementation (which I do not find) to solve such problems Thanks! Original-Nachricht Betreff: Re: Bug#674122: otrs2: fails to upgrade from squeeze: Can't create table 'otrs2.#sql-1712_71 Datum: Wed, 23 May 2012 20:18:45 +0200 Von: Patrick Matthäipmatth...@debian.org Antwort an: pmatth...@debian.org Organisation: www.Debian.org An: Thomas Muellertho...@chaschperli.ch, 674122-submit...@bugs.debian.org Am 23.05.2012 10:39, schrieb Thomas Mueller: Installing new version of config file /etc/init.d/otrs2 ... dbconfig-common: writing config to /etc/dbconfig-common/otrs2.conf Replacing config file /etc/otrs/database.pm with new version creating database backup in /var/cache/dbconfig-common/backups/otrs2_2.4.9+dfsg1-3+squeeze1.mysql. applying upgrade sql for 2.4.9+dfsg1-3+squeeze1 - 3.0. error encountered processing /usr/share/dbconfig-common/data/otrs2/upgrade/mysql/3.0: mysql said: ERROR 1005 (HY000) at line 322: Can't create table 'otrs2.#sql-1712_71' (errno: 150) dbconfig-common: otrs2 configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing otrs2 (--configure): subprocess installed post-installation script returned error exit status 1 Can't reproduce this error. I tried to reproduce this error, please notice that I also upgraded to mysql-server-5.5. After I had installed otrs2 on squeeze and upgraded to sid I get: otrs2 (3.1.5+dfsg1-1) wird eingerichtet ... Neue Version der Konfigurationsdatei /etc/init.d/otrs2 wird installiert ... dbconfig-common: writing config to /etc/dbconfig-common/otrs2.conf Replacing config file /etc/otrs/database.pm with new version creating database backup in /var/cache/dbconfig-common/backups/otrs2_2.4.9+dfsg1-3+squeeze1.mysql. applying upgrade sql for 2.4.9+dfsg1-3+squeeze1 - 3.0. error encountered processing /usr/share/dbconfig-common/data/otrs2/upgrade/mysql/3.0: mysql said: ERROR 1005 (HY000) at line 322: Can't create table 'otrs2.#sql-2ddc_72' (errno: 150) dbconfig-common: otrs2 configure: aborted. Then I simply tried out following: mysql drop database otrs2; create database otrs2; root@squeeze:~/usr/share/dbconfig-common/data/otrs2/install# mysql -ptest otrs2 mysql root@squeeze:~/usr/share/dbconfig-common/data/otrs2/install# (this was the squeeze database, I habe unpackaged it to ~/) root@squeeze:~/usr/share/dbconfig-common/data/otrs2/install# mysql -ptest otrs2
Bug#674210: patches
tag 674210 +patch
forwarded 674210 http://bugs.mysql.com/bug.php?id=65408
thanks
Patch attached
Author: Nicholas Bamber nicho...@periapt.co.uk
Subject: FTBS when in build directory containing '+'
Bug-Debian: http://bugs.debian.org/674210
Last-Update: 2012-05-24
--- a/mysql-test/include/mysqld--help.inc
+++ b/mysql-test/include/mysqld--help.inc
@@ -47,7 +47,11 @@
s/\b4294967295\b/18446744073709551615/;
s/\b2146435072\b/9223372036853727232/;
s/\b196608\b/262144/;
-foreach $var (@env) { s/$ENV{$var}/$var/ }
+foreach $var (@env) {
+ my $re = $ENV{$var};
+ $re =~ s/\+/\\\+/g;
+ s/$re/$var/
+}
next if /use --skip-(use-)?symbolic-links to disable/; # for valgrind, again
next if $skip;
print;
--- a/mysql-test/suite/sys_vars/t/character_sets_dir_basic.test
+++ b/mysql-test/suite/sys_vars/t/character_sets_dir_basic.test
@@ -7,6 +7,7 @@
# TODO: fix with a proper comparison in mysqltest
let $rcd= `SELECT REPLACE('$MYSQL_CHARSETSDIR', '\', '.')`;
let $rcd= `SELECT REPLACE('$rcd', '/', '.')`;
+let $rcd= `SELECT REPLACE('$rcd', '+', '.')`;
let $regex_charsetdir= `SELECT '/$rcd[\/\]/MYSQL_CHARSETSDIR/'`;
--replace_regex $regex_charsetdir
Bug#674395: libdbd-mysql-perl: FTBFS: ld: cannot find -lssl
Yeah the SSL stuff should have gone away now. (Except for the moment on amd64 where a Perl regular expression messed things up. ;-) ) On 24/05/12 13:38, gregor herrmann wrote: On Thu, 24 May 2012 14:23:17 +0200, Salvatore Bonaccorso wrote: Can confirm this, and adding libssl-dev to Build-Depends solves the FTBFS. I haven't looked yet, but this seems new ... Can this be related to changes in libmysqlclient-dev from 5.1 to 5.5? http://packages.debian.org/changelogs/pool/main/m/mysql-5.5/current/changelog mentions SSL stuff at some points ... (Random factoid: Lucas' rebuild was against libmysqlclient-dev 5.5.23-2, yesterday 5.5.23+dfsg-1 was uploaded with the changelog entry: * Revert having libssl-dev as a build dependency and changed WITH_SSL option to 'bundled' from 'yes' (Closes: #590905) and (Closes: #673865) ) Luckily periapt is involved here and there and might know better what's going on :) Cheers, gregor -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674210: FTBS: when build directory contains: '+'
Package: mysql-5.5 Version: 5.5.23+dfsg-1 Severity: serious Justification: Policy 2.2.1 When the build directory contains a '+' certain tests fail. This looks like it should be easily fixable with a bit of Perl. Build logs follow: https://buildd.debian.org/status/fetch.php?pkg=mysql-5.5arch=amd64ver=5.5.23%2Bdfsg-1stamp=1337765150 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673541: mysql-5.5: source tarball contains Docs/mysql.info which is not DFSG
Peter, It means I think that it can be redistibuted if unmodified. However the copyight file does not make it clear. Also I have no idea how you fix snapshot. I'm only trying to fix unstable. 5.5.23-1 (experimental) will have the same issue. I doubt anything else does but they need to be checked until the last one Norbert worked on/. On 20/05/12 13:14, Peter Palfrader wrote: On Sat, 19 May 2012, Nicholas Bamber wrote: On 19/05/12 21:59, Peter Palfrader wrote: Hi, On Sat, 19 May 2012, Nicholas Bamber wrote: Now it seems that at some point I directly downloaded from upstream and that it is this tarball that has been uploaded with 5.5.23-2. thanks for your report. For snapshot, can you tell me if that file is at least distributable, even if not DFSG-free? Cheers, Peter, The license is here for now: http://paste.debian.net/170119/. I hope to raise a fix asap which should make the issue moot. You can't fix snapshot that way. And linking to a paste on the BTS is a bad idea. It means your message is useless in a couple hours. Also, it did not really answer my question. Do you know if mysql.info is redistributable? I think the text you pasted suggested that, but I am not sure. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673541: mysql-5.5: source tarball contains Docs/mysql.info which is not DFSG
On 20/05/12 13:32, Peter Palfrader wrote: On Sun, 20 May 2012, Nicholas Bamber wrote: Peter, It means I think that it can be redistibuted if unmodified. However the copyight file does not make it clear. Also I have no idea how you fix snapshot. I'm only trying to fix unstable. 5.5.23-1 (experimental) will have the same issue. I doubt anything else does but they need to be checked until the last one Norbert worked on/. Snapshot is fixed by *removing* history. If we can ship the file as is, then we're fine. Thanks, weasel Surely it's better to remove it to be on the safe side. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590905: testing so far
The attached debdiff seems to help gmysqlcc, mediatomb, mydumper,
mysql-connector-++ to build.
It still fails for myodbc with the following error:
make[2]: Entering directory `/home/nicholas/debian/exp/myodbc-5.1.6/util'
/bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I../driver -I.. -D_FORTIFY_SOURCE=2 -I/usr/include -O3 -DDBUG_OFF
-I/usr/include/mysql -DBIG_JOINS=1 -fno-strict-aliasing -g -g -O2
-fstack-protector --param=ssp-buffer-size=4 -Wformat
-Werror=format-security -c -o stringutil.lo stringutil.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../driver -I..
-D_FORTIFY_SOURCE=2 -I/usr/include -O3 -DDBUG_OFF -I/usr/include/mysql
-DBIG_JOINS=1 -fno-strict-aliasing -g -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Werror=format-security -c
stringutil.c -fPIC -DPIC -o .libs/stringutil.o
stringutil.c: In function 'sqlchar_as_sqlwchar':
stringutil.c:125:5: error: too many arguments to function 'my_free'
/usr/include/mysql/my_sys.h:156:13: note: declared here
make[2]: *** [stringutil.lo] Error 1
make[2]: Leaving directory `/home/nicholas/debian/exp/myodbc-5.1.6/util'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/nicholas/debian/exp/myodbc-5.1.6'
dh_auto_build: make -j1 returned exit code 2
diff -Nru mysql-5.5-5.5.23/debian/changelog mysql-5.5-5.5.23/debian/changelog
--- mysql-5.5-5.5.23/debian/changelog 2012-05-08 05:59:19.0 +0100
+++ mysql-5.5-5.5.23/debian/changelog 2012-05-19 21:01:10.0 +0100
@@ -1,3 +1,13 @@
+mysql-5.5 (5.5.23-3) UNRELEASED; urgency=low
+
+ * Changes to prevent certain failures to build from scratch
+when building against MySQL 5.5 (Closes: #590905)
+- Patched mysql_config so that it no longer mandates -lssl -lcrypto
+- Added libwrap0-dev as a dependency of libmysqld-dev, libmysqld-pic
+- Added libaio-dev as a Linux dependency of libmysqld-dev, libmysqld-pic
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Fri, 18 May 2012 17:36:37 +0100
+
mysql-5.5 (5.5.23-2) unstable; urgency=low
* Stopped overriding the -j build parameter (Closes: #512964)
diff -Nru mysql-5.5-5.5.23/debian/control mysql-5.5-5.5.23/debian/control
--- mysql-5.5-5.5.23/debian/control 2012-05-07 19:33:17.0 +0100
+++ mysql-5.5-5.5.23/debian/control 2012-05-19 21:01:35.0 +0100
@@ -27,7 +27,8 @@
Package: libmysqld-pic
Architecture: any
Section: libdevel
-Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends}
+Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends},
+ libwrap0-dev (= 7.6-8.3), libaio-dev[linux-any]
Description: PIC version of MySQL embedded server development files
MySQL is a fast, stable and true multi-user, multi-threaded SQL database
server. SQL (Structured Query Language) is the most popular database query
@@ -39,7 +40,8 @@
Package: libmysqld-dev
Architecture: any
Section: libdevel
-Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends}
+Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends},
+ libwrap0-dev (= 7.6-8.3), libaio-dev[linux-any]
Description: MySQL embedded database development files
MySQL is a fast, stable and true multi-user, multi-threaded SQL database
server. SQL (Structured Query Language) is the most popular database query
diff -Nru mysql-5.5-5.5.23/debian/rules mysql-5.5-5.5.23/debian/rules
--- mysql-5.5-5.5.23/debian/rules 2012-05-05 13:32:23.0 +0100
+++ mysql-5.5-5.5.23/debian/rules 2012-05-19 23:40:20.0 +0100
@@ -177,6 +177,12 @@
install -m 0644 -o root -g root $(BUILDDIR_PIC)/libmysqld/libmysqld.a
$(TMP)/usr/lib/mysql/libmysqld_pic.a
# mysql_config won't report the -fPIC, so give libmysqld-pic users a
way to get their flags
install -m 0755 -o root -g root $(BUILDDIR_PIC)/scripts/mysql_config
$(TMP)/usr/bin/mysql_config_pic
+ # As per #590905 we don't want mysql_config saying -lssl -lcrypto
+ # because those libraries are overkill for most packages.
+ # Patch mysql_config inline rather using quilt because the latter
+ # seems not to work, though I don't know why. Comments hold
+ # but not the real bit of work. The source is scripts/mysql_config.sh.
+ sed -i -e's/-lssl -lcrypto //' debian/libmysql*/usr/bin/mysql_config*
# mysql-client
install -m 0755 debian/additions/mysqlreport $(TMP)/usr/bin/
install -m 0755 debian/additions/innotop/innotop $(TMP)/usr/bin/
Bug#590905: testing so far
Matej,
I confirm that the experimental myodbc works for me against my package.
Also the last debdiff was incorrect. New one attached.
I understand what you are you saying about the extra libraries. The
extra libraries put there by mysql_config show up as warnings in the
shlibs stage of the build.
However I am more comfortable with this approach for now. For the
following reasons.
1.) I have not fully worked out how to conquer cmake.
2.) The whole issue of MySQL and the libraries needs more work. Symbol
files for example?
3.) The output now matches what ubuntu generates.
I am quite happy for this bug report to be cloned to tackle thr longer
term issues.
On 20/05/12 15:00, Matej Vela wrote:
Nicholas Bambernicho...@periapt.co.uk writes:
The attached debdiff seems to help gmysqlcc, mediatomb, mydumper,
mysql-connector-++ to build.
From what I can tell, mysql_config --libs and mysql_config --libs_r
still pull in other libraries? I really think they should be restricted
to -lmysqlclient and -lmysqlclient_r respectively. Every additional
dependency can complicate transitions and upgrades down the line, and
doesn't bring any upside. What we should be aiming for is the behavior
from wheezy:
$ mysql_config | grep -- --libs
--libs [-rdynamic -L/usr/lib/mysql -lmysqlclient]
--libs_r [-rdynamic -L/usr/lib/mysql -lmysqlclient_r]
It still fails for myodbc with the following error:
[...]
stringutil.c:125:5: error: too many arguments to function 'my_free'
As Steve mentioned in #673264, you should test with the version from
experimental (it was building fine without -lssl -lcrypto when I
checked on Friday).
Cheers,
Matej
diff -Nru mysql-5.5-5.5.23/debian/changelog mysql-5.5-5.5.23/debian/changelog
--- mysql-5.5-5.5.23/debian/changelog 2012-05-08 05:59:19.0 +0100
+++ mysql-5.5-5.5.23/debian/changelog 2012-05-19 21:01:10.0 +0100
@@ -1,3 +1,13 @@
+mysql-5.5 (5.5.23-3) UNRELEASED; urgency=low
+
+ * Changes to prevent certain failures to build from scratch
+when building against MySQL 5.5 (Closes: #590905)
+- Patched mysql_config so that it no longer mandates -lssl -lcrypto
+- Added libwrap0-dev as a dependency of libmysqld-dev, libmysqld-pic
+- Added libaio-dev as a Linux dependency of libmysqld-dev, libmysqld-pic
+
+ -- Nicholas Bamber nicho...@periapt.co.uk Fri, 18 May 2012 17:36:37 +0100
+
mysql-5.5 (5.5.23-2) unstable; urgency=low
* Stopped overriding the -j build parameter (Closes: #512964)
diff -Nru mysql-5.5-5.5.23/debian/control mysql-5.5-5.5.23/debian/control
--- mysql-5.5-5.5.23/debian/control 2012-05-07 19:33:17.0 +0100
+++ mysql-5.5-5.5.23/debian/control 2012-05-19 21:01:35.0 +0100
@@ -27,7 +27,8 @@
Package: libmysqld-pic
Architecture: any
Section: libdevel
-Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends}
+Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends},
+ libwrap0-dev (= 7.6-8.3), libaio-dev[linux-any]
Description: PIC version of MySQL embedded server development files
MySQL is a fast, stable and true multi-user, multi-threaded SQL database
server. SQL (Structured Query Language) is the most popular database query
@@ -39,7 +40,8 @@
Package: libmysqld-dev
Architecture: any
Section: libdevel
-Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends}
+Depends: libmysqlclient-dev (= ${source:Version}), ${misc:Depends},
+ libwrap0-dev (= 7.6-8.3), libaio-dev[linux-any]
Description: MySQL embedded database development files
MySQL is a fast, stable and true multi-user, multi-threaded SQL database
server. SQL (Structured Query Language) is the most popular database query
diff -Nru mysql-5.5-5.5.23/debian/rules mysql-5.5-5.5.23/debian/rules
--- mysql-5.5-5.5.23/debian/rules 2012-05-05 13:32:23.0 +0100
+++ mysql-5.5-5.5.23/debian/rules 2012-05-20 16:03:23.0 +0100
@@ -93,6 +93,7 @@
-DCMAKE_VERBOSE_MAKEFILE=ON \
$(FORCE_FPIC) \
-DMYSQL_UNIX_ADDR=/run/mysqld/mysqld.sock \
+ -DCMAKE_VERBOSE_MAKEFILE=yes \
-DMYSQL_USER=mysql \
-DWITH_LIBWRAP=ON \
-DWITH_READLINE=OFF \
@@ -177,6 +178,13 @@
install -m 0644 -o root -g root $(BUILDDIR_PIC)/libmysqld/libmysqld.a
$(TMP)/usr/lib/mysql/libmysqld_pic.a
# mysql_config won't report the -fPIC, so give libmysqld-pic users a
way to get their flags
install -m 0755 -o root -g root $(BUILDDIR_PIC)/scripts/mysql_config
$(TMP)/usr/bin/mysql_config_pic
+ # As per #590905 we don't want mysql_config saying -lssl -lcrypto
+ # because those libraries are overkill for most packages.
+ # Patch mysql_config inline rather using quilt because the latter
+ # seems not to work, though I don't know why. Comments hold
+ # but not the real bit of work. The source is scripts/mysql_config.sh
Bug#673528: mysql-5.5: source tarball contains Docs/mysql.info which is not DFSG
Source: mysql-5.5 Version: 5.5.23-2 Severity: serious Justification: Policy 2.1 Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? debian/rules contains a get-orig-source rule that downloads the tarball and strips out the Docs directory. Amongst other things the Docs directory contains an mysql.info file (which is non-DFSG) and a missing upstream ChangeLog file (which is DFSG compliant). The rule is not particularly well documented and as far as I can see there is nothing in the Debian packaging to say that the upstream tarball had been modified to make it DFSG compliant. Now it seems that at some point I directly downloaded from upstream and that it is this tarball that has been uploaded with 5.5.23-2. Also there is a debian/watch file which is broken. The debian/rules rules hard codes the chosen mirror. One possible solution would be as follows: 1.) Fix the watch file to strip out Docs/mysql.info and use a number of working mirrors. 2.) Rewrite the get-orig-source rule to use uscan. 3.) Install the upstream changelog and remove the associated lintian overrides 4.) Upload a version 5.5.23+dfsg-1. -- System Information: Debian Release: wheezy/sid 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-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#673541: mysql-5.5: source tarball contains Docs/mysql.info which is not DFSG
On 19/05/12 21:59, Peter Palfrader wrote: Hi, On Sat, 19 May 2012, Nicholas Bamber wrote: Now it seems that at some point I directly downloaded from upstream and that it is this tarball that has been uploaded with 5.5.23-2. thanks for your report. For snapshot, can you tell me if that file is at least distributable, even if not DFSG-free? Cheers, Peter, The license is here for now: http://paste.debian.net/170119/. I hope to raise a fix asap which should make the issue moot. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590905: fix coming up
Looks like we'll be uploading a special fix for this. (00:10:20) periapt: What do you guys want done about 673262 672824 673263 672619 being blocked by 590905? That is do you want another upload of mysql-5.5 or localized fixes (for now). (00:10:29) KiBi: http://release.debian.org/transitions/export/packages.yaml (00:11:05) ***raphael thinks there should be a no soname bumps, REJECT them mode a-la transitions.yaml :) (00:11:07) KiBi: periapt: I don't think I'll be able to comment on mysql this evening. (00:11:09) periapt: I'll take the This is what happens when you dump shit on us as read if you take my profuse apologies as read. :-/ (00:11:23) mbiebl: KiBi: thanks a lot (00:11:29) periapt: KiBi: I'll wait. (00:12:23) KiBi: periapt: Hmm. I think this bug wants a fix, which should be quite easy? (00:12:58) gusnan left the room (quit: Quit: Lämnar). (00:13:15) periapt: Kibi. Can do. I was working round to it. I would appreciate a review of it before uploading. (00:14:34) periapt: I mean I was expecting to fix it a long time after the freeze. (00:15:13) KiBi: why delaying that fix, especially if packages are directly affected? (00:15:25) KiBi: I'm not sure pushing a workaround in those packages in the way to go. (00:15:57) periapt: KiBi: Well that's all water under the bridge. If you want a fix you'll get a fix. (00:18:04) periapt: What procedure would you like me to follow at this juncture? (00:20:10) DeepDiver left the room (quit: Remote host closed the connection). (00:28:18) periapt: Okay I'll do the following: 1.) Try to reproduce the bugs listed as being blocked by 590905 2.) Build 5.5.23-2-w1 3.) Test those packages against that. 4.) upload with high urgency. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649955: non-maintainer upload of mod-auth-mysql
Joey, I am going to upload a 15-day delayed build of mod-auth-mysql to fix an FTBS. If you would prefer to fix it yourself I am sure you know what to do. I should say the package needs other maintenance which I am not going to attempt. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672928: [debian-mysql] libdbi-drivers FTBS against latest MySQL
On 15/05/12 09:49, Olaf van der Spek wrote: On Tue, May 15, 2012 at 12:24 AM, Nicholas Bamber nicho...@periapt.co.uk wrote: Thomas, I attach a patch to enbale libdbi-drivers to build against the latest Are you sure this is right? Shouldn't the headers and libs still be found automatically? Olaf Normally yes, but I am pretty sure that the patch would not be backwards compatible. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672207: [debian-mysql] Bug#672207: Processed: Reassign bug #672207 to mysql-server-core-5.5
tag 672207 -moreinfo block 671115 by 672207 reassign 672207 amarok thanks Actually I see what the problem is. The change needs to happen on the amarok side. It is a mysql bug only in as much as you *should* have had more warning and the mysqlclient transition will not complete until this is fixed. Basically you need to change your dependencies and recompile. Build dependencies -- libmysqld-pic (= 5.1.36-2) - libmysqld-pic (= 5.5) mysql-server-core-5.1 | mysql-server-5.1 - mysql-server-5.5 (or possibly mysql-sever (= 5.5) Binary dependencies libmysqlcient18 (should not be explicitly specified but picked up by the shlibs system hopefully). Maybe you would do better to have a looser coupling on the MySQL versions. On 15/05/12 21:56, Nicholas Bamber wrote: tag 672207 +moreinfo thanks Please send: 1.) Whatever you have for config (Put '' in place of any passwords) 2.) log files of it working 3,) log files of it not working. On 15/05/12 21:24, Debian Bug Tracking System wrote: Processing commands for cont...@bugs.debian.org: reassign 672207 mysql-server-core-5.5 Bug #672207 [amarok] [amarok] Fails to open internal database after upgrade to mysql 5.5 from 5.1 Bug reassigned from package 'amarok' to 'mysql-server-core-5.5'. No longer marked as found in versions amarok/2.5.0-1. Ignoring request to alter fixed versions of bug #672207 to the same values previously set End of message, stopping processing here. Please contact me if you need assistance. ___ pkg-mysql-maint mailing list pkg-mysql-ma...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mysql-maint ___ 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#672928: found in
found 672928 0.8.3-1+s-3 thanks I have patch. Will upload when tested a bit. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672950: yate: FTBFS on ia64, powerpc, s390, s390x
Source: yate Version: 4.1.0-1~dfsg-1 Severity: serious Tags: wheezy sid Hi, Your package fails to build on various architectures. g++ -Wall -I.. -I.. -O2 -fno-check-new -fno-exceptions -fPIC -DHAVE_GCC_FORMAT_CHECK -DHAVE_BLOCK_RETURN -export-dynamic -shared -Wl,--unresolved-symbols=ignore-in-shared-libs -Wl,--retain-symbols-file,/dev/null -o h323chan.yate -I/usr/include/ptlib -D_REENTRANT -I/usr/include/openh323 h323chan.cpp -L/usr/lib -lopenh323 -L/usr/lib -lpt -L.. -lyate g++ -Wall -I.. -I.. -O2 -fno-check-new -fno-exceptions -fPIC -DHAVE_GCC_FORMAT_CHECK -DHAVE_BLOCK_RETURN -export-dynamic -shared -Wl,--unresolved-symbols=ignore-in-shared-libs -Wl,--retain-symbols-file,/dev/null -o gsmcodec.yate -I/usr/include gsmcodec.cpp -lgsm -L.. -lyate /usr/bin/make -C ../libs/miniwebrtc make[3]: Entering directory `/build/buildd-yate_4.1.0-1~dfsg-1-ia64-FYYJ55/yate-4.1.0-1~dfsg/libs/miniwebrtc' g++ -Wall -I. -I./audio/common/processing -I./audio/common/vad -I./audio/processing/aec -I./audio/processing/aecm -I./audio/processing/agc -I./audio/processing/ns -I./audio/processing/utility -I./system_wrappers -O2 -fno-check-new -fno-exceptions -fPIC -DHAVE_GCC_FORMAT_CHECK -DHAVE_BLOCK_RETURN -DWEBRTC_NS_FLOAT=true -c -o audio/common/resampler/resampler.o audio/common/resampler/resampler.cc In file included from ./audio/common/processing/signal_processing_library.h:22:0, from audio/common/resampler/resampler.cc:19: ./typedefs.h:83:2: error: #error Please add support for your architecture in typedefs.h make[3]: *** [audio/common/resampler/resampler.o] Error 1 make[3]: Leaving directory `/build/buildd-yate_4.1.0-1~dfsg-1-ia64-FYYJ55/yate-4.1.0-1~dfsg/libs/miniwebrtc' make[2]: *** [../libs/miniwebrtc/libminiwebrtc.a] Error 2 make[2]: Leaving directory `/build/buildd-yate_4.1.0-1~dfsg-1-ia64-FYYJ55/yate-4.1.0-1~dfsg/modules' make[1]: *** [modules] Error 2 make[1]: Leaving directory `/build/buildd-yate_4.1.0-1~dfsg-1-ia64-FYYJ55/yate-4.1.0-1~dfsg' make: *** [build-arch-stamp] Error 2 (more) Logs available here: https://buildd.debian.org/status/package.php?p=yate -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672928: libdbi-drivers FTBS against latest MySQL
Thomas, I attach a patch to enbale libdbi-drivers to build against the latest MySQL. I will upload my build with a 15 day delay. Of course plese feel free to fix it yourself if you have any issues with my patch. Nicholas diff -Nru libdbi-drivers-0.8.3-1+s/debian/changelog libdbi-drivers-0.8.3-1+s/debian/changelog --- libdbi-drivers-0.8.3-1+s/debian/changelog 2012-04-14 18:25:27.0 +0100 +++ libdbi-drivers-0.8.3-1+s/debian/changelog 2012-05-14 23:07:05.0 +0100 @@ -1,3 +1,10 @@ +libdbi-drivers (0.8.3-1+s-3.1) unstable; urgency=low + + * Non-maintainer upload. + * Pick up multi-arch libraries for MySQL (Closes: #672928) + + -- Nicholas Bamber nicho...@periapt.co.uk Mon, 14 May 2012 23:06:51 +0100 + libdbi-drivers (0.8.3-1+s-3) unstable; urgency=low [ Thomas Goirand ] diff -Nru libdbi-drivers-0.8.3-1+s/debian/control libdbi-drivers-0.8.3-1+s/debian/control --- libdbi-drivers-0.8.3-1+s/debian/control 2012-04-14 18:25:27.0 +0100 +++ libdbi-drivers-0.8.3-1+s/debian/control 2012-05-14 20:33:36.0 +0100 @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: Thomas Goirand z...@debian.org -Build-Depends: debhelper (= 9), autotools-dev, libdbi-dev (= 0.8.4-5), libmysqlclient-dev, libpq-dev (= 8.3~rc2-1+b1), libsqlite0-dev, libsqlite3-dev, freetds-dev, automake, libtool, mysql-server, mysql-client, postgresql, postgresql-client, locales-all | language-pack-en, dh-autoreconf +Build-Depends: debhelper (= 9), autotools-dev, libdbi-dev (= 0.8.4-5), libmysqlclient-dev (= 5.5), libpq-dev (= 8.3~rc2-1+b1), libsqlite0-dev, libsqlite3-dev, freetds-dev, automake, libtool, mysql-server (= 5.5), mysql-client (= 5.5), postgresql, postgresql-client, locales-all | language-pack-en, dh-autoreconf Standards-Version: 3.9.3.1 Vcs-Browser: http://git.debian.org/?p=users/zigo/libdbi-drivers.git Vcs-Git: http://git.debian.org/git/users/zigo/libdbi-drivers.git diff -Nru libdbi-drivers-0.8.3-1+s/debian/rules libdbi-drivers-0.8.3-1+s/debian/rules --- libdbi-drivers-0.8.3-1+s/debian/rules 2012-04-14 18:25:27.0 +0100 +++ libdbi-drivers-0.8.3-1+s/debian/rules 2012-05-14 08:44:11.0 +0100 @@ -30,6 +30,8 @@ --prefix=/usr \ --with-pgsql \ --with-mysql \ + --with-mysql-incdir=/usr/include/$(DEB_HOST_MULTIARCH) \ + --with-mysql-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \ --with-sqlite \ --with-sqlite-incdir=/usr/include/$(DEB_HOST_MULTIARCH) \ --with-sqlite-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
Bug#672588: investigating
Adding '--nodefaults' to the definition of mysqladmin in debian/setup-mysql.sh gets round the issue of the invalid option. However when I resume with fakeroot debian/rules binary all the tests fail. Perhaps the build is in a confusd state by that point. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672714: ruby-dataobjects-mysql: FTBFS against mysql-5.5 (cannot connect to mysql-server)
Source: ruby-dataobjects-mysql Version: 0.10.8-2 Severity: serious Tags: wheezy sid Hi, Your package fails to build against mysql-5.5 on hurd and kfreebsd-i386. /usr/bin/mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/tmp.dHJPGMuqfj/mysql.sock' (2)' Check that mysqld is running and that the socket: '/tmp/tmp.dHJPGMuqfj/mysql.sock' exists! Logs available here: https://buildd.debian.org/status/fetch.php?pkg=ruby-dataobjects-mysqlarch=kfreebsd-i386ver=0.10.8-2stamp=1336560106 https://buildd.debian.org/status/fetch.php?pkg=ruby-dataobjects-mysqlarch=hurd-i386ver=0.10.8-2stamp=1336769902 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
