On Fri, Oct 14, 2022 at 03:37:29PM +0200, Marco d'Itri wrote:
> On Oct 14, Vincent Lefevre wrote:
>
> > > This is obviously convenient on Guillem's part, but we have to optimize
> > > systems by default for the general case and not just for dpkg -i.
> > This dpkg FAQ says that this is not benefi
On Oct 14, Vincent Lefevre wrote:
> > This is obviously convenient on Guillem's part, but we have to optimize
> > systems by default for the general case and not just for dpkg -i.
> This dpkg FAQ says that this is not beneficial for just dpkg,
> but also "for any application in the system".
[cit
On Fri, Oct 14, 2022 at 01:32:41PM +0800, Paul Wise wrote:
> On Thu, 2022-10-13 at 17:35 +0200, Julien Cristau wrote:
> > I'd prefer if we could make things work vs making things fail,
> > however loudly.
>
> There seem to be a few ways to deal with this transition:
(quotes reordered in Pauls pre
On Fri, Oct 14, 2022 at 01:32:41PM +0800, Paul Wise wrote:
> 4. Keep all non-free-firmware packages in non-free too. This would be
> backwards compatible, but may expose bugs in dak, debian-cd, apt and
> other tools, so IIRC this has been vetoed by the archive and CD teams.
> This also wouldn't res
On 2022-10-14 12:44:25 +0200, Marco d'Itri wrote:
> On Oct 14, Vincent Lefevre wrote:
> > > This is not "the Debian FAQ" but "the DPKG FAQ", which has been known to
> > > recommend awful things in the past.
> > But it is still considered in the present times by the dpkg developers.
> > Bug 923423
* Paul Wise [221014 01:35]:
> On Thu, 2022-10-13 at 17:35 +0200, Julien Cristau wrote:
>
> > I'd prefer if we could make things work vs making things fail,
> > however loudly.
>
> There seem to be a few ways to deal with this transition:
>
> 2. Add some code somewhere to automatically modify th
On Oct 14, Vincent Lefevre wrote:
> > This is not "the Debian FAQ" but "the DPKG FAQ", which has been known to
> > recommend awful things in the past.
> But it is still considered in the present times by the dpkg developers.
> Bug 923423 was closed several hours ago based on this dpkg FAQ:
This
On 2022-10-14 11:59:09 +0200, Marco d'Itri wrote:
> On Oct 14, Vincent Lefevre wrote:
>
> > The /etc/fstab file is created using by default ext4 with just
> > the errors=remount-ro option. However, the Debian FAQ recommends
> > the nodelalloc mount option to avoid performance degradation and
> >
A while ago I split the policykit-1 package into two binary packages:
- polkitd: the authorization daemon and associated utilities
- pkexec: the sudo-like tool to run arbitrary commands as root
policykit-1 is a transitional package to pull in both. Since upgrading
to upstream version 121 which us
On Oct 14, Vincent Lefevre wrote:
> The /etc/fstab file is created using by default ext4 with just
> the errors=remount-ro option. However, the Debian FAQ recommends
> the nodelalloc mount option to avoid performance degradation and
> preserve data safety:
This is not "the Debian FAQ" but "the DP
On Fri, Oct 14, 2022 at 10:52:01AM +0200, Santiago Ruano Rincón wrote:
> El 14/10/22 a las 13:32, Paul Wise escribió:
> > On Thu, 2022-10-13 at 17:35 +0200, Julien Cristau wrote:
> >
> > > I'd prefer if we could make things work vs making things fail,
> > > however loudly.
> >
> > There seem to b
El 14/10/22 a las 13:32, Paul Wise escribió:
> On Thu, 2022-10-13 at 17:35 +0200, Julien Cristau wrote:
>
> > I'd prefer if we could make things work vs making things fail,
> > however loudly.
>
> There seem to be a few ways to deal with this transition:
>
> 1. Document it in the release notes a
Package: wnpp
Owner: deba...@debian.org
Severity: wishlist
* Package name: py-rnp
Version : 0.1.0
Upstream Author : Daniel Wyatt
* URL or Web page : https://github.com/rnpgp/py-rnp
* License : (under investigation)
Description : Intent to Package [ITP]
Python bindin
13 matches
Mail list logo
