Couchbase Server

[Doc when ready] distribute couchbase-server through yum and debian package repositories

Details

  • Flagged:
    Release Note

Description

this helps us in handling dependencies that are needed for couchbase server
sdk team has already implemented this for various sdk packages.

we might have to make some changes to our packaging metadata to work with this schema

Issue Links

blocks

Task - A task that needs to be done. MB-7821 yum install couchbase-server from couchbase repo failed ( no mirrors to try )

  • Blocker - Blocks development and/or testing work, production could not run.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
duplicates

Improvement - An improvement or enhancement to an existing feature or task. MB-2299 Create signed RPM's

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Resolved - A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Karen Zeller added a comment -
Removing duplicate ticket:

http://www.couchbase.com/issues/browse/MB-7860
Show
Karen Zeller added a comment - Removing duplicate ticket: http://www.couchbase.com/issues/browse/MB-7860
Hide
Permalink
Anil Kumar added a comment -
thanks Tim, we have removed it from release notes. we will add instructions about yum/deb repo's locations/files/keys to documentation once its available. thanks!
Show
Anil Kumar added a comment - thanks Tim, we have removed it from release notes. we will add instructions about yum/deb repo's locations/files/keys to documentation once its available. thanks!
Hide
Permalink
Tim Ray added a comment -
could we either remove the note about yum/deb repo's in the release notes or get those repo locations / sample files / keys added to public pages? The only links that seem that they 'might' contain the info point to internal pages I don't have access to.
Show
Tim Ray added a comment - could we either remove the note about yum/deb repo's in the release notes or get those repo locations / sample files / keys added to public pages? The only links that seem that they 'might' contain the info point to internal pages I don't have access to.
Hide
Permalink
Anil Kumar added a comment -
Yes I'll be having discussion with Phil and will update here with details.
Show
Anil Kumar added a comment - Yes I'll be having discussion with Phil and will update here with details.
Hide
Permalink
Dipti Borkar added a comment -
Anil, can you work with Phil to see what are the next steps here?
Show
Dipti Borkar added a comment - Anil, can you work with Phil to see what are the next steps here?
Hide
Permalink
Matt Ingenthron added a comment -
Reopening, since this isn't documented that I can find. Apologies if I'm just missing it.
Show
Matt Ingenthron added a comment - Reopening, since this isn't documented that I can find. Apologies if I'm just missing it.
Hide
Permalink
Matt Ingenthron added a comment -
What are the public URLs for these repositories? This was mentioned in the release notes here:
http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-server-rn_2-0-0l.html
Show
Matt Ingenthron added a comment - What are the public URLs for these repositories? This was mentioned in the release notes here: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-server-rn_2-0-0l.html
Hide
Permalink
Karen Zeller added a comment -
Added to 2.0.1 RN as:

Fix:

We now provide Couchbase Server as a yum and Debian package
repositories.
Show
Karen Zeller added a comment - Added to 2.0.1 RN as: Fix: We now provide Couchbase Server as a yum and Debian package repositories.
Hide
Permalink
Phil Labee added a comment -
Now have DEB repo working, but another issue has come up: We need to distribute the public key so that users can install the key before running apt-get.

wiki page has been updated.
Show
Phil Labee added a comment - Now have DEB repo working, but another issue has come up: We need to distribute the public key so that users can install the key before running apt-get. wiki page has been updated.
Hide
Permalink
Jin Lim added a comment -
Please ensure that we also confirm/validate the upgrade process moving from 2.0.1 to 2.0.2. Thanks.
Show
Jin Lim added a comment - Please ensure that we also confirm/validate the upgrade process moving from 2.0.1 to 2.0.2. Thanks.
Hide
Permalink
Dipti Borkar added a comment -
Have we figured out the upgrade process moving forward. for example from 2.0.1 to 2.0.2 or 2.0.1 to 2.1 ?
Show
Dipti Borkar added a comment - Have we figured out the upgrade process moving forward. for example from 2.0.1 to 2.0.2 or 2.0.1 to 2.1 ?
Hide
Permalink
Farshid Ghods added a comment -
we should resolve this task once 2.0.1 is released .
Show
Farshid Ghods added a comment - we should resolve this task once 2.0.1 is released .
Hide
Permalink
Farshid Ghods added a comment -
Phil,
please sync up with Farshid and get instructions that Sergey and Pavel sent
Show
Farshid Ghods added a comment - Phil, please sync up with Farshid and get instructions that Sergey and Pavel sent
Hide
Permalink
Steve Yen added a comment -
back to 2.01, per bug-scrub
Show
Steve Yen added a comment - back to 2.01, per bug-scrub
Hide
Permalink
Steve Yen added a comment -
back to 2.01, per bug-scrub
Show
Steve Yen added a comment - back to 2.01, per bug-scrub
Hide
Permalink
Steve Yen added a comment -
to 2.0.2 per bug-scrub

first step is do the repositories?
Show
Steve Yen added a comment - to 2.0.2 per bug-scrub first step is do the repositories?

People

  • Assignee:
    Phil Labee
    Reporter:
    Farshid Ghods
Vote (1)
Watch (11)

Dates

  • Created:
    Updated: