Re: How to handle a package triggering ice or segv during build?
Le 14/06/2013 08:50, Thomas Moulard a écrit : > Dear all, > the ViSP[1] software I maintain is causing GCC[2,3] and Doxygen[4] to crash > on some platforms. > > It is difficult for me to fix or to report these issues as: > 1. I am neither a DD or a DM, > 2. I do not have access to these architectures by myself. Dear Thomas, Even if you are not yet a DD or DM, you are the maintainer of the package and you may (and should) request access to whatever you need to do your work. The limitations are only technical, just think of it as if you were learning how to drive with someone sitting next to you as in the French "conduite accompagnée" system. In particular, you can ask for SSH access to porteboxes. See: http://dsa.debian.org/doc/guest-account/ You will need a DD to support your request. Best would be to ask your usual (or last) sponsor. > I was wondering if opening a bug (on the Debian BTS) for GCC and > Doxygen is acceptable > in this case? If you think the bug is in GCC and Doxygen rather than in your own package, definitely. If the bug is in visp, file a bug against visp instead, to keep track of the issue, request help etc. > Another question is: do DM have SSH access to Debian machines to > validate packages on > various architectures? No, not readily. They need ta ask DSA specifically, just like you. Only they don't need a DD to support the request. Kind regards, Thibaut. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51bac94c.9030...@free.fr
Re: How to handle a package triggering ice or segv during build?
On Thu, Jun 13, 2013 at 11:50 PM, Thomas Moulard wrote: > Dear all, > the ViSP[1] software I maintain is causing GCC[2,3] and Doxygen[4] to crash > on some platforms. [snip] In addition to everything Thibaut mentioned, you also have the option of asking for your package to be rebuilt on the buildds, by requesting a "give-back" for your package. Refer to [1] for details. If you aren't certain that there's a bug specifically with doxygen and/or GCC, I would consider asking for a rebuild first. Intermittent issues on the buildds, while not very common, do tend to occur from time to time on the some of the more obscure archs, e.g. [2]. Regards, Vincent [1] http://release.debian.org/wanna-build.txt [2] http://lists.debian.org/debian-mips/2012/07/msg00034.html -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caczd_tdcjpqywwquor+ui+g5y73c6w11cx2fs2w5wuyl-oi...@mail.gmail.com
Bug#704425: Fwd: review for RFS sysadmin-guide
Hi Debian Mentors, The reviewer comments' have been processed into the new version of the package. New package uploaded and is pending another review and sponsorship. Note that the package was built on amd64 architecture, because that is the only 'sid' distro I have access to these days. Let me know if you can sponsor upload for me, any comments or corrections required before the upload. Thanks, Miklos -- Forwarded message -- From: Bart Martens Date: Fri, Jun 14, 2013 at 5:47 AM Subject: Re: review for RFS sysadmin-guide To: Miklos Quartus Hi Miklos, On Fri, Jun 14, 2013 at 01:10:34AM +0100, Miklos Quartus wrote: > Note that I only have access to amd64 unstable Debian machine, that is why > was built in amd64. That is OK. Most people have only one architecture available. > Let me know how to proceed. Shall I write an email again to debian-mentors > list to ask for sponsors? I suggest to mention on RFS 704425 that "the review comments have been processed into the package at mentors". Then it is clear for everyone that the next step is for a sponsor. The message on the RFS will be automatically copied to the debian-mentors list. Regards, Bart Martens -- Miklos
Re: Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
Hi, Am Wed, 12 Jun 2013 20:05:38 +0200 schrieb kardan : > I tried to compile scantailor and am stuck with zlib1g. > Could not find zlib headers. I solved this, by reinstalling the package. Obviously the header file has been lost on the disk. Now there is another issue with boost. $ cmake . -- Boost version: 1.49.0 -- Could NOT find Boost CMake Error at CMakeLists.txt:297 (MESSAGE): Could not find boost headers or libraries. You may need to install a package named libboost1.35-dev or similarly. ii libboost-dev1.49.0.1 The interesting line CMakeLists.txt is 295: FIND_PACKAGE(Boost 1.35.0 COMPONENTS unit_test_framework prg_exec_monitor) < /usr/share/cmake-2.8/Modules/FindBoost.cmake # Currently this module searches for the following version numbers: # 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, 1.35, 1.35.0, 1.35.1, # 1.36, 1.36.0, 1.36.1, 1.37, 1.37.0, 1.38, 1.38.0, 1.39, 1.39.0, # 1.40, 1.40.0, 1.41, 1.41.0, 1.42, 1.42.0, 1.43, 1.43.0, 1.44, 1.44.0, # 1.45, 1.45.0, 1.46, 1.46.0, 1.46.1, 1.47, 1.47.0, 1.48, 1.48.0, # 1.49, 1.49.0, 1.50, 1.50.0, 1.51, 1.51.0, 1.52, 1.52.0, # 1.53, 1.53.0, 1.54, 1.54.0, 1.55, 1.55.0, 1.56, 1.56.0 With my limited view I assume it is not necessary to request this specific version. Otherwise I see obstacles to use scantailor on wheezy. Any hints are welcome. thanks, kardan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130614151110.4b2dd014@delight
Re: Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
> Now there is another issue with boost. > > $ cmake . > -- Boost version: 1.49.0 > -- Could NOT find Boost > CMake Error at CMakeLists.txt:297 (MESSAGE): > Could not find boost headers or libraries. > > You may need to install a package named libboost1.35-dev or similarly. > > ii libboost-dev1.49.0.1 > > The interesting line CMakeLists.txt is > 295: FIND_PACKAGE(Boost 1.35.0 COMPONENTS unit_test_framework > prg_exec_monitor) > > < /usr/share/cmake-2.8/Modules/FindBoost.cmake > # Currently this module searches for the following version numbers: > # 1.33, 1.33.0, 1.33.1, 1.34, 1.34.0, 1.34.1, 1.35, 1.35.0, 1.35.1, > # 1.36, 1.36.0, 1.36.1, 1.37, 1.37.0, 1.38, 1.38.0, 1.39, 1.39.0, > # 1.40, 1.40.0, 1.41, 1.41.0, 1.42, 1.42.0, 1.43, 1.43.0, 1.44, 1.44.0, > # 1.45, 1.45.0, 1.46, 1.46.0, 1.46.1, 1.47, 1.47.0, 1.48, 1.48.0, > # 1.49, 1.49.0, 1.50, 1.50.0, 1.51, 1.51.0, 1.52, 1.52.0, > # 1.53, 1.53.0, 1.54, 1.54.0, 1.55, 1.55.0, 1.56, 1.56.0 > > With my limited view I assume it is not necessary to request this > specific version. Otherwise I see obstacles to use scantailor on wheezy. I found (1) and there under Configuration: * If you have missing dependencies you will get an error message telling you what is missing. You can then search for the missing package and install it. * If you have a library and header files installed in a non-standard place then cmake will not find them. In that case you can run the interactive program ccmake which allows you to specify paths to libraries and header files. My POV is: As you already found the error (line 295), your conclusion is wrong. You have 1.49.0.1, but cmake searches for 1.35. So patch CMakeLists.txt or run ccmake. If you don't want scantailor just to compile and run on your personal Wheezy box, compile for unstable, wait for testing migration and then do a backport. HTH, Martin 1: http://sourceforge.net/apps/mediawiki/scantailor/index.php?title=Building_from_source_code_on_Linux_and_Mac_OS_X -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51bb1f87.6060...@gmx.de
Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
Hi Martin,
thanks for your answer.
Am Fri, 14 Jun 2013 15:49:59 +0200
schrieb Martin Eberhard Schauer :
> My POV is: As you already found the error (line 295), your conclusion
> is wrong. You have 1.49.0.1, but cmake searches for 1.35.
You are right and I am confused. Boost has already been found at the
beginning but this is forgotten later. I learn, that FIND_PACKAGE
overrides all former states even if it was found already.
Also from [1] I learned that FIND_PACKAGE does not fail because of the
higher version as EXACT is not set, but as you can see in the following
it is about the COMPONENTS.
> So patch CMakeLists.txt or run ccmake.
$ grep -n -i boost CMakeLists.txt
74:INCLUDE(FindBoost)
152:FILE(GLOB boost_dirs1 "${build_outer_dir}/boost_1_[0-9]*_[0-9]*")
153:FILE(GLOB boost_dirs2 "${source_outer_dir}/boost_1_[0-9]*_[0-9]*")
286:BOOST_ROOT boost-build.jam PATHS ${boost_dirs1} ${boost_dirs2}
287:DOC "Path to top-level Boost source directory."
289:SET(Boost_USE_STATIC_LIBS ON)
291:ADD_DEFINITIONS(-DBOOST_TEST_DYN_LINK)
294:SET(Boost_USE_MULTITHREADED ON)
295:FIND_PACKAGE(Boost 1.35.0 COMPONENTS unit_test_framework prg_exec_monitor)
296:FIND_PACKAGE(Boost 1.49.0 COMPONENTS unit_test_framework prg_exec_monitor)
297:FIND_PACKAGE(Boost 1.49.0)
298:FIND_PACKAGE(Boost 1.49.1 COMPONENTS unit_test_framework prg_exec_monitor)
299:IF(NOT Boost_FOUND)
302:"Could not find boost headers or libraries.\n"
303:"You may need to install a package named libboost1.35-dev or
later."
305:ENDIF(NOT Boost_FOUND)
307:INCLUDE_DIRECTORIES(${Boost_INCLUDE_DIRS})
308:LINK_DIRECTORIES(${Boost_LIBRARY_DIRS})
354:${QT_DEFINITIONS} -DBOOST_MULTI_INDEX_DISABLE_SERIALIZATION
573:# There seems to be a bug in either gcc or boost that makes page
sorting either crash
$ cmake .
-- Boost version: 1.49.0
-- Could NOT find Boost
-- Could NOT find Boost
-- Boost version: 1.49.0
-- Could NOT find Boost
CMake Error at CMakeLists.txt:300 (MESSAGE):
Could not find boost headers or libraries.
You may need to install a package named libboost1.35-dev or later
Only the third line hits (except FindBoost in 74). This leads to the
conclusion the there is some problem with the components
'unit_test_framework prg_exec_monitor'. Please correct me.
> If you don't want scantailor just to compile and run on your personal
> Wheezy box, compile for unstable, wait for testing migration and then
> do a backport.
> HTH, Martin
I would like to help. In this case the package is already RFS and I
think repackaging it would be counterproductive?
thanks,
kardan
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130614164259.2cdc67cc@delight
Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
Hi Kardan, I should have looked at 712056 before my answer. But as I did some C programming in the past, I thought that I understood the problem and "Hey, this one is easy to solve" :-( > I would like to help. In this case the package is already RFS and I > think repackaging it would be counterproductive? Yup. There is no need to do it again. But I suggest another point of view. Daniel managed to overcome your problem. His package was reviewed (1) and some work still has to be done. Comparing what you did and what Daniel did may be quite instructive. But instead of browsing in different sources and comparing them it's probably more effictive to have a look at the "maint-guide(-xx)" (2) and "developers-reference" (3) packages - in that order. Take it as an exercise. Reading a text book or listening to some lecture is one thing. Making use of some theory in real life *and failing to do so* is the other thing. And that is really instructive :-( Martin 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712056#15 2: http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=maint-guide 3: http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=all&keywords=developer+reference -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51bb3ee7.8010...@gmx.de
Re: Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
>> My POV is: As you already found the error (line 295), your conclusion
>> is wrong. You have 1.49.0.1, but cmake searches for 1.35.
My POV is wrong :( (see below)
> $ grep -n -i boost CMakeLists.txt
> 74:INCLUDE(FindBoost)
> 152:FILE(GLOB boost_dirs1 "${build_outer_dir}/boost_1_[0-9]*_[0-9]*")
> 153:FILE(GLOB boost_dirs2 "${source_outer_dir}/boost_1_[0-9]*_[0-9]*")
> 286:BOOST_ROOT boost-build.jam PATHS ${boost_dirs1}
${boost_dirs2}
> 287:DOC "Path to top-level Boost source directory."
> 289:SET(Boost_USE_STATIC_LIBS ON)
> 291:ADD_DEFINITIONS(-DBOOST_TEST_DYN_LINK)
> 294:SET(Boost_USE_MULTITHREADED ON)
> 295:FIND_PACKAGE(Boost 1.35.0 COMPONENTS unit_test_framework
prg_exec_monitor)
> 296:FIND_PACKAGE(Boost 1.49.0 COMPONENTS unit_test_framework
prg_exec_monitor)
> 297:FIND_PACKAGE(Boost 1.49.0)
> 298:FIND_PACKAGE(Boost 1.49.1 COMPONENTS unit_test_framework
prg_exec_monitor)
> 299:IF(NOT Boost_FOUND)
> 302:"Could not find boost headers or libraries.\n"
> 303:"You may need to install a package named
libboost1.35-dev or later."
> 305:ENDIF(NOT Boost_FOUND)
You are close here - but I still disagree slightly. As I understand things,
the problem is the incompatibility between the upstream code (above) and the
Debian version - 1.49.0 vs 1.49.0.1.
> You are right and I am confused. Boost has already been found at the
> beginning but this is forgotten later. I learn, that FIND_PACKAGE
> overrides all former states even if it was found already.
> Also from [1] I learned that FIND_PACKAGE does not fail because of the
> higher version as EXACT is not set, but as you can see in the following
> it is about the COMPONENTS.
> $ cmake .
> -- Boost version: 1.49.0
> -- Could NOT find Boost
> -- Could NOT find Boost
> -- Boost version: 1.49.0
> -- Could NOT find Boost
> CMake Error at CMakeLists.txt:300 (MESSAGE):
> Could not find boost headers or libraries.
"but this is forgotten later". Take it as nitpicking - there is a difference
between "not used" and "forgotten". But the *effect* is the same - FTBFS.
Martin
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/51bb467a.6010...@gmx.de
Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
Hi, Am Fri, 14 Jun 2013 18:03:51 +0200 schrieb Martin Eberhard Schauer : > I should have looked at 712056 before my answer. But as I did some C > programming in the past, I thought that I understood the problem and > "Hey, this one is easy to solve" :-( > 1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712056#15 It's all fine for me now. The problems in the linked comment are still relevant but not in relation to boost. I found out that COMPONENT unit_test_framework is delivered by libboost-test-dev, which was missing. I added a patch to notify the user. 300c300 < "You may need to install a package named libboost1.35-dev or similarly." --- > "You may need to install a package named libboost-dev > and libboost-test-dev version 1.35 or later." > Daniel managed to overcome your problem. His package was reviewed (1) > and some > work still has to be done. Comparing what you did and what Daniel did > may be quite instructive. But instead of browsing in different > sources and comparing > them it's probably more effictive to have a look at the > "maint-guide(-xx)" (2) > and "developers-reference" (3) packages - in that order. > 2: > http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=names&keywords=maint-guide > 3: > http://packages.debian.org/search?suite=default§ion=all&arch=any&searchon=all&keywords=developer+reference > Thanks. Will use this in the future. Great software! Definitively worth packaging. A first taste (some scans are in poor quality due to the scan): http://heahdk.net/~kardan/books/ The html is created with scantailor2html, find it attached, free for further distribution. Cheers, Kardan300c300 < "You may need to install a package named libboost1.35-dev or similarly." --- > "You may need to install a package named libboost-dev and libboost-test-dev version 1.35 or later." scantailor2html Description: Binary data
Re: Bug#712056: RFS: scantailor [ITP] -- interactive post-processing tool for scanned document pages
Hey Martin,
one last thing from me on this. Thanks for the fun and the help!
> the problem is the incompatibility between the upstream code (above)
> and the Debian version - 1.49.0 vs 1.49.0.1.
Thanks to the maintainer everything is fine with boost (for this).
Am Fri, 14 Jun 2013 18:36:10 +0200
schrieb Martin Eberhard Schauer :
> >> My POV is: As you already found the error (line 295), your
> >> conclusion is wrong. You have 1.49.0.1, but cmake searches for
> >> 1.35.
>
> My POV is wrong :( (see below)
>
> > $ grep -n -i boost CMakeLists.txt
> > 74:INCLUDE(FindBoost)
> > 152:FILE(GLOB boost_dirs1
> > "${build_outer_dir}/boost_1_[0-9]*_[0-9]*") 153:FILE(GLOB
> > boost_dirs2 "${source_outer_dir}/boost_1_[0-9]*_[0-9]*")
> > 286:BOOST_ROOT boost-build.jam PATHS ${boost_dirs1}
> ${boost_dirs2}
> > 287:DOC "Path to top-level Boost source directory."
> > 289:SET(Boost_USE_STATIC_LIBS ON)
> > 291:ADD_DEFINITIONS(-DBOOST_TEST_DYN_LINK)
> > 294:SET(Boost_USE_MULTITHREADED ON)
> > 295:FIND_PACKAGE(Boost 1.35.0 COMPONENTS unit_test_framework
> prg_exec_monitor)
> > 296:FIND_PACKAGE(Boost 1.49.0 COMPONENTS unit_test_framework
> prg_exec_monitor)
> > 297:FIND_PACKAGE(Boost 1.49.0)
> > 298:FIND_PACKAGE(Boost 1.49.1 COMPONENTS unit_test_framework
> prg_exec_monitor)
> > 299:IF(NOT Boost_FOUND)
> > 302:"Could not find boost headers or libraries.\n"
> > 303:"You may need to install a package named
> libboost1.35-dev or later."
> > 305:ENDIF(NOT Boost_FOUND)
>
> You are close here - but I still disagree slightly. As I understand
> things, the problem is the incompatibility between the upstream code
> (above) and the Debian version - 1.49.0 vs 1.49.0.1.
>
> > Boost has already been found at
> > the beginning but this is forgotten later.
>
> > $ cmake .
> > -- Boost version: 1.49.0
> > -- Could NOT find Boost
> > -- Could NOT find Boost
> > -- Boost version: 1.49.0
> > -- Could NOT find Boost
> > CMake Error at CMakeLists.txt:300 (MESSAGE):
> > Could not find boost headers or libraries.
>
> "but this is forgotten later". Take it as nitpicking - there is a
> difference between "not used" and "forgotten". But the *effect* is
> the same - FTBFS.
>
(: nitpicking back: The error is raised because of the last
unsuccessfull "FIND_PACKAGE(Boost 1.49.1 COMPONENTS unit_test_framework
prg_exec_monitor)" which fails because neither 1.49.1 nor
libboost-test-dev are installed and overrides the success of the former
test (from libboost-dev package info: Version: 1.49.0.1, "This package
is a dependency package, which depends on Debian's default Boost
version (currently 1.49)").
<
FIND_PACKAGE(Boost 1.49.0 COMPONENTS unit_test_framework
prg_exec_monitor)
FIND_PACKAGE(Boost 1.49.1)
>
-- Boost version: 1.49.0
-- Found the following Boost libraries:
-- unit_test_framework
-- prg_exec_monitor
-- Could NOT find Boost
CMake Error at CMakeLists.txt:298 (MESSAGE):
Could not find boost headers or libraries.
You may need to install packages named libboost-dev and
libboost-test-dev version 1.35 or later.
I think the topic is ready to bury :)
Kardan
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130614195618.760500e0@delight
RFS seeking interim sponsor for dov4l and setpwc
Dear mentors, I seek an interim sponsor that can upload the packages dov4l and setpwc. I have a sponsor but he is rather busy with stuff other than Debian at the moment. It would be good if these packages are uploaded as it would close critical bugs (build dependency on the long deprecated dbs). The upstream software is created by Folkert van Heusden. dov4l: Homepage: http://www.vanheusden.com/dov4l/ Description: program to set and query settings of video4linux devices The dov4l program can set properties such as frequency, tuner, inputchannel, mode, brightness, hue, color, contrast, whiteness, palette, width, and height of a video4linux device. It can also query current settings. setpwc: Homepage: http://www.vanheusden.com/setpwc/ Description: program to set and query settings of (mainly) Philips WebCams The setpwc program can set and list various settings of Philips WebCams, and also some WebCams from other manufacturers, but based on the PWC chipset. The program can set properties such as compression preference, framerate, gain control, shutter speed, white red and blue balance, etc. It can also query current settings. . In addition, setpwc can store the settings in nonvolatile RAM, as well as restore factory defaults. The Debian packages are available from: deb http://lennartsson.se/debian/ ./ deb-src http://lennartsson.se/debian/ ./ The key used to sign packages and Release file is available in http://lennartsson.se/anders_lennartsson.asc Regards, Anders Lennartsson -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130614194530.ga7...@isis.lennartsson.se
RFS: s3cmd python module
Hi, I'm completing in ITA via the packing and upload of the new upstream release for s3cmd. I use this tool daily to keep my local files and Amazon S3 backup in sync. I've been using Debian since the release of sarge. For the last year I've been wanting to help in the Debian project. When I saw that s3cmd came up for adoption I jumped at the opportunity. Please review my upload and let me know what needs fixing. https://mentors.debian.net/package/s3cmd Thanks very much, Robinson
