This bug was fixed in the package landscape-client -
1.0.28-0ubuntu1.9.04.0
---
landscape-client (1.0.28-0ubuntu1.9.04.0) jaunty; urgency=low
* Fix minor packaging issues in last release (LP: #343954)
- Version number in landscape.VERSION is now correct
- Fixed package versi
Okay, I've prepared the branch, it's lp:~radix/landscape-
client/jaunty-1.0.28-fixed
It only changes landscape/__init__.py, landscape/setup.py, and the
debian changelog.
- This is based on the new upstream release branch with 1.0.28 in its version
numbers
- I put in all the changelog entries to
** Branch linked: lp:~radix/landscape-client/jaunty-1.0.28-fixed
--
Update landscape-client to 1.0.28
https://bugs.launchpad.net/bugs/343954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
oops, sorry, was out of date when I posted that comment. I'll prepare a
new branch based on the ubuntu-core-dev branch.
--
Update landscape-client to 1.0.28
https://bugs.launchpad.net/bugs/343954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Can you please merge the 1.0.28 release into trunk and tag it
appropriately, to fix the version number in the landscape code itself?
Please also add the changelog entries you want to see, then I can do
another upload which closes all of them.
--
Update landscape-client to 1.0.28
https://bugs.laun
I'm preparing a new package to fix these issues.
--
Update landscape-client to 1.0.28
https://bugs.launchpad.net/bugs/343954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Christopher,
sorry; I asked about this on IRC yesterday, and therve said that trunk
is basically okay, except that 1.0.28 wasn't tagged. The current ubuntu
package is a proper branch of trunk, thus applying debdiffs instead of
merging would destroy history and the whole point of revision control?
Actually, there were some problems with that upload. For some reason,
the debdiff which I crafted and attached wasn't used, and instead lp
:landscape-client trunk was used.
- The changelog entry didn't have all of the details which I included
- The version number that I specified wasn't used, whic
This bug was fixed in the package landscape-client - 1.0.28-0ubuntu1
---
landscape-client (1.0.28-0ubuntu1) jaunty; urgency=low
* New upstream release. (LP: #343954)
-- Martin PittWed, 18 Mar 2009 20:42:05
+0100
** Changed in: landscape-client (Ubuntu Jaunty)
Status: C
sponsored.
--
Update landscape-client to 1.0.28
https://bugs.launchpad.net/bugs/343954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
Since this was recently approved for SRU microrelease exceptions, and
you did a similar QA, I approve this FFE.
--
Update landscape-client to 1.0.28
https://bugs.launchpad.net/bugs/343954
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Okay, here are the Feature Freeze Exception details for the jaunty
package.
- A description of the proposed changes, with sufficient detail to
estimate their potential impact on the distribution
The description of the changes are in the ticket description. The
potential impact isn't too high bec
Here's another debdiff, from 1.0.26.1 to 1.0.28. For Jaunty.
** Summary changed:
- Update landscape-client to 1.0.27
+ Update landscape-client to 1.0.28
** Description changed:
Binary package hint: landscape-client
- 1.0.27 is currently available: https://launchpad.net/landscape-
+ 1.0.28
13 matches
Mail list logo
