On Mon, 4 May 2015 at 19:12 Florian Ernst wrote:
> root@vzhost04:/usr/local/users/support/fe# apt-cache policy
> pve-kernel-2.6.32-37-pve
> pve-kernel-2.6.32-37-pve:
> Installed: 2.6.32-150
> Candidate: 2.6.32-150
> Version table:
> *** 2.6.32-150 0
> 500 http://download.proxmox.co
On 5 May 2015 at 19:45, Ansgar Burchardt wrote:
> * Packages currently at "important":
> - cron:
> Not needed in chroot/container environments.
Hm, i'd say it's not needed full-stop. There are systemd timer units
and e.g. systemd-cron that satisfy the need for periodic execution,
with
Neil Williams, le Wed 06 May 2015 20:34:15 +0100, a écrit :
> On Wed, 6 May 2015 20:36:25 +0200
> Samuel Thibault wrote:
>
> > Neil Williams, le Wed 06 May 2015 12:03:30 +0100, a écrit :
> > > If the patch *is* trivial and testable then it is up to the porters
> > > to arrange a fully tested NMU.
On May 06 2015, Neil Williams wrote:
> You can continue expecting others to do the work for you (which leads
> to bugs sliding down the priority list of some of the maintainers) or
> you can do the work.
It seems to me that you don't (want to?) realize that in some cases the
porters are doing all
On Wed, 6 May 2015 20:36:25 +0200
Samuel Thibault wrote:
> Neil Williams, le Wed 06 May 2015 12:03:30 +0100, a écrit :
> > If the patch *is* trivial and testable then it is up to the porters
> > to arrange a fully tested NMU.
>
> How can a porter fully test a package? Only maintainers really kn
Neil Williams, le Wed 06 May 2015 12:03:30 +0100, a écrit :
> If the patch *is* trivial and testable then it is up to the porters to
> arrange a fully tested NMU.
How can a porter fully test a package? Only maintainers really know
their package well, testing a package is rarely documented.
> Mai
On 2015-05-06 10:44, Thorsten Glaser wrote:
> [ with my m68k buildd maintainer and (ex-?) porter hat ]
>
> Aurelien Jarno dixit:
>
> >- debian-ports uses mini-dak instead of dak. It uses less resources and
> > brings some features that are useful for new architectures like
> > accepting binary
On Tue, 05 May 2015 09:17:02 +0200, Samuel Thibault wrote:
(replying only to -devel)
> * Appearing on packages' and maintainers' PTS
> pages like http://buildd.debian.org/bash and
> https://buildd.debian.org/sthiba...@debian.org
>
> This makes people aware of portability issues; when hurd-i386 m
On 2015-05-06 15:23:58 +0100, Neil Williams wrote:
> So, no, there isn't something broken - the uploader needs to file the
> bug as set out in the developer reference.
Thanks for the information. To make sure that it is done and since
bugs.debian.org didn't show any such bug, I've just filed such
On May 06, Neil Williams wrote:
> So, no, there isn't something broken - the uploader needs to file the
> bug as set out in the developer reference.
And please have this fixed in stable as well.
--
ciao,
Marco
pgp6i77j5JMCo.pgp
Description: PGP signature
On Wed, 6 May 2015 16:09:18 +0200
Vincent Lefevre wrote:
> On 2015-05-06 11:21:13 +0200, Marco d'Itri wrote:
> > On May 05, Ansgar Burchardt wrote:
> > > - nfacct:
> > > No idea why this is at Priority: important.
> > > -> demote to "optional"
> > Even extra... This is a very nic
On Wednesday, May 06, 2015 01:05:20 PM Alastair McKinstry wrote:
> * Package name: autosubmit
Please use a more specific package name for such a specialised package.
Thank you!
Thomas Koch
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe".
On 2015-05-06 11:21:13 +0200, Marco d'Itri wrote:
> On May 05, Ansgar Burchardt wrote:
> > - nfacct:
> > No idea why this is at Priority: important.
> > -> demote to "optional"
> Even extra... This is a very niche package and I have no idea why it is
> being installed everywhere!
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: python-matplotlib-venn
Version : 0.11
Upstream Author : Konstantin Tretyakov
* URL : https://pypi.python.org/pypi/matplotlib-venn
* License : MIT
Programming Lang: Python
Description
On 2015-05-06 11:21:13 +0200, Marco d'Itri wrote:
> dpkg --purge \
> discover discover-data libdiscover2 installation-report laptop-detect \
> nano tasksel tasksel-data task-english acpi acpid acpi-support-base \
> isc-dhcp-client isc-dhcp-common eject \
> nfacct libmnl0 libnetfilter-acct1
On Wed, May 06, 2015 at 02:21:06PM +0200, Martin Zobel-Helas wrote:
> ed needs to go back into important, so we can drop the other editors?
We have vim-tiny in important, which provides "ex", aka mostly ed.
Bastian
--
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a s
Hi,
On Wed May 06, 2015 at 14:09:30 +0200, Vincent Lefevre wrote:
> > Note that I believe this has changed over time: with the advent of VMs
> > and containers the expectations what a system should minimally provide
> > have become smaller.
> >
> > I'll not comment on where I see emacs and vim ;
On 2015-05-06 12:21:14 +0200, Ansgar Burchardt wrote:
> On 05/06/2015 11:34 AM, Martin Zobel-Helas wrote:
> > cron is part of POSIX.
>
> The problem here is what the expectations of an experienced UNIX person
> are... I hopefully count as having some experience, but I don't expect
> cron to be ava
On Wed, May 6, 2015 at 7:03 PM, Neil Williams wrote:
> Maintainers should help porters for release architectures wherever
> possible - for non-release architectures, that really isn't something
> you can do anything about except do the work yourselves.
One could argue the same for the official po
Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry
* Package name: autosubmit
Version : 3.0.0rc8
Upstream Author : Domingo Manubens-Gil
* URL : https://autosubmit.ic3.cat
* License : GPLv3
Programming Lang: Python
Description : Manage weather a
On Wed, May 06, 2015 at 06:26:19PM +0800, Paul Wise wrote:
>On Wed, May 6, 2015 at 6:21 PM, Ansgar Burchardt wrote:
>> On 05/06/2015 11:34 AM, Martin Zobel-Helas wrote:
>>> cron is part of POSIX.
>>
>> The problem here is what the expectations of an experienced UNIX person
>> are...
>
>Perhaps uni
On Wed, 6 May 2015 12:49:44 +0200
Samuel Thibault wrote:
> Neil Williams, le Wed 06 May 2015 11:39:29 +0100, a écrit :
> > It's not at all that the maintainers are "lazy" or that those
> > maintainers could have done anything differently. Those maintainers
> > have their workloads and have made a
Neil Williams, le Wed 06 May 2015 11:39:29 +0100, a écrit :
> If the wave simply moves on, leaving the port behind, it is harder to
> accept, very hard to regain momentum and high time that the porters
> ask themselves the hard question of whether it is worthwhile to
> continue, as the crest of the
On May 06, Ansgar Burchardt wrote:
> Note that I believe this has changed over time: with the advent of VMs
> and containers the expectations what a system should minimally provide
> have become smaller.
The differences between VMs and "normal" servers are very small, limited
only to a few packa
Neil Williams, le Wed 06 May 2015 11:39:29 +0100, a écrit :
> It's not at all that the maintainers are "lazy" or that those
> maintainers could have done anything differently. Those maintainers
> have their workloads and have made an assessment of their priorities.
I'm sorry I have to disagree her
On Wed, 6 May 2015 18:26:19 +0800
Paul Wise wrote:
> On Wed, May 6, 2015 at 6:21 PM, Ansgar Burchardt wrote:
> > On 05/06/2015 11:34 AM, Martin Zobel-Helas wrote:
> >> cron is part of POSIX.
> >
> > The problem here is what the expectations of an experienced UNIX
> > person are...
>
> Perhaps un
[ with my m68k buildd maintainer and (ex-?) porter hat ]
Aurelien Jarno dixit:
>- debian-ports uses mini-dak instead of dak. It uses less resources and
> brings some features that are useful for new architectures like
> accepting binary uploads when it "improves" the version even if it is
> no
On Wed, 6 May 2015 18:18:34 +0800
Paul Wise wrote:
> On Wed, May 6, 2015 at 6:11 PM, Neil Williams wrote:
>
> > You've admitted that the port cannot keep pace because it needs
> > changes to be made by maintainers who do not see the port as a
> > particular priority and that this blocks or imped
On Wed, May 6, 2015 at 6:21 PM, Ansgar Burchardt wrote:
> On 05/06/2015 11:34 AM, Martin Zobel-Helas wrote:
>> cron is part of POSIX.
>
> The problem here is what the expectations of an experienced UNIX person are...
Perhaps unix/posix tasks would satisfy such folks.
--
bye,
pabs
https://wiki.d
On 05/06/2015 11:34 AM, Martin Zobel-Helas wrote:
> On Tue May 05, 2015 at 20:45:09 +0200, Ansgar Burchardt wrote:
>> * Packages currently at "important":
>> - cron:
>> Not needed in chroot/container environments.
>> -> demote to "standard"
>
> RC.
>
> | important
> | Important p
On Wed, May 6, 2015 at 6:11 PM, Neil Williams wrote:
> You've admitted that the port cannot keep pace because it needs changes
> to be made by maintainers who do not see the port as a particular
> priority and that this blocks or impedes further changes. You've
> tried and failed to increase the l
On Wed, 6 May 2015 11:35:45 +0200
Samuel Thibault wrote:
> Neil Williams, le Wed 06 May 2015 09:47:36 +0100, a écrit :
> > Lack of widespread interest in any particular port is a problem with
> > that port not having widespread appeal.
>
> And lack of helping maintainers will entail a lack of wo
Neil Williams, le Wed 06 May 2015 09:47:36 +0100, a écrit :
> Lack of widespread interest in any particular port is a problem with
> that port not having widespread appeal.
And lack of helping maintainers will entail a lack of working stuff in
the port, and thus a more difficult appeal, and the lo
Hi,
On Tue May 05, 2015 at 20:45:09 +0200, Ansgar Burchardt wrote:
> * Packages currently at "important":
> - cron:
> Not needed in chroot/container environments.
> -> demote to "standard"
RC.
| important
| Important programs, including those which one would expect to find on
|
On May 06, Ansgar Burchardt wrote:
> But is this enough reason to keep w3m at priority standard? Personally I
> would rather use "ssh -D" or such than bothering with a rather limited
> text-mode browser.
Agreed.
--
ciao,
Marco
pgppFLgum_uM8.pgp
Description: PGP signature
On May 06, Josh Triplett wrote:
> That said, as mentioned in my response, I think rsyslog ought to stay
> important
> until something else replaces it. Logging of *some* kind is important.
We have journald. :-)
> Why, when it's just an "apt install at" away? It's one more running
> daemon. R
On May 05, Ansgar Burchardt wrote:
> I would like to re-evaluate what we change by default for Stretch, that
Me too.
Let's look at the problem from a different point of view. This is what
I remove when building cloud images for my employer's infrastructure:
dpkg --purge \
discover discover-da
On Wed, 6 May 2015 10:11:02 +0200
Samuel Thibault wrote:
> Neil Williams, le Wed 06 May 2015 08:56:38 +0100, a écrit :
> > Ports which take so long to develop that a stable release is
> > deemed unlikely will also struggle. That is a problem caused by that
> > port, not by the project or other ma
On Wednesday, May 6, 2015 5:21:14 AM EEST, Wookey wrote:
+++ Samuel Thibault [2015-05-06 01:09 +0200]:
Ansgar Burchardt, le Tue 05 May 2015 20:45:09 +0200, a écrit :
- info, texinfo, install-info:
I admit having used info only in desperation. Most documentation
comes in man page
Package: wnpp
Severity: wishlist
Owner: Thomas Goirand
* Package name: python-xstatic-angular-lrdragndrop
Version : 1.0.2.2
Upstream Author : Thai Tran
* URL : https://github.com/stackforge/xstatic-angular-lrdragndrop
* License : Apache-2.0
Programming Lang:
Neil Williams, le Wed 06 May 2015 08:56:38 +0100, a écrit :
> Ports which take so long to develop that a stable release is
> deemed unlikely will also struggle. That is a problem caused by that
> port, not by the project or other maintainers.
Not only. A typical scenario that does happen and can
On Tue, 05 May 2015 23:36:32 +0100
peter green wrote:
> >
> > > Perhaps we need a political decision here?
When considering maintainers not directly involved in the port,
motivation for doing work which only helps a particular port tends to
be easier to find when the objective of that port is t
Paul Wise writes:
>> - cron:
>> Not needed in chroot/container environments.
>> -> demote to "standard"
>
> A lot of packages ship cron jobs, I guess this means they will need to
> depend on cron?
They already have to depend on cron if it is required for proper
operation (or recom
43 matches
Mail list logo
