also sprach Joerg Jaspert [2013.01.24.2017 +1300]:
> > And say that a year later 2.3 comes out and it's the bee's knees
> > because it fully replaces 1.1 except that the configuration cannot
> > be automatically migrated, and all the power users on #debian-devel
> > persuade you to backport it, wh
martin f krafft writes:
> also sprach Russ Allbery [2013.01.24.1856 +1300]:
>> I always understood that I had a responsibility as a backporter to
>> release security fixes as necessary, and if I wasn't going to do that,
>> I shouldn't upload the backport in the first place. I handle backport
>>
Package: wnpp
Severity: wishlist
Owner: Brian Hodges
* Package name: ad2openldap
Version : 0.10
Upstream Author : FHCRC SciComp
* URL :
https://github.com/FredHutch/IT/tree/master/general/ad2openldap
* License : GPLv3
Programming Lang: Python
Description
On 13101 March 1977, martin f. krafft wrote:
>> I always understood that I had a responsibility as a backporter to release
>> security fixes as necessary, and if I wasn't going to do that, I shouldn't
>> upload the backport in the first place. I handle backport security fixes
>> exactly the way t
also sprach Russ Allbery [2013.01.24.1856 +1300]:
> I always understood that I had a responsibility as a backporter to release
> security fixes as necessary, and if I wasn't going to do that, I shouldn't
> upload the backport in the first place. I handle backport security fixes
> exactly the way
On Thu, Jan 24, 2013 at 12:39 AM, martin f krafft wrote:
> Hey folks,
>
> For a while now, the backports archive sets "ButAutomaticUpdates:
> yes" in its Release file, causing packages in the archive to be
> pinned with priority 100, rather than 1 (which was previously the
> case).
>
> The effect o
On 01/22/2013 10:32 PM, Neil Williams wrote:
> On Tue, 22 Jan 2013 15:05:58 +0100
> Josselin Mouette wrote:
>
>> Le mardi 22 janvier 2013 à 14:57 +0100, Svante Signell a écrit :
>>> Worthwhile to read, definitely.
>> Yet full of misinformation, like the idea that using D-Bus makes a
>> service le
martin f krafft writes:
> While this might seem like a good idea at first — like when
> a security fix reaches the backports archive
Indeed.
> I am sure we all agree that the
> deny-all-but-what-is-explicitly-allowed policy is the better one. So
> why did we make the switch?
Because of securit
Chow Loong Jin writes:
> * But if it ever fails due to a bug within it, $DEITY help you, because
> you're going to have to go through everything mentioned in your first
> point here (save the issues with getting patches accepted)
Sometimes, debugging can be easier in monoli
Adam Borowski writes:
> Putting it another way:
> * the monolithic design has a huge freeness problem. To do anything not on
> a rigid list of features you need to learn the intricaties of a large
> complex system, and you can be certain that even if you manage to do so,
> your patches wi
Hey folks,
For a while now, the backports archive sets "ButAutomaticUpdates:
yes" in its Release file, causing packages in the archive to be
pinned with priority 100, rather than 1 (which was previously the
case).
The effect of this is that once a backport package is installed and
a new version a
On 24/01/2013 13:09, Adam Borowski wrote:
> [...]
> * the monolithic design has a huge freeness problem. To do anything not on
> a rigid list of features you need to learn the intricaties of a large
> complex system, and you can be certain that even if you manage to do so,
> your patches wil
On 24/01/2013 12:56, Paul Johnson wrote:
> [...]
> I've just learned that, if I build amd64 packages, I can't install
> them for testing because I've not also built the i386 packages.
> [...]
> That's really inconvenient! I don't understand why there has to be a
> linkage between the shared library
On Wed, Jan 23, 2013 at 08:45:49PM -0800, Russ Allbery wrote:
> Adam Borowski writes:
>
> > There are two ways to design a system:
> > * a monolithic well-integrated system, granting features and efficiency at
> > the cost of portability and hackability
> > * the traditional Unix way, with a st
This is a multiarch issue I had not considered before. Have you seen
it? I never wanted to be a "cross compiler", I really only want to
build amd64. But I have some i386 libraries for a particular program
(acroread).
I've just learned that, if I build amd64 packages, I can't install
them for test
Adam Borowski writes:
> There are two ways to design a system:
> * a monolithic well-integrated system, granting features and efficiency at
> the cost of portability and hackability
> * the traditional Unix way, with a stress on replaceable tools that do only
> one thing, granting freedom to
On Wed, Jan 23, 2013 at 08:16:40PM +0100, Philipp Kern wrote:
> On Tue, Jan 22, 2013 at 02:57:58PM +0100, Svante Signell wrote:
> > On Tue, 2013-01-22 at 14:41 +0100, Adam Borowski wrote:
> > > On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> > > > This blogpost is months old
Package: wnpp
Severity: wishlist
Owner: Joenio Costa
* Package name: libxml-compile-dumper-perl
Version : 0.13
Upstream Author : Mark Overmeer
* URL : http://search.cpan.org/dist/XML-Compile-Dumper/
* License : Perl
Programming Lang: Perl
Description :
Package: wnpp
Severity: wishlist
Owner: Joenio Costa
* Package name: libxml-compile-cache-perl
Version : 0.992
Upstream Author : Mark Overmeer
* URL : http://search.cpan.org/dist/XML-Compile-Cache/
* License : Perl
Programming Lang: Perl
Description :
* Jon Dowland:
> On Wed, Jan 23, 2013 at 10:46:33AM +0100, Josselin Mouette wrote:
>> You might find this useful:
>> http://np237.livejournal.com/33449.html
>>
>> I made this presentation in the hope to make such things easier to
>> understand for the sysadmin.
>
> Just for the record I found it
Package: wnpp
Severity: wishlist
Owner: Joenio Costa
* Package name: libxml-compile-tester-perl
Version : 0.90
Upstream Author : Mark Overmeer
* URL : http://search.cpan.org/dist/XML-Compile-Tester/
* License : Perl
Programming Lang: Perl
Description :
On Tue, Jan 22, 2013 at 02:57:58PM +0100, Svante Signell wrote:
> On Tue, 2013-01-22 at 14:41 +0100, Adam Borowski wrote:
> > On Tue, Jan 22, 2013 at 12:06:16PM +0100, Pau Garcia i Quiles wrote:
> > > This blogpost is months old but it makes some interesting reflections:
> > > http://www.pappp.net/
Package: wnpp
Severity: wishlist
Owner: Joenio Costa
* Package name: libbusiness-br-ids-perl
Version : 0.0022
Upstream Author : A. R. Ferreira
* URL : http://search.cpan.org/dist/Business-BR-Ids/
* License : Perl
Programming Lang: Perl
Description : Mo
On Wed, Jan 23, 2013 at 10:46:33AM +0100, Josselin Mouette wrote:
> You might find this useful:
> http://np237.livejournal.com/33449.html
>
> I made this presentation in the hope to make such things easier to
> understand for the sysadmin.
Just for the record I found it a good read, and mentally
Josselin Mouette writes:
> You might find this useful:
> http://np237.livejournal.com/33449.html
>
> I made this presentation in the hope to make such things easier to
> understand for the sysadmin.
I read that back then when you originally posted it and I still think
it's one of the most useful
Le mardi 22 janvier 2013 à 16:32 -0500, Theodore Ts'o a écrit :
> One of the big things which is incredibly frustrating with the D-Bus
> interfaces is that they aren't documented; and if they are documented,
> it's not obvious where.
I can only agree completely. It is very frustrating for some pl
26 matches
Mail list logo
