Re: [pkg-go] May I upgrade golang-blackfriday, golang-testify, etc. to latest versions?

[Michael Stapelberg]

On Tue, Sep 8, 2015 at 8:53 AM, Anthony Fok  wrote:
> Hello all,
>
> I would like to package Hugo ( http://gohugo.io/ ) for Debian,
> and I am starting to package the various Go packages that
> Hugo depends on.
>
> One of the packages that need updating is golang-blackfriday
> because Hugo depends on some new features in the latest
> russross/blackfriday in git HEAD, and would not compile with
> the old release of blackfriday 1.2.
>
> Other packages that might need updating include golang-testify,
> golang-objx, etc.
>
> May I...
>
>   1. ... just go ahead and update them?  :-)

Yes.

>
>   2. Or should I first ask for permissions from the previous uploaders?

You should at least let them know, but team policy is that we don’t
have such strict ownership. The packages are team-maintained for a
reason.

>
>   3. Or should I create new packages like golang-github-russross-blackfriday
>   for the cutting-edge version, and leave golang-blackfriday
>   as the stable 1.2 version?

No, but you should rename the existing packages to the proper name.
See other recently uploaded packages for examples on how to do that
with regards to Breaks/Replaces if you’re unsure about that.

>
> Thank you for your advice!

Thank you for your contributions :).

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



-- 
Best regards,
Michael

___
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] May I upgrade golang-blackfriday, golang-testify, etc. to latest versions?

[Anthony Fok]

Hello all,

I would like to package Hugo ( http://gohugo.io/ ) for Debian,
and I am starting to package the various Go packages that
Hugo depends on.

One of the packages that need updating is golang-blackfriday
because Hugo depends on some new features in the latest
russross/blackfriday in git HEAD, and would not compile with
the old release of blackfriday 1.2.

Other packages that might need updating include golang-testify,
golang-objx, etc.

May I...

  1. ... just go ahead and update them?  :-)

  2. Or should I first ask for permissions from the previous uploaders?

  3. Or should I create new packages like golang-github-russross-blackfriday
  for the cutting-edge version, and leave golang-blackfriday
  as the stable 1.2 version?

Thank you for your advice!

Cheers,
Anthony

___
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] May I upgrade golang-blackfriday, golang-testify, etc. to latest versions?

[Paul Tagliamonte]

On Tue, Sep 08, 2015 at 09:00:34AM +0200, Michael Stapelberg wrote:
> >   1. ... just go ahead and update them?  :-)
> 
> Yes.

Yesish. Yes, you should absolutely update them, but you should also
check all their reverse build dependencies to ensure that we don't cause
FTBFSs. Yo, sECuRE - is RATT ready for team use?

> >   2. Or should I first ask for permissions from the previous uploaders?
> 
> You should at least let them know, but team policy is that we don’t
> have such strict ownership. The packages are team-maintained for a
> reason.

Absolutely true. Just be careful of an upload before we know what might
trigger FTBFSs -- upstreams in Goland seem to break API all the time, so
we should be a bit careful in leau of versioning.

> >   3. Or should I create new packages like golang-github-russross-blackfriday
> >   for the cutting-edge version, and leave golang-blackfriday
> >   as the stable 1.2 version?
> 
> No, but you should rename the existing packages to the proper name.
> See other recently uploaded packages for examples on how to do that
> with regards to Breaks/Replaces if you’re unsure about that.
> 
> >
> > Thank you for your advice!
> 
> Thank you for your contributions :).

+1!

Cheers,
   Paul


signature.asc
Description: 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] May I upgrade golang-blackfriday, golang-testify, etc. to latest versions?

[Michael Stapelberg]

Yeah, https://github.com/Debian/ratt should be ready to use. Please
let me know of any issues you encounter.

On Tue, Sep 8, 2015 at 8:37 PM, Paul Tagliamonte  wrote:
> On Tue, Sep 08, 2015 at 09:00:34AM +0200, Michael Stapelberg wrote:
>> >   1. ... just go ahead and update them?  :-)
>>
>> Yes.
>
> Yesish. Yes, you should absolutely update them, but you should also
> check all their reverse build dependencies to ensure that we don't cause
> FTBFSs. Yo, sECuRE - is RATT ready for team use?
>
>> >   2. Or should I first ask for permissions from the previous uploaders?
>>
>> You should at least let them know, but team policy is that we don’t
>> have such strict ownership. The packages are team-maintained for a
>> reason.
>
> Absolutely true. Just be careful of an upload before we know what might
> trigger FTBFSs -- upstreams in Goland seem to break API all the time, so
> we should be a bit careful in leau of versioning.
>
>> >   3. Or should I create new packages like 
>> > golang-github-russross-blackfriday
>> >   for the cutting-edge version, and leave golang-blackfriday
>> >   as the stable 1.2 version?
>>
>> No, but you should rename the existing packages to the proper name.
>> See other recently uploaded packages for examples on how to do that
>> with regards to Breaks/Replaces if you’re unsure about that.
>>
>> >
>> > Thank you for your advice!
>>
>> Thank you for your contributions :).
>
> +1!
>
> Cheers,
>Paul



-- 
Best regards,
Michael

___
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] May I upgrade golang-blackfriday, golang-testify, etc. to latest versions?

[Paul Tagliamonte]

On Tue, Sep 08, 2015 at 06:05:45PM -0600, Anthony Fok wrote:
> > No, but you should rename the existing packages to the proper name.
> > See other recently uploaded packages for examples on how to do that
> > with regards to Breaks/Replaces if you’re unsure about that.
> 
> Thank you for this very important note.  I took some time to examine existing
> packages (basically git cloned 237 Go packages and grep'd for ^Replaces: etc.)
> and noticed slight discrepancies.  Now, regarding the renaming:
> 
>  1. Rename the binary -dev package
>  2. Rename the source package in debian/control (and hence orig.tar.xx too)
>  3. Rename the git repository too, i.e. "ssh git.debian.org",
>  "cd /git/pkg-go/packages", then "mv old-name.git new-name.git"
> 
> Should I just do #1?  (e.g. golang-gocolorize, a new package)
> Or just #1 and #2?  (e.g. golang-golang-x-net-dev)
> Or all three?  (e.g. golang-github-gorilla-mux)

I actually haven't thought about the right thing here -- but some
related thoughts from an archive standpoint:

1: Package enters binNEW, old binary package is marked by NBS, and
   it'll get tracked as archive cruft.

2: Package enters source NEW, marked as a binary hijack, and old source
   package is marked as obsolete source package, and gets tracked as
   archive cruft.

1 and 2: Package enters Source NEW *and* has new binaries, and dak won't
 see the old package as cruft


My thoughts are if we do #1 and #2 at the same time, we must also file
ftp-master removal bugs. If we do #1 and then #2 later, we wind up going
through NEW twice. Or #2 then #1. Doing both is more work on us, and
doing them independently will put more work on the ftpteam (and lag
updates).

That being said, I'm happy to process such things out of NEW.

> And, should I use Breaks/Replaces/Provides with transitional package
> (e.g. golang-golang-x-net-dev) instead of Conflicts/Replaces/Provides
> without transitional package (e.g. golang-github-gorilla-mux)?

I'd avoid using a new package for this, no reason we can't just provide
the package and make it virtual, I guess. Other thoughts on the team?

> Sorry for sounding pedantic, but as I am still pretty new to this
> and will be upgrading/migrating at least a handful of Go packages,
> I would like to know the best way before I dive all in.
> 
> Thanks again!
> 
> Cheers,
> Anthony

Cheers,
   Paul


signature.asc
Description: 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