Your message dated Mon, 7 Mar 2016 23:42:30 +0100
with message-id <56de03d6.6020...@debian.org>
and subject line Re: Bug#817064: nmu: dovecot-antispam_2.0+20150222-1
has caused the Debian Bug report #817064,
regarding nmu: dovecot-antispam_2.0+20150222-1
to be marked as done.
This means that you c
I've been advised on Debian Devel IRC mainly by juliank to stick
to libtesseract3 and not do libtesseract3a. See bug 815056.
Personally, I am in over my head but the IRC folks sound confident
that this is the right course of action.
P.S. Tersseract 3.04.01-4 has a breaks/replace against the ill fa
Subject: transition: tesseract-ocr
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
Severity: normal
As described in bug #815056, there was a packaging mistake that led to
the brief existance of libtesseract4. This problem has been corrected
and we are
On 07-03-16 21:36, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Friday 22 January 2016 17:52:08 Sebastiaan Couwenberg wrote:
>> On 22-01-16 17:03, Lisandro Damián Nicanor Pérez Meyer wrote:
>>> FWIW you also need Qt5's QWT. The packages are kind of ready in
>>> experimental but need a transiti
> +rm_conffile /etc/fonts/conf.avail/65-andika.conf 1.004-2~ fonts-sil-andika
That won't work as expected ... you will need a version of 1.004-2+deb8u2~
otherwise that "fix" won't be applied to systems that already have 1.004-2
installed.
Andreas
QWT with Qt5 support has already entered unstable, feel free to either push
zygrib's experimental version to unstable or ask us for a binNMU for the
version currently in unstable (if suitable).
--
Los estadounidenses no tienen la culpa, la guerra tiene la culpa. La falta de
voluntad de la gente
On Friday 22 January 2016 17:52:08 Sebastiaan Couwenberg wrote:
> On 22-01-16 17:03, Lisandro Damián Nicanor Pérez Meyer wrote:
> > FWIW you also need Qt5's QWT. The packages are kind of ready in
> > experimental but need a transition. I haven't heard of qwt's
> > maintainer in almost two months.
On Sun, 2016-02-21 at 13:07 +, Ben Hutchings wrote:
> On Sun, 2016-02-21 at 12:24 +, Adam D. Barratt wrote:
> > Hi,
> >
> > We're due both Jessie and Wheezy point releases, and are proposing doing
> > both on the same weekend again, as we did for 8.2 and 7.9, as the CD
> > team seem happy
cc += kibi
On Sun, Mar 6, 2016 at 11:21:24 +0100, Samuel Thibault wrote:
> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Hello,
>
> I'd like to upload to Jessie the attached changes to the espeakup
> package.
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Dear Release Team,
Please schedule a binNMU for dovecot-antispam in unstable, in order for
it to be rebuilt against dovecot 2.2.21 (ABI version 2.2.abiv20) and
allow dovecot to migrate to
On Monday 07 March 2016 18:22:45 Emilio Pozuelo Monfort wrote:
[snip]
> Go ahead.
ACK.
Gudjon: I'll do the upload as a team upload.
--
No subestimes el ancho de banda de un camión
cargado de cintas.
Andrew S. Tanenbaum
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://per
On Sunday 06 March 2016 11:37:27 you wrote:
> Go ahead.
Done
All the best
Control: tags -1 confirmed
On 07/03/16 13:43, Lisandro Damián Nicanor Pérez Meyer wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Dear RT: this is a request to transition qwt from experimental to unstable.
>
> As t
Processing control commands:
> tags -1 confirmed
Bug #817035 [release.debian.org] transition: qwt
Added tag(s) confirmed.
--
817035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 7 Mar 2016 18:18:33 +0100
with message-id <56ddb7e9.8070...@debian.org>
and subject line Re: Bug#817047: nmu: cyphesis-cpp_0.6.0-3
has caused the Debian Bug report #817047,
regarding nmu: cyphesis-cpp_0.6.0-3
to be marked as done.
This means that you claim that the problem
On 2016-03-07 16:34, Ben Hutchings wrote:
We've discussed updates of linux for the next point releases and wheezy
and jessie, and I finally made the uploads at the weekend. Are you
expecting bug reports from me with a summary of changes, or is that
enough?
Just uploading is fine, thanks. The f
We've discussed updates of linux for the next point releases and wheezy
and jessie, and I finally made the uploads at the weekend. Are you
expecting bug reports from me with a summary of changes, or is that
enough?
Ben.
--
Ben Hutchings
The most exhausting thing in life is being insincere. - An
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
It seems that cyphesis-cpp has had problems building on several
architectures, with the result that it depends on various old
library packages on these arches. However the Reproducible Builds
project has mana
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Dear RT: this is a request to transition qwt from experimental to unstable.
As the auto tracker noted this release has an API/ABI breakage without
upstream doing a proper SONAME bump and
On 2016-03-07 10:17, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> Control: forwarded -1
> https://release.debian.org/transitions/html/glibc-2.22.html
>
> On 07/03/16 01:19, Aurelien Jarno wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@pack
Control: tags -1 confirmed
Control: forwarded -1
https://release.debian.org/transitions/html/glibc-2.22.html
On 07/03/16 01:19, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> Dear release team,
>
>
Processing control commands:
> tags -1 confirmed
Bug #817003 [release.debian.org] transition: glibc
Added tag(s) confirmed.
> forwarded -1 https://release.debian.org/transitions/html/glibc-2.22.html
Bug #817003 [release.debian.org] transition: glibc
Set Bug forwarded-to-address to
'https://releas
On 07/03/16 06:50, Sebastiaan Couwenberg wrote:
> What to do about the entanglement with the libvigraimpex transition
> (#815153) through saga?
>
> Should we get saga removed from testing to allow the rest of the
> affected packages in the gdal transition to migrate?
I'm not sure that'll be neces
23 matches
Mail list logo
