Bug#880199: #880199 ITP: skopeo -- Utility performing various operations on container images and image repositories
Hi Reinhard, Dimitry, I have performed some testing of the packaged skopeo, it's looking good. Specifically I have run the following commands as root on a relatively clean bullseye running in a VM: # git clone https://salsa.debian.org/go-team/packages/skopeo.git # cd skopeo/ # apt-get install dh-golang go-md2man golang-any golang-github-containers-image-dev golang-github-containers-storage-dev golang-github-opencontainers-go-digest-dev golang-github-opencontainers-image-spec-dev golang-github-pkg-errors-dev golang-github-sirupsen-logrus-dev golang-github-stretchr-testify-dev golang-github-urfave-cli-dev golang-gopkg-check.v1-dev # wget https://github.com/containers/skopeo/archive/v0.1.35.tar.gz # mv v0.1.35.tar.gz ../skopeo_0.1.35.orig.tar.gz # dpkg-buildpackage # dpkg -i ../skopeo_0.1.35-1_amd64.deb # mkdir /etc/containers # curl https://raw.githubusercontent.com/containers/skopeo/master/default-policy.json -o /etc/containers/policy.json The result was that I could successfully run the skopeo command: # skopeo copy docker://docker.io/httpd oci:httpd:latest Getting image source signatures Copying blob 000eee12ec04 done Copying blob 32b8712d1f38 done Copying blob f1ca037d6393 done Copying blob c4bd3401259f done Copying blob 51c60bde4d46 done Copying config e8463a1665 done Writing manifest to image destination Storing signatures I looked around in the resulting httpd directory, everything seems in-order and correct. Many thanks for packaging this, I hope it's progression through the NEW queue is uneventful. -- Brian
Bug#866331: fai-server: fai-diskimage exits with 0 even when a script does not
Package: fai-server Version: 5.3.6 Severity: normal Dear Maintainer, I'm relatively new to FAI, so please close this as wontfix if it's expected behaviour. However, it's quite unexpected for me to see that fai-diskimage exits with status code 0 when a script in "scripts" fails with a non-zero status code. I can see the failure in the log output, but don't see any other way of verifying that there were no failures while building the image. Is this expected? why? Many thanks, Brian -- System Information: Debian Release: 9.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fai-server depends on: ii debootstrap 1.0.89 ii fai-client 5.3.6 ii xz-utils 5.2.2-1.2+b1 Versions of packages fai-server recommends: pn isc-dhcp-server pn libproc-daemon-perl pn nfs-kernel-server pn openbsd-inetd | inet-superserver ii openssh-client1:7.4p1-10 ii openssh-server1:7.4p1-10 pn tftpd-hpa | atftpd Versions of packages fai-server suggests: pn aptitude ii binutils 2.28-5 pn debmirror ii fai-setup-storage 5.3.6 pn grub2 pn perl-tk ii qemu-utils 1:2.8+dfsg-6 ii reprepro 5.1.1-1 pn squashfs-tools pn xorriso -- no debconf information
Bug#806785: closed by James McCoy <james...@debian.org> (Bug#806785: fixed in vim 2:7.4.963-1)
12315082 > vim_7.4.963.orig.tar.gz > 20c4627522d8a42e86f1f34009ee1bea60910e21e64923da034c032cccfaa625 165828 > vim_7.4.963-1.debian.tar.xz > Files: > f6e82ebe746361ea30b0ee62b59c2583 2925 editors optional vim_7.4.963-1.dsc > d61fcdffa0d95c6de79170bf9ec6e68c 12315082 editors optional > vim_7.4.963.orig.tar.gz > 956d64d0aa25e38e9a0c290fbcb2101f 165828 editors optional > vim_7.4.963-1.debian.tar.xz > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1 > > iQJ8BAEBCgBmBQJWaW6XXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ5MUJGQkY0RDY5NTZCRDVERjdCNzJEMjNE > RkU2OTFBRTMzMUJBM0RCAAoJEN/mka4zG6Pb7UwQALHwpnyRCasfpwbSKMJtFydN > 5vOlgjPVgZyyJ5iOHoM6wmVwXaUhtLY1BKoBz7Af25LyzveAOnyH+O8eI/Kqu1Os > 4pMy5TrtdKVYxLqo17n9gdpqWdemhbzT5GgTS3+6lEXyO9rMa4Q/pxQLjzzs+eTn > ITCd6RrSXq2yfy7O1RgY8nYZzlvs3M7yzIwYULIqCFbxFfoRyxVtWVQ4ExtGatRL > 12Ot+1vpQFclg7PVQ4gWiEXiOe5Ax/AcYHDAItAn6Up3mOJSK1LeipBaOtrOz+JP > My8Fr6tsgS/eSinbL7dG7I6zD5n0QIJCz6Jgnb46EZioRWnOdnqy1JuOI1B1GrlI > TK8jKBDSGYwRavUkk2Y7S1JEYiJlSiXRuQ/mgcicuRlKbrh5rMVcrcGcHffjc2CF > rc5TMqqPnltHcgMTzTB0YgO/ldx0bTHtNKoeXzVm02fBGZumwDflpEd3VYMuuoGo > 3uF049djI+saKdBW4FOtbjzwJ978kv8Er3oQzWAMib4ioE7heFudrGxHblIcTvVO > CkkOx1LM9g8crt6efstWzVwo37DA9LnTM+HZS+d1P76fL2ybcx/71j8b4+SJFEkB > jCPf9IKSdB6Nxw67Zm+hSIjd1gjpd9m/Y9TzsArEkvgsmoogDp06Zi6VJIRiUWW4 > 9hSYE/x/7MeExWnSZ4vv > =Afup > -END PGP SIGNATURE- > > Package: ganglia-monitor > Version: 3.6.0-6 > Severity: normal > > Dear Maintainer, > > The current initscript has 2 undesireable behaviours: > > * It fails to start if there is another gmond service running >(even though the other process uses a different configuration) > * When it stops, it also kills other, unrelated gmond services. > > My use case is that I am using multiple gmond processes on a "head" node > to collect statistics from a dynamic cluster. I am starting the other > gmond processes with a systemd unit file similar to: > > [Unit] > Description=Other gmond > > [Service] > Type=simple > User=root > PrivateTmp=true > ProtectSystem=full > ProtectHome=read-only > NoNewPrivileges=true > PrivateDevices=true > ExecStart=/usr/sbin/gmond -f -c /usr/lib/mypkg/channel-1.conf > > [Install] > WantedBy=multi-user.target > > So far it's working great except for that impolite init script... > > I can think of 3 possible solutions: > > * Add a systemd initscrit to ganglia-monitor > * Split out the gmond binary into a separate package >so it can be used separately > * Fix the existing initscript to not arbitrarily kill other processes >(possible?) > > I am willing to work on the first option if it would be acceptable. > > -- System Information: > Debian Release: 8.2 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages ganglia-monitor depends on: > ii adduser 3.113+nmu3 > ii libapr1 1.5.1-3 > ii libc62.19-18+deb8u1 > ii libconfuse0 2.7-5 > ii libexpat12.1.0-6+deb8u1 > ii libganglia1 3.6.0-6 > ii libpcre3 2:8.35-3.3 > ii zlib1g 1:1.2.8.dfsg-2+b1 > > ganglia-monitor recommends no packages. > > ganglia-monitor suggests no packages. > > -- Configuration Files: > /etc/ganglia/gmond.conf changed [not included] > /etc/init.d/ganglia-monitor changed [not included] > > -- no debconf information -- Brian Sutherland
Bug#806785: ganglia-monitor: Impolite initscript interferes with other gmond services
Package: ganglia-monitor Version: 3.6.0-6 Severity: normal Dear Maintainer, The current initscript has 2 undesireable behaviours: * It fails to start if there is another gmond service running (even though the other process uses a different configuration) * When it stops, it also kills other, unrelated gmond services. My use case is that I am using multiple gmond processes on a "head" node to collect statistics from a dynamic cluster. I am starting the other gmond processes with a systemd unit file similar to: [Unit] Description=Other gmond [Service] Type=simple User=root PrivateTmp=true ProtectSystem=full ProtectHome=read-only NoNewPrivileges=true PrivateDevices=true ExecStart=/usr/sbin/gmond -f -c /usr/lib/mypkg/channel-1.conf [Install] WantedBy=multi-user.target So far it's working great except for that impolite init script... I can think of 3 possible solutions: * Add a systemd initscrit to ganglia-monitor * Split out the gmond binary into a separate package so it can be used separately * Fix the existing initscript to not arbitrarily kill other processes (possible?) I am willing to work on the first option if it would be acceptable. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ganglia-monitor depends on: ii adduser 3.113+nmu3 ii libapr1 1.5.1-3 ii libc62.19-18+deb8u1 ii libconfuse0 2.7-5 ii libexpat12.1.0-6+deb8u1 ii libganglia1 3.6.0-6 ii libpcre3 2:8.35-3.3 ii zlib1g 1:1.2.8.dfsg-2+b1 ganglia-monitor recommends no packages. ganglia-monitor suggests no packages. -- Configuration Files: /etc/ganglia/gmond.conf changed [not included] /etc/init.d/ganglia-monitor changed [not included] -- no debconf information
Bug#779324: van.pydeb causing several FTBFS bugs - bump up to RC
On Fri, Jun 19, 2015 at 08:00:02AM -0700, Daniel Schepler wrote: severity 779324 serious thanks This bug is causing FTBFS in several source packages. As the original author of van.pydeb I would not be sad to see it be removed from Debian. The latest dh_python is an almost complete replacement and most packages could/should be converted to it. Unfortunately, my day job and 2 little tadpoles running around mean that I definitely won't get around to it for a long time to come. For example, from my pbuilder build log for zope.i18n: ... running install_egg_info Copying src/zope.i18n.egg-info to /tmp/buildd/zope.i18n-3.7.4/debian/python-zope.i18n/usr/lib/python2.7/dist-packages/zope.i18n-3.7.4.egg-info Installing /tmp/buildd/zope.i18n-3.7.4/debian/python-zope.i18n/usr/lib/python2.7/dist-packages/zope.i18n-3.7.4-nspkg.pth running install_scripts dh_pydeb pydeb: Working on source package zope.i18n pydeb: Working on python distribution zope.i18n Traceback (most recent call last): File /usr/bin/van-pydeb, line 9, in module load_entry_point('van.pydeb==1.3.3', 'console_scripts', 'van-pydeb')() File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 552, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2672, in load_entry_point return ep.load() File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2345, in load return self.resolve() File /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py, line 2351, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File /usr/lib/python2.7/dist-packages/van/pydeb/__init__.py, line 20, in module from pkg_resources import component_re # Is this a public interface? ImportError: cannot import name component_re pydeb: Working on binary package ERROR: Expected binary package in debian/control but did not find it. debian/rules:6: recipe for target 'binary' failed make: *** [binary] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2 -- Daniel Schepler ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753404: zope.security: Port python-zope.security-untrustedpython from Ubuntu
On Tue, Jul 01, 2014 at 10:56:05AM -0400, Barry Warsaw wrote: Source: zope.security Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, In Ubuntu, the zope.security package has the following delta. zope.security (3.8.3-2ubuntu1) precise; urgency=low * Merge from Debian. Remaining changes: - Add metapackage for untrustedpython extra -- Gediminas Paulauskas mene...@pov.lt Mon, 14 Nov 2011 22:29:48 +0200 However, the package is quite old in Ubuntu and I am going to sync it up with the latest Debian version, which will add Python 3 support. I'm not entirely sure what the untrustedpython metapackage is for, but I'm filing this bug to keep track of this, since Gediminas must have had a good reason for adding it. However, I do not want to hold up syncing and promotion of the new version for adding this new binary package and having it be held up in the NEW queue, at least not right now. The reason it was not added in Debian is because it requires the RestrictedPython package: https://pypi.python.org/pypi/RestrictedPython That has security implications, and no-one wanted to take responsibility for that. Here's the debian/control bits: Package: python-zope.security-untrustedpython Architecture: all Depends: python-zope.security (= ${binary:Version}), ${pydeb:Depends}, ${misc:Depends} Description: Zope Security Framework - Untrusted interpreter support Provides support for compiling untrusted code - -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTsswCAAoJEBJutWOnSwa/yZsP/0CxKYGhpCho6c2VvCOnMORz xP3CTcRq0jACNKF1HSKcpuPKGveURdJwJOMlj+orvlIXrxpZDsp+ZxnyrZLRwcT2 zFh7K9TVIcTlymumt0GiLpD16CN69D0S4KyDhV9HmNWlggynvfLKbUz/2rc35J1t qpGvGv8986M670av32NSZuwVNhzcSJLHhnKoD/pB63LB7fKbASMJR9pCGcalpr0a VPKDb3zkcxsbILrYJJHfon3eTjN4G3+egVdo6XLPlO4Dnx4QoBsPRYEEIoALJLJQ F7114EMsXzNL42AdWmU7p+UwVQeV/SH/nzXmIfDIqaTFGdGrOyQvr5P1hssdqycW fhha1IuF5DhVcLQy1gNhfwnAJdcV2+8w9MuxQC7MU/5pVjLOnE2v92V8SykrEqX+ rW9hBh1ENZ9OL8C+GzA+HBp05Gyzgoz6B1iHQCSxi83JtLYMK40AZ5bz4VcrCs0v ATk7TGfvF2vM7jyIB7S6ajycFHbJNFERnDgXlV4zpwJuDnAYPJK5leFe/gtmDBW3 ZoX67Sg6tEDD1tt5L+ctZbp81SgQQwWuhz7EviGQb15DlH/eURb0yZtHiNf2PoYy oRmZiRAXULdnpDheos/2cfWgHPuixUTz2/VTSlBIUr+IhiIB7rxzPPoU0aaNA6Fx tghmXej6Zn7hamefSig2 =PWFq -END PGP SIGNATURE- ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666914: /usr/lib/python2.7/dist-packages/zope/__init__.py:3: UserWarning: Module dap was already imported from None
The code which actually prints the warning is pkg_resources, which is in python-pkg-resources. There's a lot of code out there importing pkg_resources, removing the import from zope/__init__.py isn't going to help much (and will break some things). There's already a bug on python-pkg-resources about this`: #473584 On Mon, Apr 02, 2012 at 03:35:15PM +0200, Laurent Bonnaud wrote: Package: python-zope.interface Version: 3.6.1-1 Severity: normal Hi, this package is the cause of error messages in unrelated packages, for instance: $ reportbug /usr/lib/python2.7/dist-packages/zope/__init__.py:3: UserWarning: Module dap was already imported from None, but /usr/lib/python2.7/dist-packages is being added to sys.path import pkg_resources -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-rt-686-pae (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-zope.interface depends on: ii libc6 2.13-27 ii python2.7.2-10 ii python-pkg-resources 0.6.24-1 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-1 python-zope.interface recommends no packages. python-zope.interface suggests no packages. -- no debconf information ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616650: Info received (2011h is available)
On Sun, Sep 18, 2011 at 12:59:53AM -0400, Yaroslav Halchenko wrote: On Sat, 17 Sep 2011, Arnaud Fontaine wrote: While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). as far as I see it -- there is no code change between, only that 2011g more up-to-date and includes more zones (which is a good thing): $ diff -Naur pytz-2011g pytz-2011h | lsdiff pytz-2011g/PKG-INFO pytz-2011g/pytz/__init__.py pytz-2011g/pytz/tests/test_tzinfo.py pytz-2011g/pytz/zoneinfo/America/Kralendijk pytz-2011g/pytz/zoneinfo/America/Lower_Princes pytz-2011g/pytz/zoneinfo/Asia/Anadyr pytz-2011g/pytz/zoneinfo/Asia/Irkutsk pytz-2011g/pytz/zoneinfo/Asia/Kamchatka pytz-2011g/pytz/zoneinfo/Asia/Krasnoyarsk pytz-2011g/pytz/zoneinfo/Asia/Magadan pytz-2011g/pytz/zoneinfo/Asia/Novokuznetsk pytz-2011g/pytz/zoneinfo/Asia/Novosibirsk pytz-2011g/pytz/zoneinfo/Asia/Omsk pytz-2011g/pytz/zoneinfo/Asia/Sakhalin pytz-2011g/pytz/zoneinfo/Asia/Vladivostok pytz-2011g/pytz/zoneinfo/Asia/Yakutsk pytz-2011g/pytz/zoneinfo/Asia/Yekaterinburg pytz-2011g/pytz/zoneinfo/Europe/Kaliningrad pytz-2011g/pytz/zoneinfo/Europe/Moscow pytz-2011g/pytz/zoneinfo/Europe/Samara pytz-2011g/pytz/zoneinfo/Europe/Volgograd pytz-2011g/pytz/zoneinfo/iso3166.tab pytz-2011g/pytz/zoneinfo/W-SU pytz-2011g/pytz/zoneinfo/zone.tab pytz-2011g/pytz.egg-info/PKG-INFO pytz-2011g/pytz.egg-info/SOURCES.txt Just a FYI, the zoneinfo files should not matter. We remove them before installation and use the system ones from the tzdata package. You can see that they are not even included in the package: http://packages.debian.org/sid/all/python-tz/filelist The original bug report is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416202 Moreover, after looking quickly at your package, it includes egg-info into the diff.gz... (maybe I'm just being too fuzzy ;)) I guess that one got corrected by setup.py clean ;-) --- python-tz-2011h.orig/pytz.egg-info/SOURCES.txt +++ python-tz-2011h/pytz.egg-info/SOURCES.txt @@ -2,6 +2,7 @@ LICENSE.txt MANIFEST.in README.txt +setup.cfg setup.py pytz/__init__.py pytz/exceptions.py If you build using svn-buildpackage you don't get this. It's a pity setuptools is makes a mess here. -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#616650: Info received (2011h is available)
On Wed, Sep 21, 2011 at 05:45:45PM +0300, Gediminas Paulauskas wrote: 2011/9/17 Arnaud Fontaine ar...@debian.org: Hi, I have checked on difference of 2011h from 2010b: * API changes are minimal and seems to be backward compatible * primarily it is an update of timezones information I saw no harm of updating unstable with it, so I did a sloppy uupdate, cloned original bugreport to leave 3k compatibility on TODO list, tested the package (lintian warnings remained), and uploaded to 10-days delayed. (if you don't mind, I could re-upload to 0-delay ;) ) If rejected/objected, NMU and its backports for all recent Debian and Ubuntu releases could be found at neuro.debian.net Indeed, I was waiting for Gediminas to confirm that there is no problem with updating the packages in pkg-zope SVN repository (which includes pytz) to ZTK 1.1.2 before uploading these packages... Gediminas: have you had time to look at that? While the upload of pytz seems harmless, I would prefer to follow ZTK 1.1.2 versions (unless Gediminas disagrees of course), which suggests pytz 2011g (even if it's just a small change). I would like all the work that is already done uploaded first, and only then look what is not up-to-date with ZTK 1.1 pytz is not even part of ZTK, and should always be the latest, so this discussion did not need to happen. I can update the ZTK myself, and the bump of pytz version would be one I would worry the least about. It is best to match the tzdata version, because python-tz package uses that data instead of the included one. tzdata in sid is already at 2011j. As I said in another e-mail, the python-tz package does not contain the zoneinfo data itself. It is patched to use the data from tzdata. So we only need to upload it when the code changes. We get data upgrades for free and we'll always be in-sync with tzdata. -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#622856: yui-compressor: Please upload new version
Package: yui-compressor Version: 2.4.2-1.1 Severity: wishlist Both the yui-compressor's github page: https://github.com/yui/yuicompressor/tree/master/build And stackoverflow: http://stackoverflow.com/questions/4144706/is-there-a-version-of-yui-compressor-that-deals-correctly-with-media-queries Point out the existence of new versions of yui-compressor. -- System Information: Debian Release: 5.0.8 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.21.7-2.fc8xen-ec2-v1.0 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages yui-compressor depends on: ii default-jre-headless 1.5-30 Standard Java or Java compatible R ii gij-4.3 [java5-runti 4.3.2-2 The GNU Java bytecode interpreter ii java-gcj-compat-head 1.0.78-2Java runtime environment using GIJ ii java-wrappers0.1.6 wrappers for java executables ii libjargs-java1.0.0-1 Command-line argument parsing for ii openjdk-6-jre-headle 6b18-1.8.3-2~lenny1 OpenJDK Java runtime, using Hotspo ii sun-java5-jre [java5 1.5.0-22-0lenny1Sun Java(TM) Runtime Environment ( ii sun-java6-jre [java5 6-22-0lenny1Sun Java(TM) Runtime Environment ( yui-compressor recommends no packages. yui-compressor suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595928: python-mechanize: New upstream version available
On Thu, Sep 09, 2010 at 04:09:17PM +0400, Mikhail Lukyanchenko wrote: 2010/9/9 Brian Sutherland br...@vanguardistas.net: I reviewed the package you uploaded to http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=python-mechanize and have a number of questions/comments. 1. The upstream changelog [1] states for 0.2.0: ClientForm has been merged into mechanize. This means that mechanize has no dependencies other than Python itself. ... I probably won't do further standalone releases of ClientForm. So why does the package still depend on python-clientform? 2. Why does the package now have XS-Python-Version: = 2.6 in debian/control and 2.5- in debian/pyversions? At best that's inconsistent. Upstream claims to support any python version above 2.4 [2] What's up? There's no reason for 1 and 2. Just dirty packaging. Ok. 3. Looking at the changelog of zope.testbrowser [3], it appears incompatible with versions of python-mechanize above 0.2.0. A new zope.testbrowser version would have to be uploaded to prevent breakage there. That may require changes elsewhere as the differences between our current zope.testbrowser and the latest are quite large. Indeed, current Squeeze version of zope.testbrowser should be incompatible with my mechanize upload. But I'm not sure how to resolve this issue because I have no experience with zope. Treat zope.testbrowser just like any other python module for packaging purposes. In this case, I think you may be lucky zope.testbrowser has few other hard dependencies. You might want to try just packaging the latest version of testbrowser. You'll need to ask the pkg-zope mailing list if there are any objections to this: http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers 4. Squeeze is frozen [4]. Perhaps now is not the time to introduce major new versions of packages that trigger breakage in other packages? You need a very strong reasoning for that, what is it? You are absolutely right. As I was told at debian-mentors list I should have targeted this upload at experimental. Given points 3 and 4, I'm afraid of uploading this package before squeeze is released. Afterwards, it definitely should be uploaded along with a new version of zope.testbrowser at least. I'll improve my package according to your comments 1 and 2 and then will have a look if I could package current zope.testbrowser release. But I'm afraid I have no sufficient expertise to deal with it. You probably also want to look at other packages that depend on python-mechanize. To see if they will be affected by the change. AFAIK, the best way to search for reverse dependencies is using apt-cache rdepends. The only one I know about off-hand is twill: http://packages.debian.org/sid/python-twill It would be a shame if Debian stuck with outdated mechanize release. Yes, it would be a shame. It's also a shame to ship with broken software because of a last minute dependency change. I'll take old-but-working software over broken software any time. This version should have been uploaded a long time ago, before the freeze. It would have been much easier. I currently develop mechanize-dependant project which I plan to distribute as Debian package. And I'm pretty sure it won't run with pre-0.2 mechanize. Nice to see mechanize becoming widely used :) Does your project have a name, btw? -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#595928: python-mechanize: New upstream version available
On Tue, Sep 07, 2010 at 03:27:43PM +0400, Mikhail Lukyanchenko wrote: Package: python-mechanize Version: 0.2.1-1+nmu1 Severity: normal New upstream version 0.2.2 is available. It fixes #456206 and several other bugs not mentioned at Debian bugs. Hi, thanks for packaging this! I reviewed the package you uploaded to http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=python-mechanize and have a number of questions/comments. 1. The upstream changelog [1] states for 0.2.0: ClientForm has been merged into mechanize. This means that mechanize has no dependencies other than Python itself. ... I probably won't do further standalone releases of ClientForm. So why does the package still depend on python-clientform? 2. Why does the package now have XS-Python-Version: = 2.6 in debian/control and 2.5- in debian/pyversions? At best that's inconsistent. Upstream claims to support any python version above 2.4 [2] What's up? 3. Looking at the changelog of zope.testbrowser [3], it appears incompatible with versions of python-mechanize above 0.2.0. A new zope.testbrowser version would have to be uploaded to prevent breakage there. That may require changes elsewhere as the differences between our current zope.testbrowser and the latest are quite large. 4. Squeeze is frozen [4]. Perhaps now is not the time to introduce major new versions of packages that trigger breakage in other packages? You need a very strong reasoning for that, what is it? Given points 3 and 4, I'm afraid of uploading this package before squeeze is released. Afterwards, it definitely should be uploaded along with a new version of zope.testbrowser at least. [1] http://wwwsearch.sourceforge.net/mechanize/ChangeLog.txt [2] http://wwwsearch.sourceforge.net/mechanize/faq.html [3] http://pypi.python.org/pypi/zope.testbrowser#id1 [4] http://www.debian.org/News/2010/20100806 -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583875: python-tz: pytz is missing in pymodules/python2.6
On Mon, May 31, 2010 at 11:27:04AM +0200, Matteo Bertini wrote: Package: python-tz Version: 2010b-1 Severity: grave Justification: renders package unusable The package is installed (and reinstalled) but 'ipython -pylab' fails to start with an error like the one in bug #565432. A workaround is to create a folder like this: $ ls -l /usr/lib/pymodules/python2.6/pytz total 0 lrwxrwxrwx 1 root root 36 2010-05-31 10:59 __init__.py - /usr/share/pyshared/pytz/__init__.py lrwxrwxrwx 1 root root 37 2010-05-31 10:59 reference.py - /usr/share/pyshared/pytz/reference.py lrwxrwxrwx 1 root root 34 2010-05-31 10:59 tzfile.py - /usr/share/pyshared/pytz/tzfile.py lrwxrwxrwx 1 root root 34 2010-05-31 10:59 tzinfo.py - /usr/share/pyshared/pytz/tzinfo.py Hi, I tried to reproduce this, but couldn't. Can you try (without the folder that you created as a workaround) this command in the shell: python2.6 -c 'import pytz; print pytz.__file__' To try reproduce this, I installed python-tz on a brand new minimally installed machine. It worked as expected from the python2.6 command line: # python2.6 Python 2.6.5+ (release26-maint, May 30 2010, 13:37:47) [GCC 4.4.4] on linux2 Type help, copyright, credits or license for more information. import pytz print pytz.__file__ /usr/lib/python2.6/dist-packages/pytz/__init__.pyc -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (990, 'stable'), (600, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages python-tz depends on: ii python 2.5.2-3 An interactive high-level object-o ii python-central 0.6.16register and build utility for Pyt ii tzdata 2010a-0lenny1 time zone and daylight-saving time python-tz recommends no packages. python-tz suggests no packages. -- no debconf information ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#583875: python-tz: pytz is missing in pymodules/python2.6
On Mon, May 31, 2010 at 01:08:24PM +0200, Matteo Bertini wrote: On lun, 2010-05-31 at 12:36 +0200, Brian Sutherland wrote: Hi, I tried to reproduce this, but couldn't. Can you try (without the folder that you created as a workaround) this command in the shell: python2.6 -c 'import pytz; print pytz.__file__' [13:00] bert...@armonia:~$ python2.6 Python 2.6.5 (r265:79063, Mar 18 2010, 23:38:15) [GCC 4.4.3] on linux2 Type help, copyright, credits or license for more information. import pytz Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named pytz I just removed --purge pytz and matplotlib and reinstalled but the problems still remains. Can this be is a weird problem related to some easy_install-ed package that silently causes an half pytz install? If it's it possible to add some option to have a debug trace off the package installation I can attach it here. python-central symlinks the pytz files into place at installation time. There may be something weird going on with that. Could you show what happens when you reinstall? Unfortunately I'm not very well versed in python-central, so I'm just guessing at this point. Thanks, Matteo Bertini -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552918: zope.sendmail: FTBFS: mv: cannot stat `debian/python-zope.sendmail/usr/lib/python2.4/site-packages/zope.se ndmail-*-py2.4.egg-info': No such file or directory
On Wed, Oct 28, 2009 at 11:47:33AM +0100, Lucas Nussbaum wrote: Source: zope.sendmail Version: 3.6.0-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091028 qa-ftbfs Justification: FTBFS on amd64 This bug should have been fixed with the upload of van.pydeb 1.3.0-2, now in testing. -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552945: van.pydeb: FTBFS: mv: cannot stat `debian/python-van.pydeb/usr/lib/python2.4/site-packages/van.pydeb-* -py2.4.egg-info': No such file or directory
pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547857: Fix for this bug
tag 547857 + pending thanks Applied modified patch from Kumar Appaiah for this bug to svn. -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547986: RM: python-pullparser -- ROM; Unmaintained upstream, no rdepends
Package: ftp.debian.org Severity: normal According to the upstream website this module is no longer maintained: http://wwwsearch.sourceforge.net/pullparser/ It also has no reverse dependencies in unstable. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547987: O: smart-notifier
Package: wnpp Severity: normal I do not have the ability to easily test changes to smart-notifier anymore and thus cannot fix bugs. But I see that it's growing in popularity and home someone else is up to the job. -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538176: zope3 and python-zope.i18nmessageid: error when trying to install together
-twisted-bin. Unpacking python-twisted-bin (from .../python-twisted-bin_8.2.0-2_amd64.deb) ... Selecting previously deselected package python-twisted-core. Unpacking python-twisted-core (from .../python-twisted-core_8.2.0-2_all.deb) ... Selecting previously deselected package python-twisted-conch. Unpacking python-twisted-conch (from .../python-twisted-conch_1%3a8.2.0-2_all.deb) ... Selecting previously deselected package python-twisted-web2. Unpacking python-twisted-web2 (from .../python-twisted-web2_8.1.0-2_all.deb) ... Selecting previously deselected package python-pullparser. Unpacking python-pullparser (from .../python-pullparser_0.1.0-1.1_all.deb) ... Processing triggers for man-db ... Can not write log, openpty() failed (/dev/pts not mounted?) Setting up python2.4-minimal (2.4.6-2) ... Setting up mime-support (3.46-1) ... Setting up libdb4.5 (4.5.20-13) ... Setting up python2.4 (2.4.6-2) ... Setting up zope-common (0.5.48) ... Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously deselected package zope3. (Reading database ... 11073 files and directories currently installed.) Unpacking zope3 (from .../zope3_3.4.0-1_amd64.deb) ... Selecting previously deselected package python-pkg-resources. Unpacking python-pkg-resources (from .../python-pkg-resources_0.6c9-2_all.deb) ... Selecting previously deselected package python-setuptools. Unpacking python-setuptools (from .../python-setuptools_0.6c9-2_all.deb) ... Selecting previously deselected package python-zope.component. Unpacking python-zope.component (from .../python-zope.component_3.7.0-1_all.deb) ... Selecting previously deselected package python-zope.i18nmessageid. Unpacking python-zope.i18nmessageid (from .../python-zope.i18nmessageid_3.4.3-4_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/python-zope.i18nmessageid_3.4.3-4_amd64.deb (--unpack): trying to overwrite `/usr/lib/python2.5/site-packages/zope/i18nmessageid/_zope_i18nmessageid_message.so', which is also in package zope3 Errors were encountered while processing: /var/cache/apt/archives/python-zope.i18nmessageid_3.4.3-4_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail. Possible solutions are to have the two packages conflict, to rename the common file in one of the two packages, or to remove the file from one package and have this package depend on the other package. File diversions or a Replace relation are another possibility. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/lib/python2.5/site-packages/zope/i18nmessageid/_zope_i18nmessageid_message.so This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. -Ralf. ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537581: zope.interface: FTBFS with python 2.6
On Sun, Jul 19, 2009 at 05:07:11PM +0200, Michael Bienia wrote: Package: zope.interface Version: 3.5.1-2 Severity: wishlist Tags: patch Hello, I tried building zope.interface in Ubuntu karmic which has already python 2.6 as the default python version. The build failed with the following error: Thanks! I've applied a version of your patch (modified to build on Debian Lenny) to the pkg-zope subversion repository. It'll be in the next upload. -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#536419: zope3: broken install
While this is indeed a zope3 bug, in the long term gaphor would need to depend directly on the python-zope.* pacakges it requires. These have just recently entered unstable: http://packages.debian.org/search?keywords=python-zope On Tue, Jul 14, 2009 at 11:59:08AM +0200, Michael Schutte wrote: severity 536419 serious thanks On Thu, Jul 09, 2009 at 09:28:44PM +0300, Andrew O. Shadoura wrote: Hello. Just have tried to install gaphor which uses zope3, and install was completely broken: [???] Setting up python-mechanize (0.1.7b-3) ... pycentral: pycentral pkginstall: not overwriting local files: /usr/lib/python2.5/site-packages/mechanize/__init__.py /usr/lib/python2.5/site-packages/mechanize/_auth.py /usr/lib/python2.5/site-packages/mechanize/_clientcookie.py /usr/lib/python2.5/site-packages/mechanize/_gzip.py /usr/lib/python2.5/site-packages/mechanize/_headersutil.py /usr/lib/python2.5/site-packages/mechanize/_html.py /usr/lib/python2.5/site-packages/mechanize/_lwpcookiejar.py /usr/lib/python2.5/site-packages/mechanize/_mechanize.py /usr/lib/python2.5/site-packages/mechanize/_mozillacookiejar.py /usr/lib/python2.5/site-packages/mechanize/_msiecookiejar.py /usr/lib/python2.5/site-packages/mechanize/_opener.py /usr/lib/python2.5/site-packages/mechanize/_pullparser.py /usr/lib/python2.5/site-packages/mechanize/_request.py /usr/lib/python2.5/site-packages/mechanize/_urllib2.py /usr/lib/python2.5/site-packages/mechanize/_useragent.py /usr/lib/python2.5/site-packages/mechanize/_util.py [???] zope3 ships private copies of a lot of Python packages, which is bad enough on its own, but it additionally installs them system-wide in /usr/lib/python2.5/site-packages. This is a huge problem because it not only replaces symlinks placed there by python-central (potentially newer library versions!), but also breaks later installations of affected python-* packages, like python-tz or python-mechanize. For these reasons I consider this bug release-critical. The best solution would be to create a zope3 (or, even better, python-zope) package which only ships the ???zope??? module hierarchy and depends on all the other stuff it needs; of course, some of the included modules have yet to be packaged. If this is impossible because, say, zope absolutely requires the modules as included, a private Python module directory in /usr/share/zope might be an alternative. Cheers, -- Michael Schutte mi...@uiae.at ___ pkg-zope-developers mailing list pkg-zope-develop...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#464193: smart-notifier: message points user to wrong log file
On Tue, Feb 05, 2008 at 11:17:57AM -0700, dann frazier wrote: Package: smart-notifier Version: 0.28-1 Severity: normal Today I got a couple of pop-ups from smart-notifier, with the following text: /snip I don't have any entries from smartd in /var/log/messages, but I do have a number in /var/log/syslog and /var/log/daemon.log: Feb 5 10:41:08 krebs smartd[3035]: Device: /dev/sdc, No such device, open() failed Feb 5 11:11:09 krebs smartd[3035]: Device: /dev/sdc, No such device, open() failed I'm guessing that perhaps /var/log/messages is the upstream default, but the Debian default is actually /var/log/daemon.log. This message is only displayed by smart-notifier, it originates with smartd. Seems like the bug should be re-assigned there. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ia64 Kernel: Linux 2.6.24-1-mckinley (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages smart-notifier depends on: ii dbus 1.1.2-1simple interprocess messaging syst ii python-central0.5.15-0.1 register and build utility for Pyt ii python-dbus [python2.4-dbus] 0.82.4-1 simple interprocess messaging syst ii python-glade2 [python2.4-glad 2.12.1-1 GTK+ bindings: Glade support ii python-gtk2 [python2.4-gtk2] 2.12.1-1 Python bindings for the GTK+ widge ii python2.4 2.4.4-7An interactive high-level object-o ii smartmontools 5.37-6 control and monitor storage system smart-notifier recommends no packages. -- no debconf information -- Brian Sutherland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#422373: schooltool status ?
On Tue, Sep 11, 2007 at 01:25:59PM +0100, Regis Boudin wrote: Hi, This FTBFS bug has been open for 4 months without a reply, and one of the b-deps was removed 3 months ago. What's your plan ? Currently there is an upstream SchoolTool release in alpha stage. We depend on and are waiting for Zope 3.4 to be released before finalizing the latest SchoolTool release. Zope 3.4 is currently in beta, and so hasn't been uploaded to unstable yet. The current release date for Zope 3.4 is it will be done when it's done, (http://mail.zope.org/pipermail/zope3-dev/2007-August/023452.html). There are testing versions of all these packages at: deb http://ftp.schooltool.org/schooltool/archives/debian/ unstable main Is this package still actively maintained ? Yep. Regis ___ pkg-zope-developers mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#423831: [UNMETDEPS] python2.4-schoolbell depends on zope3 (= 3.3)
schoolbell and python2.4-schoolbell have been removed from debian, so I guess this bug is fixed in a way. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394654 On Mon, May 14, 2007 at 01:43:59PM +0200, Luca Falavigna wrote: From: Luca Falavigna [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: [UNMETDEPS] python2.4-schoolbell depends on zope3 (= 3.3) Package: schoolbell Version: 1.2.4-2 Severity: normal python2.4-schoolbell depends on zope3 (= 3.3), but Debian ships 3.3.1-1. When trying to install it, apt returns this error: The following packages have unmet dependencies: python2.4-schoolbell: Depends: zope3 (= 3.3) but 3.3.1-1 is to be installed E: Broken packages This bug was initially reported in Ubuntu: https://launchpad.net/bugs/112144 Thank you. ___ pkg-zope-developers mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416202: python-tz: Provides duplicate timezone information.
On Mon, Mar 26, 2007 at 05:57:36PM +0200, Kurt Roeckx wrote: On Mon, Mar 26, 2007 at 12:21:40PM +0200, Brian Sutherland wrote: On Sun, Mar 25, 2007 at 10:13:42PM +0200, Kurt Roeckx wrote: Package: python-tz Severity: wishlist Hi, It seems that python-tz basicly packs the Olson database which is also provided by the tzdata package. It would be good if we only had 1 package that provided that data, so we only have to update one of them. It seems to contain the same data, but in a different format. It would be nice if it could just get that information from the tzdata package instead. Ubuntu seems to have a patch for this: https://bugs.launchpad.net/ubuntu/+source/gcj-4.1/+bug/41159 The patch is at: http://patches.ubuntu.com/p/python-tz/python-tz_2007c-0ubuntu1.patch FYI: looks like the patch might cause this bug https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/94415 -- Brian Sutherland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394654: Uninstallable due to unmet dep on zope3 ( 3.3)
On Tue, Apr 17, 2007 at 01:37:43PM +0200, Lucas Nussbaum wrote: On 25/10/06 at 20:24 +0200, Brian Sutherland wrote: On Sun, Oct 22, 2006 at 03:12:16PM +0200, Luk Claes wrote: Package: python2.4-schoolbell Severity: serious Version: 1.2.4-2 Hi Your package is not installable as it depends on zope3 ( 3.3) while version 3.3.0-3 of zope3 is in unstable... Yes, and unfortunately it will remain that way until someone updates schoolbell code to work with zope 3.3.0. That is non-trivial and doesn't seem like it will happen soon. (See bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393244 for more info) SchoolBell should be removed from testing until the work is done or we decide to remove it from Debian completely. Hi, Has there been some progress on this ? Wouldn't it be better to remove schoolbell from Debian if it's unlikely to be ported to zope 3 soon ? Upstream is is planning a release of schooltool, but not of schoolbell. So, yes, I guess requesting the removal of schoolbell is the right course of action. Thank you, -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ___ pkg-zope-developers mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418457: python-mechanize: new upstream version
On Mon, Apr 09, 2007 at 11:04:33PM +0200, Bernd Zeimetz wrote: Heya, Could you please package the last upstream version of python-mechanize (e.g. 0.1.6b)? as this is another dependency of Zenoss I'll upgrade mechanize in svn to the latest upstream version so we have somethign to test. J�r�my updated it when I was writing the mail... Please don't let this get into testing. Updating to a new mechanize now has very likely broken zope3. Thanks! -- Bernd Zeimetz [EMAIL PROTECTED] http://bzed.de/ ___ pkg-zope-developers mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland
Bug#418457: python-mechanize: new upstream version
On Mon, Apr 09, 2007 at 11:49:17PM +0200, Bernd Zeimetz wrote: Heya, Please don't let this get into testing. Updating to a new mechanize now has very likely broken zope3. would it make sense to ship more than one version of mechanize, as it is done with python-snmp for example? I once tried to actually tried to use python-snmp. It took me a long time to figure out where was the code I should have been using. Breakign zope3 would not be a good idea, but not beeing able to use other packages because zope3 depends on older versions isn't good either. Er, take my remarks in the time that I thought we were in. i.e. before Etch was released. But, yes Etch has been released !!Hooray!! So I don't have many objections to uploading a new mechanize. Cheers, Bernd -- Bernd Zeimetz [EMAIL PROTECTED] http://bzed.de/ -- Brian Sutherland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#416202: python-tz: Provides duplicate timezone information.
On Sun, Mar 25, 2007 at 10:13:42PM +0200, Kurt Roeckx wrote: Package: python-tz Severity: wishlist Hi, It seems that python-tz basicly packs the Olson database which is also provided by the tzdata package. It would be good if we only had 1 package that provided that data, so we only have to update one of them. It seems to contain the same data, but in a different format. It would be nice if it could just get that information from the tzdata package instead. Ubuntu seems to have a patch for this: https://bugs.launchpad.net/ubuntu/+source/gcj-4.1/+bug/41159 It's definitely something to look into after etch is released. Kurt -- Brian Sutherland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390152: python2.3: Also broken in python2.4
Package: python2.3 Version: 2.3.5-14 Followup-For: Bug #390152 This is still an issue in python2.4. Using this python2.4: Python 2.4.4 (#2, Oct 20 2006, 00:23:25) [GCC 4.1.2 20061015 (prerelease) (Debian 4.1.1-16.1)] on linux2 and this test program: import logging logging.basicConfig(level=logging.DEBUG, format='%(pathname)s:%(lineno)d') logging.info('whoops') The output when the logging/__init__.pyc file exists is: logging/__init__.py:1072 and when the __init__.pyc is deleted the output becomes: tst.py:5 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python2.3 depends on: ii libbz2-1.01.0.3-2high-quality block-sorting file co ii libc6 2.3.6-7GNU C Library: Shared libraries ii libdb4.3 4.3.29-5 Berkeley v4.3 Database Libraries [ ii libncurses5 5.5-2 Shared libraries for terminal hand ii libreadline5 5.1-7 GNU readline and history libraries ii libssl0.9.8 0.9.8c-1 SSL shared libraries ii python-central0.5.8 register and build utility for Pyt ii zlib1g1:1.2.3-11 compression library - runtime Versions of packages python2.3 recommends: ii python2.3-cjkcodecs 1.1.1-1Python Unicode Codecs Collection f ii python2.3-iconvcodec 1.1.2-2.2 Python universal Unicode codec, us -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405258: schooltool: [INTL:de] German po-debconf template translation
On Tue, Jan 02, 2007 at 12:37:15AM -0500, Matthias Julius wrote: Package: schooltool Version: 0.11.4-3 Severity: minor Tags: patch l10n I have prepared a translation of the template for po-debconf into German. Please include it in debian/po. Thanks, I've committed this translation to the pkg-zope repository, however an upload might take some time as schooltool is in limbo until the next upstream release. In contrast to the other strings the last string mentions a SchoolBell database. Is this correct? Yep, it was wrong. I've also fixed that in subversion, thanks. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396163:
On Mon, Oct 30, 2006 at 08:13:35AM +0100, AsT wrote: Package: smart-notifier Version: 0.25-1 Severity: normal It just doesnt start without error(stalls) That's kindof what it's meant to do. It just sits and listens on the dbus until it is notified. If you want to trigger it to actually do something visible, please read /usr/share/doc/smart-notifier/README.Debian -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395151: zope3: Zope 3.3 breaks with python 2.4.4
Package: zope3 Version: 3.3.0-3 Severity: normal Tags: patch Hi, It seems that zope3 is broken on unstable at the moment because of python 2.4.4, please apply the upstream patch that addresses the issue: http://mail.zope.org/pipermail/zope3-checkins/2006-October/028609.html I will also provide a zope3 3.3.0-4 package with this patch applied at: deb-src ftp://ftp.schooltool.org/pub/schooltool/archives/debian unstable main if anyone wants to sponsor it. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages zope3 depends on: ii libc6 2.3.6-7GNU C Library: Shared libraries ii lsb-base 3.1-5 Linux Standard Base 3.1 init scrip ii python-clientform 0.2.2-2module for handling HTML forms on ii python-docutils 0.4-1 Utilities for the documentation of ii python-mechanize 0.1.2b-3 stateful programmatic web browsing ii python-twisted-conch 1:0.7.0-1 The Twisted SSH Implementation ii python-twisted-web2 0.2.0-1An HTTP/1.1 Server Framework ii python-tz 2006g-1Python version of the Olson timezo ii python-xml0.8.4-5XML tools for Python ii python-zopeinterface 3.3.0-3The implementation of interface de ii python2.4 2.4.3-8An interactive high-level object-o ii zope-common 0.5.24 common settings and scripts for zo zope3 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394654: Uninstallable due to unmet dep on zope3 ( 3.3)
On Sun, Oct 22, 2006 at 03:12:16PM +0200, Luk Claes wrote: Package: python2.4-schoolbell Severity: serious Version: 1.2.4-2 Hi Your package is not installable as it depends on zope3 ( 3.3) while version 3.3.0-3 of zope3 is in unstable... Yes, and unfortunately it will remain that way until someone updates schoolbell code to work with zope 3.3.0. That is non-trivial and doesn't seem like it will happen soon. (See bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393244 for more info) SchoolBell should be removed from testing until the work is done or we decide to remove it from Debian completely. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394654: Uninstallable due to unmet dep on zope3 ( 3.3)
On Wed, Oct 25, 2006 at 10:43:17PM +0200, Luk Claes wrote: Brian Sutherland wrote: On Sun, Oct 22, 2006 at 03:12:16PM +0200, Luk Claes wrote: Package: python2.4-schoolbell Severity: serious Version: 1.2.4-2 Hi Your package is not installable as it depends on zope3 ( 3.3) while version 3.3.0-3 of zope3 is in unstable... Yes, and unfortunately it will remain that way until someone updates schoolbell code to work with zope 3.3.0. That is non-trivial and doesn't seem like it will happen soon. (See bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393244 for more info) SchoolBell should be removed from testing until the work is done or we decide to remove it from Debian completely. What about schooltool as schoolbell won't be removed from testing if it makes it's reverse dependencies uninstallable...? I've just asked for a sponsor to upload a beta version of the next schooltool release which does not have a dependency on schoolbell: http://lists.alioth.debian.org/pipermail/pkg-zope-developers/2006-October/002468.html I didn't really want to upload a beta version of schooltool, but it seems like the least bad option at the moment. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393244: schoolbell: FTBFS: ImportError: No module named servicecontainer
Hi Fabio, On Sun, Oct 22, 2006 at 12:11:14PM +0200, Fabio Tranchitella wrote: On mer, 18 ott 2006, Brian Sutherland wrote: Hi Andreas, The error you describe is probably from trying to build schoolbell with Zope3.3 which was lately uploaded in an un-coordinated fashion. Are you talking about uploads in Debian? Yes. Zope3.3 has been uploaded a few days after the official release, so the lately doesn't apply to the context. I meant lately in the sense of recently. I guess it wasn't very clear. But waiting with the Zope 3.3 upload wouldn't have helped very much anyway, for reasons I explain below. SchoolBell needs to be updated to work with Zope 3.3, but it looks as if upstream is not willing to make that happen. No outside volunteers have appeared to take over that role. Well, doesn't schooltool depend on schoolbell? The dependencies were changed in the latest development cycle. SchoolTool and SchoolBell now both depend independently on a collection of libraries under the schooltool.* namespace. The schoolbell module will still exist, but is almost empty and just for backwards compatibility. So, both schooltool and schoolbell should depend on python-schooltool and be built from the same source package. SchoolBell was broken during this development, and never fixed. So there are 3 paths that I can see: 1. Update the current schoolbell to work with Zope 3.3 2. Fix the current development branch of schoolbell so that it works. 3. Remove schoolbell from testing until 1 or 2 is done. There just hasn't been the volunteers or paid development to do 1 or 2, so it must be 3. How can upstream release a zope 3.3-compatible product for one without the other one? Since schooltool doesn't depend on schoolbell anymore, this can be done. Are you talking about just `schoolbell.app'? I think it is just a matter of conditional import, isn't it? schoolbell.app does not exist anymore. The code that was schoolbell.app is now at schooltool.sbapp. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#393244: schoolbell: FTBFS: ImportError: No module named servicecontainer
On Sun, Oct 15, 2006 at 07:28:36PM +0200, Andreas Jochens wrote: Package: schoolbell Version: 1.2.4-2 Severity: serious Hello, when building 'schoolbell' in a clean unstable chroot, I get the following error: Hi Andreas, The error you describe is probably from trying to build schoolbell with Zope3.3 which was lately uploaded in an un-coordinated fashion. SchoolBell needs to be updated to work with Zope 3.3, but it looks as if upstream is not willing to make that happen. No outside volunteers have appeared to take over that role. If this continues, schoolbell should be removed from testing and perhaps later from Debian. Note that it was never released in a stable release. For SchoolTool, the situation is completely different. There is a new release around the corner which will be compatible with Zope 3.3. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381389: Reproduceable, and not smart-notifier's fault
On Wed, Oct 04, 2006 at 09:42:14AM +0200, Raphael Hertzog wrote: On Wed, 16 Aug 2006, Brian Sutherland wrote: On Sat, Aug 12, 2006 at 12:17:21PM -0300, Margarita Manterola wrote: I can reproduce this in my machine. It's due to the fact that /usr/bin/python points to python2.3 in my box, and smart-notifier's python version is current. Changing this in /var/lib/dpkg/status, fixes this bug. Therefore, as discussed with Pierre Habouzit, this is a bug in dh_python, which is not placing the correct version in the Python-Version field, and It looks to me like this is what happens: smart-notifier has XS-Python-Version set to 2.4 but the binary package gets Python-Version current if built with python2.4 as the default python. Can you really reproduce that with the dh_python of debhelper 5.0.37.3 ? I reproduced the installation problem, but didn't try the build leading up to it with the latest debhelper. I wanted to prepare a patch for this, but I really get 2.4 and not current when building smart-notifier with python 2.4... Yeah, I get the same. But I will note that the smart-notifier binary in the archive has Python-Version set to current and build depends on =5.0.37.2. So looks like it was only a problem in 5.0.37.2, or something else changed in between then and now. Thanks for looking into it. I guess now the bug should be sent back to smart-notifier to be fixed with an updated build dependency. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385144: [Pkg-zope-developers] Bug#385144: zope-zms: New upstream version available for some time
On Tue, Aug 29, 2006 at 04:32:06PM +0200, Uwe Steinmann wrote: I built a new debian package from zms 2.9.2, which was quite simple, but I'm simply too unfamiliar with zope and its intances to make it work on zope3. Would be great if you could create a new package for zope3. zope3 is a complete re-write of Zope 2 with totally different architecture and concepts. So, right now, it is almost impossible to write a non-trivial extension that works on both. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385144: [Pkg-zope-developers] Bug#385144: zope-zms: New upstream version available for some time
On Tue, Aug 29, 2006 at 05:58:03PM +0200, Uwe Steinmann wrote: On Tue, Aug 29, 2006 at 05:38:30PM +0200, Brian Sutherland wrote: On Tue, Aug 29, 2006 at 04:32:06PM +0200, Uwe Steinmann wrote: I built a new debian package from zms 2.9.2, which was quite simple, but I'm simply too unfamiliar with zope and its intances to make it work on zope3. Would be great if you could create a new package for zope3. zope3 is a complete re-write of Zope 2 with totally different architecture and concepts. So, right now, it is almost impossible to write a non-trivial extension that works on both. Is there any documentation or a best practise example on how to package a product like zms for zope3? It's not really a matter of packaging. More that you would probably have to re-write most of zms to make it work with zope3. Which I guess would take a _long_ time. However, Zope 2 is slowly starting to be based on Zope 3 (a process of years). So, perhaps by Zope 2.15 porting zms to pure Zope3 will probably be easier. However, if you want to, probably the best first step would be to learn to write Zope 3 extensions. Googling for 'zope 3 10 minutes' gives some reasonable places to start with links to further docs. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: +2331 840446Fax: +2331 843920 -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381389: Reproduceable, and not smart-notifier's fault
On Tue, Aug 22, 2006 at 12:42:03AM +0200, Josselin Mouette wrote: Le mercredi 16 ao�t 2006 � 11:34 +0200, Brian Sutherland a �crit : smart-notifier has XS-Python-Version set to 2.4 but the binary package gets Python-Version current if built with python2.4 as the default python. In my tests with python2.3 as the default, Python-Version is set to 2.4. In both cases there is no python dependency (only python2.4). So anyone installing smart-notifier built with python2.4 as the defualt on a machine with python2.3 as the default experiences breakage when python-central tries to compile the bytecode for python2.3. It seems to me that dh_python should set Python-Version to x.y if XS-Python-Version is x.y regardless of what the current default python is. At least that is what I would have expected. This is one of the reasons why I don't like the X?-Python-Version fields. There is no way for the build process to tell between those two cases: 1. building for python2.4 only as we build for one version only and python2.4 is the default version; 2. building for python2.4 only as this is the only supported version. Does this not work for case 1: XS-Python-Version: current and for case 2: XS-Python-Version: 2.4 If we apply the solution you describe, case 2 will be fixed, but case 1 will break: when upgrading the default python interpreter, the module will not be available for the new version. Thus, we need separate interfaces to tell the helper tools about that. The -V flag was reintroduced in dh_pysupport (in 0.4) to fix this case, and I believe something similar should be done in dh_pycentral as well - dh_python is doomed to be removed anyway. Yep, with the latest strategy of dh_python, this is probably a python-central bug and has very little to do with dh_python or python-support. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!!
Bug#383099: smart-notifier: Fails to install: invalid syntax
On Tue, Aug 15, 2006 at 01:48:20AM +0100, Sam Morris wrote: Package: smart-notifier Version: 0.27-1 Severity: serious Justification: fails to install This is related to 381389 (a bug in dh_python). But until that is fixed you can work around it by updating your python to 2.4. (basically `apt-get install python` from unstable) I'll leave this bug open until I can build-depend on a new debhelper. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381389: Reproduceable, and not smart-notifier's fault
On Sat, Aug 12, 2006 at 12:17:21PM -0300, Margarita Manterola wrote: I can reproduce this in my machine. It's due to the fact that /usr/bin/python points to python2.3 in my box, and smart-notifier's python version is current. Changing this in /var/lib/dpkg/status, fixes this bug. Therefore, as discussed with Pierre Habouzit, this is a bug in dh_python, which is not placing the correct version in the Python-Version field, and It looks to me like this is what happens: smart-notifier has XS-Python-Version set to 2.4 but the binary package gets Python-Version current if built with python2.4 as the default python. In my tests with python2.3 as the default, Python-Version is set to 2.4. In both cases there is no python dependency (only python2.4). So anyone installing smart-notifier built with python2.4 as the defualt on a machine with python2.3 as the default experiences breakage when python-central tries to compile the bytecode for python2.3. It seems to me that dh_python should set Python-Version to x.y if XS-Python-Version is x.y regardless of what the current default python is. At least that is what I would have expected. I'm reassigning to debhelper (I'm sorry :-/) :) No worries. Just my luck to update this in the middle of a python transition! -- Love, Marga -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#373785: Anything new?
On Fri, Jul 28, 2006 at 09:16:48PM +0100, Baruch Even wrote: Hi, Anything new about this bug? While trying to update zpkg to the new python policy, I noticed that when zope3 moved to python2.4 broke zpkg. Very badly and quite a while ago. Nobody filed a bug == nobody cares. So, if I get the time today (I'll be on vacation from today till Aug 15) I'll set things in motion to get zpkg removed from unstable. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#381174: ftp.debian.org: Please remove zpkg, broken, superseeded and no users
Package: ftp.debian.org Severity: normal Please remove zpkg from unstable because: * zpkg has been superseeded by python eggs. * Upstream is dead, or nearly so. * It has been very broken for a long time and nobody has filed a bug. * popcon says that the number of installations is 1. * It is not in testing and has never been released. * It has no reverse dependencies. For reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=373785 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380953: Python transition (#2): you are building a private python module !
On Tue, Aug 01, 2006 at 12:32:47PM +0200, [EMAIL PROTECTED] wrote: Package: smart-notifier Version: 0.25-1 Severity: important Hi, your package has been detected as generating a (for most of that mass bug fill: private) python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page[2] explains what has to be done to upgrade your packages to the new Policy. This bug may be a false positive, in that case, please just close the bug. This bug is part of a mass bug filling, and its severity will be raised to serious when python will default to python2.4 (which should happend on tomorrow - Wed 2nd of July). Please note that this bug (even not being RC) falls under the 0-day NMU policy. I have prepared an upload (0.27-1) and asked a sponsor to upload it. otherwise, find it here: deb-src http://lentejasverdes.ath.cx/packages unstable main [1] http://lists.debian.org/debian-devel-announce/2006/06/msg9.html [2] http://wiki.debian.org/DebianPython/NewPolicy especially Notes for packages with private modules/extensions Special Notes * embedded interpreters: You don't *need* to do anything for your package, though using XS/XB-Python-Version is much appreciated as it helps tracking your package for binNMUs when python2.4 will become default. * if you need help updating your package, you can either: - mail debian-python@lists.debian.org , - tag your bug + help , - come on #debian-python/OFTC. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380995: Python transition (#2): you are building a private python module !
On Tue, Aug 01, 2006 at 12:32:53PM +0200, [EMAIL PROTECTED] wrote: Package: zpkg Version: 1.0.0-1 Severity: important Hi, your package has been detected as generating a (for most of that mass bug fill: private) python module/extension that may need an upgrade to the new Python Policy[1]. A wiki page[2] explains what has to be done to upgrade your packages to the new Policy. This bug may be a false positive, in that case, please just close the bug. This bug is part of a mass bug filling, and its severity will be raised to serious when python will default to python2.4 (which should happend on tomorrow - Wed 2nd of July). Please note that this bug (even not being RC) falls under the 0-day NMU policy. Please do not NMU zpkg, I have requested it's removal from debian. But I don't have a bugnumber yet. (I will pick this up again after my vacation, i.e. August 15) [1] http://lists.debian.org/debian-devel-announce/2006/06/msg9.html [2] http://wiki.debian.org/DebianPython/NewPolicy especially Notes for packages with private modules/extensions Special Notes * embedded interpreters: You don't *need* to do anything for your package, though using XS/XB-Python-Version is much appreciated as it helps tracking your package for binNMUs when python2.4 will become default. * if you need help updating your package, you can either: - mail debian-python@lists.debian.org , - tag your bug + help , - come on #debian-python/OFTC. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378604: dh_python generates dependencies on unversioned python versions for versioned python modules
On Tue, Jul 18, 2006 at 11:53:26AM +0200, Matthias Klose wrote: Raphael Hertzog writes: tag 378604 + patch thanks On Mon, 17 Jul 2006, Matthias Klose wrote: Package: debhelper Version: 5.0.37.3 Severity: important Looking at python2.4-schoolbell, ${python:Depends} is expanded to python-central (= 0.5), python ( 2.5), python (= 2.4) | python2.4 which is wrong. It's not really wrong... but it's not really optimized for the purpose of the package. The package puts files in /usr/lib/python2.4/site-packages so it won't work with python2.5 ... the python ( 2.5) guarantees that. There's no script using #!/usr/bin/python2.4 otherwise you would have had a dependency python2.4 ... In theory, looking at the package it should have gotten a python (= 2.4), python ( 2.5) dependency however since that's not satisfiable in sid right now, it has been loosened to the dependency above. If modules are meant for public uses, they should work with all python versions and in that case the dependency they get is the right one. But in this case, we have public modules which are not really meant to be used by the end-user and which are only used by one application and thus compiled for the version that this application uses. all the modules are for public use. however zope3 is only available for python2.4 (and not above), so the same is needed for packages depending on zope3. You have two hints that a dependency on a unversioned python is unwanted: - XS-Python-Version is explicitely set - the package is named python2.4-xxx FYI, in the schooltool packages for the next upstream release, the package name will take the form python-xxx. However the XS-Python-Version will continue to be set to a subset of the python versions of the its dependencies (zope3 being the main culprit). -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378596: python-imaging: missing dependencies of .so module
Package: python-imaging Version: 1.1.5-10 Severity: important It appears that python-imaging somehow lost the dependencies of the extension module. Perhaps in the conversion to the new policy. Trying this in a minimal pbuilder environment with python2.4, python-imaging installed: [EMAIL PROTECTED]:/# python2.4 Python 2.4.4c0 (#2, Jun 14 2006, 22:35:41) [GCC 4.1.2 20060613 (prerelease) (Debian 4.1.1-4)] on linux2 Type help, copyright, credits or license for more information. from PIL import _imaging Traceback (most recent call last): File stdin, line 1, in ? ImportError: libjpeg.so.62: cannot open shared object file: No such file or directory % apt-cache depends python2.3-imaging python-imaging python2.3-imaging Depends: python2.3 Depends: libc6 Depends: libfreetype6 Depends: libjpeg62 Depends: zlib1g |Depends: mime-support Depends: python2.3-imaging-tk python-imaging-tk Suggests: python-imaging-doc Conflicts: pil Conflicts: python-pil Replaces: pil Replaces: python-pil python-imaging Depends: python-central Depends: python Depends: python |Depends: mime-support Depends: python-imaging-tk Suggests: python-imaging-doc Conflicts: pil Conflicts: python-pil Conflicts: python2.3-imaging Conflicts: python2.4-imaging Replaces: pil Replaces: python-pil Replaces: python2.3-imaging python-imaging Replaces: python2.4-imaging python-imaging -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages python-imaging depends on: ii mime-support 3.36-1 MIME files 'mime.types' 'mailcap ii python2.3.5-11 An interactive high-level object-o ii python-central0.5.0 register and build utility for Pyt python-imaging recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378066: [Pkg-zope-developers] Bug#378066: python2.4-schooltool: Uninstallable due to python transition
On Thu, Jul 13, 2006 at 03:42:14AM +0200, Adeodato Simó wrote: Package: python2.4-schooltool Version: 0.11.4-1 Severity: serious Hi. Your package is unninstallable as it depends on python2.4-libxml2, which is not available any more. While I agree that python2.4-schooltool should be updated to follow the new python policy, I also think that python-libxml2 should provide python2.4-libxml2 thus preventing this breakage. But this point is moot because I cannot install zope3 at the moment, and thus cannot build/test a new schooltool/schoolbell. (/me goes to file bugs on zope3 dependencies to also provide python2.4 versions) P.S. It appears that there is actually someone out there that can install zope3 because schoolbell wa just NMU'ed... Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org From the moment I picked your book up until I put it down I was convulsed with laughter. Some day I intend reading it. -- Groucho Marx ___ Pkg-zope-developers mailing list [EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!!
Bug#378066: [Pkg-zope-developers] Bug#378066: python2.4-schooltool: Uninstallable due to python transition
On Thu, Jul 13, 2006 at 07:18:26PM +0200, Adeodato Simó wrote: * Brian Sutherland [Thu, 13 Jul 2006 18:54:39 +0200]: Hi, While I agree that python2.4-schooltool should be updated to follow the new python policy, I also think that python-libxml2 should provide python2.4-libxml2 thus preventing this breakage. It wouldn't be prevented, no, since your dependency on python2.4-xml is versioned. hmm, never mind what I said, also the other stuff. I had a bad case of shoot hole in foot. Cheers, -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org A pretty boy like you With hands that could break me in two But don't -- Anja Garbarek, Can I keep him? -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!!
Bug#375798: python-clientform: please upload version 0.2.2
On Thu, Jun 29, 2006 at 10:23:50AM +0200, Alexandre Fayolle wrote: Hello Hi;) (be careful, you CC'd [EMAIL PROTECTED] in your answer) Strange, I remember that pressing 'g' normally sent the response to the bug as well. But yeah, I'll be more careful in future. On Wed, Jun 28, 2006 at 09:58:09PM +0200, Brian Sutherland wrote: On Wed, Jun 28, 2006 at 09:39:59AM +0200, Alexandre Fayolle wrote: Package: python-clientform Severity: wishlist Hi Could you please upload version 0.2.2 ? python-mechanize has a versionned Depends relationship with python-clientform-0.2.2 which currently cannot be satisfied and maked the version in sid uninstallable. I know and am trying:) I have a version prepared for upload for a number of days now, but my sponsor is over-worked at the moment, so maybe it takes time. If you can somehow get it uploaded, the package is at: deb-src http://lentejasverdes.ath.cx/packages unstable main Note that it is a -2 version, so you will need the dpkg-buildpackage -sa option. I'll upload the package today (after closing this bug in the changelog), it this is fine with you. Great! At this point I just want it uploaded. Would you be interested in uploading the zc.* and hurry.* packages I have prepared? I am looking for a sponsor for those as well. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations D�veloppement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!!
Bug#375798: python-clientform: please upload version 0.2.2
On Wed, Jun 28, 2006 at 09:39:59AM +0200, Alexandre Fayolle wrote: Package: python-clientform Severity: wishlist Hi Could you please upload version 0.2.2 ? python-mechanize has a versionned Depends relationship with python-clientform-0.2.2 which currently cannot be satisfied and maked the version in sid uninstallable. I know and am trying:) I have a version prepared for upload for a number of days now, but my sponsor is over-worked at the moment, so maybe it takes time. If you can somehow get it uploaded, the package is at: deb-src http://lentejasverdes.ath.cx/packages unstable main Note that it is a -2 version, so you will need the dpkg-buildpackage -sa option. Thanks -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8-smp Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#373785: Please do not release zpkg
Package: zpkg Version: 1.0.0-1 Severity: normal Please remove zpkg from testing (even though it is not buggy) because: * zpkg has been superseeded by python eggs * Upstream is dead, or nearly so * Current users (Zope Community) will probably convert to using eggs in the next couple of years, at wich time I will ask for zpkg's removal from debian. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages zpkg depends on: ii python2.3.5-8An interactive high-level object-o ii zope3 3.2.1-2Open Source Web Application Server zpkg recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365049: schooltool: logrotate script does not use invoke-rc.d
Package: schooltool Version: 0.11.4-1 Severity: normal The schooltool logrotate script does not use invoke-rc.d but rather /etc/init.d/schooltool restart. This is probably a bad thing I should investigate sometime. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-9-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages schooltool depends on: ii adduser 3.64ubuntu1 Add and remove users and groups ii debconf [debconf-2.0]1.4.56ubuntu2 Debian configuration management sy ii lsb-base 3.0-12 Linux Standard Base 3.0 init scrip ii openssl 0.9.7g-1ubuntu1 Secure Socket Layer (SSL) binary a ii python2.42.4.3-3 An interactive high-level object-o pn python2.4-schooltool none (no description available) ii ssl-cert 1.0-11 Simple debconf wrapper for openssl schooltool recommends no packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360585: Provide .desktop file so that smart-notifier is autostarted
On Mon, Apr 03, 2006 at 01:54:22PM +0100, Sam Morris wrote: Package: smart-notifier Version: 0.24-1 Severity: wishlist The freedesktop.org autostart-spec provides a mechanism by which per-session daemons can be registered to be started automatically when a user logs in. Basically this involves creating a .desktop file for smart-notifier and dropping it into /etc/xdg/autostart. Further details are available from http://standards.freedesktop.org/autostart-spec/. This will ensure that smart-notifier is started for the users of GNOME (2.14, according to http://www.gnome.org/start/2.14/notes/en/rndevelopers.html), KDE, XFCE and possibly Rox, as well as any other desktop environment that implements the spec. Great! I had looked briefly for something like that, but could not find it. I'll implement it in a few days. It's worth thinking about what happens if two users run smart-notifier at the same time. Both should recieve the message; is this what currently happens? I agree, but am not sure what currently happens. I'll leave this bug open until I'm sure. Thanks! -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.16-1-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages smart-notifier depends on: ii python2.4 2.4.1-2An interactive high-level object-o ii python2.4-dbus0.61-5 simple interprocess messaging syst ii python2.4-glade2 2.8.2-3GTK+ bindings: Glade support ii python2.4-gtk22.8.2-3Python bindings for the GTK+ widge ii smartmontools 5.33+5.34cvs20050802-4 control and monitor storage system -- no debconf information -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353358: smart-notifier: Packaging problems
On Fri, Feb 17, 2006 at 06:56:21PM +0100, Matthias Urlichs wrote: Package: smart-notifier Severity: important Hi Mattias, Sorry for being so tardy in replying, but I will get to these issues in the next upload (which is blocked for un-related reasons) * You are building a native package with a non-native version number. Please don't do that. Hint: The trigger for building a non-native version is the presence of a correctly-named *.orig.tar.gz file in the parent directory. yep, i'll make sure about that one the next time. * If you build-dep on Python, but then depend on pythonX.Y-foo libraries, your packaging will probably break when the next version (x.[y+1]) of Python is released. The python build-dep is for dh_python, the distribution has no setup.py and the files are installed by hand, so no versioned build-dep on python necessary. I'm just too lazy right now to write a setup.py to install about 5 files when make can do it just fine in 5 lines and one less file. - -- System Information: Debian Release: testing/unstable APT prefers dapper APT policy: (850, 'dapper'), (740, 'breezy'), (620, 'unstable'), (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'breezy-updates'), (500, 'breezy-security') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1.27 Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD9g5F8+hUANcKr/kRApOnAJ9nY0zoftZjP9uM4TRUSpnuNvNYRgCggzll gGQb5AD9Rv+RFHgmtVc0/C0= =G6Ny -END PGP SIGNATURE- -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#351980: zope.testbrowser related failure in zope3 self tests
Package: zope3 Version: 3.2.0-2 Severity: normal Tags: patch Using a testrunner script (included later) against an installed zope3 package I found a number of failures due to the mechanize module not finding the right pullparser module (ours) and using the one included in zope3. This can be fixed by applying the patch used to fix the issue upstream: http://mail.zope.org/pipermail/zope3-checkins/2006-January/026957.html (except for adding the ClientForm.py and pullparser.py modules) The failures look like: Failure in test /usr/lib/python2.4/site-packages/zope/app/apidoc/browser/README.txt Failed doctest test for README.txt File /usr/lib/python2.4/site-packages/zope/app/apidoc/browser/README.txt, line 0 -- File /usr/lib/python2.4/site-packages/zope/app/apidoc/browser/README.txt, line 8, in README.txt Failed example: browser = Browser() Exception raised: Traceback (most recent call last): File /usr/lib/python2.4/site-packages/zope/testing/doctest.py, line 1256, in __run compileflags, 1) in test.globs File doctest README.txt[1], line 1, in ? browser = Browser() File /usr/lib/python2.4/site-packages/zope/testbrowser/testing.py, line 146, in __init__ mech_browser = PublisherMechanizeBrowser() File /usr/lib/python2.4/site-packages/mechanize/_mechanize.py, line 238, in __init__ links_factory = LinksFactory() File /usr/lib/python2.4/site-packages/mechanize/_mechanize.py, line 73, in __init__ assert pullparser.__version__[:3] = (0, 0, 7), \ AssertionError: pullparser 0.0.7 or newer is required The testrunner script used is: #!/usr/bin/env python2.4 ## # # Copyright (c) 2004 Zope Corporation and Contributors. # All Rights Reserved. # # This software is subject to the provisions of the Zope Public License, # Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution. # THIS SOFTWARE IS PROVIDED AS IS AND ANY AND ALL EXPRESS OR IMPLIED # WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED # WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS # FOR A PARTICULAR PURPOSE. # ## Test script for Debian Zope3 packages. This test script will run the self tests of an installed zope3 debian package. Simply do: pythonx.y test.py import logging, os, sys, warnings here = os.path.abspath(os.path.dirname(sys.argv[0])) # Remove this directory from path: sys.path[:] = [p for p in sys.path if os.path.abspath(p) != here] from zope.testing import testrunner # Change the directory so that zope.app.functional # will be able to find the ftesting zcml os.chdir('/usr/lib/zope3/zopeskel') # run both functional and unit tests defaults = ['--tests-pattern', '^f?tests$'] # add the debian pythonpath pyver = '.'.join([str(i) for i in sys.version_info[:2]]) defaults += ['--path', '/usr/lib/python%s/site-packages' % pyver] # regex of modules to be tested, maybe this is not a complete list defaults += ['-m', '^(' 'zope' '|' 'RestrictedPython' '|' 'transaction' '|' 'zodbcode' ')'] # Don't bother trying to remove old bytecode, as we probably can not defaults += ['-k'] # Get rid of twisted.conch.ssh warning warnings.filterwarnings( 'ignore', 'PyCrypto', RuntimeWarning, 'twisted[.]conch[.]ssh') result = testrunner.run(defaults) # Avoid spurious error during exit. Some thing is trying to log # something after the files used by the logger have been closed. logging.disable(9) sys.exit(result) -- System Information: Debian Release: testing/unstable APT prefers stable APT policy: (990, 'stable'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-9-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages zope3 depends on: ii libc6 2.3.5-12 GNU C Library: Shared libraries an ii lsb-base 3.0-12 Linux Standard Base 3.0 init scrip ii python-docutils 0.3.9-0.1 Utilities for the documentation of ii python2.4 2.4.2-1An interactive high-level object-o ii python2.4-clientcookie1.1.1-1Python 2.4.x module for automating ii python2.4-mechanize 0.0.11a-2 stateful programmatic web browsing ii python2.4-tz 2005r-1Python version of the Olson timezo ii zope-common 0.5.9 common settings and scripts for zo zope3 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#348378: smart-notifier: does not start (DBus policy error)
On Mon, Jan 16, 2006 at 12:29:50PM -0500, Zack Weinberg wrote: Package: smart-notifier Version: 0.23-1 Severity: grave Justification: renders package unusable Per instructions, I set up smartd, started my usual X session, and then ran smart-notifier from within the session. It immediately quit with errors: $ smart-notifier Traceback (most recent call last): File /usr/bin/smart-notifier, line 11, in ? smart_notifier.service() File /usr/share/smart-notifier/smart_notifier/__init__.py, line 68, in service bus=dbus.SystemBus()) File /usr/lib/python2.3/site-packages/dbus.py, line 244, in __init__ dbus_bindings.bus_acquire_service(self._bus.get_connection(), service_name) File dbus_bindings.pyx, line 1489, in dbus_bindings.bus_acquire_service dbus_bindings.DBusException: Connection :1.5 is not allowed to own the service smart_notifier.DbusService due to security policies in the configuration file $ I'm not sure what's wrong here, but if I had to guess, I would be guessing that it oughta be asking for the session bus, not the system bus...? Only maybe then it doesn't work? Yeah, it is meant to be on the system bus, because it needs to communicate from a process running as root to a process running as the user. The package does install the config for that, but doesn't re-start the dbus daemon for it to take effect. A simple /etc/init.d/dbus-1 restart should solve it. That was meant to be in my next upload, but I am having problems updating the package to the new API in python2.4-dbus. Sadly that API seems to be a brick wall which just doesn't work. confused, zw -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.15-1-686-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages smart-notifier depends on: ii python2.3 2.3.5-9An interactive high-level object-o ii python2.3-dbus0.23.4-8 simple interprocess messaging syst ii python2.3-glade2 2.6.3-2GTK+ bindings: Glade support ii python2.3-gtk22.6.3-2Python bindings for the GTK+ widge ii smartmontools 5.33+5.34cvs20050802-3 control and monitor storage system smart-notifier recommends no packages. -- no debconf information -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#347687: smart-notifier: python2.3-dbus has gone away
On Thu, Jan 12, 2006 at 10:58:01AM +0800, Paul Wise wrote: Package: smart-notifier Version: 0.23-1 Severity: serious Justification: uninstallable The new dbus no longer builds python2.3-dbus, so you should depend on the python 2.4 version. Also, you will have to depend on python 2.4 versions for all your deps. Also, testing migration blocking bugs need to be severity serious or higher. Thanks for letting me know, but try as I might I cannot get my package ported to the API in python2.4-dbus. If I emit a signal, it makes it onto the bus, but there is nothing I can do to actually receive it. I cannot either go deep enough to pinpoint the problem. None of the examples I found (in the dbus source, or mailinglist) worked either. So after a day of trying, am going to give up for a while and try again with a newer version of python2.4-dbus. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#346024: smart-notifier not ready for release
Package: smart-notifier Version: 0.23-1 Severity: normal While there are no obvious bugs in smart-notifier, I do not consider it ready for release. Purely because of lack of testing. Thus this bug is to stop migration of smart-notifier to testing. Some reports of using this package may change my mind;) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-9-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages smart-notifier depends on: ii python2.3 2.3.5-8An interactive high-level object-o ii python2.3-dbus0.23.4-8 simple interprocess messaging syst ii python2.3-glade2 2.6.3-2GTK+ bindings: Glade support ii python2.3-gtk22.6.3-2Python bindings for the GTK+ widge ii smartmontools 5.33+5.34cvs20050802-3 control and monitor storage system smart-notifier recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#345617: smart-notifier: wrong python dependency
On Mon, Jan 02, 2006 at 05:15:36PM +0800, Paul Wise wrote: The python package is at version 2.3 in debian. Please rebuild the package with debian (instead of ubuntu/whatever), which uses python 2.3. Er, I guess I can only say 'oops' to this. I will try to make this package only depend on python2.3 and not python (as was my original intention). It probably isn't nessecary to depend on the python2.3 versions of pyglade and pygtk either. There is no python-dbus. So unless I want to mix python- and python2.3- dependencies, I can't do that. In addition, the rebuilt package does not work on my system, but that is a story for another bug. I am still interested in this story, would you mind letting me know so that I can try to fix them both at the same time? -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#339923: Typo in package description
On Sat, Nov 19, 2005 at 06:33:48PM +0100, Loic Minier wrote: Package: zpkg Severity: minor Tags: patch Hi, There's a slight typo in the package description: The Zope Packaging Tool, or zpkg, is a tool used to build software distributions based on the Python distutils package. The generated distributions can be used like any other distuils-based distribution. s/distuils-based/distutils-based Fixed in my repository, but it will wait till the next upload. Cheers, -- Lo�c Minier [EMAIL PROTECTED] -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336804: [schooltool-dev] [Pkg-zope-developers] Bug#336804: schoolbell: includes a fr_FR.po translation instead of fr.po
On Thu, Nov 10, 2005 at 06:05:19AM +0100, Christian Perrier wrote: As explained in my original message, there is barely no reason to have different translations with country variants. Written French is the same, whether it's written in France, Canada, Belgium, Switzerland or other French-speaking countries. I agree, but I am not going to delete the fr_FR translation and would have no idea how to merge the two translations. I also have no control over how rosetta does things. What I can propose you is taking all the fr* translations, have a look at them along with the debian-l10n-french team, merge them in *one* translation, in concertation with the people mentioned in Last-Translator. Then you should be able to only use a fr.po file and probably request that all other translations are removed from Rosetta so that they don't come in again. While I agree with you in most points, I just simply don't have the time to do it. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338693: python-clientcookie: Please provide a python 2.4 version of clientcookie
Package: python-clientcookie Severity: normal It would be nice if there was a python 2.4 version of clientcookie. This is because I am packaging python-mechanize, which depends on python-clientcookie and would like to provide python 2.4 versions of this package. -- System Information: Debian Release: testing/unstable Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-9-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336804: [schooltool-dev] [Pkg-zope-developers] Bug#336804: schoolbell: includes a fr_FR.po translation instead of fr.po
On Tue, Nov 01, 2005 at 04:45:58PM +0100, Debian Bug Forwarder wrote: Package: schoolbell Version: N/A Severity: normal This package includes a fr_FR.po file which contains the French translation of the program strings. Could you please tell me exactly where, I struggle to find it: [EMAIL PROTECTED] ~/src/arch-pkg-zope/schoolbell/schoolbell-1.2.3 % find -iname 'fr_FR.po' We seem to have a number of french translations imported from rosetta, by far the most complete is the fr translation. I don't think deleting the other translations is a good idea. [EMAIL PROTECTED] ~/src/arch-pkg-zope/schoolbell/schoolbell-1.2.3/src/schoolbell/app % ls locales/fr*/* locales/fr_BE/LC_MESSAGES: schoolbell.po locales/fr_CA/LC_MESSAGES: schoolbell.po locales/fr_FR/LC_MESSAGES: schoolbell.po locales/fr/LC_MESSAGES: schoolbell.po -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336804: [schooltool-dev] [Pkg-zope-developers] Bug#336804: schoolbell: includes a fr_FR.po translation instead of fr.po
On Wed, Nov 09, 2005 at 11:27:15PM +0100, Christian Perrier wrote: Could you please tell me exactly where, I struggle to find it: This is found on the following page: http://www.debian.org/intl/l10n/po/fr_FR wow, thats quite nice, didn't know about it. We seem to have a number of french translations imported from rosetta, by far the most complete is the fr translation. I don't think deleting the other translations is a good idea. As explained in my original message, there is barely no reason to have different translations with country variants. Written French is the same, whether it's written in France, Canada, Belgium, Switzerland or other French-speaking countries. I agree, but I am not going to delete the fr_FR translation and would have no idea how to merge the two translations. I also have no control over how rosetta does things. In fact, I don't see any way to resolve these bugs, apart from letting them be a record. The fact that they come from Rosetta is not a big surprise to me as, unfortunately, Rosetta allows this without much control. SchoolTool doesn't have any translations except what arrives through rosetta. So far no translator has appeared who wants to work through subversion. For all its faults (and yes, I have some gripes), rosetta has been a good source of translations for us. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#272057: Status of ClientForm ITP
Hi Pawel, It's been over a year now since you filed this ITP on clientform. Are you still interested in packaging it? The reason I ask is because I need clientform packaged as it is a dependency of an ITP of mine, mechanize [1]. If not, please let us know. Regretfully I also have to think about the possibility of not getting a reply to this mail and so have to state my intention to take over this ITP in a week or so. [1] http://www.mail-archive.com/debian-wnpp@lists.debian.org/msg42650.html -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334620: [Pkg-zope-developers] Bug#334620: initscript zope3 action start failed
On Tue, Oct 18, 2005 at 08:40:26PM -0500, Leticia Larrosa wrote: /etc/init.d/zope3: line 6: /lib/lsb/init-functions: No such file or directory invoke-rc.d: initscript zope3, action start failed. Looks like a missing dependency on lsb-base. Perhaps you could try again with lsb-base installed? -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334279: ITP: cando -- student competency tracker
On Mon, Oct 17, 2005 at 02:52:04AM +0200, Alexander Schmehl wrote: Hi Brian! Hey Alex, * Brian Sutherland [EMAIL PROTECTED] [051016 20:47]: Extra ITP information: I am packaging this for unstable so that more people can use this, but do not think it is ready for release until it is more closely integrated with the SchoolTool packages. A serious bug will be filed to keep cando out of testing until then. Isn't that what experimental is for? The packages I have available are already in production at a few sites, so not that experimental. Also I want people to use them [1];) The people using them are also non-developers for whom adding experimental to their sources is downright dangerous. [1] http://www.perrier.eu.org/weblog/2005/09/30 -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334241: ITP: python-mechanize -- stateful programmatic web browsing
Package: wnpp Severity: wishlist * Package name: python-mechanize Version : 0.0.9a Upstream Author : Jhon J. Lee [EMAIL PROTECTED] * URL : http://wwwsearch.sourceforge.net/mechanize/ * License : BSD Description : stateful programmatic web browsing A library for browsing the web in python. Mechanize acts like a browser allowing you to do web scraping, functional testing of web sites and things no one has thought of yet. Among other things, mechanize: * Follows links * Fills in HTML forms * Automatically observes robots.txt * Has a browser history It was modelled after the Perl module WWW::Mechanize. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334241: ITP: python-mechanize -- stateful programmatic web browsing
On Sun, Oct 16, 2005 at 05:26:28PM +0200, Andreas Schuldei wrote: * Brian Sutherland [EMAIL PROTECTED] [2005-10-16 16:32:04]: Among other things, mechanize: * Follows links * Fills in HTML forms * Automatically observes robots.txt * Has a browser history does it speak java script? I doubt it, but am not completely sure. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334269: ITP: python-pullparser -- simple pull API for HTML parsing
Package: wnpp Severity: wishlist * Package name: python-pullparser Version : 0.0.6 Upstream Author : Jhon J. Lee [EMAIL PROTECTED] * URL : http://wwwsearch.sourceforge.net/pullparser/ * License : BSD Description : simple pull API for HTML parsing Many simple HTML parsing tasks are simpler this way than with the HTMLParser module. pullparser.PullParser is a subclass of HTMLParser.HTMLParser. After Perl's HTML::TokeParser. Additonal ITP info: python-pullparser is an unpackaged dependency required for python-mechanize (ITP: 334241). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334279: ITP: cando -- student competency tracker
Package: wnpp Severity: wishlist * Package name: cando Version : 2005.2.2 Upstream Authors: CanDo Developers [EMAIL PROTECTED] * URL : http://www.schooltool.org/products/cando * License : BSD Description : student competency tracker CanDo is an SchoolTool product that allows teachers and administrators to track student acquisition of competencies during a course. Using a database of competencies which students are expected to acquire, teachers can use CanDo to track and manage student progress in meeting their competency goals. Extra ITP information: I am packaging this for unstable so that more people can use this, but do not think it is ready for release until it is more closely integrated with the SchoolTool packages. A serious bug will be filed to keep cando out of testing until then. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332845: [Pkg-zope-developers] Bug#332845: Uncorrect named file
On Sun, Oct 09, 2005 at 12:12:17AM +0200, Sven Wilhelm wrote: Package: zope3 Version: 3.1.0-1 zope.configuration.config.ConfigurationExecutionError: zope.configuration.exceptions.ConfigurationError: Help Topic definition usr/lib/zope3/lib/python/zope/interface/README.txt does not exist in: File /usr/lib/zope3/lib/python/zope/app/apidoc/bookmodule/book.zcml, line 11.4-16.10 bookchapter id=interface title=Interfaces doc_path=README.txt parent=ifaceschema / Reason: This file is called README.ru.txt in the package. Fix:Rename the file and ZOPE starts as expected Are you using Ubuntu? This smells suspiciously like an Ubuntu specific bug to me;) Looking at the contents of the zope3 package in Debian: % dpkg-deb -c ~/zope3_3.1.0-1_i386.deb |grep zope/interface/README.txt -rw-r--r-- root/root 20630 2005-10-02 20:47:59 ./usr/lib/python2.4/site-packages/zope/interface/README.txt And now of the same package in Ubuntu: % dpkg-deb -c ~/python2.4-zopeinterface_3.1.0-1_i386.deb |grep zope/interface/README.txt % dpkg-deb -c ~/zope3_3.1.0-1_i386.deb |grep zope/interface/README.txt A suggested (untested) patch: % diff -u rules.old rules --- rules.old 2005-10-09 15:19:09.001609880 +0200 +++ rules 2005-10-09 15:21:01.413520672 +0200 @@ -162,11 +162,12 @@ /usr/bin/python2.4 setup.py install --prefix=$(PWD)/$(d_zif24)/usr -find debian/python*-zopeinterface -name '*.py[co]' | xargs rm -f - # Move README.txt to the right place + # Copy README.txt to the right place + # (Zope needs the README to be there, see 332845) set -x ; for dir in debian/python2*-zopeinterface ; do \ pkg=$$(basename $$dir) ; \ mkdir -p $$dir/usr/share/doc/$$pkg ; \ - mv $$(find $$dir -name README.txt) $$dir/usr/share/doc/$$pkg ; \ + cp $$(find $$dir -name README.txt) $$dir/usr/share/doc/$$pkg ; \ done # Remove interface module which has been split out -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329795: ITP: zpkg -- a tool to build software distributions based on the Python distutils package.
Package: wnpp Severity: wishlist * Package name: zpkg Version : 1.0.0 Upstream Author : Fred Drake fred at zope.com * URL : http://www.zope.org/Members/fdrake/zpkgtools/ * License : ZPL Description : a tool to build software distributions based on the Python distutils package. The Zope Packaging Tool, or zpkg, is a tool used to build software distributions based on the Python distutils package. The generated distributions can be used like any other distuils-based distribution. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.10-5-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317742: [Pkg-zope-developers] Bug#317742: pytz is bundled
On Sun, Jul 31, 2005 at 06:50:53PM +0200, Brian Sutherland wrote: On Mon, Jul 11, 2005 at 05:32:06PM +0900, Seo Sanghyeon wrote: Package: zope3-lib Version: 3.0.91-1 Severity: wishlist zope3-lib package bundles pytz. It should use python-tz package instead. To do this, python-tz needs to be built for Python 2.4. Maintainer CC'd. I will get my sponsor to upload this as soon as I am back from my holidays:) python2.4-tz should be in the archive now, I added a Replaces: zope3-lib which hopefully should take care of the upgrade. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317742: pytz is bundled
On Mon, Jul 11, 2005 at 05:32:06PM +0900, Seo Sanghyeon wrote: Package: zope3-lib Version: 3.0.91-1 Severity: wishlist zope3-lib package bundles pytz. It should use python-tz package instead. patch attached. It also changes the way docutils is removed so that `./debian/rules check` will be done against the currently installed python-docutils and saves CPU cycles:) To do this, python-tz needs to be built for Python 2.4. Maintainer CC'd. I will get my sponsor to upload this as soon as I am back from my holidays:) -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! diff -u -r zope3--debian--3.1--patch-1/control zope3--debian--3.1--patch-4/control --- zope3--debian--3.1--patch-1/control 2005-07-28 23:44:53.932604944 +0200 +++ zope3--debian--3.1--patch-4/control 2005-07-28 23:53:24.593972616 +0200 @@ -9,7 +9,7 @@ Package: zope3-lib Section: python Architecture: any -Depends: ${z3lib:Depends}, ${shlibs:Depends}, python-docutils (= 0.3.7) +Depends: ${z3lib:Depends}, ${shlibs:Depends}, python-docutils (= 0.3.7), python2.4-tz (= 2005i) Conflicts: zopex3-lib, python2.4-zopeinterface Replaces: zopex3-lib Provides: python2.4-zopeinterface diff -u -r zope3--debian--3.1--patch-1/rules zope3--debian--3.1--patch-4/rules --- zope3--debian--3.1--patch-1/rules 2005-07-28 23:44:53.955601448 +0200 +++ zope3--debian--3.1--patch-4/rules 2005-07-28 23:53:24.594972464 +0200 @@ -54,6 +54,11 @@ unpack-stamp: tar xfz $(zbase).tgz mv $(zbase) z + + : # Remove docutils and pytz modules packaged in separate packages + rm -rf z/Dependencies/docutils* + rm -rf z/Dependencies/pytz* + touch unpack-stamp configure: config-stamp @@ -166,9 +171,6 @@ ) endif - : # Remove docutils module packaged in a separate package - rm -rf $(d_lib)/$(pylibdir)/docutils - -find $(d_lib)/$(pylibdir) -depth -type d -empty -exec rmdir {} \; # for d in `find debian/$(PYVER)-zopeinterface -depth -type d -empty 2 /dev/null`; do \
Bug#278411: marked as done (SchoolBell should not be released with sarge)
On Mon, Jun 20, 2005 at 01:56:50PM -0700, Steve Langasek wrote: Yay, sarge is out. By the time etch comes around these packages will be ready for stable. So, is schooltool *currently* in a releasable state? If you don't think so, it would be nice to keep it out of testing until it is. Ok, I've re-opened this bug which should keep both schooltool and schoolbell out of testing. -- Brian Sutherland Metropolis - it's the first movie with a robot. And she's a woman. And she's EVIL!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#310304: [schooltool-dev] Bug#310304: schoolbell: no RESTive interface
On Mon, May 23, 2005 at 03:20:19AM +0200, Debian Bug Forwarder wrote: Hi, after an upgrade to version 1.0-1, I lost the RESTive interface. The webinterface is working fine (using default port 7180), just no-one is listening on port 7101. I tried on another machine with a fresh install, same result. Find attached the output of netstat and my config file. Hi Til, Rather a lot changed in the project between 0.9 and 1.0 upstream, mostly the project was ported from twisted/zope3 to pure zope3. This huge amount of work couldn't be done in the timeframe of one release, so quite a number of features had to wait until 1.1. This list list includes the RESTive interface which will re-appear in 1.1. There already is a release candidate for 1.1 [1] and release date is set to the 31st May. [1] http://www.schooltool.org/releases/schoolbell1.1/rc1 Thanks, -- Brian Sutherland It's 10 minutes, 5 if you walk fast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#286859: [schooltool] Bug#286859: schoolbell: Please switch to gettext-based debconf templates
On Thu, Jan 06, 2005 at 04:06:54PM +0100, Debian Bug Forwarder wrote: On Wed, Jan 05, 2005 at 08:12:37PM +0100, Christian Perrier wrote: Otherwise I would like to close this bug. Please don't do so. Please keep this bug as open until schoolbell gets removed. I'm not the only one providing such conversion patches, and it would be bad to have this [useless] work dupplicated. Please reduce its severity and mark it wontfix if you want, but don't close it... Hi Martin, A new schoolbell package was uploaded which uses debconf-po and included the style work you did on the schoolbell templates. So I am marking this bug done. Thanks for the help, -- Brian Sutherland It's 10 minutes, 5 if you walk fast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#297146: dpkg-reconfigure freezes
On Sun, Feb 27, 2005 at 03:31:22PM +0100, Eduard Bloch wrote: the topic says all. I see just Stopping SchoolTool: schoolbell. after answering the questions. ps shows me: openssl req -config /tmp/tmp.ck9pra -new -x509 -nodes -out /etc/schoolbell/schoolbell.cert.pem -keyout /etc/schoolbell/s choolbell.privkey.pem Could you try moving the mouse a lot? No, really, I'm mot joking, when you run out of randomness in /dev/random it can take a long time to generate an SSL certificate. Moving the mouse helps. -- Brian Sutherland It's 10 minutes, 5 if you walk fast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#295049: [schooltool] Bug#294997: schooltool: FTBFS (amd64/gcc-4.0): static declaration of 'SpecType' follows non-static declaration
merge 294997 295049 tags 294997 pending thanks On Mon, Feb 14, 2005 at 01:06:04PM +0200, Marius Gedminas wrote: On Sat, Feb 12, 2005 at 11:20:07PM +0100, Debian Bug Forwarder wrote: Package: schooltool Severity: normal Tags: patch When building 'schooltool' on amd64 with gcc-4.0, I get the following error: ... With the attached patch 'schooltool' can be compiled on amd64 using gcc-4.0. Thanks, I've forwarded the bug upstream to Zope 3 issue tracker: http://zope.org/Collectors/Zope3-dev/366 I was wondering how to do that. Brian, do you plan to build new schooltool/schoolbell packages with this patch applied? Andreas, please feel free to NMU. No, considering our status not in testing and that I have to bother my very busy sponsor for every upload. By the way, how do you tell the Debian BTS to merge duplicate bugs (294997, 295049)? look above, or at: http://www.debian.org/Bugs/server-control I will forward this mail to [EMAIL PROTECTED] shortly. -- Brian Sutherland It's 10 minutes, 5 if you walk fast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#294240: ITP: python-tz -- Python version of the Olson timezone database
Package: wnpp Severity: wishlist * Package name: python-tz Version : 2005a Upstream Author : Stuart Bishop [EMAIL PROTECTED] * URL : http://pytz.sourceforge.net/ * License : BSD like Description : Python version of the Olson timezone database python-tz brings the Olson tz database into Python. This library allows accurate and cross platform timezone calculations using Python 2.3 or higher. It also solves the issue of ambiguous times at the end of daylight savings, which you can read more about in the Python Library Reference (datetime.tzinfo). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#278410: Bug#278411 and Bug#278410: SchoolBell and SchoolTool should not be released with sarge
The status of these bugs have changed, partial database upgrades will be available from 0.8 to 1.0 and full upgrades thereafter. However, I still consider SchoolBell/SchoolTool unsuitable for release with sarge as the packages contain a large amount of a current checkout of the zope 3 trunk. The inclusion of these libraries will make security bugfix support difficult, if not impossible. -- Brian Sutherland It's 10 minutes, 5 if you walk fast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#282968: - Please reverse the removal of schoolbell
I previously asked for the removal of schoolbell on the basis that the codebase of schoolbell and schooltool had converged to having a difference of one line. However the codebases are going to diverge again, this time properly with minimal overlap. Also upstream requires different release schedules. Which I believe requires separate source packages. Could you reverse the removal of schoolbell and tell this muppet with tangled strings (me) what he should do? -- Brian Sutherland It's 10 minutes, 5 if you walk fast. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]