+1 maintenance status − June 4-5
Hello everyone, I was on +1 maintenance shift this Thursday and Friday. This was my first time doing this, so a part of my shift was spent reading documentation, and getting familiar with the tools and processes. Many thanks to seb128 for mentoring me through it. Following is a summary of what I did in terms of actual +1 maintenance: * metis/i386: submitted a MR to add a force-badtest hint ( https://code.launchpad.net/~osomon/britney/hints-ubuntu-i386-badtests/+merge/385113 ) * fonts-dejavu: the transitional packages were removed, but a number of rdepends still listed them, so I went through all of them and filed bugs and submitted patches where relevant: * enigma-data: attached patch to https://bugs.debian.org/921469 * 0ad: not needed * frogatto-data: already done in 1.3.1+dfsg-2, needs releasing * astromenace: filed https://bugs.debian.org/962195 and submitted https://salsa.debian.org/games-team/astromenace/-/merge_requests/1 * zatacka (https://bugs.debian.org/961863): submitted https://github.com/alexdantas/zatacka.debian/pull/3 * xmoto-data (https://bugs.debian.org/946057): already done in 0.6.0+repack-1, currently in unstable (and in groovy-proposed) * singularity: filed https://bugs.debian.org/962196 and attached patch * scilab-test: filed https://bugs.debian.org/962198 and submitted https://salsa.debian.org/science-team/scilab/-/merge_requests/4 * sarg: filed https://bugs.debian.org/962200 and submitted https://salsa.debian.org/debian/sarg/-/merge_requests/1 * plymouth-theme-hamara: not needed * natbraille: filed https://bugs.debian.org/962201 and submitted https://salsa.debian.org/a11y-team/natbraille/-/merge_requests/1 * miceamaze: not needed * manaplus-data: filed https://bugs.debian.org/962207 and attached patch * libgazebo-dev: already done in 11.0.0+dfsg1-3 * icewm: not needed * castle-game-engine-doc (https://bugs.debian.org/961602): submitted https://salsa.debian.org/pascal-team/castle-game-engine/-/merge_requests/1 * blobwars-data: filed https://bugs.debian.org/962210 and attached patch * blobandconquer-data: filed https://bugs.debian.org/962211 and attached patch * mythtv*: filed https://launchpad.net/bugs/1882108 and submitted https://github.com/MythTV/packaging/pull/78 * wmforkplop (https://bugs.debian.org/861191): already done in 0.9.3-2.2 (uploaded to DELAYED/7 on 1st June) * fontforge FTBFS on s390x (preventing libreoffice from building there): https://bugs.debian.org/961841, identified and tested upstream commit that fixes the build ( https://github.com/fontforge/fontforge/commit/fde85b13382595cb3ab889e38570b4944edad808), and later realized that that commit has already been cherry-picked in salsa ( https://salsa.debian.org/fonts-team/fontforge/-/commit/ad2b5f648241de5920a6f7f738dea091290a0af0), it is now pending a release * r-cran-gwidgetstcltk test failures (blocking xorg-server): filed https://bugs.debian.org/962280 and submitted https://salsa.debian.org/r-pkg-team/r-cran-gwidgetstcltk/-/merge_requests/1 * glade/i386 test failures (badpkg) blocking gdk-pixbuf 2.40.0+dfsg-5: ran the tests locally and they passed, so I asked seb128 to re-trigger, and it succeeded Have a good week-end, Olivier -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance June 2nd-5th
On Fri, Jun 05, 2020 at 09:09:49PM +0200, Christian Ehrhardt wrote:
> On Fri, Jun 5, 2020 at 8:29 PM Bryce Harrington <
> bryce.harring...@canonical.com> wrote:
>
> > On Fri, Jun 05, 2020 at 08:11:40AM +0200, Christian Ehrhardt wrote:
> > > php-horde
> > >
> > > Next was a look at php-horde-* which is not only split into many packages
> > > but also has plenty of autopkgtests due to that.
> > > 10/10 tests that I checked were blocked at the same issue: "E: Package
> > > 'php-horde-test' has no installation candidate"
> > > If there is another issue, then I need this to resolve to be able to see
> > it
> > > :-)
> > >
> > > It turned out to be rather easy: php-horde-test isn't in groovy-release -
> > > not even an older version.
> > > Due to that the tests fail to find anything.
> > >
> > > 104 source packages and counting :-). The reason for all that was that
> > the
> > > status was a mixed feeling before [6] and removed from focal.
> > > It was removed from Debian as well [7] and the current flurry of
> > > builds&tests is caused by re-uploads to bring it back.
> > > Some bits are still hanging in Debian's new queue like the core
> > "php-horde
> > > 5.2.21+debian1-1" itself.
> > >
> > > We should give it a chance now, but if it looks as bad with proper test
> > > triggers it likely should be removed until this has resolved to a proper
> > > state in Debian (gladly the package was adopted, so this will become
> > better
> > > over time).
> > >
> > > For now we can't go on, this will need to wait until php-horde passes the
> > > new queue and is in groovy-proposed.
> > > Then we want to run something like the following to properly restart the
> > > tests.
> > >
> > > $ wget
> > >
> > https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
> > > $ for p in $(grep -Hrn '>php-horde-.* (- to php-horde-/php-horde-/' | sed -e
> > > 's/<\/a>.*//' ); do retry-autopkgtest-regressions --series groovy
> > --blocks
> > > "${p}"; done | sed -e
> > >
> > 's/$/&trigger=php-horde-test%2F2.6.3%2Bdebian0-5&trigger=php-horde%2F5.2.21%2Bdebian1-1/'
> > >
> > > ---
> > >
> > > php-horde
> > >
> > > Still waiting in Debian new queue, due to that still nothing to do.
> >
> > php-horde was dropped in focal, and should be for groovy as well, and
> > blacklisted:
> >
> > https://bugs.launchpad.net/ubuntu/+source/php-horde/+bug/1880776
> >
> > php-horde-* wraps a vast number of other system packages, so whenever
> > there are any changes in plumbing, invariably some chunk of php-horde
> > ends up broken. We don't see a high enough usage of php-horde to
> > warrant the effort maintaining it has been taking.
> >
>
>
> Hi Bryce,
> thanks for the background.
> I remember and even read the old removal bug when looking at the case this
> week.
> I thought we could give it a chance if it is better now, but I'm fine to
> remove it if that is still the right thing to do.
> So you are saying we should re-remove and more actively block further
> syncing then?
> I can do so next week, just please confirm to me that this is the path to
> go on this.
Yes, that's what I recommend - re-remove it and actively block it from
being sync'd back in.
It's been a frequent visitor to update-excuses, and given that it's not
widely used, it's consuming engineering attention that'd be better
focused on more pressing matters.
Bryce
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance June 2nd-5th
On Fri, Jun 5, 2020 at 8:29 PM Bryce Harrington <
bryce.harring...@canonical.com> wrote:
> On Fri, Jun 05, 2020 at 08:11:40AM +0200, Christian Ehrhardt wrote:
> > php-horde
> >
> > Next was a look at php-horde-* which is not only split into many packages
> > but also has plenty of autopkgtests due to that.
> > 10/10 tests that I checked were blocked at the same issue: "E: Package
> > 'php-horde-test' has no installation candidate"
> > If there is another issue, then I need this to resolve to be able to see
> it
> > :-)
> >
> > It turned out to be rather easy: php-horde-test isn't in groovy-release -
> > not even an older version.
> > Due to that the tests fail to find anything.
> >
> > 104 source packages and counting :-). The reason for all that was that
> the
> > status was a mixed feeling before [6] and removed from focal.
> > It was removed from Debian as well [7] and the current flurry of
> > builds&tests is caused by re-uploads to bring it back.
> > Some bits are still hanging in Debian's new queue like the core
> "php-horde
> > 5.2.21+debian1-1" itself.
> >
> > We should give it a chance now, but if it looks as bad with proper test
> > triggers it likely should be removed until this has resolved to a proper
> > state in Debian (gladly the package was adopted, so this will become
> better
> > over time).
> >
> > For now we can't go on, this will need to wait until php-horde passes the
> > new queue and is in groovy-proposed.
> > Then we want to run something like the following to properly restart the
> > tests.
> >
> > $ wget
> >
> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
> > $ for p in $(grep -Hrn '>php-horde-.* (- to php-horde-/php-horde-/' | sed -e
> > 's/<\/a>.*//' ); do retry-autopkgtest-regressions --series groovy
> --blocks
> > "${p}"; done | sed -e
> >
> 's/$/&trigger=php-horde-test%2F2.6.3%2Bdebian0-5&trigger=php-horde%2F5.2.21%2Bdebian1-1/'
> >
> > ---
> >
> > php-horde
> >
> > Still waiting in Debian new queue, due to that still nothing to do.
>
> php-horde was dropped in focal, and should be for groovy as well, and
> blacklisted:
>
> https://bugs.launchpad.net/ubuntu/+source/php-horde/+bug/1880776
>
> php-horde-* wraps a vast number of other system packages, so whenever
> there are any changes in plumbing, invariably some chunk of php-horde
> ends up broken. We don't see a high enough usage of php-horde to
> warrant the effort maintaining it has been taking.
>
Hi Bryce,
thanks for the background.
I remember and even read the old removal bug when looking at the case this
week.
I thought we could give it a chance if it is better now, but I'm fine to
remove it if that is still the right thing to do.
So you are saying we should re-remove and more actively block further
syncing then?
I can do so next week, just please confirm to me that this is the path to
go on this.
> Bryce
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: +1 maintenance June 2nd-5th
On Fri, Jun 05, 2020 at 08:11:40AM +0200, Christian Ehrhardt wrote:
> php-horde
>
> Next was a look at php-horde-* which is not only split into many packages
> but also has plenty of autopkgtests due to that.
> 10/10 tests that I checked were blocked at the same issue: "E: Package
> 'php-horde-test' has no installation candidate"
> If there is another issue, then I need this to resolve to be able to see it
> :-)
>
> It turned out to be rather easy: php-horde-test isn't in groovy-release -
> not even an older version.
> Due to that the tests fail to find anything.
>
> 104 source packages and counting :-). The reason for all that was that the
> status was a mixed feeling before [6] and removed from focal.
> It was removed from Debian as well [7] and the current flurry of
> builds&tests is caused by re-uploads to bring it back.
> Some bits are still hanging in Debian's new queue like the core "php-horde
> 5.2.21+debian1-1" itself.
>
> We should give it a chance now, but if it looks as bad with proper test
> triggers it likely should be removed until this has resolved to a proper
> state in Debian (gladly the package was adopted, so this will become better
> over time).
>
> For now we can't go on, this will need to wait until php-horde passes the
> new queue and is in groovy-proposed.
> Then we want to run something like the following to properly restart the
> tests.
>
> $ wget
> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
> $ for p in $(grep -Hrn '>php-horde-.* (- to php-horde-/php-horde-/' | sed -e
> 's/<\/a>.*//' ); do retry-autopkgtest-regressions --series groovy --blocks
> "${p}"; done | sed -e
> 's/$/&trigger=php-horde-test%2F2.6.3%2Bdebian0-5&trigger=php-horde%2F5.2.21%2Bdebian1-1/'
>
> ---
>
> php-horde
>
> Still waiting in Debian new queue, due to that still nothing to do.
php-horde was dropped in focal, and should be for groovy as well, and
blacklisted:
https://bugs.launchpad.net/ubuntu/+source/php-horde/+bug/1880776
php-horde-* wraps a vast number of other system packages, so whenever
there are any changes in plumbing, invariably some chunk of php-horde
ends up broken. We don't see a high enough usage of php-horde to
warrant the effort maintaining it has been taking.
Bryce
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
