Certainly you can understand that a bug report on a random package is
not the place to put in question a process as critical as stable release
updates.
I understand the upstream Glom developers are responsible enough to do
high quality stable releases, nevertheless the current SRU process
I didn't find the first version number of Glom where this bug is fixed
so I grabbed the latest 1.6 release (1.6.6 currently) and compared to
the one in gutsy (1.6.0).
The diff exposes:
1) changes in the build rules:
-SUBDIRS = po glom docs macros examples xslt icons
+SUBDIRS = po glom macros
Thanks, but sorry, I'm not prepared to have a mutant version of Glom in
Ubuntu when there's a perfectly good stable release. Nobody's patch
review of the source code will be as good as the general testing of a
real release. I'm also not prepared to deal with multiple conflicting
patches (or the
Yes, the version in Hardy fixes this issue (it has Glom 1.6.6) though
Hardy's version is still old (Glom 1.6.8 is the latest version, with
more bug fixes).
Also, could you please integrate this bug as per
https://wiki.ubuntu.com/StableReleaseUpdates, section Propose ? This will
help us a lot
Sorry for mistakenly nominating for release for Hardy. I can't remove
that now.
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It was recently updated, information required is now under Procedure.
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The motu-sru team needs the information mentioned at
https://wiki.ubuntu.com/StableReleaseUpdates#head-
a7a957d3d691c2754ba24e5085481107ed703b49
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received this bug notification because you are a member of Ubuntu
Bugs, which is
OK, so:
Check that the bug is fixed in the current development release, and
its bug report task is Fix released.
Already done.
Use Nominate for release to mark the bug as an SRU candidate for the
appropriate Ubuntu releases (e. g. the current LTS and latest stable
release),
then
** Changed in: glom (Ubuntu)
Status: Fix Committed = Incomplete
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Is version in Hardy fixed?
Also, could you please integrate this bug as per
https://wiki.ubuntu.com/StableReleaseUpdates, section Propose ? This
will help us a lot to review your request. Thanks!
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received this bug
Is it possible to isolate a patch to fix this issue?
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Theoretically yes, but there are other issues fixed too, and a released
tarball is generally going to be more reliable and tested than a patch.
This is the stable branch of Glom, not some bundle of random changes.
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received
** Changed in: glom (Ubuntu)
Status: New = Fix Committed
--
Can't change field types
https://bugs.launchpad.net/bugs/186869
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
13 matches
Mail list logo
