On Sat, 12 Oct 2019 21:47:30 +0900,
Adam D. Barratt wrote:
> I've flagged that for rejection, please re-upload as a source-only
> upload (ensuring that the changes file is _source.changes) so we can
> ensure that all of the binaries are built cleanly.
I had uploaded both stable and oldstable.
On Fri, 2019-10-04 at 15:18 +0900, Takatsugu Nokubi wrote:
> On Sat, 21 Sep 2019 20:47:25 +0100 "Adam D. Barratt"
> wrote:
> > Control: tags -1 + moreinfo
> > What environment were the amd64 packages that you uploaded built
> > in?
>
> Sorry, I had built on a stretch environment, so I rebuild it
On Sat, 21 Sep 2019 20:47:25 +0100 "Adam D. Barratt"
wrote:
> Control: tags -1 + moreinfo
> What environment were the amd64 packages that you uploaded built in?
Sorry, I had built on a stretch environment, so I rebuild it with
git-pbuilder environment,
tested with piuparts, and had uploaded.
Control: tags -1 + moreinfo
On Thu, 2019-09-19 at 09:46 +0900, NOKUBI Takatsugu wrote:
> I'll upload a new version of libsixel for buster.
> It contains many security fix reported by #931311
>
> fixed package for unstable had already uploaded.
> This is just a backports but almost same.
What
On Thu, 19 Sep 2019 09:46:30 +0900 NOKUBI Takatsugu wrote:
> I'll upload a new version of libsixel for buster.
> It contains many security fix reported by #931311
The package is insufficient, so we updated the package source.
Package: release.debian.org
Severity: normal
Tags: patch security buster
User: release.debian@packages.debian.org
Usertags: pu
I'll upload a new version of libsixel for buster.
It contains many security fix reported by #931311
fixed package for unstable had already uploaded.
This is just a
6 matches
Mail list logo
