On Fri, May 31, 2024 at 12:35 PM Benjamin Drung wrote:
> rust-axum-core
> ==
>
> update_excuse claims that rust-axum-core has no binaries on any arch,
> but https://launchpad.net/ubuntu/+source/rust-axum-core/0.3.4-1 shows
> that librust-axum-core-dev was build on all archs. I asked
On Wed, May 29, 2024 at 07:04:11PM +, Graham Inggs wrote:
> I was on +1 maintenance from 2024-05-23 until 2024-25-29. Below are
> the things I worked on.
>
>
> The autopkgtest queues were completely empty following the Mardid
> sprint. I noticed the update_excuses report [1] still showed
On Tuesday, February 27 2024, Colin Watson wrote:
> On Fri, Jan 26, 2024 at 06:31:39PM -0500, Sergio Durigan Junior wrote:
>> * celery
>> - Spent a long time investigating the Python 3.12 segfault that
>> happens when running dh_auto_test. I was able to obtain a usable
>> stacktrace.
On Fri, Jan 26, 2024 at 06:31:39PM -0500, Sergio Durigan Junior wrote:
> * celery
> - Spent a long time investigating the Python 3.12 segfault that
> happens when running dh_auto_test. I was able to obtain a usable
> stacktrace.
> - I'll file an upstream bug.
I don't know if you ever
Heya Benjamin,
Just wanted to followup in sharing the spreadsheet as it is so far.
Thanks again for all the suggestions!
https://docs.google.com/spreadsheets/d/1wLOIM-mkN02O-n84YXAOMC6MjEetCyID5JMonEAZSIU
Definitely let me know if you stumble across other useful things, or
even just have
On 07.02.24 09:17, Utkarsh Gupta wrote:
On Wed, Feb 7, 2024 at 6:17 AM Pushkar Kulkarni
wrote:
=== freedombox/bootstrapform ===
The freedombox package depends on bootstrapform. Autopkgtests of the
former fail because the latter imports distutils. I did a Debian MR
[15] to replace
Hi,
On Wed, Feb 7, 2024 at 10:42 AM Andreas Hasenack wrote:
>
> Hi,
>
> On Tue, Feb 6, 2024 at 9:47 PM Pushkar Kulkarni
> wrote:
> >
> > === freedombox/bootstrapform ===
> > The freedombox package depends on bootstrapform. Autopkgtests of the
> > former fail because the latter imports
Hi Pushkar,
On Wed, Feb 7, 2024 at 6:17 AM Pushkar Kulkarni
wrote:
> I was on my first +1 maintenance shift last week. I began the week
> with some reading of +1 report of the past shifts, to get a basic idea
> of what to do and how to do it.
Nice, thanks for your good work and excellent
Hi,
On Tue, Feb 6, 2024 at 9:47 PM Pushkar Kulkarni
wrote:
>
> === freedombox/bootstrapform ===
> The freedombox package depends on bootstrapform. Autopkgtests of the
> former fail because the latter imports distutils. I did a Debian MR
> [15] to replace distutils.StrictVersion with
Hi Sergio,
On Fri, Jan 26, 2024 at 06:31:39PM -0500, Sergio Durigan Junior wrote:
> * r-bioc-savr
> - There's an RM bug against the package on Debian. I didn't touch the
> FTBFS.
However, Debian package removal requests take an indeterminate amount of
time to be acted on by the ftp team,
Hi Bryce,
On Fri, 2023-12-15 at 15:54 -0800, Bryce Harrington wrote:
> Heya Benjamin,
>
> Quick question for you. I'm collecting a list of tools people are
> finding useful or interesting for doing +1 maintenance. Can you mention
> any such scripts you used on your rotation this week? I'm in
Heya Benjamin,
Quick question for you. I'm collecting a list of tools people are
finding useful or interesting for doing +1 maintenance. Can you mention
any such scripts you used on your rotation this week? I'm in particular
looking for weird/random/unusual stuff, personal or one-off codes,
I was on +1 maintenance this week and worked on the following:
- stdgpu: requested to move libthrust-dev to the universe to resolve
dependency-wait. Package migrated. LP: 2037908
- atop: investigated the autopkgtest failure on armhf. The root cause
was the atopacctd service not starting in the
On Friday, September 01 2023, Benjamin Drung wrote:
> * **gsl**: Retried failing ruby-gsl/2.1.0.3+dfsg1-5build2 on ppc64el.
> It is still failing and needs to be investigated.
I did a little investigative work and found that the problem can be
workarounded by compiling with -O2 instead of -O3.
On Mon, Aug 21, 2023 at 02:28:50PM -0700, Bryce Harrington wrote:
> > The armhf lxd containers do not have hard partitioning of memory
> > allocations, so *generally* tests on armhf will have more memory available
> > than on other architectures. But that memory is also shared across tests,
> >
On Mon, Aug 21, 2023 at 09:47:18AM -0700, Steve Langasek wrote:
> On Mon, Aug 21, 2023 at 10:16:31AM +0800, Shengjing Zhu wrote:
> > + golang-github-protonmail-go-crypto
> > The error message says "out of memory". I can reproduce this on a VM with
> > 500M memory.
> > It's because the
On Mon, Aug 21, 2023 at 10:16:31AM +0800, Shengjing Zhu wrote:
> + golang-github-protonmail-go-crypto
> The error message says "out of memory". I can reproduce this on a VM with
> 500M memory.
> It's because the testdata in TestSymmetricDecryptionArgon2 uses a large
> memory exponent
On Fri, Jul 28, 2023 at 05:43:36PM +0100, Robie Basak wrote:
> # rust-block-padding
> I didn't really make sense of this. How is a build of
> rust-block-buffer-0.9 resulting in a binary
> librust-block-buffer-0.9+block-padding-dev that has a versioned binary
> dependency on
On Fri, Jun 30, 2023 at 03:18:04PM -0400, Nick Rosbrook wrote:
> # lua-resty-core (LP 2025072) [needs AA]
> This package is uninstallable due to a dependency on
> libnginx-mod-http-lua, which is not in the Ubuntu archive due to an
> intentional removal (LP: #1986853).
> lua-resty-core has no
On Fri, Jun 09, 2023 at 06:20:55PM +0100, Danilo Egea Gondolfo wrote:
> I had a shorter week with some Netplan distractions but here we go:
>
> 1. delve
>
> FTBFS due to the installed bpftool not matching the running kernel version.
> I tried to workaround this by calling bpftool directly from
>
On Sat, Jun 03, 2023 at 10:43:41PM +0800, Shengjing Zhu wrote:
> 3. librnd + camv-rnd + pcb-rnd
> camv-rnd and pcb-rnd are in dep-wait status, it needs librnd > 4.
> It's a small library transition. So I just ask @ginggs to kick off the
> transition.
> Also ask for revoking the
On Fri, May 26, 2023 at 09:40:02AM -0700, Simon Chopin wrote:
> See https://bugs.launchpad.net/ubuntu/+source/rust-gio/+bug/2020880
> See https://bugs.launchpad.net/ubuntu/+source/rust-graphene-sys/+bug/2020902
Thanks for tagging these update-excuse!
--
Steve Langasek Give me
On Fri, May 19, 2023 at 05:53:54PM +0200, Benjamin Drung wrote:
> * Follow-up on Lukas Märdian +1 shift: matplotlib 3.6.3-1 was not
> synced. My sync was rejected: "same version already has published
> binaries in the destination archive". I did a fake sync by uploading
> 3.6.3-1fakesync1
> Overall, it seems that you looked at a large number of packages in
> -proposed, but that for most of them you stopped at analysis (which is
> useful) without preparing and submitting fixes for the issues identified.
> In the future, please focus more on the latter, as that's what's actually
>
Congratulations on your first +1 maintenance rotation!
On Mon, Apr 10, 2023 at 12:45:49AM -0600, Zixing Liu wrote:
> rust-criterion (0.3.6-3 to 0.4.0-2)
> Due to the `rustc` version discrepancy between Ubuntu and Debian,
> `rust-criterion` failed to compile in Ubuntu.
> I have backported an
On Thu, Apr 06, 2023 at 05:59:46PM -0300, Lucas Kanashiro wrote:
> This week is shorter than usual because of the holiday tomorrow, so I am
> sending my report today:
> ruby-mocha
> ==
>
> It is blocked by ruby-bourne for more than 3 months. ruby-bourne does not
> support ruby 3.1 and it
On Mon, Feb 20, 2023, Steve Langasek wrote:
> On Mon, Feb 20, 2023 at 03:51:50PM +0100, Adrien Nader wrote:
> > Due to the size of the queues, I decided to start with the oldest
> > issues.
>
> Out of interest, how did you identify these "oldest issues"? I happened to
> spend some time on
On Mon, Feb 20, 2023 at 03:51:50PM +0100, Adrien Nader wrote:
> Due to the size of the queues, I decided to start with the oldest
> issues.
Out of interest, how did you identify these "oldest issues"? I happened to
spend some time on proposed-migration on Thursday, and all of the packages I
On Thursday, February 16 2023, I wrote:
> On Monday, February 13 2023, Steve Langasek wrote:
>
>> On Fri, Feb 10, 2023 at 01:58:56PM -0500, Sergio Durigan Junior wrote:
>>> * gatb-core
>>> - Debian dropped s390x from the list of supported architectures.
>>> - Pinged ubuntu-archive and asked
On Thu, Feb 16, 2023 at 02:35:51PM -0500, Sergio Durigan Junior wrote:
> >> * bcbio & mosdepth & nim-{unicodeplus,regex}
> >> - In -proposed for 95 days.
> >> - bcbio is FTBFSing because it B-D on mosdepth.
> >> - mosdepth is FTBFSing because it B-D on nim-regex.
> >> - nim-regex and its
On Monday, February 13 2023, Steve Langasek wrote:
> On Fri, Feb 10, 2023 at 01:58:56PM -0500, Sergio Durigan Junior wrote:
>> * gatb-core
>> - Debian dropped s390x from the list of supported architectures.
>> - Pinged ubuntu-archive and asked them to reflect this decision so
>> that
On Fri, Feb 10, 2023 at 01:58:56PM -0500, Sergio Durigan Junior wrote:
> * gatb-core
> - Debian dropped s390x from the list of supported architectures.
> - Pinged ubuntu-archive and asked them to reflect this decision so
> that britney lets the package migrate.
Missed in backlog while I
Hi Nick,
On Mon, Feb 13, 2023 at 4:18 AM Nick Rosbrook
wrote:
> ### openlibm FTBFS on armhf
>
> LP: #2006501
>
> Debian already has a fix committed, but has not released for a few
> months now. I verified the fix works for us, and proposed uploading
> the fix with a `maysync` version to allow
On Mon, Dec 05, 2022 at 05:06:30PM -0800, Steve Langasek wrote:
> > However, sometimes you might find --apt-pocket=proposed=... *not* used,
> > even when triggers appear to exist. I didn't get to the bottom of this.
> > Maybe it's something to do with magic fallback behaviour I've heard
> >
On Mon, Dec 05, 2022 at 05:06:30PM -0800, Steve Langasek wrote:
> Second, even though the above should already pick up more packages from
> -proposed that we need, I've also added --all-proposed, saying to grab all
> packages from -proposed. Two reasons for this:
FYI, although this is correct in
Sorry to hear that you had a frustrating time with +1 maintenance last week.
Large transitions can definitely be frustrating because many times, it's so
unclear how to make progress on them.
Some notes:
- The request.cgi API endpoint does deduplication of test requests on the
backend. So
Hi Seb,
On Mon, Dec 05, 2022 at 09:01:32PM +0100, Sebastien Bacher wrote:
> Hey Robie, your email was interesting to read, I've one question bellow
>
> Le 05/12/2022 à 18:04, Robie Basak a écrit :
> > I thought I recalled a
> >colleague mentioning something about this in ubuntu-helpers
>
>
Hey Robie, your email was interesting to read, I've one question bellow
Le 05/12/2022 à 18:04, Robie Basak a écrit :
I thought I recalled a
colleague mentioning something about this in ubuntu-helpers
Could you share a reference to ubuntu-helpers? I don't know about that
project and neither
Hi,
Em sex., 21 de out. de 2022 19:47, Sergio Durigan Junior <
sergio.duri...@canonical.com> escreveu:
> * golang-github-containerd-stargz-snapshotter
> - FTBFSing on Ubuntu, but not on Debian, which is strange.
> - I've started investigating it but couldn't progress much further
>
On Friday, October 21 2022, Steve Langasek wrote:
> Hi Sergio,
Hello,
> On Fri, Oct 21, 2022 at 06:47:09PM -0400, Sergio Durigan Junior wrote:
>> * cryfs
>> - FTBFS on ppc64el due to RLIMIT_MEMLOCK being too low.
>> - After spending some time playing with setrlimit et al, it's clear to
>>
Hi Sergio,
On Fri, Oct 21, 2022 at 06:47:09PM -0400, Sergio Durigan Junior wrote:
> * cryfs
> - FTBFS on ppc64el due to RLIMIT_MEMLOCK being too low.
> - After spending some time playing with setrlimit et al, it's clear to
> me that the problem cannot be easily fixed in the source code.
Hi Bryce,
On Wed, Oct 05, 2022 at 06:37:06PM -0700, Bryce Harrington wrote:
> ### scikit-learn ###
> This package hits a 'bus error' on armhf. This issue seems not to have
> a bug report in Debian, however bus errors are mentioned on both Deb:
> #1008369 and #1003165. Both bugs have extensive
On Fri, Sep 30, 2022 at 12:17:34PM +0200, Heinrich Schuchardt wrote:
> *vectorscan*
>
> vectorscan does not build on amd64
> This seems to be due to warnings for the implementation of vectors in
> libboost.
> We have not updated libboost since 2 years. We should have a look at it
> after the
On Sun, Sep 18, 2022 at 08:51:51AM -0700, eeickme...@ubuntu.com wrote:
> On Fri, 2022-09-16 at 18:12 -0600, Dan Bungert wrote:
> > # qtav / matrix-mirage (LP: #1989613) #
> > "QtAV is no longer maintained" per
> > https://github.com/wang-bin/QtAV/blob/master/.github/ISSUE_TEMPLATE#L19
>
On Fri, 2022-09-16 at 18:12 -0600, Dan Bungert wrote:
> # qtav / matrix-mirage (LP: #1989613) #
>
> "QtAV is no longer maintained" per
> https://github.com/wang-bin/QtAV/blob/master/.github/ISSUE_TEMPLATE#L19
>
> It does have a reverse dependency from matrix-mirage, which itself
>
Hey,
On Mon, Sep 12, 2022 at 8:20 PM Lucas Kanashiro
wrote:
> # rails
>
> It is stuck in -proposed because the new version contains a fix for
> CVE-2022-32224 which introduced a behavior change in the way
> hashes are serialized. I filed LP: #1988782 and tagged it as
> update-excuse. Utkarsh as
On Fri, Aug 19, 2022 at 07:30:47PM +0200, Olivier Gayot wrote:
> opencolorio:
> ---
> The package had also been updated recently with a new upstream version ahead
> of Debian. Unfortunately, the SONAME was bumped but the binary library
> package was not renamed.
> To fix it, I decided to
On Tue, Aug 16, 2022 at 7:13 PM Steve Langasek
wrote:
>
> On Tue, Aug 16, 2022 at 11:29:34AM -0400, Nick Rosbrook wrote:
>
> > ## libxsmm FTBFS (https://pad.lv/1984111)
>
> > This FTBFS with an undefined reference to pthread_yield. Upstream
> > already has fixes for this, so I cherry-picked
On Tue, Aug 16, 2022 at 11:29:34AM -0400, Nick Rosbrook wrote:
> ## libxsmm FTBFS (https://pad.lv/1984111)
> This FTBFS with an undefined reference to pthread_yield. Upstream
> already has fixes for this, so I cherry-picked those.
> I am still looking for a sponsor for this patch.
Thanks,
On Wed, Aug 03, 2022 at 09:21:04PM -0400, Sergio Durigan Junior wrote:
>
> On Friday, July 22 2022, Steve Langasek wrote:
>
> > Hi Sergio,
>
> Hello,
>
> Sorry for the delay. I was travelling and then on medical leave.
>
> > I notice in this report that most of the items you worked on
On Friday, July 22 2022, Steve Langasek wrote:
> Hi Sergio,
Hello,
Sorry for the delay. I was travelling and then on medical leave.
> I notice in this report that most of the items you worked on requiring
> source changes have Debian bugs or MPs as references, but there is no
> mention of
On Mon, 1 Aug 2022 at 11:51, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
>
>
> On Mon, 1 Aug 2022 at 11:06, Steve Langasek
> wrote:
>
>> On Sun, Jul 31, 2022 at 05:48:25PM -0400, Jeremy Bicha wrote:
>> > On Sun, Jul 31, 2022 at 4:02 PM Steve Langasek
>> > wrote:
>> > > On Fri,
On Mon, 1 Aug 2022 at 11:06, Steve Langasek
wrote:
> On Sun, Jul 31, 2022 at 05:48:25PM -0400, Jeremy Bicha wrote:
> > On Sun, Jul 31, 2022 at 4:02 PM Steve Langasek
> > wrote:
> > > On Fri, Jul 29, 2022 at 03:36:32PM +1200, Michael Hudson-Doyle wrote:
> > > > There is some stuff on NBS due to
On Sun, Jul 31, 2022 at 7:06 PM Steve Langasek
wrote:
> It is my understanding that ldc is not broken but that gir-to-d is not
> compatible with the current version. There are 6 source packages in the
> archive that have successfully rebuilt against the new version of
> libphobos2-ldc-shared,
On Sun, Jul 31, 2022 at 05:48:25PM -0400, Jeremy Bicha wrote:
> On Sun, Jul 31, 2022 at 4:02 PM Steve Langasek
> wrote:
> > On Fri, Jul 29, 2022 at 03:36:32PM +1200, Michael Hudson-Doyle wrote:
> > > There is some stuff on NBS due to a ldc transition: r-to-d,
> > > appstream-generator, tilix,
On Sun, Jul 31, 2022 at 4:02 PM Steve Langasek
wrote:
> On Fri, Jul 29, 2022 at 03:36:32PM +1200, Michael Hudson-Doyle wrote:
> > There is some stuff on NBS due to a ldc transition: r-to-d,
> > appstream-generator, tilix, etc. AFAICT all of these packages have been
> > removed from Debian testing
On Tue, Jul 26, 2022 at 07:02:02PM -0600, Dan Bungert wrote:
> # unpaper (LP: #1982594) #
> A newer version of unpaper is in the deferred queue currently and does build
> for Kinetic and Sid. I suggest we sync that, when available.
Will be synced automatically since the package in
Hi Michael,
On Fri, Jul 29, 2022 at 03:36:32PM +1200, Michael Hudson-Doyle wrote:
> autofdo (last package depending on libgoogle-glog0v5) ftbfs, probably
> because our llvm is too new. Upstream /may/ have this fixed in git,
> unfortunately in an omnibus commit with the message "Update to the
On 29/07/2022 05:08, eeickme...@ubuntu.com wrote:
> Moreover, I cannot find any sign of the source code for 8.x, but
> they've somehow released some pre-alpha appimages (???!).
master branch on invent.kde.org is 8.0.0 development
https://www.digikam.org/download/git/
The project version in the
Hi Michael!
On Fri, 2022-07-29 at 15:36 +1200, Michael Hudson-Doyle wrote:
> Thanks to sickness and leave and other interruptions I didn't get a
> whole lot done in my shift, and I didn't do a very good job of
> recording the things I did do I'm afraid.
My condolances, I hope you feel better
Hi Sergio,
I notice in this report that most of the items you worked on requiring
source changes have Debian bugs or MPs as references, but there is no
mention of what is done to get them resolved in Ubuntu. We want to push
fixes upstream to Debian and minimize unnecessary delta, but the purpose
Hi,
On 18/07/2022 12:02, Nick Rosbrook wrote:
### ruby-certificate-authority FTBFS (https://pad.lv/1981458)
There was a print format change for the x509 v3 authority key
identifer field in openssl 3.0, and this test suite appears to depend
on that format. Changing the expected test string to
On Wed, Jul 13, 2022 at 05:05:15PM -0400, Sergio Durigan Junior wrote:
> I've been on +1 maintenance shift from Monday to Wednesday. I'm also
> working on my DebConf presentation & debuginfod in parallel.
>
> Retriggers that worked
> ==
>
> sqlite> SELECT DISTINCT
On Wednesday, July 13 2022, I wrote:
> * sbcl
> - As Athos mentioned
> (https://lists.ubuntu.com/archives/ubuntu-devel/2022-July/042200.html),
> we're starting to work on bootstrapping sbcl on ppc64el.
> - Unfortunately we've hit some bumps... The build is mysteriously
>
On Fri, Jul 01, 2022 at 05:39:38PM -0700, Brian Murray wrote:
> On Fri, Jul 01, 2022 at 03:25:39PM -0700, Bryce Harrington wrote:
> > As William Wilson and Graham Inggs mentioned, there seems to be a higher
> > than usual amount of FTBFS compared with autopkgtest failures. There
> > doesn't seem
On Fri, Jul 01, 2022 at 03:25:39PM -0700, Bryce Harrington wrote:
> As William Wilson and Graham Inggs mentioned, there seems to be a higher
> than usual amount of FTBFS compared with autopkgtest failures. There
> doesn't seem to be a common pattern going on, just a lot of package
> ecosystems in
On Fri, Jul 01, 2022 at 03:25:39PM -0700, Bryce Harrington wrote:
> As William Wilson and Graham Inggs mentioned, there seems to be a higher
> than usual amount of FTBFS compared with autopkgtest failures. There
> doesn't seem to be a common pattern going on, just a lot of package
> ecosystems in
On Fri, Jul 01, 2022 at 11:54:12AM -0700, Steve Langasek wrote:
> On Fri, Jul 01, 2022 at 01:40:53PM -0500, William Wilson wrote:
> > Steve,
>
> > Thank you for your work on this. I apologize for the lack of detail in my
> > earlier email. In order to get g-g-j-pgtype to build in my PPA with
> >
On Fri, Jul 01, 2022 at 01:40:53PM -0500, William Wilson wrote:
> Steve,
> Thank you for your work on this. I apologize for the lack of detail in my
> earlier email. In order to get g-g-j-pgtype to build in my PPA with
> g-g-j-pgx version 3.x, I had to change a line in d/control. I changed the
>
Steve,
Thank you for your work on this. I apologize for the lack of detail in my
earlier email. In order to get g-g-j-pgtype to build in my PPA with
g-g-j-pgx version 3.x, I had to change a line in d/control. I changed the
dependency "golang-github-jackc-pgx-v4-dev" to
On Fri, Jul 01, 2022 at 11:28:25AM -0700, Steve Langasek wrote:
> > So, I think the bootstrap solution might be:
> > 1. Verify that g-g-j-pgtype (1.10.0-3) actually does build
> > successfully against g-g-j-pgx-dev (3.6.2-2). (This is probably
> > best to verify in a PPA.) If so,
On Fri, Jul 01, 2022 at 10:08:26AM -0700, Bryce Harrington wrote:
> > Are there any methods for dealing with this type of circular dependency?
> > In Debian I can see they did a binary-only upload to fix this, but as
> > far as I know there is no such thing in Ubuntu.
> Right, that's not
Bryce,
Thanks for replying here and in IRC. it does appear g-g-j-pgtype does
successfully build with g-g-j-pgx 3.6.2-2. I'm about to EOW but will
contact an AA next week about the next steps.
Thanks again!
William
On Fri, Jul 1, 2022 at 12:08 PM Bryce Harrington <
On Fri, Jul 01, 2022 at 11:34:13AM -0500, William Wilson wrote:
> Greetings ubuntu-devel,
>
> This week I was on +1 maintenance and I noticed an odd circular dependency
> between two packages.
>
>- Package golang-github-jackc-pgtype is in NEW and is dependency wait on
>
Hi,
On Mon, Jun 13, 2022 at 7:29 AM Simon Chopin
wrote:
> ruby-gitlab-fog-azure-rm:
> The test suite fails due to Ruby 3.0 incompatibilities.
> I patched out the Proc.new.call invocations into explicit block.call ones,
> submitted both to upstream and Debian. The upstream MR has been merged
>
On Mon, May 30, 2022 at 09:38:33AM -0300, Lucas Kanashiro wrote:
> Hi,
>
> Last week was my +1 maintenance shift, this time I decided to try to unblock
> packages stuck in -proposed for too long (bottom of the excuses page). Below
> you can find a summary of what I did:
>
> # debos
>
> Revisit
And I forgot to mention:
astroquery
I added a patch to fix the permission denied on accessing files here :
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13638113/+listing-archive-extra
But then autopkgtest fails on armhf
Hi Robie
On Fri, 13 May 2022 at 23:04, Robie Basak wrote:
> octave is in dep-wait on riscv64 for libpetsc-real3.16-dev
> Produced by src:petsc which FTBFS on riscv64
> FTBFS is because of missing symbol SCOTCH_ParMETIS_V3_NodeND
> On amd64 this is shipped in libptscotchparmetisv3-7.0.1.so in
>
On Tue, Apr 05, 2022 at 11:36:20AM +0100, Robie Basak wrote:
> On Mon, Apr 04, 2022 at 10:35:36PM -0700, Steve Langasek wrote:
> > I unfortunately do not have a good place to publish it at the moment so that
> > it's more visible to developers. Suggestions welcome.
> On the server team, as an
On Mon, Apr 04, 2022 at 10:35:36PM -0700, Steve Langasek wrote:
> I unfortunately do not have a good place to publish it at the moment so that
> it's more visible to developers. Suggestions welcome.
On the server team, as an experiment we started a git repository to
share this kind of "I wrote a
Thanks for your work on +1 maintenance!
One bit I want to call attention to:
On Mon, Apr 04, 2022 at 10:17:44PM -0700, Bryce Harrington wrote:
> ## NBS ##
> I uploaded no-change rebuilds of the 11 NBS packages to a PPA; 4 of
> these build successfully, so I uploaded the no-change rebuilds to
On Fri, Feb 18, 2022 at 05:14:46PM +, Robie Basak wrote:
> I was on +1 maintenance this week.
>
> It's been a long time (years) since I last did this. I'm not sure I had
> a good feel for what would be useful to work on, so rather than spending
> time changing my mind constantly I just
On Mon, Feb 14, 2022 at 03:16:56PM +0100, Alexandre Ghiti wrote:
> Hi,
>
> I was on +1 maintenance last week and I focused on python3-defaults
> regressions:
>
> libapache2-mod-python
> ---
>
> This package must be adapted to support python 3.10, patches can be
>
Hiya,
On Mon, Jan 24, 2022 at 9:51 PM Utkarsh Gupta
wrote:
> ## node-pbkdf2 (LP: #191828)
>
> The tests have been failing on s390x because of it
> being big-endian but I've been in touch with people
> on the Debian side (we're all part of the JS team)
> and we're trying to fix this. The upstream
On Fri, Dec 17, 2021 at 12:18 PM Simon Chopin
wrote:
> I picked up a short +1 shift for the last two days of the week. I
> focused on -proposed migrations.
>
> # ruby-gnome
>
> Fix the autopkgtests for ruby-gnome, which were missing a dependency on
> ruby-webrick after the ruby 3.0 transition,
On Sat, Nov 20, 2021 at 05:59:49PM -0800, Steve Langasek wrote:
> segyio:
> Tries to use MINSIGSTKSZ as part of a constant expression, but in glibc 2.34
> this now expands to a call to sysconf(). Needs a bit more C++ surgery than
> I was prepared to do at the end of my shift. Filed LP: #1951658.
On Fri, Nov 12, 2021 at 05:03:10PM -0300, Lucas Kanashiro wrote:
Hi all,
This is the summary of my +1 maintenance shift:
# consul
The package in Debian is FTBFS [1], this was reported by me in Ubuntu as
well [2]. I added a commit to salsa backporting an upstream patch which
fixes the FTBFS,
On Mon, Oct 04, 2021 at 09:22:03AM +0200, Christian Ehrhardt wrote:
> On Sat, Oct 2, 2021 at 6:34 PM Steve Langasek
> wrote:
> > +1 Maintenance, Sep 27-Oct 1
> >
> ...
> > xrdp:
> > a warning about unknown archs has been promoted to an error, causing build
> > failures on ppc64el and s390x.
On Sat, Oct 2, 2021 at 6:34 PM Steve Langasek wrote:
>
> +1 Maintenance, Sep 27-Oct 1
>
...
>
> xrdp:
> a warning about unknown archs has been promoted to an error, causing build
> failures on ppc64el and s390x. Without further analysis for correctness,
> I've added ppc64el and s390x to the list
Christian Ehrhardt wrote on 01/10/2021:
# Help
Gladly this week Paride was so kind to help me and pick a few more +1 tasks.
That way some more than what I managed to resolve got done. I assume he will
reply to this thread with his own content he worked on this week.
Thanks @paride!
I
Hi Graham,
On Mon, Sep 27, 2021 at 6:14 PM Graham Inggs wrote:
> I think I can answer this now. Previously, python-meshio was writing
> and reading STL files in native byte order, so the STL test passed on
> big-endian systems. However, the data should have been in
> little-endian byte order
On Thu, 23 Sept 2021 at 17:41, Utkarsh Gupta
wrote:
> Whilst working through this, do you happen to know "what" exactly
> happened?
I think I can answer this now. Previously, python-meshio was writing
and reading STL files in native byte order, so the STL test passed on
big-endian systems.
On Thu, 23 Sept 2021 at 19:59, Bryce Harrington
wrote:
> Looking at the commit Graham points to at the upstream bug, there
> appears to be a change from using np.uint32() to .astype(" presumably issue is differences in platform datatype assumptions between
> these two routines?
In NumPy, the '<'
On Thu, Sep 23, 2021 at 09:10:31PM +0530, Utkarsh Gupta wrote:
> Hello,
>
> On Thu, Sep 23, 2021 at 7:57 PM Graham Inggs wrote:
> > python-meshio
> > =
> > python-meshio's autopkgtest on s390x has been failing since 4.3.11-1.
> > I found bryceh had looked at this previously in LP:
Hello,
On Thu, Sep 23, 2021 at 7:57 PM Graham Inggs wrote:
> python-meshio
> =
> python-meshio's autopkgtest on s390x has been failing since 4.3.11-1.
> I found bryceh had looked at this previously in LP: #1939057. I then
> found utkarsh2102 had reported an issue upstream, so I left
On 7/7/21 4:30 AM, Matthias Klose wrote:
On 7/6/21 5:07 PM, Heather Ellsworth wrote:
June 28 - July 2 (with 1.5 days afk to take care of a sick kiddo)
Last week I worked on a few packages:
* libpam-alreadyloggedin
Ubuntu pulls this package from sid and distributes it without modification.
On 7/6/21 5:07 PM, Heather Ellsworth wrote:
> June 28 - July 2 (with 1.5 days afk to take care of a sick kiddo)
>
> Last week I worked on a few packages:
>
> * libpam-alreadyloggedin
> Ubuntu pulls this package from sid and distributes it without modification.
> Debian sid ships gcc 10.2.1 and
On 7/5/21 8:15 AM, Chris MacNaughton wrote:
> Over Thursday and Friday (1 - 1 July). I worked on a few packages,
> starting with minor changes:
>
> - python-monasca-statsd: I updated the autopkgtest configuration with
> the actually python package name to enable minimal autopkgtests
> - manila: I
Hey there,
Le 21/06/2021 à 18:29, Brian Murray a écrit :
> I had also looked at tiff / pylibtiff and used import-bug-from-debian,
> from ubuntu-dev-tools, to create http://launchpad.net/bugs/1932588 which
> I tagged 'update-excuse'. However, looking at the proposed migration
> report I don't see
On Mon, Jun 21, 2021 at 10:57:57AM +1200, Robert Ancell wrote:
> The packages I managed to resolve issues for on the week 14-17th June:
>
> - xscreensaver - merged from Debian.
> - v4l-utils - had one test that had timed out, but worked once retried.
> - micropython - diagnosed the build failure,
1 - 100 of 139 matches
Mail list logo
