RFS: tk-table

iate a review without an upload since I am not familar with tcl/tk and therefore I am unsure about whether the package fits into the Debian tcl/tk subsystem. Best regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Tr

RFS: tk-table

be glad if someone uploaded this package for me. I would also very appreciate a review without an upload since I am not familar with tcl/tk and therefore I am unsure about whether the package fits into the Debian tcl/tk subsystem. Best regards, Ole Streicher -- To UNSUBSCRIBE, email to

RFS: tcl-signal

ackage for me. I am also still seeking a sponsor for "tk-table", http://mentors.debian.net/package/tk-table. Kind regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.

Re: [Pkg-tcltk-devel] RFS: tcl-signal

Hi Sergei, On 23.01.2012 10:47, Sergei Golovan wrote: [tcl-signal] > 1) It's a signal extension for Tcl, not for Tk (the description is incorrect). > 2) Manpage should be names signal.3tcl, not signal.3tk > 3) add Suggests: ${wish:Depends} to the control file. > 4) Don't use ${tcl:Depends}. [tk

RFS: xpa -- Seamless communication between Unix programs

is needed in order to bring the astronomical package "saods9" back into Debian (ITP: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655648). I would be glad about a review and if someone uploaded this package for me. Kind regards, Ole Streicher -- To UNSUBSCRIBE, email to

Re: [Pkg-tcltk-devel] RFS: xpa -- Seamless communication between Unix programs

On 30.01.2012 15:52, Sergei Golovan wrote: > dpkg-source: error: diff > `xpa-2.1.13/debian/patches/fix_manpages.patch' patches file > xpa-2.1.13/man/man1/xpaset.1 twice This is true; however I didn't get this error. I corrected it and re-uploaded the file. Could you try to build it again? Thank

RFS: tk-html3 -- Render HTML and CSS content with tk

using this command: dget -x http://mentors.debian.net/debian/pool/main/t/tk-html3/tk-html3_3.0~fossil20110109-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of &q

Bug#661504: RFS: tk-html3/3.0~fossil20110109-1 [ITP ] -- Render HTML and CSS content with tk

bug system. Since then, I added some minor changes. The tk-html3 package is needed in order to re-debianize the astronomy program "saods9" <http://bugs.debian.org/655648>. I would be glad if someone uploaded this package for me. I am also interested in a review of the package. Be

Repost: RFS: tk-html3/3.0~fossil20110109-1 [ITP ] -- Render HTML and CSS content with tk

ly independent Web engine suitable f.e. for smaller computers, and for the seemless inclusion into Tcl/Tk. My personal interest in getting tk-html3 into Debian is that I need this widget for the astronomical "saods9" package. A would appreciate for a review and/or upload of the package. B

Repost: RFS: tk-html3/3.0~fossil20110109-1 [ITP ] -- Render HTML and CSS content with tk

ly unsure whether having the download from a fossil VCS is done in the right, "Debianic" way. Best regards Ole On 27.02.2012 19:19, Ole Streicher wrote: > Package: sponsorship-requests > Severity: wishlist > X-Debbugs-Cc: pkg-tcltk-de...@lists.alioth.debian.org > > Dear

Re: Bug#661504: [Pkg-tcltk-devel] Repost: RFS: tk-html3/3.0~fossil20110109-1 [ITP ] -- Render HTML and CSS content with tk

, 2012 at 1:13 PM, Sergei Golovan wrote: >> On Wed, Mar 21, 2012 at 1:06 PM, Ole Streicher >> wrote: >>> Dear mentors, >>> >>> I just want to repost this sponsorship request so that it does not get >>> forgotten :-) > > The package is fine, t

Install a patched BLT version?

Dear mentors and specialists, I am currently working on a Tcl/Tk package (saods9; ) which builds on top of a patched/unofficial "3.0" release of BLT. Using the 2.4z version distributed with Debian produces mysterious segmentation faults; also some features are missin

Re: Install a patched BLT version?

Hi Paul, Am 14.04.2012 11:09, schrieb Paul Wise: > I would suggest working with BLT upstream to get version 3.0 released > so that you can depend on it. Please don't do embedded code copies or > static linking (which is almost as bad). > http://wiki.debian.org/EmbeddedCodeCopies I know this: for

Request for review: saods9, libstarlink-ast

Dear Mentors, after a few months, I finished the (re-)packaging of the "saods9" package: * Package name: saods9 Version : 6.2+dfsg-1 Upstream Author : William Joye * URL : http://hea-www.harvard.edu/RD/ds9/ * License : GPLv2+ Section : science

RFR: ftools-fv and fitsTcl

Hi, I almost finished my work on the "ftools-fv" package (ITP: ): This is a re-packaging of the "fv" package removed in 2009 (PTS: ; Removal bug: ). Since the name is too short, the package will

Package separation/naming conventions

Dear list, I am currently packaging the "wcslib" package (Bug #641624) as my first Debian package, and I am wondering about the naming conventions. The package contains two libraries, some tools and an common API documentation for both libraries. I would now make the following binary packages: -

Re: Package separation/naming conventions

Jakub Wilk writes: > * Ole Streicher , 2011-09-21, 16:42: >>- libwcs4 and libwcs4-dev >>- libpgsbox4 and libpgsbox4-dev > First of all, don't version your -dev package(s), unless you want to > keep multiple versions of it in the archive at the same people. (You > pr

Re: Package separation/naming conventions

Hi Ansgar, Ansgar Burchardt writes: > Ole Streicher writes: >> Is the division into main and contrib done automatically based on the >> dependencies to non-free packages? > No, it is done by hand using the Section field in debian/control. OK, so I have to add the flags the

Re: Package separation/naming conventions

Jakub Wilk writes: > A -dev package should have a strict versioned dependency on all the shared > libraries it provides .so symlink for. This is clear, but means that the wcslib-dev would depend on libpgsbox4, and therefore on pgplot5, which is not nice. >> libpgsbox.a would contain references t

Shared libs dependencies

Dear list, I am a bit confused about how I have to declare the dependencies when creating a shared library package. I've read the Debian Policy Manual; however I do not now understand what to do. First of all: what is the difference between the "Depends" field in the control file and the "shlibs"

Re: Package separation/naming conventions

Gergely Nagy writes: > * Either don't build the part which (build-)depends on non-free, and > don't ship it at all, then both the source and the resulting binaries > can be in main. I will probably go with this option. If one really needs the libpgsbox, I would create a completely new source

Re: Shared libs dependencies

Gergely Nagy writes: > Or, to put it in other words: Depends lists the packages your library > depends on, shlibs lists the libs that packages built against your lib > should depend on. So, this means that in the usual cases (like my one) this file looks like libwcs 4 libwcs4 (>= 4.8.1-1) right

Re: Shared libs dependencies

Gergely Nagy writes: > Ole Streicher writes: >> libwcs 4 libwcs4 (>= 4.8.1-1) > debian/libwcs4.shlibs should be the line you wrote above. It would be good if the policy would use the same naming conventions as the debhelper. Currently, the Debian Policy states (8.6.4) | if yo

Re: Package separation/naming conventions

Jakub Wilk writes: > * Ole Streicher , 2011-09-23, 13:58: >> My question is not the naming of the binary packages. The original library >> is called "wcslib", and to maximize confusion, there exists somewhere else >> another (not compatible, less used) library for t

Re: Package separation/naming conventions

Charles Plessy writes: > Le Fri, Sep 23, 2011 at 04:13:42PM +0200, Ole Streicher a écrit : >> the "wcslib" exists under this name already for some years, and is >> always referenced under this name. Changing the name to libwcs would >> confuse people with the

E helper-templates-in-copyright

te. However, I think that I changed it according to the package's needs: 8< This work was packaged for Debian by: Ole Streicher on Wed, 14 Sep 2011 16:31:30 +0200 It was downloaded from http://www.atnf.csiro.au/

Re: E helper-templates-in-copyright

Arno Töll writes: > Moreover you eventually want to use DEP-5 instead, please see [1]. DEP-5 > is required for many sponsored maintainers from their sponsors, but no > global Debian requirement. OK, I am changing the copyright to this file. This looks better to me than the "pseudo-freetext" that

RFS: wcslib

visit the following URL: http://mentors.debian.net/package/wcslib Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/w/wcslib/wcslib_4.8.1-1.dsc I would be glad if someone uploaded this package for me. Kind reg

Dependency from a specific binary version

Hi, in a library that I want to package for Debian, there is a runtime check that another library has the same version number as at compile time: ---8<- float cfitsio_version; const float cfitsio_version_diff = fits_get_version(&cfit

RFS: ESO Common Pipeline Library

net/package/cpl Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cpl/cpl_5.3.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Ole Streicher -- To UNSUBSCRIBE, email to debi

RFS: EsoRex - - Execution Tool for European Southern Observatory pipelines

is command: dget -x http://mentors.debian.net/debian/pool/main/e/esorex/esorex_3.9.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trou

Re: RFS: ESO Common Pipeline Library

Julian Taylor writes: > On 10/12/2011 06:57 PM, Ole Streicher wrote: >> I am looking for a sponsor for my package "cpl". > the package does not build in a clean unstable chroot: > configure:12738: error: cfitsio was not found on your system. Please check! > This

Re: RFS: ESO Common Pipeline Library

ool/main/c/cpl/cpl_5.3.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http:

Re: RFS: EsoRex - - Execution Tool for European Southern Observatory pipelines

e with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/e/esorex/esorex_3.9.0-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "

Re: RFS: ESO Common Pipeline Library

Am 13.10.2011 20:55, schrieb Julian Taylor: > On 10/13/2011 06:04 PM, Ole Streicher wrote: >> Am 12.10.2011 20:20, schrieb Julian Taylor: >>> Else the package looks nice, good work. >> >> I implemented all changes from you and Sylvestre and re-uploaded the >>

Confusing "ancient-autotools-helper-file" error

Dear list, I am trying to pack the "pywcs" package, (Python wrapper for wcslib; ITP ) which contains a convienence copy of the wcslib. As required, I ignore the convienence copy of wcslib and use the version packaged for Debian. The convien

Re: Confusing "ancient-autotools-helper-file" error

Jakub Wilk writes: > * Ole Streicher , 2011-10-17, 13:42: >>E: python-pywcs source: ancient-autotools-helper-file >>wcslib/config/config.guess 2003-10-03 >>E: python-pywcs source: ancient-autotools-helper-file >>wcslib/config/config.sub 2003-08-18 >> >>

Upstream changelog name change

Dear list, my upstream package has a file "CHANGELOG" which does not get installed by default. When I just include this file name into debian/docs, lintian complains about "wrong-name-for-upstream-changelog". Is there a simple way to rename this file? Or do I need to write a specific debian/rules

watch file syntax

Dear list (again :-)), thank you very much for helping so far -- I have now another problem: the upstream url is something like , but the URL just gives some errors, preventing the watch file from working

Re: Upstream changelog name change

Ansgar Burchardt writes: > Ole Streicher writes: >> my upstream package has a file "CHANGELOG" which does not get installed >> by default. When I just include this file name into debian/docs, lintian >> complains about "wrong-name-for-upstream-changelog"

Re: Upstream changelog name change

Guido van Steen writes: >> there? (I use debhelper -8.9.0ubuntu1). > Are you packaging for Debian of for Ubuntu? If I packaged for Debian I > would not use an Ubuntu version of debhelper... Both. On my desktop, I use Ubuntu, and when everything goes fine, I change to a larger computer running De

Python: Including Nosetest

Dear lists, I am working on a package (python-pywcs) that may include a "nosetest" which I want to run before installation. For this, I put the following line into debian/rules (for debhelper): override_dh_auto_test: nosetest However, when I try to build the package, I get the error ==

Re: Python: Including Nosetest

Am 18.10.2011 15:10, schrieb Yaroslav Halchenko: > well -- if you discover some other way -- please let me know. >From elsewhere , I got the hint to try python setup.py build_ext -i which builds the extension in-

RFS: python-pywcs

is command: dget -x http://mentors.debian.net/debian/pool/main/p/python-pywcs/python-pywcs_1.10-1.dsc I would be glad if someone uploaded this package for me. Best regards, Ole Streicher -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe&quo

Re: RFS: python-pywcs

Hi Sylvestre, Am 23.10.2011 21:20, schrieb Sylvestre Ledru: > I am willing to sponsor your package. However, I would like to know > first if you could update to move it into Debian Science. I could; however I tried to register a project for it (as well as projects for my other packages: wcslib, c

Re: RFS: python-pywcs

Am 25.10.2011 22:42, schrieb Sylvestre Ledru: > Le lundi 24 octobre 2011 à 16:23 +0200, Ole Streicher a écrit : > You have to join this project to get access to the VCS. Sorry, I didn't write that: I already applied for a membership. I still did not get an approval, but I am listed in

RFS: python-cpl

Dear mentors, I am looking for a sponsor for my package "python-cpl". * Package name: python-cpl Version : 0.3.5-1 Upstream Author : Ole Streicher * URL : http://www.aip.de/~oles/python-cpl/index.html * License : GPL-2 Section :

Re: RFS: python-pywcs

Dear Sylvestre, Am 03.11.2011 21:22, schrieb Sylvestre Ledru: > Yes, you are a member. I just checked and you are indeed listed as a member. > About the VCS issue, it is likely to be a configuration issue on your > side. Could you drop me a message when it is solved? >> I would feel a bit unluck

Re: RFS: python-cpl

Hi Igor, Igor Pashev writes: > I think the name "python-cpl" is not descriptive enough what would you propose? I guess, the usual naming way for a python wrapper around a package "foo" is "python-foo". Best regards Ole > 04.11.2011 00:07, Ole Streiche

Re: RFS: python-pywcs

Am 04.11.2011 09:58, schrieb Sylvestre Ledru: > The issue is on your side (ie it is not alioth's fault but yours). OK; I created a git repository for python-pywcs and committed everything for python-pywcs. Since I am not too experienced with git: could you please check this before I store the rem

RFR: python-astropy -- Core functionality for performing astrophysics with Python

Dear mentors, I am looking for review for my package "python-astropy". I still don't need a sponsor since the packaged version is just a beta version, with the final release expected soon. To speed up the process, I'd however like to start to sort out packaging problems already now. * Package nam

Bug#710248: RFS: fitsverify/4.16 [ITP] -- FITS File Format-Verification Tool

URL: http://mentors.debian.net/package/fitsverify Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/f/fitsverify/fitsverify_4.16-1.dsc The package is quite small, so a review should take not much of your time ;-) Best Regards Ole

Bug#710248: RFS: fitsverify/4.16 [ITP] -- FITS File Format-Verification Tool

Hi Thibaut, Am 29.05.2013 13:44, schrieb Thibaut Paumard: > Le 29/05/2013 12:44, Ole Streicher a écrit : >> I am looking for a sponsor for my package "fitsverify" > package looks good. I couldn't find upstream's license and copyright > statement though, where i

Re: Bug#710248: RFS: fitsverify/4.16 [ITP] -- FITS File Format-Verification Tool

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thibaut, Am 29.05.2013 14:38, schrieb Thibaut Paumard: > I don't think the FTP master will let the package in with just > this short notice (so short that I missed it despite looking for > it). Maybe they would be OK if you reproduced said e-mail i

Bug#719720: RFS: skycat/3.1.2+starlink1~b-1 [ITP]

Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: debian-scie...@lists.debian.org, package-sponsorship-reque...@lists.debian.org, pkg-tcltk-de...@lists.alioth.debian.org, debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "skycat" * Package na

Re: Bug#719720: RFS: skycat/3.1.2+starlink1~b-1 [ITP]

Hi Anton, Am 14.08.2013 20:16, schrieb Anton Gladky: > why is the tarball on mentors different from that one, which is on the > website? I did not use the tarball provided by ESO but the one provided by Starlink . Reasons are

Bug#723962: RFS: cpl-plugin-hawki/1.8.12-1 [ITP] -- ESO data reduction pipeline HAWK-I

Package: sponsorship-requests Severity: wishlist X-Debugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for a number of plugins (currently five) for the "cpl" library. Each plugin contains the software to process ("reduce" in the astronomer's slang) the data of one

Bug#723968: RFS: cpl-plugin-sinfo/2.3.3-1 [ITP] -- ESO data reduction pipeline SINFONI

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-mentors@lists.debian.org, debian -scie...@lists.debian.org Dear mentors, I am looking for a sponsor for a number of plugins (currently five) for the "cpl" library. Each plugin contains the software to process ("reduce" in the

Bug#723970: RFS: cpl-plugin-fors/4.9.23-1 [ITP] -- ESO data reduction pipeline FORS

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for a number of plugins (currently five) for the "cpl" library. Each plugin contains the software to process ("reduce" in the astronomer's slang) the data of one

Bug#723971: RFS: cpl-plugin-giraf/2.11.1-1 [ITP] -- ESO data reduction pipeline GIRAFFE

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for a number of plugins (currently five) for the "cpl" library. Each plugin contains the software to process ("reduce" in the astronomer's slang) the data of one

Bug#723972: RFS: cpl-plugin-amber/4.2.2-1 [ITP] -- ESO data reduction pipeline AMBER

Package: sponsorship-requests Severity: wishlist X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for a number of plugins (currently five) for the "cpl" library. Each plugin contains the software to process ("reduce" in the astronomer's slang) the data of one

Bug#743691: RFS: wcslib-contrib/4.20 [ITP] -- Draw and label curvilinear coordinate grids with pgplot

Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: debian-as...@lists.debian.org, debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "wcslib-contrib" * Package name: wcslib-contrib Version : 4.20-1 Upstream Author : Mark Calabretta

Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)

ugin-xshoo * Change maintainer and VCS location to debian-astro -- Ole Streicher Fri, 11 Apr 2014 16:58:53 +0200 I need a sponsor since there is a name change in the upstream package (xsh --> xshoo), and for consistency I want to have the same name in the Debian packages. Also, the package

Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thibaut, Am 13.04.2014 14:45, schrieb Thibaut Paumard: I mainly followed the rule of renaming a package. "Replaces" is correct wrt policy: 7.6 Overwriting files and replacing packages - Replaces Packages can declare in their control file that t

Bug#743691: RFS: wcslib-contrib/4.20 [ITP] -- Draw and label curvilinear coordinate grids with pgplot

X-Debbugs-Cc: debian-as...@lists.debian.org, debian-scie...@lists.debian.org > I am looking for a sponsor for my package "wcslib-contrib" > > * Package name: wcslib-contrib > Version : 4.20-1 Since upstream released the new version 4.22, I updated the package on mentors. So, the "d

Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thibaut, my mail program seemed to eat the citations. 2nd attempt: Am 13.04.2014 14:45, schrieb Thibaut Paumard: > Why does the package Conflict and Replace cpl-plugin-xsh? None of > the files are the same (so at least the Replace is wrong). I ma

Re: Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thibaut, Am 13.04.2014 17:24, schrieb Thibaut Paumard: The problem here is that B *is* actually A. All files that were originally in A are now in B. There is no conflict just because the package has them in version (and package) dependent subdire

Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 13.04.2014 17:24, Thibaut Paumard wrote: > - file f was is package A, now it is in package B. Either package A > is removed from the archive, or there is a new version of package A > without file f. (Normally, Breaks+Replaces). One correction here:

Bug#744280: RFS: cpl-plugin-xshoo/2.4.0+dfsg-1 (name change)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Thibaut, I removed now the Provides/Replaces from the -xshoo and -xshoo-calib packages, put Replaces/Breaks to -xshoo-doc and uploaded this to mentors. I think this is the best compromise I'll take care of removing the -xsh* packages from testing o

Bug#745609: RFS: eso-midas/13.09pl1.2-1 [ITP] -- European Southern Observatory Munich Image Data Analysis System

Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: debian-as...@lists.debian.org, debian-mentors@lists.debian.org, debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package "eso-midas" * Package name: eso-midas Version : 13.09pl1.2-1 Upst

Re: Bug#745609: RFS: eso-midas/13.09pl1.2-1 [ITP] -- European Southern Observatory Munich Image Data Analysis System

Hi Thorsten, thank you for the review of the licensing. I now removed all questionable files -- most important was IMO gui/GraphLib/libsrc/uimxR5/include/msg.h which was ASCL licensed (not dfsg-free). It is now replaced by a patch with its original one from netBSD. Best regards Ole On 24.04.201

Deterministic "ar" breaks build

Hi, since a while, the "ar" command is built with --enable-deterministic-archives, which basiacally resets (among others) the timestamp to null. This has the unfortune disadvantage, that Makefiles that use this timestamp do not work correctly anymore. For example, my wcslib package has $(WCSLIB)(

Weird unmet build dependencies on buildds

Hi, I am trying to get my package "dpuser" compiled. While this works nicely on my local pbuilder with up-to-date packages, it fails on the buildds: https://buildd.debian.org/status/package.php?p=dpuser f.e. for i386: ---8<- Dependency installabil

uscan for a single text file

Hi, I want to create a watch file for a package that contains a single text file (which itself has the version into it): --8 version=3 http://www.ngdc.noaa.gov/IAGA/vmod/igrf.html igrf(\d+)coeffs.txt \ debian debian/repackage.sh ---

Re: uscan for a single text file

Sergio Durigan Junior writes: >> What is wrong here? I thought that mk-orig.tar.gz should be called only >> when it is a tar archive? > > Yeah, uscan is the responsible for invoking mk-origtargz. That can be a > problem indeed for cases like yours. Hmm, the manpage of uscan says: | Please note

Re: uscan for a single text file

Sergio Durigan Junior writes: > On Saturday, July 16 2016, Ole Streicher wrote: > >> Sergio Durigan Junior writes: >>>> What is wrong here? I thought that mk-orig.tar.gz should be called only >>>> when it is a tar archive? >>> >>> Yeah, usc

Re: uscan for a single text file

Paul Wise writes: > On Fri, Jul 15, 2016 at 11:13 PM, Ole Streicher wrote: > >> I want to create a watch file for a package that contains a single text >> file (which itself has the version into it): > ... >> The "repackage.sh" script would then just create a

Re: uscan for a single text file

Sergio Durigan Junior writes: > On Sunday, July 17 2016, Ole Streicher wrote: >> If mk-origtargz doesn't repack it, why does it look into it? The symlink >> could be created without as well. > > It makes sure that there is a tarball compressed using the supported >

NFS_SUPER_MAGIC portability

Hi, I have the problem that in a package (casacore) there is basically the following code: -8< #include #include Bool Directory::isNFSMounted() const { struct statfs buf; if (statfs (itsFile.path().expandedName().chars()

Re: NFS_SUPER_MAGIC portability

Christian Seiler writes: > Therefore, it might be a good idea to know _why_ you want to check for > NFS here? What's the use case? Perhaps there's a better and more > portable way to check for that specific thing. That was the key question ;-) Scanning the code showed me that the function is act

Version comparison with "+repack"

Hi, my package "saods9" has currently a RC release in experimental that is named 7.5~rc+repack-1 Now, upstream released a second RC which I want to upload as well: 7.5~rc2+repack-1 However, it turns out that this release is actually *smaller* than the first RC release? I originally thought tha

Re: Version comparison with "+repack"

Santiago Vila writes: > On Fri, Oct 07, 2016 at 11:00:17AM +0200, Ole Streicher wrote: >> dpkg --compare-versions 7.5~rc+repack lt 7.5~rc2+repack && echo lt || echo >> ge >> ge >> >> What is the best way to fix this? > > The best way I don&#

Re: Version comparison with "+repack"

Mattia Rizzolo writes: > On Fri, Oct 07, 2016 at 12:26:09PM +0200, Ole Streicher wrote: >> Santiago Vila writes: >> > On Fri, Oct 07, 2016 at 11:00:17AM +0200, Ole Streicher wrote: >> >> dpkg --compare-versions 7.5~rc+repack lt 7.5~rc2+repack &&

Re: Version comparison with "+repack"

Adam Borowski writes: > On Fri, Oct 07, 2016 at 11:23:45AM +, Mattia Rizzolo wrote: >> agreed. What about >> 7.5~rc.2+repack >> ? >> >> The full stop is ugly at my eyes, but does the work and there are worse >> things in the world. > > What about rc-2+repack? A matter of taste but I'd c

dcut cancel|rm command

Hi, I am (again) stuck with using the dcut tool to remove an upload. I have two packages which are uploaded, but still not accepted (in the incoming queue), which I want to cancel: wsclean and aoflagger. I thought the way to do would be (with dcut-ng): dcut cancel -f wsclean_1.12-3_source.chang

Re: dcut cancel|rm command

Hi, On 18.10.2016 18:17, Gianfranco Costamagna wrote: >> dcut cancel -f wsclean_1.12-3_source.changes >> >> but this returns a mail "No upload found: >> wsclean_1.12-3_source.changes". > > the package has already been accepted? It isn't; at least I didn't get the acceptance mail and it is not i

Data updates in debian packages

Hi, We have the problem (I am not sure whether I posted about this already), that the "casacore" package needs additional "casacore-data-XXX" packages, providing the basic data to work with casacore. Some of the data are almost immutable, others (for example leap seconds) are changing every year o

Re: Data updates in debian packages

Hi Paul, On 29.10.2016 03:37, Paul Wise wrote: > On Fri, Oct 28, 2016 at 6:38 PM, Ole Streicher wrote: >> We have the problem (I am not sure whether I posted about this already), >> that the "casacore" package needs additional "casacore-data-XXX" >> packag

Re: Data updates in debian packages

Ben Finney writes: > Ole Streicher writes: >> How sure can one be that they will be installed in-time? > > This confuses me too. If the file is installed, you have the > leap-seconds data for the installed version of ‘tzdata’. > > So I think I don't understand. What

Re: Data updates in debian packages

On 30.10.2016 04:42, Paul Wise wrote: > On Sun, Oct 30, 2016 at 4:36 AM, Ole Streicher wrote: > >> The canonical source for leap seconds is the IERS. Our current plan was >> to take the leap second list from there and build our package from this >> (as it is done in th

Re: Data updates in debian packages

On 30.10.2016 04:38, Paul Wise wrote: > On Sat, Oct 29, 2016 at 8:45 PM, Ole Streicher wrote: >> The update script itself could even be distributed with the casacore >> package itself. And for simplicity I would make >> casacore-data-autoupdater a binary package withi

Re: Data updates in debian packages

Russ Allbery writes: > The required timeliness depends a lot on what you're using leap seconds > for, and in particular if you need to know about them far in advance, or > if it's only necessary to have an updated table before the leap second > itself arrives. We need it to put correct time on as

Re: Data updates in debian packages

Christian Seiler writes: > On 10/31/2016 09:07 AM, Ole Streicher wrote: [leap seconds] >> We need it to put correct time on astronomical registrations, so it is >> most important to have them once they are effective. Having them in >> advance would be an additional plus,

Re: Data updates in debian packages

Paul Wise writes: > On Sat, Oct 29, 2016 at 8:45 PM, Ole Streicher wrote: >> The package in question (casacore) wants them in a specific format "CASA >> table" (which is uniformly used within that package), and dependent >> packages access this in that specific f

Re: ITP's not showing up on debian-devel?

Andrey Rahmatullin writes: > On Mon, Nov 07, 2016 at 11:28:55PM -0800, Walter Landry wrote: >> Hi Everyone, >> >> I recently posted two ITP's >> >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843325 >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843570 >> >> The confirmation message s

Debian privacy policy

Hi, for a discussion with upstream (removal of a default "anonymously logging home" feature), I would like to have a reference that Debian prefers strong privacy (no default logging, even not anonymously) over usefullness for upstream. The only point I could find is the "Our priorities are our use

Re: Debian privacy policy

Sean Whitton writes: > On Wed, Nov 16, 2016 at 05:17:32PM +0100, Ole Streicher wrote: >> for a discussion with upstream (removal of a default "anonymously >> logging home" feature), I would like to have a reference that Debian >> prefers strong privacy (no defaul

Re: Debian privacy policy

Paul Wise writes: > On Thu, Nov 17, 2016 at 12:17 AM, Ole Streicher wrote: >> a reference that Debian prefers strong privacy > > AFAICT we don't have an official statement about this, but: > https://lists.debian.org/debian-policy/2008/02/msg00060.html [...] Is there a rea

Package not migrating

Hi, I have a package (casacore-data-tai-utc), that doesn't migrate to testing, even if it is marked as "valid candidate": excuses: * 12 days old (needed 10 days) * casacore-data-tai-utc/i386 unsatisfiable Depends: python3-casacore * Valid candidate The second item comes from the fact, that th

Non-understandable piuparts

Hi, I have a piuparts message that I don't understand: https://piuparts.debian.org/sid/fail/python-pyvo_0.4.1+dfsg-1.log it basically complains the python-requests could not be installed; however this package is available both in sid and testing (for more than 6 months without change), and manua

  1   2   3   >