Hi!
I've just pushed a tag and "dch -r" for my first release the
vagrant-librarian-puppet package.
I've tested install and functionality of the vagrant plugin, and I
believe I'm ready for reviews before the package is uploaded! You can
find the code here:
On 19-08-28 08:27:26, Georg Faerber wrote:
> Still, we could at least disable notifications for the pipelines which
> are triggered if tags are pushed. I didn't test this yet, but
> disabling the hook for "Tag push events" should do the trick. This
> way, the pipeline would still run two times,
Hey,
On 28/08/19 6:55 pm, Georg Faerber wrote:
> Hi,
>
> On 19-08-28 10:07:34, Utkarsh Gupta wrote:
>> ruby-benchmark-memory
> Doesn't build for me, the last log lines read:
>
> missing:
> pkg:
> package: sbuild-build-depends-main-dummy
> version: 0.invalid.0
>
Hey,
On 28/08/19 4:18 pm, rajudev wrote:
>
> On 28 August 2019 3:46:27 PM IST, Utkarsh Gupta
> wrote:
>> Hey,
>>
>> On 28/08/19 1:57 pm, Georg Faerber wrote:
>>> Hi,
>>>
>>> This topic is two fold, in my opinion:
>>>
>>> On 19-08-28 08:25:06, Utkarsh Gupta wrote:
It doesn't make much sense
Uploaded with a small change in the patch.
On 19-08-28 11:06:07, Antonio Terceiro wrote:
> What's obsolete/unnecessary is `Testsuite: autopkgtest`, when you have
> debian/tests/control, because dpkg-source will add `Testsuite:
> autopkgtest` for you.
>
> Any other value of `Testsuite:`, including but not limited to
>
On Wed, Aug 28, 2019 at 01:25:15PM +, Georg Faerber wrote:
> - Testsuite: autopkgtest-pkg-ruby in debian/control is obsolete.
What's obsolete/unnecessary is `Testsuite: autopkgtest`, when you have
debian/tests/control, because dpkg-source will add `Testsuite:
autopkgtest` for you.
Any other
Hi,
On 19-08-28 10:07:34, Utkarsh Gupta wrote:
> ruby-benchmark-memory
Doesn't build for me, the last log lines read:
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
Writing extended state
On 28 August 2019 3:46:27 PM IST, Utkarsh Gupta
wrote:
>Hey,
>
>On 28/08/19 1:57 pm, Georg Faerber wrote:
>> Hi,
>>
>> This topic is two fold, in my opinion:
>>
>> On 19-08-28 08:25:06, Utkarsh Gupta wrote:
>>> It doesn't make much sense to run CI on the tags :/
>> Yes, I agree. That's why I
Hey,
On 28/08/19 1:59 pm, Georg Faerber wrote:
> On 19-08-28 13:26:40, Utkarsh Gupta wrote:
>> The upstream code is mostly hosted on GitHub, but that's not the case
>> always, no?
> Yes.
>
>> I am not sure how to do this d/watch thingy because though the
>> homepage mentioned is mostly the URL
Hey,
On 28/08/19 1:57 pm, Georg Faerber wrote:
> Hi,
>
> This topic is two fold, in my opinion:
>
> On 19-08-28 08:25:06, Utkarsh Gupta wrote:
>> It doesn't make much sense to run CI on the tags :/
> Yes, I agree. That's why I created [1] some time ago, more recently [2]
> was created, both
On 19-08-28 13:26:40, Utkarsh Gupta wrote:
> The upstream code is mostly hosted on GitHub, but that's not the case
> always, no?
Yes.
> I am not sure how to do this d/watch thingy because though the
> homepage mentioned is mostly the URL where the source code is hosted
> but sometimes it refers
Hi,
This topic is two fold, in my opinion:
On 19-08-28 08:25:06, Utkarsh Gupta wrote:
> It doesn't make much sense to run CI on the tags :/
Yes, I agree. That's why I created [1] some time ago, more recently [2]
was created, both tickets asking to disable CI by default for tags.
However, so
Hi,
On 19-08-12 11:48:32, Cédric Boutillier wrote:
> This is a list of packages I noticed already used ci, but not with
> debian/salsa-ci.conf.
> the ci config file is still pointing to the original file.
>
> [...]
> ruby-gpgme
> ruby-mail-gpg
> schleuder
> schleuder-gitlab-ticketing
I've fixed
Hi!
,Let's fix the deadline on Wednesday 4 September, 23:59 UTC.
My plan is to try to hold the sprint on the campus of my university, which
should give us good network connection and easy to reach location. It will be
easier to negotiate a room soon if I know the date.
Cheers,
Cedric.
Hey,
On 28/08/19 12:26 pm, Georg Faerber wrote:
> On 19-08-28 10:13:53, Utkarsh Gupta wrote:
>> Perfecto.
>> I just did add a metadata file to include d/upstream/metadata (as we
>> discussed in the BoF); rest in on you :D
> :)
>
>> Also, if possible, I'd love to see gem2deb using the correct
On 19-08-28 10:07:34, Utkarsh Gupta wrote:
> I did complete fixing the pending test failures (as an attempt to
> enable tests in all the packages), thus requesting you to review and
> upload the same (since they are NEW).
>
> ruby-benchmark-memory
> ruby-ammeter
> ruby-arbre (thanks to terceiro
On 19-08-28 10:13:53, Utkarsh Gupta wrote:
> Perfecto.
> I just did add a metadata file to include d/upstream/metadata (as we
> discussed in the BoF); rest in on you :D
:)
> Also, if possible, I'd love to see gem2deb using the correct upstream
> tarballs in d/watch *somehow* instead of what it
18 matches
Mail list logo
