Hello Marcelo,
On 10/04/2018 01:22 AM, Marcelo Roberto Jimenez wrote:
> I have make a pull request for your gmrender-resurrect github repo with
> my changes.
Yeah, I saw that and already asked the Debian-Maintainer of
gmrender-resurrect to test it. (Though that was in irc so he might have
missed
[2018-10-02 09:38] Emilio Pozuelo Monfort
> part text/plain 567
> On 11/08/2018 09:40, Dmitry Bogatov wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> >
> > Hello. According to [1] I req
Hello,
On Wed, Oct 03, 2018 at 10:01:23PM +0200, Sandro Knauß wrote:
> Hey,
>
> after the first archs have compiled complete kde pim 18.08. Now several
> packages needs to get recompiled against
> the new kdepim, they needs to get rebuilt on any architecture:
[...]
>
> nmu kio-gdrive . ANY . -m
On 2018-10-03 21:02, Alastair McKinstry wrote:
Hi,
See thread below.
I've just uploaded 3.1.2-5 which I believe fixes the hangs due to
OpenMPI ( non-atomic handling of sending a 64-bit tag, occuring mostly
on archs with 32-bit atomics).
Awkward observation: openmpi 3.1.2-5 now causes dolfin t
Hi,
Niels Thykier wrote:
> Before this transition can start, we will need a solution for amule,
> djmount, gmrender-resurrect and linphone (which is either RM or upload
> with a fix).
>
> Removing all of them leads to the following collateral damage[1]:
>
> """
> Checking reverse dependencies...
Hi Uwe,
I have make a pull request for your gmrender-resurrect github repo with my
changes.
I also have the aMule port ready. Does anyone knows if they accept patches
in github?
In the case of djmount has an internal frozen libupnp that is compiled
static by default, at least in the repo I clone
Ah and please remember to also binNMU scribus-ng in experimental :)
On Tue, 2 Oct 2018, 5:00 p.m. Mattia Rizzolo, wrote:
> On Tue, Oct 02, 2018 at 04:46:11PM +0200, Emilio Pozuelo Monfort wrote:
> > Yes. That (openssl) is going to block other larger transitions from
> starting as
> > well, so I'
Processing control commands:
> block 909288 by -1
Bug #909288 [release.debian.org] transition: kdepim 18.08
909288 was blocked by: 908869
909288 was not blocking any bugs.
Added blocking bug(s) of 909288: 910248
--
909288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909288
910248: https://
Hey,
after the first archs have compiled complete kde pim 18.08. Now several
packages needs to get recompiled against
the new kdepim, they needs to get rebuilt on any architecture:
nmu ktorrent . ANY . -m 'Rebuild against kdepim 18.08.1'
dw ktorrent . ANY . -m 'libkf5syndication-dev (>= 18.08.0~
Hi,
Em qua, 3 de out de 2018 às 16:24, Mattia Rizzolo escreveu:
>
> On Wed, Oct 03, 2018 at 02:02:25PM +0100, Alastair McKinstry wrote:
> > Any ideas on how to write the ben tracker script? I think it would work by
> > looking for packages with binaries linked to openmpi rather than mpich, but
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
PostgreSQL 11 RC1 will be released next week, and 11.0 will follow one
week later if everything goes well. I plan to target unstable with RC1.
PG 11 is the version that will be released w
Hi!
On Wed, Oct 03, 2018 at 05:20:59PM +0100, Neil Williams wrote:
> https://release.debian.org/transitions/html/python3.7.html
>
> At what point does a package listed as unknown get processed to
> determine if it is good or bad?
python3 transitions are annoyingly hard to track due to many case
https://release.debian.org/transitions/html/python3.7.html
At what point does a package listed as unknown get processed to
determine if it is good or bad?
What is the trigger for that process?
How do arch:all packages affect the tracker?
https://tracker.debian.org/pkg/nuitka is marked as good b
Hi Philipp!
On 10/3/18 4:29 PM, Philipp Kern wrote:
> Please excuse my ignorance, but which architecture do we still have with
> 2 GiB address space? The main point of removing s390 was that this was
> unsustainable.
The 32-bit MIPS architectures have this limitation which causes various
build is
On 2018-10-03 22:12, Mattia Rizzolo wrote:
the false positives could be just handled manually (i.e. listed in the
transition bug), I don't think there are many that links to both.
Also, please note that mpich never built on riscv64, and is not up2date
on hppa and ppc64. I think at least the ri
On Sat, Sep 29, 2018 at 05:05:17PM +0200, John Paul Adrian Glaubitz
wrote:
Well, I have had people from IBM fix 32-bit PowerPC code. There is
naturally more involvement behind the 64-bit stuff because that's where
the commercial interests are.
The kernel itself dropped 32bit powerpc support yea
ср, 3 окт. 2018 г. в 17:48, Jonathan Dowland :
>
> On Sat, Sep 29, 2018 at 05:05:17PM +0200, John Paul Adrian Glaubitz
> wrote:
> >Well, I have had people from IBM fix 32-bit PowerPC code. There is
> >naturally more involvement behind the 64-bit stuff because that's where
> >the commercial interest
On 29.09.2018 00:30, John Paul Adrian Glaubitz wrote:
> On 9/28/18 11:26 PM, Adam D. Barratt wrote:
>> On Fri, 2018-09-28 at 14:16 +0200, John Paul Adrian Glaubitz wrote:
>>> So, it's not always a purely technical decision whether a port
>>> remains a release architecture. It's also often highly po
On Wed, Oct 03, 2018 at 02:02:25PM +0100, Alastair McKinstry wrote:
> Any ideas on how to write the ben tracker script? I think it would work by
> looking for packages with binaries linked to openmpi rather than mpich, but
> there are a number of packages that would be false positives (HDF5,
> open
Hi,
See thread below.
I've just uploaded 3.1.2-5 which I believe fixes the hangs due to
OpenMPI ( non-atomic handling of sending a 64-bit tag, occuring mostly
on archs with 32-bit atomics).
With this, I think it is appropriate to start the ball rolling on making
mpich the default MPI for bu
Processing control commands:
> block 909288 by -1
Bug #909288 [release.debian.org] transition: kdepim 18.08
909288 was not blocked by any bugs.
909288 was not blocking any bugs.
Added blocking bug(s) of 909288: 908869
> severity -1 serious
Bug #908869 [blogilo] blogilo: FTBFS with pimtextedit 18.0
Your message dated Wed, 3 Oct 2018 09:23:06 +0200
with message-id <464f1a10-86bb-3b2c-03f2-ef0f5f8eb...@debian.org>
and subject line Re: Bug#910136: nmu: php-ast_0.1.6-2
has caused the Debian Bug report #910136,
regarding nmu: php-ast_0.1.6-2
to be marked as done.
This means that you claim that th
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
nmu php-ast_0.1.6-2 . ANY . unstable . -m "Rebuild for PHP 7.3"
nmu php-geoip_1.1.1-2 . ANY . unstable . -m "Rebuild for PHP 7.3"
nmu php-gmag
23 matches
Mail list logo
