Re: Supporting armel/armhf in wheezy-lts
On Mon, 18 Apr 2016, Raphael Hertzog wrote: > In the mean time, the sponsor clarified that they will join as "gold > sponsor" so they are effectively sponsoring 8 hours of work per month, > which seems to be enough to cover for the increased work that those > ports might represent. The sponsorship is now confirmed since they have paid for a full year already. Plat'Home is the fourth gold LTS sponsor. >From IRC discussions it looks like that the buildd maintainers (at least Neil Williams and Riku Voipio) have no objections to supporting armel/armhf (Riku is rather pleased by it). On the ftpmaster side, I had no official feedback but at least Ansgar seemed to be fine with it when I asked him on IRC. On the Debian Admin side, I have not had any feedback yet. The LTS period is about to start soon and we will send out an announce soon... it would be nice to be able to say a word about armel/armhf, so an official confirmation from ftpmasters/DSA would be nice. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Re: Supporting armel/armhf in wheezy-lts
]] Raphael Hertzog I am not speaking on behalf of DSA here. > The LTS period is about to start soon and we will send out an announce > soon... it would be nice to be able to say a word about armel/armhf, so > an official confirmation from ftpmasters/DSA would be nice. So, I'm a bit divided on all this. While the DMUP is heavy artillery and we should be careful about invoking it, I think it crosses the line in «Don't use Debian Facilities for private financial gain or for commercial purposes, including consultancy or any other work outside the scope of official duties or functions for the time being, without specific authorization to do so.», so you need explicit authorization before you start. We have to balance multiple issues here: on one hand, LTS is clearly useful. On the other hand, Debian is a volunteer organisation and we don't pay people to work on Debian. By asking for donations for «Debian LTS» and then paying folks to work on it, we're at least very, very close to that line, if we don't cross it, somewhat depending on who «we» are and how it's marketed and presented, and I think that is not particularly clearly communicated today. JFTR, for me at least, this isn't about wanting a piece of the action; I don't want to be paid for my DSA work. One option I've been toying about with (but which I'm not sure is a good one) is that some portion of the Debian LTS income go to Debian, rather than individuals. -- Tollef Fog Heen UNIX is user friendly, it's just picky about who its friends are
Re: libidn test packages [resent]
On 2016-04-16 18:46:50, Alessandro Ghedini wrote: > On Tue, Apr 12, 2016 at 03:20:04PM -0400, Antoine Beaupré wrote: >> (Fixed list address, sorry for the duplicate.) >> >> Hi, >> >> I have looked at porting the security fixes on the libidn package from >> squeeze to wheezy. As usual, signed test packages are available here: >> >> https://people.debian.org/~anarcat/debian/wheezy-lts/ >> >> And a debdiff is available for review by the security team: > > FWIW I already prepared wheezy and jessie packages for this a while ago: > https://people.debian.org/~ghedo/libidn_1.25-2+deb7u1.diff > https://people.debian.org/~ghedo/libidn_1.29-1+deb8u1.diff > > But never uploaded them because I couldn't get the jessie one to build. > > This was sort of "documented" in the dsa-needed.txt file and IIRC Tianon Gravi > was also interested in this a while ago. Interesting, it seems I missed that... Your patchset differs from mine significantly. It seems you have reran gnulib in there? I have found that it was easier to just add the missing check code through patches and rerun autoconf, as it makes the patch more readable... Did the wheezy version compile and work correctly? I have not worked on a jessie version so I can't comment on that... Not sure how to handle the twin pacakges, sorry I missed your packages... A. -- Freedom is being able to make decisions that affect mainly you. Power is being able to make decisions that affect others more than you. If we confuse power with freedom, we will fail to uphold real freedom. - Richard Stallman
Re: libidn test packages [resent]
On Fri, Apr 22, 2016 at 03:17:19pm -0400, Antoine Beaupré wrote: > On 2016-04-16 18:46:50, Alessandro Ghedini wrote: > > On Tue, Apr 12, 2016 at 03:20:04PM -0400, Antoine Beaupré wrote: > >> (Fixed list address, sorry for the duplicate.) > >> > >> Hi, > >> > >> I have looked at porting the security fixes on the libidn package from > >> squeeze to wheezy. As usual, signed test packages are available here: > >> > >> https://people.debian.org/~anarcat/debian/wheezy-lts/ > >> > >> And a debdiff is available for review by the security team: > > > > FWIW I already prepared wheezy and jessie packages for this a while ago: > > https://people.debian.org/~ghedo/libidn_1.25-2+deb7u1.diff > > https://people.debian.org/~ghedo/libidn_1.29-1+deb8u1.diff > > > > But never uploaded them because I couldn't get the jessie one to build. > > > > This was sort of "documented" in the dsa-needed.txt file and IIRC Tianon > > Gravi > > was also interested in this a while ago. > > Interesting, it seems I missed that... > > Your patchset differs from mine significantly. It seems you have reran > gnulib in there? I have found that it was easier to just add the missing > check code through patches and rerun autoconf, as it makes the patch > more readable... I simply imported the upstream commits and worked from there. Not many changes were required IIRC, and I certainly didn't re-run gnulib (but I did run autoconf since the upstream repo doesn't include the configure and Makefile.in files). > Did the wheezy version compile and work correctly? Yes, as far as I remmber. Cheers signature.asc Description: PGP signature
Re: working for wheezy-security until wheezy-lts starts
Brian May writes: > libpostproc-dev will be uninstallable - does this matter? Whoops. Just noticed that libpostproc-dev is provided by the old libav, however not provided by the new libav. I had thought it was another source package. So any packages that depend on it will need to be fixed not to depend on it. -- Brian May
Re: working for wheezy-security until wheezy-lts starts
Moritz Muehlenhoff writes: > In general, all the libav transitions have been handled via the BTS, so > patches > should be found there. Some packages also ended up being > incompatible/abandoned > and were eventuall removed, so please also check whether any of the failing > packages are actually still in jessie. Otherwise they should be EOLed. I can't see any patches for opencv. Or should I jump straight to the Jessie version? Some problems are easy solved: * Prefix CODEC_* macros with AV_ * CodecID --> AVCodecID * Drop CODEC_ID_SNOW However it looks like other problems are due to use of legacy APIs which have been removed. My current error/warning list is: In file included from /<>/modules/highgui/src/cap_ffmpeg.cpp:45:0: /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In member function 'void CvCapture_FFMPEG::close()': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:457:31: error: 'av_close_input_file' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In member function 'bool CvCapture_FFMPEG::reopen()': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:488:27: error: 'av_close_input_file' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:491:52: error: 'av_open_input_file' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:492:27: error: 'av_find_stream_info' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:499:50: error: 'avcodec_thread_init' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:502:28: error: 'avcodec_open' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In member function 'bool CvCapture_FFMPEG::open(const char*)': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:529:63: error: 'av_open_input_file' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:534:33: error: 'av_find_stream_info' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:546:54: error: 'avcodec_thread_init' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:551:36: error: 'avcodec_open' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:555:23: warning: 'AVFrame* avcodec_alloc_frame()' is deprecated (declared at /usr/include/libavcodec/avcodec.h:3211) [-Wdeprecated-declarations] /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:555:43: warning: 'AVFrame* avcodec_alloc_frame()' is deprecated (declared at /usr/include/libavcodec/avcodec.h:3211) [-Wdeprecated-declarations] /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In member function 'double CvCapture_FFMPEG::getProperty(int)': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:734:74: error: 'AVStream' has no member named 'r_frame_rate' /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:770:34: error: 'AVStream' has no member named 'r_frame_rate' /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In member function 'bool CvCapture_FFMPEG::setProperty(int, double)': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:818:64: error: 'AVStream' has no member named 'r_frame_rate' /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In function 'AVFrame* icv_alloc_picture_FFMPEG(int, int, int, bool)': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1000:12: warning: 'AVFrame* avcodec_alloc_frame()' is deprecated (declared at /usr/include/libavcodec/avcodec.h:3211) [-Wdeprecated-declarations] /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1000:32: warning: 'AVFrame* avcodec_alloc_frame()' is deprecated (declared at /usr/include/libavcodec/avcodec.h:3211) [-Wdeprecated-declarations] /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In function 'AVStream* icv_add_video_stream_FFMPEG(AVFormatContext*, AVCodecID, int, int, int, double, int)': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1031:26: error: 'av_new_stream' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1117:21: error: 'AV_CODEC_FLAG_GLOBAL_HEADER' was not declared in this scope In file included from /<>/modules/highgui/src/cap_ffmpeg.cpp:45:0: /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In function 'int icv_av_write_frame_FFMPEG(AVFormatContext*, AVStream*, uint8_t*, uint32_t, AVFrame*)': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1149:72: error: 'avcodec_encode_video' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In member function 'void CvVideoWriter_FFMPEG::close()': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1326:20: error: 'url_fclose' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp: In member function 'bool CvVideoWriter_FFMPEG::open(const char*, int, double, int, int, bool)': /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1439:35: error: 'av_set_parameters' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1443:35: error: 'dump_format' was not declared in this scope /<>/modules/highgui/src/cap_ffmpeg_impl.hpp:1470:36: error: 'avcodec_open' was not declared in this scope /<>/modules/h
Re: working for wheezy-security until wheezy-lts starts
Brian May writes: > Whoops. Just noticed that libpostproc-dev is provided by the old libav, > however not provided by the new libav. I had thought it was another > source package. What do I do with ffmpeg? Looks like this use to be provided by libav. Jessie doesn't have ffmpeg (except in backports). Stretch has ffmpeg new package from new source. So guessing the solution might be to backport the stretch version to wheezy? Some packages from wheezy do depend on ffmpeg (e.g. synfig). -- Brian May
