[pkg-go] gitlab-ci-multi-runner REMOVED from testing

[Debian testing watch]

FYI: The status of the gitlab-ci-multi-runner source package
in Debian's testing distribution has changed.

  Previous version: 1.11.4+dfsg-2
  Current version:  (not in testing)
  Hint: 
Bug #890107: docker-runc FTBFS on s390x: kill.go:42:20: error: reference to 
undefined identifier 'syscall.SIGUNUSED'
# in docker-runc
Bug #891739: gitlab-ci-multi-runner FTBFS: r.EncodeArrayStart undefined 
(type codec.genHelperEncDriver has no field or method EncodeArrayStart)

The script that generates this mail tries to extract removal
reasons from comments in the britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

[pkg-go] prometheus-alertmanager 0.6.2+ds-5 MIGRATED to testing

[Debian testing watch]

FYI: The status of the prometheus-alertmanager source package
in Debian's testing distribution has changed.

  Previous version: 0.6.2+ds-3
  Current version:  0.6.2+ds-5

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

[pkg-go] golang-github-alecthomas-chroma 0.4.0-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the golang-github-alecthomas-chroma source package
in Debian's testing distribution has changed.

  Previous version: 0.3.0-1
  Current version:  0.4.0-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

[pkg-go] golang-github-jacobsa-crypto 0.0~git20171018.0.c73681c+dfsg1-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the golang-github-jacobsa-crypto source package
in Debian's testing distribution has changed.

  Previous version: 0.0~git20171018.0.c73681c+dfsg1-1
  Current version:  0.0~git20171018.0.c73681c+dfsg1-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

[pkg-go] Processed: gitaly is not configured and not starting with a custom configuration

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.com/gitlab-org/gitaly/issues/1119
Bug #894277 [gitaly] gitaly is not configured and not starting with a custom 
configuration
Set Bug forwarded-to-address to 
'https://gitlab.com/gitlab-org/gitaly/issues/1119'.
> affects -1 gitlab
Bug #894277 [gitaly] gitaly is not configured and not starting with a custom 
configuration
Added indication that 894277 affects gitlab

-- 
894277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

[pkg-go] Bug#894277: gitaly is not configured and not starting with a custom configuration

[Pirate Praveen]

Package: gitaly
Version: 0.91.0+debian-1
Severity: grave
Control: forwarded -1 https://gitlab.com/gitlab-org/gitaly/issues/1119
Control: affects -1 gitlab

This breaks gitlab.



signature.asc
Description: OpenPGP digital signature
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Re: [pkg-go] pkg-go will migrate to salsa.debian.org on 2018-04-02

[Free Ekanayaka]

Great plan and work, can't wait for that. Thanks!

Alexandre Viau  writes:

> Dear pkg-go contributors,
>
> [all pkg-go contributors are in Bcc]
>
> I will be migrating all of pkg-go's Alioth repositories to
> salsa.debian.org on 2018-04-02.
>
> === About the migration ===
>
> - A mail will be sent to pkg-go-maintainers@lists.alioth.debian.org when
> the migration starts and when it ends. I intend to start early in the
> morning, maybe close to 8 AM EDT.
>
> - All repositories in git.debian.org:/git/pkg-go/packages will be
> migrated to the pkg-go-team group on salsa.debian.org[1] You should join
> the group if you are not already in it!
>
> - Repositories will keep the same name, with the trailing ".git" removed.
>
> - HTTP anonscm.debian.org links of migrated repositories will be
> redirected to the new location.
>  for example, you can test the following links:
>   - https://anonscm.debian.org/cgit/pkg-go/packages/syncthing
>   - https://anonscm.debian.org/git/pkg-go/packages/syncthing.git
>
>  - Packages that use the git:// scheme in their vcs-git urls, and that
> have uploaded modifications or upstream versions, will be left behind.
>
> - Packages that use the git:// scheme will be uploaded with new vcs-* urls.
>
> - I will produce a list of what was left behind, and the reason, so that
> we can finish the work. I may have the time to fix it all by myself
> during the migration.
>
> - Pushes to Alioth will be disabled as soon as the migration starts and
> we don't plan to enable them again. If your package was left behind by
> the migration and you want to work on it, you will have to migrate it
> yourself to salsa.debian.org.
>
> === During the migration ===
>
> - You may start using salsa repositories immediately after they are created.
>
> === After the migration ===
>
> - A copy of the migrated repositories will remain available in
> git.debian.org:/git/pkg-go/packages-migrated-to-salsa
>
> - You may point your git working directories to the new remote address
> with this oneliner:
>  ``git remote set-url origin g...@salsa.debian.org:go-team/$(git
> config --get remote.origin.url | tr "/" "\n" | tail -n 1)``
>
> 1. https://salsa.debian.org/go-team
>
> Feel free to ask any questions.
>
> Cheers,
>
> -- 
> Alexandre Viau
> av...@debian.org

___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers