On Sat, 2023-01-28 at 21:35:01 +0200, Adrian Bunk wrote:
> I don't think such arguments are bringing us forward,
> we should rather resolve the problem that these differ.
>
> All/Most(?) packages where they do differ are packages that were until
> recently part of the essential set, and since deb
On Sun, Jan 29, 2023 at 01:33:56AM +0100, Jonas Smedegaard wrote:
> Hi,
>
> Can someone help me understand what is going wrong in Bug#1029911?
>
> The source package build-depends on libstring-shellquote-perl but it
> seems like that build-dependency is not getting installed on the buildd.
>...
Quoting Adrian Bunk (2023-01-29 01:53:19)
> On Sun, Jan 29, 2023 at 01:33:56AM +0100, Jonas Smedegaard wrote:
> > Hi,
> >
> > Can someone help me understand what is going wrong in Bug#1029911?
> >
> > The source package build-depends on libstring-shellquote-perl but it
> > seems like that build-d
On Sat, Jan 28, 2023 at 7:18 PM Simon McVittie wrote:
> I think a better route might be to get it into experimental for now, then
> when it seems like it has stabilized more, put it into unstable/trixie
> and potentially also bookworm-backports.
It's in the NEW queue targeted for experimental now
Hi,
Can someone help me understand what is going wrong in Bug#1029911?
The source package build-depends on libstring-shellquote-perl but it
seems like that build-dependency is not getting installed on the buildd.
I use same setup for a range of Rust library packages, and this is the
only one fai
On Sat, 28 Jan 2023 at 16:41:28 -0500, Jeremy Bicha wrote:
> This solves a problem: currently you can use update-alternatives to
> choose a default terminal for a Debian system, but what happens when
> you have multiple users on the same Debian system with different
> preferences?
Another problem
Sebastian Ramacher writes:
> As with all mass bug filings, discuss the issue first on debian-devel.
> See developer's reference 7.1.1. This discussion could have both
> answered the questions whther RC severity is appropriate for this type
> of bug and whether it's a bug at all.
Historically, we
On Sat, Jan 28, 2023 at 10:23:19PM +0100, Santiago Vila wrote:
> El 28/1/23 a las 22:18, Adrian Bunk escribió:
> > On Sat, Jan 28, 2023 at 09:45:14PM +0100, Santiago Vila wrote:
> > > ...
> > > The other one: There are a bunch of packages whose unit tests rely on
> > > tzdata. The tzdata
> > > pac
Package: wnpp
Severity: wishlist
Owner: jeremy.bi...@canonical.com
X-Debbugs-CC: debian-devel@lists.debian.org
Package Name: xdg-terminal-exec
Version: git snapshot
Upstream Author: Vladimir Kudrya
License: GPL-3+
Programming Lang: Shell
Description: user default terminal execution utility
xdg-t
On Sat, Jan 28, 2023 at 09:45:14PM +0100, Santiago Vila wrote:
>...
> The other one: There are a bunch of packages whose unit tests rely on tzdata.
> The tzdata
> package changes often during the lifetime of stable, and as a result, some
> package might
> stop building from source. If we wanted t
El 28/1/23 a las 22:18, Adrian Bunk escribió:
On Sat, Jan 28, 2023 at 09:45:14PM +0100, Santiago Vila wrote:
...
The other one: There are a bunch of packages whose unit tests rely on tzdata.
The tzdata
package changes often during the lifetime of stable, and as a result, some
package might
sto
On 2023-01-28 20:44:50 +0100, Sebastian Ramacher wrote:
> On 2023-01-28 15:03:04 +0200, Adrian Bunk wrote:
> > On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote:
> > >...
> > > * Those bugs are RC by definition and have been for a long time.
> > >...
> >
> > Please provide a pointer wh
On 2023-01-28 21:56:23 +0100, Santiago Vila wrote:
> El 28/1/23 a las 20:44, Sebastian Ramacher escribió:
> > On 2023-01-28 15:03:04 +0200, Adrian Bunk wrote:
> > > On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote:
> > > > ...
> > > > * Those bugs are RC by definition and have been for
> "Santiago" == Santiago Vila writes:
Santiago> El 28/1/23 a las 20:44, Sebastian Ramacher escribió:
>> On 2023-01-28 15:03:04 +0200, Adrian Bunk wrote:
>>> On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote:
... * Those bugs are RC by definition and have been
El 28/1/23 a las 20:44, Sebastian Ramacher escribió:
On 2023-01-28 15:03:04 +0200, Adrian Bunk wrote:
On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote:
...
* Those bugs are RC by definition and have been for a long time.
...
Please provide a pointer where a release team member ha
El 28/1/23 a las 20:35, Adrian Bunk escribió:
I have so far not seen any technical arguments why removing tzdata from
the build essential set would be better for Debian than keeping it there.
Removing tzdata reduces the size of a chroot that has the build
dependencies for the hello package instal
Hi,
Am 28. Januar 2023 17:27:28 MEZ schrieb Cyril Brulebois :
>Holger Wansing (2023-01-28):
>> now that there's massive work on making non-free firmware to work easily
>> in debian-installer and the distribution, would it be possible, to bring
>> the topic of ath9k-htc free firmware forward?
>>
On Sat, Jan 28, 2023 at 07:34:48PM +0100, Guillem Jover wrote:
> On Sat, 2023-01-28 at 16:32:17 +0100, Adam Borowski wrote:
> > On Sat, Jan 28, 2023 at 01:59:40PM +0100, Santiago Vila wrote:
> > > Unsupported by whom? What is supported or unsupported is explained in
> > > policy.
> > > Policy says
On 2023-01-28 15:03:04 +0200, Adrian Bunk wrote:
> On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote:
> >...
> > * Those bugs are RC by definition and have been for a long time.
> >...
>
> Please provide a pointer where a release team member has said so
> explicitly in recent years.
>
On Sat, 2023-01-28 at 16:32:17 +0100, Adam Borowski wrote:
> On Sat, Jan 28, 2023 at 01:59:40PM +0100, Santiago Vila wrote:
> > Unsupported by whom? What is supported or unsupported is explained in
> > policy.
> > Policy says it must work. Therefore it should be supported (by fixing the
> > bugs)
Package: wnpp
Followup-For: Bug #1028207
Owner: Safir Secerovic
X-Debbugs-Cc: debian-devel@lists.debian.org, stephanlach...@debian.org
Following instructions of Stephan for initial debianization.
Package: wnpp
Severity: wishlist
Owner: Jan Mojzis
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: randombytes
Version : 20230126
Upstream Author : Daniel J. Bernstein
* URL : https://randombytes.cr.yp.to/
* License : Public domain
Programming Lan
Holger Wansing (2023-01-28):
> now that there's massive work on making non-free firmware to work easily
> in debian-installer and the distribution, would it be possible, to bring
> the topic of ath9k-htc free firmware forward?
>
> There are some longstanding bugreports for this (and related, some
On Sat, Jan 28, 2023 at 03:11:39PM +0100, Johannes Schauer Marin Rodrigues
wrote:
> And I asked in my mail to please "decouple the policy and bug severity
> question
> from the question of what a buildd chroot should contain" for a reason.
yes, I know. my point was that too many people won't be
On Sat, Jan 28, 2023 at 03:28:58PM +0100, Johannes Schauer Marin Rodrigues
wrote:
>...
> My proposal is to fix debootstrap #837060 (patch is in the bug report) so that
> it only installs Essential:yes, build-essential and apt and discuss if it
> makes
> sense to have packages like tzdata or e2fsp
Johannes Schauer Marin Rodrigues wrote:
> Do you agree that the software in our archive should agree on which
> packages are needed to build a source package? Currently, they do
> not. dose3 requires only Essential:yes and build-essential being
> installed. Who is buggy?
Well, the /informational/
On Sat, Jan 28, 2023 at 01:59:40PM +0100, Santiago Vila wrote:
> El 28/1/23 a las 12:50, Andreas Henriksson escribió:
>
> > Claiming there's no point to free software when the problem is simply
> > that you are using an *unsupported* setup?!?!
>
> Unsupported by whom? What is supported or unsuppo
Quoting Ansgar (2023-01-28 14:41:31)
> Johannes Schauer Marin Rodrigues writes:
> > I think the much more interesting question is in what environment we want to
> > build our packages in. Currently, on buildds, we build them in a chroot that
> > has Priority:required and build-essential because of
Quoting Holger Levsen (2023-01-28 14:53:37)
> On Sat, Jan 28, 2023 at 02:28:30PM +0100, Johannes Schauer Marin Rodrigues
> wrote:
> > could we decouple the policy and bug severity question from the question of
> > what a buildd chroot should contain, please?
> [...]
> > Why do people call just acc
On Sat, Jan 28, 2023 at 02:28:30PM +0100, Johannes Schauer Marin Rodrigues
wrote:
>...
> Why do people call just accepting that Priority:required packages have to be
> part of the buildd chroot the easier solution? We just need to fix debootstrap
> bug #837060 and we are done, no?
This is mostly
On Sat, Jan 28, 2023 at 02:28:30PM +0100, Johannes Schauer Marin Rodrigues
wrote:
> could we decouple the policy and bug severity question from the question of
> what a buildd chroot should contain, please?
[...]
> Why do people call just accepting that Priority:required packages have to be
> part
On Sat, Jan 28, 2023 at 9:29 PM Johannes Schauer Marin Rodrigues
wrote:
> To me it seems that we nearly are already at (2). The debootstrap bug #837060
> has a working patch and mmdebstrap exists that can do what is needed today.
> Santiago did an archive rebuild to make sure our source package co
Johannes Schauer Marin Rodrigues writes:
> I think the much more interesting question is in what environment we want to
> build our packages in. Currently, on buildds, we build them in a chroot that
> has Priority:required and build-essential because of (what I think is) a bug
> in
> debootstrap:
Quoting Timo Röhling (2023-01-28 13:30:42)
> Hi Andreas,
>
> * Andreas Henriksson [2023-01-28 12:50]:
> >Policy is not a religion. Policy has many bugs. Policy is very outdated.
> >[...]
> >Here's an example you could follow:
> >https://lists.debian.org/debian-policy/2022/12/msg00023.html
> Your
On 2023-01-28 13:59, Adrian Bunk wrote:
I am not saying that trying to force maintainers to spend time on such
issues by making them release critical is better, but you are also
creating extra work and frustration for the people who are doing QA work
in Debian.
It also pushes some maintainers t
On Sat, Jan 28, 2023 at 12:24:47PM +0100, Santiago Vila wrote:
>...
> * Those bugs are RC by definition and have been for a long time.
>...
Please provide a pointer where a release team member has said so
explicitly in recent years.
In my experience they are usually saying that FTBFS that do not
On Sat, Jan 28, 2023 at 12:20:16AM +0100, Santiago Vila wrote:
> El 27/1/23 a las 22:37, Adrian Bunk escribió:
> > On Fri, Dec 16, 2022 at 02:15:13AM +0100, Santiago Vila wrote:
...
> > I am right now looking at #1027382, and the first question is how I can
> > make apt remove e2fsprogs so that I c
Package: debian-policy
[ This is basically #1027832 ]
Timo Röhling writes:
> * Andreas Henriksson [2023-01-28 12:50]:
>>Policy is not a religion. Policy has many bugs. Policy is very outdated.
>>[...]
>>Here's an example you could follow:
>>https://lists.debian.org/debian-policy/2022/12/msg00023
El 28/1/23 a las 13:59, Adrian Bunk escribió:
Policy 4.2 also says
Source packages should specify which binary packages they require to
be installed or not to be installed in order to build correctly.
We are not following the "not to be installed" part,
which is the can of worms you would
El 28/1/23 a las 12:50, Andreas Henriksson escribió:
Policy is not a religion. Policy has many bugs. Policy is very outdated.
buildd is not a religion. buildd has bugs, etc.
Claiming there's no point to free software when the problem is simply
that you are using an *unsupported* setup?!?!
U
Hi Andreas,
* Andreas Henriksson [2023-01-28 12:50]:
Policy is not a religion. Policy has many bugs. Policy is very outdated.
[...]
Here's an example you could follow:
https://lists.debian.org/debian-policy/2022/12/msg00023.html
Your argument cuts both ways. Right now, Policy says that
the bug
Hello,
I've previously discussed this topic with Santiago Vila on a bug report
but sharing my opinion here for the wider audience.
On Sat, Jan 28, 2023 at 12:20:16AM +0100, Santiago Vila wrote:
> El 27/1/23 a las 22:37, Adrian Bunk escribió:
[...]
> This is not the right time to change policy.
T
El 28/1/23 a las 10:11, Vincent Bernat escribió:
On 2023-01-28 00:20, Santiago Vila wrote:
Release Policy exists as a canonical list of what should be RC and > what not,
and it's intended to avoid stupid discussions like this one.
Extending build-essential is easier than asking many people to
Hi all,
now that there's massive work on making non-free firmware to work easily in
debian-installer and the distribution, would it be possible, to bring the
topic of ath9k-htc free firmware forward?
There are some longstanding bugreports for this (and related, some in CC); is
there any chance t
On 2023-01-28 00:20, Santiago Vila wrote:
Release Policy exists as a canonical list of what should be RC and > what not,
and it's intended to avoid stupid discussions like this one.
Extending build-essential is easier than asking many people to do
pointless work to satisfy a set of non-existi
45 matches
Mail list logo