Bug#952524: ITP: golang-github-op-go-logging -- Golang logging library
Package: wnpp Severity: wishlist Owner: Anthony Fok * Package name: golang-github-op-go-logging Version : 1+git20160315.970db52-1 Upstream Author : Örjan Persson * URL : https://github.com/op/go-logging * License : BSD-3-clause Programming Lang: Go Description : Golang logging library Package logging implements a logging infrastructure for Go. Its output format is customizable and supports different logging backends like syslog, file and memory. Multiple backends can be utilized with different log levels per backend and logger. Reason for packaging: Required by Go applications such as bitbucket.org/modima/dbsync2
Re: Y2038 - best way forward in Debian?
Arnd Bergmann wrote: >is clearly needed anyway. Once there is a working armhf version with >full time64 user space, there can be a separate discussion about what >to do with the i386 port (phase out i386 before y2038, migrate all of >i386 to time64 quickly, have two separate i386 ports, or something I’d greatly appreciate that. I don’t own a̲n̲y̲ 64-bit machines (of any architecture)¹ and would like to proceed using Debian on some, and, perhaps even now already, be able to calculate things less than two decades in the future. If there’s need for manpower to do the 64-bit switch for i386 count me in, I already did part of the work on MirBSD and on Debian/x32 already anyway. Thanks in advance, //mirabilos ① I occasionally work on a Thinkpad X61, which belongs to my employer though, not me, as does the x32 desktop and the virtualisation hosts at $dayjob -- den AGP stecker anfeilen, damit er in den slot aufm 440BX board passt… oder netzteile, an die man auch den monitor angeschlossen hat und die dann für ein elektrisch aufgeladenes gehäuse gesorgt haben […] für lacher gut auf jeder LAN party │ damals, als der pizzateig noch auf dem monior "gegangen" ist
Bug#952542: ITP: libarray-base-perl -- array index offseting
Package: wnpp Severity: wishlist Owner: Hideki Yamane X-Debbugs-Cc: debian-devel@lists.debian.org * Package name: libarray-base-perl Version : 0.0.6 Upstream Author : Andrew Main (Zefram) * URL : https://metacpan.org/release/Array-Base * License : Artistic or GPL-1+ Programming Lang: C, Perl Description : array index offseting Perl5.30 has an incompatible change "Assigning non-zero to $[ is fatal" but we can use this module for it. Array::Base implements automatic offsetting of array indices. In normal Perl, the first element of an array has index 0, the second element has index 1, and so on. This module allows array indexes to start at some other value. Most commonly it is used to give the first element of an array the index 1 (and the second 2, and so on), to imitate the indexing behaviour of FORTRAN and many other languages. It is usually considered poor style to do this. . The array index offset is controlled at compile time, in a lexically-scoped manner. Each block of code, therefore, is subject to a fixed offset. It is expected that the affected code is written with knowledge of what that offset is. -- Regards, Hideki Yamane henrich @ debian.org/iijmio-mail.jp
bootstrap.min.js in pydoctor
For -devel, context is that Anthony Fok just uploaded a new upstream version of pydoctor (a tool for extracting API docs for python modules) in order to fix a couple of upstream bugs. Anthony, thank you very much for your work to help fix one of our (mutual) indirect dependencies. Unfortunately the new pydoctor has some DFSG issues (#952546, CC'd). I am hoping that -devel can advise what the conventional approach is to the package containing a sourceless copy of bootstrap.min.js. I'm guessing that the answer is to strip the sourceless file from the package, and have the binary package contain a symlink into the file tree of some other package which contains an appropriate bootstrap file ? But is this right, and if so which package ? I vaguely remembered this having been discussed before but I couldn't find the conclusions written down anywhere. I looked in quite a few places for answers to this: I searched the lintian tags for missing source, but they all seemed quite generic. I tried to search -devel archives for "bootstrap" (too many hits) and "bootstrap.min.js" (nothing relevant). I tried various wiki searches too. (The d/copyright problem with epydoc should be easy if tedious to fix; I don't understand why it wants epydoc which I thought was obsolete but this is far from my field of expertise.) Regards, Ian.
Re: bootstrap.min.js in pydoctor
Quoting Ian Jackson (2020-02-25 18:40:47) > For -devel, context is that Anthony Fok just uploaded a new upstream > version of pydoctor (a tool for extracting API docs for python > modules) in order to fix a couple of upstream bugs. Anthony, thank > you very much for your work to help fix one of our (mutual) indirect > dependencies. > > Unfortunately the new pydoctor has some DFSG issues (#952546, CC'd). > > I am hoping that -devel can advise what the conventional approach is > to the package containing a sourceless copy of bootstrap.min.js. > > I'm guessing that the answer is to strip the sourceless file from the > package, and have the binary package contain a symlink into the file > tree of some other package which contains an appropriate bootstrap > file ? But is this right, and if so which package ? > > I vaguely remembered this having been discussed before but I couldn't > find the conclusions written down anywhere. I looked in quite a few > places for answers to this: I searched the lintian tags for missing > source, but they all seemed quite generic. I tried to search -devel > archives for "bootstrap" (too many hits) and "bootstrap.min.js" > (nothing relevant). I tried various wiki searches too. If you need Bootstrap 3.x, then add symlink to path /usr/share/javascript/bootstrap/js/bootstrap.min.js and depend on package libjs-bootstrap. If instead you need Bootstrap 4.x, then you should do something similar but for some path below /usr/share/javascript/bootstrap4 and package libjs-bootstrap4 (I am vague here because that package apparently use a symlink internally requiring actually installing the package to know for certain which exact path it is - no, you should *not* link below /usr/share/nodejs as that path is not reliable). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Re: bootstrap.min.js in pydoctor
On Tue, Feb 25, 2020 at 05:40:47PM +, Ian Jackson wrote: > (The d/copyright problem with epydoc should be easy if tedious to fix; > I don't understand why it wants epydoc which I thought was obsolete > but this is far from my field of expertise.) epydoc has been unmaintained for a long time, but the API documentation of various projects (notably Twisted) still relies on its docstring format for automatically-generated HTML documentation in a way that would be extremely tedious to replace with something else. As a result, the approach that the Twisted developers ended up taking for pydoctor was to take a copy of the bits of epydoc that they needed and port those bits to Python 3 themselves. (This is second-hand; I'm not on the Twisted team, but I contribute a fair bit there and generally keep an eye on what they're doing since we rely on Twisted at work.) -- Colin Watson [cjwat...@debian.org]
Re: bootstrap.min.js in pydoctor
Control: tags -1 + pending On Tue, Feb 25, 2020 at 12:06 PM Colin Watson wrote: > > On Tue, Feb 25, 2020 at 05:40:47PM +, Ian Jackson wrote: > > (The d/copyright problem with epydoc should be easy if tedious to fix; > > I don't understand why it wants epydoc which I thought was obsolete > > but this is far from my field of expertise.) > > epydoc has been unmaintained for a long time, but the API documentation > of various projects (notably Twisted) still relies on its docstring > format for automatically-generated HTML documentation in a way that > would be extremely tedious to replace with something else. As a result, > the approach that the Twisted developers ended up taking for pydoctor > was to take a copy of the bits of epydoc that they needed and port those > bits to Python 3 themselves. > > (This is second-hand; I'm not on the Twisted team, but I contribute a > fair bit there and generally keep an eye on what they're doing since we > rely on Twisted at work.) Thank you Sean for the heads-up, and thank you Ian, Jonas and Colin for your valuable and helpful comments. A fix to this bug is almost ready: I have expanded d/copyright to include the missing epydoc and bootstrap.min.css copyright info, and added debian/missing-sources/bootstrap.css (vanilla Bootstrap v3.3.4, equivalent to the embedded minified version, from Bootstrap CDN). ... though I discovered I foolishly uploaded an essentially empty pydoctor binary package, and I may end up renaming it python3-pydoctor, similar to how it was named python-pydoctor for the Python2 version. That's most likely why Lintian did not pick up on the "bootstrap.min.css" missing source issue. Jonas, thanks for letting me know about linking to bootstrap.min.css in libjs-bootstrap; I'll do that. Cheers, Anthony
Re: bootstrap.min.js in pydoctor
Quoting Anthony Fok (2020-02-25 22:35:03) > A fix to this bug is almost ready: I have expanded d/copyright to > include the missing epydoc and bootstrap.min.css copyright info, and > added debian/missing-sources/bootstrap.css (vanilla Bootstrap v3.3.4, > equivalent to the embedded minified version, from Bootstrap CDN). If the package ships copy of bootstrap.min.css then I suggest to also strip that and symlink to the css in the libjs-bootstrap package. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
