Bug#777312: nmu (for stable): vlc (and mplayer?)
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Dear release team, I just dak-installed liblivemedia_2012.05.17-1+wheezy1 to release a DSA announcing fix for was recently updated in wheezy-security and wheezy-p-u to fix CVE-2013-6933. This requires vlc and mplayer to be built against this new version. The plan is to include all these fixes in the same DSA. vlc is in the security-archive mplayer is not. If I understand correctly, in the mplayer case, I just need to recompile mplayer using the now-installed liblivemedia and upload to security master as a normal security fix. Am I right? Thanks, luciano -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/13687410.RRnST32hlS@box
Bug#777312: nmu (for stable): vlc (and mplayer?)
On Sat, 2015-02-07 at 13:01 +0100, Luciano Bello wrote: I just dak-installed liblivemedia_2012.05.17-1+wheezy1 to release a DSA announcing fix for was recently updated in wheezy-security and wheezy-p-u to fix CVE-2013-6933. This requires vlc and mplayer to be built against this new version. The plan is to include all these fixes in the same DSA. So the binNMUs need to happen in wheezy-security, not p-u. I've just scheduled those. I assume they'll pick up the liblivemedia from security, but I can't check the logs. vlc is in the security-archive mplayer is not. If I understand correctly, in the mplayer case, I just need to recompile mplayer using the now-installed liblivemedia and upload to security master as a normal security fix. Am I right? You'd need the mplayer source in the security archive in order to be able to binNMU it, so if it's not there already then yes it'll need to be uploaded anyway at which point there'd be no need for binNMUs. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1423311982.1857.6.ca...@adam-barratt.org.uk
Bug#777298: unblock (pre-approval): mate-desktop-environment/1.8.0+8
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please consider unblocking of planned upload of package mate-desktop-environment. + * debian/control: ++ The lintian tool complains about the synopsis wording meta package. + Changed to metapackage. - we changed package SYNOPSIS fields to match lintians expectations (and reduce noise). ++ Add to D (mate-desktop-environment-core): gvfs-backend. (Closes: #776698). + + -- Mike Gabriel sunwea...@debian.org Sat, 07 Feb 2015 12:13:37 +0100 - Several features in Caja, MATE's file manager, do not work if gvfs-backend is not installed with a MATE desktop environment. I hope this change is considered release critical and accepted by the RT. light+love, Mike unblock mate-desktop-environment/1.8.0+8 -- System Information: Debian Release: 8.0 APT prefers stable APT policy: (990, 'stable'), (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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: sysvinit (via /sbin/init) diff -Nru mate-desktop-environment-1.8.0+7/debian/changelog mate-desktop-environment-1.8.0+8/debian/changelog --- mate-desktop-environment-1.8.0+7/debian/changelog 2014-08-04 20:02:26.0 +0200 +++ mate-desktop-environment-1.8.0+8/debian/changelog 2015-02-07 12:13:38.0 +0100 @@ -1,3 +1,13 @@ +mate-desktop-environment (1.8.0+8) unstable; urgency=medium + + [ Mike Gabriel ] + * debian/control: ++ The lintian tool complains about the synopsis wording meta package. + Changed to metapackage. ++ Add to D (mate-desktop-environment-core): gvfs-backend. (Closes: #776698). + + -- Mike Gabriel sunwea...@debian.org Sat, 07 Feb 2015 12:13:37 +0100 + mate-desktop-environment (1.8.0+7) unstable; urgency=medium [ Martin Wimpress ] diff -Nru mate-desktop-environment-1.8.0+7/debian/control mate-desktop-environment-1.8.0+8/debian/control --- mate-desktop-environment-1.8.0+7/debian/control 2014-08-04 20:01:10.0 +0200 +++ mate-desktop-environment-1.8.0+8/debian/control 2015-02-07 12:10:31.0 +0100 @@ -30,6 +30,7 @@ mate-terminal (= 1.8.0), mate-desktop (= 1.8.0), gvfs-bin, + gvfs-backend, Breaks: mate-desktop-environment ( 1.8.0), Conflicts: mate-conf, mate-conf-editor, @@ -47,7 +48,7 @@ mate-keyring ( 1.8.0), mate-doc-utils ( 1.8.0), mate-doc-utils-gnome ( 1.8.0), -Description: MATE Desktop Environment (essential components, meta package) +Description: MATE Desktop Environment (essential components, metapackage) The MATE Desktop Environment is the continuation of GNOME 2. It provides an intuitive and attractive desktop environment using traditional metaphors for Linux and other Unix-like operating systems. @@ -98,7 +99,7 @@ Suggests: x-www-browser | iceweasel, mail-reader | icedove, network-manager-gnome, -Description: MATE Desktop Environment (meta package) +Description: MATE Desktop Environment (metapackage) The MATE Desktop Environment is the continuation of GNOME 2. It provides an intuitive and attractive desktop environment using traditional metaphors for Linux and other Unix-like operating systems. @@ -132,7 +133,7 @@ mate-sensors-applet (= 1.8.0), Suggests: mate-netbook (= 1.8.0), mate-user-guide, -Description: MATE Desktop Environment (extra components, meta package) +Description: MATE Desktop Environment (extra components, metapackage) The MATE Desktop Environment is the continuation of GNOME 2. It provides an intuitive and attractive desktop environment using traditional metaphors for Linux and other Unix-like operating systems.
Bug#777316: unblock (pre-approval): x2goclient/4.0.3.1-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please consider unblocking planned upload of package x2goclient
+ * debian/patches:
++ Add 0005_really-logout-from-broker-after-logout.patch. Really log-off a
+ user if --broker-autologoff is used. (Closes: #777314).
- In X2Go upstream we recently discovered an issue with the
--broker-autologoff cmdline
options. For details, please see explanation of this issue in #777314 [1].
[1] http://bugs.debian.org/777314
light+love
Mike
unblock x2goclient/4.0.3.1-4
-- System Information:
Debian Release: 8.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing-updates'), (500,
'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-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: sysvinit (via /sbin/init)
diff -Nru x2goclient-4.0.3.1/debian/changelog x2goclient-4.0.3.1/debian/changelog
--- x2goclient-4.0.3.1/debian/changelog 2015-01-09 21:58:22.0 +0100
+++ x2goclient-4.0.3.1/debian/changelog 2015-02-07 13:15:59.0 +0100
@@ -1,3 +1,11 @@
+x2goclient (4.0.3.1-4) unstable; urgency=medium
+
+ * debian/patches:
++ Add 0005_really-logout-from-broker-after-logout.patch. Really log-off a
+ user if --broker-autologoff is used. (Closes: #777314).
+
+ -- Mike Gabriel sunwea...@debian.org Sat, 07 Feb 2015 13:03:04 +0100
+
x2goclient (4.0.3.1-3) unstable; urgency=medium
* debian/patches:
diff -Nru x2goclient-4.0.3.1/debian/patches/0005_really-logout-from-broker-after-logout.patch x2goclient-4.0.3.1/debian/patches/0005_really-logout-from-broker-after-logout.patch
--- x2goclient-4.0.3.1/debian/patches/0005_really-logout-from-broker-after-logout.patch 1970-01-01 01:00:00.0 +0100
+++ x2goclient-4.0.3.1/debian/patches/0005_really-logout-from-broker-after-logout.patch 2015-02-07 13:00:26.0 +0100
@@ -0,0 +1,39 @@
+From: Sergey_Savko sa...@tophouse.ru
+Date: Fri, 6 Feb 2015 10:30:33 + (+0300)
+Subject: Prevent passwordless re-logins into X2Go Session Broker if --broker-autologoff is...
+X-Git-Url: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff_plain;h=3f85fe2
+
+Prevent passwordless re-logins into X2Go Session Broker if --broker-autologoff is used on the cmdline. (Fixes: #782).
+---
+
+#diff --git a/debian/changelog b/debian/changelog
+#index afd5bf9..c6fe947 100644
+#--- a/debian/changelog
+#+++ b/debian/changelog
+#@@ -35,6 +35,11 @@ x2goclient (4.0.3.2-0x2go1) UNRELEASED; urgency=medium
+# * x2goclient.spec:
+# - Always set BuildRoot: parameter.
+#
+#+ [ Sergey Savko ]
+#+ * New upstream release (4.0.3.2):
+#+- Prevent passwordless re-logins into X2Go Session Broker if
+#+ --broker-autologoff is used on the cmdline. (Fixes: #782).
+#+
+# [ Heinrich Schuchardt ]
+# * New upstream release (4.0.3.2):
+# - Base the layout dialogue Session ID (which shows up when starting a
+diff --git a/httpbrokerclient.cpp b/httpbrokerclient.cpp
+index 5f009d4..5780cca 100644
+--- a/httpbrokerclient.cpp
b/httpbrokerclient.cpp
+@@ -242,6 +242,10 @@ void HttpBrokerClient::slotSshUserAuthError(QString error)
+ void HttpBrokerClient::getUserSessions()
+ {
+ QString brokerUser=config-brokerUser;
++// Otherwise, after logout from the session, we will be connected by a previous user without a password by authid.
++if (config-brokerAutologoff) {
++nextAuthId=config-brokerUserId;
++}
+ x2goDebugcalled getUserSessions: brokeruser: brokerUser authid: nextAuthId;
+ if(mainWindow-getUsePGPCard())
+ brokerUser=mainWindow-getCardLogin();
diff -Nru x2goclient-4.0.3.1/debian/patches/series x2goclient-4.0.3.1/debian/patches/series
--- x2goclient-4.0.3.1/debian/patches/series 2015-01-09 21:55:16.0 +0100
+++ x2goclient-4.0.3.1/debian/patches/series 2015-02-07 13:00:40.0 +0100
@@ -2,4 +2,5 @@
0002_fix-GUI-for-session-profile-subfolders.patch
0003_use-app-setQuitOnLastWindowClose-false-for-X2GoClient-application.patch
0004-fix-quoting+escaping-ssh-commands.patch
+0005_really-logout-from-broker-after-logout.patch
1001_deprecated-apache2-config.patch
Bug#777329: unblock: ntp/1:4.2.6.p5+dfsg-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, ntp 1:4.2.6.p5+dfsg-5 has 2 security fixes. Can you please unblock it? Kurt -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150207131104.ga1...@roeckx.be
Bug#776928: unblock: debian-installer-netboot-images/20150107
Hi, On Freitag, 6. Februar 2015, Niels Thykier wrote: debian-installer-netboot-images (20150107) unstable; urgency=low * Bump debhelper compat level to 9. so I went ahead and prepared the uploaded in git, reverted this change and added myself to uploaders even and then upon running dch -r I noticed the version, which was set to 20150108, which is neither todays date nor, more importantly, the date of the d-i release it contains. Bummer. The README says: * Note about versioning: - This package's version is simply the version of the d-i netboot images it fetches and ships. - Since d-i can be binNMU'd in stable (usually to get built against a newer kernel in proposed-updates, when no source changes are planned for stable), its version ends with +bN; using the exact same version for this package wouldn't work too well because a couple of assumptions are made in the Debian infrastructure (notably in dak) when a binNMU-like version number is seen. To work around those, the .bN suffix is used instead of the usual +bN suffix. but I don't think using a binNMU version for a normal upload would be smart. Given this, and given that the debhelper compat bump was announced in May 2013 and committed in June 2013, I wonder whether the cleanest cause of action wouldnt just be to accept this debhelper bump?!? (Another option would be to delay the upload until the next d-i release, but IMO that would be even worse, as debian-lan-config, debian-edu and debian-edu- config all rely on this package and thus cannot be tested properly since basically forever.) cheers, Holger signature.asc Description: This is a digitally signed message part.
Bug#777340: nmu: usbmuxd_1.1.0-1
Package: release.debian.org Severity: normal Tags: experimental User: release.debian@packages.debian.org Usertags: binnmu nmu usbmuxd_1.1.0-1 . ALL . experimental . -m Rebuild against libimobiledevice 1.2.0 libimobiledevice5 - libimobiledevice6 transition in experimental Andreas -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150207150737.23848.96816.report...@zam581.zam.kfa-juelich.de
Bug#777329: marked as done (unblock: ntp/1:4.2.6.p5+dfsg-5)
Your message dated Sat, 07 Feb 2015 13:29:11 + with message-id 1423315751.1857.7.ca...@adam-barratt.org.uk and subject line Re: Bug#777329: unblock: ntp/1:4.2.6.p5+dfsg-5 has caused the Debian Bug report #777329, regarding unblock: ntp/1:4.2.6.p5+dfsg-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 777329: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777329 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, ntp 1:4.2.6.p5+dfsg-5 has 2 security fixes. Can you please unblock it? Kurt ---End Message--- ---BeginMessage--- On Sat, 2015-02-07 at 14:11 +0100, Kurt Roeckx wrote: ntp 1:4.2.6.p5+dfsg-5 has 2 security fixes. Can you please unblock it? Unblocked. Regards, Adam---End Message---
Bug#777372: wheezy-pu: package frogr/0.7-2
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu The current version of Frogr in Debian wheezy no longer works due to an API change in Flickr. http://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-27th-2014/ A working version is Frogr 0.10, which is already in jessie. I was considering to backport it, but since the version in wheezy is no longer usable, what would be the recommended way to go here? Can I upload 0.10 to wheezy-pu? Should I upload it to backports instead? In that case, should I request the removal of 0.7 from wheezy? Thanks, Berto -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150207184655.28923.99123.reportbug@perseus.local
NEW changes in stable-new
Processing changes file: liblivemedia_2012.05.17-1+wheezy1_amd64.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_armel.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_armhf.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_i386.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_ia64.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_kfreebsd-amd64.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_kfreebsd-i386.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_mips.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_mipsel.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_powerpc.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_s390.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_s390x.changes ACCEPT Processing changes file: liblivemedia_2012.05.17-1+wheezy1_sparc.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_amd64.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_armel.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_armhf.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_i386.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_ia64.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_kfreebsd-amd64.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_kfreebsd-i386.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_mips.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_mipsel.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_powerpc.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_s390.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_s390x.changes ACCEPT Processing changes file: libxml2_2.8.0+dfsg1-7+wheezy3_sparc.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_amd64.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_armel.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_armhf.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_i386.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_ia64.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_kfreebsd-amd64.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_kfreebsd-i386.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_mips.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_mipsel.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_powerpc.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_s390.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_s390x.changes ACCEPT Processing changes file: mplayer_1.0~rc4.dfsg1+svn34540-1+deb7u1_sparc.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_amd64.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_armel.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_armhf.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_i386.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_ia64.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_kfreebsd-amd64.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_kfreebsd-i386.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_mips.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_mipsel.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_powerpc.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_s390.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_s390x.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u2_sparc.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_amd64.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_armel.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_armhf.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_i386.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_ia64.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_kfreebsd-amd64.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_kfreebsd-i386.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_mips.changes ACCEPT Processing changes file: ntp_4.2.6.p5+dfsg-2+deb7u3_mipsel.changes ACCEPT Processing changes file:
Processed: Re: Bug#777372: wheezy-pu: package frogr/0.7-2
Processing control commands: tags -1 + moreinfo Bug #777372 [release.debian.org] wheezy-pu: package frogr/0.7-2 Added tag(s) moreinfo. -- 777372: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b777372.142333836824616.transcr...@bugs.debian.org
Bug#777372: wheezy-pu: package frogr/0.7-2
Control: tags -1 + moreinfo On Sat, 2015-02-07 at 20:46 +0200, Alberto Garcia wrote: The current version of Frogr in Debian wheezy no longer works due to an API change in Flickr. http://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-27th-2014/ A working version is Frogr 0.10, which is already in jessie. I was considering to backport it, but since the version in wheezy is no longer usable, what would be the recommended way to go here? The URL mentioned above suggests that the basic changes are as simple as s/http/https/g. Does the version on frogr in wheezy need any changes beyond that to become functional once more? Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1423338358.746.7.ca...@adam-barratt.org.uk
Processed: closing 777312
Processing commands for cont...@bugs.debian.org: close 777312 Bug #777312 [release.debian.org] nmu (for stable): vlc (and mplayer?) Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 777312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.142334765213807.transcr...@bugs.debian.org
Bug#777114: Re : Re: [Debian-med-packaging] Bug#777114: RM: gridengine/6.2u5-7.3
- Ondřej Surý ond...@debian.org a écrit : I don't see src:gridengine in DELAYED: Tha s fine, i found it in deferred... It is removed. I need to fight to make a clean build. Indeed gridengine doesnt build anymore in jessie because libtiff2 dev is not in jessie. This impacts the build for qmon. I know how to make it pass but needs multiple modifications in d/rules , not simpky skipping all bins generation (but drmaa). I will continue my work next week and expect an upload to unstable before end of next week. Olivier https://ftp-master.debian.org/deferred.html However if you make a correct upload to unstable with same or higher Debian revision in 12 days, it will be discarded from DELAYED anyway. JFTR I always fight with removing from DELAYED as well, there's something specific you need to do and I never remember what it is :). Cheers, Ondrej On Fri, Feb 6, 2015, at 14:45, Olivier Sallou wrote: On 02/06/2015 12:55 PM, Ondřej Surý wrote: Please upload directly to unstable. DELAYED/X is meant as a safety to allow maintainer to react and this package is unmaintained for a long time. No need to wait 12 days to have this fixed. ok I will . I have made however a dcut removal of what I have uploaded. I 've just seen there was an issue with what I uploaded (a mix of builds that I cannot reproduce, and build stuff in debian dir...) Strangely, however, dcut rm returned me mails with: Log of processing your commands file /dcut.Olivier_Sallou__osallou_debian_org_.1423229957.10032.commands: rm --searchdirs libdrmaa-java_6.2u5-7.4_amd64.deb libdrmaa-java_6.2u5-7.4_amd64.deb did not match anything No files to delete I would not like to get what I uploaded in unstable. As I won't be available next few days, would you mind checking for removal ? I will try to fix build and reupload directly in unstable when I am back. Olivier Cheers, Ondrej On Fri, Feb 6, 2015, at 12:15, Olivier Sallou wrote: On 02/05/2015 04:58 PM, Ondřej Surý wrote: Control: retitle -1 (pre-approval) unblock: gridengine/6.2u5-7.4 Control: user release.debian@packages.debian.org Control: usertags -1 unblock The autoremoval is ticking till March, so I think next week is ok. Just close the RC bug on src:gridengine with the upload. Hi, I have upload to delayed/12 the grindengine package. I generate only the libdrmaa-java binary. I have sent to delayed so that one have time to react (as I won't be reachable for the next few days). After this, once accepted in unstable, we can ask for the unblock of the package. Olivier O. On Thu, Feb 5, 2015, at 16:53, Olivier Sallou wrote: On 02/05/2015 04:10 PM, Ondřej Surý wrote: Olivier, could you do NMU to src:gridengine where you remove all binary packages except the DRMAA parts? I am on holiday tonigh, so I won't have time to do it before one week. Do you mean modifying control by commenting out all binaries but the drmma lib binary , and regenerating/uploading the package ? what about the RC bug, we would lower its severity to ?? so that it is not removed ? Thanks Olivier I have no ties to src:gridengine apart to NMUing it once to finish some transition, so it would be better if somebody who actually works with the package would take care of it. Cheers, Ondrej On Thu, Feb 5, 2015, at 16:01, Olivier Sallou wrote: On 02/05/2015 03:56 PM, Salvatore Bonaccorso wrote: Hi, On Thu, Feb 05, 2015 at 09:44:46AM +0100, Ondřej Surý wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 gridengine is RC buggy and effectively unmaintained (see the discussion in #776131). There's an offer to upgrade the package to new upstream and we have a new healthy upstream available, but it's not going to happen for jessie. Ccing logol maintainer who would be affected by the removal, so he can act and prepare logol build without drmaa support in timely manner. For completeness: Another option would be to keep the gridengine sourcepackage and just only built libdrmaa-java. That's what I proposed in bug. I have already made a patch for logol to work without libdrmaa-java but this is definitly a major feature removal :-( Please tell me what is decided so that I ask for patch unblock of logol if everything is removed. Olivier Regards, Salvatore ___ Debian-med-packaging mailing list debian-med-packag...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB
Bug#777384: unblock: gnome-orca/3.14.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Hello,
A few days ago I have received a report from a user whose braille
keyboard does not work when using lightdm to log in (the braille output
works fine). The issue is that lightdm does not define WINDOWPATH,
but only XDG_VTNR, thus confusing the brlapi protocol about which
VT the xbrlapi orca input/output should go to. This needs to be
fixed in both xbrlapi and Orca. Fixing it in xbrlapi breaks the Orca
output completely, so I'm here proposing the Orca upload first, to fix
Bug#777378, and then I'll proceed with xbrlapi, which I'll make Break
the old version of Orca.
I have uploaded gnome-orca 3.14.0-3 with the attached changes.
Basically, the added lines are exactly the same as what is done for the
WINDOWPATH variable, just above.
Samuel
unblock gnome-orca/3.14.0-3
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable'),
(500, 'stable'), (500, 'oldstable'), (1, 'buildd-experimental'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.18.0 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--
Samuel
«Le monochrome, c'est pour ceux qui s'intéressent (encore) au contenu.
Usenet dans ces conditions, c'est comme le web avec lynx, on prend
trop conscience du vide, c'est déprimant.»
-+- JLC in Guide du linuxien pervers : Coup de cafard... -+-
From: Samuel Thibault samuel.thiba...@ens-lyon.org
Subject: [PATCH] Add some basic types for ioctls.
Some applications use unsigned and size_t in ioctls, so bits/ioctls.h
should define _IOT__IOTBASE_unsigned and _IOT__IOTBASE_size_t, here is a
patch.
---
http://sources.redhat.com/ml/libc-alpha/2007-07/msg00078.html
2007-07-21 Samuel Thibault samuel.thiba...@ens-lyon.org
* sysdeps/mach/hurd/bits/ioctls.h (_IOT__IOTBASE_long, _IOT_char,
_IOT_short, _IOT_int, _IOT_long, _IOT__IOTBASE_int8_t,
_IOT__IOTBASE_uint8_t, _IOT__IOTBASE_int16_t, _IOT__IOTBASE_uint16_t,
_IOT__IOTBASE_int32_t, _IOT__IOTBASE_uint32_t, _IOT__IOTBASE_int64_t,
_IOT__IOTBASE_uint64_t, _IOT__IOTBASE_size_t, _IOT__IOTBASE_ssize_t,
_IOTBASE_unsigned, _IOTBASE_signed): Define macros.
sysdeps/mach/hurd/bits/ioctls.h | 23 ++-
1 file changed, 22 insertions(+), 1 deletion(-)
diff --git a/sysdeps/mach/hurd/bits/ioctls.h b/sysdeps/mach/hurd/bits/ioctls.h
index e5203ad..efa7bdf 100644
--- a/sysdeps/mach/hurd/bits/ioctls.h
+++ b/sysdeps/mach/hurd/bits/ioctls.h
@@ -148,9 +148,26 @@ enum __ioctl_datum { IOC_8, IOC_16, IOC_32, IOC_64 };
#define_IOT_SIMPLE(type) _IOT (_IOTS (type), 1, 0, 0, 0, 0)
/* Basic C types. */
-#define_IOT__IOTBASE_int _IOT_SIMPLE (int)
#define_IOT__IOTBASE_char _IOT_SIMPLE (char)
#define_IOT__IOTBASE_short _IOT_SIMPLE (short)
+#define_IOT__IOTBASE_int _IOT_SIMPLE (int)
+#define_IOT__IOTBASE_long _IOT_SIMPLE (long)
+#define_IOT_char _IOT_SIMPLE (char)
+#define_IOT_short _IOT_SIMPLE (short)
+#define_IOT_int_IOT_SIMPLE (int)
+#define_IOT_long _IOT_SIMPLE (long)
+
+#define_IOT__IOTBASE_int8_t_IOT_SIMPLE (int8_t)
+#define_IOT__IOTBASE_uint8_t _IOT_SIMPLE (uint8_t)
+#define_IOT__IOTBASE_int16_t _IOT_SIMPLE (int16_t)
+#define_IOT__IOTBASE_uint16_t _IOT_SIMPLE (uint16_t)
+#define_IOT__IOTBASE_int32_t _IOT_SIMPLE (int32_t)
+#define_IOT__IOTBASE_uint32_t _IOT_SIMPLE (uint32_t)
+#define_IOT__IOTBASE_int64_t _IOT_SIMPLE (int64_t)
+#define_IOT__IOTBASE_uint64_t _IOT_SIMPLE (uint64_t)
+
+#define_IOT__IOTBASE_size_t_IOT_SIMPLE (size_t)
+#define_IOT__IOTBASE_ssize_t _IOT_SIMPLE (ssize_t)
/* Standard flavors of ioctls.
@@ -173,6 +190,10 @@ enum __ioctl_datum { IOC_8, IOC_16, IOC_32, IOC_64 };
#define _IOC_ENCODE_TYPE_1(typespec) _IOC_ENCODE_TYPE_2(typespec)
#define _IOC_ENCODE_TYPE_2(typespec) _IOT_##typespec
+/* Also, ignore signedness. */
+#define_IOTBASE_unsigned
+#define_IOTBASE_signed
+
/* ioctls verbatim from 4.4 sys/ioctl.h. */
--
tg: (58695b8..) t/ioctl-base-types (depends on: baseline)
Bug#776787: unblock: intel-microcode/3.20150121.1
On Fri, 06 Feb 2015, Adam D. Barratt wrote: On Sun, 2015-02-01 at 16:06 -0200, Henrique de Moraes Holschuh wrote: Please unblock package intel-microcode Intel botched a microcode update in the 20150107 release, currently in Debian jessie (testing). This broken microcode update causes core hangs and boot issues on boxes with Intel Xeon E5v3 processors (Debian bug #776431). Unblocked. Thank you! -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150207204713.ga19...@khazad-dum.debian.net
Bug#777136: unblock: ruby-pygments.rb/0.5.4~ds1-2
On Fri, Feb 06, 2015 at 10:59:43PM +0100, Niels Thykier wrote:
Control: tags -1 moreinfo
On 2015-02-05 14:42, Antonio Terceiro wrote:
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package ruby-pygments.rb
This release fixes RC bug #775631 and prevents both this package and
reverse dependencies from being removed from jessie.
the diff against the package in testing is attached.
unblock ruby-pygments.rb/0.5.4~ds1-2
[...]
The upload of ruby-pygements.rb/0.5.4~ds1-2 contains other changes than
the ones listed in your debdiff. In particular:
* It drop of NMU version 0.5.4~ds1-1.1.
* It causes #768615 to be reopened (due to the above). Even if the
changes from 0.5.4~ds1-2 *also* fixes #768615, the BTS thinks the
upload is a regression, since 0.5.4~ds1-2 removes the Closes for
the #768615 bug[1].
* It contains to d/control not mentioned in the changelog and not
listed in the debdiff in this bug.
Please resolve these issues, so that we can accept the changes that
fixes #775631.
Argh, sorry for the mess. I have just uploaded -3 fixing this, with the
attached debdiff.
--
Antonio Terceiro terce...@debian.org
diff -Nru ruby-pygments.rb-0.5.4~ds1/debian/changelog ruby-pygments.rb-0.5.4~ds1/debian/changelog
--- ruby-pygments.rb-0.5.4~ds1/debian/changelog 2014-11-22 14:17:34.0 -0200
+++ ruby-pygments.rb-0.5.4~ds1/debian/changelog 2015-02-07 13:28:09.0 -0200
@@ -1,3 +1,26 @@
+ruby-pygments.rb (0.5.4~ds1-3) unstable; urgency=medium
+
+ * Team upload.
+ * Reverted the previous upload completely, and acknowledged the NMU in
+0.5.4~ds1-1.1 by Tomasz Buchert (Closes: #768615).
+ * Update debian/patches/0007-Update-test-result.patch to fix current FTBFS
+(and properly Closes: #775631).
+
+ -- Antonio Terceiro terce...@debian.org Sat, 07 Feb 2015 13:17:48 -0200
+
+ruby-pygments.rb (0.5.4~ds1-2) unstable; urgency=medium
+
+ * Team upload
+ * fix tests (Closes: #775631):
+- test_highlight_works_with_larger_files: instead of testing for an exact
+ amount of bytes, pass with there are more than 400,000 of them.
+ (debian/patches/0007-Update-test-result.patch)
+- test_highlight_works_with_single_character_input: removed, since the
+ underlying Python code does not support that use case.
+ (debian/patches/0008-Drop-unfeasible-test.patch)
+
+ -- Antonio Terceiro terce...@debian.org Wed, 04 Feb 2015 19:43:57 -0200
+
ruby-pygments.rb (0.5.4~ds1-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru ruby-pygments.rb-0.5.4~ds1/debian/patches/0007-Update-test-result.patch ruby-pygments.rb-0.5.4~ds1/debian/patches/0007-Update-test-result.patch
--- ruby-pygments.rb-0.5.4~ds1/debian/patches/0007-Update-test-result.patch 2014-11-22 14:17:34.0 -0200
+++ ruby-pygments.rb-0.5.4~ds1/debian/patches/0007-Update-test-result.patch 2015-02-07 13:28:09.0 -0200
@@ -5,13 +5,24 @@
slightly different (2.0rc1) and there are some minor mismatches. Most
importantly, the Debian version is unable to find a good lexer for
ambigous code a. It is fixed by forcing it to use Ruby lexer.
+ Also the number of bytes produced cannot be guaranteed.
Already reported upstream https://github.com/tmm1/pygments.rb/issues/118
Author: Per Andersson avtob...@gmail.com
+Reviewed-by: Antonio Terceiro terce...@debian.org
---
--- a/test/test_pygments.rb
+++ b/test/test_pygments.rb
-@@ -88,7 +88,7 @@
+@@ -32,7 +32,7 @@ class PygmentsHighlightTest Test::Unit
+ def test_highlight_works_with_larger_files
+ code = P.highlight(REDIS_CODE)
+ assert_match 'used_memory_peak_human', code
+-assert_equal 455203, code.bytesize.to_i
++assert code.bytesize.to_i 450_000
+ end
+
+ def test_returns_nil_on_timeout
+@@ -88,7 +88,7 @@ class PygmentsHighlightTest Test::Unit
end
def test_highlight_works_with_single_character_input
@@ -20,7 +31,7 @@
assert_match 'a/span', code
end
-@@ -283,5 +283,3 @@
+@@ -283,5 +283,3 @@ class PygmentsConfigTest Test::Unit::T
assert list['Html'][:aliases].include?('html')
end
end
signature.asc
Description: Digital signature
