On Wed, 2018-08-01 at 12:42:35 +0800, David Bremner wrote:
> Guillem Jover writes:
> > Some packages might not show activity for longish periods of time,
> > because maintainers batch changes, for example to do at least one
> > upload per release, with general pac
Hi!
On Sat, 2018-09-08 at 20:18:10 +0200, Sylvestre Ledru wrote:
> Le 08/09/2018 à 18:39, Sean Whitton a écrit :
> > On Fri 07 Sep 2018 at 10:10PM +0200, Ruben Undheim wrote:
> > > However, I think the policy gives us a lot of freedom to choose (it
> > > is not very strict in this case).
> >
> >
Hi!
On Thu, 2018-10-04 at 08:38:09 +0800, Paul Wise wrote:
> On Thu, Oct 4, 2018 at 1:19 AM Lars Wirzenius wrote:
> > The problem: when a .deb package is installed, upgraded, or removed,
> > the maintainer scripts are run as root and can thus do anything.
Paul prompted a similar discussion the ot
Hi!
On Sun, 2018-09-09 at 21:32:36 +0100, Ian Jackson wrote:
> I am in favour of my "cut the child in half" rule, as a general rule.
While the intention there was good and it might apparently feel like
a good deterrent, I think the Solomonic Ruling is actually a very bad
fit for something like a
Hi!
On Thu, 2017-03-09 at 17:29:09 +, Ian Jackson wrote:
> I think the right way to solve this problem is to declare that:
[…]
> * If a library needs or wants additional software installed,
>if and when functions in that library are called, this
>should be documented in the /usr/share
Hi!
On Thu, 2017-02-23 at 17:57:33 +, Ian Jackson wrote:
> Simon McVittie writes ("Re: changelog practice, unfinalised vs UNRELEASED vs
> ~version"):
> > On Thu, 23 Feb 2017 at 12:53:40 +, Ian Jackson wrote:
> > > We could decorate the suite instead, but that does not have any
> > > effec
Hi!
On Fri, 2017-03-10 at 10:16:58 +, Simon McVittie wrote:
> I do not agree that dlopen()ing dependencies (what you have called "dynamic
> loading") is something we should encourage over normal linking with -lfoo
> (resulting in a DT_NEEDED entry, what you have called "static loading").
Than
On Tue, 2017-03-21 at 12:36:16 +, Ian Jackson wrote:
> Russ Allbery writes ("Re: Depends/Recommends from libraries"):
> > I think this would be a great way of introducing spurious bugs in our
> > distribution from [developers] who don't happen to read the README
> > file and miss dependencies t
Hi!
On Thu, 2017-03-23 at 17:34:58 +, Ian Jackson wrote:
> Russ Allbery writes ("Re: Depends/Recommends from libraries"):
> > It still feels like needless complexity to me,
>
> Here is an example I just found.
It does not turn out to be a very good example, I'm afraid. :)
> Try, in a fres
Hi!
On Thu, 2017-06-15 at 17:22:53 +0500, Andrey Rahmatullin wrote:
> On Thu, Jun 15, 2017 at 01:55:10PM +0200, Maria Bisen wrote:
> > It's been drawn to my attention the topic included in this thread:
> >
> > https://gcc.gnu.org/ml/gcc/2017-06/msg00084.html
> >
> > I've got the feeling that the
Hi!
On Fri, 2017-06-16 at 00:35:37 +1000, Stuart Prescott wrote:
> > What is `apt-helper cat-file' and how does it help ?
> $ apt-file search apt-helper
> apt: /usr/lib/apt/apt-helper
> $ /usr/lib/apt/apt-helper download-file
> http://deb.debian.org/debian/dists/sid/main/binary-amd64/Packages.x
Hi!
On Fri, 2017-06-23 at 12:22:34 +0100, Colin Watson wrote:
> The basic problem in init-select is of course the good old favourite of
> a conffile not behaving correctly when the package has been removed but
> not purged. This is probably worth fixing in unstable as follows, since
> init-select
Hi!
On Thu, 2017-06-29 at 13:58:39 +0100, Ian Jackson wrote:
> Paul Wise writes ("Re: Declarative packaging (Was: Re: Intended MBF:
> maintainer scripts not using strict mode)"):
> > IIRC last time we discussed this, the recommendation was to set an
> > environment variable that maintainer scrip
Hi!
On Tue, 2017-08-01 at 23:24:20 -0700, Paul Hardy wrote:
> I am creating a new XSLT file to convert DocBook 5 "refentry" (man page)
> files to texinfo files on a non-Debian system. I would like to bring
> DocBook 5 into Debian.
In a way, we already have some DocBook 5 support. :)
> Therefore
Hi,
On Sat, 2017-08-05 at 18:58:13 -0700, Sean Whitton wrote:
> A.2. Version 4.0.1
>
>Released August, 2017.
[…]
>9.6
>
>Packages installing a Free Desktop entry must not also install a
>Debian menu system entry.
Well this is still such terrible policy, and even
Hi!
While this sounds indeed interesting, I think it's impractical for at
least the two reason below:
On Tue, 2017-08-15 at 09:26:24 +0200, Christian Seiler wrote:
> AFAQ (Anticipated frequently asked questions):
>
> Q: How can you reconstruct a tarball from the installed system? Won't
>that
Hi!
On Mon, 2017-08-28 at 12:50:48 +0100, Colin Watson wrote:
> It did take a little while for the current format to evolve. For
> example, very early source packages had changes recorded in a
> "debian.README" file in somewhat ad-hoc formats.
>
> I think the current changelog format arrived wit
Control: forcemerge -1 843776
Hi!
On Fri, 2017-09-01 at 10:23:59 +0200, Hans-Christoph Steiner wrote:
> Package: dpkg-dev
>
> More and more packages are adding unicode files as unicode support has
> become more reliable and available. The package building process is not
> guaranteed to happen i
Hi!
On Fri, 2017-09-01 at 09:26:44 +0300, Adrian Bunk wrote:
> AFAIK the only place where we currently still need binary packages that
> have been built on a maintainer machine is for NEW, and after someone
> has implemented a solution for that there is no blocker left for
> allowing only source
Hi!
On Sun, 2017-09-10 at 07:12:08 +0100, Phil Wyett wrote:
> I found audacity now uses suil.
> http://git.drobilla.net/cgit.cgi/suil.git/tree/PACKAGING
>
> The bottom section of the doc:
>
> *** IMPORTANT GUIDELINES FOR PACKAGING SUIL ***
>
> The purpose of Suil is to abstract plugin UI toolk
On Mon, 2017-09-18 at 18:33:12 +0100, Steve McIntyre wrote:
> On Mon, Sep 18, 2017 at 05:46:34PM +0100, Ian Jackson wrote:
> >Steve McIntyre writes ("Re: Summary of the 2038 BoF at DC17"):
> >> It depends on how/where/why you're embedding 64-bit time,
> >> basically. If you're embedding a time_t (o
Hi!
First off, and just to be clear, I think decomissioning Alioth is a
good thing given its current state! Thanks for that.
One concern is whether we'll be needing to mass switch yet again git
repo URLs for the nth time? The nice thing about the current setup is
that it's decoupled from Alioth,
Hi!
On Tue, 2017-09-26 at 21:03:00 +0200, Ansgar Burchardt wrote:
> While it doesn't hurt here, I think people are on their own if they set
> POSIX_CORRECTLY or so (or include another incompatible `rmdir` in
> $PATH).
> Arguably `dpkg` could also run maintainer scripts in a more controlled
> envi
Hi!
So, dpkg 1.19.0 and 1.19.0.1 had a bug where the build target was not
being called when building packages.
Apparently this caused mass build failures, all due to packages (or
their helpers) being very Debian policy non-compliant! These are all
MUST requirements. Stuff like:
- binary-target
On Wed, 2017-10-18 at 11:54:57 +0100, Simon McVittie wrote:
> On Wed, 18 Oct 2017 at 11:57:55 +0200, Svante Signell wrote:
> > Building some packages for GNU/Hurd has been impossible in the past,
> > since also tests are run under fakeroot.
>
> Is there some reason why this would be Hurd-specific?
On Wed, 2017-10-18 at 11:30:29 +0100, Simon McVittie wrote:
> On Wed, 18 Oct 2017 at 11:36:41 +0200, Guillem Jover wrote:
> > Apparently this caused mass build failures, all due to packages (or
> > their helpers) being very Debian policy non-compliant! These are all
> > MUS
Hi!
I recently noticed that the getconf(1) interface is broken by design
when it comes to cross-compiling. It always returns the information
for the build system (GNU/dpkg terms), via the build system libc.
This means that any package using getconf(1) to get build-specific
information such as LFS
On Thu, 2017-10-19 at 10:51:30 +0100, Simon McVittie wrote:
> On Thu, 19 Oct 2017 at 10:50:36 +0200, Guillem Jover wrote:
> > When it comes to LFS, starting with dpkg 1.19.0 you can now use the
> > new «lfs» feature from the «future» feature area
>
> ... or if your upstrea
On Sun, 2017-11-12 at 18:27:16 -0500, Theodore Ts'o wrote:
> On Sun, Nov 12, 2017 at 09:13:42PM +0100, Mathieu Parent wrote:
> > There is another way to trim the locales: Use dpkg's "--path-exclude=".
> >
> > This also allows one to keep some locales. This is what we use at work
> > [1]. The probl
Hi!
On Sat, 2017-10-28 at 15:59:00 +, Niels Thykier wrote:
> * Please, review the specification plus implemenations and provide
>feedback on the proposal.
Very much appreciated, anytime.
> * Deadline for feedback: 2 weeks from today (but we are happy to extend
>it if people find th
On Wed, 2017-12-27 at 01:35:50 +0100, Philip Rinn wrote:
> > Collab-maint
> >
> >
> > If you want to allow other Debian Developers to work on your packages or
> > software, you can create projects within the
> > **Debian** group. Every Debian Developer has write access to projects
>
On Mon, 2017-12-25 at 21:10:37 +0100, Marco d'Itri wrote:
> On Dec 25, Alexander Wirt wrote:
> > Every user can create projects in their own namespace (similar to GitHub).
> What about git repository URLs?
> I am not looking forward to update all Vcs-Git and Vcs-Browser headers
> currently refer
Hi!
On Sat, 2015-09-26 at 21:12:57 +0300, Andy Beverley wrote:
> Package: wnpp
> Owner: Andy Beverley
> Severity: wishlist
> X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
>
> * Package name: libdpkg-parse-perl
> Version : 0.03
> Upstream Author : Adam
Hi!
On Mon, 2015-09-28 at 12:37:22 +0100, Andrew Beverley wrote:
> On Mon, 2015-09-28 at 13:12 +0200, Guillem Jover wrote:
> > On Sat, 2015-09-26 at 21:12:57 +0300, Andy Beverley wrote:
> > > Package: wnpp
> > > Owner: Andy Beverley
> > > Severity: wishl
On Thu, 2015-10-01 at 19:15:54 +0200, Matthias Klose wrote:
> question to the Hurd and KFreeBSD maintainers ... change that on these
> platforms too?
As it currently stands, this is not a question when it comes to
dpkg, that specific change is all or nothing. The Debian ←→ GNU
cpu mapping is globa
Hi!
On Mon, 2015-10-05 at 16:14:38 +, Niels Thykier wrote:
> As of debhelper/9.20151004, dh_makeshlibs is now using triggers rather
> than maintainer scripts to invoke ldconfig.
>
> * Lintian in untable + testing is already aware of this
> * Lintian has /not yet/ been backported. Lintian f
Hi!
On Tue, 2015-11-10 at 17:32:31 +, Mattia Rizzolo wrote:
> As part of the Reproducible Builds effort [0] we added a
> "reproducible/timeless" feature area to dpkg which exports -Wdate-time
> via CPPFLAGS [1].
>
> In our CI infrastructure we enabled that in Spring.
>
> We now think this is
Hi!
On Wed, 2015-12-30 at 16:46:23 +0300, Konstantin Khomoutov wrote:
> Two caveats:
>
> 1) Be aware that a user "foo" on your build system might have different
>UID than the user "foo" on the customer's system, and files' metadata
>has owning user and group recorded as a pair of integers
Hi!
[ Just posting to debian and fdo mailing lists, but this might be of
interest to other distros, please feel free to forward. ]
On Mon, 2016-01-18 at 18:25:36 +0100, Marco d'Itri wrote:
> On Jan 18, Steven Chamberlain wrote:
> > More background information follows. What do others think abo
Hi!
On Mon, 2016-01-18 at 09:57:27 -0800, Russ Allbery wrote:
> Steven Chamberlain writes:
> > I think it would be good for Debian to standardise on a single, good
> > arc4random implementation, available to any application that wants to
> > use it.
>
> > I'd like it to become ubiquitous, on all
Hi!
On Tue, 2016-02-02 at 20:23:08 +, Simon McVittie wrote:
> On 02/02/16 17:38, Jonathan Dowland wrote:
> > I must say that I do not like this proposal. The current situation does
> > result
> > in under-maintained packages requiring churn, but that's true for many
> > aspects
> > of them,
Hi!
On Tue, 2016-01-19 at 01:18:28 +0100, Guillem Jover wrote:
> [ Just posting to debian and fdo mailing lists, but this might be of
> interest to other distros, please feel free to forward. ]
This still applies.
> On Mon, 2016-01-18 at 18:25:36 +0100, Marco d'Itri wrote:
>
Hi!
On Mon, 2016-02-22 at 14:05:33 +, Jonathan Dowland wrote:
> [ for -devel: this is a reply to a post to debian-apache, please see
> https://lists.debian.org/debian-apache/2016/02/msg4.html ]
Inlining parts of that mail here:
> On Sat, 20 Feb 2016 01:09:18 +, Eric Mittelette wrot
Hi!
On Tue, 2016-03-15 at 15:32:40 -0700, Josh Triplett wrote:
> On Tue, Mar 15, 2016 at 11:15:16PM +0100, Joerg Jaspert wrote:
> > I've just activated a few changes to the archive we talk(ed) about for a
> > long time. And while it is not exactly the start of this release cycle,
> > it should sti
On Sun, 2016-03-20 at 20:31:13 +, Ben Hutchings wrote:
> On Sun, 2016-03-20 at 12:39 -0700, Josh Triplett wrote:
> > Leaving aside any other reasons: many packages have a versioned
> > dependency on iceweasel, and we don't have versioned provides.
> Yes we do, since dpkg 1.18.
Actually since
Hi!
On Fri, 2016-04-15 at 13:34:37 +0800, ChangZhuo Chen wrote:
> Package: wnpp
> Severity: wishlist
> Owner: "ChangZhuo Chen (陳昌倬)"
>
> * Package name: glide
There is already an unrelated glide source package in the archive.
Which also generates several *glide* binary packages. Namespacing
Hi!
Samuel Thibault recently reported in #818618 that the Binary field in
the .changes files does not get filtered to only include the binary
packages that are being uploaded, as documented in the ancient
doc/programming.sgml in dpkg 1.3.3 [P], current debian-policy and
now in the dpkg deb-changes
Hi!
On Thu, 2016-04-21 at 18:28:59 +0100, Steve McIntyre wrote:
> Control: severity -1 serious
> Justification: wasting many megabytes of space and download
Yes.
> We're shipping broken toolchain packages that are intentionally too
> large, and this is causing issues elsewhere. The "netinst" CD
Hi!
On Sat, 2016-04-30 at 21:57:47 +1000, Brian May wrote:
> Would appreciate it if somebody could confirm that the license is BSD
> and if so what version of the BSD license this is.
>
> https://github.com/mkdocs/mkdocs-bootswatch/blob/master/LICENSE
That looks like a BSD-2 clause license but w
Hi!
On Sun, 2016-05-15 at 21:45:55 +0200, Bálint Réczey wrote:
> 2016-05-15 20:49 GMT+02:00 Niels Thykier :
> > Bálint Réczey:
> >> I think making PIE and bindnow default in dpkg (at least for amd64) would
> >> be
> >> perfect release goals for Stretch.
> >
> > I support the end goal, but I suspe
On Tue, 2016-05-17 at 12:08:09 +0200, Matthias Klose wrote:
> I'm not a fan myself for turning on hardening flags in the compiler itself,
> but if you do that, then dpkg issues like https://bugs.debian.org/823869
> need to be addressed (whether all obscure build systems picking these up, or
> not).
Hi!
On Thu, 2016-05-12 at 17:39:57 +0200, Michael Biebl wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Michael Biebl
>
> * Package name: libgames-support
> Version : 1.0.2
> Upstream Author : Michael Catanzaro
> * URL : https://wiki.gnome.org/Apps/Games
> * Lic
Hi!
On Tue, 2016-05-10 at 19:17:15 -0300, 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 stretch release cycle. This
> > means dr
Hi!
On Wed, 2016-05-18 at 16:57:48 +, Sune Vuorela wrote:
> On 2016-05-18, Julien Cristau wrote:
> > Why aren't those bugs RC?
That's indeed a good question! It would probably be best if a neutral
party would do that. :)
> Either we give both users on old hardware a bad experience or all th
uggestions,
improvements, wording tweaks, etc.
Thanks,
Guillem
From d3a6f97736bade62a8945f91c22593f22f3e2ae4 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Sun, 22 May 2016 19:20:04 +0200
Subject: [PATCH] man: Document interaction between PIE and libraries
Prompted-by: Christian Seiler
---
man/dpkg-bu
Hi!
On Sun, 2016-06-19 at 23:44:50 +0800, ChangZhuo Chen wrote:
> Package: wnpp
> Severity: wishlist
> Owner: "ChangZhuo Chen (陳昌倬)"
> * Package name: pacapt
> Version : 2.3.8
> Upstream Author : Anh K. Huynh
> * URL : https://github.com/icy/pacapt
> * License
Hi!
On Sun, 2016-04-03 at 17:29:32 +, Niels Thykier wrote:
> The targets are "officially" mandatory and have been since 3.9.4
> (released in September 2012). Currently lintian and dpkg still forgive
> their absence to avoid auto-rejects and FTBFS bugs.
> However, Guillem and I would like to
Hi!
On Wed, 2016-05-04 at 02:06:56 +0200, Iustin Pop wrote:
> I'm very glad for the automatic debug packages, but I wonder if I'm
> doing something wrong since I get this warning:
>
> dpkg-genchanges: warning: package foo-dbgsym listed in files list
> but not in control info
>
> The pa
Hi!
I'd like to obsolete bzip2 (and lzma) as .deb compressors when building
binary packages. dpkg-deb currently emits warnings, this would turn them
into errors. For lzma it's fine in Debian as the archive has never
accepted them. For bzip2 there are currently 31 source packages that
produce some
Hi!
I'd like consider switching dpkg-deb --uniform-compression by default,
so that both control.tar and data.tar members use the same compression,
which currently would be xz (or gzip with -Zgzip).
This would give us more uniform and smaller packages. I think the d-i
people wanted something like
Hi!
On Wed, 2024-10-09 at 19:42:45 +0200, Ben Hutchings wrote:
> On Wed, 2024-10-09 at 10:26 +0100, Jonathan Dowland wrote:
> > On Mon Oct 7, 2024 at 8:58 AM BST, Marc Haber wrote:
> > > P.S.: Isnt it about time to rename exim4 to exim?
> >
> > Or apache2 to apache?
> The ASF is responsible for
Hi!
On Tue, 2024-10-08 at 11:37:52 +0200, Mazen Neifer wrote:
> Source: aiocoap
> Severity: important
> I would like to salvage this package because it is no more maintained.
>
> Last maintainer upload was more than 5 years ago.
> Last commit to git on salsa was on February 2019.
>
> If no obje
Hi!
On Tue, 2024-10-08 at 09:01:06 +0200, Simon Josefsson wrote:
> 1) Take current non-OpenBSD 'signify' source package and upload NEW
> 'signify-mail' with d/control modified as:
>
> Source: signify-mail
> ...
> Package: signify-mail
> Replaces: signify (<= 1.14-7)
>
> Do we need 'Breaks: signi
Hi!
On Mon, 2024-10-14 at 22:20:11 -0300, Marcos Rodrigues de Carvalho (aka oday)
wrote:
> Package: wnpp
> Severity: wishlist
> Owner: "Marcos Rodrigues de Carvalho (aka oday)"
> X-Debbugs-Cc: debian-devel@lists.debian.org, marcosrcarvalh...@gmail.com
>
> * Package name: go-nmap
> Version
Hi!
On Fri, 2024-10-04 at 18:21:01 +, Stefano Rivera wrote:
> Picking up a thread that started on debian-pyt...@lists.debian.org:
> https://lists.debian.org/msgid-search/14198883.O9o76ZdvQC@galatea
>
> Upstreams that care about supply chain security have been building
> mechanisms to authenti
Hi!
On Sun, 2024-09-08 at 08:55:58 +0530, Kathara Sasikumar wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Kathara Sasikumar
> X-Debbugs-Cc: debian-devel@lists.debian.org
>
> * Package name: sphinx-toolbox
> Version : 3.8.0
> Upstream Contact: Dominic Davis-Foster
> * URL
Hi!
On Wed, 2024-10-16 at 11:00:31 +0100, Colin Watson wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Colin Watson
> X-Debbugs-Cc: debian-devel@lists.debian.org
>
> * Package name: evalidate
> Version : 2.0.3
> Upstream Contact: Yaroslav Polyakov
> * URL : http
Hi!
On Wed, 2024-08-14 at 20:47:56 -0500, eevelweezel wrote:
> Package: wnpp
> Severity: wishlist
> Owner: eevelweezel
> X-Debbugs-Cc: debian-devel@lists.debian.org, eevel.wee...@gmail.com
> * Package name: legacycrypt
> Version : 0.0.3
> Upstream Contact: Christian Heimes
> * U
Hi!
On Fri, 2024-10-18 at 12:03:46 -0700, Mo Zhou wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Mo Zhou
> X-Debbugs-Cc: debian-devel@lists.debian.org
>
> * Package name : einops
> * URL : https://einops.rocks
> * License : MIT/Expat
> Programming Lang: Python
>
Hi!
On Tue, 2024-10-22 at 23:00:29 +0200, Serafeim (Serafi) Zanikolas wrote:
> I'd like to discover all installed linker scripts, for the purposes of
> #823531 (check for broken linker scripts files). it's not clear to me
> that there's a convention I could rely on to avoid brute forcing
> filetyp
Hi!
On Tue, 2024-10-22 at 00:00:21 +0200, Ben Hutchings wrote:
> On Mon, 2024-10-21 at 00:49 +0200, наб wrote:
> > On Sun, Oct 20, 2024 at 11:39:36PM +0200, Ben Hutchings wrote:
> > > On Sun, 2024-10-20 at 20:03 +0200, наб wrote:
> > > > I'd like to use an epoch so I'm asking for consensus per pol
Hi!
On Tue, 2024-11-12 at 11:02:53 +0100, Johannes Schauer Marin Rodrigues wrote:
> Quoting Hans (2024-11-12 09:35:08)
> > However, maybe a link is alo no more needed, even with a seperated /boot
> > partition.
>
> It's just a symlink. What's the harm?
For me, the default location of the symlink
Hi!
On Wed, 2024-09-25 at 00:39:10 +0200, Fay Stegerman wrote:
> * Guillem Jover [2024-09-24 17:45]:
> > Personally, I think fully migrating from zlib to zlib-ng would sound
> > great (even for trixie), but I guess we can take it slow if you do not
> > feel confident or ha
Hi!
On Tue, 2024-09-24 at 15:58:10 +0200, Mark Brown wrote:
> In the past I've pushed back on doing anything here since zlib is
> essential and it seemed better to be consistent over the ecosystem than
> to use a more niche implementation, and some of the early optimisation
> efforts had not worke
Hi!
On Fri, 2024-09-27 at 12:28:51 +, Francisco Vilmar Cardoso Ruviaro wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Francisco Vilmar Cardoso Ruviaro
> X-Debbugs-Cc: debian-devel@lists.debian.org, vil...@debian.org
> * Package name: golang-github-mitchellh-pointerstructure
> Ver
Hi!
On Thu, 2024-11-07 at 01:15:08 +, Colin Watson wrote:
> Source: python-catalogue
> Version: 2.1.0-6
> Severity: normal
> X-Debbugs-Cc: Andreas Tille , debian-devel@lists.debian.org
> https://pypi.org/project/catalogue/#history shows that 2.1.0 was yanked
> from PyPI, but it's what we curr
Hi!
On Thu, 2024-11-07 at 02:01:49 +, Colin Watson wrote:
> On Thu, Nov 07, 2024 at 02:42:08AM +0100, Guillem Jover wrote:
> > Given that I assume the current (non-retracted) upstream version is
> > going to be close to surpass the retracted one, I'd go for the +really
&g
Hi!
On Wed, 2024-11-06 at 17:28:38 +0500, Andrey Rakhmatullin wrote:
> On Wed, Nov 06, 2024 at 10:43:07AM +0100, Emanuele Rocca wrote:
> > As a final thought, given that new toolchain versions bring multiple
> > improvements over the years it's perhaps worth thinking about rebuilding
> > the archi
Hi!
On Tue, 2024-11-05 at 17:35:59 -0600, Aaron Rainbolt wrote:
> With all this in mind, I'd like to call some attention to a feature
> request made by Patrick Schleizer some time ago, whom I've copied on
> this email. The feature request suggests the addition of a new field to
> Debian's binary d
Hi!
[ I'll try to summarize the current discussion and status, what might
be blockers, and a potential incremental way forward. ]
On Wed, 2024-09-25 at 10:48:50 +0200, Mark Brown wrote:
> On Tue, Sep 24, 2024 at 05:45:49PM +0200, Guillem Jover wrote:
> > On Tue, 2024-09-24 at
Hi!
On Thu, 2024-11-14 at 00:48:18 -0800, Otto Kekäläinen wrote:
> I am the kind of person that gets hugely annoyed by things like this.
> Is anyone else feeling it?
>·
> Can we agree on calling Debian Enhancement Proposals DEP-N with a dash?
I'm also all for consistency, although I'm in general
Hi!
On Sun, 2024-11-24 at 16:09:42 +, Bastien Roucariès wrote:
> Le dimanche 24 novembre 2024, 12:06:26 UTC Bastien Roucariès a écrit :
> > I plan to implement freestanding architecture specification.
> > Following Toulouse debian mini debconf and javascript presentation it will
> > be really
Hi!
On Wed, 2024-12-04 at 14:37:45 +, Stefano Rivera wrote:
> Hi Guillem (2024.12.04_13:03:29_+)
> > > Are there other layers that could reasonably be used to implement a more
> > > general form of parallelism limiting based on system RAM? Ideally, we'd
> > > consolidate these implementati
Hi!
On Thu, 2024-11-28 at 10:54:37 +0100, Helmut Grohne wrote:
> I am one of those who builds a lot of different packages with different
> requirements and found that picking a good parallel=... value in
> DEB_BUILD_OPTIONS is hard. Go too low and your build takes very long. Go
> too high and you
Hi!
On Wed, 2024-12-04 at 14:03:30 +0100, Guillem Jover wrote:
> On Thu, 2024-11-28 at 10:54:37 +0100, Helmut Grohne wrote:
> > Are there other layers that could reasonably be used to implement a more
> > general form of parallelism limiting based on system RAM? Ideally, we&#x
Hi!
On Thu, 2024-12-05 at 09:23:24 +0100, Helmut Grohne wrote:
> On Wed, Dec 04, 2024 at 02:03:29PM +0100, Guillem Jover wrote:
> > On Thu, 2024-11-28 at 10:54:37 +0100, Helmut Grohne wrote:
> > > For one thing, I propose extending debhelper to provide
> > > --min-ra
Hi!
[ This was long ago, and the following is from recollection from the
top of my head and some mild «git log» crawling, and while I think
it's still accurate description of past events, interested people
can probably sieve through the various long discussions at the time
in bug reports a
Hi!
On Fri, 2024-12-27 at 12:46:02 -0500, Jonathan Kamens wrote:
> On 12/27/24 7:34 AM, Geert Stappers wrote:
> > Yeah, it feels wrong that dpkg gets file system code, gets code for one
> > particular file system.
>
> I disagree. If there is a significant optimization that dpkg can implement
> th
Hi!
On Sat, 2024-12-28 at 20:28:30 +0100, Gioele Barabucci wrote:
> There is a possible related, but independent, optimization that has the
> chance to significantly reduce dpkg install's time up to 90%.
>
> There is PoC patch [1,2] to teach dpkg to reflink files from data.tar
> instead of copyin
Package: wnpp
Severity: wishlist
Owner: Guillem Jover
* Package name: golang-github-xyproto-randomstring
Version : 1.2.0-1
Upstream Author : Alexander F. Rødseth
* URL : https://github.com/xyproto/randomstring
* License : BSD-3-clause
Programming Lang: Go
On Thu, 2025-01-23 at 17:06:04 -0800, Otto Kekäläinen wrote:
> Current https://dep-team.pages.debian.net/deps/dep14/ states that the
> default Debian branch name is 'debian/latest':
>
> > In Debian this means that uploads to unstable and experimental should be
> > prepared either in
> > the debia
Hi!
On Sat, 2025-02-01 at 22:33:16 +0100, Abou Al Montacir wrote:
> On Sat, 2025-02-01 at 17:35 +0100, Abou Al Montacir wrote:
> > But also, in this particular case, it's not the issue of the spec but of a
> > particular tool trying to enforce the rule.
> >
> > I'll file a bug to fix it.
> I fin
Hi!
On Fri, 2024-12-06 at 09:22:43 -, Sune Vuorela wrote:
> Though I do also think we have a hole in our dependency system here.
I think most of the needed pieces are there already though.
> if I set my system up to be in entish, I don't want to chase translation
> files all over the package
Hi!
On Mon, 2025-01-20 at 13:21:32 -0700, Sam Hartman wrote:
> TL;DR: Is it time for the rest of Debian to stop conforming to HURD's
> lack of maximums for path and hostname? By thispoint I think we
> recognize those lack of maximums as an anti-pattern for DOS prevention
> and other security reaso
Hi!
On Mon, 2025-01-27 at 06:28:59 -0600, G. Branden Robinson wrote:
> At 2025-01-27T12:27:12+0100, IOhannes m zmölnig (Debian GNU|Linux) wrote:
> > as for the original subject of this thread: what's actually wrong with
> > 'debian/main' instead of 'debian/latest'? i personally do not really
> >
Hi!
On Sun, 2025-01-05 at 17:44:33 +0100, Santiago Vila wrote:
> I've just uploaded gettext 0.23.1-0.1 for experimental.
Ah, great, thanks!
> In most cases, the failure is like this:
>
> make[3]: Entering directory '/<>/po'
> *** error: gettext infrastructure mismatch: using a Makefile.in.in fr
Hi!
On Sun, 2025-01-05 at 19:37:44 +0100, Santiago Vila wrote:
> El 5/1/25 a las 19:15, Guillem Jover escribió:
> > I think this indicates a problem in the upstream autotools support,
> > and it might be better to try to fix that instead of adding what seems
> > like a work
Hi!
On Mon, 2024-12-23 at 13:20:39 +0100, Chris Hofstaedtler wrote:
> * Julian Andres Klode [241223 12:49]:
> > Something still pulls in gpgv there
> > which is unfortunate, we lack a 5MB savings.
I think that would be gpgv being Priority: important, which makes
debootstrap and friends pull it i
Hi!
On Mon, 2025-01-06 at 16:45:54 +0100, Simon Josefsson wrote:
> Santiago Vila writes:
> > Note for Guillem: I've included your suggested fix in the bug template.
Great, thanks!
> I don't think we should patch upstream code for things that aren't clear
> upstream bugs. Patching upstream code
Hi!
On Wed, 2025-01-15 at 09:43:36 -0700, Sam Hartman wrote:
> My proposal is to move the man pages into libpam-doc.
> I'm not actually convinced that normal Debian users need man pages for
> all the pam modules on all Debian systems, and a suggests relationship
> should be sufficient.
> If people
801 - 900 of 910 matches
Mail list logo
