Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package skyview.
The package fixes the RC bug #923761, "skyview: FTBFS in buster/sid".
Aside from that, the Standards-Version is pushed (no change was
required), and a standa
Hi Paul,
The usual stuff: real life. In any case I am not using esajpip much
these days. So let's finally kill it. I'll file a RM bug report ASAP.
Thanks
On Mon, Mar 11, 2019 at 7:47 PM Paul Gevers wrote:
>
> Hi Mathieu,
>
> On 11-03-2019 18:41, Mathieu Malaterre wrote:
> > Could someone please
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi,
this is a new upstream release from the 390.xx legacy branch (that we
finally switched to in the last point release).
This fixes CVE‑2018‑6260.
There are only minor packaging r
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: chiara.ma...@u-psud.fr
Please unblock package aravis.
The package fixes the important bug #922823, "aravis-tools: arv-viewer
fails to start due to missing file arv-viewer.ui".
Processing commands for cont...@bugs.debian.org:
> tags 923864 - moreinfo
Bug #923864 [release.debian.org] unblock: rails/2:5.2.2+dfsg-6
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
923864: https://bugs.debian.org/cgi-bin/bugreport.cgi?
Your message dated Tue, 12 Mar 2019 13:13:01 +
with message-id
and subject line unblock live-build
has caused the Debian Bug report #924306,
regarding unblock: live-build/1:20190311
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Tue, 12 Mar 2019 13:15:15 +
with message-id
and subject line unblock g810-led
has caused the Debian Bug report #924263,
regarding unblock: g810-led/0.3.3-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is no
Your message dated Tue, 12 Mar 2019 13:19:34 +
with message-id
and subject line unblock node-istanbul
has caused the Debian Bug report #924317,
regarding unblock: node-istanbul/0.4.5+ds-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Tue, 12 Mar 2019 13:20:21 +
with message-id
and subject line unblock owasp-java-html-sanitizer
has caused the Debian Bug report #924364,
regarding unblock: owasp-java-html-sanitizer/0.1+r88-2
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Tue, 12 Mar 2019 13:17:27 +
with message-id
and subject line unblock dahdi-linux
has caused the Debian Bug report #924276,
regarding unblock: dahdi-linux/1:2.11.1.0.20170917~dfsg-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 12 Mar 2019 13:22:04 +
with message-id
and subject line unblock php7.3
has caused the Debian Bug report #924354,
regarding unblock: php7.3/7.3.3-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libqmi
The current version in Buster has incorrect "client id" tracking
and thus breaks things like ModemManagers ability to receive SMS
(and who known what else).
U
Your message dated Tue, 12 Mar 2019 14:43:07 +
with message-id
and subject line unblock libqmi
has caused the Debian Bug report #924394,
regarding unblock: libqmi/1.22.0-1.2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Your message dated Tue, 12 Mar 2019 14:44:48 +
with message-id
and subject line unblock aravis
has caused the Debian Bug report #924384,
regarding unblock: aravis/0.6.0-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now yo
Your message dated Tue, 12 Mar 2019 15:47:05 +0100
with message-id
and subject line Re: Bug#924375: unblock: skyview/3.4.2+repack-2
has caused the Debian Bug report #924375,
regarding unblock: skyview/3.4.2+repack-2
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Tue, 12 Mar 2019 14:50:26 +
with message-id
and subject line unblock dehydrated
has caused the Debian Bug report #924320,
regarding unblock: dehydrated/0.6.2-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it i
Package: release.debian.org
Severity: normal
I have detected an ugly bug in ros-catkin (#924395). It _only_ affects to
software that uses catkin and generates pkgconfig files (.pc) that uses
Boost.
In our case we have ros-rosconsole. The pkgconfig file is wrong. So, I would
like to push a new ver
Processing control commands:
> tags -1 + pending
Bug #923556 [release.debian.org] stretch-pu: package
r-cran-igraph/1.0.1-1+deb9u1
Added tag(s) pending.
--
923556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + pending
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian stretch.
Thanks for your contribution!
Upload details
==
Package: r-cran-igraph
Version: 1.0.1-1+deb9u1
Explanation: security fix [CV
Processing control commands:
> tags -1 + pending
Bug #923556 [release.debian.org] stretch-pu: package
r-cran-igraph/1.0.1-1+deb9u1
Ignoring request to alter tags of bug #923556 to the same tags previously set
--
923556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923556
Debian Bug Trackin
Le 09/03/2019 à 17:25, Adam D. Barratt a écrit :
> Ping? If nothing happens with the next couple of weeks then I plan on
> closing this bug.
>
Thanks for the heads up. I can't believe I missed your mail for so long.
Uploaded.
Kind regards, Thibaut.
signature.asc
Description: OpenPGP digital
Processing changes file: openjpeg2_2.1.2-1.1+deb9u3_amd64.changes
ACCEPT
Processing changes file: openjpeg2_2.1.2-1.1+deb9u3_arm64.changes
ACCEPT
Processing changes file: openjpeg2_2.1.2-1.1+deb9u3_armel.changes
ACCEPT
Processing changes file: openjpeg2_2.1.2-1.1+deb9u3_armhf.changes
ACCEPT
Processing changes file: debian-installer_20170615+deb9u5+b3_armhf.changes
ACCEPT
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nvidia-graphics-drivers
This is a new upstream release fixing CVE‑2018‑6260.
I had postponed the upload to have the package stack sitting in sid
(which was blocked by
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package nvidia-settings-legacy-390xx
This is a new upstream release to match the new driver (which migrated
on its own). I was a bit late to upload this package in time, too.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Dear Release Managers,
I'd llike to ask you to please unblock package lxc version
1:3.1.0+really3.0.3-6 currently lying in unstable, so it replaces lxc
version 1:3.1.0+really3.0.3-4 current
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package grfcodec
Version 6.0.6-3 adds a tiny patch to fix a serious bug (#922625).
unblock grfcodec/6.0.6-3
Thanks!
-- System Information:
Debian Release: 9.3
APT prefer
Le mardi 12 mars 2019 à 22:25:53+0100, Pierre-Elliott Bécue a écrit :
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
>
> Dear Release Managers,
>
> I'd llike to ask you to please unblock package lxc version
> 1:3.1.0+really3.0.3
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_i386.changes
ACCEPT
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_ppc64el.changes
ACCEPT
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_s390x.changes
ACCEPT
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_arm64.changes
ACCEPT
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi,
this is a new upstream version corresponding to the updated
nvidia-graphics-drivers package.
I don't want to mix the package versions in a way that features would be
missing.
T
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_armel.changes
ACCEPT
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_mipsel.changes
ACCEPT
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please unblock package movim
Upstream fixed a few semi-critical bugs, which we here would call important.
I added the bugs to the BTS and ba
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package node-gyp
- fixes #921625: node-gyp cannot extract tarballs,
something that happens when installing big projects
from npm.
- removes temporarily-needed Breaks:node-mod
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_armhf.changes
ACCEPT
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_mips.changes
ACCEPT
Processing changes file: r-cran-igraph_1.0.1-1+deb9u1_mips64el.changes
ACCEPT
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package pyglet
Unfortunately, due to my miscalculation by a few hours of when the freeze
would hit, unstable is now blocked for pyglet for future uploads to support
buster.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Please unblock package debian-edu-config
OK, first the most honest part: I f***ed up. 2.10.61 was uploade well before
full freeze, fixing a
On Saturday, March 9, 2019, at 3:17 PM EST, Paul Gevers wrote:
> [...] I took a look at the times in the bug, and it seems you uploaded
> the package *after* it got removed.
>
> Is it just me, or did you suggest a different time line? If so, why?
No, it’s not just you – I believed that I had upl
39 matches
Mail list logo
