ruby-gpgme - incorrect upload target
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
Not accepted by any per-suite acl (suite=stretch-backports)
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
ruby-gpgme_2.0.16-1~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
ruby-gpgme_2.0.16-1~bpo9+1.dsc
ruby-gpgme_2.0.16-1~bpo9+1.debian.tar.xz
ruby-gpgme-dbgsym_2.0.16-1~bpo9+1_amd64.deb
ruby-gpgme_2.0.16-1~bpo9+1_amd64.buildinfo
ruby-gpgme_2.0.16-1~bpo9+1_amd64
Mapping stretch to stable.
Mapping stable to proposed-updates.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 14 Feb 2018 03:00:05 +0100
Source: ruby-gpgme
Binary: ruby-gpgme
Architecture: source amd64
Version: 2.0.16-1~bpo9+1
Distribution: stretch
Urgency: medi
ruby-gpgme_2.0.16-1~bpo9+1_amd64.changes uploaded successfully to localhost
along with the files:
ruby-gpgme_2.0.16-1~bpo9+1.dsc
ruby-gpgme_2.0.16-1~bpo9+1.debian.tar.xz
ruby-gpgme-dbgsym_2.0.16-1~bpo9+1_amd64.deb
ruby-gpgme_2.0.16-1~bpo9+1_amd64.buildinfo
ruby-gpgme_2.0.16-1~bpo9+1_amd64
Hi Antonio,
On 18-02-11 16:14:14, Antonio Terceiro wrote:
> On Thu, Feb 08, 2018 at 12:30:01AM +0100, Georg Faerber wrote:
> > On 17-12-26 20:59:22, Pirate Praveen wrote:
> > > On 12/26/2017 08:28 PM, Chris Hofstaedtler wrote:
> > > > 1) provide a working mail adress in the Maintainer field.
> > >
Hi,
On 02/13/2018 03:40 PM, Balasankar C wrote:
> Hi,
>
> On 02/13/2018 03:05 PM, Christian Hofstaedtler wrote:
>>
>>> On 13.02.2018, at 06:25, Georg Faerber wrote:
>>>
>>> Hi all,
>>>
>>> I've pushed a commit to schleuder [1] to make use of the GitLab CI.
>>> However, it seems, CI / shared runn
Hi all,
On 18-02-13 15:40:45, Balasankar C wrote:
> On 02/13/2018 03:05 PM, Christian Hofstaedtler wrote:
> >> On 13.02.2018, at 06:25, Georg Faerber wrote:
> >>
> >> I've pushed a commit to schleuder [1] to make use of the GitLab CI.
> >> However, it seems, CI / shared runners aren't enabled for
Hi,
On 02/13/2018 03:05 PM, Christian Hofstaedtler wrote:
>
>> On 13.02.2018, at 06:25, Georg Faerber wrote:
>>
>> Hi all,
>>
>> I've pushed a commit to schleuder [1] to make use of the GitLab CI.
>> However, it seems, CI / shared runners aren't enabled for this repo, and
>> I'm not able to enab
> On 13.02.2018, at 06:25, Georg Faerber wrote:
>
> Hi all,
>
> I've pushed a commit to schleuder [1] to make use of the GitLab CI.
> However, it seems, CI / shared runners aren't enabled for this repo, and
> I'm not able to enable them on my own.
I’ve just pushed this:
https://salsa.debian.or
10 matches
Mail list logo