Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
* Package name: coreapi
Version : 2.3.3
Upstream Author : Tom Christie
* URL : https://github.com/core-api/python-client
* License : BSD
Programming Lang: Python
Description :
On Tue, 09 Jan 2018 at 04:04:39 +0100, Andreas Henriksson wrote:
> Using the pidof implementation provided by procps (upstream) would
> mean we atleast use the same implementation as other distros, but
> wouldn't gain us much else and could even give us new problems.
The other gain would be that o
On Tue, 2018-01-09 at 05:03 +, Wookey wrote:
> And the reason why you'd use it for something like this is that it
> lets you upstream patches (which change dependencies) in a reasonably
> clean way.
And is the reason this is preferable to `dpkg-vendor` based stuff
because `dpkg-vendor` cannot
Package: wnpp
Severity: wishlist
Owner: Félix Sipma
* Package name: python-twodict
Version : 1.2-1
Upstream Author : Sotiris Papadopoulos
* URL : https://github.com/MrS0m30n3/twodict
* License : Public domain
Programming Lang: Python
Description : Simp
Hi!
[ Thanks, I also wanted to chime in and mention this, because it seems
other people might not be clear on the history and motivations for
build-profiles! ]
On Mon, 2018-01-08 at 18:37:11 +, Wookey wrote:
> On 2018-01-03 13:30 +, Simon McVittie wrote:
> > On Wed, 03 Jan 2018 at 15:
Hi all,
(please Cc)
it seems that msgfmt has problems when run in a C locale, because what
is produced is not utf8 parsable.
For calibre I need proper utf8 stuff, but I don't see a way to enforce
an utf8 locale during the build process. I can depend on locales etc,
but en_US.utf8 or C.utf8 seems
On Tue, Jan 09, 2018 at 10:31:53PM +0900, Norbert Preining wrote:
> Hi all,
>
> (please Cc)
>
> it seems that msgfmt has problems when run in a C locale, because what
> is produced is not utf8 parsable.
>
> For calibre I need proper utf8 stuff, but I don't see a way to enforce
> an utf8 locale d
Package: wnpp
Severity: wishlist
Owner: Filip Pytloun
* Package name: salt-pepper
Version : 0.5.2
Upstream Author : Seth House
* URL : https://github.com/saltstack/pepper
* License : Apache-2.0
Programming Lang: Python
Description : A library and stand
Hello,
On Thu, 04 Jan 2018, Adam Borowski wrote:
> On Thu, Jan 04, 2018 at 01:01:15PM +0100, Raphael Hertzog wrote:
> > I agree. I have plans to create email addresses like
> > team+@tracker.debian.org that could be used for this purpose.
> > The package tracker would automatically add those packa
Hi Norbert et al.,
> it seems that msgfmt has problems when run in a C locale
[…]
> [force a] utf8 locale during the build process
I'm not sure whether the following applies in the case of msgfmt;
this is more of a general remark.
One thing I picked up via the Reproducible Builds project (has it
Quoting Wookey (2018-01-09 06:03:26)
> On 2018-01-08 20:36 -0500, Michael Stone wrote:
> > How, then, would you tell by looking at the package name+version which kind
> > of package you have?
> The package header says what profiles it was built with. The package
> name+version doesn't change - tha
On Tue, Jan 09, 2018 at 11:52:47PM +0900, Norbert Preining wrote:
> > No, C.UTF-8 is guaranteed to be available in Debian.
>
> Thanks, good to know - I couldn't find it/set it up, but this is
> probably my very old chroot.
It's avaiable only since libc-bin 2.13-1 (so since wheezy I think).
--
WB
> No, C.UTF-8 is guaranteed to be available in Debian.
Thanks, good to know - I couldn't find it/set it up, but this is
probably my very old chroot.
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian De
Hi Chris,
> In other words, simply forcing the *build* to do the right thing
> can mean we are hiding issues that should be fixed elsewhere
Indeed, but in this case it was simply a .mo file based on a latin1
encoding instead of UTF8, while the main program was loading/running
the files/translatio
> It's avaiable only since libc-bin 2.13-1 (so since wheezy I think).
Ah, that explains why not in my case. Thanks!
Norbert
--
PREINING Norbert http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13 fp: F7D
On 2018-01-09 15:07 +0100, Johannes Schauer wrote:
> Quoting Wookey (2018-01-09 06:03:26)
> > On 2018-01-08 20:36 -0500, Michael Stone wrote:
> > > How, then, would you tell by looking at the package name+version which
> > > kind
> > > of package you have?
> > The package header says what profile
On Tue, 09 Jan 2018 at 15:40:04 +, Wookey wrote:
> On 2018-01-09 15:07 +0100, Johannes Schauer wrote:
> > Thus, we keep packages built with a different build profile but the same
> > name/version/arcitecture bit-by-bit identical to each other.
>
> However we do have 'nodoc', which can't possib
On Tue, Jan 9, 2018 at 9:07 AM, Johannes Schauer wrote:
> So we
> could talk about whether we should allow more build profiles that change
> binary
> package contents but so far I don't see the use case for them and thus the
> discussion would be a bit academic.
Ok, let me try to provide a more
Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez
* Package name: golang-github-14rcole-gopopulate
Version : 0.0~git20171207.91c73a7-1
Upstream Author : Ryan Cole
* URL : https://github.com/14rcole/gopopulate
* License : MIT License
Programming Lan
Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez
* Package name: golang-github-ostreedev-ostree-go
Version : 0.0~git20171027.cb6250d-1
Upstream Author : OSTree Project
* URL : https://github.com/ostreedev/ostree-go
* License : ISC
Programming Lang
Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez
* Package name: go-flags
Version : 1.3.0+git20170926.f88afde-1
Upstream Author : Jesse van den Kieboom
* URL : https://github.com/jessevdk/go-flags
* License : BSD-3-clause
Programming Lang: Go
De
Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez
* Package name: fakemachine
Version : 0.0~git20171207.6af110d-1
Upstream Author : Sjoerd Simons
* URL : https://github.com/go-debos/fakemachine
* License : Apache-2.0
Programming Lang: Go
Descrip
Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez
* Package name: debos
Version : 1.0.0+git20171222.87b0d5e-1
Upstream Author :
* URL : https://github.com/go-debos/debos
* License : Apache-2.0
Programming Lang: Go
Description : Debian OS buil
On Tue, Jan 09, 2018 at 11:35:30AM -0500, Jeremy Bicha wrote:
At times, Ubuntu needs to avoid certain build-dependencies because
they would add an unwanted "universe" binary dependency to a "main"
package. In some cases, that is the *only* change Ubuntu makes to the
package. I believe it benefits
This is already packaged, as golang-go-flags-dev or something like that.
On 10/01/2018 7:08 AM, "Hector Oron" wrote:
Package: wnpp
Severity: wishlist
Owner: Héctor Orón Martínez
* Package name: go-flags
Version : 1.3.0+git20170926.f88afde-1
Upstream Author : Jesse van den Kiebo
> "Russ" == Russ Allbery writes:
Russ, I'm somewhat confused by the above.
It sounds like Debian as a whole is fairly OK with dependencies on
libsystemd0 etc.
We want systems to run without systemd as pid 1 but we don't mind
systemd libraries being installed.
I thought the point here was to
Sam Hartman writes:
> Russ, I'm somewhat confused by the above.
> It sounds like Debian as a whole is fairly OK with dependencies on
> libsystemd0 etc.
> We want systems to run without systemd as pid 1 but we don't mind
> systemd libraries being installed.
> I thought the point here was to provi
On Tue, Jan 09, 2018 at 01:22:33PM -0500, Michael Stone wrote:
> On Tue, Jan 09, 2018 at 11:35:30AM -0500, Jeremy Bicha wrote:
> > At times, Ubuntu needs to avoid certain build-dependencies because
> > they would add an unwanted "universe" binary dependency to a "main"
> > package. In some cases, t
On Tue, Jan 09, 2018 at 01:23:32PM +0100, Guillem Jover wrote:
>...
> Given the background of build-profiles, I'm very much in favor of
> introducing the equivalent usage as Gentoo USE flags, which was its
> main intention! :) It could make Debian a viable source-based
> distribution to use or base
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
* Package name: coreschema
Version : 0.0.4
Upstream Author : Tom Christie
* URL : https://github.com/core-api/python-coreschema
* License : BSD
Programming Lang: Python
Descripti
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
* Package name: python-jsonhyperschema-codec
Version : 1.0.2
Upstream Author : Tom Christie
* URL : https://github.com/core-api/python-jsonhyperschema-codec
* License : BSD
Program
Package: wnpp
Severity: wishlist
Owner: Andreas Tille
* Package name: r-cran-whisker
Version : 0.3-2
Upstream Author : Edwin de Jonge
* URL : https://cran.r-project.org/package=whisker
* License : GPL
Programming Lang: GNU R
Description : GNU R mustach
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
* Package name: python-hal-codec
Version : 1.0.2
Upstream Author : Tom Christie
* URL : https://github.com/core-api/python-hal-codec
* License : BSD
Programming Lang: Python
Desc
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
* Package name: python-openapi-codec
Version : 1.3.2
Upstream Author : Tom Christie
* URL : https://github.com/core-api/python-openapi-codec
* License : BSD
Programming Lang: Pytho
Quoting Simon McVittie (2018-01-09 17:42:04)
> On Tue, 09 Jan 2018 at 15:40:04 +, Wookey wrote:
> > On 2018-01-09 15:07 +0100, Johannes Schauer wrote:
> > > Thus, we keep packages built with a different build profile but the same
> > > name/version/arcitecture bit-by-bit identical to each other
Quoting Adrian Bunk (2018-01-09 20:54:31)
> On Tue, Jan 09, 2018 at 01:22:33PM -0500, Michael Stone wrote:
> > On Tue, Jan 09, 2018 at 11:35:30AM -0500, Jeremy Bicha wrote:
> > > At times, Ubuntu needs to avoid certain build-dependencies because
> > > they would add an unwanted "universe" binary de
On Fri, Dec 22, 2017 at 08:51:37AM -0500, Scott Kitterman wrote:
>...
> I intend to work within the FTP Team to get some clarification on the team's
> position on this, but I don't expect it to be quick. I agree we could do
> with
> better documentation of what the policy is and why.
>...
Than
Quoting Jeremy Bicha (2018-01-09 17:35:30)
> On Tue, Jan 9, 2018 at 9:07 AM, Johannes Schauer wrote:
> > So we
> > could talk about whether we should allow more build profiles that change
> > binary
> > package contents but so far I don't see the use case for them and thus the
> > discussion woul
Package: wnpp
Severity: wishlist
Owner: =?utf-8?q?Pierre-Elliott_B=C3=A9cue?=
* Package name: itypes
Version : 1.1.0
Upstream Author : Tom Christie
* URL : https://github.com/tomchristie/itypes
* License : BSD
Programming Lang: Python
Description : Pyt
> "Adrian" == Adrian Bunk writes:
Adrian> On Tue, Jan 09, 2018 at 01:23:32PM +0100, Guillem Jover wrote:
>> ... Given the background of build-profiles, I'm very much in
>> favor of introducing the equivalent usage as Gentoo USE flags,
>> which was its main intention! :) It co
On Tue, 09 Jan 2018 at 22:47:07 +0100, Johannes Schauer wrote:
> As by policy §12.3, removing (or changing) content from
> /usr/share/doc should always be fine:
>
> | Packages must not require the existence of any files in /usr/share/doc/ in
> | order to function.
>
> So by that logic gtk-doc d
On Tue, Jan 9, 2018 at 10:07 PM, Johannes Schauer wrote:
> No, there is no header in the binary packages that indicates with which
> profile
> a source package was built to generate the given binary package.
Is this information present in the new buildinfo files?
--
bye,
pabs
https://wiki.deb
Quoting Paul Wise (2018-01-10 02:40:07)
> On Tue, Jan 9, 2018 at 10:07 PM, Johannes Schauer wrote:
> > No, there is no header in the binary packages that indicates with which
> > profile a source package was built to generate the given binary package.
> Is this information present in the new buildi
43 matches
Mail list logo
