El 17/12/23 a las 22:40, Steven Robbins escribió:
On Saturday, December 16, 2023 12:23:46 P.M. CST Paul Gevers wrote:
Another topic we covered is the volume and purpose of our mail list
(debian-devel@lists.debian.org). We recognize that that list mostly just
mirrors BTS traffic. The BTS
El 26/10/23 a las 2:11, Vincent Lefevre escribió:
This seems to be due to a bug in the BTS
[...]
Hello. This is a bug or a feature depending on how you look at it.
Reopening a bug is known to clear the version on which it was closed
(I think this normally makes sense and the cases where it
El 18/3/23 a las 4:00, Ilari Jääskeläinen escribió:
There is a new upstream release available.
We already know. It's already reported (twice) in the BTS:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029106
If you absolutely need to use make 4.4.1, you can try this,
which is what I did:
El 10/2/23 a las 3:18, Johannes Schauer Marin Rodrigues escribió:
So the chgrp call in Makefile.am worked correctly and set the group owner to
"mail" but after dh_install moved mutt_dotlock from debian/tmp/ to debian/mutt/
using 'cp -a' (if I'm reading the code correctly) the group ownership
El 10/2/23 a las 3:18, Johannes Schauer Marin Rodrigues escribió:
I do not understand what makes you think that only packages using dh_fixperms
-X are affected? I think what makes the two packages that I found fail to have
correct permissions is that they both use dh_install which in turn uses
El 9/2/23 a las 15:37, Johannes Schauer Marin Rodrigues escribió:
I wanted to bring fakeroot bugs #1023286 and #1030638 to the attention of a
wider audience because even though I filed these bugs,
Thanks for bringing this up!
Can you confirm if all this is correct?
- Only packages uploaded
El 6/2/23 a las 11:26, Brian Thompson escribió:
I understand that the usual way to close out bug reports is having the
original author do it themselves. What's the policy on closing bug reports
that haven't had activity in over 6 months?
Let the maintainers handle their bugs.
Old bugs should
El 30/1/23 a las 14:05, Guillem Jover escribió:
Given the number of packages that currently declare a dependency on
tzdata (34~), the ones that seem to have the most potential to pull it
for others are language bindings such as python3-dateutil, python3-tz
ruby-tzinfo, etc, which handle timezone
El 30/1/23 a las 13:41, Santiago Vila escribió:
Note: I've downgraded the bugs in dispute to important,
so they are not RC anymore, per request of Sebastian Ramacher.
I mean: Sebastian started to downgrade them, and I've downgraded
the remaining open bugs which were not downgraded by him
El 27/1/23 a las 22:37, Adrian Bunk escribió:
Speaking as someone who is doing a lot of QA work, [...]
Note: I've downgraded the bugs in dispute to important,
so they are not RC anymore, per request of Sebastian Ramacher.
I just wanted to point out that the "it's more work for me"
argument
El 29/1/23 a las 9:56, Sebastian Ramacher escribió:
On 2023-01-28 15:55:05 -0800, Russ Allbery wrote:
Historically, we have not treated FTBFS bugs as falling into the category
of mass bug filing or requiring this pre-discussion. Various folks have
been mass-filing FTBFS bugs near the release
El 28/1/23 a las 14:41, Ansgar escribió:
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
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
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
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
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?!?!
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 peo
El 27/1/23 a las 22:37, Adrian Bunk escribió:
On Fri, Dec 16, 2022 at 02:15:13AM +0100, Santiago Vila wrote:
Greetings.
I'm doing archive-wide rebuilds again.
I've just filed 21 bugs with subject "Missing build-depends on tzdata"
in bookworm (as tzdata is not build
El 26/12/22 a las 20:29, Theodore Ts'o escribió:
I: The directory does not exist inside the chroot.
This is really a problem with schroot. I guess that this will not work either:
schroot -c the-chroot-name
This usually works when you are in your $HOME because this file:
El 16/12/22 a las 18:55, Andreas Metzler escribió:
I am wondering if there is point to this or whether policy should be
changed? Is there some value in investing work in having packages
buildable without Prioriry required packages?
I'd like to apologize to Andreas for my previous answer, as I
El 16/12/22 a las 18:55, Andreas Metzler escribió:
I am wondering if there is point to this or whether policy should be
changed? Is there some value in investing work in having packages
buildable without Prioriry required packages?
Please do not misrepresent what I said.
I never proposed such
El 16/12/22 a las 4:39, Johannes Schauer Marin Rodrigues escribió:
I think truly fixing this problem is a bit more tricky because most build tools
like the sbuild schroot backend require apt being installed in the chroot. As
of today, the sbuild schroot backend is unable to function with a
Greetings.
I'm doing archive-wide rebuilds again.
I've just filed 21 bugs with subject "Missing build-depends on tzdata"
in bookworm (as tzdata is not build-essential).
This is of course not fun for the maintainers, but it's also not fun
for people doing QA, because those bugs could be caught
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 20 Nov 2019 23:07:20 +0100
Source: gettext
Architecture: source
Version: 0.19.8.1-10
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
gettext (0.19.8.1-10) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 03 Nov 2019 13:35:14 +0100
Source: m4
Architecture: source
Version: 1.4.18-4
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
m4 (1.4.18-4) unstable; urgency=medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 03 Nov 2019 12:34:42 +0100
Source: recode
Architecture: source
Version: 3.6-24
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
recode (3.6-24) unstable; urgency=medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 03 Nov 2019 12:33:42 +0100
Source: m4
Architecture: source
Version: 1.4.18-3
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
m4 (1.4.18-3) unstable; urgency=medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 27 Aug 2019 18:32:54 +0200
Source: dialog
Architecture: source
Version: 1.3-20190808-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 930775
Changes:
dialog (1.3-20190808-1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 27 Jul 2019 18:01:36 +0200
Source: unzip
Architecture: source
Version: 6.0-25
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 932404
Changes:
unzip (6.0-25) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 11 Jul 2019 18:03:34 +0200
Source: unzip
Architecture: source
Version: 6.0-24
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 931433
Changes:
unzip (6.0-24) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 09 Jul 2019 12:05:50 +0200
Source: base-files
Architecture: source
Version: 11
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 930654
Changes:
base-files (11) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 29 May 2019 00:24:08 +0200
Source: unzip
Architecture: source
Version: 6.0-23
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 929502
Changes:
unzip (6.0-23) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 15 May 2019 12:49:00 +0200
Source: hello-traditional
Architecture: source
Version: 2.10-5
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
hello-traditional (2.10-5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 15 May 2019 11:15:20 +0200
Source: hello-traditional
Architecture: source
Version: 2.10-4
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
hello-traditional (2.10-4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 13 May 2019 22:25:32 +0200
Source: base-files
Architecture: source
Version: 10.3
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 928172
Changes:
base-files (10.3) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 13 May 2019 20:06:50 +0200
Source: hello
Architecture: source
Version: 2.10-2
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 928887
Changes:
hello (2.10-2) unstable
On Mon, May 13, 2019 at 11:32:36AM +, Holger Levsen wrote:
> hi,
>
> so there is "#928172 debian-security-support: fails to upgrade from 'testing':
> dpkg: error: error executing hook" which happens when base-files is upgraded
> before debian-security-support (but doesnt happen if d-s-s is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 19 Apr 2019 13:05:00 +0200
Source: base-files
Binary: base-files
Architecture: source
Version: 10.2
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description:
base-files - Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 08 Apr 2019 14:04:00 +0200
Source: diffutils
Binary: diffutils diffutils-doc
Architecture: source
Version: 1:3.7-3
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 18 Feb 2019 14:03:30 +0100
Source: diffutils
Architecture: source
Version: 1:3.7-2
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 922552
Changes:
diffutils (1:3.7-2) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 17 Feb 2019 23:50:00 +0100
Source: diffutils
Architecture: source
Version: 1:3.7-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
diffutils (1:3.7-1) unstable; urgency=low
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 17 Feb 2019 23:44:16 +0100
Source: dialog
Architecture: source
Version: 1.3-20190211-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Changes:
dialog (1.3-20190211-1) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 09 Feb 2019 18:12:00 +0100
Source: unzip
Architecture: source
Version: 6.0-22
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 889838
Changes:
unzip (6.0-22) unstable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 27 Jan 2019 22:35:20 +0100
Source: indent
Architecture: source
Version: 2.2.12-1
Distribution: unstable
Urgency: low
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Closes: 228112 349065 487517 657461 726105 865677
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 11 Dec 2018 22:14:40 +0100
Source: icon
Binary: icont iconx icon-ipl
Architecture: source
Version: 9.4.3-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Santiago Vila
Description:
icon-ipl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 01 Dec 2018 15:48:20 +0100
Source: sharutils
Binary: sharutils sharutils-doc
Architecture: source
Version: 1:4.15.2-4
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 01 Dec 2018 15:46:54 +0100
Source: m4
Binary: m4 m4-doc
Architecture: source
Version: 1.4.18-2
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description:
m4 - macro
: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities for the base system
gettext-doc - Documentation for GNU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 28 Oct 2018 22:30:24 +0100
Source: dialog
Binary: dialog
Architecture: source
Version: 1.3-20181022-1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description:
dialog
: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities for the base system
gettext-doc - Documentation for GNU
: unstable
Urgency: medium
Maintainer: Santiago Vila
Changed-By: Santiago Vila
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities for the base system
gettext-doc - Documentation for GNU
: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila <sanv...@debian.org>
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities
: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila <sanv...@debian.org>
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 20 Mar 2018 01:09:02 +0100
Source: sharutils
Binary: sharutils sharutils-doc
Architecture: source
Version: 1:4.15.2-3
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 14 Jan 2018 00:36:34 +0100
Source: base-files
Binary: base-files
Architecture: source
Version: 10.1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 17 Dec 2017 20:20:16 +0100
Source: dialog
Binary: dialog
Architecture: source
Version: 1.3-20171209-1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 16 Nov 2017 23:42:36 +0100
Source: procmail
Binary: procmail
Architecture: source
Version: 3.22-26
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila <sanv...@debian.org>
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities
: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila <sanv...@debian.org>
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 04 Aug 2017 23:20:16 +0200
Source: diffutils
Binary: diffutils diffutils-doc
Architecture: source
Version: 1:3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 26 Jun 2017 00:19:42 +0200
Source: base-files
Binary: base-files
Architecture: source
Version: 10
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 04 Apr 2017 18:00:30 +0200
Source: base-files
Binary: base-files
Architecture: source
Version: 9.9
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
On Mon, Feb 27, 2017 at 05:59:53PM +0100, Daniel Pocock wrote:
> Can anybody make any suggestions or add anything to the wiki?
My old Mac Mini had a crazy clock and ntp was not enough to sanitize it.
I fixed it by using adjtimex in addition to ntp.
As an example, my clock was off by 2890 parts
On Tue, Feb 21, 2017 at 09:36:58PM +0100, Vincent Bernat wrote:
> Accomodating for all build environments is a slippery slope. What if I
> use a 128MB host with 64GB of swap? Timing-related tests will start to
> fail. Is it Debian job to fix all the test suites? Should I be able to
> build
On Mon, Feb 20, 2017 at 09:22:35PM +, Ian Jackson wrote:
> If you do not get good answers, please take this to the TC.[1]
Thanks a lot for your support, Ian.
What kind of question do you think I could make to the TC?
Maybe this one for a start?:
Should building Debian source packages on
On Mon, Feb 20, 2017 at 06:46:25PM +, Holger Levsen wrote:
> On Mon, Feb 20, 2017 at 10:29:28AM -0800, Russ Allbery wrote:
> > The point is that they don't randomly fail in the sense that they don't
> > fail n% of the time when run in any possible build environment.
We don't really know. Some
On Mon, Feb 20, 2017 at 06:10:23PM +0100, Vincent Bernat wrote:
> ❦ 20 février 2017 13:44 GMT, Holger Levsen :
>
> >> As a rule of thumb, upstream usually knows better than me which tests
> >> are important. Tests are quite important for the packager to know if
> >> they
On Mon, Feb 20, 2017 at 03:24:10PM +, Simon McVittie wrote:
> On Mon, 20 Feb 2017 at 10:41:49 +0100, Santiago Vila wrote:
> > You are somehow trying to equate RC-ness with "it FTBFS in
> > buildd.debian.org".
>
> No, I'm saying that a sufficiently repeat
On Mon, Feb 20, 2017 at 11:33:23AM +, Ghislain Vaillant wrote:
> I share the same feelings towards a similar intermittent FTBFS with
> src:python-qtpy (#8544936). I admit I have no clue what is going on,
> neither does upstream, nor does the reporter (Santiago).
That would be #854496. It
On Mon, Feb 20, 2017 at 08:30:04AM +, Simon McVittie wrote:
> Debian is an operating system, not an academic exercise. If a package
> builds successfully reliably enough on buildds, porterboxes, and
> developers' hardware or VMs that we can prepare security updates and
> other urgent patches
On Mon, Feb 20, 2017 at 01:57:52AM +0100, Adam Borowski wrote:
> * single-CPU machines have gone the way of the dodo. Even the crummiest
> machine I could find while dumpster-diving looking for a non-sse3 one
> already has HT and builds your examples successfully. Same for ARM SoCs
> --
On Mon, Feb 20, 2017 at 12:05:42AM +0100, Vincent Bernat wrote:
> More and more packages come with test suites to help developers and
> packagers ensure things are working as expected. It would be great if
> test suites didn't have failures of their own but it's better to have
> them and it's
On Sun, Feb 19, 2017 at 06:27:16PM +0100, Christoph Biedl wrote:
> Ian Jackson wrote...
>
> > If there is to be a failure probability threshold I would set it at
> > 10^-4 or so. After all, computer time is cheap.
>
> To determine 10^-4 with some accurance you'd have to rebuild that
> package
On Fri, Feb 17, 2017 at 06:59:00PM +, Niels Thykier wrote:
> Santiago Vila:
> > On Fri, Feb 17, 2017 at 06:23:00AM +, Niels Thykier wrote:
> >
> >> Santiago already brought it up in #844264. I believe my answer in
> >> comment 70 is still relevant (oth
On Fri, Feb 17, 2017 at 06:23:00AM +, Niels Thykier wrote:
> Santiago already brought it up in #844264. I believe my answer in
> comment 70 is still relevant (other than I incorrectly used "after the
> freeze" when I meant "after the release").
Well, but when I said "Ok, will do" in Bug
On Wed, Feb 15, 2017 at 03:02:23PM -0500, Jeremy Bicha wrote:
> On Wed, Feb 15, 2017 at 2:36 PM, Santiago Vila <sanv...@unex.es> wrote:
> > Allowing packages to fail 50% of the time is interpreting Release
> > Policy in a somewhat twisted way.
>
> Except that your build
On Wed, Feb 15, 2017 at 08:38:17PM +0100, Bernd Zeimetz wrote:
> Hi,
>
> > The following packages FTBFS for me randomly. First column is the bug
> > number, second column is the estimated probability of failure in my
> > build environment, which is described here:
> >
> >
On Wed, Feb 15, 2017 at 08:05:51PM +0100, Thibaut Paumard wrote:
> Dear Santiago,
>
> Le 15/02/2017 à 18:26, Santiago Vila a écrit :
> > Hello.
> >
> > The following packages FTBFS for me randomly. First column is the bug
> > number, second column is the estim
Hello.
The following packages FTBFS for me randomly. First column is the bug
number, second column is the estimated probability of failure in my
build environment, which is described here:
https://people.debian.org/~sanvila/my-building-environment.txt
Before I ask the Release Managers that they
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 29 Jan 2017 19:02:04 +0100
Source: eterm
Binary: eterm
Architecture: source
Version: 0.9.6-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Santiago Vila
: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila <sanv...@debian.org>
Description:
autopoint - The autopoint program from GNU gettext
gettext- GNU Internationalization utilities
gettext-base - GNU Internationalization utilities
On Mon, Jan 16, 2017 at 05:45:19PM -0800, Russ Allbery wrote:
> > Well, maybe what it's excessively aggressive or questionable is to run
> > the tests at build time and making the package build as a whole to fail
> > when any test fails.
>
> *blink*.
>
> I'm quite surprised that you would
On Mon, Jan 16, 2017 at 11:45:42PM +0100, Markus Koschany wrote:
> No, this is not current practice. But you are obviously trying to force
> it this way by all means necessary. Nobody asks you from refraining to
> report those kind of bugs but what I and other people are seriously
> questioning
On Mon, Jan 16, 2017 at 12:02:32PM -0800, Russ Allbery wrote:
> Santiago Vila <sanv...@unex.es> writes:
>
> > Should I ask the Technical Committee to rule out that FTBFS bugs are RC,
> > even if they did not happen in buildd.debian.org yet?
>
> This seems excessivel
On Mon, Jan 16, 2017 at 12:17:48PM +0100, Ole Streicher wrote:
> Santiago Vila <sanv...@unex.es> writes:
> > On Mon, Jan 16, 2017 at 10:24:59AM +0100, Ole Streicher wrote:
> >
> >> IMO, we should trust the maintainer and their decisions until there is
> >> no
On Mon, Jan 16, 2017 at 10:24:59AM +0100, Ole Streicher wrote:
> IMO, we should trust the maintainer and their decisions until there is
> no experience that it doesn't work. Which means: keep the maintainer
> fully responsible on the package, including the ability to lower
> severity of a CI test
On Mon, Jan 16, 2017 at 10:38:42AM +0200, Lars Wirzenius wrote:
> Picture this: a cocktail party. Many people mingling around, dressed
> up and engaging in smalltalk, sipping colourful drinks. A new couple
> arrives and is immediately surrounded by old fiends. "Hi, Jack and
> Joan, how are you?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 15 Jan 2017 23:00:02 +0100
Source: base-files
Binary: base-files
Architecture: source
Version: 9.8
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 11 Jan 2017 20:02:00 +0100
Source: crafty
Binary: crafty
Architecture: source
Version: 23.4-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 10 Jan 2017 21:06:54 +0100
Source: fbzx
Binary: fbzx
Architecture: source
Version: 3.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila <sanv...@d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 10 Jan 2017 18:36:26 +0100
Source: sfront
Binary: sfront
Architecture: source
Version: 0.99-2
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila <sanv...@d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 10 Jan 2017 17:50:20 +0100
Source: indent
Binary: indent indent-doc
Architecture: source
Version: 2.2.11-5
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 09 Jan 2017 23:55:10 +0100
Source: diffutils
Binary: diffutils diffutils-doc
Architecture: source
Version: 1:3.5-3
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 08 Jan 2017 22:53:02 +0100
Source: sharutils
Binary: sharutils sharutils-doc
Architecture: source
Version: 1:4.15.2-2
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 08 Jan 2017 18:47:44 +0100
Source: original-awk
Binary: original-awk
Architecture: source
Version: 2012-12-20-6
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 08 Jan 2017 18:16:40 +0100
Source: wdiff
Binary: wdiff wdiff-doc
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 08 Jan 2017 18:25:42 +0100
Source: diffutils
Binary: diffutils diffutils-doc
Architecture: source
Version: 1:3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 08 Jan 2017 17:38:22 +0100
Source: mpegdemux
Binary: mpegdemux
Architecture: source
Version: 0.1.4-4
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila <sanv...@debian.org>
Changed-By: Santiago Vila
On Fri, Jan 06, 2017 at 02:29:12PM -0800, Nikolaus Rath wrote:
> On Jan 06 2017, Santiago Vila <sanv...@unex.es> wrote:
> > If we want to be the Universal OS, we can't assume that any time
> > (not chosen by the user) is ok to do an upgrade.
>
> If we want to be the Un
1 - 100 of 1386 matches
Mail list logo