-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
> E: klee: sharedobject-in-library-directory-missing-soname
> usr/lib/libkleeRuntest.so N: N:A shared object was identified
> in a library directory (a directory in N:the standard linker
> path) which doesn't have a SONAME. This is usua
Hi,
On 27.02.2016 05:43, Paul Wise wrote:
> I would have thought porters would be following the buildd/piuparts/CI
> pages for their port (where available) and thus would not need to be
> notified about arch-specific FTBFS or testing issues.
For the most part, maintainers are in a much better po
Quoting Bas Wijnen (2016-02-26 20:16:32)
> On Fri, Feb 26, 2016 at 07:59:29PM +0100, Jonas Smedegaard wrote:
>> Do we favor tracking the true upstreams when packaging for Debian?
>
> There was some discussion about this on the list recently, but this is
> a question that didn't really come up, AFA
Paul Wise wrote:
> I would have thought porters would be following the buildd/piuparts/CI
> pages for their port (where available) and thus would not need to be
> notified about arch-specific FTBFS or testing issues.
buildd.d.o is an essential data source, but the way it is displayed
there is not
On 02/27/2016 02:41 PM, Steven Chamberlain wrote:
> * B-D Uninstallable can be a huge list, where dozens of those only
> wait for just one package - it makes sense to group/collapse them;
> (this happens in the dose pages also)
I have a question here: package A build-depends on libB. A h
Package: wnpp
Severity: wishlist
Owner: Kartik Mistry
* Package name: apertium-sv-da
Version : 0.5.1~r44849
Upstream Author : Per Tunedal, Francis Tyers ,
Jacob Nordfalk ,
Michael Kristensen, Universitat d'Alacant (Transducens
group)
* URL
On Sat, Feb 27, 2016 at 9:41 PM, Steven Chamberlain wrote:
> buildd.d.o is an essential data source
...
> some ideas could be implemented into buildd.d.o itself someday.
Why someday and not today?
--
bye,
pabs
https://wiki.debian.org/PaulWise
Christian Seiler wrote:
> I have a question here: package A build-depends on libB. A has
> Arch: any or Arch: linux-any in debian/control. libB OTOH only
> has e.g. Arch: amd64 i386 mips in it's control file.
Concrete example:
https://bugs.debian.org/811554
There I suggested blacklisting known-ba
On 02/27/2016 05:18 PM, Steven Chamberlain wrote:
>> I have a question here: package A build-depends on libB. A has
>> Arch: any or Arch: linux-any in debian/control. libB OTOH only
>> has e.g. Arch: amd64 i386 mips in it's control file.
>
> Concrete example:
> https://bugs.debian.org/811554
Whil
Package: wnpp
Severity: wishlist
Owner: Christopher Baines
* Package name: django-prometheus
Version : 1.0.6
Upstream Author : Uriel Corfa
* URL : https://github.com/korfuri/django-prometheus
* License : Apache
Programming Lang: Python
Description : Dj
Package: wnpp
Severity: wishlist
Owner: "Víctor Cuadrado Juan"
* Package name: python-proselint
Version : 0.3.5
Upstream Author : Amperser Labs, http://github.com/amperser
* URL : http://proselint.com
* License : BSD
Programming Lang: Python
Description
11 matches
Mail list logo