Bug#995846: FTBFS: Fatal TYPE-ERROR and tests incompatible with PG14
Thanks again folks, I really appreciate the time and effort you're putting into this, and of course the good results! Cheers, happy festivities, -- Dimitri Fontaine d...@tapoueh.org Author of “The Art of PostgreSQL”, https://theartofpostgresql.com On Mon, Dec 20, 2021, at 22:54, Christoph Berg wrote: > Re: Sébastien Villemot >> I’ve uploaded a new cl-esrap. It seems pgloader builds again. > > Merci! I'll try to polish the package over the next days. > > Christoph
Bug#864309: pgloader: crashes on startup if libssl1.0.2 is not installed
Andreas Beckmann writes: > Preparing such an upload now, trying to make this (one of) the last > upload(s) still reaching stretch r0. Thanks a lot for taking care of that one! -- dim
Bug#725570: pgfincore: FTBFS: dpkg-buildpackage: error: dpkg-source -b pgfincore-1.1 gave error exit status 255
gregor herrmann writes: > I'm a bit wary to NMU a package that would have to go through NEW ... > Dimitri, are you around? I would actually like it if you want to be the main maintainer of the package now. Do you need me to add you as a github collaborator on the main github project so that you can edit the packaging there? -- dim -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#559609: hstore-new: diff for NMU version 1.0-2.1
Stefano Zacchiroli writes: > I've sponsored an NMU for hstore-new (versioned as 1.0-2.1) prepared by > Obey Arthur Liu (Cc:-ed) and uploaded it to DELAYED/3, as per devref > §5.11.1. Please feel free to tell me if I should reschedule it somehow. I'm grateful to see people caring for those packages. The real fix I'm envisioning is in the hands of Martin Pitt, though. It's a pg_buildext tool that knows about currently supported PostgreSQL version in your debian distribution and only build those. Easy to use for the module maintainers, and allow for such issue to get solved without patch nor NMU. I kind of hope to see that applied before squeeze is frozen so that I'm able to fix my bugs with it. Regards, -- dim -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#454062: tutos2: should this package be removed?
Hi, Le Sunday 02 December 2007 20:33:23 Filippo Giunchedi, vous avez écrit : > While reviewing some packages, your package came up as a possible > candidate for removal from Debian, because: > > * affected by php4 removal (424828) > * last maintainer upload in 2005-11-03 > * seems unmaintained upstream (1.3 seems to be maintained though) > > If you think that it should be orphaned instead of being removed from > Debian, please reply to this bug and tell so. In fact I'm no more in a position to maintain this package anymore, but I've been told it works ok with some PHP 5 version (maybe 5.2.0, or 5.0.x). I recently had an opportunity to give it a test (php 5.2.4 from sid) and it didn't run ok from the box (CVS BRANCH_2_0). The officially maintained branch is 1.3, though. Please consider orphaning this package. Thanks, -- dim I decry the current tendency to seek patents on algorithms.There are better ways to earn a living than to prevent other people from making use of one's contributions to computer science. -- D. E. Knuth signature.asc Description: This is a digitally signed message part.
Bug#353981: Remove MySQL support (Closes: #353981, #304613)
Le Jeudi 04 Mai 2006 09:51, [EMAIL PROTECTED] a écrit : > Hello, Hi, > I must say, I find very deceptive the way you "fixed" this bug by removing > mysql support :( I gave you all the infos to correct this and you didn't. > You just had to read Mysql 5 documentation to understand how to solve it, > and you choosed a lamer's way ! Bravo ! You may want to know a little more than you do about rdbms support in TUTOS and the way it evolved in the BRANCH-2-0. This project began with support for as many rdbm as you want to support, the way it is usually done : the written (generated) SQL command can be sent by using any protocol/library, then the resultset is parsed and its format is adapted for further usage. The problem with this way of supporting several RDBM is that the written request is written once for all of them, hence for example if you support MySQL (previous its version 5) you then can't write any subqueries in your SQL. When I was paid to develop TUTOS 2 branch, we made the choice to only support PostgreSQL, our RDBM of choice. And I wrote some complex queries involving a syntax MySQL wouldn't be able to understand. The MySQL support in TUTOS was from there broken, but I forgot to mark this in the debian package. Our way to resolve the debian bug was to effectively mark tutos as being a PostgreSQL only project, a decision taken two years ago. Hoping this answer will help you understand the choices, regards, -- Dimitri Fontaine http://dim.tapoueh.org pgpkPaUlXzV4r.pgp Description: PGP signature