Watchfile (and version numbers) for a braindead scheme

Hi, I want to write a watch file for the "esomidas" package, which has download URLs like ftp://ftp.eso.org/pub/midaspub/13SEP/sources/13SEPpl1.1.tar.gz (12 is the two-digit year, FEB the month of the release). I have some problems with it: 1. What should the version number look like for Debia

arch-dependent files in "Multi-Arch: same" package

Hi, for some of my newly uploaded packages, I got a bug report 'arch-dependent files in "Multi-Arch: same" package' [1]. The files in question are in /usr/share/doc/. However, these differences do not come from differences in the architecture but from different build environments. Specifically, t

Re: arch-dependent files in "Multi-Arch: same" package

Andreas Metzler writes: > Olе Streicher wrote: >> My question here is now how strict it is to have identical files in >> /usr/share/doc even when build in a different environment (basically, >> both versions are fine here). > > Hello, > It is quite important. If t

Re: arch-dependent files in "Multi-Arch: same" package

Paul Wise writes: > On Mon, Dec 30, 2013 at 3:00 AM, Olе Streicher wrote: >> This would be an option, as long as there is not complaint that an >> arch-independent package should be generated identically regardless of >> the architecture it is built on :-) > At some

dh: different dh option for -indep

Hi, my package will create a separate arch-independent -doc package with "sphinxdoc". Since therefore sphinx is not needed for architecure dependent builds, I moved the build dependency of the package into the Build-Depends-Indep field in debian/control: -8<---

Splitting a package

Hi, to solve the problem of , split my package into an arch-dependent part (containing the binaries) and an arch-independent part (containing the manual pages and HTML documentation): cpl-plugin-fors (4.11.12+dfsg-1) --> cpl-plugin-fors + cpl-plugin-fors-doc (4.11.

Re: Splitting a package

Arno Töll writes: > Hi Ole, > On 12.01.2014 13:30, Olе Streicher wrote: >> However, now I get a bug report <http://bugs.debian.org/734917> that the >> new "-doc" package has files that would overwrite parts of the old base >> package. > Please u

Bug archiving

Hi list, I just re-inserted a package that was removed from Debian a year ago (saods9), and following some recommendations, I exhumated the old bugs and set them to "fixed" in the new version. Shall I archive them now again manually? Or is this done somehow automatically? What is this "archived"

Re-inserting package with name change

Hi, I am working to re-insert a package that was removed three years ago. Since the package name is quite short, I also changed its name: the package name was "fv" [1], and I changed it to "ftools-fv" [2]. As recommended, I also exhumed the bugs that were closed by the package removal. They will

How to remove a package from unstable

Hi, I accidently uploaded a package to unstable (python-cpl) that should have gone to experimental. How can I remove that from unstable but not from testing? After reading http://wiki.debian.org/ftpmaster_Removals, I am unsure whether the package would be removed from testing as well if I would j

Hardening-check reports on hardened object

Hi, For the python-astropy package [1], I have a source code [2], that is compiled into a shared library (for a Python extension). The hardening flags are switched on, as seen from the build log: ---8<-- gcc -pthread -fno-strict-aliasing -DNDEBUG -g

Lintian says "package-contains-ancient-file"

Hi, I am currently working on the (re-)packaging of the "IRAF" astronomical package [1]. This is a huge package with old roots -- the history goes back to the early eighties. Therefore, the package contains a couple of files which are quite old -- some help files, sources, documentation etc. date

Multiarch: how to get arch in runtime?

Hi, I am currently creating a package [1] that I want to have Multiarch enabled. The program is started via a link to a shell script (for historic reasons, this is C shell): /usr/bin/iraf-cl -> /usr/share/iraf/unix/hlib/cl.csh where the shell script contains some environmental settings, and then

Re: Multiarch: how to get arch in runtime?

Adam Borowski writes: > But, what is the reason you want the executable to be multiarched for? In my case you are right. However, in the general case if think there is a good use case: If you have a program that uses precompiled extensions, and you have an extension only available on a certain a

Directories: FHS; permissions

Hi, In my package, I need two directories that have the permission "drwxrwxrwt": Users shall be able to create a subdirectory on their own there: one is a cache area, and the other is a storage place. The original places are /iraf/cache/ and /iraf/imdirs/, which obviously contradicts the FHS. So,

[Repost] RFS: cpl-plugin-* [ITP] -- ESO data reduction pipeline recipes

Dear mentors, Since I didn't get response since three weeks, I am reposting my Requests For Sponsorship so that it does not get lost: I have prepared five packages that have a similar structure and are to be used as plugins for the "cpl" library and the "esorex" and "python-cpl" packages. Each pl

Re: [Repost] RFS: cpl-plugin-* [ITP] -- ESO data reduction pipeline recipes

Hi Julian, Julian Taylor writes: > you put in the current maintainers of the pipelines as upstream > authors. Can you please check with them if this is correct. So far I > know the support for this software is supposed to go over > usd-h...@eso.org Also its Upstream-Contact not Upstream-Author i

How to bring life into a (Tk) package?

Dear list, I want to adopt the package "tktable2.9" but I found me confronted with some problems: 1. The package name contains the version, and since the upstream version is now 2.10, I would need to give a new name. 2. The package was orphaned since 2008 and is removed from unstable (and testi

Re: How to bring life into a (Tk) package?

Andrew Shadura writes: > Tcl API is stable enough to just depend on the lowest version it builds > against; however, it's better to build-depend on unversioned packages > (eg tcl and tk instead of tcl8.5 and tk8.5) but use versioned > dependencies on unversioned packages for your binaries (like, t

uscan, dfsg and changelog

Hi, I have a source that needs to be repackaged due to some copyright issues. From the Mentors FAQ, I found that I should name the package "foo-1.2.3+dfsg-1". So, I made a repacking script (should it have a predefined name, btw?) like: 8<--- #!/bin/sh ver=$2 or

docbase trouble

Hi everyone, on my current package, lintian complains about I: xpa-dev: possible-documentation-but-no-doc-base-registration in the package directory, I have: $ ls debian/xpa-dev/usr/share/doc/xpa-dev acl.html convert.html info.html server.htmlxpa.pdf.gz changelog.Debian.g

Re: docbase trouble

kuLa writes: > On 18/01/12 15:10, Olе Streicher wrote: >> 2. The changelog.html.gz was installed by dh_installchangelogs. However, >> the file is referenced by help.html, so I would like to have it >> uncompressed. Is there a way to instruct dh_installchangelog to keep it >

Changelog (Was: docbase trouble)

kuLa writes: > On 18/01/12 15:22, Olе Streicher wrote: >> kuLa writes: >>> On 18/01/12 15:10, Olе Streicher wrote: >>>> 2. The changelog.html.gz was installed by dh_installchangelogs. However, >>>> the file is referenced by help.html, so I would like to

Re: RFS: tk-table

"Joseph R. Justice" writes: > I would suggest that a more obvious and natural fit for a maintenance > home for this package would be: > Debian Tcl/Tk Packagers - mailto:pkg-tcltk-de...@lists.alioth.debian.org > QA Page - > http://qa.debian.org/developer.php?login=pkg-tcltk-devel%40lists.alioth.

Re: RFS: tk-table

Andrew Shadura writes: >> Depends: ${tcl:Depends}, ${tk:Depends}, ${misc:Depends}, >> ${shlibs:Depends} > For that to work properly, you have to call tcltk-depends during > package build process. How do I do that? > Tcl manpages need to be installed within section 3tcl or 3tk, not 3. OK, I'll c

How to migrate to testing

Hi everyone, I recvently adopted a package (sextractor) which was uploaded to unstable 11 days ago. The previous version is really old (~ 6 years) and had a few bugs. The problem is now that the new version depends on some packages that are still not available everywhere (libatlas-base-dev), and

Re: How to migrate to testing

Jakub Wilk writes: > * Arno Töll , 2012-01-24, 11:48: >>> The problem is now that the new version depends on some packages that are >>> still not available everywhere (libatlas-base-dev), > Like where? (Presumably you meant s/depend/build-depends/.) You are right here. However, the binary would

Re: How to migrate to testing

Jakub Wilk writes: > * Olе Streicher , 2012-01-24, 12:52: >>>>> The problem is now that the new version depends on some packages that are >>>>> still not available everywhere (libatlas-base-dev), >>>Like where? (Presumably you meant s/depend/build-depe

Re: How to migrate to testing

Jakub Wilk writes: > * Olе Streicher , 2012-01-24, 13:04: >>>>>>> The problem is now that the new version depends on some packages that >>>>>>> are still not available everywhere (libatlas-base-dev), >>>>>Like where? (Presumably you mean

Re: How to migrate to testing

Joachim Wiedorn writes: > Jakub Wilk wrote on 2012-01-24 18:14: >> Does the test suite involve heavy floating-point computations? Two of >> our mips buildds, corelli and lucatelli, doesn't have FPU, so it >> wouldn't be surprising if they couldn't run such a testsuite in a > I have seen in som

Renaming file names because of conflicts

Hi, one of my packages has conflicts with file names in /usr/bin, and I am convinced to change this. The question is now, where is the right place to do this? Shall I do something like overwrite_dh_movefiles: dh_movefiles mv debian/wcstools/bin/imcat debian/wcstools/bin/imcatalog

Packaging source from a git repository

Hi, I need create a package from a git repository (specifically libraries/sla from ). What are the best options to do this? Best Ole -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Co

Re: Providing a non-free alternative to a free package

Gergely Nagy writes: > If it is obfuscated, then it is most probably not the preferred form of > modification (and not the real source, but something derived from that), > thus, them being GPL'd is invalid, and it's not even fit for non-free, > as far as I see. This is something I have to discuss

Re: Providing a non-free alternative to a free package

Gergely Nagy writes: > debian-de...@liska.ath.cx (Olе Streicher) writes: >> For example "saods9" would use slalib as a shared library, and I want to >> git the user a choide to run it either with the free, or with the >> non-free version. > Are the two librarie

Re: Providing a non-free alternative to a free package

Adam Borowski writes: > Is slalib the contents of libraries/sla/ in the repository you linked > to? Yes. > If so, it appears the current upstream is not the sole copyright > holder, and there are many other contributors dating from 2004 for > sla, and 1989 for the project as a whole (counting on

Mentors.debian.net incoming queue

Dear mentors, I wonder how the incoming queue of mentors.debian.net is processed? Yesterday, I tried to re-upload my package (tk-html3) after removing the old package, and it did not arrive in the package list yet; I also did not get a mail response. The package list, however, contains packages th

l18n?

Dear mentors, I am currently working on a Tcl/Tk package (saods9; ) which has a "msg" subdirectory containing translations into a handful languages: $ ls -l msgs/ insgesamt 308 -rw-rw-r-- 1 ole no 39129 2012-04-11 14:01 da.msg -rw-rw-r-- 1 ole no 38259 2012-04-11 14

Re: l18n?

Thibaut Paumard writes: > At most, I would split the package in an arch-dependent and an > arch-independent package, and that's assuming ds9 has even more arch > indep data than just those messages (say, if the data reaches ~2MB). In my case, the architecture independent data (in /usr/share) are

Re: l18n?

Thibaut Paumard writes: > So you have : > > - 7MB documentation; > - 3MB other ach-indep data; > - some arch-dep data (the amount is not much relevant :-) ) > > Is the doc necessary for reliable use of the package, or is is just that > you get an error message when clicking Help->User Manual? In

Changing SONAME in library version

Dear mentors, I am the maintainer of the package "cpl". Upstream just released a new version 6.0 and changed the SONAME for the built libraries from 12 to 20. So, the source now builds a package "libcplcore20" instead of "libcplcore12". There are a few dependencies of other packages from libcplcor

Re: Changing SONAME in library version

Tobias Frost writes: > For soname changes you probably wanted to set up a transition. > http://wiki.debian.org/OngoingTransitions > (Usually that should be done before the upload to unstable) The > transistion page helps a lot to keep track of the transistion, so you > should ask the release team

(un)patching patched files

Dear Mentors, For a package [1], I have to patch one file (Makefile.am) twice: once from debian/patches, and the other times from debian/rules. The patch in debian/patches is needed to bring allow the use of a standard automake (upstream uses a patched version), while the patch done from debian/ru

Re: (un)patching patched files

gregor herrmann writes: > Maybe try to move the second sed call from _clean to _autoreconf > directly after the dh_autoreconf invocation? I've tried this -- this triggers a re-creation of Makefile.in with the original names, which are then errornously used to build the package. Cheers Ole --

Re: (un)patching patched files

Gergely Nagy writes: > The patch in debian/patches will be large, possibly complicated and > whatnot, but you can explain how it is created in debian/README.source, > and live happily ever after. > > There are cases where a bit of ugliness is acceptable. This is one such > case. I still do not se

Re: (un)patching patched files

Hi Thibaut, Thibaut Paumard writes: > If you use a patch system, you should use it to do the patching OK, so I created a small shell script what creates/updates a file in debian/patches. However, now I have another problem: when I run debuild debuild clean I get an error since "debuild clean

Re: (un)patching patched files

Thibaut Paumard writes: > Can you not override clean to be a no-op or at least not trigger > autoreconf if the patches have not been applied? Overriding with no-op doesn't help since then my directory is still cluttered with all the trash from the build. To me, this problem sounds like a bug in

Re: (un)patching patched files

Thibaut Paumard writes: > Have you tried debuild -tc? It ought to call debian/rules clean before > unapplying the patches. IMHO, it should be the default. I agree. Since debuild [...] debuild clean is recommended in the docs [1], I would think it is a bug. Cheers Ole [1] http://www.debian.o

Re: Changing SONAME in library version

Dear mentors, could someone give me a hint on how to proceed here? debian-de...@liska.ath.cx (Olе Streicher) writes: > Tobias Frost writes: >> For soname changes you probably wanted to set up a transition. >> http://wiki.debian.org/OngoingTransitions >> (Usually that shou

Re: Changing SONAME in library version

Hi Thibaut, Thibaut Paumard writes: > Le 14/05/12 11:15, Olе Streicher a écrit : >> could someone give me a hint on how to proceed here? > The release team will answer your [request] soon and let you know > whether it's OK to transition your packages. In the meantime you co

Re: Changing SONAME in library version

Hi Thibaut, Thibaut Paumard writes: > Le 14/05/12 15:06, Olе Streicher a écrit : >> Some of the "out-of-date" excuses, however, result from the SONAME >> change (libcplcore12 --> libcplcore20), and I don't know hoe to handle >> them. > As part of the