[needs-packaging] liquibase

Bug #252359 reported by Maia Everett
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
New
Wishlist
Unassigned

Bug Description

A Java library required by Execute Query.
LiquiBase is an open source, DBMS-independent library for tracking, managing and applying database changes. It is built on a simple premise: All database changes (structure and data) are stored in an XML-based descriptive manner and checked into source control.

URL: http://liquibase.org/
License: GNU Lesser General Public License (LGPL)
Notes: Requires Java >= 1.5

Revision history for this message
Nathan Handler (nhandler) wrote :

Thank you for taking the time to request this package and helping to make Ubuntu better. Unfortunately you have not provided enough information for a developer to start packaging this application. Please make sure this bug meets the guidelines at [WWW] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages. An example of a complete package request is available at [WWW] https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages.

Revision history for this message
Maia Everett (linneris) wrote :

I think I have provided enough information for _myself_ to start packaging it - and the upstream website certainly provides enough information for any potential packager. Perhaps I should have assigned it to myself from the start to make the intention clear.

I don't like canned responses - they establish a sense of detachment. In the future, could you please specify, in your own words, what exactly is missing, instead of using a canned response?

Revision history for this message
Nathan Handler (nhandler) wrote :

First, you did not have yourself assigned to this bug, or the status set to 'In Progress'. There was no way for me to know that you intended to package it yourself. needs-packaging bugs (which is what this is) should be tagged with the 'needs-packaging' tag, contain a description (more than one sentence) about what the program does, mention the license that the application is distributed under, and contain any additional notes that might be important to the person who decides to package it. Most of this required information is missing, or not complete. However, since you are packaging the application, it is not really necessary to add it to the bug report.

I have no issue providing additional information about what was wrong with a bug report (which I have done above). The reason I use canned responses is that most people are able to read the canned responses, follow the links, and figure out what they need to add. Since a canned response is quick and easy to use, it allows me to reply to more bugs than I would be able to if I gave personal responses to each of them. Another reason for the canned responses is, many people post a bug, and then they forget about it. As a result, they will never even look at my response. These are some of the reasons why many bug triagers, including myself, prefer to use canned responses.

description: updated
Revision history for this message
Łukasz Stefaniak (lustefaniak) wrote :

is there any progress on this?

Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Is any progress being made on this package? The last update seems to have been in 2008.

Mattia Rizzolo (mapreri)
Changed in ubuntu:
assignee: Maia Everett (lucidfox) → nobody
status: In Progress → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.