Bug#996393: pdfarranger git repo has moved
Package: pdfarranger Version: 1.6.2-3 The debian/upstream/metadata URLs for the pdfarranger package are no longer correct, the GitHub repo has moved. The correct URLs are now: Bug-Database: https://github.com/pdfarranger/pdfarranger/issues Bug-Submit: https://github.com/pdfarranger/pdfarranger/issues/new Repository: https://github.com/pdfarranger/pdfarranger.git Repository-Browse: https://github.com/pdfarranger/pdfarranger This change also affects the debian/watch file, which is why uscan is failing. HTH, Allison
Bug#948294: ITS: 4digits
Hi Boyuan, Removing the package from the archive seems like the right decision here. Upstream hasn't been updated since 2015. Thanks for offering to ITS, though. Allison
Bug#919951: Request about the /usr/bin/dune filename
On Tue, 22 Jan 2019 14:45:36 + Anil Madhavapeddy wrote: > Dear Debian project leader (CCed), we’ve resolved the rather > simple technical matter in this thread amicably by directly > communicating with the upstream software projects involved. Glad to hear it, that's the way it should be. :) > However, there are lots of references to what Debian ‘should’ > and ‘must’ do in the above quoted email, but very little clarity on > Ian Jackson’s actual authority to speak for Debian. Who is he, > and is he speaking for the Debian project (with insults and all)? > He appears to have resigned from the Debian Technical Committee > some years back, but I am not familiar with the internal structure > of your project. [...] > If he *doesn't* speak for Debian, then we’d love to be able to > directly speak to whoever resolves these matters so that the > hardworking Debian package maintainer for OCaml can get > on with his volunteer efforts without being harassed by Ian Jackson. As with many open source projects, Debian is a collection of volunteers who each represent the project in various ways in the course of their day-to-day contributions. We tend to be egalitarian, and while we have governing bodies and a project leader, those are more of a last resort when we can't sort things out any other way. Ian can speak for the Debian project at times (as may any Debian Developer), but most of the time he is expressing his own personal opinion. He is a long-term member of the Debian project, and we greatly respect his opinion. But, even he freely admits that he sometimes speaks more acerbically than the situation merits. > I hope that’s clear enough. Same here, but if it's not, I'm happy to pop over to your office two doors down to explain further. :) Allison
Bug#840930: vmware-nsx: FTBFS: AttributeError: 'module' object has no attribute 'SecurityGroup'
IIRC, in the OpenStack packaging sprint at DebCamp last week we agreed to remove vmware-nsx from unstable. (The package never made it to testing or any stable release.)
Bug#840930: vmware-nsx: FTBFS: AttributeError: 'module' object has no attribute 'SecurityGroup'
On 02/27/2017 05:34 PM, Thomas Goirand wrote: > > Yes, because it FTBFS as well. Thanks Thomas. How important would you rate vmware-nsx? It's currently removed from testing. It has no rdepends, so I'm thinking it's probably fine to leave it out of stretch, and fix it in unstable for future releases. (I'm just reviewing RC bugs for the OpenStack packages, there aren't many.) Allison
Bug#840930: vmware-nsx: FTBFS: AttributeError: 'module' object has no attribute 'SecurityGroup'
The version of the neutron package currently in unstable and stretch (9.1.1) is incompatible with the version of vmware-nsx in unstable (8.0.0). During the Newton release cycle, Neutron was changed to move SecurityGroup from: neutron.db.securitygroups_db to: neutron.db.models.securitygroup For the specific line of code failing in this FTBFS, see this change that was made in the 9.1.0 release of vmware-nsx: https://anonscm.debian.org/cgit/openstack/vmware-nsx.git/commit/?h=debian/newton=4950717f9550732f6655c97afda07ed401a37a0d The fix for this bug is to package a compatible version of vmware-nsx. Apparently the 9.1.0 package of vmware-nsx was created, but never uploaded to unstable: https://anonscm.debian.org/cgit/openstack/vmware-nsx.git/log/?h=debian/newton Allison
Bug#835860: RM: parrot -- ROM; unused; dead upstream
Package: ftp.debian.org Please remove parrot from unstable, since the upstream project is no longer developed or maintained. It has no rdeps in the archive. This removal includes: libparrot-dev | 6.6.0-1+b1 | mips64el libparrot-dev | 6.6.0-1+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x libparrot6.6.0 | 6.6.0-1+b1 | mips64el libparrot6.6.0 | 6.6.0-1+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x parrot |6.6.0-1 | source parrot | 6.6.0-1+b1 | mips64el parrot | 6.6.0-1+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x parrot-devel | 6.6.0-1+b1 | mips64el parrot-devel | 6.6.0-1+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x parrot-doc |6.6.0-1 | all parrot-minimal | 6.6.0-1+b1 | mips64el parrot-minimal | 6.6.0-1+b2 | amd64, arm64, armel, armhf, hurd-i386, i386, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, ppc64el, s390x We have discussed the removal of the parrot packages on the Debian Parrot Maintainers team mailing list, and on the upstream Parrot Developer mailing list. http://lists.alioth.debian.org/pipermail/pkg-parrot-devel/2016-August/000431.html http://lists.parrot.org/pipermail/parrot-dev/2016-July/007660.html Thanks, Allison
Bug#816241: quassel-client: notifications that mark taskbar entry also force immediate window focus
Package: quassel-client Version: 1:0.12.3-1 Severity: normal On the Cinnamon desktop in Stretch, when a quassel-client notification is set to "Mark taskbar entry" (which is set for all notifications by default), it has two effects: - Notification events immediately shift focus back to the quassel-client window. - If "Show message in a popup" is set, the popup flashes by so quickly, it's no more than a blue smudge in the upper right corner of the screen. The instant focus is quite disruptive. I frequently end up typing characters I meant for a completely different application into IRC. The notification integration for quassel-client with Cinnamon was brilliant in Jessie. I'm not sure what changed. I'm happy to dig into this further, but I'm not sure whether to look for the problem in the Quassel codebase, in Qt, or in Cinnamon. Thanks for any thoughts, Allison -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-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/dash Init: systemd (via /run/systemd/system) Versions of packages quassel-client depends on: ii dbus-x11 1.10.6-1 ii gawk 1:4.1.3+dfsg-0.1 ii libc6 2.21-8 ii libdbusmenu-qt5-2 0.9.3+15.10.20150604-1 ii libkf5configwidgets5 5.16.0-1 ii libkf5coreaddons5 5.16.0-1 ii libkf5notifications5 5.16.0-1 ii libkf5notifyconfig5 5.16.0-1 ii libkf5sonnetui5 5.16.0-1 ii libkf5textwidgets55.16.0-1 ii libkf5widgetsaddons5 5.16.0-1 ii libkf5xmlgui5 5.16.0-1 ii libphonon4qt5-4 4:4.8.3-2 ii libqt5core5a 5.5.1+dfsg-13 ii libqt5dbus5 5.5.1+dfsg-13 ii libqt5gui55.5.1+dfsg-13 ii libqt5network55.5.1+dfsg-13 ii libqt5webkit5 5.5.1+dfsg-2 ii libqt5widgets55.5.1+dfsg-13 ii libstdc++65.3.1-8 ii phonon4qt54:4.8.3-2 ii quassel-data 1:0.12.3-1 ii zlib1g1:1.2.8.dfsg-2+b1 quassel-client recommends no packages. quassel-client suggests no packages. -- no debconf information
Bug#699062: libsvn-web-perl: test failure caused by locale setting
Package: libsvn-web-perl Version: 0.63-1 The 0.63-1 version of libsvn-web-perl sets the locale for running tests in debian/rules with: override_dh_auto_test: dh_auto_test -- LC_CTYPE=C.UTF-8 On Ubuntu, this causes an FTBFS, which is resolved by changing it to: override_dh_auto_test: dh_auto_test -- LC_ALL=C.UTF-8 With this fix, it passes all tests, and the package builds successfully. See the Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/libsvn-web-perl/+bug/1106378 Thanks, Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#698665: Version bump requested
I'm happy to work on this update, if the current maintainer doesn't mind. I'll wait for a bit to give Patrick time to comment. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674213: gpsdrive: not installable in sid
Hi Hamish, What's the status on the upstream work here? Is it worth waiting for a new upstream release, or is it better to go ahead and package 2.11? Could the fixes for mapnik be applied to the 2.11 packages as patches, or are the changes too extensive for that? Note that this FTBFS has been (temporarily) resolved in the latest Debian packages of 2.10 with patches disabling mapnik in the build. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694808: libv8: CVE-2012-5120 CVE-2012-5128
The details on these two CVE's are 403 for me: CVE-2012-5120 https://code.google.com/p/chromium/issues/detail?id=150729 CVE-2012-5128 https://code.google.com/p/chromium/issues/detail?id=157124 So presumably they're still embargoed and only accessible to certain members of pkg-javascript. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#471927: [Scratch] Scratch 1.4 source code released under GPL v2
On 03/30/2012 04:10 PM, Miriam Ruiz wrote: It works for me with squeak-vm 4.0.3.2202 (squeeze) but when trying to run it on squeak-vm 4.4.7 (wheezy) I just get a black screen [1] [2] According to jredrejo, the modification causing this problem might be related to the changes made to the squeak-vm to be able to run it with composite managers and compiz. Okay, makes sense. Ubuntu is shipping squeak-vm 4.4.7 in both Oneiric and Precise, so we'd have to wait on a fix for this too. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#471927: [Scratch] Scratch 1.4 source code released under GPL v2
2012/3/28 Amos Blanton a...@scratch.mit.edu: The Scratch Team has re-released the Scratch 1.4 source code under the GPL v2. This is great news! :) On 03/28/2012 01:34 PM, Miriam Ruiz wrote: Yay! I'm going to package it for Debian Double-check on the DFSG and the Scratch trademark policy. The code itself will be fine under the DFSG, but the trademark policy may not satisfy The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software. Worst-case, Debian would just need to use a different name/logo, like it does with Iceweasel and Icedove. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650453: magics++: as-needed.patch doesn't apply, causing, FTBFS
I looked into it a little further last night, and the error was on the AC_CHECK_LIB check for libemosR64, failing with errors such as: /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libemosR64.so: undefined reference to `sqrtq' This appears to be related to the --no-add-needed option. The fix is to add the relevant libraries directly to LIBS (they previously would have been pulled in indirectly by -lemosR64). The attached patch fully fixes the FTBFS, tested on sid and Ubuntu precise. It doesn't address the questions about the debian-changes-* patches and failure to fully clean before a second run of debuild, I was just focused on clearing the FTBFS. Hope this helps, and gives you a little more free time on the weekend. === modified file 'debian/as-needed.patch' --- debian/as-needed.patch 2011-09-13 13:45:47 + +++ debian/as-needed.patch 2011-12-06 09:30:04 + @@ -3,12 +3,12 @@ Note that this patch is applied by ./debian/rules AFTER autoreconf is run; it cannot be applied in ./debian/patches Bug-Debian: http://bugs.debian.org/347650 -Last-Updated: 2011-09-13 +Last-Updated: 2011-12-05 Forwarded: no ltmain.sh.orig 2011-09-13 10:05:45.0 +0100 -+++ ltmain.sh 2011-09-13 10:22:40.0 +0100 -@@ -5500,6 +5500,11 @@ +--- ltmain.sh.orig 2011-12-05 23:13:53.614777184 + ltmain.sh 2011-12-05 23:21:58.310794860 + +@@ -5512,6 +5512,11 @@ continue ;; @@ -20,19 +20,19 @@ -export-symbols | -export-symbols-regex) if test -n $export_symbols || test -n $export_symbols_regex; then func_fatal_error more than one -exported-symbols argument is not allowed -@@ -6150,6 +6155,15 @@ +@@ -6163,6 +6168,15 @@ lib= found=no case $deplib in -+ -Wl,--as-needed) -+ if test $linkmode,$pass = prog,link; then -+ compile_deplibs=$deplib $compile_deplibs -+ finalize_deplibs=$deplib $finalize_deplibs -+ else -+ deplibs=$deplib $deplibs -+ fi -+ continue -+ ;; - -mt|-mthreads|-kthread|-Kthread|-pthread|-pthreads|--thread-safe|-threads) ++ -Wl,--as-needed) ++ if test $linkmode,$pass = prog,link; then ++ compile_deplibs=$deplib $compile_deplibs ++ finalize_deplibs=$deplib $finalize_deplibs ++ else ++ deplibs=$deplib $deplibs ++ fi ++ continue ++ ;; + -mt|-mthreads|-kthread|-Kthread|-pthread|-pthreads|--thread-safe \ + |-threads|-fopenmp|-openmp|-mp|-xopenmp|-omp|-qsmp=*) if test $linkmode,$pass = prog,link; then - compile_deplibs=$deplib $compile_deplibs === modified file 'debian/changelog' --- debian/changelog 2011-10-20 10:40:35 + +++ debian/changelog 2011-12-06 18:46:00 + @@ -1,3 +1,14 @@ +magics++ (2.12.9-6) UNRELEASED; urgency=low + + * Update debian/as-needed.patch so it applies to changed +config/ltmain.sh. + * debian/rules: Add -lm -lquadmath -lgfortran to LIBS in configure +line to directly link libraries that are needed. + * Update debian/patches/dynamic_link.patch to add +-lm -lquadmath -lgfortran. + + -- Allison Randal alli...@lohutok.net Tue, 06 Dec 2011 10:43:17 -0800 + magics++ (2.12.9-5) unstable; urgency=low * Recommends: pkg-config in -dev package. === modified file 'debian/patches/dynamic_link.patch' --- debian/patches/dynamic_link.patch 2011-07-08 17:16:45 + +++ debian/patches/dynamic_link.patch 2011-12-06 18:12:07 + @@ -1,20 +1,20 @@ Description: Link libMagPlus.so.3.0.0 against extra libraries that are provided in dynamic form by Debian. Author: Alastair McKinstry mckins...@debian.org -Last-Updated: 2010-07-23 +Last-Updated: 2011-12-06 Forwarded: no -Index: Magics++-2.12.1/configure.ac +Index: debbug-650453/configure.ac === Magics++-2.12.1.orig/configure.ac 2011-02-14 14:26:20.0 + -+++ Magics++-2.12.1/configure.ac 2011-02-14 14:27:00.0 + -@@ -747,7 +747,9 @@ +--- debbug-650453.orig/configure.ac 2011-12-06 16:22:38.194231000 + debbug-650453/configure.ac 2011-12-06 18:09:26.757261761 + +@@ -767,7 +767,9 @@ fi AC_SUBST(cairo) - +# Add dynamic libs needed by Debian -+LIBS=$CAIRO_LIBS $LIBS -lemosR64 -lgrib_api -lterralib -lstdc++ -lm $NETCDF_LIBS ++LIBS=$CAIRO_LIBS $LIBS -lemosR64 -lgrib_api -lterralib -lstdc++ -lm -lquadmath -lgfortran $NETCDF_LIBS +LDFLAGS=$CAIRO_LDFLAGS $LDFLAGS -Wl,--as-needed # Autoheader === modified file 'debian/rules' --- debian/rules 2011-09-24 15:05:00 + +++ debian/rules 2011-12-06 18:46:30 + @@ -37,7 +37,7 @@ dh_auto_configure -- \ --enable-bufr --enable-static --enable-cairo --with-emos-libraries=/usr/lib \ --with-terralib=/usr --enable-python \ - LDFLAGS=-L$(shell pwd)/src/.libs -Wl,--as-needed LIBS= -lX11 -lpng12 -lz + LDFLAGS=-L$(shell pwd)/src/.libs -Wl,--as-needed LIBS= -lX11 -lm -lquadmath -lgfortran -lpng12 -lz override_dh_auto_test check: echo Tests disabled; see README-testfailures.txt
Bug#650453: magics++: as-needed.patch doesn't apply, causing, FTBFS
On 12/06/2011 01:15 PM, Julien Cristau wrote: On Tue, Dec 6, 2011 at 11:41:00 -0800, Allison Randal wrote: /usr/lib/gcc/x86_64-linux-gnu/4.6/../../../../lib/libemosR64.so: undefined reference to `sqrtq' That sounds like a bug in libemos. It's actually an expected (even intended) result of compiling with --no-add-needed. See: http://wiki.debian.org/ToolChain/DSOLinking And the documentation I wrote on the same transition in Ubuntu: https://wiki.ubuntu.com/NattyNarwhal/ToolchainTransition#Indirect_Linking_for_Shared_Libraries Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650453: magics++: as-needed.patch doesn't apply, causing, FTBFS
On 12/06/2011 02:48 PM, Julien Cristau wrote: I know about no-add-needed, but that doesn't make it ok for a library such as libemosR64.so to have undefined symbols. It's also possible to make the fix for the linking flags in libemos instead. If -lm -lquadmath -lgfortran are really only used by libemos, then that would be the more correct fix. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650453: magics++: as-needed.patch doesn't apply, causing, FTBFS
The attached file is an update for the as-needed.patch file, and applies
cleanly during the build. However, the package is still FTBFS with this
change, failing later in override_dh_auto_configure with:
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=${prefix}/include --mandir=${prefix}/share/man
--infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--libdir=${prefix}/lib/x86_64-linux-gnu
--libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode
--disable-dependency-tracking --enable-bufr --enable-static
--enable-cairo --with-emos-libraries=/usr/lib --with-terralib=/usr
--enable-python LDFLAGS=-L/tmp/buildd/magics++-2.12.9/src/.libs
-Wl,--as-needed LIBS= -lX11 -lpng12 -lz returned exit code 1
make[1]: *** [override_dh_auto_configure] Error 255
make[1]: Leaving directory `/tmp/buildd/magics++-2.12.9'
make: *** [build] Error 2
Author: Alastair McKinstry mckins...@debian.org
Description: Patch to ensure -Wl,--as-needed is NOT reordered by libtool.
Note that this patch is applied by ./debian/rules AFTER autoreconf is run;
it cannot be applied in ./debian/patches
Bug-Debian: http://bugs.debian.org/347650
Last-Updated: 2011-12-05
Forwarded: no
--- ltmain.sh.orig 2011-12-05 23:13:53.614777184 +
+++ ltmain.sh 2011-12-05 23:21:58.310794860 +
@@ -5512,6 +5512,11 @@
continue
;;
+ -Wl,--as-needed)
+deplibs=$deplibs $arg
+continue
+;;
+
-export-symbols | -export-symbols-regex)
if test -n $export_symbols || test -n $export_symbols_regex; then
func_fatal_error more than one -exported-symbols argument is not allowed
@@ -6163,6 +6168,15 @@
lib=
found=no
case $deplib in
+ -Wl,--as-needed)
+ if test $linkmode,$pass = prog,link; then
+ compile_deplibs=$deplib $compile_deplibs
+ finalize_deplibs=$deplib $finalize_deplibs
+ else
+ deplibs=$deplib $deplibs
+ fi
+ continue
+ ;;
-mt|-mthreads|-kthread|-Kthread|-pthread|-pthreads|--thread-safe \
|-threads|-fopenmp|-openmp|-mp|-xopenmp|-omp|-qsmp=*)
if test $linkmode,$pass = prog,link; then
Bug#651018: libsoup2.4: multiarch support for libsoup*
Source: libsoup2.4
Version: 2.36.1-1
Tags: patch
Hi,
I'm at the Portland Bug Squashing Party today. Please consider applying
the following patch, which adds multiarch support to libsoup2.4 and
libsoup-gnome2.4.
See http://wiki.debian.org/Multiarch/Implementation for more details.
Thanks,
Allison
diff -Nru libsoup2.4-2.36.1/debian/changelog libsoup2.4-2.36.1/debian/changelog
--- libsoup2.4-2.36.1/debian/changelog 2011-11-27 17:17:23.0 +
+++ libsoup2.4-2.36.1/debian/changelog 2011-12-04 23:52:35.0 +
@@ -1,3 +1,9 @@
+libsoup2.4 (2.36.1-2) UNRELEASED; urgency=low
+
+ * Transition to multiarch.
+
+ -- Allison Randal alli...@lohutok.net Sun, 04 Dec 2011 22:32:53 +
+
libsoup2.4 (2.36.1-1) unstable; urgency=low
[ Martin Pitt ]
diff -Nru libsoup2.4-2.36.1/debian/compat libsoup2.4-2.36.1/debian/compat
--- libsoup2.4-2.36.1/debian/compat 2011-07-29 01:29:01.0 +
+++ libsoup2.4-2.36.1/debian/compat 2011-12-04 22:05:06.0 +
@@ -1 +1 @@
-8
+9
diff -Nru libsoup2.4-2.36.1/debian/control.in
libsoup2.4-2.36.1/debian/control.in
--- libsoup2.4-2.36.1/debian/control.in 2011-11-17 15:47:57.0 +
+++ libsoup2.4-2.36.1/debian/control.in 2011-12-05 00:30:53.0 +
@@ -3,8 +3,8 @@
Priority: optional
Maintainer: Debian GNOME Maintainers
pkg-gnome-maintain...@lists.alioth.debian.org
Uploaders: @GNOME_TEAM@
-Build-Depends: debhelper (= 8),
- cdbs (= 0.4.90),
+Build-Depends: debhelper (= 8.1.3~),
+ cdbs (= 0.4.93~),
gnome-pkg-tools,
libglib2.0-dev (= 2.30.0),
glib-networking (= 2.28.4),
@@ -23,6 +23,7 @@
Package: libsoup2.4-dev
Architecture: any
+Multi-Arch: same
Section: libdevel
Depends: ${misc:Depends},
libsoup2.4-1 (= ${binary:Version}),
@@ -56,6 +57,8 @@
Package: libsoup2.4-1
Section: libs
Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends},
${shlibs:Depends},
glib-networking (= 2.28.4)
@@ -112,6 +115,8 @@
Package: libsoup-gnome2.4-1
Section: libs
Architecture: any
+Multi-Arch: same
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends},
${shlibs:Depends}
Description: HTTP library implementation in C -- GNOME support library
@@ -142,6 +147,7 @@
Package: libsoup-gnome2.4-dev
Architecture: any
+Multi-Arch: same
Section: libdevel
Depends: ${misc:Depends},
libsoup-gnome2.4-1 (= ${binary:Version}),
diff -Nru libsoup2.4-2.36.1/debian/gir1.2-soup-2.4.install
libsoup2.4-2.36.1/debian/gir1.2-soup-2.4.install
--- libsoup2.4-2.36.1/debian/gir1.2-soup-2.4.install2011-07-29
01:30:15.0 +
+++ libsoup2.4-2.36.1/debian/gir1.2-soup-2.4.install2011-12-04
23:55:14.0 +
@@ -1 +1 @@
-usr/lib/girepository-1.0
+usr/lib/*/girepository-1.0/* usr/lib/girepository-1.0
diff -Nru libsoup2.4-2.36.1/debian/libsoup-gnome2.4-1.install
libsoup2.4-2.36.1/debian/libsoup-gnome2.4-1.install
--- libsoup2.4-2.36.1/debian/libsoup-gnome2.4-1.install 2011-07-29
01:30:40.0 +
+++ libsoup2.4-2.36.1/debian/libsoup-gnome2.4-1.install 2011-12-04
22:09:10.0 +
@@ -1 +1 @@
-usr/lib/libsoup-gnome-2.4.so.*
+usr/lib/*/libsoup-gnome-2.4.so.*
diff -Nru libsoup2.4-2.36.1/debian/libsoup-gnome2.4-dev.install
libsoup2.4-2.36.1/debian/libsoup-gnome2.4-dev.install
--- libsoup2.4-2.36.1/debian/libsoup-gnome2.4-dev.install 2011-07-29
01:31:24.0 +
+++ libsoup2.4-2.36.1/debian/libsoup-gnome2.4-dev.install 2011-12-04
22:25:08.0 +
@@ -1,5 +1,5 @@
usr/include/libsoup-gnome-2.4
-usr/lib/libsoup-gnome-2.4.so
-usr/lib/libsoup-gnome-2.4.a
-usr/lib/pkgconfig/libsoup-gnome-2.4.pc
+usr/lib/*/libsoup-gnome-2.4.so
+usr/lib/*/libsoup-gnome-2.4.a
+usr/lib/*/pkgconfig/libsoup-gnome-2.4.pc
usr/share/gir-1.0/SoupGNOME-2.4.gir
diff -Nru libsoup2.4-2.36.1/debian/libsoup2.4-1.install
libsoup2.4-2.36.1/debian/libsoup2.4-1.install
--- libsoup2.4-2.36.1/debian/libsoup2.4-1.install 2011-07-29
01:30:19.0 +
+++ libsoup2.4-2.36.1/debian/libsoup2.4-1.install 2011-12-04
22:12:13.0 +
@@ -1 +1 @@
-usr/lib/libsoup-2.4*.so.*
+usr/lib/*/libsoup-2.4*.so.*
diff -Nru libsoup2.4-2.36.1/debian/libsoup2.4-dev.install
libsoup2.4-2.36.1/debian/libsoup2.4-dev.install
--- libsoup2.4-2.36.1/debian/libsoup2.4-dev.install 2011-07-29
01:31:16.0 +
+++ libsoup2.4-2.36.1/debian/libsoup2.4-dev.install 2011-12-04
22:43:04.0 +
@@ -1,5 +1,5 @@
usr/include/libsoup-2.4
-usr/lib/libsoup-2.4.so
-usr/lib/libsoup-2.4.a
-usr/lib/pkgconfig/libsoup-2.4.pc
+usr/lib/*/libsoup-2.4.so
+usr/lib/*/libsoup-2.4.a
+usr/lib/*/pkgconfig/libsoup-2.4.pc
usr/share/gir-1.0/Soup-2.4.gir
diff -Nru libsoup2.4-2.36.1/debian/rules libsoup2.4-2.36.1/debian/rules
--- libsoup2.4-2.36.1/debian/rules 2011-07-29 01:22:28.0 +
+++ libsoup2.4-2.36.1/debian/rules 2011-12-04 23:56:56.0 +
@@ -10,5
Bug#646446: gpsdrive: FTBFS: mapnik.cpp:33:15: error: 'mapnik::Image32' has not, been declared
Source: gpsdrive
Version: 2.10~pre4-6.dfsg-5.1
Severity: serious
Tags: patch
The gpsdrive package is FTBFS with version 2.0.0 of the mapnik library,
which is the current version in Debian wheezy and sid, and Ubuntu
precise. The FTBFS occurs because the APIs of the new 2.0.0 version of
Mapnik are backward-incompatible to the old 0.7.1 version of Mapnik (see
https://github.com/mapnik/mapnik/wiki/Mapnik2).
Note, there is a Debian bug requesting to update the gpsdrive packages
to version 2.11 (Bug #591260), however this will not help resolve the
FTBFS, because 2.11 of gpsdrive is also FTBFS with mapnik version 2.0.0.
Since I'm not sure when or if the gpsdrive developers plan to migrate to
Mapnik 2.0.0, I've submitted a patch to the Ubuntu package that disables
the optional mapnik library in the gpsdrive packages. Attaching the
patch, for Debian upstream application. (I haven't made/tested the minor
changes needed for precise-unstable.)
Allison
=== modified file 'debian/README.Debian'
--- debian/README.Debian 2008-08-31 17:40:05 +
+++ debian/README.Debian 2011-12-01 22:27:04 +
@@ -1,6 +1,14 @@
gpsdrive for Debian
---
+Using gpsdrive with mapnik 2.0
+--
+
+* Gpsdrive is incompatible with the new APIs of mapnik 2.0.0. This
+ optional library is now disabled in the package.
+
+ -- Allison Randal alli...@canonical.com Thu, 01 Dec 2011 12:48:22 -0800
+
Upgrading from gpsdrive 2.09 (etch)
-
* The mysql database schema has been changed.
=== modified file 'debian/changelog'
--- debian/changelog 2011-11-23 23:34:54 +
+++ debian/changelog 2011-12-01 22:55:21 +
@@ -1,3 +1,12 @@
+gpsdrive (2.10~pre4-6.dfsg-5ubuntu4) precise; urgency=low
+
+ * Disable optional mapnik libraries, gpsdrive is incompatible with
+APIs of mapnik version 2.0.0.
+ * debian/patches/107-fix-disable-mapnik.dpatch:
+Fix known bug with gpsdrive-2.10pre4 when disabling Mapnik library.
+
+ -- Allison Randal alli...@canonical.com Thu, 01 Dec 2011 12:48:22 -0800
+
gpsdrive (2.10~pre4-6.dfsg-5ubuntu3) precise; urgency=low
* Rebuild for libmysqlclient transition
=== modified file 'debian/control'
--- debian/control 2010-07-26 06:41:40 +
+++ debian/control 2011-12-01 21:39:32 +
@@ -6,7 +6,7 @@
Uploaders: Andreas Putzo andr...@putzo.net, Francesco Paolo Lovergine fran...@debian.org
DM-Upload-Allowed: yes
Build-Depends: debhelper (= 7), automake1.9, libtool, pkg-config, libpcre3-dev, libgtk2.0-dev,libart-2.0-dev, libxml2-dev, libmysqlclient-dev,
- autotools-dev, dpatch, libmapnik-dev (= 0.6), libboost-dev, libboost-filesystem-dev, libboost-serialization-dev, libdbus-glib-1-dev
+ autotools-dev, dpatch, libboost-dev, libboost-filesystem-dev, libboost-serialization-dev, libdbus-glib-1-dev, libltdl-dev (= 2.4)
Standards-Version: 3.8.4
Homepage: http://gpsdrive.de
Vcs-Svn: svn://svn.debian.org/svn/pkg-grass/packages/gpsdrive/trunk
@@ -40,7 +40,7 @@
Package: gpsdrive-scripts
Architecture: all
-Depends: gpsdrive, ${perl:Depends}, python, python-imaging, python-mapnik, libdbi-perl, libdbd-mysql-perl, libdate-manip-perl, libfile-slurp-perl,
+Depends: gpsdrive, ${perl:Depends}, python, python-imaging, libdbi-perl, libdbd-mysql-perl, libdate-manip-perl, libfile-slurp-perl,
libmime-base64-perl, libtime-local-perl, libwww-curl-perl, libwww-mechanize-perl, libxml-parser-perl, libxml-simple-perl, libxml-twig-perl,
libxml-writer-perl, perlmagick, perl-tk
Description: Various scripts for gpsdrive
=== modified file 'debian/gpsdrive-scripts.install'
--- debian/gpsdrive-scripts.install 2008-03-26 18:35:38 +
+++ debian/gpsdrive-scripts.install 2011-12-01 20:56:19 +
@@ -5,7 +5,7 @@
usr/bin/gpspoint2gpsdrive.pl
usr/bin/gpsreplay
usr/bin/poi-manager.pl
-usr/bin/gpsdrive_mapnik_gentiles.py
+#usr/bin/gpsdrive_mapnik_gentiles.py
usr/share/perl5/Geo/Filter/*usr/share/perl5/Geo/Gpsdrive/Filter
usr/share/perl5/Geo/GPX/* usr/share/perl5/Geo/Gpsdrive/GPX
usr/share/perl5/Geo/Geometry.pm usr/share/perl5/Geo/Gpsdrive
=== modified file 'debian/gpsdrive.install'
--- debian/gpsdrive.install 2008-08-31 17:40:05 +
+++ debian/gpsdrive.install 2011-12-01 20:55:54 +
@@ -2,5 +2,5 @@
usr/bin/friendsd2
usr/share/applications/gpsdrive.desktop
usr/share/gpsdrive/map_koord.txt
-usr/share/gpsdrive/mapnik/osm.xml
+#usr/share/gpsdrive/mapnik/osm.xml
usr/share/map-icons/icons.xml usr/share/gpsdrive/map-icons/
=== modified file 'debian/patches/00list'
--- debian/patches/00list 2011-07-05 12:30:16 +
+++ debian/patches/00list 2011-12-01 22:35:18 +
@@ -22,3 +22,4 @@
104-lp-325288
105-fix-xcursor-check.dpatch
106-add-boost-links.dpatch
+107-fix-disable-mapnik.dpatch
=== added file 'debian/patches/107-fix-disable-mapnik.dpatch'
--- debian/patches/107-fix-disable-mapnik.dpatch 1970-01-01 00:00:00 +
+++ debian/patches/107-fix-disable-mapnik.dpatch 2011-12-01 22:37:18 +
@@ -0,0 +1,24 @@
+#! /bin/sh
Bug#648569: ITA: 4digits - number-guessing game aka Bulls and Cows
Package: wnpp Severity: normal The package 4digits was orphaned and removed from Debian in 2008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479098 But, the upstream developer has continued working on it, and recently submitted it to Ubuntu's Application Review Board. Rather than making this an Ubuntu-only package, it seems to make sense to adopt the package upstream in Debian. As mentioned in the Debian bug, 4digits is not superseded by gnome-mastermind, it's a different game. A much older game, in fact, (by a century or more) which may have inspired the creation of Mastermind. See, the wikipedia page, which singles out this particular developer's work as the example implementation: http://en.wikipedia.org/wiki/Bulls_and_cows I've imported the old packaging into a git repository and updated it for the new 1.0 release and for DEP-5 and other current best practices. This work is in a temporary github repo: https://github.com/allisonrandal/pkg-4digits And, I've also submitted an updated package to mentors.debian.net: http://mentors.debian.net/package/4digits I'll be mentoring the developer in how to maintain his debian/ packaging files. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#642175: remove RPM spec file generator, 02_spec.dpatch
Package: libnet-server-perl Version: 0.99-2 Severity: normal Downstream in Ubuntu, we've had an FTBFS in libnet-server-perl (version 0.99-2ubuntu1) in Oneiric, caused by a missing value for $version in the file Net-Server.spec.PL. This appears to be related to changes in the behavior of MakeMaker. https://launchpadlibrarian.net/79887943/buildlog_ubuntu-oneiric-i386.libnet-server-perl_0.99-2ubuntu1_FAILEDTOBUILD.txt.gz The weird thing about the file Net-Server.spec.PL, is that it's a script to automatically generate an RPM spec file. This file is not in the upstream Perl module, it is added by the patch 02_spec.dpatch, which first appeared in the Debian packages in version 0.87-1 in 2004. In this same release 0.87, the same file was removed from the upstream Perl module (it was in the Perl module tarball in version 0.86 http://cpansearch.perl.org/src/BBB/Net-Server-0.86/, and removed in version 0.87 http://cpansearch.perl.org/src/BBB/Net-Server-0.87/). It looks suspiciously like the patch 02_spec.dpatch may be unnecessary. I rebuilt the packages without the patch, and have encountered no problems. The only output from the spec file generator is the RPM spec file, so it's not affecting other parts of build process. The patch was added during a fairly chaotic period for libnet-server-perl, involving a changeover in upstream maintainers for the module in CPAN, and a changeover in Debian maintainers. I reviewed the FTBFS in Ubuntu at Scott Kitterman's request, and am recommending the solution of removing the patch 02_spec.dpatch, rather than continuing to maintain an RPM spec file generator that the upstream developers abandoned 6 years ago. Debian may want to consider the same fix. HTH, Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636944: [Pkg-parrot-devel] Bug#636944: Please binNMU parrot on i386
On 08/09/2011 05:03 PM, Dominique Dumont wrote:
IMHO, there are 2 long-term solutions:
- without ffi: as kibi suggested, this requires a --with{,out}-libffi flag in
parrot's Configure.pl. In the meantime, the binNMU on i386 will achieve the
same result.
- with ffi: parrot needs a build-dep on libfffi-dev and libparrot-dev needs a
dependency on libffi-dev. Then rakudo needs to be re-built for all arches.
Only upstream parrot people know what's best.
Allison, what do you think ?
I've been thinking about it, and talking with other Parrot devs. The
thing is, libffi is entirely optional for Parrot. When it's present at
compile-time, Parrot will use it, and when it's not, Parrot uses a
different method for linking to C libraries (precompiled signature
thunks). It's not clear yet in the long-term which method will be
preferred in Parrot, so I've been debating which method we should choose
in the Debian packaging.
(What is clear is that we need to use the provided Parrot configure
flags to explicitly choose one method, rather than relying on the
dynamic configuration options to choose a method based on what's
installed at compile-time. For packaging, we need the builds for all
architectures to be the same, no matter what's installed on the build
machine.)
Weighing the options, it is certain than parrot+libffi is slower than
parrot+thunks at runtime, but it's unlikely that the slow-down is
significant enough to be noticed by Rakudo. On the other hand, there is
a chance that parrot+libffi is smaller (for install footprint) than
parrot+thunks, but again, unlikely that the size difference is
significant. Both of these questions need more testing and benchmarking
to be certain.
On the whole, if there's no radical difference in performance or
resources, I'm inclined to go with the conservative strategy for now,
and not add any additional dependencies to the Parrot packages until
it's clear that we need them. This means configuring Parrot in Debian
using the --without-libffi option (which already exists), to guarantee
that all packages on all architectures are built without libffi.
Allison
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636300: debian-maintainers: Please add Allison Randal as a Debian Maintainer
Package: debian-maintainers Severity: normal Tags: patch Please add my key to the DM keyring. I've attached a jetring changeset. My primary GPG UID is alli...@lohutok.net, but I use the UID alli...@parrot.org for packaging Parrot. Thanks, Allison Comment: Add Allison Randal alli...@lohutok.net as a Debian Maintainer Date: Mon, 01 Aug 2011 19:56:29 -0700 Action: import Recommended-By: Colin Watson cjwat...@debian.org, Manoj Srivastava sriva...@ieee.org Agreement: http://lists.debian.org/debian-newmaint/2011/07/msg00044.html Advocates: http://lists.debian.org/debian-newmaint/2011/07/msg00043.html http://lists.debian.org/debian-newmaint/2011/07/msg00048.html Data: -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.4.10 (GNU/Linux) mQINBE4mIWQBEAC/GG/wr5dfmJsNoNyzysDPD+vgUq2ShNIEiDEdz4xCYJCGmMxG 70lNboMl+rmnEbZzBP78AC5rKyqRCvPaP0VY554TUlYh6EFWR89g2l0dIUyyb25P Vo/7PwsfoGM3hjXbkxUurPteIOMaSah3ir+snfAspkLumrFszLAQphdQZQLC1PmL ZteNvcC4uIlAZugSE8hkH5Kuh9ZCRcPvEDRM1QrL8TU6fI4BMQiYOVmpGhVLfGcG pcamZzI4I/b/hu6MO8KFoZNpiaziztRAMZR3JZorQuakYISFOZlLBtdlb0ScR4Na KkJL8G9Ew8RVuL5iWlkEKCmFWUq3ziqISonr1nxFkOdiGDWX+vuC7WJSZQU373bW vXOquDYk96pZ+VnjZGu4yJs1ai+mktydoAs9DqJP98GB8jpJS1ePHhn9LyJrAE5J yCYzB/locs/1lcG286TOwKZ2Gx+q1RDeoUVkbWGWPwP2qe4Pa/sLhyC2b2fN/c80 Vtv6fwXgpaQvqAjvivVlHq1YtVRqY+1WsqaSsjpyWAU7p2ToYRMomj5MsVF2nVHO kcGALu05pN96+b7twXAuK5lKN/2Vn99aAH4WoS/2bolBII2pZvEyN8VGW1b8r0Bu J0mq+L7k6LDJVzVO7QcxBrDrnOOfY51psF3L9GYyXJv4xIGNdUzR0SD/swARAQAB tC1BbGxpc29uIFJhbmRhbCA8YWxsaXNvbi5yYW5kYWxAY2Fub25pY2FsLmNvbT6J AjcEEwEIACEFAk4qZ94CGwMFCwkIBwMFFQoJCAsFFgIDAQACHgECF4AACgkQloj/ wceBAt91zw/9FnGgrsdH4zFfoVZeiUWpuhgYpqY6EgWgHNI4yXeVkz3xaIp99CbF 4JJa5CS/pIc9dMxRgFW3qlbs61wfMlWUD72eqGfotfvSLPwBBs1RNE1K06CXJCN8 S3HLZEAstxitZdJtbIjEOyZgsv34qvGua5BAvZi5GKi4CkumdDH85yvsDHvPcu1R mAi12Fsk+3h1uD2maSBYIDI0O7iYovXj3Z2B/nBQ+NNagj27CMDJypH8PpvBwHit GPwI14Drlq5Tc3mfDhS8KjiHDL6iXZOPKgBFWHvaV0lUXSmDdcEjMZXQdP8fceP/ MtVof4kfnTLsp105BTPpuJuyJFs0ERtHyrmxGVMse6tERrdvA3jpS6INjB8mJwdL XavUhNReptiivnizymPJ4K7Rv/CjNDEf+bceHZUt/Y8zMx0hc5JSC47QyWHPz91R sq2iWod1mom2beIKOGEhD4zCc4gmCXSVe4+UQG8xiui4uz5jG6FeX7/YSa94dYZo O/YcErAD6yuNxdT5PJ6Q8I0Mg4wzXWkDsRJ//d5DBF0TB18k9Ky+mw9NkEAk7jw0 6pGlWReyA0jT52mwT8ELKbXVXkCKL+m6Q0nEo9keefvCPNr7z0dV0W81H1i6h9Z5 kpUxQyP2/EGXFoBYos3wA9i3tm0v6JOx8AW+HLU557K59dheViOKqiqJAhwEEAEI AAYFAk4qzKEACgkQV1nzUAGqSmQZgQ/9EPERmxoYoNwwDgud0MnJJD2rhflSj1FI DeLk2g3NQN6Lpv0k8+ADRQv44v2UogstU9PT5qWkSPbTcKpQlUF1feoALEMBrScL C48GBIwPoD2T4rsCeXRvB6bPAD7ADr9mqlVzobMv4xWhiLruuHqaWOGWkY5zzWHR MY3pARPYEncPAc5xb4OBxsLCCnuThdtTrLJqA/DXXfpNTtyykAm5kPrldMpA9Ivi NwijlsZe2rafnOv7nWZPDa+Rv3YC1ix15+/1xRUFiEZaA0gI7Mc7uN8HhYTgDagE 0VKC045eoFvZP8TeMV3kzPZXO/6GEAyq6B/as/qJSsJ+laS7LwI4H6Yzf9P+iLpt 4SeITo7/zPFuCsFQnJlK5gbZvsaXyjfGKwc5tY4u0z4ZWD+r5zddjgba0GjcaBgD RdXk05EDOhcUHfTkZOrJkrLiZDzf4L0y/t8HbEP14P/wyabQ6DJOQrhUqxzD4dnX 1MxhwbqMDs0lTo+CTT1UHu+pyFRmJlru64UpX9Y4qBJGXsmjFCwjPxxmrh72jhu1 lCFn9qvGt19JKy2x8jBZ0mgTRn95ONKCPY80IQgsgAZHbnooY1NrkAm6kbNnAmfn /pOAdAMxZpDD8V3CrVZnLFPdUf8Wyi5u+Mj3g2fqO1sp4229zuBKL00mrMncIIU+ ESB/4cFZ42KIRgQQEQgABgUCTirNfAAKCRAo3q5/KZguWp5vAKCoOxcvc8kOa3qk lV1kAM/YJM1R1QCggfQGDVBNF6kmwSZrn0pQexw/G0SJAhsEEAECAAYFAk4tqjgA CgkQxjiXTWR5LWcREg/4m8NKHxXf4/0Tfzhed+lnxl7irA0S/Yo1uVFRu2kTrVTb Z0oqbNXYH3VJ5KPattO8X3FwFhxsnc6Simq0dQjTTZlcv9+CpaR92vQC/5JpCHsl I0QYXZR082yI5477i6GHOae8trt8OUwFWprbzHKw95OBdTLVJhFYDR1h2att5G4Q 0ZJ3Qf7Nzowb/TD1GjZl5mpAzVo5BhjXMFnOFlD3hGd06K/xLdf72B/WUhcmAjuS oAAeCEzPjMstN+pQLe2QiTfhEwQgwIO9BacNl6c1Eezx0jdGc8dAamk0CPm/pWek BGgUvTm4OsPYuMEi3F7B9EK9pay0fmokTC3u2VSJpirlcVZpFaG/fSGkjTxP9ujQ TJz10gxR3EZehkNrSKGC57kvDN7wfQuBmEsue/cn1XLgfFTBxGYHrk2MDfA1Kcgi AcRBvCGHhKdftIRmWQknzh5y2m4KAQhdRPaljGuj26EbKmk/hMEEp9zJ8F6xivkk 8u4KvCiB0sdDNeA6kSTcGoDV+8MhoclQBGjTh08zlzVS6BwCn6Bc7nHIvG2Ana0O dL7smaA5eDg45KCGOnS+uqvhegcQRTtG+5sAB/woHRQpXm7N1rh386R7WRmmdS34 rrR9rHsa6MuvXvHnYdNmEoYNju18xwiiUfWBKxo9gaJS/316m5d4u1kvfEC0PYkC HAQQAQoABgUCTjCkUgAKCRBAv+6GiwVdmgyUD/9necTAKYsr1jDTDq1zzYA06hou EkMXxypEueRPQjY5lBgR8Ou6Kcj8D5Mojvf9SuK/Ie+OySmh1DIoPQROilwn2TQa Ewa+/EWTLHhzhZpSYYzvLV51ku8KKPitNXrJKAILA/4RdjUX7LZBVtPuypQdjhfy eQNS98ssntGztg/cKFbFEyrLiDN2tSRAQ/FLeNKy2umHhLg59d9kSqMp6ShNXguO s6zjzyBroDnoEDuwQI1rpgATzq/Kn0Gw9hnazSeMTEetFnLMmJfYU1zYZxcJOStC RmWcb75vOCmiTDAUUTae8lsDo4Ririh+BGx0mmvHIgTPUjz9oT3nCjGXFPtm71+G Q9tMB4TRmskm9zi2k0csD2i6HiniFPnLQqSDKZHNAqylfJi5+zvdxGgnRmW3BIJo ugvvjjJTJb9LDt6znm1sXB6w9H55bNpeFlG7bGjo4wo4DUf6W9igtvMTlVJ5w2c2 K8TIuhY2ZCbw1jkVwUuMJGLO9Ul9aBfOXaJo3U1D8OmwbXRv5xVq9NzQEogXy0K+ ajJdsZlAOgEKcmCiQ48SI4j8Ek4u0nYxtqL3gzMBuXfaD05jKWzQBW7fkgo6ne6S iGJG/HoQwDw/SIQjfw5IYonodGpwpXC/ihJMasUzbn6L8p+YpmJHCteuGFRJQoqG Vpp03EQo7A3/OCIqkYhGBBARCAAGBQJOLxTRAAoJENXKmwTyxCO8K2AAnRCwA0cm VuEUpOXtSfX6l+M6R/gpAJ9f8Wo2TtxmBf1WlPjS5u3FC0gsXokCHAQQAQgABgUC Ti8VAQAKCRCcMVA8bYZjlmtHD/9gwwbgNuy2fvypFmq3t2O3bLdsEfE2f8cgMnti hI7Rms6L4F40RPOOj+z+ZAaEXbb/pk3dx7kF68CNG3Y+4GgeTR3Ew0eqfZPn2hOd
Bug#622398: New upstream release (1.5.3.4)
Package: password-gorilla Version: 1.4-4.1 Severity: wishlist The packages for the Gorilla password manager are several versions out of date from the current stable release, 1.5.3.4. (It looks like the 1.4 release was July 2006. The Debian package for 1.4 was certainly shipped in Ubuntu's April 2008 release, so it's at least 2 years old.) Could we get an update of this package? I'm happy to make the update if someone else will sponsor the upload, but will wait first to see if Patrick (the original packager) wants to do the update himself. Thanks, Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#610760: Bug #610760 further wide character problems with gcc 4.5 and FORTIFY_SOURCE
Package: bsdmainutils Version: 8.2.1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu natty ubuntu-patch I was working on this bug independently, didn't realize Kees was working on it too. Here's an additional patch, it catches the same problem in usr.bin/calendar/io.c. The problem was introduced by the debian quilt patch debian/patches/calendar_wcs.diff, so this patch fixes that patch, rather than layering another one on top. This patch also fixes related compile warnings caused by incorrect handling of wide characters: -- io.c: In function ‘cal’: io.c:133:6: warning: format ‘%ls’ expects type ‘wchar_t *’, but argument 3 has type ‘char *’ io.c:216:10: warning: passing argument 1 of ‘swprintf’ from incompatible pointer type /usr/include/bits/wchar2.h:286:1: note: expected ‘wchar_t * __restrict__’ but argument is of type ‘wchar_t (*)[31]’ io.c:227:12: warning: passing argument 1 of ‘swprintf’ from incompatible pointer type /usr/include/bits/wchar2.h:286:1: note: expected ‘wchar_t * __restrict__’ but argument is of type ‘wchar_t **’ -- The compile warning on io.c:133 was causing a locale error message in 'calendar' to incorrectly truncate as: calendar: switch to locale `` You can see the related Launchpad bug at https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/697213 Thanks, Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584500: [Pkg-parrot-devel] Bug#584500: parrot: new upstream release
On 6/4/10 11:32 AM, Matt Kraai wrote: Oh. I asked because the latest Rakudo release appears to require the latest Parrot release. Would it be possible to package the latest development release of Parrot in experimental? Parrot 2.5 will be out next Tuesday, is that soon enough? Uploading the monthly releases can be tricky, because it sometimes takes as much as a month to get packages through our sponsors. I'm in the process of applying for Debian Maintainer status, which should make it much easier to keep the monthly releases regularly updated in experimental. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584500: [Pkg-parrot-devel] Bug#584500: parrot: new upstream release
Parrot 2.4 is not a stable release, it's a developer release. We only package the stable releases, which happen on a 3-month cycle (x.0, x.3, x.6, and x.9). On 6/4/10 5:05 AM, Matt Kraai wrote: Source: parrot Severity: wishlist Hi, Parrot 2.4.0 was released on 2010-05-18. Would you please package it? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ___ Pkg-parrot-devel mailing list pkg-parrot-de...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-parrot-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot
Ryan Niebur wrote: ya. preparing an experimental upload would be great. Do you want to wait for the September release or package the SVN version? Let's wait for the releases. Parrot and Rakudo are carefully sync'd at release points, but there's no guarantee of compatibility at random SVN/git revisions. adding experimental to the sources.list and running apt-get install -t experimental rakudo is easier than downloading .debs from alioth, and it means that it's more official (because it's actually in Debian repos). other than that, I don't see the difference. I talked some with Patrick about plans for Rakudo releases. It sounds like it'll be useful to have the 1.6 (maybe 1.8) and 2.3 releases of Parrot in experimental. Rakudo packages could be in experimental around Parrot 1.6, (maybe 1.8,) 2.0 (January), and 2.3 (April), then aim for Rakudo in Debian unstable around Parrot 2.6 (July). Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544399: ITP: rakudo -- implementation of Perl 6 for Parrot
Ryan Niebur wrote: please keep the ITP bug CCed. Apologies, was replying from my phone. On Mon, Aug 31, 2009 at 03:45:07PM -0700, Allison Randal wrote: they're actually in unstable. anyways, I need the unreleased versions of parrot (more recent than 1.5.0 even). I'm using r40789 from SVN locally. Now that I have real internet access again... the automated notice was that 1.4 packages were migrated to testing. So, yes, not relevant to what you're looking for. We only package the stable releases because the intermediate monthly releases are for development testing, not for broader use. I'm willing to package some monthly releases between now and Parrot's next stable release (2.0 in January), just to be absolutely sure that Rakudo packages can enter unstable at the same time as Parrot 2.0. As long as it's understood that the experimental packages don't supersede the 1.4 packages in unstable/testing, and won't ever migrate to unstable or testing. They're just throwaway packages for Rakudo testing. But, it really boils down to a question of whether you have Rakudo users testing Debian experimental. If not, then it makes more sense to put the intermediate packages up on alioth. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531381: [Pkg-parrot-devel] Bug#531381: parrot: FTBFS on GNU/kFreeBSD (hint file needed)
Thanks Petr,
Could you try the attached patch? The 1.4 production release is next
Tuesday, so I could get this into the next version of of Debian packages
if it works for you.
Allison
Index: config/init/hints.pm
===
--- config/init/hints.pm (revision 40086)
+++ config/init/hints.pm (working copy)
@@ -37,6 +37,7 @@
my $hints_used = 0;
my $osname = lc( $conf-data-get_p5('OSNAME') );
+$osname = 'linux' if ($osname eq 'kfreebsd');
my $hints_file = catfile('config', 'init', 'hints', $osname.pm);
if ( -f $hints_file ) {
my $hints_pkg = init::hints:: . $osname;
Bug#531381: [Pkg-parrot-devel] Bug#531381: parrot: FTBFS on GNU/kFreeBSD (hint file needed)
Petr Salinger wrote: Unfortunately, it does not work. This one (also tested) is better: Excellent. Are there remaining build problems after your modified patch, or does that resolve the issue? Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531381: [Pkg-parrot-devel] Bug#531381: parrot: FTBFS on GNU/kFreeBSD (hint file needed)
Petr Salinger wrote: It would help if you could provide more details on the failure to build. The best is if you can provide a full dump of the build process output. https://buildd.debian.org/fetch.cgi?pkg=parrotarch=kfreebsd-amd64ver=1.0.0-1stamp=1243831790file=logas=raw Oh, it builds from source just fine. It's failing on the package install, because the Debian packages expect to find a shared library libparrot.so.1.0.0. But, Parrot built as static because it doesn't have a hints file for that platform to tell it that building a shared parrot library is safe. They (Linux and GNU/kFreeBSD) are not the same, but the current content of hint file could be same. They both use the same gcc, same binutils, same glibc. The only kernel is totally different. May be it would be better to name the hint file glibc.pm and share it between linux, GNU/kFreeBSD and hurd. Okay, for now they'll both use the linux hints file, but if you ever need different configuration parameters than linux, let us know and we can create a separate hints file. Could you send me a copy of the file lib/Parrot/Config/Generated.pm in the parrot build directory? I particularly need to know the values of the archname, osname, and cpuarch configuration variables, as I'll use those to tell parrot use the linux hints file for this architecture. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#531381: parrot: FTBFS on GNU/kFreeBSD (hint file needed)
Thanks for the report Petr. Simply copying the hints file from linux to another name isn't going to help. The configuration hints files provide needed information for Parrot to know how to compile on a particular platform, so either kFreeBSD is exactly the same as linux (and should use the same hints file not a copy of it under a different name), or kFreeBSD has different configuration parameters (in which case, it should have its own hints file, but again, not a copy of the linux one). It's possible that kFreeBSD will be closer to FreeBSD, which already has its own hints file. It would help if you could provide more details on the failure to build. The best is if you can provide a full dump of the build process output. It might make more sense to continue this on parrot-...@lists.parrot.org or in a ticket on https://trac.parrot.org, since it's not really a Debian bug. Thanks, Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#365100: Static building parrot to avoid the NEW queue
Pugs is irrelevant now (mostly dead, and not using Parrot anymore), but the shared library is still necessary for Parrot, especially for the bytecode compiled to executable produced by the pbc_to_exe tool. We will only be packaging the stable releases of Parrot (which happen every six months), so you don't have to be concerned about hitting the NEW queue with every monthly developer release. Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444708: Status of the ITA
Hi Michael, Yes, we've been generating regular packages. The 1.0 release of Parrot is coming up in March, and it would be nice to get that one in. I'll check in with our debian sponsors. Thanks, Allison -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#444708: ITA: parrot -- virtual machine for dynamic languages
John Lightsey wrote: Hi there, Do you still intend to adopt the Debian Parrot packages? From what I can see, there was some talk in December about setting up group maintenance of Parrot, but it doesn't look like that ever took off. The group is in place, and we have 3 Debian Developers as sponsors. We've also updated the packages, and have them ready to upload. What we're waiting for now is confirmation that one final Debian bug report has been resolved (#382147). For that we need a working ia64 box. All other reported bugs have been resolved and are noted as such in the updated changelog file. Once we have this final bug confirmed, we'll start submitting monthly Debian packages along with our monthly releases. Allison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458385: New version of Artistic License
Hmmm... Russ and Gunnar seem to have traded positions. Whatever the policy group decides is, of course, fine. Just let us know. I'll check back in a few months if I don't hear anything more. Gunnar Wolf wrote: I'm more worried about the tons of changes this will inflict on the pkg-perl group ;-) But well, that's just me. Agreed. That's one reason we plan to maintain our own packages, at least for the core. Allison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458385: New version of Artistic License
Russ Allbery wrote: That's additional information that I didn't have. Are all hundred of those modules covered under the Artistic 2.0 license? Yes, with the exception of 3 explicitly mentioned in the README. I was under the impression that the Perl 6 modules in the archive were being packaged independently like the Perl 5 modules, since I think I've seen several of them already. I didn't realize that you had a monolithic package that you were going to break up. What you've likely seen is the Perl 5 modules that emulate parts of Perl 6 syntax. Those are all named Perl6::something. Hm. I think you're going out on a considerable legal limb here, but presumably you've talked to a lawyer and have gotten a firm legal opinion before taking this step. I'm not a lawyer, so I won't question legal judgement, and the wording of the Artistic License is odd enough that this may be possible. However, in general, relicensing requires assignment or consent, so if you *haven't* gotten a specific legal opinion on exactly this question, I strongly recommend doing so before relicensing just to avoid unfortunate problems. Indeed, we got legal counsel on the question before we even started to revise the license. The legal steps are squared away. There is still a community process for the update, because that's the way Perl development works. Allison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458385: New version of Artistic License
Russ Allbery wrote: Licenses are included in common-licenses primarily on the basis of how commonly they're used in the archive. Currently, there are only about five packages in the archive covered by this license, so I don't believe this is warranted at this time. Basically, the license isn't common. GPL-3 isn't common either, yet. But it is included, because it's the latest version of a license that is quite common, and it's expected that many packages will update their license. The Debian Policy Manual states that packages released under the Artistic License should refer to the files in /usr/share/common-licenses. I intended to comply with that policy for the updated Parrot packages, but found I couldn't since the directory only contained an old version of the license. Allison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458385: New version of Artistic License
Russ Allbery wrote: Gunnar Wolf [EMAIL PROTECTED] writes: Many Perl modules are just licensed under the same terms as Perl itself, so as soon as Perl is released under this license, we will have several hundreds of packages automagically under it. Of course, this will require updating/changing many of them (as Perl6 is not backwards-compatible)... But I do see a case for including this license in common-licenses. Right, this is really a question of Perl 6. Perl 6 is already distributed under version 2.0, currently included in the Parrot package. As are over a hundred Perl 6 modules, currently included in the Pugs package. We haven't split them out into separate Debian packages yet, but will in the next 6 months or so. If you want me to wait 6 months and ask again, I can. It just made more sense to me to ask before we create a hundred or so 'copyright' files for a hundred or so packages. Perl 5 can never legally be released under this license so far as I can see. The Perl maintainers didn't do copyright assignment, so relicensing the existing Perl code base would require contacting every contributor and obtaining their permission to relicense their code. This isn't really feasible. Version 2.0 of the license was intentionally drafted so it's entirely compatible with version 1.0 of the license. It has the same terms, only cleaner and more legally precise. It's a drop-in replacement, and copyright assignments aren't necessary. Allison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#458385: New version of Artistic License
Package: base-files Version: 4.0.1 Severity: wishlist I'd like to request the addition of the file: http://www.perlfoundation.org/attachment/legal/artistic-2_0.txt as Artistic-2 in /usr/share/common-licenses/. Thanks, Allison -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
