Vincent Bernat:
> [...]
>
> [...] The policy doesn't state that a package
> must build when there is not enough disk space or memory. Maybe it would
> be far simpler to allow packages to fail to build if there is not enough
> CPUs.
>
On a related note: Having some way to declare minimum requirem
Chris Lamb:
> Hi -devel,
>
> There's a very active conversation happening on Hacker News right
> now entitled «What do you want to see in Ubuntu 17.10?»:
>
> https://news.ycombinator.com/item?id=14002821
>
> I haven't read every comment yet, but are there any feature requests
> that seem parti
ni...@thykier.net:
> Hi,
>
> Release date
>
>
> We plan to release on 2017-06-17.
>
> [...]
> In summary:
>
> * Deadline: > 2017-06-09 13:00 UTC <
>
> [...]
>
Hi,
Extra note, the dates / deadlines ment
Christoph Biedl:
> [...] Niels has mentioned declarative approaches which seem
> like a good idea. No idea about the status, though, and I'm interested
> in details if there already are some.
>
> Christoph
>
Hi,
Up till now, we deal with some easy wins by converting debhelper
maintscripts t
Simon McVittie:
> On Sat, 22 Jul 2017 at 12:28:04 +0200, Steffen Möller wrote:
>> And quite some packages in our
>> distribution do not really need to be installed as root if they were
>> installed where the user has write permissions. There would hence be
>> little overhead over what we have now.
intrigeri:
Hi,
Overall, this sounds like an interesting proposal and personally, I
agree that I think the Debian Linux ports would be better off with an
LSM enabled by default.
> What's the cost for Debian users?
> -
>
> AppArmor unavoidably breaks functionality
Stefan Fritsch:
> Hi,
>
> [...]
>
Hi,
Thanks for improving dbgsym integration. :)
> BTW, in some discussions some other questions were raised:
>
> - Is it really a good idea that foo-dbgsym depends on "foo (==
> foo-version)"? Wouldn't a Conflict or breaks on "foo (!= foo-version)"
> make m
Hi
We have written a new specification for supporting selective usage of
(fake)root during package builds (see attached file). The specification
defines a new field called "Rules-Requires-Root" (R³ for short) that
enables maintainers to define if and how their package requires root
during package
Niels Thykier:
> Hi
>
> We have written a new specification for supporting selective usage of
> (fake)root during package builds (see attached file). The specification
> defines a new field called "Rules-Requires-Root" (R³ for short) that
> enables maintainers to def
Hi Adam,
Thanks for the feedback. :)
Adam Borowski:
> [...]
>
> Have you perhaps gathered some data about how many packages would build
> reproducibly wrt the old state after a blind mechanical change to R³?
> I'd guess it's the vast majority (especially if you change MakeMaker).
>
I have not,
Hi,
Adam Borowski:
> On Tue, Nov 07, 2017 at 11:16:41AM +0100, John Paul Adrian Glaubitz wrote:
>> I think a possible solution is the plan we had inside Debian Ports which is
>> to introduce a Britney instance within Debian Ports and hence be able to
>> provide a Debian testing release.
>>
>> My d
Hi,
The debhelper compat level 11 is about to be finalized and we invite you
to test it out. There are no additional changes planned to compat 11 at
the moment, but there might be changes in response to feedback from testers.
* If you start to use the compat 11 in your package in uploads to
Adrian Bunk:
> On Sun, Nov 12, 2017 at 10:25:00AM +0000, Niels Thykier wrote:
>> ...
>>
>> Backport availability
>> =
>> ...
>> *Caveat*: Packages using the cmake build system should be careful as
>> cmake in stretch does not respo
Emilio Pozuelo Monfort:
> On 12/11/17 11:25, Niels Thykier wrote:
>> Hi,
>>
>>
>> The debhelper compat level 11 is about to be finalized and we invite you
>> to test it out. There are no additional changes planned to compat 11 at
>> the moment, but there m
Maximiliano Curia:
> ¡Hola Niels!
>
> El 2017-11-18 a las 11:41 +0000, Niels Thykier escribió:
>> Emilio Pozuelo Monfort:
>>> It'd make more sense to me to change that in compat 11 to be enabled
>>> by default and run with --list-missing (--fail-missing is pr
Emilio Pozuelo Monfort:
> On 18/11/17 12:41, Niels Thykier wrote:
>> I have received several requests to make --list-missing or
>> --fail-missing the default (#650129 and #858834) and I intend to do so
>> eventually. I am a little concerned with adding more changes to comp
Christoph Biedl:
> Emilio Pozuelo Monfort wrote...
>
>> One thing with compat 10 that doesn't make a lot of sense to me is how
>> dh_missing is enabled by default but a no-op. It'd make more sense to me to
>> change that in compat 11 to be enabled by default and run with --list-missing
>> (--fail-
Hi,
Just a heads up: The debhelper compat level 11 is now stable and
available in stretch-backports.
Thanks,
~Niels
Hi,
EXECUTIVE SUMMARY
=
I am planning to remove the following features/commands in debhelper in
the near future:
* compat level 1,2 and 3.
* dh_scrollkeeper
All of the listed commands do nothing except a deprecation warning.
Please see "BACKGROUND AND NUMBERS" for more informa
On 2015-09-13 14:12, John D. Hendrickson wrote:
> [...]
>
> you seem to be crossing your testimony
>
> first you say "does nothing but print warning". then you talk about
> patterns not matching and removing dh_scrollkeeper which is used by any
> packaged doing update for NOT-gnome3, which is ma
On 2015-09-13 11:04, Niels Thykier wrote:
> Hi,
>
> EXECUTIVE SUMMARY
> =
>
> I am planning to remove the following features/commands in debhelper in
> the near future:
>
> * compat level 1,2 and 3.
> * dh_scrollkeeper
>
> All of the
On 2015-09-13 21:02, Matthias Klose wrote:
> [...]
>
> still using the globbing feature for command line arguments in DH_COMPAT=2
> mode.
> Was this re-added in higher levels again?
>
> Matthias
>
Hi Matthias,
Ok, I was not aware of this feature. To be honest, I suspect it was an
artefact
On 2015-09-17 22:02, Santiago Vila wrote:
> Hello.
>
Hi,
> I see "serious" bug reports asking for packages to drop
> "dh_installdocs --link-doc" (see Bug #799316 for an example).
>
To clarify (for those who haven't read the bug): I requested that
--link-doc between arch:any AND arch:all packag
On 2015-09-20 19:04, Tomasz Rybak wrote:
> Dnia 2015-08-25, wto o godzinie 13:41 +, Jean-Michel Vourgère
> pisze:
>> Hi
>>[...]
>>
>> The question is also valid for python2:
>>
>> When using dh --with python2 *and* build-depending on python-all-dbg,
>> I'm getting [1]:
>> * Some files like /usr
Hi,
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 from backports still
(incorrectly) reports this an issue.
Please d
Niels Thykier:
> Hi,
>
> EXECUTIVE SUMMARY
> =
>
> I am planning to remove the following features/commands in debhelper in
> the near future:
>
> * compat level 1,2 and 3.
>
> All of the listed commands do nothing except a deprecation warn
Niels Thykier:
> Hi,
>
> EXECUTIVE SUMMARY
> =
>
> I am planning to remove the following features/commands in debhelper in
> the near future:
>
> * compat level 1,2 and 3.
> * dh_scrollkeeper
>
> All of the listed commands do nothing except
Hi,
In the new version of apt-file (currently in experimental), we have
changed/removed some features that will affect some packages. Packages
listed below are BCC'ed to this mail.
Notably:
* /var/cache/apt-file will disappear
- command-not-found and dh-make-perl are known consumers
* Per
Paul Wise:
> On Sat, Dec 5, 2015 at 8:39 PM, Niels Thykier wrote:
>
>> * The full list of known incompatibilities is in the changelog[1]
>
> - Special uses of "-a" to search in Source packages or
>udebs have been replaced by "--index-names"
Vincent Danjean:
> Le 05/12/2015 13:58, The Wanderer a écrit :
>> On 2015-12-05 at 07:39, Niels Thykier wrote:
>>
>>> Hi,
>>>
>>> In the new version of apt-file (currently in experimental), we have
>>> changed/removed some features that will af
James McCoy:
> On Sat, Dec 05, 2015 at 12:39:36PM +0000, Niels Thykier wrote:
>> Hi,
>>
>> In the new version of apt-file (currently in experimental), we have
>> changed/removed some features that will affect some packages. Packages
>> listed below are B
Damyan Ivanov:
> -=| Niels Thykier, 05.12.2015 12:39:36 + |=-
>> In the new version of apt-file (currently in experimental), we have
>> changed/removed some features that will affect some packages. Packages
>> listed below are BCC'ed to this mail.
>>
>>
Hi,
As of today, dak supports the dbgsym packages built by debhelper and
with debhelper/9.20151219 they are now built by default! With this, a
decade old idea is now implemented and available for general
consumption[1]. :)
* A huge thanks to Ansgar Burchardt for finishing up the remaining
lo
Niels Thykier:
> Hi,
>
> As of today, dak supports the dbgsym packages built by debhelper and
> with debhelper/9.20151219 they are now built by default! With this, a
> decade old idea is now implemented and available for general
> consumption[1]. :)
>
> [...]
>
Hi,
Bernd Zeimetz:
> Hi,
>
Hi,
>> So how will we deal with the migration from -dbg to -dbgsym for
>> jessie -> stretch?
>>
>> * Should we keep transitional -dbg packages around even if the
>> -dbgsym packages are in another archive?
>>
To be honest, I do not think this will make sense/work (for tha
Dirk Eddelbuettel:
>
> Hi all,
>
> I was just updating one of my several dozen r-cran-* packages. These all use
> the same (source) r-cran.mk script shipped with the main R packages.
>
> And now all of sudden it wants to build a -dbgsym package.
>
> That may not be such a good idea for the seve
Dirk Eddelbuettel:
>
> Hi Niels,
>
> Thanks for the prompt and detailed answer! It addressed all my questions.
>
> On 20 December 2015 at 21:11, Niels Thykier wrote:
> | Dirk Eddelbuettel:
> | > I was just updating one of my several dozen r-cran-* packages. Thes
Dirk Eddelbuettel:
>
> On 20 December 2015 at 21:52, Niels Thykier wrote:
> | Dirk Eddelbuettel:
> | >
> | > Hi Niels,
> | >
> | > Thanks for the prompt and detailed answer! It addressed all my questions.
> | >
> | > On 20 December 2015 at 21:11, N
Anthony DeRobertis:
> Are there plans to teach httpredir.debian.org about the new debug mirror
> network?
>
> http://httpredir.debian.org/debian-debug/dists/unstable-debug/main/binary-amd64/Release
> is currently 404.
>
Thanks for the suggestion.
I have filed a request for it in [1] - patches
Lucas Nussbaum:
> On 28/12/15 at 14:24 +0100, Bastien ROUCARIES wrote:
>>> qa-vcs_but_not_git_or_svn.txt (290 packages)
>>>
>>>The package is maintained using a VCS, which is not either Git or SVN.
>>
>> This one is really bellow pedantic...
>
> I agree. And this could also apply to "still usi
Philippe Cerfon:
> On Sun, Jan 3, 2016 at 7:35 AM, Christian PERRIER wrote:
>> Discussing infrastructure changes like what you're proposing (which I
>> have no advice about) should usually be done through our mailing
>> lists,
> Which one would be the appropriate list?
>
> I thought general would
Riku Voipio:
> On Fri, Jan 08, 2016 at 09:50:56AM +0100, Marc Haber wrote:
>> The loss of keyscript just broke my clients. I am really afraid of the
>> first system update breaking my _servers_, causing a resinstall to be
>> necessary. I know of one customer who already said that if a reinstall
>>
Marc Haber:
> Debian has already been forked by people who found Debian's release
> cycles too long. The result is called Ubuntu, and we lost many of the
> users (and developers!) who want shorter release cycles to them.
>
> Now, we aim for shorter release cycles ourselves, which won't bring
> any
Marvin Renich:
> * Vincent Danjean [151208 03:17]:
>> [...]
>>
>> I use "apt-file search" very sporadically. And even when I use it,
>> most of the time, it is to find a package containing a header file,
>> so I do not need its database to be up-to-date. So I update it only
>> when the result fr
Johannes Schauer:
> Hi,
>
> [...]
>
> in #807312 Ansgar helpfully pointed me to [1]. I have no clue at all about
> britney but from my naive understanding I get that one of the things it does
> is
> to check if a source package's build dependencies and its binary packages'
> runtime dependencies
Andreas Tille:
> Hi,
>
> On Thu, Feb 04, 2016 at 02:21:06PM +0100, Wouter Verhelst wrote:
>>
>> Right. So something like...
>>
>> debian/control:
>> Vcs-Git: ${vcs:repo}
>> Vcs-Browser: ${vcs:browser}
>>
>> debian/vcs:
>> Vcs-Type: Git
>> Vcs-Host: Debian
>> Vcs-Path: /
>>
>> debian/rules:
>> over
Hi,
In continuation of [1], there is the next round of deprecated debhelper
features that I would like to remove from debhelper.
* dh_desktop - 24 packages remaining
* No compat file - 119 packages remaining
- Due to #811059 and #805405
* compat 4 - 402 packages remaining
In total 489 /un
Niels Thykier:
> Hi,
>
> [...]
> Deadlines
> =
>
> I envisioned the following deadlines for these removals:
>
> * dh_desktop: 1st of April (3 weeks from the bug filing)
> * No compat file: 15th of April (5 weeks from the bug filing)
> * compat 4: 15t
David Prévot:
> Le 18/03/2016 18:06, Josh Triplett a écrit :
>
>> I would suggest that Firefox addon packages should depend on "firefox |
>> firefox-esr"
>
> Most of those packages are mozilla-devscripts for the build and just
> need to be rebuilt to get fixed. Even if our infrastructure has all
Hi,
With the latest debhelper upload today, I believe compat 10 is now ready
for widespread testing.
The following is the list of changes:
> v10 This compatibility level is open for beta testing; changes may
> occur.
>
> Changes from v9 are:
>
> - dh_installin
Hi,
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 get the remaining packages
updated sooner rather than later (notab
Andreas Tille:
> Hi Niels,
>
> thanks a lot for working on debhelper!
>
You are welcome :)
> On Sun, Apr 03, 2016 at 10:12:46AM +, Niels Thykier wrote:
>> A couple of notes:
>>
>> * On autoreconf vs config.{sub,guess}: The default sequence now
>>
Matthias Klose:
> On 03.04.2016 12:12, Niels Thykier wrote:
>> Hi,
>>
>> With the latest debhelper upload today, I believe compat 10 is now ready
>> for widespread testing.
>
> please could you consider generating new style dbg files (using
> build-id) fo
Simon McVittie:
> On Tue, 05 Apr 2016 at 19:43:13 +0000, Niels Thykier wrote:
>> I do not mind managing a mass-bug filing for removing manual dbg
>> packages without reverse dependencies if that is any help.
>
> Is there a plan/timeline for having -dbgsym packages appear in t
Sean Whitton:
> So dh-elpa-test needs its own sequencer script in
> /usr/share/perl5/Debian/Debhelper/Sequence, and so it also needs its own
> corresponding /usr/bin/dh_elpa_test. But then for ease of maintenance
> it should be its own source package.
Hi,
I am not aware of any reason why a packa
Alastair McKinstry:
>
>
> On 10/04/2016 08:05, Andreas Tille wrote:
>> Hi,
>>
>> > The only use case I could imagine is to create an executable that can
>> > run outside of Debian.
> Static builds are still common in (parts of) scientific computing.
> Two main reasons:
>
> (1) When performan
Hi,
Christoph Biedl:
> No big surprise. Given the amount of unneeded information combined
> with the experience several gotchas were missing ... I've stopped
> reading them. Several other people probably too.
>
* I agree there is a lot of boilerplate text and I would be happy to
restructure
Adam D. Barratt:
> On Mon, 2016-05-09 at 21:44 +0200, Ondřej Surý wrote:
>> On Mon, May 9, 2016, at 20:42, Niels Thykier wrote:
>>> * We are too few to write the release-notes to keep track of all the
>>>relevant parts for a release.
>>>- HELP IS VERY
Marc Haber:
> On Mon, 9 May 2016 18:42:52 +0000, Niels Thykier
> wrote:
>> [...]
>
> Maybe we should introduce a BTS tag "release notes" so that (1) bug
> reports of such gotchas can be flagged appropriately and (2) it is
> easily possible to track such repo
Christoph Biedl:
> Niels Thykier wrote...
>
>> I appreciate it was (hopefully) not your intention. But with that
>> remark you make me feel like I have wasted my time and effort trying to
>> the write the Jessie release notes.
>
> Niels,
>
> offendi
Marco d'Itri:
> On May 03, Josh Triplett wrote:
>
>> While this doesn't make PIC absolutely free, it does eliminate almost
>> all of the cost, to the point that it no longer seems worthwhile to
>> build without -fPIC. Apart from that, building *all* code with -fPIC
>> (including both programs an
Bálint Réczey:
> Hi,
>
> [...]
>
Hi,
> 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 suspect we should enable PIE by default
via GCC-6's new configure switch[1]. Assuming it does what I hope,
Theodore Ts'o:
> Hi, is it intended that the Contents and Packages file in the dbgsyms
> archive are empty?
>
Hi,
http://debug.mirrors.debian.org/debian-debug/dists/unstable-debug/main/binary-amd64/Packages.xz
does not appear to be empty?
Mind you, the debug archive was created with less backw
Theodore Ts'o:
> One other thought. Since someone might be trying to debug a core file
> for an executable belonging to a package which has since been
> superceded by a newer version in unstable or in testing, it would be
> useful if there was a Redis (or some other NoSQL) database where you
> can
Jose M Calhariz:
> Hi,
>
> I am investigating why I can turn off the lintian information
> hardening-no-fortify-functions. In the beginning of my debian/rules I
> have:
>
> export DEB_BUILD_MAINT_OPTIONS=hardening=+all
>
> What I am doing wrong?
> How can I debug if the hardening is really on t
Sven Joachim:
> On 2016-07-06 02:51 +0200, Guillem Jover wrote:
>
>> [...]
>> This has happened now with the upload of dpkg 1.18.8.
>
> Anyone volunteering to upgrade the severity of those 82 bugs to serious?
>
> Cheers,
>Sven
>
>
> 1.
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?t
Jakub Ružička:
Hello,
I've fixed #1081191 through changelog entry in knot/3.4.0-3 and it's
marked as Done but the bug still blocks knot migration for reasons I
don't understand:
https://qa.debian.org/excuses.php?package=knot
What do I need to do to finally finish migration?
Cheers,
Jakub Ruž
Hi
We would like to propose a change in default for `dpkg`, which will
enable `rootless` by default (changing it from "opt-in" to "opt-out").
This would be a considerable milestone bringing us to into 90-99%
territory of removing the need for root (`fakeroot` or otherwise)
in the Debian packaging
Santiago Vila:
This is awesome work! I hope you can start the MBF soon.
One minor comment:
* 862 failures
- Of these 217 failed with an error related to this change
- The remaining failed for other reasons (including running
out of memory on the host, etc.)
I'd like to look a
Helmut Grohne:
Hi Guillem and other developers,
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 swap until the OOM ki
Michael Biebl:
Hi Niels, hi Guillem,
thanks for the initiative and +1 from my side.
Thanks.
Am 29.11.24 um 11:08 schrieb Niels Thykier:
# The bug template used
What's your proposed timeframe for making the switch? Trixie, Forky, no
targetted release but when bug count is reasonabl
Michael Biebl:
Hi Niels, hi Guillem,
thanks for the initiative and +1 from my side.
Thanks.
Am 29.11.24 um 11:08 schrieb Niels Thykier:
# The bug template used
What's your proposed timeframe for making the switch? Trixie, Forky, no
targetted release but when bug count is reasonabl
Simon Josefsson:
Otto Kekäläinen writes:
[...]
Could you propose a DEP -1 to establish a recommended naming procedure?
Including how to escape negative numbers in the shortened form, for
which I suggest using DEP--1 to avoid confusion with DEP-1.
:)
/Simon
Surely, the short form of DEP--1
Andreas Tille:
Hi Niels,
Am Sun, Jan 05, 2025 at 12:40:54PM +0100 schrieb Niels Thykier:
The "I'll do the job until the second someone else shows up" sounds close to
RFA (Request For Adoption).
Maybe we can do with a variant like OFA (Open For Adoption), which does not
have
Niels Thykier:
Hi,
This is an update on the MBF for `Rules-Requires-Root: no` as the new
default.
Two weeks further down the line with another update. :)
# Qualitative updates:
* I have asked the release team to look into whether we should go ahead
with this for Trixie or wait until
Hi,
Historically, if you omitted `Priority` and `Section` from your
package, `dpkg` would warn and use `-` or `unknown` as placeholder
when it absolutely needed a value for these fields in the `.dsc` and
the `.changes` file. The resulting `.deb` would omit the field.
We would like to change this
Daniel Baumann:
Hi,
both sound good (dropping mandatory priority is nice and consistent,
fixing unknown section behaviour too), thanks!
Thanks for the feedback. :)
ideally these changes would be in dpkg in trixie, but maintainers would
start dropping priority fields *after* trixie so that f
Charles Plessy:
Le Sun, Dec 15, 2024 at 09:27:06AM +0100, Niels Thykier a écrit :
We would like [...] that `dpkg` provides defaults [...] if the fields
are omitted from `debian/control`, you get `Priority: optional` and
`Section: unknown` as default in all artifacts (`.dsc`, `.changes`,
and in
Hi,
This is an update on the MBF for `Rules-Requires-Root: no` as the new
default.
# Qualitative updates:
* The bugs have all been filed. Most where filed on Dec 7, but I had
to file 15 special cases manually, which happened Dec 14.
* A number of permission denied issues have been iden
Marc Haber:
On Sat, 21 Dec 2024 22:23:19 +0100, Gioele Barabucci
wrote:
This branch of the discussion started by pointing out the fact that some
maintainers _do_ in fact orphan their packages to remove the "feeling of
being responsible", and then go on maintaining these packages.
Its a way to
Niels Thykier:
Marc Haber:
On Sat, 21 Dec 2024 22:23:19 +0100, Gioele Barabucci
wrote:
This branch of the discussion started by pointing out the fact that some
maintainers _do_ in fact orphan their packages to remove the "feeling of
being responsible", and then go on maintai
Julien Plissonneau Duquène:
(trimming the Cc: list a bit now that the announcements are done, last
Cc: to #1091394, followup on debian-devel)
Hi Helmut,
Le 2025-01-16 10:18, Helmut Grohne a écrit :
I'm attaching my proof of concept. Would you join forces and turn either
of these PoCs into a
Sam Hartman:
"Simon" == Simon McVittie writes:
Simon> On Thu, 16 Jan 2025 at 09:38:38 -0700, Sam Hartman wrote:
>> But the meson setup call is in override_dh_auto_configure. I
>> don't know at that point how to figure out of I am building arch
>> all packages.
Simon>
Hi,
Starting with announcement:
The next dpkg upload will change the default!
The Release Team has accepted the default change as long as we follow it
to the door, which I have every intention to do. :)
With this, we are now entering the endgame for this transition!
# How can you help?
301 - 384 of 384 matches
Mail list logo
