Your message dated Wed, 09 Mar 2016 22:02:05 +0000
with message-id <[email protected]>
and subject line Bug#811158: Removed package(s) from unstable
has caused the Debian Bug report #409389,
regarding Provide a mysql-server-dev package for engine plugins
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
409389: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409389
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-dfsg-5.1
Version: 5.1.11beta-1
I was considering to package Primebase XT (pbxt) which is a Mysql
Database Engine, that can be plugged into mysql-5.1. But for pbxt to
build it must access all mysql headers (not only client headers). This
headers today could only be accessed by getting mysql-dfsg-5.1 sources.
This way, a mysql-server-dev (or something like this) package providing
the mysql server headers.
I've discussed a little with seanius in #debian-devel about this...
follows the log...
<ruoso> seanius, hi... I'm considering packaging primebase-xt
<ruoso> but it needs mysql headers that are not available in
libmysql-client-dev
<ruoso> (which is actually fine, since they're not client headers)
* ruoso refers to mysql-5.1 (in experimental)
<seanius> ruoso: fyi the version in experimental has a broken (changed
abi, same soname) client lib
<seanius> so you need headers that are only in 5.1, or you need headers
that aren't packaged by us at all?
<ruoso> headers that aren't pacakge at all
<ruoso> s/pacakge/packaged/
<ruoso> like mysql_priv.h
<ruoso> my_handler.h
<ruoso> and many others I think
<ruoso> btw, primebase-xt is a database engine for mysql
<seanius> ruoso: yeah, i googled it
<seanius> myql_priv sounds, well, kinda private :)
<ruoso> yeah...
<ruoso> but...
<ruoso> how am I supposed to build it?
<ruoso> without the headers?
<seanius> ruoso: it's a good question. i don't think we want to expose
any headers or other parts of the ABI that mysql doesn't want to expose
<seanius> the ABI breaks enough as it is :)
<seanius> but maybe we can work something out
<ruoso> create mysql-dontusethis-headers
<ruoso> :)
<ruoso> btw, I'm oppening a bug in mysql 5.1, so we can discuss this...
I'm including this conversation in the bug report...
<seanius> i'd suggest summarizing this in an email to me, christian
(the "real" maintainer), and monty taylor (mtaylor at mysql.com), who
seems to be our "inside friend" @ mysql
Daniel
--- End Message ---
--- Begin Message ---
Version: 5.5.46-0+deb8u1+rm
Dear submitter,
as the package mysql-5.5 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/811158
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
