Hi all,
On 06-12-15 14:23, Paul Gevers wrote:
> For those of you that backport their packages via the Debian backports
> archive, I will provide a backport of dbconfig-common once version 2.0.0
> reaches testing.
This has happened. dbconfig-common, dbconfig- and
dbconfig-no-thanks are now in sid,
Hi Frederic-Emmanuel,
On 30-01-16 09:30, PICCA Frederic-Emmanuel wrote:
> I am the maintainer of tango-db which use dbconfig-common and a mysql
> database.
> It seems that there is currently a discussion about he support of mysql and
> mariadb for Debian 9
Can you please point me to the relevan
Package: wnpp
Severity: wishlist
Owner: Balasankar C
* Package name: ruby-sentry-raven
Version : 0.15.3
Upstream Author : Sentry
* URL : https://github.com/getsentry/raven-ruby
* License : Apache-2.0
Programming Lang: Ruby
Description : client interface
Hello
thanks a lot for your work on dbconfig-common.
I am the maintainer of tango-db which use dbconfig-common and a mysql database.
It seems that there is currently a discussion about he support of mysql and
mariadb for Debian 9
Do you know if dbconfig-common will integrate a way to switch fro
Hello Paul
> Can you please point me to the relevant discussion?
I speak about this [1]
> Actually, I don't think that is in scope of dbconfig-common. I would
> rather expect that MariaDB would provide that functionality. It is
> required for more packages and situations than just those supporte
On 2016-01-30 at 04:51, Paul Gevers wrote:
> Hi Frederic-Emmanuel,
>
> On 30-01-16 09:30, PICCA Frederic-Emmanuel wrote:
>> Do you know if dbconfig-common will integrate a way to switch from
>> mysql to mariadb in the near futur. something whcih can help do the
>> migration database from mysql t
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-aodhclient
Version : 0.1.0
Upstream Author : OpenStack Foundation
* URL : https://github.com/openstack/python-aodhclient
* License : Apache-2.0
Programming Lang: Python
Descripti
Hi,
On 30-01-16 12:30, PICCA Frederic-Emmanuel wrote:
>> If a package relies on the dbconfig-common framework for database setup
>> and maintenance, installing dbconfig-no-thanks instead of one of
>> dbconfig's database-specific packages will block this function. It is
>> intended for cases where
Hello,
it has been clear to me for a while that I am unable to stay on top of
my Debian responsibilities. I feel like my usual pattern of things in
debian has gone like this:
1. I see a problem, I have an idea how to solve it, I make a prototype
for it, I deploy it, look after it until I se
Excerpts from The Wanderer's message of 2016-01-30 04:28:42 -0800:
> On 2016-01-30 at 04:51, Paul Gevers wrote:
>
> > Hi Frederic-Emmanuel,
> >
> > On 30-01-16 09:30, PICCA Frederic-Emmanuel wrote:
>
> >> Do you know if dbconfig-common will integrate a way to switch from
> >> mysql to mariadb in
On 30/01/16 13:22, Enrico Zini wrote:
> Hello,
>
> it has been clear to me for a while that I am unable to stay on top of
> my Debian responsibilities.
Hi Enrico,
First of all, I'm sure I won't be the only person to want to thank you
for all that you have done for Debian (and beyond) so far. It'
Enrico Zini writes ("Downscaling responsibilities"):
> [stuff]
I just wanted to say thanks for all the work you have put in.
And also to tell you that it is totally OK to not want to end up here:
> 2. I get stuck looking after it forever.
So it is totally OK for you to to do this:
> I have no
On Sat, Jan 30, 2016 at 03:20:48PM +, Chris Boot wrote:
> I guess the bit I don't follow is removing features from various
> services, but carrying on maintaining them.
Chopping some overengineering out of debtags.debian.net is something I
could actually have fun with. I also hope that by fre
On Sat, Jan 30, 2016 at 05:02:10PM +, Ian Jackson wrote:
> Enrico Zini writes ("Downscaling responsibilities"):
> > I have now decided to hit the reset button and end this situation. I'm
> > going to orphan most of my packages, and radically scale down the
> > complexity of the web services I'm
Hi,
Let me give a status update on how well cross building works in
unstable.
Toolchain
-
We have cross compilers and crossbuild-essential-* packages in unstable
for quite a while now. (Thanks to Matthias Klose.) These tend to work
well. Recently, sbuild saw significant improvements wrt.
Enrico Zini writes:
> it has been clear to me for a while that I am unable to stay on top of
> my Debian responsibilities. I feel like my usual pattern of things in
> debian has gone like this:
>
> 1. I see a problem, I have an idea how to solve it, I make a prototype
> for it, I deploy it
On 2016-01-30 at 08:49, Clint Byrum wrote:
> Excerpts from The Wanderer's message of 2016-01-30 04:28:42 -0800:
>
>> On 2016-01-30 at 04:51, Paul Gevers wrote:
>>> Actually, I don't think that is in scope of dbconfig-common. I
>>> would rather expect that MariaDB would provide that
>>> functiona
On Sat, Jan 30, 2016 at 8:08 PM, Helmut Grohne wrote:
> Hi,
>
> Let me give a status update on how well cross building works in
> unstable.
>
> Toolchain
> -
>
> We have cross compilers and crossbuild-essential-* packages in unstable
> for quite a while now. (Thanks to Matthias Klose.) The
Hi,
Quoting Bastien ROUCARIES (2016-01-31 00:49:14)
> Could you document on wiki how can we begin as a package manager. For
> instance I could not achieve to parse
> http://bootstrap.debian.net/cross_all/imagemagick.html
I apologize. Since I wrote the software it is hard for me to put myself into
Hi,
over time I have seen several changes in the values we should put in to
Vcs-* fields. The latest one is s/http:/https:/. While using config
model editor helps a lot to follow those changes we will probably see
more and more packages inside the archive that never changed but start
accumulatin
On Sun, Jan 31, 2016 at 08:23:11AM +0100, Andreas Tille wrote:
> Hi,
>
> over time I have seen several changes in the values we should put in to
> Vcs-* fields. The latest one is s/http:/https:/. While using config
> model editor helps a lot to follow those changes we will probably see
> more an
21 matches
Mail list logo