Bug#1095200: unblock rust-sqlx/0.8.3-1 rust-sqlx-core/0.8.3-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock rust-sqlx-core and rust-sqlx seem to be blocked by some autopkgtest snarlups, particularly 3 autopkgtests seem to be stuck in "test in progress". The test for rust-ognibuild with the new r

[Pkg-rust-maintainers] Updates to the trixie freeze policy

>Milestone 1: Toolchain and d-i freeze > > >Milestone 2 (Milestone 1 + 2 months): Transition freeze The big question, for those of us who were anticiapting a schedule similar to trixie is does this mean. Toolchain freeze two months earlier than anticipated or transition freeze two months later

Bug#1084824: unblock: rust-sqlx-postgres/0.8.2-3 rust-debversion/0.4.3-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock I am trying to get the new versions of rust-sqlx and related packages into testing, this is a prerequisite for getting the new version of rust-base64 into testing. It's currently blocked b

Bug#1082798: unblock: rust-sequoia-keystore-tpm/0.1.0-2

On 26/09/2024 16:02, Paul Gevers wrote: Hi Peter, On 26-09-2024 16:24, Peter Green wrote: Firstly britney is scheduling tests with the old version of rust-sequoia-keystore and the new version of rust-sequoia-keystore-tpm, despite the fact that the old version of rust-sequoia-keystore does not

Bug#1082798: unblock: rust-sequoia-keystore-tpm/0.1.0-2

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock rust-sequoia-keystore-tpm is blocked from migrating to testing by two issues. I do not believe either of these issues represent real issues in the rust-sequoia-keystore-tpm package and ther

Bug#1080982: unblock: rust-unicode-width/0.1.13-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock rust-unicode-width is blocked from migrating to testing by autopkgtest failures in rust-tui. rust-tui is abandoned upstream and we intend to get rid of it (see bugs 1080293 and 1080400). Up

Bug#1079355: unblock: rust-sqlx/0.7.3-4

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock rust-sqlx, it is currently blocked by an autopkgtest "regression" of rust-debversion on riscv64, which is caused by the fact that rust-debversion is uninstable in testing on

Bug#1079040: unblock: rust-debian-copyright/0.1.13-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock rust-debian-copyright, it is currently blocked by an autopkgtest "regression" of rust-debian-analyzer on riscv64, which is caused by the fact that rust-debian-analyzer is uni

Bug#1077284: unblock: rust-debian-copyright/0.1.13-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock rust-debian-copyright, it is currently blocked by an autopkgtest "pregression" of rust-debian-analyzer on riscv64, which is caused by the fact that rust-debian-analyzer is un

Bug#1077958: nmu: rust-async-broadcast_0.7.1-1

That's why the test timeout on riscv64 is double that of other architectures: Unfortunately in many cases, the performance difference seems a lot more than a factor of two. Take rust-gix for example, looking at the results for testing migration tests I see 18-28m on amd64 53-59m on arm64 33-47

Bug#1073193: bookworm-pu: package tor/0.4.8.12-X

-/blob/tor-0.4.7.16/src/app/config/auth_dirs.inc?ref_type=tags with https://gitlab.torproject.org/tpo/core/tor/-/blob/tor-0.4.8.12/src/app/config/auth_dirs.inc?ref_type=tags -- | .''`. ** Debian ** Peter Palfrader | : :' :

Bug#1068106: bookworm-pu: package libarchive/3.6.2-1+deb12u1

On Sat, Mar 30, 2024 at 08:51:10PM +0200, Peter Pentchev wrote: > Package: release.debian.org > Severity: normal > Tags: bookworm > X-Debbugs-Cc: libarch...@packages.debian.org, r...@debian.org > Control: affects -1 + src:libarchive > User: release.debian@packages.debian.

Bug#1068106: bookworm-pu: package libarchive/3.6.2-1+deb12u1

chive-3.6.2/debian/changelog 2024-03-30 20:36:47.0 +0200 @@ -1,3 +1,9 @@ +libarchive (3.6.2-1+deb12u1) bookworm; urgency=medium + + * Add the robust-error-reporting upstream patch. Closes: #1068047 + + -- Peter Pentchev Sat, 30 Mar 2024 20:36:47 +0200 + libarchive (3.6.2-1) unstable; ur

Bug#1061487: bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1

On Mon, Jan 29, 2024 at 09:51:45PM +, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Thu, 2024-01-25 at 14:39 +0200, Peter Pentchev wrote: > > Version 4.18 of RPM changed the format of its internal database > > from the traditional BerkeleyDB one to a new

Bug#1061487: bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1

. Closes: #1061258 + + -- Peter Pentchev Thu, 25 Jan 2024 14:18:24 +0200 + rpm (4.18.0+dfsg-1) unstable; urgency=medium * Team upload. diff -Nru rpm-4.18.0+dfsg/debian/rules rpm-4.18.0+dfsg/debian/rules --- rpm-4.18.0+dfsg/debian/rules2023-01-05 20:29:48.0 +0200 +++ rpm-4.18.0

Bug#1053800: transition: libgit2

The Rust Team did not react. Too bad. Please raise the bug to RC. Apologies for not engaging with this sooner, I had mentally filed it as "deal with this once the cargo update is done" but the cargo update has been taking a lot longer than hoped. I've uploaded a new version of the rust bindin

re: rust-grep-regex REMOVED from testing

Previous version: 0.1.11-1 Current version: (not in testing) Hint: # 2023-11-04 # blocks lots of packages from migrating # 1053431 Assuming your goal was to allow rust-regex and friends to migrate to testing, you will also want

Bug#1050113: unblock: rust-rustls-webpki/0.101.3-1.1

Reopen 1050113 thanks Bumped the hint to 0.101.3-2. Testing migration was unfortunately interrupted by a security bug. then some follow-up issues with the new upstream version uploaded to fix the security bug. Can you update the hint to 0.101.4-4?

Bug#1035304: Bug#1038451: bullseye-pu: package systemd/247.3-7+deb11u4

text looks good to me, but I think u3 also fixed a memory leak?

Bug#1035304: Info received (please ship this to bullseye-updates)

plus Cc to pkg-systemd-maintainers

Bug#1035304: please ship this to bullseye-updates

Hello! Just in my immediate surroundings, around one person a week is hit by the udev serial/by-id bug that this version (deb11u3) fixes. Can you push it to bullseye-updates? I understand this will also push deb11u4, which seems good to me too. Thank you! -- Peter van Dijk pe...@7bits.nl

Bug#1041555: bookworm-pu: package stunnel4/3:5.68-2+deb12u1

nection without proper TLS shutdown messaging. +Closes: #1041545 + + -- Peter Pentchev Thu, 20 Jul 2023 22:01:31 +0300 + stunnel4 (3:5.68-2) unstable; urgency=medium * Add the 07-tests-errmsg patch to fix the FTBFS on several architectures diff -Nru stunnel4-5.68/debian/patches/08-tls-eof.pat

Bug#1036002: unblock: utf8-locale/1.0.0-2

n the library one. +Closes: #1035441 + * Add the year 2023 to my debian/* copyright notice + * Declare compliance with Policy 4.6.2 with no changes + + -- Peter Pentchev Thu, 04 May 2023 21:30:41 +0300 + utf8-locale (1.0.0-1) unstable; urgency=medium * Declare compliance with Policy 4.6.1

Bug#1036000: unblock: sniproxy/0.6.0-2.1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: snipr...@packages.debian.org, snipr...@packages.debian.org, r...@debian.org Control: affects -1 + src:sniproxy Please unblock package sniproxy Version 0.6.0-2.1 fixes the #10

Bug#1035034: unblock: libmodulemd/2.14.0-3

Control: tags -1 -moreinfo On Fri, Apr 28, 2023 at 08:55:51PM +0200, Sebastian Ramacher wrote: > Control: tags -1 moreinfo confirmed > > On 2023-04-28 04:58:51 +0300, Peter Pentchev wrote: > > Package: release.debian.org > > Severity: normal > > User: release.deb

Re: librust---dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye

On 28/04/2023 06:05, Helmut Grohne wrote: Can you go into more detail as to what you mean with "don't support version ranges"? You can place a lower bound on the version, place an upper bound on the version or constrain to a precise version. But you can't constrain to a range of versions. I

Bug#1035034: unblock: libmodulemd/2.14.0-3

+Replaces older versions of +the -dev one. Closes: #1034935 + + -- Peter Pentchev Fri, 28 Apr 2023 04:48:28 +0300 + libmodulemd (2.14.0-2) unstable; urgency=medium * Use the GitHub API in the watch file. diff -Nru libmodulemd-2.14.0/debian/control libmodulemd-2.14.0/debian/control

Re: librust---dev: missing Breaks+Replaces for librust-mio-dev when upgrading from bullseye

Summarising a number of bug reports by Helmut Ghrone: Please ensure that librust---dev has sufficient Breaks and Replaces declarations. The issue specifically appears to be that the breaks+replaces are declared against a virtual package, it seems dpkg is honoring the breaks against the virtua

reason for removal of zeroc-ice on armhf and arm64.

I recently became aware that mumble's build-dependencies were no longer satisfiable on armhf due to a missing zeroc-ice. I looked at the build logs for zeroc-ice and all were green. So I looked at the removal log and found the following. [Date: Sun, 12 Feb 2023 17:56:51 -] [ftpmaster: Scott

Re: Testing migration with pending autopkgtest

on-policy-issues.html#britney-complains-about-autopkgtest Peter

Bug#1013631: nmu: xnee_3.19-8

On Fri, Jun 24, 2022 at 03:09:43PM +0300, Peter Pentchev wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > X-Debbugs-Cc: r...@debian.org > > nmu xnee_3.19-8 . ANY . unstable . -m "Chase fun

Bug#1013631: nmu: xnee_3.19-8

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu X-Debbugs-Cc: r...@debian.org nmu xnee_3.19-8 . ANY . unstable . -m "Chase functions broken out into the libXi.so.6 library. Closes: #1013581"

Re: Apparently uncoordinated libnetpbm transition.

On 25/04/2022 14:55, Paul Gevers wrote: Hi Andreas, On 07-04-2022 09:21, Andreas Tille wrote: Sorry, that's my fault.  I'm preparing an upload to fix #1007984 targeting new. Looking at https://ftp-master.debian.org/new/netpbm-free_2:10.98.00-1.html, is there any reason why you didn't add "Pr

Bug#1009080: transition: libgit2

libgit2-glib has now been fixed, so I believe it is time to binnmu git-evtag and gnome-builder, both packages were sucessfully binnmu'd in raspbian.

testing migration of mir-core and stdx-allocator binnmus

I noticed that stdx-allocator had unsatisfiable build-dependencies in testing, checking why I discovered that this was because the mir-core binnmus had not migrated to testing. The update_output says. trying: mir-core/i386 skipped: mir-core/i386 (0, 37, 5) got: 25+0: a-1:a-21:a-0:a-0:i-2:m-0

Apparently uncoordinated libnetpbm transition.

A new version of netpbm-free was recently uploaded to unstable which replaced the libnetpbm9, libnetpbm9-dev, libnetpbm10 and libnetpbm10-dev packages with libnetpbm11 and libnetpbm11-dev packages. I could not find any evidence of an attempt to coordinate this transition with the release team, no

Bug#1006522: bullseye-pu: package djbdns/1:1.05-13+deb11u1

autopkgtest suite's Python code is cleaned up. The autopkgtest suite performs an additional check: run a lot of queries against a tinydns server to make sure it keeps responding. Thanks in advance for looking at this, and keep up the great work! G'luck, Peter diff -Nru djbdns-1.05/debia

Britney says "Rejected due to piuparts regression"but piuparts.debian.org says "succesfully tested".

https://tracker.debian.org/pkg/rust-gtk says "Rejected due to piuparts regression - https://piuparts.debian.org/sid/source/r/rust-gtk.html"; but when I follow that link it says "successfully-tested 0.14.3-1". This has been the case for several days so it doesn't appear to be a transient issue o

Bug#1002703: bullseye-pu: package libarchive/3.4.3-2+deb11u1

On Thu, Dec 30, 2021 at 09:10:34PM +0100, Salvatore Bonaccorso wrote: > Hi Peter, > > On Mon, Dec 27, 2021 at 10:10:58PM +0200, Peter Pentchev wrote: > > Package: release.debian.org > > Severity: normal > > Tags: bullseye > > User: release.debian@packages.

Bug#1002703: bullseye-pu: package libarchive/3.4.3-2+deb11u1

dling of symlink ACLs; Closes: 1001986 +- never follow symlinks when setting file flags; Closes: 1001990 + + -- Peter Pentchev Mon, 27 Dec 2021 18:45:51 +0200 + libarchive (3.4.3-2) unstable; urgency=medium * Add some more upstream patches: diff -Nru libarchive-3.4.3/debian/patches/s

Bug#1002685: bullseye-pu: package prips/1.1.1-3+deb11u1

+- fix-different-cidr: fix the CIDR (-c) output when the addresses + differ in their very first bit. Closes: #1001924 + + -- Peter Pentchev Sun, 26 Dec 2021 23:15:45 +0200 + prips (1.1.1-3) unstable; urgency=medium * Declare compliance with Debian Policy 4.5.0 with no changes. diff -Nru

Bug#993079: release.debian.org: autopkgtest scheduling does not seem to understand virtual packages correctly.

On 27/08/2021 10:10, plugwash wrote: Britney now seems to understand versioned virtual packages (at least in simple cases) for the main migration and for auto removals, but it still does not seem to properly understand them for testing migration.Typo, that should have said "it still does not see

Bug#992688: nmu: tor_0.4.5.10-1

needed as that does not ship systemd files. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/

Bug#991787: unblock: ucspi-unix/1.0-2

On Tue, Aug 03, 2021 at 09:19:27AM +0200, Sebastian Ramacher wrote: > On 2021-08-02 01:52:18 +0300, Peter Pentchev wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > X-Debbugs-Cc: r

Bug#991787: unblock: ucspi-unix/1.0-2

/changelog --- ucspi-unix-1.0/debian/changelog 2018-11-28 06:26:16.0 +0200 +++ ucspi-unix-1.0/debian/changelog 2021-08-02 01:36:27.0 +0300 @@ -1,3 +1,14 @@ +ucspi-unix (1.0-2) unstable; urgency=medium + + [ Dmitry Bogatov ] + * Add a Gitlab CI config file. + + [ Pete

Bug#990880: unblock: nomad/0.12.10+dfsg1-3

5 and add it as +the disable-cap-net-raw patch. Closes: #990581 + + -- Peter Pentchev Sat, 10 Jul 2021 02:29:09 +0300 + nomad (0.12.10+dfsg1-2) unstable; urgency=medium * Disabled "TestConfig_outgoingWrapper_OK" (Closes: #987644). diff -Nru nomad-0.12.10+dfsg1/debian/patches/

Bug#990766: unblock: kakoune/2020.01.16-3

0.01.16-3) unstable; urgency=medium + + * Add the 13-upstream-check-dir-owner and 14-upstream-rework-dir-logic +patches from the upstream Git repository to stop kakoune started as +root from making its runtime directory inaccessible to the normal +user account of the session user. Closes: #990

Bug#990455: unblock: rpm/4.16.1.2+dfsg1-2

Control: retitle -1 unblock: rpm/4.16.1.2+dfsg1-3 On Wed, Jun 30, 2021 at 02:15:43AM +0300, Peter Pentchev wrote: > On Tue, Jun 29, 2021 at 09:02:43PM +0200, Sebastian Ramacher wrote: > > Control: tags -1 moreinfo > > > > On 2021-06-29 20:15:33 +0300, Peter Pentchev wrote:

Bug#990455: unblock: rpm/4.16.1.2+dfsg1-2

On Tue, Jun 29, 2021 at 09:02:43PM +0200, Sebastian Ramacher wrote: > Control: tags -1 moreinfo > > On 2021-06-29 20:15:33 +0300, Peter Pentchev wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > U

Bug#990455: unblock: rpm/4.16.1.2+dfsg1-2

+0300 @@ -1,3 +1,35 @@ +rpm (4.16.1.2+dfsg1-2) unstable; urgency=medium + + * Team upload. + * Amend the CVE-2021-3421-CVE-2021-20271 patch, add two follow-up +upstream commits that relax the restrictions a little bit to +allow for some existing RPM packages. + + -- Peter Pentchev Tue, 29 Jun

Bug#990372: buster-pu: package feature-check/0.2.2-3

rsion +string comparisons. Closes: #990276 + + -- Peter Pentchev Sun, 27 Jun 2021 17:49:55 +0300 + feature-check (0.2.2-3) unstable; urgency=medium * Switch to a DEP-14 debian/master branch. diff -Nru feature-check-0.2.2/debian/patches/cmp-num.patch feature-check-0.2.2/debian/patches/cm

Bug#990370: unblock: alttab/1.5.0-2

64357 + + -- Peter Pentchev Sun, 27 Jun 2021 16:57:21 +0300 + alttab (1.5.0-1) unstable; urgency=medium * New upstream release diff -Nru alttab-1.5.0/debian/control alttab-1.5.0/debian/control --- alttab-1.5.0/debian/control 2020-07-23 12:19:05.0 +0300 +++ alttab-1.5.0/debian/control

Bug#990356: unblock: donkey/1.2.0-6

not always +sending us the full output of the command that was run. +Closes: #990355 + + -- Peter Pentchev Sun, 27 Jun 2021 01:00:00 +0300 + donkey (1.2.0-5) unstable; urgency=medium * Disable the "stringop-truncation" GCC warning: our use of strncpy() diff -Nru donkey-1.2.0

Bug#990277: unblock: feature-check/0.2.2-7

Control: tags -1 -moreinfo On Fri, Jun 25, 2021 at 08:39:02PM +0200, Sebastian Ramacher wrote: > Control: tags -1 moreinfo confirmed > > On 2021-06-24 15:42:28 +0300, Peter Pentchev wrote: > > Package: release.debian.org > > Severity: normal > > User: release.deb

Bug#990277: unblock: feature-check/0.2.2-7

-0.2.2/debian/changelog2021-06-24 15:33:07.0 +0300 @@ -1,3 +1,10 @@ +feature-check (0.2.2-7) unstable; urgency=medium + + * Add the cmp-num and cmp-rest upstream patches to fix some version +string comparisons. Closes: #990276 + + -- Peter Pentchev Thu, 24 Jun 2021 15:33:07

Bug#990102: nmu: qosmic_1.6.0-4

lem, https://tracker.debian.org/media/packages/f/flam3/changelog-3.1.1-4 and qosmic builds using flam3 via static library. qosmic was last built using flam3_3.1.1-2+b1 Please nmu qosmic on ANY. Regards, Peter

Bug#990068: unblock: tor/0.4.5.9-1

ooner? Thanks, weasel -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System | `-https://www.debian.org/

Bug#988453: rust-rustyline 3.0.0-2+deb10u2 flagged for acceptance

49:59.0 + +++ rust-rustyline-3.0.0/debian/changelog 2021-06-12 15:19:47.0 + @@ -1,3 +1,11 @@ +rust-rustyline (3.0.0-2+deb10u3) buster; urgency=medium + + * Team upload. + * Apply another upstream patch so that the code builds with +both rustc 1.34 and rustc 1.

Bug#988453: buster-pu: package rust-rustyline/3.0.0-2

2021-06-11 14:49:59.0 + @@ -1,3 +1,12 @@ +rust-rustyline (3.0.0-2+deb10u2) buster; urgency=medium + + * Team upload. + * Reset timestamp on .cargo-vcs-info.json to avoid +1970 timestamp which triggers a ftpmaster autoreject. +(Closes: 989636) + + -- Peter Michael Green Fri,

Bug#988453: buster-pu: package rust-rustyline/3.0.0-2

On 29/05/2021 15:17, Adam D. Barratt wrote: Control: tags -1 + confirmed On Thu, 2021-05-13 at 11:13 +0100, plugwash wrote: rust-rustyline fails to build in buster due to a change of behaviour in rustc, this has been fixed in bullseye/sid for some time and I was able to locate the upstream comm

Bug#988634: unblock: tor/0.4.5.8-1

tags -1 - moreinfo On Mon, 17 May 2021, Sebastian Ramacher wrote: > On 2021-05-17 06:53:02 +0000, Peter Palfrader wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: unblock > > > >

Bug#988634: unblock: tor/0.4.5.8-1

ems. Fixes bug 40318; bugfix on 0.4.5.1-alpha. Patch by } Daniel Pinto. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `' Operating System

Bug#988412: unblock: stunnel4/3:5.56+dfsg-10

-10) unstable; urgency=medium + + * Allocate a new memory buffer for the pidfile path in +the 04-restore-pidfile-default patch, since it may be freed when +stunnel is reconfigured, e.g. on a SIGHUP. +Closes: #987265; LP: #1901784 + + -- Peter Pentchev Wed, 21 Apr 2021 09:12:28 +0300

Re: Fixing rust package FTBFS in buster

On 08/05/2021 17:36, Adrian Bunk wrote: On Wed, May 05, 2021 at 08:01:13AM +0100, peter green wrote: On 04/05/2021 12:28, Santiago Vila wrote: 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

Fixing rust package FTBFS in buster (was: Bug#931003: Removed package(s) from unstable )

On 04/05/2021 12:28, Santiago Vila wrote: 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 prope

re: Bug#931003: Bug#931003: Removed package(s) from unstable

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 has abandoned the crate in question. Afaict the only purpose this package ser

Re: test bullseye upgrade of DSA maintained machines

orking as they should on bullseye. That sounds about right. Time/tuits permitting, and that's probably a limiting factor these days. -- | .''`. ** Debian ** Peter Palfrader | : :' : The

Re: Release status of i386 for Bullseye and long term support for 3 years?

Then there was the short netbook boom, but AFAIR some early ones had 64bit CPUs but 32bit-only firmware. My memory is that at the height of the boom the dominant processors were the N270 and N280, which are 32-bit only. By the time 64-bit netbook processors showed up the boom was on the dec

Bug#971571: transition: libgit2

I've rebuilt the relevant reverse-build-dependencies from unstable In addition to the packages mentioned here, it seems there is another package involved: golang-gopkg-libgit2-git2go.v28 . It only builds arch-all packages and does not directly depend on the library, but it FTBFS and it's autopkg

Bug#975297: buster-pu: package tor/3.5.12-1

On Fri, 20 Nov 2020, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > Hi, > > On Fri, 2020-11-20 at 07:43 +, Peter Palfrader wrote: > > Stable currently has Tor 0.3.5.10. > > > > Upstream released 0.3.5.11 and 0.3.5.12 since, which bring some >

Bug#975297: buster-pu: package tor/3.5.12-1

On Fri, 20 Nov 2020, Peter Palfrader wrote: > I would like to build and upload packages for tor 3.5.12. Actually, that's 0.3.5.12, and the package would be 0.3.5.12-1. -- | .''`. ** Debian ** Peter Palfrader | : :' :

Bug#975297: buster-pu: package tor/3.5.12-1

things more. See https://gitweb.torproject.org/tor.git/tree/ChangeLog?h=tor-0.3.5.12 for a full list. I would like to build and upload packages for tor 3.5.12. Please ack? -- | .''`. ** Debian ** Peter Palfrader | : :' : The u

Bug#970132: buster-pu: package rustc/1.41.1+dfsg1-1~deb10u1

On 17/09/2020 15:06, Emilio Pozuelo Monfort wrote: On 12/09/2020 11:09, Emilio Pozuelo Monfort wrote: This updates buster's rustc to 1.41, as needed by the new firefox 78 ESR. The bootstrap happens with the upstream binaries as we've done in the past. I have also avoided the bump to LLVM 9/10, w

android-framework-23 autorm weirdness.

The tracker for android-framework-23 shows it as due for autoremoval today (and IIRC has been saying that for some time) , and indeed britney is trying to remove it but is failing to do so. Strangely the tracker for andriod-framework-23 says it will cause the autoremoval of android-platform-dal

Bug#969158: expeyes: maybe a false positive generated by mail_autoremovals.pl?

(note: this mail represents my opinions as an ordinary dd, I am not a member of the release team) due to the fact that it is supposed to (build-)depend on binutils-avr, which FTBFS. As I understand it "(build-)depends" should be interpreted as "depends or build-depends" The source package e

charliecloud: Overdue migration to testing

, Peter [0] https://qa.debian.org/excuses.php?package=charliecloud [1] https://tracker.debian.org/pkg/charliecloud

Bug#962563: transition: nettle

I just went through the remaining items on the transition tracker for this transition filing bug reports where appropriate. freewheeling: sid-only, unrelated FTBFS bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946863 haskell-hopenpgp/haskell-hopenpgp-tools: haskell-incremental-parser h

Is it time to remove python-numpy from testing?

python-numpy* is no longer buildable in testing due to the removal of the "cython" binary package. The maintainer has requested removal of python-numpy from unstable but the ftpmasters have not yet actioned it, presumably because there are still reverse-dependencies in unstable. A rc bug is pre

why did hypercorn migrate to testing?

At the start of the month python-asynctest and hypercorn were removed from testing due to a rc bug in python-asynctest and the fact that hypercorn build-depends on python3-asynctest (which is built from the python-asynctest source package). However hypercorn just migrated to testing again, despit

Bug#960193: ICU rebuilds

On 10/06/2020 19:03, Sebastian Ramacher wrote: > Hi Peter > > On 2020-06-10 18:28:24 +0100, Peter wrote: >> On 09/06/2020 21:19, Sebastian Ramacher wrote: >>> On 2020-06-09 19:56:00 +0200, László Böszörményi (GCS) wrote: >>>> Hi, >>>> >>

Bug#960193: ICU rebuilds

ulate >>> performous >>> qtbase-opensource-src >>> qtlocation-opensource-src >>> qtwebkit-opensource-src >>> webkit2gtk >>> zimwriterfs > Scheduled. > > Cheers Hi, Please could someone add qosmic to the binNMU list?   { https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962095 } Cheers, Peter

future of aufs in Debian.

The aufs package last saw a maintainer upload in September 2019 and was last-updated (by a NMU) in October 2019. It has had broken build-dependencies in testing for half a year now (since Linux 5.3.9-3 migrated to testing in November 2019). According to dak rm the aufs source-package has two r

Bug#959890: buster-pu: package confget/2.2.0-4+deb10u1

s the changelog entry, just in case: confget (2.2.0-4+deb10u1) buster; urgency=medium * Fix the Python module's handling of values containing "=": - add the test-ini-eq patch to add a test for such values - add the python-value-eq patch to fix the problem - Closes: #959887

Bug#958988: key packages script does not take account of virtual packages.

package: qa.debian.org user: qa.debian@packages.debian.org usertags: udd x-debbugs-cc: debian-release@lists.debian.org The debian rust team makes heavy use of virtual packages to reduce the number of real packages in the archive (and in some cases the number of trips through new) while reta

rust-grep testing migration.

Hi Rust-grep is currently blocked from testing migration because of an autopkgtest failure on arm64, it appears that the test failed due to a version mismatch issue. The test was run over three weeks ago and the offending version is no longer in testing. I tried hitting the "retry" button a f

testing migration of gtk-d and tilix binnmus

While investigating self-contained buildability issues in testing I noticed that the gtk-d and tilix binnmus were not migrating to testing. I'm not an expert on reading britney output but I think they may be being blocked by dependencies on each other and britney needs a hint to try them toget

state of the rust ecosystem (and particularly rust-cbindgen) in Debian (was: Requesting backport of cbindgen > 0.10.0 to buster)

(note: these are my observations as a maintainer of a derivative) The rust ecosystem in Debian recently had (and I expect still has) trouble to properly migrate to testing Indeed there are still issues, most notablly IMO that firefox-esr's build-dependencies have been unsatisfiable in testing

re: git-buildpackage to be autoremoved due to python2 transition

Relevant packages and bugs: 943107 git-buildpackage: Python2 removal in sid/bullseye This bug is not marked as rc. Nevertheless I believe that this bug report is in-fact a false positive. From what I can tell git-buildpackage, even in buster, does not (build-)depend on python 2 or any python

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

There's another kind of issue Yeah, sadly the transition tracker only looks at unstable, so packages that are fixed in unstable but haven't migrated to testing for some reason won't show up. ; here is an example : - sagemath builds only for Python 3.7, so some of this subpackages don't load un

Bug#942106: looking at the remaining "bad" packages in the "add python 3.8" transition

I just took a look at the "add python3.8 transition tracker", and split the remaining "bad" packages into categories. Key package, rc bug with patch. * gpgme1.0 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944774 Not key package, but not marked for autoremoval from testing * macs version i

Re: Bug#948722: qemu-block-extra, (build-)dependencies unsatisfiable on mipsel.

On 14/01/2020 10:24, Michael Tokarev wrote: Control: severity -1 normal Control: tag -1 + moreinfo 12.01.2020 18:37, peter green wrote: Package: qemu-block-extra Version: 1:4.2-1 Severity: serious The binary packages built from the ceph source package were recently removed from mipsel

Re: possible bug in auto-removals.

On 16/12/2019 21:02, Paul Gevers wrote: Hi Peter, On 16-12-2019 01:21, peter green wrote: I have been observing a number of python cruft packages that are still in testing recently, and I noticed that there seems to be an issue with an auto-removal. cruft has never been supposed to be in

possible bug in auto-removals.

I have been observing a number of python cruft packages that are still in testing recently, and I noticed that there seems to be an issue with an auto-removal. My understanding is that auto-removals is supposed to keep track of reverse dependencies and initially delay auto-removal, then later,

astroid2 removal from testing (after removal from unstable)

astroid2 was removed from unstable a couple of weeks ago. However it is still in testing, britney claims. trying: -astroid2 skipped: -astroid2 (424, 28, 295) got: 32+0: a-1:a-0:a-0:a-0:i-28:m-2:m-0:p-0:s-1 * mips64el: python-guiqwt, python3-guiqwt However neither of those packages s

Haskell binnmus is there a problem?

Recently I noticed that haskell binnmus no longer seemed to be happening. For example mediawiki2latex has no been BD-Uninstallable since it was uploaded 24 days ago and https://buildd.debian.org/status/architecture.php?a=arm64&suite=sid doesn't show any haskell binnmus currently being built (th

Bug#928381: unblock: stunnel4/3:5.54~b3-1

On Fri, May 31, 2019 at 11:14:15AM +0300, Peter Pentchev wrote: > On Thu, May 30, 2019 at 09:00:18PM +0200, Paul Gevers wrote: > > Hi Peter, > > > > On 30-05-2019 11:24, Peter Pentchev wrote: > > > Just for my information, is there a chance that this upgrade could be

Bug#928381: unblock: stunnel4/3:5.54~b3-1

On Thu, May 30, 2019 at 09:00:18PM +0200, Paul Gevers wrote: > Hi Peter, > > On 30-05-2019 11:24, Peter Pentchev wrote: > > Just for my information, is there a chance that this upgrade could be > > allowed later on during the buster lifecycle as a stable update? > > If

Bug#928381: unblock: stunnel4/3:5.54~b3-1

On Thu, May 30, 2019 at 11:08:02AM +0200, Paul Gevers wrote: > tags 928381 wontfix > thanks > > Hi Peter, > > On Fri, 3 May 2019 13:48:43 +0300 Peter Pentchev wrote: > > I am aware that new upstream versions are not usually allowed in during > > a release freeze

Re: self-contained buildability check on buster.

On 23/05/19 20:13, Peter Michael Green wrote: I just wrote a quick python script ( http://incoming.debian.org/debian-buildd/pool/main/a/acorn/acorn_5.5.3+ds3-3.dsc ) Correction, the url is https://github.com/plugwash/checkscb/blob/master/checkscb.py

self-contained buildability check on buster.

I just wrote a quick python script ( http://incoming.debian.org/debian-buildd/pool/main/a/acorn/acorn_5.5.3+ds3-3.dsc ) to do a "self-contained buildability" check for buster. That is check that for all binaries in buster the corresponding sourcepackage/architecture combination passes dose-buil

  1   2   3   4   5   >