Bug#725671: different source packages, co-ordinated release to jessie
Package: release.debian.org PostBooks has multiple source packages. Specifically, there is src:postbooks (the client) and src:postbooks-schema-(empty|quickstart|demo) The client can only be used with the matching postbooks-schema version Is there an automated way to ensure these packages (and future updates) all propagate to jessie together or not at all? -- 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/52526f5f.4020...@pocock.com.au
Bug#725671: marked as done (different source packages, co-ordinated release to jessie)
Your message dated Mon, 7 Oct 2013 10:42:03 +0200 with message-id 20131007084203.gc29...@mraw.org and subject line Re: Bug#725671: different source packages, co-ordinated release to jessie has caused the Debian Bug report #725671, regarding different source packages, co-ordinated release to jessie 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.) -- 725671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org PostBooks has multiple source packages. Specifically, there is src:postbooks (the client) and src:postbooks-schema-(empty|quickstart|demo) The client can only be used with the matching postbooks-schema version Is there an automated way to ensure these packages (and future updates) all propagate to jessie together or not at all? ---End Message--- ---BeginMessage--- Daniel Pocock dan...@pocock.com.au (2013-10-07): PostBooks has multiple source packages. Specifically, there is src:postbooks (the client) and src:postbooks-schema-(empty|quickstart|demo) The client can only be used with the matching postbooks-schema version Is there an automated way to ensure these packages (and future updates) all propagate to jessie together or not at all? Sure, get your dependencies right… Mraw, KiBi. signature.asc Description: Digital signature ---End Message---
Bug#725661: pu: opencv/2.3.1+dfsg-1
Control: tag -1 wheezy moreinfo Hi, Nobuhiro Iwamatsu iwama...@debian.org (2013-10-07): Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu I'd like to propose an upgrade of opencv. opencv distributed in wheezy includes source code of non-free (#724920). I want to solve this problem. Source code of the target is the code for test. It does not affect the actual working. I attached debdiff. Could you consider this change suitable for stable-proposed-updates? (for the records, we usually prefer when bugs are fixed in testing / unstable before considering updates in stable.) Anyway, if the files indeed got relicensed under a suitable license, why should they get removed from an earlier release? At best we could ship a package with updated headers and licensing info to reflect the facts all those files are actually OK? Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#725661: pu: opencv/2.3.1+dfsg-1
Processing control commands: tag -1 wheezy moreinfo Bug #725661 [release.debian.org] pu: opencv/2.3.1+dfsg-1 Added tag(s) wheezy and moreinfo. -- 725661: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725661 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: http://lists.debian.org/handler.s.b725661.138113528224675.transcr...@bugs.debian.org
Re: Roll call for porters of architectures in sid and testing
On Sun, Sep 01, 2013 at 09:33:51AM +0200, Niels Thykier wrote: If you are (or intend to become) an active porter for the lifetime of jessie, then please send a signed email explaining your involvement in the port to the Release Team debian-release@lists.debian.org before 1st of October 2013. Please explain the level of your involvement in the port. Sorry I missed the deadline, but I guess the information is still valuable. Hi, I am active porter for armel and also help on armhf and arm64. I intend to continue helping for the lifetime for jessie. For armel, I - maintain the buildd's, file bugs on failed builds - provide packagers bugfixes in case they are unable to fix armel bugs in their package themself For armel, armhf and possibly in future for arm64: - test packages on the architectures - fix arch-related bugs I am a DD, Riku Voipio -- 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/20131007101951.ga16...@afflict.kos.to
Re: Results of the porter roll call (Was: Roll call for porters of architectures in sid and testing)
On Wed, Oct 02, 2013 at 04:07:25PM +0100, Wookey wrote: +++ Niels Thykier [2013-10-02 09:45 +0200]: armel: Wookey (DD), Gatis Visnevskis (!DD), Nobuhiro Iwamatsu (DD), Steve McIntyre (DD) armhf: Jeremiah Foster (!DD, but NM?), Wookey (DD), Justus Winter (!DD), Lennart Sorensen (!DD), Nobuhiro Iwamatsu (DD), Steve McIntyre (DD) I am surprised not to see Riku Voipio and Hector Oron on this list as I know they help manage the buildds and Riku signs uploads. I don't know if they are trying to escape, or just being too slack to send mail :-) Sorry, I missed the fact that this request had a deadline. Anyways, I am available for arm related issues - just try not to use debian-devel to reach me, as I tend to just skim subjects here... Riku -- 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/20131007102229.gb16...@afflict.kos.to
Re: [Pkg-phototools-devel] Uncoordinated transition away from libyaml-cpp0.3
Hi! On Mon, Oct 07, 2013 at 01:13:27AM +0200, Cyril Brulebois wrote: you dropped the following binary package from the yaml-cpp source package: libyaml-cpp0.3 It appears it is still depended on by the following packages: [...] | opencolorio: libopencolorio1 [amd64 armel armhf i386 ia64 mips mipsel powerpc s390 s390x sparc] | opencolorio-tools [amd64 armel armhf i386 ia64 mips mipsel powerpc s390 s390x sparc] | python-pyopencolorio [amd64 armel armhf i386 ia64 mips mipsel powerpc s390 s390x sparc] [...] Did you coordinate with your reverse dependencies? At least, I fail to find a transition bug on the release team side for coordination, which isn't too nice. Exactly. A test build on kFreeBSD-amd64 porterbox falla (attached) against yaml-cpp 0.5.1 shows that the package now FTBFS badly. -- Matteo F. Vescovi Debian Maintainer GnuPG KeyID: 0x83B2CF7A dpkg-buildpackage -rfakeroot -D -us -uc dpkg-buildpackage: source package opencolorio dpkg-buildpackage: source version 1.0.9~dfsg0-1 dpkg-buildpackage: source distribution UNRELEASED dpkg-buildpackage: source changed by Matteo F. Vescovi mfv.deb...@gmail.com dpkg-source --before-build opencolorio dpkg-buildpackage: host architecture kfreebsd-amd64 fakeroot debian/rules clean dh clean -Scmake -Bdebian/cmake --parallel --with python2 dh_testdir -O-Scmake -O-Bdebian/cmake -O--parallel debian/rules override_dh_auto_clean make[1]: Entering directory `/home/mfv/opencolorio' pyclean . dh_auto_clean make[1]: Leaving directory `/home/mfv/opencolorio' dh_clean -O-Scmake -O-Bdebian/cmake -O--parallel dpkg-source -b opencolorio dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building opencolorio using existing ./opencolorio_1.0.9~dfsg0.orig.tar.gz dpkg-source: info: building opencolorio in opencolorio_1.0.9~dfsg0-1.debian.tar.gz dpkg-source: info: building opencolorio in opencolorio_1.0.9~dfsg0-1.dsc debian/rules build dh build -Scmake -Bdebian/cmake --parallel --with python2 dh_testdir -O-Scmake -O-Bdebian/cmake -O--parallel debian/rules override_dh_auto_configure make[1]: Entering directory `/home/mfv/opencolorio' dh_auto_configure -- \ -DCMAKE_CXX_FLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 \ -DOCIO_BUILD_DOCS=ON \ -DOCIO_BUILD_NUKE=OFF \ -DOCIO_BUILD_STATIC=OFF \ -DOCIO_BUILD_TESTS=OFF \ -DOCIO_BUILD_TRUELIGHT=OFF \ -DOCIO_USE_SSE=OFF \ -DUSE_EXTERNAL_TINYXML=ON \ -DUSE_EXTERNAL_YAML=ON -- The C compiler identification is GNU 4.8.1 -- The CXX compiler identification is GNU 4.8.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Setting Build Type to: RelWithDebInfo -- Setting Namespace to: OpenColorIO -- Exec prefix not specified, defaulting to /usr -- Use Boost Ptr: OFF -- Setting python bin to: python Python library: /usr/lib/python2.7/config-x86_64-kfreebsd-gnu/libpython2.7.so -- Setting EXTDIST_PYTHONPATH: /usr/lib/python2.7/dist-packages -- Found TinyXML: /usr/lib/x86_64-kfreebsd-gnu/libtinyxml.so -- TinyXML version: 2.6.2 -- External TinyXML will be used. -- Found PkgConfig: /usr/bin/pkg-config (found version 0.26) -- checking for module 'yaml-cpp' -- found yaml-cpp, version 0.5.1 -- System yaml-cpp library will be used. -- Generate Documentation: ON -- Create sphinx conf.py from conf.py.in -- Copying doc to staging area -- Copy extra doc files to staging area -- Extracting .rst files from C++ headers -- SSE Optimizations: OFF -- Create OpenColorABI.h from OpenColorABI.h.in -- Setting OCIO SOVERSION to: 1 -- Create OpenColorIO.pc from OpenColorIO.pc.in -- Build Unit Tests: OFF -- Found OIIO library /usr/lib/libOpenImageIO.so -- Found OIIO includes /usr/include -- Looking for XOpenDisplay in /usr/lib/x86_64-kfreebsd-gnu/libX11.so;/usr/lib/x86_64-kfreebsd-gnu/libXext.so -- Looking for XOpenDisplay in /usr/lib/x86_64-kfreebsd-gnu/libX11.so;/usr/lib/x86_64-kfreebsd-gnu/libXext.so - found -- Looking for gethostbyname -- Looking for gethostbyname - found -- Looking for connect -- Looking for connect - found -- Looking for remove -- Looking for remove - found -- Looking for shmat -- Looking for shmat - found -- Found X11: /usr/lib/x86_64-kfreebsd-gnu/libX11.so -- Found OpenGL: /usr/lib/x86_64-kfreebsd-gnu/libGL.so -- Found OpenGL library /usr/lib/x86_64-kfreebsd-gnu/libGLU.so;/usr/lib/x86_64-kfreebsd-gnu/libGL.so;/usr/lib/x86_64-kfreebsd-gnu/libX11.so;/usr/lib/x86_64-kfreebsd-gnu/libXext.so -- Found OpenGL includes /usr/include -- Could NOT find GLUT
NEW changes in stable-new
Processing changes file: base-files_7.1wheezy2_amd64.changes ACCEPT -- 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/e1vtadj-0005qt...@franck.debian.org
Re: RM: kfreebsd-headers-9.2-1-486 [i386] -- ANAIS; obsolete package
Steven Chamberlain: http://release.debian.org/migration/testing.pl?package=kfreebsd-9 Updating kfreebsd-9 makes 5 non-depending packages uninstallable on i386: cuse4bsd-dkms, fuse4bsd-dkms, kfreebsd-headers-486, kfreebsd-headers-686, kfreebsd-headers-xen Note that britney tests i386 first, then aborts without checking other architectures. cuse4bsd-dkms and fuse4bsd-dkms are Arch: all so I'm not sure why that's a problem. I think Britney considers uninstallability of an Arch: all package on i386 a regression, and therefore doesn't allow it. I guess this part will require manual handling by -release? (CCing) Otherwise we'd have to make those packages kfreebsd-any... kfreebsd-defaults should not provide kfreebsd-headers-* metapackages on linux. I just uploaded 9+2 without them. -- Robert Millan -- 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/5252b23d.1060...@debian.org
NEW changes in stable-new
Processing changes file: base-files_7.1wheezy2_i386.changes ACCEPT Processing changes file: base-files_7.1wheezy2_ia64.changes ACCEPT Processing changes file: base-files_7.1wheezy2_kfreebsd-amd64.changes ACCEPT Processing changes file: base-files_7.1wheezy2_kfreebsd-i386.changes ACCEPT Processing changes file: base-files_7.1wheezy2_mipsel.changes ACCEPT Processing changes file: base-files_7.1wheezy2_powerpc.changes ACCEPT Processing changes file: base-files_7.1wheezy2_s390.changes ACCEPT Processing changes file: base-files_7.1wheezy2_s390x.changes ACCEPT Processing changes file: base-files_7.1wheezy2_sparc.changes ACCEPT Processing changes file: xinetd_2.3.14-7.1+deb7u1_powerpc.changes ACCEPT -- 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/e1vtdg3-dg...@franck.debian.org
NEW changes in stable-new
Processing changes file: base-files_7.1wheezy2_mips.changes ACCEPT -- 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/e1vtdux-0002dh...@franck.debian.org
Re: RM: kfreebsd-headers-9.2-1-486 [i386] -- ANAIS; obsolete package
On 2013-10-07 14:08, Robert Millan wrote: Steven Chamberlain: http://release.debian.org/migration/testing.pl?package=kfreebsd-9 Updating kfreebsd-9 makes 5 non-depending packages uninstallable on i386: cuse4bsd-dkms, fuse4bsd-dkms, kfreebsd-headers-486, kfreebsd-headers-686, kfreebsd-headers-xen Note that britney tests i386 first, then aborts without checking other architectures. cuse4bsd-dkms and fuse4bsd-dkms are Arch: all so I'm not sure why that's a problem. I think Britney considers uninstallability of an Arch: all package on i386 a regression, and therefore doesn't allow it. Specifically, britney requires arch:all packages to be installable on i386, and only checks them on that architecture. I guess this part will require manual handling by -release? (CCing) Otherwise we'd have to make those packages kfreebsd-any... It'd need a force-hint, which says ignore any installability issues created by migrating this source package and only applies to the particular version of the package. That's obviously not ideal for something that's going to want to migrate on a fairly regular basis. Regards, Adam -- 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/2611b9d75ecfc3d471d048ac55b68...@mail.adsl.funky-badger.org
NEW changes in stable-new
Processing changes file: base-files_7.1wheezy2_armel.changes ACCEPT -- 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/e1vtdj3-0004ni...@franck.debian.org
Re: Feel free to let win32-loader/0.7.4.9 into testing
Hi Cyril, (adding ftpmaster in CC). Le lundi, 7 octobre 2013 01.57:42 Cyril Brulebois a écrit : looking at the testing summary page for d-i, I noticed win32-loader is blocked from automatic migration. I'm not sure whether we want to keep it that way but at least the 0.7.4.9 release currently in sid shouldn't hurt AFAICT; some bits of modernity on the source side, and updated Built-Using field on the binary side, so it should be OK to get testing in sync. Sure, no problem for me. FTP-Masters need to copy (shortly after the migration of the package ideally) tools/win32-loader/unstable to tools/win32-loader/testing , see #710514. Cheers, OdyX -- OdyX -- 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/2626879.XAnzoYzleD@gyllingar
NEW changes in stable-new
Processing changes file: base-files_7.1wheezy2_armhf.changes ACCEPT -- 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/e1vtfmf-0003n2...@franck.debian.org
Bug#721921: pu: package ttytter/2.0.1-1+deb7u1
Control: tags -1 + pending On Sat, 2013-10-05 at 11:52 +0100, Adam D. Barratt wrote: On Mon, 2013-09-23 at 04:26 +0200, Cyril Brulebois wrote: Thijs Kinkhorst th...@debian.org (2013-09-05): I'd like to see the possibilities of updating TTYtter in stable. The goal is to make TTYtter work with the new Twitter API: the version currently in wheezy is unusable because of this API change. [...] if the idea is rebuilding 2.1.0-1 in wheezy, you probably could, or even should version it as 2.1.0-1~deb7u1 (adding a changelog entry on top of what's in unstable/testing). [...] The idea doesn't look crazy to me, but the diff is huge… I think I might wait for another opinion on this one. It's less huge than I was expecting it might be, based on that comment. :-) Hopefully twitter won't be making any further large breaking API changes in the near future; please go ahead. For the record, the window for 7.2 officially closed yesterday. However, as ttytter is arch:all and the package in stable is effectively useless right now, I've flagged it for acceptance; thanks for the upload. Regards, Adam -- 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/1381171586.6288.14.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#721921: pu: package ttytter/2.0.1-1+deb7u1
Processing control commands: tags -1 + pending Bug #721921 [release.debian.org] pu: package ttytter/2.0.1-1+deb7u1 Added tag(s) pending. -- 721921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721921 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: http://lists.debian.org/handler.s.b721921.138117159523781.transcr...@bugs.debian.org
NEW changes in stable-new
Processing changes file: ttytter_2.1.0-1~deb7u1_amd64.changes ACCEPT -- 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/e1vtfph-0007oi...@franck.debian.org
Bug#725731: RM: irssi-plugin-otr/0.3-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm The pre-1.0 versions of the OTR plugin are very broken for all software (xchat, irssi, etc) and are considered insecure as OTRv1 is susceptible to downgrade attacks (if my memory is correct). I have been asked by numerous users to remove xchat-otr from squeeze, so here it the formal request. I am going to backport the irssi-otr plugin to wheezy soon, if if there are enough requests, to squeeze-sloppy-backports too. Note, however, that the new version of the package doesn't support xchat anymore, but that is because upstream was never updated. -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.10-0.bpo.2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_CA.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/20131007191458.27953.17881.report...@angela.anarcat.ath.cx
Bug#725311: pu: Getting Debian Edu 7.1+edu0 into the Upcoming stable point release (7.2)
Hi,
On Sonntag, 6. Oktober 2013, Adam D. Barratt wrote:
debian-edu itself is a little more complicated, as the new version adds
a dependency on the new package from debian-edu-config, so we'd have to
take the new versions together (or neither). I'd still like to have more
team discussion around the new package, but it seems like the relevant
people aren't around this weekend. :-( We may have to consider looking
at -edu{,-config} for 7.3.
What could be useful in the short term is an upload of the debian-edu
version currently in wheezy (1.702) just dropping the chmsee recommends.
[21:11] h01ger | adsb: what do you think about uploading debian-edu
1.713 (=jessie + edu0 release version) with chmsee and
debian-edu-config-gosa-netgroup recommends removed? (i
mostly ask because someone forget to keep a tag for 1.702 (sigh!!) and i'd
like to upload something which is based on a sane $vcs version)
[21:12] h01ger | maybe not mostly. its also much closer to what we
really need
[21:12] adsb is it useful without the -edu-config-gosa-netgroups recommends?
[21:12] h01ger | yes.
[21:12] h01ger | way more than 1.702
[21:13] adsb doesn't sound entirely crazy then
[21:13] h01ger | (and people who need this functionality can just
install -edu-config-gosa-netgroups manually)
[21:13] h01ger | so i'll do this instead then. great! :-)
[21:14] h01ger | shall i send this conversation to the bug for the
benefit to those who dont read irc (backlogs)?
[21:15] adsb feel free
[21:15] adsb that leaves -config in the to consider for 7.3 pile
[21:18] h01ger | yes
[21:19] h01ger | and then debian-edu as a consequence :) plus we have
one small bugfix already, which was found after the initial request.. (just a
small partitioning layout change in d-e-i,
but meh..)
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
Bug#725731: RM: irssi-plugin-otr/0.3-2
Hi, tl;dr: I support Antoine's proposal to drop from Squeeze and Wheezy any OTR client or plugin that supports both OTRv1 and OTRv2. I strongly doubt we're still shipping anything that supports v1 only, but it would be wise to check. OTRv1 is susceptible to downgrade attacks (if my memory is correct). Some more background info, in case it matters, or if someone is curious: OTRv1 has various security issues known for years, that were fixed in the v2 protocol. Any client supporting both OTRv1 and OTRv2 (such as pidgin-otr 3.x) is subject to downgrade attacks. So, the only safe way these days is to only support OTRv2. It took a while to obsolete older v1-only software, but now I think the time has come when we can reasonably expect v2-only to work for everyone. (Probably OT as far as the release team is concerned: it might be worth filing CVE's against the clients that still support v1 and v2. Antoine, do you want to ask the OTR developers what's their take on it?) I have been asked by numerous users to remove xchat-otr from squeeze, so here it the formal request. I am going to backport the irssi-otr plugin to wheezy soon, if if there are enough requests, to squeeze-sloppy-backports too. FWIW, I had in mind to do basically the same for pidgin-otr, including the RM request, now that the libotr transition is over. (And no, I've not talked to the maintainer yet, not filed any bug report yet, and I've no idea if they're aware of the big picture in which their specific package is taking part. Will do.) Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- 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/85a9ikdff5@boum.org
Re: RM: kfreebsd-headers-9.2-1-486 [i386] -- ANAIS; obsolete package
Adam D. Barratt: I guess this part will require manual handling by -release? (CCing) Otherwise we'd have to make those packages kfreebsd-any... It'd need a force-hint, which says ignore any installability issues created by migrating this source package and only applies to the particular version of the package. That's obviously not ideal for something that's going to want to migrate on a fairly regular basis. We make it kfreebsd-any then? -- Robert Millan -- 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/525312d4.2060...@debian.org
Bug#725731: RM: irssi-plugin-otr/0.3-2
On 2013-10-07 15:55:26, intrigeri wrote: Hi, (Probably OT as far as the release team is concerned: it might be worth filing CVE's against the clients that still support v1 and v2. Antoine, do you want to ask the OTR developers what's their take on it?) I wouldn't bother, personnally. It took me enough time to file this RM request... :P Cheers, A. -- Travail, du latin Tri Palium trois pieux, instrument de torture. pgp7iVIb8ms5N.pgp Description: PGP signature
Re: RM: kfreebsd-headers-9.2-1-486 [i386] -- ANAIS; obsolete package
On Mon, 2013-10-07 at 20:00 +, Robert Millan wrote: Adam D. Barratt: I guess this part will require manual handling by -release? (CCing) Otherwise we'd have to make those packages kfreebsd-any... It'd need a force-hint, which says ignore any installability issues created by migrating this source package and only applies to the particular version of the package. That's obviously not ideal for something that's going to want to migrate on a fairly regular basis. We make it kfreebsd-any then? For the sake of one (or was it two) extra binary package build, that would seem the easiest solution all round, yes. Regards, Adam -- 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/1381177019.6288.18.ca...@jacala.jungle.funky-badger.org
Bug#725731: RM: irssi-plugin-otr/0.3-2
Control: tags -1 + squeeze pending Control: retitle -1 RM: irssi-plugin-otr -- RoM; security issues On Mon, 2013-10-07 at 21:14 +0200, Antoine Beaupré wrote: The pre-1.0 versions of the OTR plugin are very broken for all software (xchat, irssi, etc) and are considered insecure as OTRv1 is susceptible to downgrade attacks (if my memory is correct). I have been asked by numerous users to remove xchat-otr from squeeze, so here it the formal request. I am going to backport the irssi-otr plugin to wheezy soon, if if there are enough requests, to squeeze-sloppy-backports too. Added to the to-do list for 6.0.8. Regards, Adam -- 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/1381177199.6288.21.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#725731: RM: irssi-plugin-otr/0.3-2
Processing control commands: tags -1 + squeeze pending Bug #725731 [release.debian.org] RM: irssi-plugin-otr/0.3-2 Added tag(s) squeeze and pending. retitle -1 RM: irssi-plugin-otr -- RoM; security issues Bug #725731 [release.debian.org] RM: irssi-plugin-otr/0.3-2 Changed Bug title to 'RM: irssi-plugin-otr -- RoM; security issues' from 'RM: irssi-plugin-otr/0.3-2' -- 725731: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725731 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: http://lists.debian.org/handler.s.b725731.138117721029112.transcr...@bugs.debian.org
Re: Uncoordinated transition from libtorrent-rasterbar6 to libtorrent-rasterbar7
On Sun, 6 Oct 2013 23:59:44 +0200
Cyril Brulebois k...@debian.org wrote:
Hi,
it doesn't appear you coordinated the libtorrent-rasterbar{6,7}
transition with the release team, but I've set up a tracker anyway:
http://release.debian.org/transitions/html/libtorrent-rasterbar7.html
Ideally you would have contacted us in advance, waited for a transition
slot, also making sure your reverse dependencies build and work fine
with the new library. After we gave you a go, you would upload the new
library and we would deal with binNMUs.
Now that the transition started already, please make sure your reverse
dependencies are OK with that change, and report back, so that we
schedule binNMUs, or so that you get reverse dependencies updated to
deal with the new library if needed.
Hi Cyril,
I'm sorry but I've been busy lately (libtorrent-rasterbar has been
NMUed two times in the meanwhile).
AFAICS, the current status of reverse-deps in unstable is:
1) flush: builds fine,
2) qbittorrent: FTBFS, needs upload to unstable of the version in
experimental (3.0.9) or higher,
3) fatrat: FTBFS, but the root cause seems deeper than what I expected
(maybe it needs to be patched for qt compatibility, or dropped at
all).
Thanks,
--
Cristian Greco
GPG key ID: 0xCF4D32E4
signature.asc
Description: PGP signature
Processed (with 3 errors): Bug#725633: nmu: gtg-trace_0.2+dfsg-1
Processing control commands: reassign -1 release.debian.org Bug #725633 [libgtg0] libgtg0: depends on obsolete libotf-trace1 Bug reassigned from package 'libgtg0' to 'release.debian.org'. No longer marked as found in versions gtg-trace/0.2+dfsg-1. Ignoring request to alter fixed versions of bug #725633 to the same values previously set retitle -1 nmu: gtg-trace_0.2+dfsg-1 Bug #725633 [release.debian.org] libgtg0: depends on obsolete libotf-trace1 Changed Bug title to 'nmu: gtg-trace_0.2+dfsg-1' from 'libgtg0: depends on obsolete libotf-trace1' user release.debian@packages.debian.org Unknown command or malformed arguments to command. usertags binnmu Unknown command or malformed arguments to command. subscribe -1 sthiba...@debain.org Unknown command or malformed arguments to command. -- 725633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725633 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: http://lists.debian.org/handler.s.b725633.138118045316630.transcr...@bugs.debian.org
Re: RM: kfreebsd-headers-9.2-1-486 [i386] -- ANAIS; obsolete package
Adam D. Barratt: On Mon, 2013-10-07 at 20:00 +, Robert Millan wrote: Adam D. Barratt: I guess this part will require manual handling by -release? (CCing) Otherwise we'd have to make those packages kfreebsd-any... It'd need a force-hint, which says ignore any installability issues created by migrating this source package and only applies to the particular version of the package. That's obviously not ideal for something that's going to want to migrate on a fairly regular basis. We make it kfreebsd-any then? For the sake of one (or was it two) extra binary package build, that would seem the easiest solution all round, yes. Done (for both fuse4bsd and cuse4bsd). This problem is likely to resurface in the future. Please consider finding a long term solution for Britney. Thanks -- Robert Millan -- 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/52532643.7040...@debian.org
Re: First autoremovals happen in about 8 days
On Sun, Oct 06, 2013 at 09:52:17AM +0200, Niels Thykier wrote: Hi, This is a friendly reminder. If you are listed below, then the listed packages of yours will be automatically removed from testing within 15 days. The first batch of automatic removals will happen in about 8 days. Please remember that fixing your RC bug(s) can sometimes be as simple as correcting the metadata of the bugs (see also #725321[0]) or (where inflated) downgrade the severity of the bug. This mail was a one-time public service annoucement; I *do not* intend to send out reminders in the future. Remember that you can pull the same data from [1] or [2]. I am concerned that in the event a package is removed from testing, the people most interested with restoring the package will miss the removal, since the package will stay installed on their systems. This, then, cause stable releases to be missing packages that users are depending on, which reduce the value of the distribution. This is not a new problem, and it is not entirely clear whether such early removal will reduce or increase this issue. However we should address it if we want Debian stable releases to be something users can rely on. So while it is possible that the _maintainer_ is not needing a friendly remainder, other interested third-party might. Cheers, Bill. -- 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/20131007220421.ga17...@master.debian.org
Bug#725748: pu: package netcfg/1.108
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu wheezy Hi, (first off, sorry for being so late. I would understand punting that until 7.3, etc.) due to check's being broken (#712140) and netcfg's trying to use its pkgconfig file in its master branch, netcfg's #717449 is still unfixed in unstable. The fix I suggested was tested live by Michael, though, and Philipp happily pushed it to git. That's why it doesn't look too insane to me to try and get that into stable now, to lower user surprise when it comes to autoconfigured network after installation. Changelog: | netcfg (1.108+deb7u1) wheezy; urgency=low | | [ Philipp Kern ] | * Wrap dpkg-query call to check for network-manager with sh. | Thanks to Michael Biebl for the patch. (Closes: #717449) | | -- Cyril Brulebois k...@debian.org Tue, 08 Oct 2013 01:04:51 +0200 Sorry again. Mraw, KiBi. diff -Nru netcfg-1.108/debian/changelog netcfg-1.108+deb7u1/debian/changelog --- netcfg-1.108/debian/changelog 2013-04-07 22:00:45.0 +0200 +++ netcfg-1.108+deb7u1/debian/changelog 2013-10-08 01:04:57.0 +0200 @@ -1,3 +1,11 @@ +netcfg (1.108+deb7u1) wheezy; urgency=low + + [ Philipp Kern ] + * Wrap dpkg-query call to check for network-manager with sh. +Thanks to Michael Biebl for the patch. (Closes: #717449) + + -- Cyril Brulebois k...@debian.org Tue, 08 Oct 2013 01:04:51 +0200 + netcfg (1.108) unstable; urgency=low [ Samuel Thibault ] diff -Nru netcfg-1.108/finish-install.d/55netcfg-copy-config netcfg-1.108+deb7u1/finish-install.d/55netcfg-copy-config --- netcfg-1.108/finish-install.d/55netcfg-copy-config 2013-04-07 21:09:45.0 +0200 +++ netcfg-1.108+deb7u1/finish-install.d/55netcfg-copy-config 2013-10-08 01:04:33.0 +0200 @@ -18,7 +18,7 @@ fi # Flag to determine whether Network Manager is installed. -if in-target dpkg-query -s network-manager 2/dev/null | grep -q '^Status: install ok installed'; then +if in-target sh -c dpkg-query -s network-manager 2/dev/null | grep -q '^Status: install ok installed'; then NM_IS_INSTALLED=true else NM_IS_INSTALLED=false
Processed: Re: Bug#725748: pu: package netcfg/1.108
Processing commands for cont...@bugs.debian.org: tag 725748 wheezy Bug #725748 [release.debian.org] pu: package netcfg/1.108 Added tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 725748: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725748 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: http://lists.debian.org/handler.s.c.138118885510319.transcr...@bugs.debian.org
Bug#725751: pu: package iso-scan/1.43
Package: release.debian.org Severity: normal Tags: wheezy User: release.debian@packages.debian.org Usertags: pu Hi, here's another tiny update I'd like to see in stable. Due to a simple error in the state machine, asking the installer to perform a full search (“2nd pass”) to find an ISO image harder would lead back to the 1st pass. This issue was user-reported, user-patched, and fixed in unstable almost a month ago. I think this request can be put in the “nice to have even though not critical” bucket, so definitely OK to delay until 7.3 (yet small enough to be considered for 7.2 though). Slightly terse changelog: | iso-scan (1.43+deb7u1) wheezy; urgency=low | | [ Joey Hess ] | * Fix full search entry when no isos are found. Closes: #722711 | Thanks, Gagou | | -- Cyril Brulebois k...@debian.org Tue, 08 Oct 2013 01:30:36 +0200 Actual patch is an one-liner (fixed status code in the state machine). Mraw, KiBi. diff -Nru iso-scan-1.43/debian/changelog iso-scan-1.43+deb7u1/debian/changelog --- iso-scan-1.43/debian/changelog 2012-11-01 19:41:17.0 +0100 +++ iso-scan-1.43+deb7u1/debian/changelog 2013-10-08 01:30:40.0 +0200 @@ -1,3 +1,11 @@ +iso-scan (1.43+deb7u1) wheezy; urgency=low + + [ Joey Hess ] + * Fix full search entry when no isos are found. Closes: #722711 +Thanks, Gagou + + -- Cyril Brulebois k...@debian.org Tue, 08 Oct 2013 01:30:36 +0200 + iso-scan (1.43) unstable; urgency=low [ Updated translations ] diff -Nru iso-scan-1.43/debian/iso-scan.postinst iso-scan-1.43+deb7u1/debian/iso-scan.postinst --- iso-scan-1.43/debian/iso-scan.postinst 2012-10-14 22:57:15.0 +0200 +++ iso-scan-1.43+deb7u1/debian/iso-scan.postinst 2013-10-08 01:28:02.0 +0200 @@ -408,7 +408,7 @@ if [ $RET = false ]; then exit 1 fi - STATE=10 + STATE=29 continue ;;
Re: First autoremovals happen in about 8 days
Hi, On Dienstag, 8. Oktober 2013, Bill Allombert wrote: So while it is possible that the _maintainer_ is not needing a friendly remainder, other interested third-party might. anyone interested in a package can opt-in via the PTS... cheers, Holger signature.asc Description: This is a digitally signed message part.
Re: Dropped binary package: python-aeidon
Hi KiBi, Ansgar opened #714063 a while back for us and there was some discussion about this bug on the debian-python list at the time. The choices appear to be limited to: (a) upload translate-toolkit with support for translating subtitle files disabled (b) upload an older version of python-aeidon as a different source package (or put an embedded copy in translate-toolkit... yum) and live with the duplication of code and what amounts to a python2-only fork of aeidon. I don't know how widely used the ability to convert to and from subtitle formats is so I don't really know the scope of the impact of dropping python- aeidon support. This is used, for example, in the po2sub/sub2po commands in translate-toolkit which then allows subtitle translators to use the normal range of po editors (virtaal/pootle/poedit/lokalize/etc). Popcon tells me that lots of people have the old python-aeidon installed but that is just because they have translate-toolkit installed [0]. Neither (a) nor (b) is a nice choice which is why I've left this fester while hoping that an option (c) would occur to me. Translate toolkit's upstream is aware of the problem as it will affect them in more places in the long term, but they can always just tell people to get the older version of aeidon from pipy; I've not yet got a response from them. Any advice on (a) vs (b) or a possible (c) from the great and the good of d- release gratefully received. cheers Stuart [0] popcon data gaupol: installed: 2171 translate-toolkit: installed: 5359 python-aeidon: installed: 5692 python3-aeidon: installed: 100 -- Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net Debian Developer http://www.debian.org/ stu...@debian.org GPG fingerprintBE65 FD1E F4EA 08F3 23D4 3C6D 9FE8 B8CD 71C5 D1A8 GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7 signature.asc Description: This is a digitally signed message part.
Re: First autoremovals happen in about 8 days
On Tuesday 08 October 2013 01:51:41 Holger Levsen wrote: Hi, On Dienstag, 8. Oktober 2013, Bill Allombert wrote: So while it is possible that the _maintainer_ is not needing a friendly remainder, other interested third-party might. anyone interested in a package can opt-in via the PTS... I really doubt that possibly interested people will subscribe to all the packages they are interested in. -- Antiguo proverbio del Viejo Machi: Prefiero que mi cerebro esté en la cresta de la ola, y mi PC un paso atrás sirviéndolo y no tener mi PC en el 'estado del arte' y mi cerebro un paso atrás asistiéndola. http://www.grulic.org.ar/lurker/message/20090507.020516.ffda0441.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
