Bug#738833: release.debian.org: transition tracker for python3.4 as supported
Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: transition Dear Release team, python3.4 is added as a supported version, please setup a tracker to transition / rebuild packages to pick up 3.4 as supported. I think something like that should do: Affected: .build-depends ~ /python3(all)?-dev|python3.3|python3/ Good: .depends ~ /python3 \( 3\.5\)/ | (!.depends ~ /python3 \( 3\.5\)/ .depends ~ /libpython3\.3/ .depends ~ /libpython3\.4/) | .depends ~ /python3.4/ Bad: .depends ~ /python3 \( 3\.4\)/ | .breaks ~ /python \(= 3\.4\)/ | (.depends ~ /libpython3\.3/ !.depends ~ /libpython3\.4/) Or use same stanzas as were used for 3.2(default) + 3.3(supported) transition. Regards, Dimitri. -- System Information: Debian Release: jessie/sid APT prefers trusty APT policy: (500, 'trusty') Architecture: amd64 (x86_64) Foreign Architectures: i386 armhf Kernel: Linux 3.13.0-8-generic (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 -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ob2b9u2s@debian.org
Re: A new metric for source package importance in ports
On 28 November 2013 00:04, Steven Chamberlain ste...@pyro.eu.org wrote: Hi josch! On 27/11/13 17:58, Johannes Schauer wrote: http://mister-muffin.de/p/Gid8.txt One can see that now the amount of source packages which is needed to build the rest of the archive is only 383. So, there are 383 packages that share the same, maximum value (in this case 11657) in the second column? Does anybody see enough value in these numbers for source package importance in the light of bootstrapping Debian (either for a new port or for rebuilding the archive from scratch)? I find the list of 383 packages interesting, at least. I think this closure is what I had in mind[0] for regular testing of ports' toolchains and reproducibility of builds. Because each Debian port depends in some indirect way on the authenticity of these packages. And likewise any toolchain bugs are most critical here. I just didn't think there would be so many packages. Does the list vary by architecture? I see many odd things in here such as 'systemd' and 'redhat-cluster' which would be unavailable if trying to bootstrap a non-Linux port, for example. I also find it interesting to see openjdk-7 listed but not gcj; or even gcc-4.8. Was this computed for jessie or sid? I guess implicit relationships are not considered: build-essential build-dependencies, and essential dependencies. I would expect for packages in those to sets have the highest rank, since, hypothetically, all packages in debian build-depend depend on those. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANBHLUiifmR+_keS3eSQa_b3_CfZ_56o9vBRR8p2SeY=hy9...@mail.gmail.com
Bug#706798: transition: Libav 9
On 09/11/2013 06:02 PM, Moritz Mühlenhoff wrote: On Fri, Sep 06, 2013 at 05:06:03PM +0200, Moritz Mühlenhoff wrote: Hi, two more testing removals related to the libav9 transition: - libavg 1.7.1-3 fails to build for unrelated boost reasons. Popcon is virtually non-existant. Well the patch for boost problem is uploaded into debian (built in a jessie chroot / against older libav that is). Such that to prevent erroneous FTBFS attribution to earlier boost failure in the build process. This was available since August 27th in Ubuntu, but not uploaded into debian as I couldn't build the package in sid as it FTBFS against libav 9. Unfortunately I'm not familiar with libav API changes to port libavg, I'll poke upstream about it, but at the moment I'm tagging libavg FTBFS against libav 9 bug with help. Is there a libav 9 porting guide available somewhere? Or can someone help out with a patch to fix libav 9 FTBFS? Also, why did libavg was removed from testing? Was it actually blocking any removals from the archive and/or transitions? As far as I can see all libraries that libavg binaries are linked against are still present in sid. This haste removal seems inconsistent to me w.r.t. how other transitions library removals are handled by the release team. ps. Popcon is virtually non-existant because virtually libavg has only been recently reintroduced in debian after having been away for a long time. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhluhj_cv+fgjyqx5s7osxql2m41d8-qgkgzckxygzian...@mail.gmail.com
Re: Call for Jessie Release Goals
On 18 September 2013 03:42, Mathieu Malaterre ma...@debian.org wrote: On Wed, Sep 11, 2013 at 9:17 PM, Jonathan Wiltshire j...@debian.org wrote: Release goals are areas of functionality which developers would like to see as an aim for the next release. They will not hold up the release, but allow the bugs opened for that goal to be of severity 'important'. I am not sure if this qualify as Release goals. So I'd like to ask first what people think of using C++11 in the next release. I know of a couple of C++ libraries which could be compiled with the new gcc compilation option. And I have at least one application (no shared lib) which requires C++11 to compile properly. Since C++11 introduce an ABI incompatibility [*], this may not be a Release Goal but simply a tech-ctte decision. Comments ? I think I have replied about similar requests before (not sure if it was on these mailing lists). In essence, at the moment we do not have any compiler stdlib with complete and stable ABI for C++11. It is expected that gcc4.8 will break C++11 ABI to further implement the standard. Other non-default compilers also are fully featured at the moment (w.r.t. C++11 compiler features). Thus at the moment we cannot consider switching. One can compile with C++11 enable where one must, but also one then gets to keep the ABI incompatibilities down the road (boost / template libraries especially). While one would want to start using C++11, it's not default at the moment and not feasible to make the default standard level C++11. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANBHLUgYHMH6OymwjNc-b2O_ryuv6i_wKqDd=cnvmgzdb07...@mail.gmail.com
Bug#704032: transition: boost-defaults
Looking at boost1.53 transition in ubuntu[1] at the moment. It's probably as best as I can prepare the transition. There are still a few FTBFS in ubuntu but the numbers of those are quite low. Looking at the blocking bugs in Debian, most of them are easy quick uploads once the transtition starts. I would request to ignore ogre it's reverse dependencies at the moment. To support, boost1.53 ogre needs a soname bump to a version 1.8.1 or higher. And the maintainer expressed to transition straight to ogre 1.9 when that becomes available.[2] There are a couple blocking issues - e.g. in boost itself recent possible breakage in gcc-4.8. But apart from those, I'd like to request start of the transition soonish. (pending any other overlapping transitions and such like). [1] http://people.canonical.com/~ubuntu-archive/transitions/boost1.53.html [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704044#85 Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhluizjbzaazcfzutsxtpdndgb9qeqm5ygzprat8t-qfk...@mail.gmail.com
Bug#704032: transition: boost-defaults
On 9 May 2013 08:40, Matthias Klose d...@debian.org wrote: Am 09.05.2013 05:39, schrieb Steve M. Robbins: On May 8, 2013 12:05:39 PM Julien Cristau wrote: On Tue, Mar 26, 2013 at 23:08:15 -0500, Steve M. Robbins wrote: I would like to change Debian's default boost version from 1.49 to 1.53 or later -- likely to the most current Boost at the time the transition is scheduled. This change does not directly impact any binary packages. However, it will affect the buildability of source packages. Do we know how many (and which) packages would start FTBFS if the change was done now? Dmitrijs: did you do a full rebuild of the archive using Boost 1.53? If so, can you post your results here? I did a full rebuild before starting, but those results are not as relevant any more due to the sheer amount of issues fixed. The best buildability estimate at the moment is: http://people.canonical.com/~ubuntu-archive/transitions/boost1.53.html Which is still transition in progress. Please note a few issues that are still open in debian, have been uploaded into ubuntu: * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704044 ( ogre transition, closed in error, now reopened ) * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704045 ( qt4 moc fix ) * http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701288 ( example of underlinking) I have yet to see a gcc4.8 specific FTBFS that has not been filed in debian BTS or otherwise known (for example as the case is with aptitude boost-thread dependency on boost-system and dropping of -mt compat symlinks are the biggest problems so far. My current plan to is to continue process with the transition, now that I am back file bugs with patches. All bugs so far are marked as blocking this transition. IMHO it's easier to schedule binNMUs rather than uploading patches to transition things. And I will do a new proper rebuild soonish. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhlugxaivadzb7j34v5vsb_ydsvv1_9bqpc1xvlyqc_zx...@mail.gmail.com
Re: e2fsprogs_1.42.5-1.1_amd64.changes ACCEPTED into unstable
On 22 March 2013 22:17, Nicolas Boulenguez nico...@debian.org wrote: On Wed, Mar 20, 2013 at 09:50:07PM -0400, Theodore Ts'o wrote: e2fsprogs (1.42.5-1.1) unstable; urgency=low * Non-maintainer upload. This shouldn't have been uploaded to unstable without first getting permission from the Debian Release team (and preferably me --- it would have been nice if you had asked me before uploading the NMU) Sorry to be fussy, but I only suggested the patch via the BTS. Dmitrijs, please put your own name into debian/changelog next time you sign an NMU. Ok, I can see how it can be confusing. who-uploads does show that it was my gpg signature on the upload. It's just this way I sponsor any other uploads were the code/changes I am not the author of. How should I credit the author? Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhlugcnwwisnkqh4rhnh5_gzaxxe5uhxpw0biy7c-xbpz...@mail.gmail.com
Re: e2fsprogs_1.42.5-1.1_amd64.changes ACCEPTED into unstable
On 22 March 2013 23:26, Theodore Ts'o ty...@mit.edu wrote: On Thu, Mar 21, 2013 at 02:09:44AM +, Dmitrijs Ledkovs wrote: I was about to file unblock request and ping the installer team coordinators. Sorry, if this is the wrong way around with respect to an upload to unstable. Well, normally, I'd ask the Release team first whether they would be willing to unblock, this late in the release cycle. Nonetheless, the bug was still marked as RC. Why didn't you comment on the bug report or downgrade it for almost one month now since nmu.diff was posted? I did ask if the Release team would be interested in an upload (although of a much larger change, admittedly), and they said no. Also, usually I saw such requests with a diff attached to a bug report opened against release.debian.org, not by piling it in the unrelated bug-report against a package. Personally, I view a bug which can destroy a user's file system as being more serious that failing to delete a symlink from a pre-lenny install, but I suppose I should have downgraded the bug report, or explicitly asked if they would be willing to take a smaller change (that would still involve re-rolling the installer image at this late state of the game.) I'm not sure if the installer team would want to reroll the images or not, since there is no code changes to the udebs. But the fix will benefit to be present in the CD's pool to anyone who upgrades from CDs without internet access. In any case, the earlier e-mail about your upload has already been sent to the Debian Release team, so at this point, I'd suggest waiting for their response. Right now I feel bad, and not quite sure why. It's just two symlinks that got overlooked due to a dpkg quirk/feature. Yet it took about a month to be commented or uploaded, and once it did get uploaded we have spend all of this time emailing each other. If it gets unblocked and d-i team respins to pick up some other fixes, maybe they will consider to pick this one up as well. If not, so be it, people will pick it up jessie. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhlugnuh-v_2yrpxasd59_vaupqe9mb7dk3tbbfqh8bgx...@mail.gmail.com
Bug#703788: unblock: scratch/1.4.0.6~dfsg1-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package scratch
Closes: #703141
unblock scratch/1.4.0.6~dfsg1-4
Regards,
Dmitrijs.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJRTfELAAoJEIh7YGGLPBauwkwP/0RzNNKDmcDgT+FQENJk03Z9
0V6D6yLWXNSRCdtTPFgv3YTTQ7CUAsV5R++4HEFPNaXem8mS9lgR/7pMEHWVYjpo
Urg3s+4Fmjqfwk05e+Q0hmxDMlscUH6xaG5kyIAC1XEuEDa8BnrAThas+oUI08XW
IlHZMqHIA/BeAFPChWMjBWw8skTiO4ze0wDE7UXE61qfuPXiSQMYdGwL46nPMnzn
E/qUWjZRn1kpY8CrcUcFSW/M7EW0DIjlrKkZqIpgpokM5yEucQ7bTzyNhiD+2hHM
Rmg+veK4YPVYFSBFhQWDeQTvpDLaCuUhK6/zIhd8Ojjp+roj5QEZiWa4kE7lFBVx
1dC7pOwZpbeOsH5UvfFL4zN6FpLSGNeyGu8zyoyCEKoGhVLBNXPjhRStr5LKx1JL
AEYGQMIAkkh+ZqtpgVeM4ANdbjVmJLc8NYegM0VFFrnfpaHVG/p6gHrIHvwHEeL7
UFkl5JdvWqXk6WWgOlTYQw6iaVmL2r+piqxFURbe69QfCXugSIxpi2jRU3bfhocT
XpjAFOLTTdGedKaAt/cwDRnlxFP6QqfTKQhc+8exNct7vG19UHHc3bOTdg2TdM2V
ldMVwRMlRae3+24cHIhU2LAu2YO92GnVIYcSsYMf/Xbt7SEby3g4OqIO6bXEuCmN
5b3gJgC6XgUuoPpZck9j
=zDw8
-END PGP SIGNATURE-
diff -Nru scratch-1.4.0.6~dfsg1/debian/application-registry/scratch.applications scratch-1.4.0.6~dfsg1/debian/application-registry/scratch.applications
--- scratch-1.4.0.6~dfsg1/debian/application-registry/scratch.applications 1970-01-01 01:00:00.0 +0100
+++ scratch-1.4.0.6~dfsg1/debian/application-registry/scratch.applications 2013-03-21 09:19:28.0 +
@@ -0,0 +1,7 @@
+scratch
+ command=scratch
+ name=Scratch Application
+ can_open_multiple_files=false
+ expects_uris=false
+ requires_terminal=false
+ mime_types=application/x-scratch-project
diff -Nru scratch-1.4.0.6~dfsg1/debian/bin/scratch scratch-1.4.0.6~dfsg1/debian/bin/scratch
--- scratch-1.4.0.6~dfsg1/debian/bin/scratch 2012-07-04 23:00:04.0 +0100
+++ scratch-1.4.0.6~dfsg1/debian/bin/scratch 2013-03-15 01:17:34.0 +
@@ -7,7 +7,7 @@
VM_VERSION=`find /usr/lib/squeak/ -name squeakvm -type f|cut -f5 -d/`
SQ_DIR=/usr/lib/squeak/$VM_VERSION
VM=$SQ_DIR/squeakvm
-VMOPTIONS=-encoding UTF-8 -vm-display-x11 -xshm -plugins /usr/lib/scratch/plugins/:$SQ_DIR/
+VMOPTIONS=-encoding UTF-8 -vm-display-x11 -plugins /usr/lib/scratch/plugins/:$SQ_DIR/
IMAGE=/usr/share/scratch/Scratch.image
IMOPTIONS=
DOCUMENT=
@@ -25,7 +25,7 @@
usage()
{
-echo Usage: scratch [--param value] [-vmopt value] [arg value]
+echo Usage: scratch [--help] [--param value] [-vmopt value] [arg value]
echowhere --param is --vm, --image, or --document;
echo-vmopt is an option passed to the Squeak VM;
echoand args are passed to the Squeak image.
@@ -33,6 +33,10 @@
if [ $# -eq 1 ] ; then
case $1 in
+ --help)
+ usage
+ exit
+ ;;
/*) DOCUMENT=$1
;;
*) DOCUMENT=$PWD/$1
@@ -94,12 +98,9 @@
# make Compose input methods work
[ -z $LC_ALL ] export LC_ALL=$LANG
-# if pulseaudio is running, fall back to OSS
+# if pulseaudio is running, use it.
if pulseaudio --check 2/dev/null ; then
-VMOPTIONS=$VMOPTIONS -vm-sound-oss
-if padsp true 2/dev/null ; then
-WRAPPER=padsp
-fi
+VMOPTIONS=$VMOPTIONS -vm-sound-pulse
fi
# VM, Image, and Document are non-optional
diff -Nru scratch-1.4.0.6~dfsg1/debian/changelog scratch-1.4.0.6~dfsg1/debian/changelog
--- scratch-1.4.0.6~dfsg1/debian/changelog 2012-07-13 09:18:57.0 +0100
+++ scratch-1.4.0.6~dfsg1/debian/changelog 2013-03-21 19:00:58.0 +
@@ -1,3 +1,24 @@
+scratch (1.4.0.6~dfsg1-4) unstable; urgency=low
+
+ * Removed dependency from hicolor-icon-theme. Closes: #703141
+ * Added proper support for MIME
+ * Removed obsolete postinst/postrm scripts
+
+ -- Miriam Ruiz mir...@debian.org Thu, 21 Mar 2013 09:10:03 +0100
+
+scratch (1.4.0.6~dfsg1-3) unstable; urgency=low
+
+ [ Miriam Ruiz ]
+ * Added support for help in starting script. Thanks to Alec Clews.
+ * Changed my email to mir...@debian.org
+
+ [ Amos Blanton ]
+ * Prefer pulse plugin if pulse is present, because pulse ALSA emulation
+fails when user records sounds.
+ * Remove -xshm switch to squeakvm to prevent Ubuntu Bug 1025013.
+
+ -- Miriam Ruiz mir...@debian.org Fri, 15 Mar 2013 02:20:01 +0100
+
scratch (1.4.0.6~dfsg1-2) unstable; urgency=low
* Added SVN links to debian/control
diff -Nru scratch-1.4.0.6~dfsg1/debian/control scratch-1.4.0.6~dfsg1/debian/control
--- scratch-1.4.0.6~dfsg1/debian/control 2012-07-13 09:17:10.0 +0100
+++ scratch-1.4.0.6~dfsg1/debian/control 2013-03-21 08:16:05.0 +
@@ -1,7 +1,7 @@
Source: scratch
Section: education
Priority: optional
-Maintainer: Miriam Ruiz little_m...@yahoo.es
+Maintainer: Miriam Ruiz mir...@debian.org
Standards-Version: 3.9.3
Build-Depends: debhelper (= 7)
Homepage: http://scratch.mit.edu
@@ -13,7 +13,7 @@
Depends: squeak-vm, squeak-plugins-scratch, libgtk2.0-bin, shared-mime-info,
${misc:Depends}
Suggests: pulseaudio (= 1.0.9)
-Description: easy to use programming
Bug#703573: unblock: roundcube/0.7.2-7
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package roundcube
Closes: #680917, #656886, #688634, #699604.
The #688634 is the most important to close here.
unblock roundcube/0.7.2-7
- -- System Information:
Debian Release: wheezy/sid
APT prefers raring-updates
APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500,
'raring'), (100, 'raring-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8.0-13-generic (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJRSk7lAAoJEIh7YGGLPBauMFwP/AvwrVRXkhuiMTX9g2TVsooo
ZMWjI+mipShUzpoFndukegwojCa4tFktQ9/NI/gZJZEN5TEmya8uUrzs9IiUrtrh
jFhgPBZYcudtHzcbVGE6q7DnYG/+iHPbvretOZ+V6s/lLXLMYFtPHN1a/mj1p177
iaNtLCgPFugYdXiLwzcvpptJv2O+4lF20ADE+ElVmn9bpmC3JXDuUF+Lrkfvc1Cs
bZhinbbUW9Y9bJkeKzB+2OWGCFEmIj7Sb3lFKczdlouQfCzh0ZOuCyXSsPee9K/s
vGjKQ+ILnu44CX10GNg7Goe7TW+UyxgSEkogCcsRpzTInIpza9OCjOgQjgxYBpfw
VEdEQRn5qSNCDfeC5IrTtlW7n8kOHHvyf+a5W/Ygl5p0g49rIEFnWzBwXy8anksL
Jr0VxnD0nMIqELIZRIIIhivBRSwAcgJi2dvwcBnmqVrgEewoUZBpe4nNWSsCxecL
PH4w3OzpKeT0N550PHm4OeZQoEtURiTpHSlmxqYmFpWjSd/1Fg8VMBx0A37ldQid
DHYf7VqUWBlIZHAeUQrIo0nUXmFb9YBS8IrrhORpFLde6JMIdz5exvNkypm4tY07
RHCJ1OtWabRW5LiquGu0EiGKQW8c1a/Sn31VZ7NsQsL6dp1OMQE0//9fGSQ0WBQR
HOJJcqsSnHT1xebD+2qn
=EZXZ
-END PGP SIGNATURE-
diff -Nru roundcube-0.7.2/debian/changelog roundcube-0.7.2/debian/changelog
--- roundcube-0.7.2/debian/changelog 2012-09-29 10:39:58.0 +0100
+++ roundcube-0.7.2/debian/changelog 2013-03-16 16:26:29.0 +
@@ -1,3 +1,20 @@
+roundcube (0.7.2-7) unstable; urgency=low
+
+ * Fix dependencies to postgresql and postgresql-client. Closes: #699604.
+ * Drop roundcube-sqlite transition package since we don't provide an
+automatic upgrade path. The user will have to remove the package by
+herself. Move the related NEWS entry from roundcube-sqlite to
+roundcube-core and explain how to continue upgrade. Closes: #688634.
+
+ -- Vincent Bernat ber...@debian.org Sat, 16 Mar 2013 17:26:20 +0100
+
+roundcube (0.7.2-6) unstable; urgency=low
+
+ * Fix the symlink mess in postinst when upgrading from 0.5 to a more
+recent version. Closes: #680917, #656886.
+
+ -- Vincent Bernat ber...@debian.org Sat, 10 Nov 2012 13:51:17 +0100
+
roundcube (0.7.2-5) unstable; urgency=low
* Fix problem with some uuencoded attachments. Patch from Michał
diff -Nru roundcube-0.7.2/debian/control roundcube-0.7.2/debian/control
--- roundcube-0.7.2/debian/control 2012-09-29 10:39:58.0 +0100
+++ roundcube-0.7.2/debian/control 2013-03-16 16:26:29.0 +
@@ -46,13 +46,6 @@
.
This package will install a full roundcube application.
-Package: roundcube-sqlite
-Architecture: all
-Depends: roundcube-mysql | roundcube-pgsql, ${misc:Depends}
-Section: oldlibs
-Description: transitional dummy package
- This package is a dummy transitional package. It can be safely removed.
-
Package: roundcube-mysql
Architecture: all
Depends: php-mdb2-driver-mysql (= 1.5.0b2), mysql-client | virtual-mysql-client, ${misc:Depends}
@@ -64,8 +57,8 @@
Package: roundcube-pgsql
Architecture: all
-Depends: php-mdb2-driver-pgsql (= 1.5.0b2), postgresql-client-8.1 | postgresql-client, ${misc:Depends}
-Suggests: postgresql-server
+Depends: php-mdb2-driver-pgsql (= 1.5.0b2), postgresql-client-9.1 | postgresql-client, ${misc:Depends}
+Suggests: postgresql
Description: metapackage providing PostgreSQL dependencies for RoundCube
This package provides PostgreSQL dependencies for RoundCube Webmail,
a skinnable AJAX based webmail solution for IMAP servers. Install
diff -Nru roundcube-0.7.2/debian/roundcube-core.NEWS roundcube-0.7.2/debian/roundcube-core.NEWS
--- roundcube-0.7.2/debian/roundcube-core.NEWS 2012-09-29 10:39:58.0 +0100
+++ roundcube-0.7.2/debian/roundcube-core.NEWS 2013-03-16 16:26:29.0 +
@@ -1,3 +1,22 @@
+roundcube (0.7.2-7) unstable; urgency=low
+
+Roundcube SQLite support is limited to SQLite 2.x. No support for
+SQLite 3.x currently exists. Unfortunately, SQLite 2.x is unmaintained
+for several years and therefore has been dropped from php5
+package.
+
+You need to select another database to continue to use
+Roundcube. Unfortunately, there is currently no migration script
+available. You have to start from an empty database and migrate
+data yourself if you want to keep your settings. You can find some
+directions here:
+ http://wiki.debian.org/Roundcube/DeprecationOfSQLitev2
+
+Once the migration is done, you can remove roundcube-sqlite
+package.
+
+ -- Vincent Bernat ber...@debian.org Sat, 02 Mar 2013 22:20:17 +0100
+
roundcube (0.3.1-2) unstable; urgency=low
Starting from Roundcube 0.3, an incompatibility
Bug#703581: unblock: e2fsprogs/1.42.5-1.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package e2fsprogs Closes #698879 This is also a request for udeb-unblock from the installer team. unblock e2fsprogs/1.42.5-1.1 - -- System Information: Debian Release: wheezy/sid APT prefers raring-updates APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring'), (100, 'raring-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8.0-13-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJRSm0SAAoJEIh7YGGLPBauB6MP/iTl4ulKrqAnn9Xr2TPtudd/ Rt12pCLUcJ3KReyE/DHjIKAeiq41IYcr2nZ7087eRuT+EFZGtTWYxHv4U3CX89bT zNWdX2UqUMKQR6xwc/3+BXKbTJOswcjQxnF0qb/8TJbQkhREub5ts7G2dx2SDqWZ x2ke/DOO6lbslO6G/N1+RUYY7fHgpwpQCm0RZF8t17b1xTVVUhhs/awwt1wzoaKi oDAdtU4TidO3FdlYQxBAqAqqT+Jcoj2jzxTmEV4tDeRptowd42PIKmKAyXk3ippA 2o3FgVQNVZ81sMQEN1MDpxhi302YSfyym0x8rS/DTqayIuT1PoQfJ5MzvVI0nukJ x3UGbJhIQokJVMoeFH7sEzftqTJIrAPlVNv7t9OGycYYNlCp1Gn6FO7tmYknWDye 1z91djudgLYcnUHpSU9hh1T8zBTQgavq9E4/oPs4LQlTr64+wamgQLpCVd27LSm3 B4KqylEEHzKB+3KuPcbz9SxfCAGyKnHN0KQKN+R9AgMThdDrv6E7drz8Yy0qMwdB JBpHhXhzAXYwr05LZs6mgmmwjSysIJyFhG2MMs3mCqEo8zsCbwp50uviAKnx4e8F +MOPOZi4AwMN0VGTcYZ4X6svuZt60ugcxozDY7gJ1zOGdpxd3mq5OtVpx6MLE/xy IDNQ6WycVIMro+mgBMTe =DClc -END PGP SIGNATURE- diff -Nru e2fsprogs-1.42.5/debian/changelog e2fsprogs-1.42.5/debian/changelog --- e2fsprogs-1.42.5/debian/changelog 2012-07-30 01:01:45.0 +0100 +++ e2fsprogs-1.42.5/debian/changelog 2013-03-21 00:07:18.0 + @@ -1,3 +1,12 @@ +e2fsprogs (1.42.5-1.1) unstable; urgency=low + + * Non-maintainer upload. + * e2fsck-static, e2fsprogs: let preinst remove a symbolic link in +/usr/share/doc, that should have been replaced with a directory since +1.39+1.40-WIP-2006.10.02+dfsg-1. (Closes: #698879). + + -- Nicolas Boulenguez nico...@debian.org Fri, 22 Feb 2013 23:14:59 +0100 + e2fsprogs (1.42.5-1) unstable; urgency=low * New upstream version diff -Nru e2fsprogs-1.42.5/debian/e2fsck-static.preinst e2fsprogs-1.42.5/debian/e2fsck-static.preinst --- e2fsprogs-1.42.5/debian/e2fsck-static.preinst 1970-01-01 01:00:00.0 +0100 +++ e2fsprogs-1.42.5/debian/e2fsck-static.preinst 2013-03-21 00:07:18.0 + @@ -0,0 +1,19 @@ +#!/bin/sh + +# Abort on error. +set -e + +PKG=e2fsck-static +DOCLNK=/usr/share/doc/$PKG +if test $1 = upgrade \ +-a -L $DOCLNK +then +rm $DOCLNK +fi + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 diff -Nru e2fsprogs-1.42.5/debian/e2fsprogs.preinst e2fsprogs-1.42.5/debian/e2fsprogs.preinst --- e2fsprogs-1.42.5/debian/e2fsprogs.preinst 1970-01-01 01:00:00.0 +0100 +++ e2fsprogs-1.42.5/debian/e2fsprogs.preinst 2013-03-21 00:07:18.0 + @@ -0,0 +1,19 @@ +#!/bin/sh + +# Abort on error. +set -e + +PKG=e2fsprogs +DOCLNK=/usr/share/doc/$PKG +if test $1 = upgrade \ +-a -L $DOCLNK +then +rm $DOCLNK +fi + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0
Bug#699035: unblock: unattended-upgrades/0.79.4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock unattended-upgrades to fix
bug #698552: unattended-upgrades - Fails with xz compress debs
The fix is to add missing dependency on xz-utils.
Also a unit tests is added explicitly testing xz compressed deb.
Attaching debdiff.
Regards,
Dmitrijs.
diff -Nru unattended-upgrades-0.79.3/debian/changelog unattended-upgrades-0.79.4/debian/changelog
--- unattended-upgrades-0.79.3/debian/changelog 2012-08-07 11:20:06.0 +0100
+++ unattended-upgrades-0.79.4/debian/changelog 2013-01-21 16:29:27.0 +
@@ -1,3 +1,11 @@
+unattended-upgrades (0.79.4) unstable; urgency=low
+
+ * lp:~mvo/unattended-upgrades/xz-support:
+ - add missing xz-utils dependency, thanks to Bastian Blank
+ (closes: #698552)
+
+ -- Michael Vogt m...@debian.org Mon, 21 Jan 2013 17:27:31 +0100
+
unattended-upgrades (0.79.3) unstable; urgency=low
* unattended-upgrade:
diff -Nru unattended-upgrades-0.79.3/debian/control unattended-upgrades-0.79.4/debian/control
--- unattended-upgrades-0.79.3/debian/control 2012-07-13 19:52:54.0 +0100
+++ unattended-upgrades-0.79.4/debian/control 2013-01-21 16:29:27.0 +
@@ -11,7 +11,7 @@
Architecture: all
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, python,
python-apt (= 0.7.90), apt-utils, apt, ucf, lsb-release,
- lsb-base (= 3.2-14)
+ lsb-base (= 3.2-14), xz-utils
Suggests: bsd-mailx, mail-transport-agent
Description: automatic installation of security upgrades
This package can download and install security upgrades automatically
diff -Nru unattended-upgrades-0.79.3/test/aptroot/var/log/apt/history.log unattended-upgrades-0.79.4/test/aptroot/var/log/apt/history.log
--- unattended-upgrades-0.79.3/test/aptroot/var/log/apt/history.log 2012-08-07 11:20:17.0 +0100
+++ unattended-upgrades-0.79.4/test/aptroot/var/log/apt/history.log 2013-01-21 16:29:47.0 +
@@ -1,4 +1,4 @@
-Start-Date: 2012-08-07 12:20:17
+Start-Date: 2013-01-21 17:29:47
Upgrade: awstats:amd64 (6.9~dfsg-1ubuntu3, 6.9~dfsg-1ubuntu3.10.04.1), apt-doc:amd64 (0.7.25.3ubuntu9, 0.7.25.3ubuntu9.13)
-End-Date: 2012-08-07 12:20:17
+End-Date: 2013-01-21 17:29:47
diff -Nru unattended-upgrades-0.79.3/test/aptroot/var/log/apt/term.log unattended-upgrades-0.79.4/test/aptroot/var/log/apt/term.log
--- unattended-upgrades-0.79.3/test/aptroot/var/log/apt/term.log 2012-08-07 11:20:17.0 +0100
+++ unattended-upgrades-0.79.4/test/aptroot/var/log/apt/term.log 2013-01-21 16:29:47.0 +
@@ -1,3 +1,3 @@
-Log started: 2012-08-07 12:20:17
-Log ended: 2012-08-07 12:20:17
+Log started: 2013-01-21 17:29:47
+Log ended: 2013-01-21 17:29:47
diff -Nru unattended-upgrades-0.79.3/test/aptroot/var/log/unattended-upgrades.log unattended-upgrades-0.79.4/test/aptroot/var/log/unattended-upgrades.log
--- unattended-upgrades-0.79.3/test/aptroot/var/log/unattended-upgrades.log 2012-08-07 11:20:17.0 +0100
+++ unattended-upgrades-0.79.4/test/aptroot/var/log/unattended-upgrades.log 2013-01-21 16:29:47.0 +
@@ -1,25 +1,27 @@
-2012-08-07 12:20:12,876 INFO Initial blacklisted packages: ant-doc
-2012-08-07 12:20:12,877 INFO Starting unattended upgrades script
-2012-08-07 12:20:12,877 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
-2012-08-07 12:20:13,973 DEBUG Checking: ant-doc ([Origin component:'main' archive:'lucid-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True, Origin component:'main' archive:'lucid-security' origin:'Ubuntu' label:'Ubuntu' site:'security.ubuntu.com' isTrusted:True])
-2012-08-07 12:20:13,975 DEBUG skipping blacklisted package 'ant-doc'
-2012-08-07 12:20:13,976 DEBUG Checking: apt-doc ([Origin component:'main' archive:'lucid-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True, Origin component:'main' archive:'lucid-security' origin:'Ubuntu' label:'Ubuntu' site:'security.ubuntu.com' isTrusted:True])
-2012-08-07 12:20:14,020 DEBUG Checking: awstats ([Origin component:'main' archive:'lucid-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True, Origin component:'main' archive:'lucid-security' origin:'Ubuntu' label:'Ubuntu' site:'security.ubuntu.com' isTrusted:True])
-2012-08-07 12:20:14,105 DEBUG pkgs that look like they should be upgraded: apt-doc
+2013-01-21 17:29:45,200 INFO Initial blacklisted packages: ant-doc
+2013-01-21 17:29:45,201 INFO Starting unattended upgrades script
+2013-01-21 17:29:45,202 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
+2013-01-21 17:29:45,651 DEBUG adjusting candidate version: 'Version: package:'apt-doc' version:'0.7.25.3ubuntu9.13''
+2013-01-21 17:29:45,744 DEBUG Checking: ant-doc ([Origin component:'main' archive:'lucid-updates' origin:'Ubuntu' label:'Ubuntu' site:'archive.ubuntu.com' isTrusted:True, Origin component:'main' archive:'lucid-security' origin:'Ubuntu' label:'Ubuntu'
Bug#692327: libotr: Please provide libotr2
On 05/11/12 10:58, Thibaut VARENE wrote: severity 692327 important thanks I don't see how this is a serious bug. Currently libotr2* are not build from any source package in sid. That means that any packages depending on it cannot transition into testing (if it was not frozen). That also means that libotr5 cannot transition into testing (if it was not frozen). Sure it's not a problem. But if the existing status quo is kept, neither libotr5 nor the new pidgin will make it into wheezy nor jessie. Your package is not fit for inclusion in a stable release. Given your position, maybe you should file removal requests for package that still depend on libotr2. In Ubuntu, I have uploaded libotr2 source package to transition libotr5 into testing and keep all applications that use libotr2 or libotr5 installable and releasable. Thanks, for you time. -- Regards, Dmitrijs. signature.asc Description: OpenPGP digital signature
Bug#692327: libotr: Please provide libotr2
Package: libotr, release.debian.org Severity: serious User: release.debian@packages.debian.org Usertags: transition Recently libotr has been updated to version 4.x.x with binary package name libotr5. By the looks of things, it was done because of pidgin-otr package which now requires libotr5. But this means an un-coordinated transition has started, as there are 6 other packages that build-depend on libotr2-dev and all of them fail to build from source against libotr5-dev: * bitlbee * irssi-plugin-otr * kdenetwork * mcabber * psi-plus * python-otr Please do something to resolve this. Input from release team is highly welcome. Possibilities I can think of are: * revert libotr source package to 3.2.1-1 upload libotr5 (4.0.0-2) source package * keep libotr source package as it is, upload libotr2 (3.2.1-1) source package * provide patches/NMUs to fix FTBFS for above packages when built against libotr5-dev. Usually disruptive uploads like this one, should be co-ordinated with the release team with a transition bug, and staged in experimental to do test rebuilds. Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vcdkevox@canonical.com
Bug#688576: unblock: software-center/5.1.2debian2.1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Please unblock package software-center Fix RC bug 671768 for debdiff see above bug. unblock software-center/5.1.2debian2.1 - -- System Information: Debian Release: wheezy/sid APT prefers quantal-updates APT policy: (500, 'quantal-updates'), (500, 'quantal-security'), (500, 'quantal'), (100, 'quantal-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.6.0-030600rc4-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJQX2+BAAoJEIh7YGGLPBaurvsP+wdChG4UziOLaN8pxqdAEzIv rIspqINSdvE3C2YHlsP24Aq4l/iCGKl2SduhBsMlxEFj2w1teSMUvF8C145NYaRa QJ6qQPd2Rr0PeGf/ClGq1NSCrgy5Y4mdlsVp79fb5pOfuDQds6BsWZanVT9nwB+Z FtNbp+cNCwAjYTOS3wHO8TP7IhK2W0wUe8DhPcOES3NBzle8KgWOi/BAgxQH/6Km JintFoa72tKEpzipw+BX/TyXDsELAGCLLrWrSVtPbxL12WnI3bScpmkoLhhShxMe 28hxLgq35NxmawLcpHuFMYxO1UMgb5U019Jzq+GZLXFiXx0Jqahhh+K5RBeM0Arj lCGaM6arq6f3QPWq/+jduOkxac1/MTE9MvoqKWpjsEPMJ/ENe/c5f4j5YmlkJ06S Acahey1LIJyBmizwFf7FArT1Jd/MWzx5GvLbXlhH0xGt3twbpg7w0wPlmiJrxQMs 8UIuNBi8b6/3bBzhLZL0GDtIrua33owJTBsqYS2QHO8wSWnSLxn4f578QEjJ30HD Io/Er3Wlh8FXKg2ufPfhBxVIIeOnu/5KtFQ4kECvR6pGLvHtPOlCoyefpPWiHUyi BrLR4ecwNKr4QYXmu/CyKJCwWsuhxI8ZWRzZs3b5JbBPqFdZxWDyrXthHqEVqDGA aD8uy5D75cMbGmMZhvO8 =ZGq6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120923202226.20175.20950.reportbug@ip6-localhost
Bug#668206: nmu: rebuild against libsword9
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Please schedule the following nmu to migrate to new libsword9 library. nmu biblememorizer . ALL . -m Rebuild against libsword9 nmu bibletime . ALL . -m Rebuild against libsword9 nmu xiphos . ALL . -m Rebuild against libsword9 dw biblememorizer . ALL . -m libsword-dev = 1.6.2+dfsg-3 dw bibletime . ALL . -m libsword-dev = 1.6.2+dfsg-3 dw xiphos . ALL . -m libsword-dev = 1.6.2+dfsg-3 -- Regards, Dmitrijs. signature.asc Description: OpenPGP digital signature
Hint: sword bibletime biblememorizer
Dear Debian Release Team I would like to hint that source packages sword bibletime biblememorizer should go into testing together. Also package bibletime-i18n is obsolete and should be removed (Bug #536722 against ftp.debian.org) On behalf of Crosswire Packaging Team. -- With best regards Dmitrijs Ledkovs (for short Dima), Ледков Дмитрий Юрьевич -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
