On Thu, Apr 18, 2013 at 04:18:38PM +0100, Neil Williams wrote:
> > - Third party modules for interpreters should be cross-buildable.
> >Many build systems for interpreter languages are written in the
> >interpreter language itself. So you do require the interpreter
> >for the build, an
Le 18/04/2013 12:07, Marc Haber a écrit :
>> The tool you are looking for is "mk-build-deps" from the package
>> "devscripts".
>
> So one uses mk-build-deps to create a .deb containing the build
> dependencies as binary dependencites, put that .deb into an local
> aptable archive, run apt-get upd
On Thu, Apr 18, 2013 at 04:18:20PM +0100, Neil Williams wrote:
> On Thu, 18 Apr 2013 16:41:35 +0200
> Matthias Klose wrote:
>
> > - running a gdb:amd64 on i386 to debug 64bit binaries. This is the
> >reason for our current gdb64 package on i386, but it is missing the
> >support for the p
Joachim Breitner writes:
> Hi,
>
> 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?
>
> The package haskell-debian-utils contains a program named
> apt-get-
Marc Haber writes:
> On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy
> wrote:
>>The tool you are looking for is "mk-build-deps" from the package "devscripts".
>
> So one uses mk-build-deps to create a .deb containing the build
> dependencies as binary dependencites, put that .deb into an local
The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.
Total number of orphaned packages: 514 (new: 1)
Total number of packages offered up for adoption: 147 (new: 0)
Total number of packages request
On 18 April 2013 19:13, Sergei Golovan wrote:
> Hi!
>
> On Thu, Apr 18, 2013 at 9:56 PM, Andrew Shadura wrote:
>>
>> Hello,
>>
>>
>> By the way, have you contacted Sergei on this?
>
> I saw the bugreports and I'm planning to start working on them after
> wheezy release.
>
Yeah there is no rush r
Hi!
[ I had pending warning about this on debian-devel before the release,
so this is a good way to do that. :) ]
On Thu, 2013-04-18 at 16:41:35 +0200, Matthias Klose wrote:
> There are maybe not many use cases where you do want to install an interpreter
> like python or perl for a foreign arch
Hi Gabriela,
Some history in this link:
http://www.debian.org/doc/manuals/project-history/ch-releases.es.html
And looking for the packages for that release:
I can see the kernel version was 1.2.13
http://archive.debian.org/debian-archive/debian/dists/Debian-0.93R6/binary/Packages
In the secti
On Thu, Apr 18, 2013 at 09:20:33PM +, GABITA RODRIGUEZ DE MEDINA wrote:
> Hi, sorry to bother you, but I'm doing research for operating systems in my
> study center, the question is technical features that had debian 0.93, which
> kernell used, which network protocols, file system, etc..Thank
Hi,
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?
The package haskell-debian-utils contains a program named
apt-get-build-depends that does exactly that.
> your question is better suited for one of the various support
> channels. Including but not limited to the
> debian-u...@lists.debian.org mailinglists, which are even available
> in different languages.
> Some quick answers anyway:
Thanks
I changed it from the user list at the last minute as
Hi, sorry to bother you, but I'm doing research for operating systems in my
study center, the question is technical features that had debian 0.93, which
kernell used, which network protocols, file system, etc..Thank you for helping
GABRIELA RODRIGUEZMONTEVIDEO URUGUAY
Hi Kevin,
your question is better suited for one of the various support channels.
Including but not limited to the debian-u...@lists.debian.org mailinglists,
which are even available in different languages.
Some quick answers anyway:
On Thu, Apr 18, 2013 at 11:42 PM, Kevin Chadwick wrote:
> Doe
Hi,
Thank you for your comment.
2013/4/17 Lennart Sorensen :
> On Wed, Apr 17, 2013 at 08:53:24AM +0900, Nobuhiro Iwamatsu wrote:
>> 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.
>>
>> h
http://superuser.com/questions/95509/tell-aptitude-to-ignore-broken-package
Does this work and is aptitude the best way to update whilst ignoring
incorrect or even debatable dependencies or can apt-get do so too.
Is equiv a fast and easy solution?
Currently I am getting fix broken on steam-laun
]] Neil Williams
> The code to do this exists, it up to you to use it instead of whinging
> about the Social Contract, *again*. (Always the last resort of those
> who only want to complain without actually writing some code.)
That's not a particularly useful comment in this context as the bug in
Matthias Klose writes:
> There are maybe not many use cases where you do want to install an
> interpreter like python or perl for a foreign architecture, but there
> are some use case where such a setup makes sense.
One additional use case: I want to be able to do this in order to
cross-grade (t
On Thu, Apr 18, 2013 at 06:15:26PM +0100, Ian Jackson wrote:
> Goswin von Brederlow writes ("Re: multiarch and interpreters/runtimes"):
> > Co-installability of interpreters is generally not planed and would
> > have to be made as custom solutions, i.e. place the interpreter in
> > /usr/lib/x86_64-
Hello,
On Thu, 18 Apr 2013 22:13:04 +0400
Sergei Golovan wrote:
> > To Sergei (added to Cc): I'd like to join the effort in packaging
> > Tcl/Tk and stuff, as I said before; but as you've been the most
> > active person on the team for quite some time I'm a bit hesitant
> > about interrupting th
Hi!
On Thu, Apr 18, 2013 at 9:56 PM, Andrew Shadura wrote:
>
> Hello,
>
>
> By the way, have you contacted Sergei on this?
I saw the bugreports and I'm planning to start working on them after
wheezy release.
>
> > Personally, I'm not yet convinced about this interpreter
> > multiarchification,
Hello,
On Thu, 18 Apr 2013 16:07:44 +0100
Dmitrijs Ledkovs wrote:
> > On 18 April 2013 16:41, Matthias Klose wrote:
> >> - Tcl/Tk: Wookey and Dimitrij did start on that in Ubuntu, patches
> >>are available in Debian bug reports.
> >>Currently the shared libraries are split out into sep
Hi,
2013-04-16 21:19, Nikolaus Rath:
> Has someone already written a tool to automate this? I.e., parse
> debian/control and run the appropriate apt-get command?
If you not fear using a different package manager, try this:
http://people.debian.org/~jackyf/cupt-satisfy-control-deps
(parser sucks,
Goswin von Brederlow writes ("Re: multiarch and interpreters/runtimes"):
> Co-installability of interpreters is generally not planed and would
> have to be made as custom solutions, i.e. place the interpreter in
> /usr/lib/x86_64-linux-gnu/perl/ and provide /usr/bin/perl as
> alternative.
I think
On Thu, 18 Apr 2013 18:42:10 +0200
Marc Haber wrote:
> And because we want to do a really really good solution, a ten year
> old wishlist bug which has a patch in the BTS for three years remains
> unsolved?
It's wishlist - I dread to think how many higher severity bugs have been
opened and clos
On Thu, 18 Apr 2013 12:27:15 +0200, Jakub Wilk
wrote:
>Or just pass -i to mk-build-deps, which does all the steps for you.
Missed that. Sorry. Thanks.
Greetings
Marc
--
-- !! No courtesy copies, please !! -
Marc Haber | " Questions are the
On Thu, 18 Apr 2013 12:32:50 +0200, Jakub Wilk
wrote:
>* Lars Wirzenius , 2013-04-18, 11:19:
>>ideally, dpkg-checkbuilddeps could have an output mode that just lists
>>the package names and could be fed to apt-get install:
>>
>>apt-get install $(dpkg-checkbuilddeps --package-names-only)
>
>#2
On Thu, 18 Apr 2013 18:13:08 +0800, Paul Wise wrote:
>On Thu, Apr 18, 2013 at 6:07 PM, Marc Haber wrote:
>> On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy wrote:
>>>The tool you are looking for is "mk-build-deps" from the package
>>>"devscripts".
>>
>> So one uses mk-build-deps to create a .d
Le jeudi 18 avril 2013 à 16:41 +0200, Matthias Klose a écrit :
> - Python: co-installable runtime and development files, cross-buildability
>upstreamed for 2.7.4 and 3.3.1. There is a way to cross-build third
>party modules using distutils/setuptools. Packages are available in
>experim
On Thu, Apr 18, 2013 at 12:07 PM, Marc Haber
wrote:
> On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy
> wrote:
>>The tool you are looking for is "mk-build-deps" from the package "devscripts".
>
> So one uses mk-build-deps to create a .deb containing the build
> dependencies as binary dependenc
Package: wnpp
Severity: wishlist
Owner: Luke Faraone
* Package name: defusedxml
Version : 0.4.1
Upstream Author : Christian Heimes
* URL : https://pypi.python.org/pypi/defusedxml
* License : Python
Programming Lang: Python
Description : XML bomb protec
On Thu, 18 Apr 2013 16:41:35 +0200
Matthias Klose wrote:
> - running a gdb:amd64 on i386 to debug 64bit binaries. This is the
>reason for our current gdb64 package on i386, but it is missing the
>support for the python based pretty printer.
>Installing gdb:amd64 on i386 in wheezy wil
On Thu, 18 Apr 2013 16:41:35 +0200
Matthias Klose wrote:
> - running a gdb:amd64 on i386 to debug 64bit binaries. This is the
>reason for our current gdb64 package on i386, but it is missing the
>support for the python based pretty printer.
>Installing gdb:amd64 on i386 in wheezy wil
On 18 April 2013 15:55, Andrew Shadura wrote:
> Hello,
>
> On 18 April 2013 16:41, Matthias Klose wrote:
>> - Tcl/Tk: Wookey and Dimitrij did start on that in Ubuntu, patches
>>are available in Debian bug reports.
>>Currently the shared libraries are split out into separate packages,
>>
On Thu, Apr 18, 2013 at 04:41:35PM +0200, Matthias Klose wrote:
> There are maybe not many use cases where you do want to install an interpreter
> like python or perl for a foreign architecture, but there are some use case
> where such a setup makes sense. For now I see this limited for architectu
Hello,
On 18 April 2013 16:41, Matthias Klose wrote:
> - Tcl/Tk: Wookey and Dimitrij did start on that in Ubuntu, patches
>are available in Debian bug reports.
>Currently the shared libraries are split out into separate packages,
>and are co-installable. Not yet tested if this enough
On Tue, Apr 16, 2013 at 09:19:27PM -0700, Nikolaus Rath wrote:
> Hello,
>
> When downloading a source package from somewhere else, I often find
> myself in the situation that after..
If by downloading you mean "apt-get source foo" then the answere is:
apt-get build-dep foo
Otherwise there is
On Thu, Apr 18, 2013 at 11:04:11AM +0200, Ansgar Burchardt wrote:
> On 04/18/2013 10:48, Goswin von Brederlow wrote:
> > On Sun, Apr 07, 2013 at 09:29:19PM +0800, Thomas Goirand wrote:
> >> On 04/02/2013 09:18 PM, Goswin von Brederlow wrote:
> >>> Actually that hits another problem. Namely that the
There are maybe not many use cases where you do want to install an interpreter
like python or perl for a foreign architecture, but there are some use case
where such a setup makes sense. For now I see this limited for architecture
pairs like amd64/i386, armel/armhf, ia64/i386, i.e. for architectur
On Thu, Apr 18, 2013 at 04:13:32PM +0200, Tollef Fog Heen wrote:
> ]] Lars Wirzenius
>
> > - if it's a lot of packages, I construct a complicated sed
> > and awk and so on pipeline to extract the package names
> > and feed those to apt-get install
>
> Aka /usr/lib/pbuilder/pbuild
]] Lars Wirzenius
> - if it's a lot of packages, I construct a complicated sed
> and awk and so on pipeline to extract the package names
> and feed those to apt-get install
Aka /usr/lib/pbuilder/pbuilder-satisfydepends ?
--
Tollef Fog Heen
UNIX is user friendly, it's just picky
Am 16.04.2013 15:19, schrieb Wookey:
> +++ Игорь Пашев [2013-04-16 16:49 +0400]:
>> 2013/4/16 Neil Williams :
>>> On Tue, 16 Apr 2013 16:11:24 +0400
>>>
>>
>>
>> So, is it important, that multiarch dirs go after crossdirs:
>> our @librarypaths = (DEFAULT_LIBRARY_PATH, @crosslibrarypaths);
>> ?
>
>
Hi!
Marc Haber writes:
> On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy
> wrote:
>>The tool you are looking for is "mk-build-deps" from the package "devscripts".
>
> So one uses mk-build-deps to create a .deb containing the build
> dependencies as binary dependencites, put that .deb into an
* Lars Wirzenius , 2013-04-18, 11:19:
ideally, dpkg-checkbuilddeps could have an output mode that just lists
the package names and could be fed to apt-get install:
apt-get install $(dpkg-checkbuilddeps --package-names-only)
#214566
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-devel-
* Marc Haber , 2013-04-18, 12:07:
The tool you are looking for is "mk-build-deps" from the package
"devscripts".
So one uses mk-build-deps to create a .deb containing the build
dependencies as binary dependencites, put that .deb into an local
aptable archive, run apt-get update and apt-get inst
On Thu, 18 Apr 2013 12:07:25 +0200
Marc Haber wrote:
> On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy
> wrote:
> >The tool you are looking for is "mk-build-deps" from the package
> >"devscripts".
>
> So one uses mk-build-deps to create a .deb containing the build
> dependencies as binary d
On Thu, Apr 18, 2013 at 12:07:25PM +0200, Marc Haber wrote:
> On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy
> wrote:
> >The tool you are looking for is "mk-build-deps" from the package
> >"devscripts".
>
> So one uses mk-build-deps to create a .deb containing the build
> dependencies as bin
On Thu, Apr 18, 2013 at 6:07 PM, Marc Haber wrote:
> On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy wrote:
>>The tool you are looking for is "mk-build-deps" from the package "devscripts".
>
> So one uses mk-build-deps to create a .deb containing the build
> dependencies as binary dependencites,
On Wed, 17 Apr 2013 09:45:32 +0100, Roger Leigh
wrote:
>On Tue, Apr 16, 2013 at 09:19:27PM -0700, Nikolaus Rath wrote:
>> Has someone already written a tool to automate this? I.e., parse
>> debian/control and run the appropriate apt-get command?
>>
>> I think I am *not* looking for apt-get build-
On Wed, 17 Apr 2013 14:05:47 +0900, Charles Plessy
wrote:
>The tool you are looking for is "mk-build-deps" from the package "devscripts".
So one uses mk-build-deps to create a .deb containing the build
dependencies as binary dependencites, put that .deb into an local
aptable archive, run apt-get
On 04/18/2013 10:48, Goswin von Brederlow wrote:
> On Sun, Apr 07, 2013 at 09:29:19PM +0800, Thomas Goirand wrote:
>> On 04/02/2013 09:18 PM, Goswin von Brederlow wrote:
>>> Actually that hits another problem. Namely that the epoch does not
>>> appear in the binary package filename. While wheezy wo
On 2013-04-18 10:48 +0200, Goswin von Brederlow wrote:
> On Sun, Apr 07, 2013 at 09:29:19PM +0800, Thomas Goirand wrote:
>> On 04/02/2013 09:18 PM, Goswin von Brederlow wrote:
>> > Actually that hits another problem. Namely that the epoch does not
>> > appear in the binary package filename. While
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 name or the libperl
> > SONAME. The aim was to experiment with different configu
On Sun, Apr 07, 2013 at 09:29:19PM +0800, Thomas Goirand wrote:
> On 04/02/2013 09:18 PM, Goswin von Brederlow wrote:
> > Actually that hits another problem. Namely that the epoch does not
> > appear in the binary package filename. While wheezy would have 1.2.3-1
> > and unstable would have 1:1.2.3
On Thu, Apr 18, 2013 at 02:58:21PM +1000, Stuart Prescott wrote:
> Helmut Grohne wrote:
> > The conclusion here is that the only way to fix this bug in sgml-base is
> > to have *no* dependency on dpkg at all.
>
> Actually, removing the dependency on dpkg doesn't change the outcome at all
> --
>
55 matches
Mail list logo
