** Changed in: pygobject (Debian)
Status: Unknown => Fix Released
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobj
This bug was fixed in the package pygobject - 2.14.2-0ubuntu2
---
pygobject (2.14.2-0ubuntu2) hardy-proposed; urgency=low
[ Colin Watson ]
* Pass PYTHON environment variable to make as well as configure, in case
timestamp skew causes make to rerun autoconf and ./config.status
Using python-gobject 2.14.2-0ubuntu2 in hardy-proposed I saw no
regressions in behavior versus python-gobject 2.14.2-0ubuntu1 in hardy-
updates while using update-manager, alacarte, quodibet, or system-
config-printer-gnome. Also, the examples in /usr/share/doc/python-
gobject/examples behave iden
** Description changed:
The version of pygobject in hardy-updates on sparc is misbuilt to supply
only a python2.5 version. This causes ubiquity to fail to build since
python-gtk2 is uninstallable (http://launchpadlibrarian.net/20576122
/buildlog_ubuntu-hardy-sparc.ubiquity_1.8.13_FAILEDTOB
NB: Package built fine on all arches in hardy-proposed.
I don't have a hardy desktop; would be nice if someone with a hardy
install would smoketest the binaries.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug n
The problem isn't present in jaunty as there's a separate patch for the
autotools update. The PYTHON= robustness change is present in Debian's
SVN, but isn't merged yet in jaunty; I think it can wait until our next
rebase on Debian, either in jaunty or jaunty+1.
** Changed in: pygobject (Ubuntu J
Please fix this in Jaunty soon, too.
** Changed in: pygobject (Ubuntu Jaunty)
Status: New => Triaged
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug notification because you are a member of Ubuntu
Desktop
Ah, thanks for the explanation. Fine for me then.
** Changed in: pygobject (Ubuntu Hardy)
Status: New => Fix Committed
** Tags added: verification-needed
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug n
It's just the opposite of a trap; it's a further safety measure. It
arranges that, *even if* an autotools update is accidentally run, then
everything will still work. The intention is not that an autotools
update *should* be run - I agree that that is often risky - but to
provide insurance in case
** Tags added: regression-update
** Tags removed: regression-updates
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject
So both of you have the firm opinion that the debian/rules behaviour
change should be done in an SRU? It seems to be a big potential trap to
me.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug notification becaus
For the record, I changed debian/rules in pygobject's packaging SVN repo
to backup/restore config.guess and .sub after patching/before
unpatching, and these files wont show up in the diff anymore.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/b
For the record, I changed debian/rules in pygobject's packaging SVN repo
to backup/restore config.guess and .sub after patching/before
unpatching, and these files wont show up in the diff anymore.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/b
So, I did workaround the autoupdate in the attached new debdiff, but be
aware that config.sub/.guess will be copied over nevertheless during the
build (see debian/rules around line 84), and a subsequent uploader will
have to workaround this manually as well.
** Attachment added: "Alternate debdiff
** Tags added: regression-updates
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in ubuntu.
--
desktop-bugs mailin
That's why I said that you can avoid it by temporarily moving
/usr/share/misc/config.{guess,sub} aside; that way you can 'debuild -S'
and it won't change those files.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received this b
RIght, it's cdbs' unconditional config.guess/.sub update mechanism; I
could hand fix the debdiff or workaround the update, but it wouldn't
represent the actual source which I'll upload as it will have to be
cleaned when building the source (I don't think you can debuild/dpkg-
buildpackage with both
config.guess and config.sub are updated automatically by debian/rules.
However, for the purposes of building a minimal change, you can avoid
this by temporarily moving /usr/share/misc/config.{guess,sub} aside.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.la
Why do we need both changes? I like Loic's approach in moving the
configure/aclocal.m4 changes to the last patch, since that will fix the
bug without introducing any other changes. I don't particularly like a
re-running of autoconf tools, since I got bitten too often by that. It
would only mean to
While I haven't tried building it myself,
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/309674/comments/4
is fine with me. Loïc, can you go ahead and upload this?
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
You received
** Attachment added: "Alternate debdiff which moves aclocal and configure
diffes to a new patch to avoid the timestamp skews; still keeps Colin's changes
as a safety net"
http://launchpadlibrarian.net/20578632/pygobject-hardy-debdiff
--
python-gobject in hardy-updates on sparc misbuilt only
I'd recommend implementing (a) as well, or also (d): patch in
AM_MAINTAINER_MODE. I'm not too confident in the effect of re-running
the autotools, even with PYTHON passed to the make which will do so.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.
** Bug watch added: Debian Bug tracker #509192
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509192
** Also affects: pygobject (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509192
Importance: Unknown
Status: Unknown
** Attachment added: "hardy-proposed patch"
This is consistently reproducible by editing the apply-patches rule in
/usr/share/cdbs/1/rules/simple-patchsys.mk and inserting a 'sleep 2'
command just before the end of the for loop.
--
python-gobject in hardy-updates on sparc misbuilt only for python2.5
https://bugs.launchpad.net/bugs/309674
Y
24 matches
Mail list logo
