Comments (3)
So, you basically just get tell 'git bloom-import-upstream' to look on the fuerte-devel branch when importing and pass fuerte to git bloom-release rather than groovy and that's it.
I just finished some preliminary documentation for this: https://github.com/ros/bloom/blob/master/doc/index.rst#releasing-for-fuerte
I think that should work for now, I hope to have 0.2 of bloom out by the end of the week which will be the final version for groovy (hopefully).
Let me know if you run into other problems.
from bloom.
Pretty sure that my change to bloom.conf would have the same effect as the "--upstream-devel" option, but I'll do another patch release (into both groovy and fuerte) later today and report on any funkiness I encounter.
from bloom.
It does, the '--upstream-devel' option is just a one time override, useful because most of the time you release from groovy-devel but infrequently you want to release from fuerte-devel.
There will be a warning that the version you are importing is older than the previously imported version, but you can just ignore that, it is just something to prevent accidental release of the wrong version.
Definitely let me know if you have any trouble.
from bloom.
Related Issues (20)
- Generate machine-readable `debian/copyright` file HOT 7
- Generate a compliant distribution copyright metadata HOT 4
- Bloom allows inconsistent distro configuration
- Platform generators being run for removed packages.
- I want to use bloom get a release ros package but i meet some problem
- bloom-release opens PR to rosdistro with old branch name HOT 1
- Cannot use `setup.py develop` on setuptools 59.6.0
- debian generator always uses Architecture: any HOT 1
- Non-Interactive Bloom HOT 4
- python3-bloom depends on both python3-rosdep2 and python3-rosdep HOT 5
- Move bloom configuration details from wiki to bloom ReadTheDocs
- Failed to debianize a ros2 humble pacakge HOT 1
- PkgResourcesDeprecationWarning: is an invalid version and will not be supported in a future release HOT 2
- Improvement Idea: Mark Packages as Deprecated
- 'execute_command' failed to call 'git mv rpm/template.spec rpm/ros-rolling-<package>.spec' which had a return code (128): HOT 4
- Dropping support for non-git repository types (svn, hg, etc.) HOT 6
- How to delete a certain patch from a release repo ? HOT 2
- A command line workflow for adding just source/doc entries to rosdistro without a bloom release.
- ament_cmake binarydeb job cannot find own package for tests
- support meson HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bloom.