Bug#779910: ITP: docker-compose -- Tool to define and run complex applications with Docker
Package: wnpp Severity: wishlist Owner: "ChangZhuo Chen (陳昌倬)" * Package name: docker-compose Version : 1.1.0 Upstream Author : Docker, Inc. * URL : https://github.com/docker/compose * License : Apache 2.0 Programming Lang: Python Description : Tool to define and run complex applications with Docker Compose is a tool for defining and running complex applications with Docker. With Compose, you define a multi-container application in a single file, then spin your application up in a single command which does everything that needs to be done to get it running. -- ChangZhuo Chen (陳昌倬) http://czchen.info/ Key fingerprint = EC9F 905D 866D BE46 A896 C827 BE0C 9242 03F4 552D signature.asc Description: Digital signature
CUT rolling release debian
Hello, I was exited when I heard couple of years ago about rolling release debian - CUT. But there are not news on this topic anywhere ... is this idea still living? best regards mira
Bug#779923: ITP: libosmium -- Fast and flexible C++ library for working with OpenStreetMap data
Package: wnpp Severity: wishlist Owner: Bas Couwenberg * Package name: libosmium Version : 0.0~20150303-f074d94 Upstream Author : Osmium Developers * URL : http://osmcode.org/libosmium/ * License : BSL-1.0 Programming Lang: FIXME Description : Fast and flexible C++ library for working with OpenStreetMap data The Osmium Library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. Osmium is a header-only library, so there is nothing to compile to build it. Just include the header files you need. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium, osmium-contrib & osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306132802.23353.5689.report...@osiris.linuxminded.xs4all.nl
Bug#779927: ITP: node-osmium -- Osmium library Node.js bindings
Package: wnpp Severity: wishlist Owner: Bas Couwenberg * Package name: node-osmium Version : 0.0~20150303-f074d94 Upstream Author : Osmium Developers * URL : http://osmcode.org/node-osmium/ * License : BSL-1.0 Programming Lang: JavaScript Description : Osmium library Node.js bindings The osmium module for Node.js allows you to access some of the features of the Osmium Library from Javascript code. The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib & osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306140517.28696.49658.report...@osiris.linuxminded.xs4all.nl
Re: CUT rolling release debian
On 03/06/2015 06:12 AM, Jaromír Mikeš wrote: Hello, I was exited when I heard couple of years ago about rolling release debian - CUT. But there are not news on this topic anywhere ... is this idea still living? best regards mira Hello. This isn't a direct answer to your question about CUT, but might be of some help. I've been using Debian testing as a kind of rolling release since Lenny on my four most important systems. (I just use "testing" in place of the code word -- lenny, squeeze, wheezy, jessie, etc. --in /etc/apt/sources.list.) On rare occasions I've had to scramble for a few minutes to regain lost functions when a package upgrade has resulted in malfunction of one part of the system or another, but none of the systems has ever been down-and-out for more than the few minutes it takes to find out what's wrong and reconfigure to fix it. This has even been the case when it comes time for the distro upgrade that happens when testing becomes the new stable. I'd suggest that it's best to upgrade a system configured in this manner daily. This makes the changes more incremental instead of sweeping. Longer periods between upgrades might make troubleshooting a new issue pretty tough to do since you'd have a lot more package changes to sort through to find a culprit. Reading the development and announcement lists is very helpful in knowing what to expect. And using apt-listchanges and apt-listbugs along with aptitude's interactive TUI during each daily upgrade has made the upgrading and troubleshooting process very logical and easy to do, in my experience. Obviously, during a freeze (like the one for Jessie now) you see far fewer package upgrades which are much less likely to cause functional issues. The braver souls run Sid / experimental as a kind of rolling release. That, I think, requires quite a bit more savvy in the use of techniques like pinning and other manipulations of apt's configuration. But it provides a more consistent access to later versions of all of the software packages and their new features. So, maybe you can set up your own personal rolling release? It is more work on a routine basis that running stable, but I've enjoyed doing it. Good luck! JP -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54f9b524.1090...@comcast.net
Bug#779932: ITP: pyosmium -- Osmium library bindings for Python
Package: wnpp Severity: wishlist Owner: Bas Couwenberg * Package name: pyosmium Version : 0.0~20150204-298c708 Upstream Author : Osmium Developers * URL : http://osmcode.org/pyosmium/ * License : BSD-2-Clause Programming Lang: Python Description : Osmium library bindings for Python The PyOsmium module allows you to access some of the features of the Osmium library from Python code. The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib & osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306143345.32202.83694.report...@osiris.linuxminded.xs4all.nl
Bug#779938: ITP: osmium-tool -- Command line tool for working with OpenStreetMap data
Package: wnpp Severity: wishlist Owner: Bas Couwenberg * Package name: osmium-tool Version : 0.0~20150306-4ef5dd5 Upstream Author : Osmium Developers * URL : http://osmcode.org/osmium-tool/ * License : GPL-3+ Programming Lang: C++ Description : Command line tool for working with OpenStreetMap data Osmium Tool is a multipurpose command line tool based on the Osmium library. With the Osmium Tool you currently can: * Get information about an OSM file * Convert OSM files from one format into another (supports all XML and PBF formats) * Merge and apply change files to an OSM file (with or without history) * Extract data from OSM history files for a given point in time or a time range The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib & osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306151729.6522.39965.report...@osiris.linuxminded.xs4all.nl
Bug#779942: ITP: osmium-contrib -- Various programs showing what you can do with the Osmium library
Package: wnpp Severity: wishlist Owner: Bas Couwenberg * Package name: osmium-contrib Version : 0.0~20150306-0c4f263 Upstream Author : Osmium Developers * URL : http://osmcode.org/osmium-contrib/ * License : public-domain Programming Lang: C++ Description : Various programs showing what you can do with the Osmium library Osmium Contrib contains various programs showing what you can do with the Osmium library. The osmium-contrib repository collects little programs that use the Osmium library in various ways. These programs can be useful in their own right, but they also provide nice examples for developers who want to learn about the features of the Osmium library. Currently the following programs are available: * amenity_list - Print list of amenities in OSM file * export_to_wkt - Write out node, way, and area geometries as WKT * mapolution- Show evolution of OSM map * node_density - Create image showing OSM node density * pub_names - Extract names of pubs from OSM file * road_length - Calculate length of highways from an OSM file The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib & osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306155338.11234.4989.report...@osiris.linuxminded.xs4all.nl
Bug#779944: ITP: osmcoastline -- Extract coastline data from OpenStreetMap planet file
Package: wnpp Severity: wishlist Owner: Bas Couwenberg * Package name: osmcoastline Version : 0.0~20150306-1f2b90a Upstream Author : Osmium Developers * URL : http://osmcode.org/osmcoastline/ * License : GPL-3+ Programming Lang: C++ Description : Extract coastline data from OpenStreetMap planet file OSMCoastline extracts the coastline from an OSM planet file and assembles all the pieces into polygons for use in map renderers etc. OSMCoastline relies on the Osmium library for its OpenStreetMap data handling. The Osmium library has extensive support for all types of OSM entities: nodes, ways, relations, and changesets. It allows reading from and writing to OSM files in XML and PBF formats, including change files and full history files. Osmium can store OSM data in memory and on disk in various formats and using various indexes. Its easy to use handler interface allows you to quickly write data filtering and conversion functions. Osmium can create WKT, WKB, OGR, GEOS and GeoJSON geometries for easy conversion into many GIS formats and it can assemble multipolygons from ways and relations. This package is part of the new Osmium family superseding the existing osmium source package. The new Osmium family consists of libosmium, node-osmium, pyosmium, osmium-tool, osmium-contrib & osmcoastline. The packages for the Osmium family will be maintained in the Debian GIS team. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306160838.13299.20535.report...@osiris.linuxminded.xs4all.nl
Re: CUT rolling release debian
2015-03-06 15:09 GMT+01:00 Jape Person : > On 03/06/2015 06:12 AM, Jaromír Mikeš wrote: > >> Hello, >> >> I was exited when I heard couple of years ago about rolling release debian >> - CUT. >> But there are not news on this topic anywhere ... is this idea still >> living? >> > > This isn't a direct answer to your question about CUT, but might be of > some help. > I've been using Debian testing as a kind of rolling release since Lenny on > my four most important systems > That's what I am happily doing already couple of years ;) Point of view of debian maintainer ;) I am DM and I am caring about +/- 100 small packages ... during a freeze time I shouldn't upload new upstream releases to unstable. And as DM I can't upload to experimental. So there is waiting quite a lot of work for me when new debian is released. Situation is even worse if your new version of package depends on new upstream version of package maintained by somebody else ... Everybody doing the same ... holding new releases. >From time to time (in freeze time) I am getting emails from upstreams if I am still maintaining their package ... because they released month ago and I still didn't update. Sometimes in freeze time I am getting emails from Ubuntu users which wants to have new upstream version in upcoming Ubuntu release. And I sometimes hear opinion from upstreams (but not only them) that debian shipping old releases and is slow on updating and thus not best for users which needs fresh upstream releases. So that's why I think CUT - rolling release debian would be great improvement for "certain users" probably desktop users and maintainers too. best regards mira
Re: CUT rolling release debian
And as DM I can't upload to experimental. Sometimes in freeze time I am getting emails from Ubuntu users which wants to have new upstream version in upcoming Ubuntu release. DMs can upload to experimental, and Ubuntu will sync from there if you ask them to: see e.g. https://tracker.debian.org/pkg/flightgear -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54fa2818.3010...@zoho.com
Re: CUT rolling release debian BUT a cautionary comment
On 20150306_0909-0500, Jape Person wrote: > On 03/06/2015 06:12 AM, Jaromír Mikeš wrote: > >Hello, > > > >I was exited when I heard couple of years ago about rolling release debian > >- CUT. > >But there are not news on this topic anywhere ... is this idea still living? > > > >best regards > > > >mira > > > > Hello. > > This isn't a direct answer to your question about CUT, but might be of some > help. > > I've been using Debian testing as a kind of rolling release since Lenny on > my four most important systems. (I just use "testing" in place of the code > word -- lenny, squeeze, wheezy, jessie, etc. --in /etc/apt/sources.list.) > > On rare occasions I've had to scramble for a few minutes to regain lost > functions when a package upgrade has resulted in malfunction of one part of > the system or another, but none of the systems has ever been down-and-out > for more than the few minutes it takes to find out what's wrong and > reconfigure to fix it. This has even been the case when it comes time for > the distro upgrade that happens when testing becomes the new stable. > > I'd suggest that it's best to upgrade a system configured in this manner > daily. This makes the changes more incremental instead of sweeping. Longer > periods between upgrades might make troubleshooting a new issue pretty tough > to do since you'd have a lot more package changes to sort through to find a > culprit. > > Reading the development and announcement lists is very helpful in knowing > what to expect. And using apt-listchanges and apt-listbugs along with > aptitude's interactive TUI during each daily upgrade has made the upgrading > and troubleshooting process very logical and easy to do, in my experience. > > Obviously, during a freeze (like the one for Jessie now) you see far fewer > package upgrades which are much less likely to cause functional issues. > > The braver souls run Sid / experimental as a kind of rolling release. That, > I think, requires quite a bit more savvy in the use of techniques like > pinning and other manipulations of apt's configuration. But it provides a > more consistent access to later versions of all of the software packages and > their new features. > > So, maybe you can set up your own personal rolling release? It is more work > on a routine basis that running stable, but I've enjoyed doing it. When things are 'normal', testing actually *is* a rolling release, except that Debian people like to use words to mean what they actually mean and not what some over enthusiastic booster wishes. > > Good luck! My comment to OP: I've been using Debian since Potato. I love it, but you should have at least two computers running Debian, and be able to spend a few hours or days with one of them non-functional, for the following reason: After a release of a new stable, i.e. a distribution baring a code name, such as Woody, or Jessie, the pre-release freeze on non-release-critical packages is un-frozen and a flood of package updates, etc. arrive in 'testing'. IMHO, one should avoid doing upgrades just to keep uptodate. Its best to wait for the flood to subside. But how will you know? And how long can you wait with your only computer in a non-bootable state? If you know about this, which might not be the case, be warned and have a plan. With only one computer, and it broken, it is hard to get help from this list. It might be a disaster. OTOH, it might be a good excuse to rush out and buy newer, fancier computer. ;-) -- Paul E Condon pecon...@mesanetworks.net -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306222632.ga9...@big.lan.gnu
Re: CUT rolling release debian BUT a cautionary comment
Paul E Condon writes: I've been using Debian since Potato. So have I. > I love it, but you should have at least two computers running Debian, > and be able to spend a few hours or days with one of them > non-functional I've never had that problem. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/871tl1d92q@thumper.dhh.gt.org
Re: CUT rolling release debian BUT a cautionary comment
On Fri, Mar 06, 2015 at 03:26:32PM -0700, Paul E Condon wrote: > you should have at least two computers running Debian, and be able to > spend a few hours or days with one of them non-functional, for the > following reason: Or, use btrfs. Put your / onto a subvolume named sys-current, and have the following cronjob: # btrfs subv snap sys-current backups/sys-`date +%Y-%m-%d` Whenever shit happens, such as, say, an upload of xorg that takes two weeks for nvidia drivers to get back into a functional state, you do: # mv sys-current sys-broken && btrfs subv snap backups/sys-2015-03-07 sys-current then reboot[1]. Even if things broke so bad you can't boot, simply edit the grub entry to include subvol=backups/sys-2015-03-07 on the kernel's commandline and you're set. Such a scheme makes using unstable so much nicer that I wonder why it's not an option in the d-i. Perhaps we should discuss it[2] and implement it post-jessie? [1]. Can't delete the bad version immediately as you're using it currently. [2]. Besides separate /home (duh), you'll want to reduce the size of backups by separating out /var/cache, make sure noatime is set, etc. -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150306235631.gb32...@angband.pl
Re: CUT rolling release debian
2015-03-06 23:20 GMT+01:00 Rebecca N. Palmer : > And as DM I can't upload to experimental. >> Sometimes in freeze time I am getting emails from Ubuntu users which >> wants to have new upstream version in upcoming Ubuntu release. >> > DMs can upload to experimental, and Ubuntu will sync from there if you ask > them to: see e.g. https://tracker.debian.org/pkg/flightgear > Right DM is not allowed to upload to a suite where there's no package already. So first you need to ask some DD to upload your package to experimental for you than DM can upload too. Sorry to not be accurate ;) mira
Bug#779969: ITP: coreclr -- .NET Core Runtime
Package: wnpp Severity: wishlist Owner: Mirco Bauer * Package name: coreclr Version : git Upstream Author : Microsoft and contributors * URL : http://www.dotnetfoundation.org/netcore5 * License : MIT/X11 Programming Lang: C++, C# Description : .NET Core Runtime The .NET Core Runtime also named CoreCLR is an open source, cross-platform runtime for the Common Language Infrastructure. The runtime currently only supports on Linux the AMD64/x86_64 CPU architecture. This runtime provides an smaller alternative to the Mono runtime. The CoreCLR is not feature on par with Mono. This package will be maintained under the Debian CLI/Mono umbrella. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150307031423.14145.19047.report...@redhorse.lan.qnetp.net
Bug#779970: ITP: corefx -- .NET Core Libraries
Package: wnpp Severity: wishlist Owner: Mirco Bauer * Package name: corefx Version : git Upstream Author : Microsoft and contributors * URL : http://www.dotnetfoundation.org/netcore5 * License : MIT Programming Lang: C# Description : .NET Core Libraries The .NET Core Runtime also named CoreCLR is an open source, cross-platform runtime for the Common Language Infrastructure. The runtime currently only supports on Linux the AMD64/x86_64 CPU architecture. This package contains the libraries of the runtime. This package will be maintained under the Debian CLI/Mono umbrella. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150307033125.1764.26438.report...@redhorse.lan.qnetp.net
Re: CUT rolling release debian
On Fri, Mar 6, 2015 at 10:09 PM, Jape Person wrote: > I've been using Debian testing as a kind of rolling release since Lenny on > my four most important systems. (I just use "testing" in place of the code > word -- lenny, squeeze, wheezy, jessie, etc. --in /etc/apt/sources.list.) Some more tips on running Debian testing: http://bonedaddy.net/pabs3/log/2012/10/29/thoughts-on-debian-testing/ -- bye, pabs https://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6HGJju88=B6Y5yW38e0crfnhgzcmcAQ2P7y=LmHwk52=w...@mail.gmail.com
Re: CUT rolling release debian
On 03/06/2015 04:56 PM, Jaromír Mikeš wrote: 2015-03-06 15:09 GMT+01:00 Jape Person : On 03/06/2015 06:12 AM, Jaromír Mikeš wrote: Hello, I was exited when I heard couple of years ago about rolling release debian - CUT. But there are not news on this topic anywhere ... is this idea still living? This isn't a direct answer to your question about CUT, but might be of some help. I've been using Debian testing as a kind of rolling release since Lenny on my four most important systems That's what I am happily doing already couple of years ;) Oops! I completely misinterpreted your situation and your question. I might have understood better had I noticed that I was replying to someone on debian-devel and not on the user list. Point of view of debian maintainer ;) I am DM and I am caring about +/- 100 small packages ... during a freeze time I shouldn't upload new upstream releases to unstable. And as DM I can't upload to experimental. So there is waiting quite a lot of work for me when new debian is released. Situation is even worse if your new version of package depends on new upstream version of package maintained by somebody else ... Everybody doing the same ... holding new releases. From time to time (in freeze time) I am getting emails from upstreams if I am still maintaining their package ... because they released month ago and I still didn't update. Sometimes in freeze time I am getting emails from Ubuntu users which wants to have new upstream version in upcoming Ubuntu release. And I sometimes hear opinion from upstreams (but not only them) that debian shipping old releases and is slow on updating and thus not best for users which needs fresh upstream releases. So that's why I think CUT - rolling release debian would be great improvement for "certain users" probably desktop users and maintainers too. Very interesting. Thank you for explaining this to me. I have to agree that a concept like CUT is appealing. I'd jump on a rolling release like this immediately if it were available. Thank you again for the explanation. I'll follow the discussion with interest. Regards, JP -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54fa78db.2020...@comcast.net
