Hi,
according to
https://magenta.jak-linux.org/ubuntu-archive/distcheck/noble.armhf/global-ben.rebuild-for.txt
we still have a lot of hard-coded dependencies on shared library packages.
These fixes just take some minutes, not only replacing a shared library
name with another hard-coded name.
On 09.02.24 18:51, Brian Murray wrote:
Additionally, we've increased the default instance size from 1 CPU and
1536MB to 2 CPUs and 4096MB. Subsequently, the Ubuntu QA team will also
be testing all the packages hinted to run on the big flavor to see if
the hint is still necessary.
is this just
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
The feature freeze for the 24.04 LTS release is approaching (Feb 29),
however we have some packages which didn't see merges since the last
Ubuntu LTS release, including packages with new upstream versions.
Please have a look at
https://merges.ubuntu.com/universe.html
and merge packages in
The feature freeze for the 24.04 LTS release is approaching (Feb 29),
however we have some packages which didn't see merges since the last
Ubuntu LTS release, including packages with new upstream versions.
Please have a look at
https://merges.ubuntu.com/universe.html
and merge packages in
I don't think that checks for ABI stability should be at the discretion of the
package maintainer. Symbols files for C++ is the implementation which is not
ideal, but currently in use. The right thing to do is to replace these with
state of the art technology, like abi-check from Google, or
On 06.05.22 08:53, Steve Langasek wrote:
Hi Andreas,
On Thu, May 05, 2022 at 05:33:37PM -0300, Andreas Hasenack wrote:
Hi,
this came up again in a review, and I wanted to ask a broader audience.
How to we send LTO[1] related delta to Debian, given that Debian isn't
using LTO (yet)?
On 1/13/22 14:22, Christian Ehrhardt wrote:
> On Thu, Jan 13, 2022 at 12:58 PM Graham Inggs wrote:
>>
>> The first test rebuild of Jammy Jellyfish was started on December 17
>> 2021 for all architectures, all components. The rebuild is finished
>> for all architectures for the main component and
On 12/9/21 15:24, Christian Ehrhardt wrote:
> On Thu, Dec 9, 2021 at 2:25 PM Matthias Klose wrote:
>>
>> This weekend, we will bump the baseline for the ppc64el architecture to
>> POWER9.
>> A test compiler (gcc-11) for jammy can be found at
>>
>> ht
This weekend, we will bump the baseline for the ppc64el architecture to POWER9.
A test compiler (gcc-11) for jammy can be found at
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/p9
We will not do an explicit test rebuild for that change, but do the first test
rebuild during the
The first test rebuild of Impish Indri was started on August 05 2021 for
all architectures, all components. The rebuild is finished on amd64 and i386 for
all components, and finished for all architectures for the main component.
Still running for universe and multiverse for non-x86 architectures.
The first test rebuild of Impish Indri was started on August 05 2021 for
all architectures, all components. The rebuild is finished on amd64 and i386 for
all components, and finished for all architectures for the main component.
Still running for universe and multiverse for non-x86 architectures.
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
Done as part of a comparative test rebuild, there are two test rebuilds (main
only) for focal and groovy, with both the release and the updates pocket
enabled. Results can be found at
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210602-focal-focal.html
First time +1 maintenance for a full week (minus the bank holiday on Monday).
Looks I like doing that better for two times half a week to get other stuff
done.
Things I didn't address:
- golang 1.16 issue, not seen with 1.15
Addressed:
- bazel-bootstrap not migrating on riscv64.
We’re pleased to announce that impish is now *open for development*.
auto-sync has been enabled and will run soon. As usual, we expect a
large influx of builds and autopkgtests in this initial period, which
will cause delays. Please help with fixing any breakage that occurs.
The release schedule
The second test rebuild of Hirsute Hippo was started on March 25 2021 for
all architectures, all components. The rebuild is finished for the main
component, it's still running for the other components.
Results (please also look at the superseded builds) can be found at
The second test rebuild of Hirsute Hippo was started on March 25 2021 for
all architectures, all components. The rebuild is finished for the main
component, it's still running for the other components.
Results (please also look at the superseded builds) can be found at
On 1/29/21 1:34 PM, Matthias Klose wrote:
> Link time optimization (LTO) is a way to run optimizations across multiple
> translation units, enabling more opportunities for optimizations at link time.
> The optimizations allow for faster code and smaller files.
>
> LTO
done this Mon and Tue.
- krop, run autopkg test with allow-stderr
- merge osmnx, avoiding autopkg test failure
- merge ruby-graphviz, avoiding autopkg test failure
- retry krop autopkg tests
- sync the missing request-tracker5 packages from experimental,
the ones in -proposed didn't build.
-
While looking at autopkg test failures, noticed that we had a bunch of nine or
ten day old "in progress" tests. reported to #debian-release. Would be nice to
see checks for these on a more regular basis.
- libdist-zilla-plugin-requiresexternal-perl autopkg test failure,
fixed with
On 2/15/21 3:17 AM, Alex Murray wrote:
> Hi Michael,
>
> For Ubuntu we try and take an approach where we want as much code that
> is compiled for and *on* Ubuntu to try and take advantage of the various
> toolchain hardening options that are available. This gives end-users
> the most protection
On 2/15/21 3:17 AM, Alex Murray wrote:
> Hi Michael,
>
> For Ubuntu we try and take an approach where we want as much code that
> is compiled for and *on* Ubuntu to try and take advantage of the various
> toolchain hardening options that are available. This gives end-users
> the most protection
Since debhelper v9, dh_strip created detached debug files in a file system
layout based on the build-id. This created file conflicts for any detached
debug file with the same build id, usually seen with
- private shared libraries shipped in different packages
- loadable modules
- packages
With the feature and Debian import freeze approaching in about three weeks, I'd
like to propose to also address universe/multiverse merges in our +1 maintenance
tasks within these three weeks. There's a lot untouched for more than one or
two years.
For merges of the main pocket, owned by the
- removal of NBS in -proposed
- looked at some "uninstallable" packages, two of them were
caused by ftbfs of dependent packages. successfully retried builds.
- looked at openmpi and connected transitions
- very puzzled about the dolfin ftbfs ...
- finally found out that openmpi needed a
Link time optimization (LTO) is a way to run optimizations across multiple
translation units, enabling more opportunities for optimizations at link time.
The optimizations allow for faster code and smaller files.
LTO will be turned on for the 64bit architectures (except riscv64) by default
for
I didn't work the full two days on Mon/Tue on +1, because I was already working
on things during the XMas/New Year break, mostly:
- accepting new binary packages
- doing no-change uploads for imported transitions
- resolving component mismatches for those transitions
Continued with the
The first test rebuild of Hirsute Hippo was started on December 20 2020 for
all architectures, all components. The rebuild is almost finished.
It is still running for the multiverse component on some architectures.
Thanks to everybody keeping the buildds going during the end-of-year break.
The first test rebuild of Hirsute Hippo was started on December 20 2020 for
all architectures, all components. The rebuild is almost finished.
It is still running for the multiverse component on some architectures.
Thanks to everybody keeping the buildds going during the end-of-year break.
What happened with libcuda1?
it appears to be removed everywhere
https://packages.ubuntu.com/search?searchon=contents=libcuda.so.1=exactfilename=hirsute=any
# apt install libcuda1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package libcuda1 is a
Santa visited early, brought a Mac Mini, and Parallels provided a first preview
of Parallels Desktop for Mac M1 yesterday.
gcc-10 build and test time is 3:10h with eight cores (38h on LP, although this
is using four cores). Julian had a small apt build benchmark, which is 11.6 sec
on the M1 (-j
afk on Thursday and Friday, doing +1 instead on Monday and Tuesday...
- no-change uploads for a handful of transitions
imported by Debian syncs.
- while the autopkg testers were idle, gave back
some tests to let those migrate.
- finally got acceptance to override any failures
- handled some network outage on Thu night, giving back packages
- disentangled perl and ocaml transitions
- restored older perl4caml
- removed hivex and supermin
- got ocaml migrating, and restored packages
- removed NBS binaries in hirsute-proposed
- worked on some ftbfs, pbbam and it's
On 11/11/20 5:44 PM, Didier Roche wrote:
> This was my first shift during the hirsute dev cycle. Here are some notes:
>
> * Get Go 1.15 as transition as default Go compiler:
> - promote golang 1.15 to main
> - dealt with some failing autopkgtests
> - fix ubuntu-report tests failing with 1.15 due
My second +1 shift in the hirsute cycle (working on fixing python 3.9 related
ftbfs during the first shift):
- started earlier this week with ocaml binNMUs.
uploads are all done, waiting for autopkg tests
- cleared up all "old binaries left" in -proposed,
no-change uploads in cases of
On 10/15/20 1:16 PM, Matthias Klose wrote:
> Python 3.9 will be the default Python3 version for 21.04 (h-series). A year
> ago
> we prepared for 3.8 as the default in focal, going ahead of Debian. For the
> transition to 3.9, we started PPA test rebuilds [1] [2] while groovy w
Hirsute Hippo is now open for development, with the uploads collected in the
queue now approved, and syncs from unstable enabled.
The development version starts with one change:
- Python 3.9 is now added as a supported Python3 version, with the
goal to ship Python 3.9 as the only Python3
Hirsute Hippo is now open for development, with the uploads collected in the
queue now approved, and syncs from unstable enabled.
The development version starts with one change:
- Python 3.9 is now added as a supported Python3 version, with the
goal to ship Python 3.9 as the only Python3
The second test rebuild of Groovy Gorilla was started on September 25 2020 for
all architectures, all components. The rebuild is finished for the
main component. It is still running for the universe/multiverse components.
Results (please also look at the superseded builds) can be found at
The second test rebuild of Groovy Gorilla was started on September 25 2020 for
all architectures, all components. The rebuild is finished for the
main component. It is still running for the universe/multiverse components.
Results (please also look at the superseded builds) can be found at
On 9/9/20 5:31 PM, Colin Watson wrote:
> On Tue, Sep 08, 2020 at 02:51:45PM -0300, Guilherme Piccoli wrote:
>> On Tue, Sep 8, 2020 at 1:48 PM Colin Watson wrote:
>>> Failing that, can somebody advise on whether there's an appropriate way
>>> to configure this in an image without having to
On 9/23/20 7:41 PM, Robie Basak wrote:
> On my SRU shift today, I'm disappointed to report that out of sixteen
> packages I looked at, I didn't end up accepting a single one.
I'm disappointed to see that scilab was rejected without referring to the SRU
exception for OpenJDK-11 in bionic. We all
On 8/4/20 10:31 PM, Steve Langasek wrote:
> On Tue, Aug 04, 2020 at 12:05:10PM +0100, Dimitri John Ledkov wrote:
>> On Tue, 4 Aug 2020 at 10:54, Michael Hudson-Doyle
>> wrote:
>
>>> Hi all,
>
>>> I noticed golang-gopkg-square-go-jose.v2 times out on armhf, filed
>>>
The first test rebuild of Groovy Gorilla was started on July 27 2020 for all
architectures (except riscv64), all components. The rebuild is finished for the
main component (except for armhf/arm64, still working on some heavy daily PPA
test builds). It is still running for the universe/multiverse
Debian started the move to GCC 10 earlier this week, and we are seeing now build
failures in groovy-proposed, mostly for symbols files only adjusted for GCC 10,
breaking builds with GCC 9. That's why I'm doing the gcc-defaults change now in
Ubuntu as well, instead of early August as planned on
On 7/17/20 1:39 AM, Steve Langasek wrote:
> On Thu, Jul 16, 2020 at 06:24:11PM +0200, Matthias Klose wrote:
>
>> the new update_excuses hides the information for successful autopkg tests
>> which makes the page more compact. I dislike that when searching for
>> failed au
On 6/16/20 7:07 PM, Iain Lane wrote:
> Over the last few weeks, I've been working on rebasing our extensive
> delta to proposed-migration. It's now at a state where it's ready for
> others to take a look at. Please check out the output from a dry-run
> (being re-run hourly from cron)
>
>
>
Looking for two days on build failures, starting at the bottom of
update_excuses, packages which have a build in both the release and proposed
pocket. These are still all initial build failures from the groovy opening.
Excluded rust-* and node-* packages.
No update to the wiki page, there's
Following Lucasz's shift, here is the status after the next shift. I'm not
summarizing the status here in the email, but reviving the old wiki page, and
added Lucasz's open items (which are still open after my shift). See
https://wiki.ubuntu.com/PlusOneMaintenanceTeam/Status
The wiki page
The second test rebuild of Focal Fossa was started on March 27 2020 for
all architectures, all components. The rebuild is finished for the main
component, still running for the universe/multiverse components.
Results (please also look at the superseded builds) can be found at
The second test rebuild of Focal Fossa was started on March 27 2020 for
all architectures, all components. The rebuild is finished for the main
component, still running for the universe/multiverse components.
Results (please also look at the superseded builds) can be found at
On 3/23/20 5:36 PM, Daniel Dromboski wrote:
> Just sent this to "ubuntu-devel," but it probably should have been
> posted here instead...
>
> ---
>
> Hi,
>
> At the moment, neither "python-is-python2-but-deprecated" nor
> "python-is-python3" provide the "python" package.
he 20.04 LTS release.
Matthias
PS: Some packages had to be removed from the archive to get this
transition/removal done. Please file a bug report to get those re-added, and CC
me on this report, even if it's after feature freeze.
On 1/25/20 4:54 AM, Matthias Klose wrote:
> One more update, the unve
On 2/14/20 9:52 AM, Julian Andres Klode wrote:
> On Thu, Feb 13, 2020 at 05:33:21PM -0800, Bryce Harrington wrote:
>> Hi devs,
>>
>> For focal the server team will be transitioning PHP to 7.4 over the
>> coming weeks.
>>
>> Since version 7.0, upstream PHP has adopted a regular release cadence,
>>
contact me on irc or via email to restore those
package. However I don't have the resources to actively port these packages to
Python3.
Up to the Python 3.8 transition ...
Matthias
On 06.01.20 14:21, Matthias Klose wrote:
> An update ... starting today, python-defaults in -proposed does
This? https://notabug.org/hp/gogs/pulls/309
Matthias
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
The first test rebuild of Focal Fossa was started on December 20 2019 for
all architectures, all components. The rebuild is finished except for some
pending universe/multiverse builds on armhf and arm64.
A first glance at the test results shows some missing dependencies for i386
builds, and some
will be reintroduced before release in a new package
python-pointing-to-python2.
Matthias
On 11.11.19 01:24, Matthias Klose wrote:
> Enabling the syncs form unstable brang all the Python2 removal goodness to
> focal, however sometimes a little bit too much. Ubuntu has it's own debt in
> now
&g
Enabling the syncs form unstable brang all the Python2 removal goodness to
focal, however sometimes a little bit too much. Ubuntu has it's own debt in now
ownerless packages which still depend on some Python2 module which is now
removed in Debian.
When looking at update_excuses.html, you
Opening a new development series, syncing packages from Debian again, and having
multiple entangled transitions ongoing is not always fun, but we need to handle
that. While working on those I see two kind of issues which could be improved.
Seeing an Ubuntu delta which is not forwarded to
point all autopkg tests for packages setup for multiple
Python3 versions will be run for 3.7 and 3.8.
- Do the first archive test rebuild with python3-defaults
supporting both 3.7 and 3.8, and then fix issues before
making 3.8 the default Python3 version.
Michael Hudson-Doyle
Matt
Focal Fossa is now open for development, with the syncs from unstable
done and built, and autopkg testers trying to catch up. The development version
starts with only a few changes:
- Python 3.8 is now added as a supported Python3 version, with the
goal to ship Python 3.8 as the only
Focal Fossa is now open for development, with the syncs from unstable
done and built, and autopkg testers trying to catch up. The development version
starts with only a few changes:
- Python 3.8 is now added as a supported Python3 version, with the
goal to ship Python 3.8 as the only
On 20.08.19 21:06, Matthias Klose wrote:
The removal of Python2 (build-)dependent packages, or the conversion of packages
has now been started in Debian. A few hundred are done, a few thousand are
still on the list :-/
Here is the list of source packages which are in Ubuntu only. It looks
We usually tend to open the archive with a few prepared changes in place, for
the 20.04 cycle we are planning to open with
- python3.8 as a supported version, maybe already as the default.
- link time optimization enabled by default in GCC. This will
add a few ftbfs (~400). I am
On 11.09.19 11:23, Dimitri John Ledkov wrote:
Are you going to copy in fixed up packages to update the report? Or
can coredevs do that somehow?
no, that's technically not possible. you should be able to do that in a regular
eoan build environment (release and proposed enabled), and for the
The second test rebuild of Eoan Ermine was started on September 06 2019 for
all architectures, all components. The rebuild of the main component is
finished, the other components (restricted, universe, multiverse) are still
building.
Unfortunately we see 1300+ build failures, and still
The second test rebuild of Eoan Ermine was started on September 06 2019 for
all architectures, all components. The rebuild of the main component is
finished, the other components (restricted, universe, multiverse) are still
building.
Unfortunately we see 1300+ build failures, and still
On 28.08.19 19:32, Robie Basak wrote:
Any comments on this plan? If there are no objections, I'll update the
wiki page documentation to match.
afaiu block-proposed tags on bugs are not specific to any series, so you are
blocking updates across all series. Not really desired.
Matthias
--
On 28.08.19 09:28, Philipp Kern wrote:
On 2019-08-28 02:00, Matthias Klose wrote:
On 20.08.19 21:06, Matthias Klose wrote:
The removal of Python2 (build-)dependent packages, or the conversion of packages
has now been started in Debian. A few hundred are done, a few thousand are
still
On 20.08.19 21:06, Matthias Klose wrote:
The removal of Python2 (build-)dependent packages, or the conversion of packages
has now been started in Debian. A few hundred are done, a few thousand are
still on the list :-/
Here is the list of source packages which are in Ubuntu only. It looks
Hi,
as previously announced in
https://lists.ubuntu.com/archives/ubuntu-devel-announce/2019-June/001262.html
GCC 9 is now the default in eoan. Using the Sunday to not disturb development
during working hours with needed promotions and demotions.
Matthias
--
ubuntu-devel mailing list
The first test rebuild of Eoan Ermine was started on June 16 2019 for
all architectures, all components.
Results (please also look at the superseded builds) can be found at
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190614-eoan.html
The report uses some additional color
The first test rebuild of Eoan Ermine was started on June 16 2019 for
all architectures, all components.
Results (please also look at the superseded builds) can be found at
https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190614-eoan.html
The report uses some additional color
On 10.04.19 07:50, Christian Ehrhardt wrote:
> On Wed, Apr 10, 2019 at 7:21 AM Matthias Klose wrote:
>>
>> Please can we delegate the hinting for autopkg test failures to core
>> developers
>> and MOTU?
>
> Hi Matthias,
> I like the idea, but to
Please can we delegate the hinting for autopkg test failures to core developers
and MOTU?
When ignoring an autopkg test failure, you usually have a reason to do so. As a
core developer you already can work around autopkg test failures with uploading
a work-around in a new package version, both
On 05.04.19 06:10, Steve Langasek wrote:
> Hi Matthias,
>
> On Thu, Apr 04, 2019 at 02:07:50PM +0200, Matthias Klose wrote:
>> On 04.04.19 01:52, Steve Langasek wrote:
>>> Thanks, Robie, for kicking off this discussion.
>
>>> In regards to rails in particular
On 10.04.19 05:48, Simon Quigley wrote:
> On 4/9/19 10:15 PM, Matthias Klose wrote:
>> On 10.04.19 04:37, Simon Quigley wrote:
>>> On 4/9/19 9:27 PM, Matthias Klose wrote:
>>>> rails is ready to migrate, there is no puma package in the release pocket.
>>&
On 10.04.19 04:37, Simon Quigley wrote:
> On 4/9/19 9:27 PM, Matthias Klose wrote:
>> rails is ready to migrate, there is no puma package in the release pocket.
>> the
>> failing puma autopkg test in -proposed shouldn't be any concern.
>>
>> Filed LP: #182404
On 06.04.19 00:14, Steve Langasek wrote:
> Hi Balint,
>
> On Thu, Apr 04, 2019 at 02:45:23PM +0200, Balint Reczey wrote:
>>> This is short-sighted, and greatly influenced by the voices of
>>> language-specific
>>> upstream communities. As seen at several occasions at PyCon: Ask an
>>> upstream
On 08.04.19 23:00, Sebastien Bacher wrote:
> Le 08/04/2019 à 22:50, Steve Langasek a écrit :
>> rls-cc-incoming bugs? I know Foundations does not actively process this
>> queue for stable releases and I would not expect other teams to do so
>> either.
>
> Desktop does review the incoming lists
On 08.04.19 22:50, Steve Langasek wrote:
> Hi Matthias,
>
> On Mon, Apr 08, 2019 at 12:35:09PM +0200, Matthias Klose wrote:
>> Here are results for a cosmic test rebuild (main only), combining the release
>> and the updates pocket:
>
>> http://people.canonical.com/~
Here are results for a cosmic test rebuild (main only), combining the release
and the updates pocket:
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html
Bug reports are filed with tags ftbfs and rls-cc-incoming. No new reports are
filed where the issue still exists
The second test rebuild of Disco Dingo was started on April 04 2019 for
all architectures, just the main component. For technical reasons we were not
able to start that rebuild earlier, and a rebuild for the universe component
wouldn't finish before the 19.04 release.
The usual comment about
The second test rebuild of Disco Dingo was started on April 04 2019 for
all architectures, just the main component. For technical reasons we were not
able to start that rebuild earlier, and a rebuild for the universe component
wouldn't finish before the 19.04 release.
The usual comment about
On 03.04.19 13:41, Robie Basak wrote:
> I'd like to talk about addressing the difficulty in maintenance of long
> tail language-specific stacks in Ubuntu. For example, right now
> `src:rails` is stuck in disco-proposed[1]. It seems to me that we spend
> a disproportionate amount of effort trying
On 04.04.19 06:08, Seth Arnold wrote:
> On Wed, Apr 03, 2019 at 12:41:04PM +0100, Robie Basak wrote:
>> 1. If a language-specific package, or stack of packages, is stuck in
>> proposed, and nobody is volunteering to get them migrated, then we are
>> more willing to delete them from the release
On 04.04.19 01:52, Steve Langasek wrote:
> Thanks, Robie, for kicking off this discussion.
>
> In regards to rails in particular, I would like to note that the same
> version of the rails package is present in the bionic, cosmic, and disco
> releases. Despite several uploads and syncs/merges
updates for 18.04 LTS
as long as we provide them for the 16.04 LTS (xenial) release.
On behalf of the OpenJDK 11 transition team,
Matthias Klose
--
List of packages in -proposed:
activemq
afterburner.fx
android-framework-23
android-platform-art
android-platform-build
android-platform-dalvik
android
The first test rebuild of Disco Dingo was started on December 21 2018 for
all architectures, all components. The number of build time failures
unfortunately is again high, even higher than for the last Cosmic Cuttlefish
test rebuild.
Results (please also look at the superseded builds) can be
The first test rebuild of Disco Dingo was started on December 21 2018 for
all architectures, all components. The number of build time failures
unfortunately is again high, even higher than for the last Cosmic Cuttlefish
test rebuild.
Results (please also look at the superseded builds) can be
On 04.12.18 18:41, Robie Basak wrote:
> I'm planning to start transitions for PHP and MySQL soon, with the first
> uploads in the next day or two. If it would be better to wait, please
> let me know.
>
> I'll detail the plan with PHP in a reply to Jeremy's email as soon as
> we've confirmed it'll
Disco Dingo is now open for development, with the syncs from unstable
done and built. The development version starts with only a few changes:
- Python 3.7 is now the default Python3 version, and the only supported
Python3 version.
- Perl was updated to version 5.28
- Merged-usr is now
On 22.09.2018 16:29, Andreas Hasenack wrote:
> Thanks for this!
>
> I couldn't find the build log related to the libapache2-mod-perl2
> build failure at
> https://launchpad.net/ubuntu/+archive/test-rebuild-20180911/+build/1535
>
> Here is a bileto build of that package in cosmic-proposed and
The first test rebuild of Cosmic Cuttlefish was started on September 11 2018 for
all architectures, all components (main component and seeded packages finished,
unseeded packages still building). The number of build time failures
unfortunately is again high.
The test rebuild was done using the
The first test rebuild of Cosmic Cuttlefish was started on September 11 2018 for
all architectures, all components (main component and seeded packages finished,
unseeded packages still building). The number of build time failures
unfortunately is again high.
The test rebuild was done using the
There are four test rebuilds done for xenial and bionic (main only), both the
release and the updates pockets. The results of both builds are combined in one
table. Please see
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180727-main-xenial.html
On 21.08.2018 17:01, Stéphane Graber wrote:
> On Tue, Aug 21, 2018 at 04:58:21PM +0200, Matthias Klose wrote:
>> On 21.08.2018 16:56, Stéphane Graber wrote:
>>> On Tue, Aug 21, 2018 at 11:46:34AM +0200, Matthias Klose wrote:
>>>> On 20.08.2018 23:13, Stéphane Graber
1 - 100 of 277 matches
Mail list logo
