El 3/6/24 a las 23:10, Helmut Grohne escribió:
On Wed, May 29, 2024 at 03:14:59PM +0200, Helmut Grohne wrote:
Since noble includes these changes and I'd get this done sooner rather
than later, how about moving forward with June 5th after 22:30 UTC (such
that all buildds have regenerated
Nevermind. I see that the upload was already accepted, and what is
missing is a binary-only upload matching the already existing source.
Yes, sorry if I wasn't clear enough about that.
No problem. I've now done the additional binary-only upload.
Thanks a lot.
As bart-cuda build-depends on nvidia-cuda-toolkit, which is in non-
free, bart-cuda is not buildable on the buildd network, so this will
also need a binary upload to be performed.
Ok, what's the best way to solve this? Can you reject the upload
so that I do it again including .debs?
El 14/5/24 a las 20:24, Adam D. Barratt escribió:
On Wed, 2024-05-08 at 17:18 +0200, Santiago Vila wrote:
This upload fixes Bug #1070757 FTBFS in bullseye.
Note: A similar request for a similar bug has been made for package
"bart".
[ Impact ]
Anybody who try to build the package f
patch from release 0.7.00-1.
+Fixes FTBFS bug. Closes: #1070757.
+
+ -- Santiago Vila Wed, 08 May 2024 16:40:00 +0200
+
bart-cuda (0.6.00-1) unstable; urgency=medium
* Initial upload of this cuda enabled bart version
diff -Nru bart-cuda-0.6.00/debian/patches/0005-relax-failing-unit-test.p
-0.6.00/debian/changelog2024-05-07 23:05:00.0 +0200
@@ -1,3 +1,11 @@
+bart (0.6.00-3+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * Cherry-pick 0004-relax-failing-unit-test.patch from
+release 0.7.00-1. Fixes FTBFS bug. Closes: #1026061.
+
+ -- Santiago Vila Tue, 07
Dear Release Managers:
Since I reported bug #1053334, I'd like to emphasize on this item:
* New upstream release includes multiple Debian build and post-build test
failure fixes:
- Generate keys and certificates for SSL tests (Closes: #1053334)
This is a FTBFS bug due to
) bookworm; urgency=medium
+
+ * Team upload.
+ * debian/rules: Add --no-parallel to avoid the effects of a Makefile bug
which
+makes the package to FTBFS randomly. Closes: #1068341.
+
+ -- Santiago Vila Mon, 08 Apr 2024 19:40:00 +0200
+
bioawk (1.0-4) unstable; urgency=medium
* d/p
Hello.
I was going to sponsor this upload and we were waiting for approval before
upload,
but given that 12.5 is approaching and I believe that rejecting an incorrect
upload is relatively easy, I've decided to go ahead and make the upload.
Please consider for 12.5.
Thanks.
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: ind...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:indent
[ Reason ]
This upload fixes CVE-2024-0911.
[ Impact ]
We remain vulnerable if the
/debian/changelog 2023-12-13 18:40:00.0 +0100
@@ -1,3 +1,11 @@
+pyzoltan (1.0.1-2+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * debian/rules: Set NPROC to 1 so that the package may be
+built on systems with a single core. Closes: #1055625.
+
+ -- Santiago Vila Wed, 13
.
+
+ -- Santiago Vila Wed, 13 Dec 2023 12:30:00 +0100
+
python-cogent (2020.12.21a+dfsg-4) unstable; urgency=high
* Team upload.
diff -Nru python-cogent-2020.12.21a+dfsg/debian/patches/series
python-cogent-2020.12.21a+dfsg/debian/patches/series
--- python-cogent-2020.12.21a+dfsg/debian/patches
.
+
+ -- Santiago Vila Tue, 12 Dec 2023 23:00:00 +0100
+
python-django-imagekit (4.0.2-3) unstable; urgency=medium
[ Ondřej Nový ]
diff -Nru python-django-imagekit-4.0.2/debian/gbp.conf
python-django-imagekit-4.0.2/debian/gbp.conf
--- python-django-imagekit-4.0.2/debian/gbp.conf2020-02-23
16
-12 21:30:00.0
+0100
@@ -1,3 +1,10 @@
+vlfeat (0.9.21+dfsg0-6+deb11u1) bullseye; urgency=medium
+
+ * Team upload.
+ * Apply patch by Dennis Filder to fix build error. Closes: #991066.
+
+ -- Santiago Vila Tue, 12 Dec 2023 21:30:00 +0100
+
vlfeat (0.9.21+dfsg0-6) unstable; urgency
; urgency=medium
+
+ * Team upload.
+ * Apply patch by Michael R. Crusoe to request a single core
+in the tests. Closes: #1031192.
+
+ -- Santiago Vila Tue, 21 Nov 2023 00:35:00 +0100
+
toil (5.9.2-2) unstable; urgency=medium
* Add patch to handle errors when testing on ec2.
diff -Nru toil
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: python3-onelogin-sa...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:python3-onelogin-saml2
[ Reason ]
This upload fixes Bug #1036255: FTBFS due
+
+ * Team upload.
+ * Disable flaky test. Closes: #976506.
+
+ -- Santiago Vila Fri, 17 Nov 2023 11:30:00 +0100
+
conda-package-handling (1.7.2-2) unstable; urgency=medium
* Team upload.
diff --git a/debian/patches/series b/debian/patches/series
index 3d1dca5..b36fda0 100644
--- a/debian
El 25/7/23 a las 23:32, Jonathan Wiltshire escribió:
This request was approved but not uploaded in time for the previous point
release (11.7). Should it be included in 11.8 or should this request be
abandoned and closed?
Hi. Since the debdiff was already approved by you (RMs), I've just
to 1 so that the package may be
+built on systems with a single core. Closes: #1055625.
+
+ -- Santiago Vila Sun, 12 Nov 2023 23:25:00 +0100
+
pyzoltan (1.0.1-5) unstable; urgency=medium
* Standards version bumped to 4.6.1 (non changes).
diff -Nru pyzoltan-1.0.1/debian/rules pyzoltan
Note: I should also include some changes in debian/salsa-ci.yml and gbp.conf.
The final debdiff may differ slightly in that minor detail only.
Thanks.
by switching to autopkgtest-pkg-pybuild. Closes: #1033822.
+ [ Bastian Germann ]
+ * Fix OpenSSL version parsing, take 1.
+ [ Arnaud Rebillout ]
+ * Fix OpenSSL version parsing, take 2. Closes: #1055598.
+
+ -- Santiago Vila Wed, 08 Nov 2023 21:38:44 +0100
+
oscrypto (1.3.0-1) unstable
are only skipped when the system has a single CPU.
+Closes: #1030885.
+
+ -- Santiago Vila Sun, 29 Oct 2023 21:45:00 +0100
+
python-cogent (2023.2.12a1+dfsg-2) unstable; urgency=medium
* Restrict to 64 bit architectures
diff -Nru
python-cogent-2023.2.12a1+dfsg/debian/patches/fix-build
Dear Release Managers:
Please reject the upload I made for bookworm.
Following the suggestion from Holger, I've fixed this issue
in the optimal way in unstable:
https://tracker.debian.org/news/1474401/accepted-python-cogent-2023212a1dfsg-4-source-into-unstable/
and now I'd like to upload the
: #1031063.
+
+ -- Santiago Vila Tue, 24 Oct 2023 09:50:00 +0200
+
wormhole-william (1.0.6-2) unstable; urgency=medium
* Don't run help2man at build time, instead generate man page
diff -Nru wormhole-william-1.0.6/debian/gbp.conf
wormhole-william-1.0.6/debian/gbp.conf
--- wormhole-william-1.
Hello.
It is just me, or lots of packages that were autoremoved
from testing have propagated to testing again this night?
Example: "broker" has #1037597, however:
$ rmadison broker
broker | 1.4.0+ds1-1 | oldstable | source
broker | 1.4.0+ds1-1 | stable | source
broker
El 21/10/23 a las 12:31, Holger Levsen escribió:
Santiago,
I don't object to fixing fails to build on a single core bugs, I just
object to fixing them by disabling tests *unconditionally*. A fix
disabling the tests on single core system *only* I would not object.
Ah, ok. Sorry for the
El 21/10/23 a las 11:33, Holger Levsen escribió:
Am Fri, Oct 20, 2023 at 07:40:55PM +0200 schrieb Santiago Vila:
+ * Update fix-build-on-single-cpu-systems.patch to skip
+"test_write_db_parallel" again. Closes: #1030885.
fwiw, I find it wrong to disable tests to make sure
/changelog 2023-10-20
19:04:00.0 +0200
@@ -1,3 +1,11 @@
+python-cogent (2023.2.12a1+dfsg-2+deb12u1) bookworm; urgency=medium
+
+ * Team upload.
+ * Update fix-build-on-single-cpu-systems.patch to skip
+"test_write_db_parallel" again. Closes: #1030885.
+
+ -- Santiago Vila F
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: python-cog...@packages.debian.org, sanv...@debian.org
Control: affects -1 + src:python-cogent
[ Reason ]
This upload fixes #1030885. FTBFS on single-CPU systems.
[
Hello Holger et al.
I was trying hard not to reply in this thread, but there are some things
that I'd like to point out and clarify.
El 10/10/23 a las 16:54, Holger Levsen escribió:
but why?
As Johannes has already replied, and I agree, there will be always
somebody annoyed, and we don't
buffer overwrite in search_brace(). Closes: #1049366.
+This one is CVE-2023-40305.
+
+ -- Santiago Vila Mon, 28 Aug 2023 12:55:00 +0200
+
indent (2.2.12-4+deb12u1) bookworm; urgency=medium
* Restore the ROUND_UP macro and adjust the initial buffer size.
diff -Nru indent-2.2.12/debian
El 1/8/23 a las 6:14, Kipp Cannon escribió:
Package: base-files
Version: 13
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
Version 13 of base-files removed VERSION_ID from /etc/os-release. As reported
in
reassign 1042805 base-files,release.debian.org
thanks
Note: I'm going to close this bug with a detailed explanation.
I'm doing a reassign first because it's something for which the
Release Managers have usually the last word.
Thanks.
the author, backported from 2.2.13.
+Fix memory handling problem. Closes: #1036851.
+
+ -- Santiago Vila Fri, 14 Jul 2023 13:40:00 +0200
+
indent (2.2.12-4) unstable; urgency=medium
[ Helge Deller ]
diff -Nru
indent-2.2.12/debian/patches/02-restore-round-up-macro-and-adjust-initial-buffer
El 1/4/23 a las 21:58, Adam D. Barratt escribió:
Have you confirmed via a binary debdiff that there are no changes to
the resulting packages?
The package contents is the expected one:
$ debdiff x4d-icons_1.2-2_all.deb x4d-icons_1.2-2+deb11u1_all.deb
File lists identical (after any
+
+ * QA upload.
+ * Apply two patches from bookworm to build with newer kernels:
+ - Patch: Linux 5.11 no longer has if_frad.h, from Ubuntu. Closes: #997222
+ - Patch: termiox removed since kernel 5.12, from ALT Linux.
+
+ -- Santiago Vila Tue, 21 Mar 2023 14:20:00 +0100
+
libexplain (1
s the same which was
+already applied in bookworm. Closes: #991067.
+ * The above patch requires raising debhelper compatibility level to 13.
+
+ -- Santiago Vila Tue, 21 Mar 2023 13:50:00 +0100
+
x4d-icons (1.2-2) unstable; urgency=medium
* QA upload.
diff -Nru x4d-icons-1.2/debian/
Closing as duplicate the one which has a greater bug number.
Sorry for the noise.
ttps://ftp.gnu.org/gnu/Licenses/ as they have
+minor editorial changes like trimming spaces, https, etc.
+ * Drop debian/current-md5sums-obsolete. Closes: #1009358.
+ * Ship a real debian/copyright file in source package instead of
+generating it at build time.
+ * Call dh_installchangelogs u
ttps://ftp.gnu.org/gnu/Licenses/ as they have
+minor editorial changes like trimming spaces, https, etc.
+ * Drop debian/current-md5sums-obsolete. Closes: #1009358.
+ * Ship a real debian/copyright file in source package instead of
+generating it at build time.
+ * Call dh_installchangel
El 16/2/23 a las 12:34, Daniel Leidert escribió:
Am Donnerstag, dem 16.02.2023 um 08:41 +0100 schrieb Paul Gevers:
Control: tags -1 moreinfo
Control: severity -1 normal
Hi Daniel,
On 16-02-2023 01:11, Daniel Leidert wrote:
I ask you to
find a reasonable approach to deal with this for the
El 21/9/22 a las 13:47, Ondřej Surý escribió:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
nmu bind-dyndb-ldap_11.6-3 . ANY . bullseye . -m "rebuild for
bind9_9.16.33-1~deb11u1"
Hi,
after the bind9_9.16.33-1~deb11u1 is release to
El 23/9/22 a las 10:21, Timo Aaltonen escribió:
Paul Gevers kirjoitti 22.9.2022 klo 22.26:
So, Timo, is the package in bullseye broken with the security update and does
it need a fix, or is it fine?
It needs a rebuild, [...]
I think it's really broken:
if_frad.h, from Ubuntu. Closes: #997222
+ - Patch: termiox removed since kernel 5.12, from ALT Linux.
+
+ -- Santiago Vila Wed, 07 Dec 2022 19:10:00 +0100
+
libexplain (1.4.D001-11) unstable; urgency=medium
* QA upload.
diff -Nru libexplain-1.4.D001/debian/patches/linux5.11.patch
libexplain
raising debhelper compatibility level to 13,
+which should not be a problem because debhelper 13 is in bullseye.
+
+ -- Santiago Vila Tue, 06 Dec 2022 17:50:00 +0100
+
x4d-icons (1.2-2) unstable; urgency=medium
* QA upload.
diff -Nru x4d-icons-1.2/debian/compat x4d-icons-1.2/debian/compat
Wilk using American Fuzzy Lop.
+Patch from Stephen R. van den Berg.
+
+ -- Santiago Vila Sun, 31 Jul 2022 20:10:00 +0200
+
procmail (3.22-26) unstable; urgency=medium
* Fix buffer overflow in loadbuf(). Closes: #876511.
diff -Nru procmail-3.22/debian/patches/31 procmail-3.22/debian
.22/debian/changelog 2022-07-02 13:20:00.0 +0200
@@ -1,3 +1,11 @@
+procmail (3.22-26+deb11u1) bullseye; urgency=medium
+
+ * Fix NULL pointer dereference. Closes: #769938.
+Reported by Jakub Wilk using American Fuzzy Lop.
+Patch from Stephen R. van den Berg.
+
+ -- Santiago Vila S
. Closes: #769938.
+Reported by Jakub Wilk using American Fuzzy Lop.
+Patch from Stephen R. van den Berg.
+
+ -- Santiago Vila Sat, 02 Jul 2022 13:20:00 +0200
+
procmail (3.22-26) unstable; urgency=medium
* Fix buffer overflow in loadbuf(). Closes: #876511.
diff -Nru procmail-3.22/debian
On Fri, May 14, 2021 at 10:21:31PM +0200, Paul Gevers wrote:
> Priority: required
> Maintainer: Santiago Vila
> Standards-Version: 4.1.3
> -Build-Depends: debhelper (>= 9)
> +Build-Depends: debhelper-compat (= 13)
>
> Please revert that [1] or show with diffoscop
11 as version number
+and "(bullseye)" as codename. Add also VERSION_ID and VERSION.
+(never expected to change)
+ - Add VERSION_CODENAME to os-release.
+(only expected on stable releases)
+ - Update README (bullseye -> bookworm).
+
+ -- Santiago Vila Sat, 10 Apr 2021 22:15:00
On Tue, May 04, 2021 at 11:48:09AM +0100, peter green wrote:
> > This was automatically closed by ftpmaster because the package was
> > removed from unstable, but this still does not fix the FTBFS problem
> > in stable.
>
> Unfortunately I don't think a proper fix will be forthcoming, upstream
>
On Thu, Nov 14, 2019 at 07:10:08PM +0100, Julien Cristau wrote:
> On Fri, Nov 08, 2019 at 01:17:20PM +0100, Santiago Vila wrote:
> > I received this bug from one of the ansible upstream authors:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931197
>
d fix a not-yet-fixed breakage
in lsb-release).
On Sun, Nov 10, 2019 at 01:14:12PM +, Holger Levsen wrote:
> On Sun, Nov 10, 2019 at 01:24:42PM +0100, Santiago Vila wrote:
> > Ok, I have just uploaded base-files as usual, but if possible I'd like
> > this to be sorted-out for 10.3 (
On Sat, Nov 09, 2019 at 03:33:26PM +, Adam D. Barratt wrote:
> On Sat, 2019-11-09 at 16:09 +0100, Santiago Vila wrote:
> > (If we can't sort this out for 10.2 I'll have to upload base-files
> > for 10.2 as usual. What's the real deadline for that? This weekend?)
>
>
On Sat, Nov 09, 2019 at 02:10:45PM +, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
>
> On Fri, 2019-11-08 at 13:17 +0100, Santiago Vila wrote:
> > I received this bug from one of the ansible upstream authors:
> >
> > https://bugs.debian.org/cgi-b
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Dear Release Managers:
I received this bug from one of the ansible upstream authors:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931197
asking to include information about
Debian 10, which in turn was extracted from
+upstream git. Should help the inkscape project. Closes: #891347.
+See https://gitlab.com/inkscape/inkscape/issues/271 for details.
+
+ -- Santiago Vila Sat, 31 Aug 2019 01:30:22 +0200
+
gettext (0.19.8.1-2) unstable; urgency=medium
* Use
-release. Closes: #829245. Please note
+that this is only for stable releases.
+
+ -- Santiago Vila Fri, 30 Aug 2019 10:45:44 +0200
+
base-files (9.9+deb9u9) stretch; urgency=medium
* Change /etc/debian_version to 9.9, for Debian 9.9 point release.
diff -Nru base-files-9.9+deb9u9/etc
Hi.
I'm still tracking FTBFS bugs in buster. Am I right to think that this
upload for stable (when accepted) will fix Bugs #931002 and #931003 in
rust-coresimd and rust-simd, making them buildable again?
(Those bugs have been closed automatically by FTPmaster, but the automatic
script does not
.
+ - Do not raise a zip bomb alert for a misplaced central directory.
+Reported by Peter Green. Closes: #932404.
+
+ -- Santiago Vila Mon, 05 Aug 2019 18:10:06 +0200
+
unzip (6.0-21+deb9u1) stretch; urgency=medium
* Fix buffer overflow in password protected ZIP archives. Closes: #889838
On Sat, Jul 27, 2019 at 01:38:46PM -0300, Adam D. Barratt wrote:
> On 2019-07-27 13:18, Santiago Vila wrote:
> > tags 932318 - moreinfo
> > thanks
> >
> > Hello.
> >
> > The problem with Firefox should now be fixed, and it was unzip's fault.
> >
&g
tags 932318 - moreinfo
thanks
Hello.
The problem with Firefox should now be fixed, and it was unzip's fault.
If possible, I'd like this upload I did 6.0-23+deb10u1 to be rejected so that
I can reuse the +deb10u1 version with all the fixes included.
Thanks.
Dear Release Managers:
Please leave this package unapproved for now.
It has some side-effects (like firefox FTBFS) which need to be
investigated:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932404
I have the feeling that this will be another case of buggy zipfile,
like this one:
in undefer_input() that misplaced the input state.
+ - Detect and reject a zip bomb using overlapped entries. Closes: #931433.
+Bug discovered by David Fifield. For reference, this is CVE-2019-13232.
+
+ -- Santiago Vila Wed, 17 Jul 2019 16:35:30 +0200
+
unzip (6.0-23) unstable; urgency=medium
On Fri, May 17, 2019 at 10:00:17PM +0200, Paul Gevers wrote:
> Hi,
>
> On 16-05-2019 22:03, Holger Levsen wrote:
> > On Thu, May 16, 2019 at 09:52:45PM +0200, Paul Gevers wrote:
> >> Well, if they are maintained by the QA group, there are at least around
> >> 90 people notified of stuff.
> >
> >
On Thu, May 16, 2019 at 07:43:09PM +0200, Paul Gevers wrote:
> The reason why it got removed, is that nobody was looking after razor.
> Otherwise, preventing removal would have been easy.
Indeed. If I had known that it was going to be removed, I would have
downgraded the severity of the bug
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal
Please allow razor back in testing, as a freeze exception.
It was autoremoved because there was a RC bug in the BTS, but the
real problem was not in the package itself but in the razor
+
+ * Add Breaks: debian-security-support (<< 2019.04.25). Closes: #928172.
+This is the first version of debian-security-support which does not break
+when /etc/debian_version contains a string in the form "10.x".
+
+ -- Santiago Vila Mon, 13 May 2019 22:25:32 +0200
+
+
.0 +0100
@@ -1 +0,0 @@
-9
diff -Nru hello-2.10/debian/control hello-2.10/debian/control
--- hello-2.10/debian/control 2015-03-22 11:00:00.0 +0100
+++ hello-2.10/debian/control 2019-05-12 22:26:59.0 +0200
@@ -2,9 +2,10 @@
Section: devel
Priority: optional
Maintainer: San
On Mon, Apr 15, 2019 at 07:57:20AM +0200, Salvatore Bonaccorso wrote:
> Hi Niels, release team and ftp-masters,
>
> [dropping backports list for this reply, adding ftp-masters]
>
> On Sun, Apr 14, 2019 at 09:02:00PM +, Niels Thykier wrote:
> > Hi Security team and backports team,
> >
> >
+0200
@@ -1,3 +1,9 @@
+diffutils (1:3.7-3) unstable; urgency=medium
+
+ * Disable tests/colors completely for buster. Closes: #922552.
+
+ -- Santiago Vila Mon, 08 Apr 2019 14:04:00 +0200
+
diffutils (1:3.7-2) unstable; urgency=low
* Increase sleeping time from 1 to 5 seconds in tests
; urgency=medium
+
+ * Fix buffer overflow in password protected ZIP archives. Closes: #889838.
+Patch borrowed from SUSE. For reference, this is CVE-2018-135.
+
+ -- Santiago Vila Sun, 10 Feb 2019 20:53:00 +0100
+
unzip (6.0-21) unstable; urgency=medium
* Rename all debian/patches
> I wish I could say unconditionally yes, but I am not sure we are ready
> for it yet. If your testing can trivially say which relation in
> Build-Depends/Build-Depends-Arch is broken, you could cross reference it
> with the [excuses] and see if they are permanently rejected due (and why).
>
> I
Package: release.debian.org
Severity: wishlist
Dear Release Managers:
I'm looking for guidance and advice here.
I'm reporting FTBFS bugs in testing, but I'm skipping bugs of type
"unmet build-depends" because I've heard somewhere that Britney takes
care of that.
However, I don't see the
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release Managers: I wish this package to be unblocked:
unblock ruby-benchmark-suite/1.0.0+git.20130122.5bded6-2
It was removed from testing because of a FTBFS bug:
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 Sun, Jan 22, 2017 at 04:41:59PM -0500, Nathan Scott wrote:
> > This is happening again and again (see bugs 776440 and 847149). The fix
> > here is to get rid of the package until the maintainer catches up, not
> > to work around him time and time again, IMO.
>
> I'm planning to start
On Wed, 4 Jan 2017, Santiago Vila wrote:
> Please help me to ensure that we are not removing (yet!) any package
> from stretch because of any of such bugs (I think this mass-severity-setting
> should yield such effect, but I'm not 100% sure).
>
> In particular, please let a
user release.debian@packages.debian.org
usertag 851530 + age-days
thanks
point release)
+ - Change PRETTY_NAME in /usr/lib/os-release, adding 9 as version number
+and "(stretch)" as codename. Add also VERSION_ID and VERSION.
+(never expected to change)
+ - Update README (stretch -> buster).
+ * Standards-Version: 3.9.8 (no special changes for this).
Package: release.debian.org
Severity: wishlist
Dear Release Managers:
I've just uploaded a base-files version which should be suitable
for stretch when it becomes stable.
I'd like the 10-days period to be reduced a little bit, if only
because d-i people are already making beta releases.
The
Us. Closes: #850979.
+
+ -- Santiago Vila <sanv...@debian.org> Sun, 15 Jan 2017 23:36:12 +0100
+
crafty (23.4-6) unstable; urgency=low
* Ubuntus oneiric build faild, because with linking the order of
diff -Nru crafty-23.4/debian/patches/07-drop-cpu-specific-code.patch
crafty-23.4/debian/pat
44, buffer overflow in zipinfo. Closes: #847486.
+Patch by the author.
+
+ -- Santiago Vila <sanv...@debian.org> Sun, 15 Jan 2017 23:30:30 +0100
+
unzip (6.0-16+deb8u2) jessie-security; urgency=high
* Non-maintainer upload by the Security Team.
diff -Nru unzip-6.0/debian/patches/12-cv
On Tue, Jan 10, 2017 at 06:23:27PM +, Ben Hutchings wrote:
> On Tue, 2017-01-10 at 18:05 +0000, Santiago Vila wrote:
> > On Tue, Jan 10, 2017 at 05:04:50PM +, Ben Hutchings wrote:
> > > I intend to upload linux version 4.9.2-1 to unstable tomorrow
> > > (We
On Tue, Jan 10, 2017 at 05:04:50PM +, Ben Hutchings wrote:
> I intend to upload linux version 4.9.2-1 to unstable tomorrow
> (Wednesday). As this is a new upstream version, there is of course an
> ABI bump.
Hi.
(Sorry if this is already reported, last time I looked at the bug page
I didn't
On Tue, Jan 10, 2017 at 05:04:50PM +, Ben Hutchings wrote:
> I intend to upload linux version 4.9.2-1 to unstable tomorrow
> (Wednesday). As this is a new upstream version, there is of course an
> ABI bump.
Hi.
(Sorry if this is already reported, last time I looked at the bug page it was
Package: release.debian.org
Dear Release Managers:
I've just set the severity of all open bugs in this list to "important":
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=sanv...@debian.org;tag=ftbfs-randomly
(I said in Bug#844264 that I would do something like that. My initial
plan was
On Fri, Dec 30, 2016 at 07:31:00AM +, Niels Thykier wrote:
> Thanks for your interest in this subject and for wanting to increase the
> stability of builds in Debian.
>
> As Julien mentioned earlier, build failures are sadly not as black and
> white as one might want them to be. Especially
Dear Release Managers:
If Release Policy wording is not going to be clarified in any way, that's ok.
Let's assume, for example [1, 2], that I found a package which FTBFS
more than 90% of the time on single-CPU machines, and rarely on
buildd.debian.org.
I do think that such bugs should still be
On Thu, 22 Dec 2016, Florian Schlichting wrote:
> On Wed, Dec 21, 2016 at 11:04:34PM +0100, Santiago Vila wrote:
> > So, if establishing a threshold is the only way to achieve that for
> > example Bug #843038 in "elki" is upgraded to serious again, so be it,
> > bu
On Wed, Dec 21, 2016 at 11:28:15PM +0200, Niko Tyni wrote:
> A severity:important bug does not mean it's all "ok". It means it's
> still a bug, but we can release with it. Autobuilders can build the
> package given a sane number of tries, security uploads can be built
> etc. If they can't due to
On Wed, Dec 21, 2016 at 07:26:59PM +0100, Julien Cristau wrote:
> On Sun, Dec 18, 2016 at 12:21:19 +0100, Santiago Vila wrote:
>
> > Do you mean it's better not to have a common rule for these bugs and
> > instead decide on a case by case basis?
> >
> > C
On Sun, Dec 18, 2016 at 04:36:57PM +0500, Andrey Rahmatullin wrote:
> On Sun, Dec 18, 2016 at 12:21:19PM +0100, Santiago Vila wrote:
> > The alternative is what it's currently happening: "Why bother to ask
> > for permission to use stretch-ignore tag when you can always do
On Sat, Dec 17, 2016 at 10:48:00AM +0100, Julien Cristau wrote:
> On Thu, Dec 15, 2016 at 21:19:23 +0100, Santiago Vila wrote:
>
> > Any progress on this?
> >
> > In case it helps, I made a list of bugs in this FTBFS-randomly category:
> >
> > https://bugs.
Any progress on this?
In case it helps, I made a list of bugs in this FTBFS-randomly category:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-randomly;users=sanv...@debian.org
In almost all cases, the failure happens because there is a test which
fails.
So: Why do we allow tests to
+
+ * Add debian/patches/03-cve-2016-8859 to fix CVE-2016-8859.
+Patch borrowed from wheezy LTS. Closes: #842169.
+ * Add locales-all to Build-Depends, required to run the test suite.
+ * Add debian/clean with files generated/modified during the build.
+
+ -- Santiago Vila <sanv...@debian.
Package: release.debian.org
Severity: wishlist
Dear Release Managers:
Release Policy here
https://release.debian.org/stretch/rc_policy.txt
says:
"Packages must autobuild without failure on all architectures on which
they are supported".
Please clarify how should this policy be applied when
On Sun, 2 Oct 2016, Emilio Pozuelo Monfort wrote:
> > It is resolved in the sense it was agreed to make this RC,
> > but I still expected the release policy to be updated accordingly:
> >
> > https://release.debian.org/stretch/rc_policy.txt
> >
> > before closing this report.
>
> I looked at
On Sat, Sep 17, 2016 at 10:16:56PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Mon, 2016-09-12 at 15:49 +0200, Santiago Vila wrote:
> > I'd like to see Bugs #774347 and #835516 fixed in jessie.
> > (This is the bug that makes /bin to be 775, not
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
Dear release team:
I'd like to see Bugs #774347 and #835516 fixed in jessie.
(This is the bug that makes /bin to be 775, not 755, on new installs).
(Well, maybe not the only one,
1 - 100 of 227 matches
Mail list logo
