For some (probably many) people, an upgrade from squeeze (or earlier) to
wheezy may be their first real experience of DNSSEC
I've tried to update the wiki page to help people who are completely new
to the subject. However, I'm sure there are people who may be able to
provide more specific
On 17/01/13 15:08, Olivier Berger wrote:
Hi.
Daniel Pocock dan...@pocock.com.au writes:
Simon and I both have some security/authentication packages in Debian.
I've proposed a group on alioth, pkg-auth, which would be an umbrella
for packages like this and potentially others
The team
A few weeks back, the pkg-monitoring team was created
Although we currently look after Ganglia related stuff, it is not
exclusively for Ganglia, and could be a good way to collaborate on any
package related to metric collection, storage and analysis
Anybody wishing to collaborate or migrate
On 19/01/13 22:07, Mathieu Parent wrote:
Hi,
2013/1/19 Daniel Pocock dan...@pocock.com.au:
A few weeks back, the pkg-monitoring team was created
Although we currently look after Ganglia related stuff, it is not
exclusively for Ganglia, and could be a good way to collaborate
I notice some upstreams hack NDEBUG into their Makefile, while others
leave it at the discretion of the user
Is there any distribution policy for this? Should I be adding something
into debian/rules to set -DNDEBUG when I prepare a package for release?
--
To UNSUBSCRIBE, email to
Mathieu Malaterre ma...@debian.org wrote:
On Tue, Feb 19, 2013 at 5:30 PM, Ian Jackson
ijack...@chiark.greenend.org.uk wrote:
Daniel Pocock writes (NDEBUG when building packages?):
I notice some upstreams hack NDEBUG into their Makefile, while
others
leave it at the discretion of the user
I've just uploaded the SIPml5 JavaScript packages into the queue for
unstable
This stuff really is revolutionary.
I've had it running with Google Chrome 25 on squeeze and wheezy, and
using a patched repro (reSIProcate) SIP proxy on wheezy.
Anybody maintaining any type of web package (e.g. a
On 24/02/13 00:20, Timo Juhani Lindfors wrote:
Daniel Pocock dan...@pocock.com.au writes:
JavaScript and give users of their package the ability to click'n'call
other users within the web page.
Have you had time to study how the technology works? If both parties are
behind a HTTP proxy
On 24/02/13 01:01, Timo Juhani Lindfors wrote:
Daniel Pocock dan...@pocock.com.au writes:
- WebSockets carries the SIP signaling (e.g. to register the user
location, find the person you want to call). WebSockets works through
HTTP proxies
http://en.wikipedia.org/wiki/WebRTC does
On 23/02/13 17:41, Hendrik Sattler wrote:
Am Samstag, 23. Februar 2013, 16:39:22 schrieb Lisandro Damián Nicanor Pérez
Meyer:
On Sat 23 Feb 2013 12:33:58 Lisandro Damián Nicanor Pérez Meyer escribió:
On Sat 23 Feb 2013 12:18:30 Lisandro Damián Nicanor Pérez Meyer escribió:
On Sat 23 Feb 2013
There was recently some discussion in pkg-javascript about how to give
more people access to the VCS (e.g. keeping the git repositories
logically organised under the pkg-javascript tree, but making write
access available to all DDs + alioth guest users and not just those in
the pkg-javascript
On 28/02/13 13:15, Simon McVittie wrote:
On 28/02/13 09:39, Daniel Pocock wrote:
Has anybody had experience controlling access to git repositories, for
example, to give users access but prevent some of the following
dangerous operations?
If you look at it from the appropriate angle
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/02/13 20:20, Jonas Smedegaard wrote:
Quoting Daniel Pocock (2013-02-28 19:20:09)
On 28/02/13 13:15, Simon McVittie wrote:
On 28/02/13 09:39, Daniel Pocock wrote:
Has anybody had experience controlling access to git
repositories
I'm just wondering if anybody else looked at this code or their license[1]?
License discussion stopped at [2], not clear if it the license is
definitely rejected or not, my impression of the clause is that it
doesn't mandate a splash screen, it just means you can't put attribution
in small
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 22/03/13 00:00, Andrew Shadura wrote:
It would also be useful for me to know which other accounting
packages are popular in the free software community and whether
people would use PostBooks if it was packaged. I tried GnuCash,
but it
On 22/03/13 00:18, Andrew Shadura wrote:
Hello,
On Fri, 22 Mar 2013 00:09:20 +0100
Daniel Pocock dan...@pocock.com.au wrote:
Would you be able to take over the ITP bug I created? Then you will
be the one closing it when you upload.
I did a search for any ITP bug before I filed one
On 28/03/13 11:06, Julien Cristau wrote:
Control: severity -1 important
I am raising this bug to critical, as it meets the definition makes
unrelated software on the system (or the whole system) break
No, it does not. hw will shut itself off before getting damaged.
Would you provide a
On 28/03/13 12:24, Martin Wuertele wrote:
* John Paul Adrian Glaubitz glaub...@physik.fu-berlin.de [2013-03-28 12:08]:
On 03/28/2013 11:47 AM, Daniel Pocock wrote:
Would you provide a guarantee to all users of wheezy that you will pay
for their laptop repair if this issue causes damage
On 28/03/13 12:32, Wouter Verhelst wrote:
On 28-03-13 11:47, Daniel Pocock wrote:
On 28/03/13 11:06, Julien Cristau wrote:
Control: severity -1 important
I am raising this bug to critical, as it meets the definition makes
unrelated software on the system (or the whole system) break
On 28/03/13 16:14, Thomas Goirand wrote:
On 03/28/2013 06:47 PM, Daniel Pocock wrote:
On 28/03/13 11:06, Julien Cristau wrote:
Control: severity -1 important
I am raising this bug to critical, as it meets the definition makes
unrelated software on the system (or the whole system) break
On 28/03/13 19:12, Lars Wirzenius wrote:
Perfection is unattainable. Every Debian stable release is buggy as
hell, and that's unavoidable, if we want to make any releases at all.
I don't think anybody raised the issue of perfection
This issue I've observed is a relative one - it was working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/03/13 18:59, Michael Biebl wrote:
Am 28.03.2013 18:48, schrieb Daniel Pocock:
I clearly understand your previous feedback and agree, that is
why I thought it might be helpful discussing this issue on
debian-devel, to get a feel for how
On 29/03/13 21:03, Svante Signell wrote:
Hi,
I recently purchased an Acer S7, having both a keyboard and a touch
screen. It is currently running Windows 8. Any chances of running Debian
GNU/Linux on that box? I've heard rumours that Ubuntu supports this
hardware, is that true?
I very
On 30/03/13 00:23, Dmitrijs Ledkovs wrote:
On 29 March 2013 20:03, Svante Signell svante.sign...@gmail.com wrote:
Hi,
I recently purchased an Acer S7, having both a keyboard and a touch
screen. It is currently running Windows 8. Any chances of running Debian
GNU/Linux on that box? I've
Are other people having trouble with empathy recently?
- about 8 months ago, I found the version in testing would not interact
with the version in squeeze
- about 3 months ago, I found it had improved a lot
- now, I find two users on the same LAN using the latest version from
wheezy can't
I've found that some default packages in Gnome are broken if
libgl1-mesa-dri is not installed
libgl1-mesa-dri is only installed on upgrade if the package xorg is
present in squeeze, but that is not always the case according to popcon:
http://qa.debian.org/popcon.php?package=xorg
On 01/04/13 14:37, John Paul Adrian Glaubitz wrote:
On 04/01/2013 11:59 AM, Daniel Pocock wrote:
I've found that some default packages in Gnome are broken if
libgl1-mesa-dri is not installed
(...)
While I've filed a bug against empathy (that is where I observed the
problem), I suspect
On 01/04/13 22:04, John Paul Adrian Glaubitz wrote:
On 04/01/2013 09:59 PM, Daniel Pocock wrote:
Agreed, but that doesn't complete the picture, as libgl1-mesa-glx
doesn't depend on libgl1-mesa-dri:
$ apt-cache depends libgl1-mesa-glx
...
Recommends: libgl1-mesa-dri
Well
On 02/04/13 01:04, Josselin Mouette wrote:
Le lundi 01 avril 2013 à 22:04 +0200, John Paul Adrian Glaubitz a
écrit :
$ apt-cache depends libgl1-mesa-glx
...
Recommends: libgl1-mesa-dri
Well, Recommends are installed by default, aren't they? However, I'm
not sure why it
On 02/04/13 09:24, Andreas Tille wrote:
[moving to debian-devel as Neil suggested]
On Mon, Apr 01, 2013 at 04:52:30PM +0100, Neil McGovern wrote:
As a general hint, requests that are obviously correct get approved
very quicky.
I can confirm this - thanks for the release team.
Things that
On 02/04/13 14:00, Cyril Brulebois wrote:
Daniel Pocock dan...@pocock.com.au (02/04/2013):
To put this in context, I recently found that one of the packages I
depend on (libasio-dev) is actually orphaned. It is mentioned in
PTS, but I was never proactively alerted by anything such as
lintian
On 02/04/13 19:57, Ian Jackson wrote:
Vincent Bernat writes (Re: Bug#455769: same problem on wheezy + Thinkpad
X220T):
❦ 28 mars 2013 20:38 CET, Thomas Goirand z...@debian.org :
Unless you are the original reporter and you need to
decide in order to fill the bug, please don't. That's the
On 02/04/13 18:35, Thomas Goirand wrote:
On 04/02/2013 07:52 PM, Daniel Pocock wrote:
The problem is, how to pass this benefit on to users without either (a)
marking every bug RC
There is absolutely no point doing that. Unless we are really
really close from releasing (like right now), even
For anybody who wants to hack away at an enhanced diagram for their own
*-buildpackage workflow, I've attached to my blog a copy of the raw dia file
http://danielpocock.com/sites/danielpocock.com/files/release-packaging-workflow.dia
It is shared under the GPL v3 terms
--
To UNSUBSCRIBE,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/04/13 22:43, Christian PERRIER wrote:
Quoting ian_br...@fastmail.net (ian_br...@fastmail.net):
If Debian bug report #684128 proves anything, it is that you will never
convince anyone with technical argument, facts advanced in support of
I notice this bug was downgraded below the RC threshold and appears to
have been missed so far:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612402
Basically, if somebody has UUID syntax in /etc/fstab, their root FS
isn't mounted and they can't boot
Patches are included, should this be
On 05/04/13 14:06, Ian Jackson wrote:
Daniel Pocock writes (SI units (was Re: failure to communicate)):
It may actually be useful for the technical committee to review what is
on the wiki and make some general statement about Debian's position (if
they haven't done so in the past
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/04/13 15:47, Neil Williams wrote:
On Sun, 07 Apr 2013 15:25:43 +0200 Daniel Pocock
dan...@pocock.com.au wrote:
I notice this bug was downgraded below the RC threshold and
appears to have been missed so far:
It was only pushed to RC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 07/04/13 18:15, Ben Hutchings wrote:
On Sun, 2013-04-07 at 16:19 +0200, Daniel Pocock wrote:
On 07/04/13 15:47, Neil Williams wrote:
On Sun, 07 Apr 2013 15:25:43 +0200 Daniel Pocock
dan...@pocock.com.au wrote:
I notice this bug
On 08/04/13 13:53, Wouter Verhelst wrote:
On 08-04-13 08:53, Daniel Pocock wrote:
I'm not suggesting that squeeze systems were installed that way by
default, although people who have migrated an FS from a raw partition
to an LV may have this in fstab.
And that fact alone makes it a non-RC bug
On 09/04/13 17:54, Bernd Zeimetz wrote:
On 02.04.2013 22:48, Thomas Goirand wrote:
On 04/02/2013 12:16 AM, Luca Falavigna wrote:
In a perfect world there wouldn't be any need for a NEW queue at all.
But we have to face with the reality.
We try to do our best to improve things where we can.
Fedora recently put in Yubikey for their packagers[1], although they are
only half way there, supporting sudo but not web auth so far.
Similar things could probably happen in Debian.
I've proposed two-factor authentication as a potential area for a GSoC
project[2], two things come up:
a)
On 11/04/13 21:25, Tollef Fog Heen wrote:
]] Luca Filipozzi
I can help with a GSoC but I think DSA would prefer to lean in the direction
of
the above.
I'm also happy to help with it. I have a bit of experience with the
yubikey tokens, and at least one of the upstreams is on the path
On 12/04/13 07:56, Thomas Goirand wrote:
On 04/12/2013 03:25 AM, Tollef Fog Heen wrote:
The Yubikey neo can run the java applet thingies, it seems, so it can
act as a GPG token too.
Please, please, please ... no java!!!
That's a security nightmare. I think we'd be less safe with
than
I came across this on Planet Debian
http://rb.doesntexist.org/blog//posts/lack_of_cooperation_from_ubuntu/
I'm guessing that Ubuntu may not have pushed the changes to sid because
of the freeze, that may well be the answer to Rogério's questions.
Nonetheless, with derivatives and Debian itself
On 25/04/13 13:50, Simon Chopin wrote:
Hi,
Nicolas Dandrimont and I are currently working on a project proposal for
the Google Summer of Code to use the messaging system written by Fedora,
fedmsg[0][1], within the Debian infrastructure (some of you might have seen
the various ITPs related to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 25/04/13 18:07, Simon Chopin wrote:
Quoting Daniel Pocock (2013-04-25 17:34:03)
ZeroMQ is a very lightweight solution - it is brokerless (like
multicast) so won't necessarily support the requirement for
durable subscriptions (keeping
I'm just wondering if anybody else has looked at OpenMAMA or seen any
potential problems for packaging it?
http://www.openmama.org/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Several students have inquired about the possibility of doing a
real-time communication (RTC) project for GSoC, one has already started
his application[1] and a few others have been corresponding with me by
email.
Rather than letting the students guess what we need or want, I'm hoping
some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 29/03/13 08:19, Salvo Tomaselli wrote:
What we need is someone who can reliably reproduce the issue and help
with debugging.
I've had a probably related problem, without using GNOME
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455769#59
Just following up on the earlier discussion about VCS (not just git) in
the packaging workflow
Would there be any hard objection to a source package format based on
git-bundle?
In other words, dpkg-source would extract all repository history (or all
of the branch used to build the package)
) as the content of such source packages. Bernhard,
could you comment on what you understood my intention was?
On 03/05/13 18:50, Bernhard R. Link wrote:
* Daniel Pocock dan...@pocock.com.au [130501 21:28]:
Would there be any hard objection to a source package format based on
git-bundle?
I think a git
On 04/05/13 08:17, Wouter Verhelst wrote:
On 04-05-13 05:04, Charles Plessy wrote:
In any case, please refrain passive-aggressive statements on other people's
projects.
Except that this time the project we're talking about was one person
asking another person can you clarify what I
I started a thread[1] on maven-user yesterday to try and understand
whether Maven's convenience with binary artifacts extrapolates to
convenience working with source
One of the first answers even suggested I should go and see the Debian
folks (the FTP master's reputation for keeping binary
On 11/05/13 04:35, Paul Wise wrote:
I think you want to discuss this on the debian-java list instead.
The reason I posted here is that the concept is just as viable for other
languages with their own distribution systems (e.g. R and Drupal both
have their own package distribution mechanisms)
There have been various discussions about how to change the release process
I'm not personally convinced that the process is fundamentally flawed.
If there are still as many wheezy systems in 10 years as there are
Windows XP machines in corporations today, then people won't remember
the freeze
On 12/05/13 21:11, Bernd Zeimetz wrote:
On 05/11/2013 10:12 AM, Daniel Pocock wrote:
On 11/05/13 04:35, Paul Wise wrote:
I think you want to discuss this on the debian-java list instead.
The reason I posted here is that the concept is just as viable for other
languages with their own
There seem to be a few new discussions about these possible solutions
As well as the traditional init scripts, I've worked with systemd on
Fedora and SMF on Solaris. Out of all possible solutions, I don't have
any strong feelings about which solution Debian should go with at this
stage.
On 30/05/13 13:19, Bastien ROUCARIES wrote:
On Thu, May 30, 2013 at 12:50 PM, Dennis van Dok denni...@nikhef.nl wrote:
On 26-05-13 20:02, Bastien ROUCARIES wrote:
On Sat, May 25, 2013 at 2:27 PM, Charles Plessy ple...@debian.org wrote:
Hi Dennis and everybody,
somewhat related to this, I
Hi,
There have been multiple complaints about the new Gnome popup asking for
the root password
I opened a bug for discussion about the issue, but it was closed by
another DD (not the maintainer) - [1]. Other users have come across the
bug too and requested attention for it with the same
On 09/06/13 19:20, Michael Banck wrote:
On Sun, Jun 09, 2013 at 06:45:18PM +0200, Daniel Pocock wrote:
There have been multiple complaints about the new Gnome popup asking
for the root password
I am not sure what you are complaining about - that you need to specify
the root password
On 10/06/13 10:21, Alexey Serikov wrote:
A few points:
1) if your user is part of sudo group, most of the time gnome will ask
for your user's password instead of root's.
2) Debian is a finite set of software. It provides packages (literally
thousands of them) that are stable, safe and
On 10/06/13 14:12, Simon McVittie wrote:
On 10/06/13 12:34, Daniel Pocock wrote:
a) a web site displaying a PolicyKit popup that resembles the wording
of the Debian popup
GNOME Shell does mitigate this by using a distinctive UI for
system-modal dialogs, which makes use of the fact
On 10/06/13 16:51, Simon McVittie wrote:
On 10/06/13 15:36, Timo Juhani Lindfors wrote:
Simon McVittie s...@debian.org writes:
* ability to use system-modal prompting or a secure input path
(partially done by PK under GNOME Shell, likely to get better
under Wayland, not
On 11/06/13 00:37, Jens Roder wrote:
Hello,
just like to add that today this feature with the popup blocked my gnome
within the suspend procedure, which I did not see but got a hot running
laptop in the bag. When I opened the laptop again I saw the problem and when
clicking on cancel, the
On 11/06/13 01:11, Michael Banck wrote:
Hi Daniel,
On Mon, Jun 10, 2013 at 09:24:39PM +0200, Daniel Pocock wrote:
Every copy of jessie could be distributed with one of the red hoods
referred to in this article:
http://www.guardian.co.uk/world/2013/jun/09/edward-snowden-nsa-whistleblower
On 28/05/13 03:02, Marco d'Itri wrote:
Now that we are done with systemd for the time being, can we have the
flame war about replacing Exim with Postfix as the default MTA?
Are there any objections other than but I like it this way!?
What about replacing SMTP?
--
To UNSUBSCRIBE,
On 11/06/13 22:56, Jeremy Stanley wrote:
On 2013-06-12 02:09:24 +0800 (+0800), Chow Loong Jin wrote:
On Tue, Jun 11, 2013 at 08:01:58PM +0200, Daniel Pocock wrote:
What about replacing SMTP?
With what?
With ESMTP, of course!
Something that doesn't have these limitations:
http
On 12/06/13 00:02, Jeremy Stanley wrote:
On 2013-06-11 23:50:01 +0200 (+0200), Daniel Pocock wrote:
Something that doesn't have these limitations:
http://tools.ietf.org/html/rfc2487#section-7
[...]
That basically just makes the case for relying on (E)SMTP only for
transporting messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/06/13 12:29, Neil McGovern wrote:
On Wed, Jun 12, 2013 at 08:08:17AM +0200, Daniel Pocock wrote:
On 12/06/13 00:02, Jeremy Stanley wrote:
On 2013-06-11 23:50:01 +0200 (+0200), Daniel Pocock wrote:
Something that doesn't have
On 12/06/13 14:41, Jonathan Dowland wrote:
On Wed, Jun 12, 2013 at 08:08:17AM +0200, Daniel Pocock wrote:
OpenPGP and S/MIME don't guarantee anonymity as they don't (and can't
really) encrypt the headers/envelope
Erm, they also identify the recipients, as it's the recipients key to which
On 12/06/13 21:35, Jeremy Stanley wrote:
On 2013-06-12 08:08:17 +0200 (+0200), Daniel Pocock wrote:
On 12/06/13 00:02, Jeremy Stanley wrote:
That basically just makes the case for relying on (E)SMTP only for
transporting messages, but leveraging OpenPGP or S/MIME to provide
authentication
On 13/06/13 12:59, Jonathan Dowland wrote:
On Wed, Jun 12, 2013 at 09:41:27PM +0200, Daniel Pocock wrote:
DFSG #4: Our priorities are our users and free software
A court prosecuting/persecuting one of our users is not in scope
I'm now struggling to understand which side of the argument you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 16/06/13 10:05, Andrei POPESCU wrote:
On Du, 16 iun 13, 09:49:41, Holger Levsen wrote:
Hi,
I'm at loss with what to do with #710047. (random freeze since
wheezy)
More information would be nice, redirect to debian-user?
And just
On 15/06/13 13:04, David Weinehall wrote:
On Thu, May 30, 2013 at 12:15:03PM +0200, Bjørn Mork wrote:
The issue that worries me most about these desktop notification plans is
the possibility that some package may decide to unnecessarily drop
support for non-desktop systems, adding
There have been various discussions about GnuPG's default use of SHA1, e.g.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612657
which impacts the archive pseudo-package but is also relevant for the
gnupg* packages
However, are such issues at the discretion of package maintainers and
On 27/06/13 21:44, Florian Weimer wrote:
* Daniel Pocock:
However, are such issues at the discretion of package maintainers and
upstream, or is it useful to have a uniform Debian approach to
cryptographic strength?
Keep in mind that RFC 4880 (OpenPGP) hard-codes SHA-1 in several
places
On 28/06/13 09:34, Thijs Kinkhorst wrote:
On Thu, June 27, 2013 22:16, Daniel Pocock wrote:
On 27/06/13 21:44, Florian Weimer wrote:
* Daniel Pocock:
However, are such issues at the discretion of package maintainers and
upstream, or is it useful to have a uniform Debian approach
I notice one of my package fails on hurd-i386, kfreebsd-* and sparc due
to various dependencies:
https://buildd.debian.org/status/package.php?p=resiprocatesuite=sid
and it appears these dependencies have been unavailable for a long time.
The bottom line is that urgent fixes in the package are
On 18/07/13 22:44, Adam D. Barratt wrote:
On Thu, 2013-07-18 at 12:46 +0200, Daniel Pocock wrote:
I notice one of my package fails on hurd-i386, kfreebsd-* and sparc due
to various dependencies:
https://buildd.debian.org/status/package.php?p=resiprocatesuite=sid
and it appears
On 21/08/13 19:08, Clint Byrum wrote:
Excerpts from Kevin Chadwick's message of 2013-08-21 08:45:27 -0700:
My point of view is that Debian Stable should be aiming for whatever
they believe the sweet point between stable and so usable without having
problems is and maximising security. Aka
After a build fails on the buildd, it would be really useful to have the
build run again twice with make -i and log the output of the second retry
Obviously I could hack something like this into debian/rules:
make || make -i ; make -i ; exit 1
but it would be nice to have a centrally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/09/13 01:20, Roger Leigh wrote:
On Sat, Sep 07, 2013 at 11:28:31PM +0200, Daniel Pocock wrote:
After a build fails on the buildd, it would be really useful to
have the build run again twice with make -i and log the output
of the second
Some of the upstream projects I work on use travis-ci.org for continuous
integration
In some cases I'd like to configure builds that depend on packages from
Debian unstable, but I'm not sure of the Ubuntu or travis way of doing
that, has anybody dealt with this before? Or is there a Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 15/09/13 23:34, Roger Leigh wrote:
On Tue, Sep 10, 2013 at 10:42:09PM +0200, Daniel Pocock wrote:
Some of the upstream projects I work on use travis-ci.org for
continuous integration
In some cases I'd like to configure builds
PostBooks distributes their schema as a Postgres binary dump file for
use with pg_restore
They are available for download here (not in the source tarball):
http://sourceforge.net/projects/postbooks/files/03%20PostBooks-databases/4.1.0/
The pg_dump documentation explains the binary format
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm particularly keen to see communication packages working on as many
architectures as possible because otherwise two-way communications
opportunities are missed if some users are excluded.
In short, I'm not formally volunteering, but if people
Andrew and I have been going over the PostBooks packages, first uploads
in the NEW queue
We have an alioth group now:
https://alioth.debian.org/projects/pkg-xtuple/
and a mailing list:
https://lists.alioth.debian.org/mailman/listinfo/pkg-xtuple-maintainers
so please join us. The
On 20/09/13 09:07, Paul Wise wrote:
On Thu, Sep 19, 2013 at 2:42 PM, Daniel Pocock wrote:
PostBooks distributes their schema as a Postgres binary dump file for
use with pg_restore
What is their reason for using the binary format? Could they be
convinced to switch to or add something more
On 20/09/13 15:49, Paul Tagliamonte wrote:
On Fri, Sep 20, 2013 at 02:47:39PM +0100, Jonathan Dowland wrote:
On Fri, Sep 20, 2013 at 12:20:38PM +0200, Paul Wise wrote:
It is also impossible to patch the binary format unlike SQL.
Interesting. For the first time, I've realised there can be a
On 20/09/13 17:07, Paul Tagliamonte wrote:
On Fri, Sep 20, 2013 at 05:04:50PM +0200, Daniel Pocock wrote:
On 20/09/13 15:49, Paul Tagliamonte wrote:
On Fri, Sep 20, 2013 at 02:47:39PM +0100, Jonathan Dowland wrote:
On Fri, Sep 20, 2013 at 12:20:38PM +0200, Paul Wise wrote:
It is also
On 20/09/13 22:09, Bastian Blank wrote:
I would call code that hits such clear definitions too buggy to be
supported.
and what if many more existing packages are found to have similar issues?
http://debile.debian.net/sources/
One of my packages has some nice colours:
upstream is using qmake for PostBooks
qmake doesn't appear to provide a make dist facility, at least not the
way the project is currently configured.
Consequently, upstream tarballs tend to be snapshots of the developer
workspace, in one case, even including things like submodules,
.gitmodules
I've been trying to create menu items for postbooks and
postbooks-updater, for example:
http://anonscm.debian.org/gitweb/?p=collab-maint/postbooks-updater.git;a=blob;f=debian/menu;h=456d003f95312b27e3a1301057dd5b8dc3efca36;hb=86c8d75cc7297ba47b6398930c256d202011ab93
is a debian/menu file
On 29/09/13 20:09, Adam D. Barratt wrote:
On Sun, 2013-09-29 at 19:55 +0200, Daniel Pocock wrote:
I can see that update-menus is run during the dpkg install and I tried
running it again manually.
I can even find the .desktop file for Gnome after update-menus has run,
it looks OK
However
On 30/09/13 01:34, Charles Plessy wrote:
Le Sun, Sep 29, 2013 at 10:01:50PM +0200, Daniel Pocock a écrit :
For those feeling lazy, I suppose we can just grab the .desktop file
generated under /var by update-menus and copy it into our packages? Or
is there a more elegant way to manage
Can anybody suggest how to share the radius client config file between
these two packages?
radiusclient-ng is deprecated
freeradius-client is the same code, but supported with some fixes from
the FreeRADIUS community
Both packages use the same config file and currently they are declared
to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 28/11/13 21:04, Niels Thykier wrote:
Architecture Status ===
ia64 causes us concern for the following reasons:
* binutils issues (#718047, #720404), resulting in build failures
blocking transitions
* many
On 29/11/13 04:14, Steve Langasek wrote:
Hi Niels,
On Thu, Nov 28, 2013 at 09:04:56PM +0100, Niels Thykier wrote:
kFreeBSD was a technology preview, and has not generated enough user
interest to bring in sufficient install base to continue in this
state.
I wonder, how is the release team
On 29/11/13 18:23, Simon McVittie wrote:
On 29/11/13 16:36, Ian Jackson wrote:
It seems likely to me that that bug is, at root, a race of some kind.
And it just so happens that the race is lost on kFreeBSD - sometimes.
Detecting such a race is valuable to the project; it's certainly not a
1 - 100 of 751 matches
Mail list logo
