On Mon, 9 May 2016 23:13:19 +0200, Philipp Kern
wrote:
>On Sun, May 08, 2016 at 07:46:52PM +0200, Marc Haber wrote:
>> btrfs has suffered severe regressions since kernel 4.4, with the btrfs
>> upstream community only offering advice like "don't use so many
>> snapshots" or "say goodbye to existing
On Mon, 9 May 2016 18:42:52 +, Niels Thykier
wrote:
>But with that
>remark you make me feel like I have wasted my time and effort trying to
>the write the Jessie release notes.
You have not wasted your time. I do read the release notes, but I have
to admit that I only do so _after_ the releas
On Tue, 10 May 2016 08:13:40 +0200, Christoph Biedl
wrote:
> Why is feature X in the new Debian release broken?
> Because you haven't read the release notes.
>(Same for NEWS.Debian)
Would you instead want the text part from release notes and/or
NEWS.Debian pasted in IRC?
>While technically true,
On Wed, 11 May 2016 00:31:00 +0200, Matthias Klose
wrote:
>On 11.05.2016 00:17, Lisandro Damián Nicanor Pérez Meyer wrote:
>> On Saturday 07 May 2016 13:23:30 Ben Hutchings wrote:
>>> Last year it was decided to increase the minimum CPU features for the
>>> i386 architecture to 686-class in the st
* Marc Haber [2016-05-11 10:47:52 +0200]:
> >The third reason is the question of how much in detail the release
> >notes should actually be. In a strange way in the past they were too
> >short. That made me reluctant to suggest entries for low-popcon
> >packages as their significance doesn't matc
On Wed, 11 May 2016 17:03:05 +0200, Nicolas Dandrimont
wrote:
>* Marc Haber [2016-05-11 10:47:52 +0200]:
>
>> >The third reason is the question of how much in detail the release
>> >notes should actually be. In a strange way in the past they were too
>> >short. That made me reluctant to suggest e
Marc Haber writes:
> apt-listchanges drowns the user in the change logs, most of which are
> irrevant. I think of a solution that will show text that has been vetted
> by the package maintainer _and_ the release teams and that documents
> possible breakage during updates only. At this point, I do
Quoting Marc Haber (2016-05-11 19:01:03)
> On Wed, 11 May 2016 17:03:05 +0200, Nicolas Dandrimont
> wrote:
> >* Marc Haber [2016-05-11 10:47:52 +0200]:
> >
> >> >The third reason is the question of how much in detail the release
> >> >notes should actually be. In a strange way in the past they we
Package: wnpp
Severity: wishlist
Owner: Miriam Ruiz
* Package name: python-pattern
Version : 2.6
Upstream Author : Tom De Smedt
* URL : http://www.clips.ua.ac.be/pages/pattern
* License : BSD
Programming Lang: Python
Description : web mining module for
On May 11, Russ Allbery wrote:
> NEWS.Debian was the solution created for that problem, and it's not bad.
> It can be a bit too verbose in a few cases, but it's almost always worth
> reading carefully.
It would help if more people opened bugs on packages with NEWS.Debian
content which is not act
On 05/11/2016 07:01 PM, Marc Haber wrote:
> On Wed, 11 May 2016 17:03:05 +0200, Nicolas Dandrimont
> wrote:
>> * Marc Haber [2016-05-11 10:47:52 +0200]:
>>
The third reason is the question of how much in detail the release
notes should actually be. In a strange way in the past they were
On Wed, 11 May 2016 10:18:05 -0700, Russ Allbery
wrote:
>Marc Haber writes:
>> apt-listchanges drowns the user in the change logs, most of which are
>> irrevant. I think of a solution that will show text that has been vetted
>> by the package maintainer _and_ the release teams and that documents
Package: wnpp
Severity: wishlist
Owner: Daniel Stender
* Package name: bitkeeper
Version : 7.2ce
Upstream Author : Wayne Scott
* URL : https://www.bitkeeper.org/
* License : Apache-2.0
Programming Lang: C
Description : source code management system (SC
2016-05-11 18:27 Christian Seiler:
On 05/11/2016 07:01 PM, Marc Haber wrote:
On Wed, 11 May 2016 17:03:05 +0200, Nicolas Dandrimont
wrote:
* Marc Haber [2016-05-11 10:47:52 +0200]:
We could have a "show-release-notes" package containing a script that
scans (pre-upgrade) the installed packag
On Wed, May 11, 2016 at 07:27:30PM +0200, Christian Seiler wrote:
> At least on my system (default configuration) apt-listchanges shows
> only NEWS.Debian, not changelog.Debian. The only qualm I have with
> it is that there appears to be no option to abort the install after
> apt-listchanges displa
Marc Haber writes:
> On Wed, 11 May 2016 10:18:05 -0700, Russ Allbery wrote:
>> NEWS.Debian was the solution created for that problem, and it's not
>> bad. It can be a bit too verbose in a few cases, but it's almost
>> always worth reading carefully.
> I'd still like to have something that is
Daniel Stender writes:
> Distributed source control management/revision control system. Known as
> being used for the Linux kernel development before Git was created. The
> now have put the code under the Apache-2.0 license. Maybe some would
> like to use this, so it would do no harm to have it
http://www.openwall.com/lists/oss-security/2016/05/10/5 <-- link to
that discussion!
On Wed, May 11, 2016 at 4:55 PM, Russ Allbery wrote:
> Daniel Stender writes:
>
>> Distributed source control management/revision control system. Known as
>> being used for the Linux kernel development before Gi
On 11.05.2016 22:55, Russ Allbery wrote:
> Daniel Stender writes:
>
>> Distributed source control management/revision control system. Known as
>> being used for the Linux kernel development before Git was created. The
>> now have put the code under the Apache-2.0 license. Maybe some would
>> lik
Hi Daniel!
* Daniel Stender , 2016-05-11, 20:08:
Distributed source control management/revision control system. Known as
being used for the Linux kernel development before Git was created. The
now have put the code under the Apache-2.0 license. Maybe some would
like to use this, so it would do
Jakub Wilk writes:
> I strongly recommend against packaging software you don't personally
> use. This never goes well. (I say this as someone who did this mistake
> in the past, multiple times.)
I don't use most of my packages myself, and I don't think it was a
mistake to package them. The reason
On Mon, May 09, 2016 at 10:21:21AM -0700, Nikolaus Rath wrote:
> > Another way is to use btrfs (or zfs or perhaps LVM snapshots): whenever
> > something goes south in a way that's not trivial to recover, you can
> > restore with a couple commands and reboot. And if unbootable because,
> > for exam
On Wed, 2016-05-11 at 13:55 -0700, Russ Allbery wrote:
> Daniel Stender writes:
>
> >
> > Distributed source control management/revision control system. Known as
> > being used for the Linux kernel development before Git was created. The
> > now have put the code under the Apache-2.0 license. M
On Wed, 2016-05-11 at 19:25 -0400, Theodore Ts'o wrote:
> On Mon, May 09, 2016 at 10:21:21AM -0700, Nikolaus Rath wrote:
> >
> > >
> > > Another way is to use btrfs (or zfs or perhaps LVM snapshots): whenever
> > > something goes south in a way that's not trivial to recover, you can
> > > restore
On May 11 2016, Theodore Ts'o wrote:
> On Mon, May 09, 2016 at 10:21:21AM -0700, Nikolaus Rath wrote:
>> > Another way is to use btrfs (or zfs or perhaps LVM snapshots): whenever
>> > something goes south in a way that's not trivial to recover, you can
>> > restore with a couple commands and reboo
On Wed, 11 May 2016 13:54:04 -0700, Russ Allbery
wrote:
>Marc Haber writes:
>> On Wed, 11 May 2016 10:18:05 -0700, Russ Allbery wrote:
>
>>> NEWS.Debian was the solution created for that problem, and it's not
>>> bad. It can be a bit too verbose in a few cases, but it's almost
>>> always worth
On Wed, May 11, 2016 at 01:54:04PM -0700, Russ Allbery wrote:
> If someone has time and willingness, reviewing the contents of NEWS.Debian
> across all packages for the stable -> testing delta before the release
> sounds like a very useful thing to do.
>From what I've seen, this is very close to o
27 matches
Mail list logo
