** No longer affects: golang-go.net-dev (Ubuntu)
** No longer affects: gccgo-go (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-go.net-dev in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core,
** No longer affects: golang-go.net-dev (Ubuntu)
** No longer affects: gccgo-go (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb, gccgo, golang
golang-go.net-dev was renamed to golang-golang-x-net-dev; please can we
promote the right source package and drop golang-go.net-dev from wily.
** Also affects: golang-golang-x-net-dev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-pretty (Ubuntu)
Importance:
golang-pretty and golang-text are showing in the dep chain for golang-
github-bmizerany-assert - adding bug tasks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
golang-pretty and golang-text are showing in the dep chain for golang-
github-bmizerany-assert - adding bug tasks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core,
golang-go.net-dev was renamed to golang-golang-x-net-dev; please can we
promote the right source package and drop golang-go.net-dev from wily.
** Also affects: golang-golang-x-net-dev (Ubuntu)
Importance: Undecided
Status: New
** Also affects: golang-pretty (Ubuntu)
Importance:
>> golang-text <<
[Availability]
In universe
[Rationale]
Dependency for github-bmizerany-assert
[Security]
No security history
[Quality assurance]
Package builds OK and runs unit tests
[Dependencies]
All in main or covered by this MIR
[Standards compliance]
OK
[Maintenance]
ubuntu-server
(neither of text or pretty executed unit tests - they now do - bugs
submitted back to Debian).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb, gccgo,
Indeed the golang-go.net-dev transitional package is now built by the
golang-golang-x-net-dev source, so the old source can indeed be removed:
Removing packages from wily:
golang-go.net-dev 0.0+git20150226.3d87fd6-1 in wily
Comment: renamed to golang-golang-x-net-dev
--
You received
Indeed the golang-go.net-dev transitional package is now built by the
golang-golang-x-net-dev source, so the old source can indeed be removed:
Removing packages from wily:
golang-go.net-dev 0.0+git20150226.3d87fd6-1 in wily
Comment: renamed to golang-golang-x-net-dev
--
You received
(neither of text or pretty executed unit tests - they now do - bugs
submitted back to Debian).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-go.net-dev in Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR]
>> golang-text <<
[Availability]
In universe
[Rationale]
Dependency for github-bmizerany-assert
[Security]
No security history
[Quality assurance]
Package builds OK and runs unit tests
[Dependencies]
All in main or covered by this MIR
[Standards compliance]
OK
[Maintenance]
ubuntu-server
>golang-go.net-dev was renamed to golang-golang-x-net-dev; please can we
promote the right source package and drop golang-go.net-dev from wily.
Ack, updating bug tasks. However, we can't remove golang-go.net-dev yet,
as we still need the transitional package until 16.04 LTS. It can be
removed
>golang-go.net-dev was renamed to golang-golang-x-net-dev; please can we
promote the right source package and drop golang-go.net-dev from wily.
Ack, updating bug tasks. However, we can't remove golang-go.net-dev yet,
as we still need the transitional package until 16.04 LTS. It can be
removed
Remaining 15.10 issues fixed in juju-core 1.24.6-0ubuntu2.
** Changed in: juju-core (Ubuntu)
Status: New => Fix Committed
** Changed in: juju-core (Ubuntu)
Assignee: Matthias Klose (doko) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
golang-x-text now builds fine. Marking Fix Committed.
** Changed in: golang-x-text (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-go.net-dev in Ubuntu.
golang-x-text now builds fine. Marking Fix Committed.
** Changed in: golang-x-text (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR]
Remaining 15.10 issues fixed in juju-core 1.24.6-0ubuntu2.
** Changed in: juju-core (Ubuntu)
Status: New => Fix Committed
** Changed in: juju-core (Ubuntu)
Assignee: Matthias Klose (doko) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
$ ./change-override -c main -t golang-juju-loggo golang-github-bmizerany-assert
golang-github-bmizerany-pat golang-go-dbus golang-golang-x-net-dev
golang-pretty golang-text golang-x-text
Override component to main
golang-juju-loggo 0.0~git20150318-0ubuntu1 in wily: universe/devel -> main
$ ./change-override -c main -t golang-juju-loggo golang-github-bmizerany-assert
golang-github-bmizerany-pat golang-go-dbus golang-golang-x-net-dev
golang-pretty golang-text golang-x-text
Override component to main
golang-juju-loggo 0.0~git20150318-0ubuntu1 in wily: universe/devel -> main
juju-local was already in main, but juju-core is seeded and was not.
$ ./change-override -c main juju-core
Override component to main
juju-core 1.24.6-0ubuntu2 in wily amd64: universe/devel/extra/100% -> main
juju-core 1.24.6-0ubuntu2 in wily arm64: universe/devel/extra/100% -> main
juju-core
$ ./change-override -c main -S golang-race-detector-runtime
Override component to main
golang-race-detector-runtime 0.0+svn229396-0ubuntu1 in wily: universe/devel ->
main
golang-race-detector-runtime 0.0+svn229396-0ubuntu1 in wily amd64:
universe/devel/extra/100% -> main
Override [y|N]? y
2
golang-race-detector-runtime is a Recommends of golang. I looked at it--
packaging is fine, pulls in no new depends, builds fine and has a
testsuite.
** Also affects: golang-race-detector-runtime (Ubuntu)
Importance: Undecided
Status: New
** Changed in: golang-race-detector-runtime
golang-race-detector-runtime is a Recommends of golang. I looked at it--
packaging is fine, pulls in no new depends, builds fine and has a
testsuite.
** Also affects: golang-race-detector-runtime (Ubuntu)
Importance: Undecided
Status: New
** Changed in: golang-race-detector-runtime
$ ./change-override -c main -S golang-race-detector-runtime
Override component to main
golang-race-detector-runtime 0.0+svn229396-0ubuntu1 in wily: universe/devel ->
main
golang-race-detector-runtime 0.0+svn229396-0ubuntu1 in wily amd64:
universe/devel/extra/100% -> main
Override [y|N]? y
2
golang-pretty packaging looks fine. Testsuite enabled in the build.
Builds on wily. Marking Fix Committed.
** Changed in: golang-pretty (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ ./change-override -c main -t juju-core
Override component to main
juju-core 1.24.6-0ubuntu2 in wily: universe/devel -> main
Override [y|N]? y
1 publication overridden.
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because
golang-text packaging looks fine, testsuite enabled in the build, builds
on wily. Marking Fix Committed.
** Changed in: golang-text (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
golang-text packaging looks fine, testsuite enabled in the build, builds
on wily. Marking Fix Committed.
** Changed in: golang-text (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
$ ./change-override -c main -t juju-core
Override component to main
juju-core 1.24.6-0ubuntu2 in wily: universe/devel -> main
Override [y|N]? y
1 publication overridden.
** Changed in: juju-core (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because
golang-pretty packaging looks fine. Testsuite enabled in the build.
Builds on wily. Marking Fix Committed.
** Changed in: golang-pretty (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
juju-local was already in main, but juju-core is seeded and was not.
$ ./change-override -c main juju-core
Override component to main
juju-core 1.24.6-0ubuntu2 in wily amd64: universe/devel/extra/100% -> main
juju-core 1.24.6-0ubuntu2 in wily arm64: universe/devel/extra/100% -> main
juju-core
As per Jamie's request, I created bug 1507470 as a skeleton for adding
generic autopkgtesting of Go libs/packages. Can someone who is familiar
with Go packages please assign themselves and provide the details?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
As per Jamie's request, I created bug 1507470 as a skeleton for adding
generic autopkgtesting of Go libs/packages. Can someone who is familiar
with Go packages please assign themselves and provide the details?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
@pitti
Thanks for creating the bug. IMO the bare minimum and the first step is
simply to rebuild (many of these golang packages do have in-build
testsuites too). More stuff could then be added later.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@pitti
Thanks for creating the bug. IMO the bare minimum and the first step is
simply to rebuild (many of these golang packages do have in-build
testsuites too). More stuff could then be added later.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
"Are you saying you want to use the embedded code copy? Has anyone
looked at the testsuite issue to fix it? Embedded code copies should be
avoided at all costs per MIR guidelines -- we are making huge
concessions for the juju and lxd teams already, can someone take a look
at this ftbfs and report
Fixed version of golang-x-text uploaded to wily (fresh snapshot).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb, gccgo, golang
To manage notifications
Fixed version of golang-x-text uploaded to wily (fresh snapshot).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core, juju-mongodb,
"Are you saying you want to use the embedded code copy? Has anyone
looked at the testsuite issue to fix it? Embedded code copies should be
avoided at all costs per MIR guidelines -- we are making huge
concessions for the juju and lxd teams already, can someone take a look
at this ftbfs and report
@Martin Packman: can you get the fixed version of golang-x-text uploaded
to wily?
As for backport packaging for current stables, like trusty, you are free
to do whatever you want with those (following whatever archive processes
you would normally follow). Ie, juju on trusty is not officially
@Martin Packman: can you get the fixed version of golang-x-text uploaded
to wily?
As for backport packaging for current stables, like trusty, you are free
to do whatever you want with those (following whatever archive processes
you would normally follow). Ie, juju on trusty is not officially
Revised packaging for juju-core using -dev packages also uploaded (see
linked branch for full details).
** Changed in: golang-x-text (Ubuntu)
Status: Incomplete => New
** Changed in: juju-core (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
Revised packaging for juju-core using -dev packages also uploaded (see
linked branch for full details).
** Changed in: golang-x-text (Ubuntu)
Status: Incomplete => New
** Changed in: juju-core (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
@steve
"Per comment #67, the Foundations team is assuming responsibility for
the maintenance of the golang toolchain, and will work with the juju
team to ensure this is properly resourced."
no, comment #67 doesn't say this. It only talks about adoption of shared
library support and golang 1.6.
@steve
"Per comment #67, the Foundations team is assuming responsibility for
the maintenance of the golang toolchain, and will work with the juju
team to ensure this is properly resourced."
no, comment #67 doesn't say this. It only talks about adoption of shared
library support and golang 1.6.
Martin Packman [2015-10-16 22:45 -]:
> > * dep8 question (comments 86, 93, 99, 100, 101, 117)
> > - pitti's comment in #99 needs to be done. It could be done as an SRU. If
> > that is the approach, please file a bug on this and comment here
>
> I would appreciate if someone who has a clear
Martin Packman [2015-10-16 22:45 -]:
> > * dep8 question (comments 86, 93, 99, 100, 101, 117)
> > - pitti's comment in #99 needs to be done. It could be done as an SRU. If
> > that is the approach, please file a bug on this and comment here
>
> I would appreciate if someone who has a clear
Per comment#128, marking golang-go.crypto Fix Committed.
** Changed in: golang-go.crypto (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
"We have manually tested the packaging change, but it is not yet
included in our automated testing and release process. We have work in
progress to break out our series-independent packaging branch. That
said, the merge should not be considered blocked on our verification."
IIUC, this means that
"This package is not a dependency of juju. It's used by
golang.org/x/net/html/charset only, so is just pulled in as a side
effect of taking the debian package. My preference would be to drop the
juju packaging dependency on golang-go.net-dev for 1.24 instead."
Are you saying you want to use the
Per comment #128, marking golang-gocheck and golang-goyaml as 'Won't
Fix'. Go ahead and use the embedded copy for 15.10 but please ensure the
transition for these is completed for 16.04.
** Changed in: golang-gocheck (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: golang-goyaml
"This package is not a dependency of juju. It's used by
golang.org/x/net/html/charset only, so is just pulled in as a side
effect of taking the debian package. My preference would be to drop the
juju packaging dependency on golang-go.net-dev for 1.24 instead."
Are you saying you want to use the
Per comment #128, marking golang-gocheck and golang-goyaml as 'Won't
Fix'. Go ahead and use the embedded copy for 15.10 but please ensure the
transition for these is completed for 16.04.
** Changed in: golang-gocheck (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: golang-goyaml
"I would appreciate if someone who has a clear understanding for the
work pitti is requesting (such as pitti himself) could file the bug and
subscribe me. We'll happily update our packaging to use any such new
mechanism if it's provided."
I'll see if I can find someone to help you.
--
You
"I would appreciate if someone who has a clear understanding for the
work pitti is requesting (such as pitti himself) could file the bug and
subscribe me. We'll happily update our packaging to use any such new
mechanism if it's provided."
I'll see if I can find someone to help you.
--
You
"We have manually tested the packaging change, but it is not yet
included in our automated testing and release process. We have work in
progress to break out our series-independent packaging branch. That
said, the merge should not be considered blocked on our verification."
IIUC, this means that
Per comment#128, marking golang-go.crypto Fix Committed.
** Changed in: golang-go.crypto (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Actually, golang-go.crypto needs a bug subscriber. Marking incomplete.
Once that is done, this can be moved back to Fix Committed.
** Changed in: golang-go.crypto (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server
Actually, golang-go.crypto needs a bug subscriber. Marking incomplete.
Once that is done, this can be moved back to Fix Committed.
** Changed in: golang-go.crypto (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@doko
"I'm still sceptical about how to track third party libaries, i.e. if
they are included as a dependency, or built form the vendorized
copies. dh-golang tries to do that, and sets the "Built-Using"
attribute for the binary packages. If juju-core doesn't want, or cannot use
dh-golang, that
Based on Steve's comment in 118, I'm marking golang as Fix Committed.
** Changed in: golang (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
@slangasek: I agree on your point regarding juju-mongodb. It is fine for
support and I filed bug 1506989 for perftools and bug 1506990 for
architectures.
Between that, the security team ACK and doko's review, marking as Fix
Committed.
** Changed in: juju-mongodb (Ubuntu)
Status: New =>
@slangasek: I agree on your point regarding juju-mongodb. It is fine for
support and I filed bug 1506989 for perftools and bug 1506990 for
architectures.
Between that, the security team ACK and doko's review, marking as Fix
Committed.
** Changed in: juju-mongodb (Ubuntu)
Status: New =>
@doko:
"While not required, it is good to see that shared library support is
being worked on, and targeted for the upcoming 1.6. release." It is only not
required for 15.10, it is a condition of this MIR (that the juju and
foundations teams already agreed to) that we gain shared library support
> Having seen these past issues, and issues with another not well
> maintained language stack in main for the last two years (ruby), I'm
> asking for explicit confirmation that the teams who are supposed to
> maintain golang do have the required resources to do so. This will
> not only include the
> Having seen these past issues, and issues with another not well
> maintained language stack in main for the last two years (ruby), I'm
> asking for explicit confirmation that the teams who are supposed to
> maintain golang do have the required resources to do so. This will
> not only include the
> golang 1.5 is now built on arm64 and ppc64el, however juju-core
> is built using gccgo. Is there a reason for it?
The reason for this is that the package is being backported directly to
trusty, under the juju Stable Release Exception for SRUs. Since there
is not a compatible version of golang
Ok, this is a very complicated MIR with so many comments it is difficult
to track. I went through the bug and came up with the following list of
remaining items. If I missed something, please comment. Hopefully, no
one has to look before this comment on if everything is done. :)
* security team
I see this is assigned to the security team. I already gave our ACK.
Based on doko's comments, marking Incomplete.
** Changed in: juju-mongodb (Ubuntu)
Status: New => Incomplete
** Changed in: juju-mongodb (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
I see this is assigned to the security team. I already gave our ACK.
Based on doko's comments, marking Incomplete.
** Changed in: juju-mongodb (Ubuntu)
Status: New => Incomplete
** Changed in: juju-mongodb (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
Ok, this is a very complicated MIR with so many comments it is difficult
to track. I went through the bug and came up with the following list of
remaining items. If I missed something, please comment. Hopefully, no
one has to look before this comment on if everything is done. :)
* security team
Regarding the golang-juju-loggo rename, I think it is too late and a
minor issue. I filed bug 1506993 so this can happen next cycle. As such,
marking as Fix Committed.
** Changed in: golang-juju-loggo (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification
@doko
"I'm still sceptical about how to track third party libaries, i.e. if
they are included as a dependency, or built form the vendorized
copies. dh-golang tries to do that, and sets the "Built-Using"
attribute for the binary packages. If juju-core doesn't want, or cannot use
dh-golang, that
Based on Steve's comment in 118, I'm marking golang as Fix Committed.
** Changed in: golang (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
golang-go-dbus only ships a dev package with source code so does not
need Built-Using (I updated the MIRteam wiki page to calrify this).
Based on mterry's comments, golang-go-dbus is ok.
** Changed in: golang-go-dbus (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug
golang-go-dbus only ships a dev package with source code so does not
need Built-Using (I updated the MIRteam wiki page to calrify this).
Based on mterry's comments, golang-go-dbus is ok.
** Changed in: golang-go-dbus (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug
"- debian/control should have Built-Using: ${misc:Built-Using} on the
golang-github-bmizerany-assert-dev package"
This isn't needed for -dev packages. Marking Fix Committed.
** Changed in: golang-github-bmizerany-assert (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this
golang-go.crypto:
- builds fine on wily and pulls in no new MIR dependencies not listed in this
bug
- has a testsuite that is run as part of the build
- Ubuntu does not carry a delta
- no watch file
- update history in Debian is sporadic
- lintian clean (one override that is ok)
- git snapshot
golang-go.crypto:
- builds fine on wily and pulls in no new MIR dependencies not listed in this
bug
- has a testsuite that is run as part of the build
- Ubuntu does not carry a delta
- no watch file
- update history in Debian is sporadic
- lintian clean (one override that is ok)
- git snapshot
"- debian/control should have Built-Using: ${misc:Built-Using} on the
golang-github-bmizerany-assert-dev package"
This isn't needed for -dev packages. Marking Fix Committed.
** Changed in: golang-github-bmizerany-assert (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this
@mterry,
I agree with doko and slangasek that we should block migration if APIs
fail and I particularly like pitti's comment in 99.
Also, you said: "I get that you're saying it's good because we don't
have to waste security-update-time fixing reverse-depends." The upstream
Go community as a
@mterry,
I agree with doko and slangasek that we should block migration if APIs
fail and I particularly like pitti's comment in 99.
Also, you said: "I get that you're saying it's good because we don't
have to waste security-update-time fixing reverse-depends." The upstream
Go community as a
@doko:
"While not required, it is good to see that shared library support is
being worked on, and targeted for the upcoming 1.6. release." It is only not
required for 15.10, it is a condition of this MIR (that the juju and
foundations teams already agreed to) that we gain shared library support
"* security team commitments: develop a process for the list of packages
to notify the juju team on when there is a security update. This is not
a precondition of this MIR, but a request of the juju team"
FYI, we have this list and have the tooling update in our backlog.
--
You received this
$ change-override -c main -S golang-check.v1
Override component to main
golang-check.v1 0.0+git20150729.11d3bc7-1 in wily: universe/devel -> main
golang-check.v1-dev 0.0+git20150729.11d3bc7-1 in wily amd64:
universe/devel/extra/100% -> main
golang-check.v1-dev 0.0+git20150729.11d3bc7-1 in wily
"* security team commitments: develop a process for the list of packages
to notify the juju team on when there is a security update. This is not
a precondition of this MIR, but a request of the juju team"
FYI, we have this list and have the tooling update in our backlog.
--
You received this
$ change-override -c main -S golang-check.v1
Override component to main
golang-check.v1 0.0+git20150729.11d3bc7-1 in wily: universe/devel -> main
golang-check.v1-dev 0.0+git20150729.11d3bc7-1 in wily amd64:
universe/devel/extra/100% -> main
golang-check.v1-dev 0.0+git20150729.11d3bc7-1 in wily
golang promoted.
$ change-override -c main -S golang
Override component to main
golang 2:1.5.1-0ubuntu2 in wily: universe/devel -> main
golang 2:1.5.1-0ubuntu2 in wily amd64: universe/devel/optional/100% -> main
golang 2:1.5.1-0ubuntu2 in wily arm64: universe/devel/optional/100% -> main
golang
golang promoted.
$ change-override -c main -S golang
Override component to main
golang 2:1.5.1-0ubuntu2 in wily: universe/devel -> main
golang 2:1.5.1-0ubuntu2 in wily amd64: universe/devel/optional/100% -> main
golang 2:1.5.1-0ubuntu2 in wily arm64: universe/devel/optional/100% -> main
golang
golang:
The packaging of the golang package looks reasonable well, it is based
on the the Debian packaging. In Ubuntu the package suffered regular
maintenance up to and beyond the 15.04 release (vivid). It's good to
see another attempt to maintain this package.
While not required, it is good
juju-core:
Others already commented on the code, and finally approved with some
comments.
I'm still sceptical about how to track third party libaries, i.e. if
they are included as a dependency, or built form the vendorized
copies. dh-golang tries to do that, and sets the "Built-Using"
attribute
golang:
The packaging of the golang package looks reasonable well, it is based
on the the Debian packaging. In Ubuntu the package suffered regular
maintenance up to and beyond the 15.04 release (vivid). It's good to
see another attempt to maintain this package.
While not required, it is good
juju-core:
Others already commented on the code, and finally approved with some
comments.
I'm still sceptical about how to track third party libaries, i.e. if
they are included as a dependency, or built form the vendorized
copies. dh-golang tries to do that, and sets the "Built-Using"
attribute
golang 1.5 is now built on arm64 and ppc64el, however juju-core is built
using gccgo. Is there a reason for it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to golang-github-bmizerany-pat in
Ubuntu.
golang 1.5 is now built on arm64 and ppc64el, however juju-core is built
using gccgo. Is there a reason for it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267393
Title:
[MIR] juju-core,
juju-mongodb has security team ACK so long as the builds use --disable-
scripting in perpetuity.
I verified the wily version is correctly using --disable-scripting in
debian/rules (if I build without '--disable-scripting', I see
src/third_party/v8 being built and build with --disable-scripting, I
juju-mongodb:
packaging bits only, the security team will follow-up with a code
review.
- the packaging is a copy of the mongodb package, however it looks
like the packaging itself isn't merged / updated where needed.
This problem is shared with the mongodb package in Ubuntu.
-
juju-mongodb:
packaging bits only, the security team will follow-up with a code
review.
- the packaging is a copy of the mongodb package, however it looks
like the packaging itself isn't merged / updated where needed.
This problem is shared with the mongodb package in Ubuntu.
-
juju-mongodb has security team ACK so long as the builds use --disable-
scripting in perpetuity.
I verified the wily version is correctly using --disable-scripting in
debian/rules (if I build without '--disable-scripting', I see
src/third_party/v8 being built and build with --disable-scripting, I
1 - 100 of 215 matches
Mail list logo
