On Thu, Apr 18, 2013 at 07:21:32PM -0700, Nikolaus Rath wrote:
> No, it's not quite as bad. The following works as well:
>
> dpkg --force-depends -i build-deps.deb && apt-get -f install
Why force-depends? Why not dpkg --unpack?
--
AJK
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.d
On 2013-04-18 09:24, Helmut Grohne wrote:
> Andreas, could you test those debdiffs with your piuparts setup? I have
I'll be offline over the weekend and look at this on Monday
> a few more requests though:
> * Can you ensure to pass -o Debug::pkgPackageManager=true to apt?
no problem
> * Can yo
On Thu, Apr 18, 2013 at 10:56:34AM +0200, Goswin von Brederlow wrote:
> On Tue, Apr 02, 2013 at 02:28:23PM -0700, Russ Allbery wrote:
> > Niko Tyni writes:
> >
> > > FWIW, I've done ABI-incompatible uploads of perl to experimental in the
> > > past without changing the perlapi-* virtual package n
On Thu, Apr 18, 2013 at 09:24:30AM +0200, Helmut Grohne wrote:
> I believe that we will need a deeper look at #482140. At the moment I do
> not fully understand that issue and its implications. The root cause
> appears to be lenny's update-xmlcatalog being in a temporarily
> inconsistent state due
On 2013-04-18, Goswin von Brederlow wrote:
>> Oh, that's a good point. Yes, I hadn't thought about that specific case
>> for testing ABI breakage in experimental.
>
> But then that simply is a broken upload. It will break horribly if you
> install the experimental perl but keep other perl package
On Thu, Apr 18, 2013 at 04:41:35PM +0200, Matthias Klose wrote:
> So what is the status for some runtimes/interpreters (would like to see some
> follow-up/corrections from package maintainers)?
> - Perl: Afaik, Neil did prepare the interpreter to cross-build, and
>to co-install the runtime a
On Thu, Apr 18, 2013 at 11:01:17PM -0700, Steve Langasek wrote:
> On Thu, Apr 18, 2013 at 04:18:38PM +0100, Neil Williams wrote:
> > I don't see a need to have the perl:i386 interpreter installed on amd64
> > in order to build third party i386 perl modules, the amd64 interpreter
> > should be fine
On Fri, Apr 19, 2013 at 05:26:41PM +0300, Niko Tyni wrote:
> On Thu, Apr 18, 2013 at 11:01:17PM -0700, Steve Langasek wrote:
> > On Thu, Apr 18, 2013 at 04:18:38PM +0100, Neil Williams wrote:
> > > I don't see a need to have the perl:i386 interpreter installed on amd64
> > > in order to build thir
Package: wnpp
Severity: wishlist
Owner: Luke Faraone
* Package name: statsd
Version : 0.6.0
Upstream Author : Etsy
* URL : https://github.com/etsy/statsd
* License : Expat
Programming Lang: Javascript (node.js)
Description : Stats aggregation daemon
St
Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard
* Package name: amqp-spec
Version : 1.0
Upstream Author : AMQP Working Group
* URL : http://www.amqp.org/
* License : BSD-3-clause
Programming Lang: XML
Description : specs for the Advanced Messag
On Fri, Apr 19, 2013 at 08:01:40AM -0700, Steve Langasek wrote:
> On Fri, Apr 19, 2013 at 05:26:41PM +0300, Niko Tyni wrote:
> > The modules aren't linked against libperl, it's
> > the other way around: libperl loads them at run time with dlopen(3).
> > They are effectively plugins in a private di
On Thu, Apr 18, 2013 at 14:58:21 +1000, Stuart Prescott wrote:
> I don't doubt that there is a smaller subset of packages that can reproduce
> this failure, especially since installing those two drags in several hundred
> others -- that was just as far as I had managed to get in narrowing it dow
Hi,
Am Donnerstag, den 18.04.2013, 19:28 -0700 schrieb Nikolaus Rath:
> Joachim Breitner writes:
> > Am Dienstag, den 16.04.2013, 21:19 -0700 schrieb Nikolaus Rath:
> >> Has someone already written a tool to automate this? I.e., parse
> >> debian/control and run the appropriate apt-get command?
>
On Fri, Apr 19, 2013 at 12:33:07AM +0200, Guillem Jover wrote:
> As I pointed out on the debian-perl mailing list, after having
> discussed about multiarch support for perl, I don't think a fully
> multiarchified perl (nor at least python) should be uploaded to sid,
> as going full multiarch on the
On Thu, Apr 18, 2013 at 04:41:35PM +0200, Matthias Klose wrote:
> - Ruby: Afaik, not yet started on multiarch.
Ruby 2.0 has multiarch support upstream. The Debian packaging is not
finished yet, but it will have multiarch.
I do not plan to multiarch 1.9.
--
Antonio Terceiro
signature.asc
Des
Hi,
2013/4/19 peter green :
> Nobuhiro Iwamatsu wrote:
>>
>> Hi, all.
>>
>> Plat'Home is one of the Debconf 13 sponsor will sell at discount to
>> Debian member and FLOSS Developer for the OpenBlocks of small ARM micro
>> server.
>>
>> https://openblocks.plathome.com/form/obs_verification/input.
Helmut Grohne wrote:
> Barring any mistakes this appears like a possible solution to the
> problem. Did you spot anything obviously wrong? Any example where you
> don't see how to work it out?
It seems correct at first glance, but not enough to solve all the issues
mentioned. Currently existing pa
17 matches
Mail list logo