Re: RFS: libcdk5 (QA upload)
Hi! Scott Howard showard...@gmail.com writes: I am looking for a sponsor for the new version 5.0.20060507-3 of my package libcdk5. This fixes two bugs (a crasher and missing files) and lintian cleaning/policy updating. It builds these binary packages: libcdk5- C-based curses widget library libcdk5-dev - C-based curses widget library (development files) The package appears to be lintian clean. The upload would fix these bugs: 452401, 500161 As Debian is in freeze at the moment, did you check with the release team if that upload is ok? The crash might in fact warrant a severity normal at least Regards Christoph -- 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/877hjubxc1@chillida.ipv6.sieglitzhof.net
shlibs file
HI I understand the role of the Depends: section in the control file information area of a .deb package - it specifies on what other libraries ( and their minimum version) our current shared library (which is in the current .deb file data area) depends in order to work correctly when it is linked to an executable. This will probably stop the current .deb from being installed until we first install all these dependencies packages . But what is the role of the shlibs file ? I am reading the Debian policy chapter 8. Each line of shlibs is of the type : libnamemajor soname version dependency This states that our package library ( assume it contains 1) with given major version number needs the package specified in the dependency field . But this is obvious because we deal /just produced the package that contains this library. Or maybe this information is used later if the package was removed and the shlibs still exist in the system to say what we need reinstall if a binary calls an API of the library and the library is missing ( was before ) Can somebody clarify ? thanks Zvi Dubitzky Email:d...@il.ibm.com IBM Haifa Research LaboratoryPhone: +972-4-8296182 Haifa, 31905, ISRAEL -- 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/of04af9509.12aa7069-onc225777e.004ebaa4-c225777e.00502...@il.ibm.com
What to do about a bug found after the freeze
Hi, A bug was reported upstream in roxterm just after Squeeze's freeze: https://sourceforge.net/tracker/?func=detailaid=3041926group_id=124080atid=698428 Not all the details are there. The main symptom is that if a profile specifies multiple tabs, the commands on the hidden ones don't get started until you click on them, and attempting to use the profile editor to resize a window before these tabs have been activated results in their trying to resize the window to considerably larger than the screen and tying up the CPU for a few seconds. Unfortunately there wasn't a quick fix; I had to change enough code to warrant, in my mind, a version change from 1.18.5(-1) to 1.19.x. This also makes it a good time to release the new web pages someone's designed for me, which should be complete in the next few days. Before that I also made it support configure --htmldir and --docdir correctly, which required a small change to the C code as well as configure.ac and Makefile.am. So what happens about the Squeeze version? 1. Just put up with the bug. 2. Backport just the code that fixes the main bug and call it 1.18.5-2. 3. As 2 but also include the docdir/htmldir correction even though it has no net effect on the Debian package (easier to create the patch). 4. Force 1.19.x into Squeeze with the new web pages. -- TH * http://www.realh.co.uk -- 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/20100813164435.6c1c7...@realh.co.uk
Re: shlibs file
Zvi Dubitzky wrote: I understand the role of the Depends: section in the control file information area of a .deb package - it specifies on what other libraries ( and their minimum version) But what is the role of the shlibs file ? Basically, to contain sufficient (and hopefully correct) information for dpkg-shlibdeps (and wrappers like dh_shlibdeps) in order to be able to generate the needed substvars of a binary package that depends on a particular library at build time. This is the so called shlibs mechanism, slowly being replaced by the more advanced and not-so-new symbols support in dpkg, which unfortunately is not applicable for some programming languages (and for some others, not so convenient to use (and for libraries with only a few reverse dependencies, not a real improvement but a maintenance burden)). But this is obvious because we deal /just produced the package that contains this library. If you (plan to) maintain a library, think from the standpoint of the *users* of the library, not merely as a maintainer of the library package. There are many things that can go wrong when you do the ungrateful job of maintaining a library for Debian, but having this in mind surely helps in many situations. It is not obvious at all (to dpkg and the maintainer of a hypothetical program using the library) what should be put in the Depends: field of a package linking against libfoo; you as a maintainer of the libfoo package ought to make a sound decision when providing/keeping up-to-date correct shlibs or symbols files. Or maybe this information is used later No. -- 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/87zkwq32oo.gnus_not_unix!%ya...@gnu.org
Re: shlibs file
On Fri, Aug 13, 2010 at 05:35:21PM +0300, Zvi Dubitzky wrote:
HI
I understand the role of the Depends: section in the control file
information area of a .deb package - it specifies on what other
libraries ( and their minimum version) our current shared library (which
is in the current .deb file data area) depends
in order to work correctly when it is linked to an executable. This will
probably stop the current .deb from being installed until
we first install all these dependencies packages .
But what is the role of the shlibs file ? I am reading the Debian policy
chapter 8.
Each line of shlibs is of the type : libnamemajor soname version
dependency
This states that our package library ( assume it contains 1) with given
major version number needs the package specified in the dependency field
.
But this is obvious because we deal /just produced the package that
contains this library.
Or maybe this information is used later if the package was removed and
the shlibs still exist in the system to say what we need reinstall if a
binary calls an API of the library and the library is missing ( was
before )
Can somebody clarify ?
From:
http://www.debian.org/doc/debian-policy/ap-pkg-sourcepkg.html#s-pkg-dpkg-shlibdeps
... When a package is built which contains any shared libraries or
compiled binaries, it must run dpkg-shlibdeps on these to determine
the libraries used and hence the dependencies needed by this package.
Then, when you create a package, you can put in your debian/control file:
...
Depends: ${shlibs:Depends}
...
See:
http://www.debian.org/doc/debian-policy/ap-pkg-sourcepkg.html#s-pkg-dpkg-shlibdeps
See also:
http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
http://wiki.debian.org/UsingSymbolsFiles
thanks
Zvi Dubitzky
Email:d...@il.ibm.com
IBM Haifa Research LaboratoryPhone: +972-4-8296182
Haifa, 31905, ISRAEL
Cheers.
--
Josué M. Abarca S.
Vos mereces Software Libre.
PGP key 4096R/70D8FB2A 2009-06-17
Huella de clave = B3ED 4984 F65A 9AE0 6511 DAF4 756B EB4B 70D8 FB2A
--
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/20100813163031.gb3...@rivendel
Re: What to do about a bug found after the freeze
Hola Tony Houghton! El 13/08/2010 a las 16:44 escribiste: A bug was reported upstream in roxterm just after Squeeze's freeze: https://sourceforge.net/tracker/?func=detailaid=3041926group_id=124080atid=698428 All new uploads need to be approved manually by the release team members to enter in squeeze. It's prefered to upload only bugfixes, and not new features, or upstream releases. -- recursividad 95, 154, 156, 201, 224, 293 -- El Lenguaje de Programacion C, pag. 293 (Kernighan Ritchie) Saludos /\/\ /\ `/ -- 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/20100813190154.gi21...@maxy.com.ar
Re: What to do about a bug found after the freeze
On Fri, 13 Aug 2010 16:01:54 -0300 Maximiliano Curia m...@debian.org wrote: Hola Tony Houghton! El 13/08/2010 a las 16:44 escribiste: A bug was reported upstream in roxterm just after Squeeze's freeze: https://sourceforge.net/tracker/?func=detailaid=3041926group_id=124080atid=698428 All new uploads need to be approved manually by the release team members to enter in squeeze. It's prefered to upload only bugfixes, and not new features, or upstream releases. OK, it sounds like the best policy is the second one (backport just the bugfix). Would it be good practice to file a Debian bug report against 1.18.5-1 first even though it's already in the upstream tracker? -- TH * http://www.realh.co.uk -- 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/20100813203528.6ba8e...@realh.co.uk
Default Configuration Issues
Hey Mentors, I'm a co-maintainer on the Fluxbox package. I have recently moved to packaging their git head, as their last release was 2008 ( even though they have had regular development since then ). The stock ( un-configured ) behavior of Fluxbox was to allow window-dragging with a left-click. This has been changed for the next release ( and thusly, the git head ). Since this was stock before, the old version of the debian keys file does not have the configuration directive ( OnTitlebar Mouse1 :StartMoving ) to enable left-click window moving. I found this out early, and patched the global configuration file. Fluxbox, however, copies the file to the ~/.fluxbox folder, and uses that without checking for additional directives in the global conf file. Whoops. This is causing breakage of old installs that are upgrading. What is the right way of fixing this? -Paul Tagliamonte -- #define sizeof(x) rand() :wq -- 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/aanlktims+5oftjhy71pylyjwnb0xsz1k97p=ecgqo...@mail.gmail.com
Re: RFS: xinput-calibrator
On Sun, Aug 8, 2010 at 1:13 AM, Tias t...@ulyssis.org wrote: I am looking for a sponsor for my package xinput-calibrator. ... I would be glad if someone verified and uploaded this package for me. Here is a review: Since you're upstream it might be a good idea to add a configure option to turn on xinput_calibrator_LDFLAGS = -Wl,--as-needed instead of using a patch. If not, then please add DEP-3 headers to the patch. http://dep.debian.net/deps/dep3/ debian/patches/debian-changes-0.7.0-2 should probably be replaced by using dh-autoreconf to rebuild the autotools stuff. Your Standards-Version is out of date, please review upgrading-checklist.txt from debian-policy and make the appropriate changes. Your debian/changelog does not close your ITP. You can remove the comments from debian/rules. Your debian/rules probably doesn't need to run ./autogen.sh since release tarballs will always have ./configure in them unless they were created in a broken way (i.e. not with `make distcheck`). In any case, running it from the pattern rule is the wrong place and you should use the override_dh_auto_configure rule. Usually DH_VERBOSE isn't set in debian/rules. Please split build instructions from README into README.install since they are not useful for users of the binary packages. Please split changes between releases from README into a NEWS file. After that, README will only contain information that is duplicated in the package description and elsewhere so you can probably just not ship it in the Debian package. I read on the upstream website that it only uses pure X11, but you build-depend on GTKmm, why is that? Looking at the debian/changelog you seem to regard Debian as a desktop distribution. Debian is a universal distribution and is used on everything from phones to servers. IMO it would be good to offer both the GTKmm and the pure X11 versions on Debian. You might want to contact Thibaut GIRKA who is adding support for the OpenMoko FreeRunner to the Debian installer. I imagine that touch-screen calibration is something that would be useful in d-i/g-i. There is a spelling error in the code: s/tranditional/traditional/ Why does the .desktop file run cat? Since I have an OpenMoko FreeRunner and use this software on non-Debian partitions I'm interested to have it in Debian too. lintian complaints: I: xinput-calibrator source: quilt-patch-missing-description link_as_needed.patch W: xinput-calibrator source: out-of-date-standards-version 3.8.4 (current is 3.9.1) I: xinput-calibrator: spelling-error-in-manpage usr/share/man/man1/xinput_calibrator.1.gz usefull useful I: xinput-calibrator: spelling-error-in-manpage usr/share/man/man1/xinput_calibrator.1.gz Usefull Useful I: xinput-calibrator: spelling-error-in-binary ./usr/bin/xinput_calibrator Succesfully Successfully I: xinput-calibrator: spelling-error-in-binary ./usr/bin/xinput_calibrator Succesfully Successfully I: xinput-calibrator: spelling-error-in-binary ./usr/bin/xinput_calibrator necesary necessary I: xinput-calibrator: spelling-error-in-binary ./usr/bin/xinput_calibrator necesary necessary -- bye, pabs http://wiki.debian.org/PaulWise -- 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/aanlktikr6k8psjgcnjw615n9kdshoi-7sfxoqrhhy...@mail.gmail.com
Re: Default Configuration Issues
Hi, Paul.
On Aug 13 2010, Paul Tagliamonte wrote:
I'm a co-maintainer on the Fluxbox package.
I happen to be a user of fluxbox.
Oh, just one stylistic note about the way that you write things both in
your text and in your changelogs:
( even though they have had regular development since then ).
You seem to put one space after a left parenthesis and one before the
right parenthesis. The usual rules for typesetting text dictates that
there should be no such spaces. Therefore, the text above should be
written as:
(even though they have had regular development since then).
The stock ( un-configured ) behavior of Fluxbox was to allow
window-dragging with a left-click.
You probably meant window dragging with a left click on the title bar,
right?
Since this was stock before, the old version of the debian keys file
does not have the configuration directive ( OnTitlebar Mouse1
:StartMoving ) to enable left-click window moving.
OK.
I found this out early, and patched the global configuration file.
OK.
Fluxbox, however, copies the file to the ~/.fluxbox folder,
the file means the global configuration file?
and uses that without checking for additional directives in the global
conf file. Whoops.
This is not clear: you say that uses that (the global config file?)
without checking for additional directives in the global conf file.
If it is using the global configuration file, it is honoring the
settings there, isn't it?
Your description didn't sound precise here.
This is causing breakage of old installs that are upgrading. What is
the right way of fixing this?
In general, a change in behavior can be handled gracefully with some
time for transitions, so that they users can adapt to that (before
that becomes the default) and with a conspicuous notice (say, in NEWS).
Regards,
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
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/20100814055539.ga2...@ime.usp.br
