ext robert bauer writes:
> The proposed alternative site (apps.formeego.com) seems to be a
> corporate-sponsored site from our own long lost friend, Nokia.
I'd say that corporate sponsership of community controlled
infrastructure is a very good thing, much better than corporate
controlled infras
ext Niels Breet writes:
> Problem Mohammad faced here is that HAM holds a lock, so you can't run
> apt-get in the background. This is why he needs to open the xterm and
> ask the user to close HAM.
Yes. But what about launching that script from a launcher entry instead
of asking people to type
ext Mohammad Abu-Garbeyyeh writes:
> Unfortunately, while this might be the right way, it caused me some problems
> with the enabler package, so to work around it, a terminal window is started
> from HAM (postinst) and then the postinst exits, the user then has to exit HAM
> and go back to the te
ext Eino-Ville Talvala writes:
> This seems like an unfortunate situation in terms of bug fixes and so on
> - we think fcam-drivers is pretty stable, so hopefully we don't have to
> update it again anytime soon!
You can make the fcam-drivers package visible in the UI, just like
applications.
ext Alistair Buxton writes:
> This is, apparently, by design.
No, not really. It's a known misfeature.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
"Tamminen Eero (Nokia-MS/Helsinki)" writes:
>> When I do:
>>dpkg -x xnee_3.02-2maemo2_all.deb .
>>
>> all I see is some docs
>
> It's a virtual package depending on the actual binary implementation
> package.
Virtual packages don't exist as archives, they are only mentioned in
"Provides".
ext Yves-Alexis Perez writes:
>> If you use apt-get unmodified, you need to provide permanent download
>> URLs for the packages, and my understanding is that the Ovi Store can
>> not provide those _and_ control their accesses. They protect against
>> unauthorized downloads by using random, tempo
ext Sivan Greenberg writes:
> Hi Marius,
>
> On Thu, Jul 22, 2010 at 11:59 AM, Marius Vollmer
> wrote:
>>
>> For Harmattan, we are putting a "Ovi Store Adaptor" into place which
>> makes the Ovi Store look like a regular repository. The apt-cache
>&g
ext Yves-Alexis Perez writes:
> On 22/07/2010 10:10, Marius Vollmer wrote:
>> The Application Manager has been 'optimized' for repositories, and the
>> code for dealing with Debian package files has been neglected. Now with
>> the Ovi Store using standalone Deb
ext Sascha Mäkelä writes:
> 1. Detectect if the device is Offline and give appropriate warning.
> 2. Detect if the device is connected and if not establish the connection.
> 3. If the connection is set to manual, the app needs to give the necessary
>prompt.
> 4. If the connection is set to au
ext Sascha Mäkelä writes:
> So according your opinion, should I wait for this issue to be resolved at
> Nokia's end or should I try to make changes to my app?
Don't wait for us, try to work around the problem on your side.
> The one suggestion I've been given several times is to statically
> in
"ext Ville M. Vainio" writes:
> That comment doesn't apply since applications are downloaded from repository,
> triggered by .install file (unless there is a terrible misunderstanding
> somewhere).
This is true for gratis packages, but paid packages are downloaded as
Debian packages, not as .ins
"ext Ville M. Vainio" writes:
> Well, that's certainly not the general understanding (inside Nokia) of how it
> should work. Do you care to elaborate so that we can escalate the issue (with
> the understanding that it's holiday period...)?
Ville, if you escalate this, the right thing IMO would b
ext Attila Csipa writes:
> It's probably not a good idea but you can work around the issue like
> the Qt smart installer does - omit any non-base firmware dependencies,
> and use a loader. That way the install will succeed, and then via the
> loader you can apt-get/application-manager install wha
"Vollmer Marius (Nokia-MS/Helsinki)" writes:
> The partitions are 2G / 256M = 8.
Of course, there is less than 256M free for apps in the rootfs, so
scratch the 8. It's probably more like 2G / 100M = 20ish. A bit
tougher, but you are almost there... :)
__
ext Martin Storsjö writes:
> OPT folder value should be 80% of USR folder.
Taken literally, this means that the OPT folder is actually supposed to
be smaller than the USR folder... :-)
> ACTUAL OUTCOME:
> Opt folder value is not 80% of usr folder ,usr=84,opt=388k.
This actually checks out for
ext Sascha Mäkelä writes:
> OK. If Ovi Store for paid apps is no using a repository, then what about
> using preinst script or something to install the dependencies?
You unfortunately can't run dpkg recursively and thus can't install
packages from maintainer scripts.
I have no good ideas, sorry
ext Sascha Mäkelä writes:
> This is rather strange, since I was under the impression that apt-get
> would automatically download the missing packages.
(The following might not be entirely accurate since I have no experience
whatsoever with Ovi myself, and not much experience with the Fremantle
A
ext Tomi Ollila writes:
> On Fri 02 Jul 2010 12:31, Martin Storsjö writes:
>
>> dh_fixperms, which write the list of files for tarlisted, doesn't
>> recognize symlinks at all, but this can be fixed with the attached
>> patch.
>
> There is a reason for that: Windows (below 7) (NTFS) filesystem
ext Cornelius Hald writes:
> On Tue, 2010-06-01 at 08:43 +0300, Marius Vollmer wrote:
>> ext Cornelius Hald writes:
>>
>> > as there has been no news since February, I think I should see whether
>> > or not someone is still responsible for this bug:
ext Cornelius Hald writes:
> as there has been no news since February, I think I should see whether
> or not someone is still responsible for this bug:
>
> https://bugs.maemo.org/show_bug.cgi?id=7707
Yep, that's me. Thanks for the reminder, I'll get back to this soon.
__
ext Robin Burchell writes:
> Things as I understand it:
> - Qt 4.5 on Maemo5 had no API/ABI compatibility guarentees.
> - Qt 4.6 took liberal advantage of that to change and fix some rather
> suboptimal parts.
This might have been handled better, though, with a proper soname change
etc. There a
ext Marcin Juszkiewicz writes:
>> Is there a way of specifiying to use the older packages?
>
> No such option.
The problem are the automatic generated dependencies, if I understand
things right.
I.e., you build against libqt4-core version 4.6.2~git20100224, and the
resulting package ends up hav
"ext luarvi...@gmail.com" writes:
> [...] What I do see though is that the Extras admission/promotions
> processes have become so bothersome to developers that they border on
> hostile.
I don't have an opinion on this, since I am not at all involved in any
of the specifics. (I have no packages
"ext Luarvique L. Luarvique" writes:
> This whole talk about "any repository but Extras is unsafe and evil"
> is mostly bullshit, and I think most users are smart enough to know
> it.
It might be mostly bullshit, but not entirely. If we teach people that
it is normal to go hunting for alternati
ext Jeremiah Foster writes:
> One huge issue with the repository is the tool used on the backend:
> apt-ftparchiver. This tool cannot automatically remove debs and source
> packages, causing huge disk bloat (some packages have four or five versions
> sitting on the repos.)
I think apt-ftparchive
"ext urho.kontt...@gmail.com" writes:
>> I don't think the centralized nature is a problem here. Our current
>> processes and implementations might not scale well enough, but
>> getting rid of a centralized repository will not help much, if at
>> all.
>
> If we would actually start supporting rep
ext Urho Konttori writes:
> Also, the current model of centralized gigantic repository does not
> scale up too well. Just look at the state of using extras-devel is on
> the current devices (hint: slow pain).
[ Urho, thanks for this opportunity to talk about how we want to make
package manage
ext Nils Faerber writes:
> What would probably help here is to create a page on the Maemo Wiki
> listing all "known" external feeds and what can be found in there. This
> would make changes like this pretty obvious for people looking for it.
Even if you do that, it is better to remove obsolete v
ext Dieter Plaetinck writes:
> On Wed, 24 Mar 2010 14:21:37 +0200
> Marius Vollmer wrote:
>
>> ext Joerg Reisenweber writes:
>>
>> > If the script doesn't work as everybody would expect, then it
>> > shouldn't be there at all.
>>
>>
ext Joerg Reisenweber writes:
> If the script doesn't work as everybody would expect, then it shouldn't be
> there at all.
It's a 'conffile', so it will be left on the device even if you remove
the package. Also, you can't really change it by putting a newer
version in your package since the u
ext Attila Csipa writes:
> I'm not sure how the HAM prompts (or doesn't) for config file
> conflicts,
HAM passes --force-confold to dpkg.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-develo
ext Attila Csipa writes:
> On Tuesday 23 March 2010 01:00:19 Gary Birkett wrote:
>> why doesn't HAM allow somebody to use a later provided version from Beniots
>> own repository?
>> there would be nothing wrong with leaving everything existing and Beniot
>> can get what he wants by still offering
ext Jeremiah Foster writes:
> On Mar 22, 2010, at 7:47 AM, Marius Vollmer wrote:
>
>> In my view, MeeGo is a development effort, not a standardization
>> effort.
>
> I am not convinced that this is true. It looks like MeeGo is going to
> track upstream closely wit
"Stoppa Igor (Nokia-D/Helsinki)" writes:
> No at all: it's about standardization. The device must support a certain
> set of features and provide well defined APIs.
>
> So if a device is MeeGo compliant, it will be advertised as such.
In my view, MeeGo is a development effort, not a standardiza
ext Attila Csipa writes:
>> What about removing old versions completely? Old versions are useful,
>> but only quite rarely. If you want, you can keep a separate
>> "extras-history" repo with all versions ever that people can use if they
>> really need to get obsolete versions.
>
> Certainly a g
ext Tor writes:
> It'll work for simple installs like that, but you lose what's known as
> 'the power of apt'.
Not necessarily. You can keep the power of apt even if you only see a
subset of the whole distribution. This is what happens when you have
only "main" in sources.list on a Debian syst
ext Alberto Mardegan writes:
> It would be nice to have a server-side logic, that generates the Packages
> file
> dynamically: the client gives a package name (and optionally a version), and
> the
> web engine generates the Packages file which enables downloading of this
> file,
> it's Depe
ext Attila Csipa writes:
> There are probably many better ways to do this, but a quick and dirty
> solution
> would be to remove the icon from the older version in the repo when a new
> version is pushed to the repo.
What about removing old versions completely? Old versions are useful,
but o
ext Victor Manuel Jáquez Leal writes:
> 2010/3/8 Marius Vollmer :
>> Then you can activate the red-pill mode and unset the "Ignore packages
>> from wrong domain" setting.
>
> Red pill mode user interface flow was rem
ext Graham Cobb writes:
> All these are **real** problems we experienced in the early days of Maemo and
> are the reasons we created the common repositories and put a LOT of pressure
> on developers to use them. By having a common repository, there is always
> only one copy of the shared libr
ext Benoît HERVIER writes:
> (or even automatically configures your
> new repository and package domain, but you didn't hear that from me, and
> if you do that, please don't do it silently).
>
> Anyway it ll not past QA Testing :)
Why wouldn't it? Do we have a policy against this? Ahh, you p
ext Thomas Perl writes:
> 2010/3/8 Marius Vollmer :
>> ext Benoît HERVIER writes:
>>> The purpose is to migrate my softwares from "extras" to my own
>>> repository as i ll not push anymore my applications to extras, but
>>> only on my own reposito
ext Benoît HERVIER writes:
> The purpose is to migrate my softwares from "extras" to my own
> repository as i ll not push anymore my applications to extras, but
> only on my own repository.
Ahh, ok. This is not something that is well supported (as you have
found out), and I believe the Maemo co
ext Benoît HERVIER writes:
> As i'm the maintainer of this packages in "extras" repository, i need
> to found a solution :
What is the exact problem that you try to solve?
Do you want to install your own version from your own repository on your
own device?
Then you can activate the red-pill mo
ext 白い熊 writes:
> I think the reason is, as the page says: When a subprocess terminates,
> Emacs reads any pending output, then stops reading output from that
> subprocess. Therefore, if the subprocess has children that are still
> live and still producing output, Emacs won't receive that output.
ext 白い熊 writes:
> [... I don't know how to effectively spawn an asynchronous process in
> Emacs and have it wait for its output, [...]
Check out process filters:
http://www.gnu.org/software/emacs/manual/html_node/elisp/Output-from-Processes.html#Output-from-Processes
__
ext Lucas Maneos writes:
> On Mon, Mar 01, 2010 at 08:12:23AM +0200, Marius Vollmer wrote:
>> It might just be the missing public key. Without it, the signature on
>> your repo will not be recognized as valid, and it will be associated
>> with the "unsigned" d
ext Lucas Maneos writes:
> The story so far:
> - mined a bunch of patches from bugs.maemo.org
> - built some updated packages with the above
> - got Nokia's blessing to modify and redistribute osso-software-version-*
> - set up a test repository.
Great!
> The missing piece: making the updat
ext Martin DeMello writes:
> How do I clear out my ignore history?
Try this:
$ rm ~/.hildon-application-manager/{seen,tapped}-updates
We don't really keep a history of what has been ignored, just a brief
record of what has been shown in the "Updates" view. This is compared
to /var/lib/hild
ext David Greaves writes:
>> That's a bug in the "ignore" machinery: I think we only store which
>> packages have been ignored, but not which versions. This means that if
>> you ignore a OS update, you will never be notified again about OS
>> updates ever.
>
> Has a fairly big impact on the assu
ext David Greaves writes:
> My wife must have done an 'ignore' on a Maemo5 update sometime in oct/nov.
>
> The device never reminded her again. She only got pr1.1.1 because she noticed
> my
> device made a sound on account connections and hers didn't... I did 2 upgrades
> in succession. Normal u
ext Dave Neary writes:
> Then a new version of the SDK comes out, which is not backwards
> compatible. A number of potentially bad things can happen:
I agree with your points in general, but I want to qualify them a bit.
There are two issues:
- I think it is very important to be able to releas
ext Michael Cronenworth writes:
> If a user has access to downloading apps, then they will be notified of
> the Maemo update. If they want a new app, they must update Maemo, but
> they can continue using their old apps as long as they want. Refusing to
> update because of a personal preference
ext Anderson Lizardo writes:
> On Fri, Feb 5, 2010 at 4:28 AM, Marius Vollmer
> wrote:
>> - All PPAs are known to the maemo.org community, and their maintainers
>> allow NMUs to them, subject to the same rules as NMUs in
>> extras-devel.
>
> Sorry to hijack t
ext Jeff Moe writes:
> Right now things are just in random locations (for me and others). It
> would be nice to have it all unified.
extras-experimental? :-)
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/l
"ext Ville M. Vainio" writes:
> I find it hard to see anything "wrong" with PPA's as such,
I am one of the guys pushing for a central repository, but I can't see
anything wrong with PPA's either, as long as the following is part of
the "code of honor" of people maintaining such PPAs:
- A PPA i
Marius Vollmer writes:
> ext Marcin Juszkiewicz writes:
>
>> Which version of Maemo it covers? Rather not Maemo6 as it had to be Qt based
>> and pdf talks about GNOME GVFS.
>
> That's just a minor inaccuracy. Maemo 6 will use GIO and Gvfs.
Oh, I read your c
ext Marcin Juszkiewicz writes:
> Which version of Maemo it covers? Rather not Maemo6 as it had to be Qt based
> and pdf talks about GNOME GVFS.
That's just a minor inaccuracy. Maemo 6 will use GIO and Gvfs.
___
maemo-developers mailing list
maemo-dev
ext Jeff Moe writes:
>> Do you have the build logs online as well?
>
> Yes, from
> http://obra.freemoe.org/freemoe-etch/3/3dchess/root.log
> to
> http://obra.freemoe.org/freemoe-etch/z/zziplib/build.log
Great!
> * Depends: are ok? Just because the Build-Depends: were there doesn't mean
> the
ext Jeff Moe writes:
> * I rebuilt all Debian Etch source packages with the Maemo 5 SDK and sdbmock.
Cool!
> * 10,220 Source packages processed.
> * 6,451 .debs produced.
This means there were a lot of build failures (as could be expected).
Mining the failures would be interesting, too. I s
ext Aldon Hynes writes:
> While there are some in the free software movement that hold to various
> definitions of what 'free' means as well as many different licenses that
> people argue about, to most people buying cellphones, those discussions are
> meaningless.
In the context of this discuss
ext Jeremiah Foster writes:
> Why do you need scratchbox to build debs?
You need it to build debs for Maemo, unfortunately. The Maemo SDK does
not run anywhere else than in Scratchbox.
(For example, last I looked, the Maemo SDK relies on
/scratchbox/tools/bin/find being there. There is no /us
"ext Zhang, Xing Z" writes:
> Thanks it worked after I checked out contextkit source from repo.
> The prior source I used is context-0.5, no such file.
Ahh, yes, I should have mentioned that.
___
maemo-developers mailing list
maemo-developers@maemo.org
"ext Zhang, Xing Z" writes:
> Hi Marius:
> I met below errors when compiling context-commander:
>
> dottreemodel.cpp:28:22: error: duration.h: No such file or directory
> dottreemodel.cpp:29:25: error: contextjson.h: No such file or directory
These headers are in libcontextsubscriber.
"ext Zhang, Xing Z" writes:
> Is there any online documentation for Contextkit?
Yes, we have the -doc packages unpackaged here:
http://zagadka.vm.bytemark.co.uk/docboy/contextkit-doc/html/context-intro.html
> I apologize for my old Fedora, it lacks so many tools to build the
> in-source d
"ext Zhang, Xing Z" writes:
> I am trying to play contextkit. The README file told me there
> should be a contextd(context daemon). Unfortunately, I can't find it
> in my source directory after build while I can see
> libcontextprovider.so.0.0.0 and libcontextsubscriber.so.0.0.0. Anyone
> k
"Kojo Tero (Nokia-D/Helsinki)" writes:
> Large publicly listed companies have very strict rules when using
> money. There's even a law about it in the USA
> (http://en.wikipedia.org/wiki/Sarbanes_oxley) That has the implication
> that a listed company cannot buy from wherever, and that limits the
"Kojo Tero (Nokia-D/Helsinki)" writes:
> Marius, I want root access on all your machines. I want it, now! :)
Dude, after all this, I wouldn't even let you ride my bicycle.
> Also Marius, would you watch your language. Calling people names is
> rude. It gives a bad picture of your character, and
Marius Vollmer writes:
> Dave, for effs sake, Joe
^^^
It's "Jeff" of course. Sorry, I blame the lack of coffee.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mail
ext Dave Neary writes:
> I guess that the problem is that you "demand" rather than request.
Dave, for effs sake, Joe is not trying to get something for him and he
is not getting angry because he isn't getting it. Joe is pointing out
opportunities for Maemo's improvement and he is getting irrita
ext Graham Cobb writes:
> I *think* that, here in Maemo, we are trying to create a model with
> different goals from any of the other distributions, so our decisions may
> also be different, but I certainly want us to learn from other experience.
I wouldn't put it as "different goals", but wit
ext Graham Cobb writes:
> It is still my view that, if at all possible, applications should install on
> the initial release.
Yes, this is very important.
[ Still, it is also important to give good guidance to the user when it
does have in fact to update the OS before he can install a certai
ext Marcin Juszkiewicz writes:
> But I also read mails on N900 and Modest do not have such one ;(
Are you saying you can not get yourself a proper email client? :)
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mai
ext Marcin Juszkiewicz writes:
>> I feel a little cheeky asking this when I've only just joined the list
>> but I was wondering if anybody else thinks it is a good idea to have
>> mails to this list (and the other maemo lists) prefix the subject line
>> with the name of the list.
>
> No, No, No!
ext Dave Neary writes:
> You could accomplish a lot more by rattling fewer cages. You've known
> this community for 50 days.
It is important to listen to newcomers. They can provide much needed
reality checks and maybe keep you from staring at your own naval too
much.
While it is certainly nic
ext Jeff Moe writes:
> Here is a good article in LWN about a presentation by Josh Berkus. How
> many of these points apply to Nokia? I'm afraid way too many.
Maybe, but I find it also interesting how many points do _not_ apply.
"Maemo - it could be so much worse"
:-)
__
ext Marcin Juszkiewicz writes:
> Dnia sobota, 16 stycznia 2010 o 10:05:28 Andrew Flegg napisał(a):
>
>> The versions of dpkg in play, according to `dpkg --version':
>>
>> Native Ubuntu (Jaunty) 1.14.24ubuntu1
>> N900 (2.2009.51-1) 1.14.25
>> Scratchbox
ext Andrew Flegg writes:
> The versions of dpkg in play, according to `dpkg --version':
>
> Native Ubuntu (Jaunty) 1.14.24ubuntu1
> N900 (2.2009.51-1) 1.14.25
> Scratchbox (Fremantle rootstrap) 1.13.25
>
> The downlevel version in the SDK means you can
Hi,
even I have noticed now that apt uses a lot more space than it used to.
One reason is that the package index files in the repository contain
entries for multiple versions of a package. This increases the size of
what apt has to download, process, and store significantly, and for no
real bene
ext Cornelius Hald writes:
> I´ll just hope that Marius finds some time to fix this and until then
> I´ll turn it off again.
Yep, I will find time.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/m
ext ibrahim writes:
> I wonder if an application package was installed from
> command-line "using dpkg -i package_name.deb" can it -at least- be
> uninstalled using the app manager ??
> does it have a chance to appear on Hildon application Manager's
> Uninstall list ??
Yes.
> If it is possib
ext Till Harbaum / Lists writes:
> i just added a debian/optify file containing nothing but the word
> auto to Maep 1.1. Unfortunately the resulting deb package still
> has the binary in /usr/bin
>
> Why?
Could you show a complete transcript of the build?
ext Valerio Valerio writes:
> Are the responsible(s) for the Application Manager willing to implement this
> change and ship it in a firmware update ? (pr1.2, pr1.3)
I think it is now high time to move the category definitions out of ham
and somehow get them from the repositories themselves.
I
ext Graham Cobb writes:
>> I still have to do something about the Python optification. I will do
>> that in the next few days.
>
> Thanks. We really need this in order to turn on optification by default.
I have some first version of a test that tries to identify Python
packages in the maemo-
ext Anderson Lizardo writes:
>> Well, the direct dependency check wouldn't do anything useful anymore,
>> or would it? (I.e., has-dependency || pymaemo-optify-is-installed ==
>> pymaemo-optify-is-installed.)
>
> Yes, having pymaemo-optify installed after .deb's have been created
> would be a ind
ext Andrew Flegg writes:
> Also, it'd be useful to have confirmation from Marius if the
> heuristics described here regarding Python apps have been implemented
> in mode "auto":
>
>
> http://lists.maemo.org/pipermail/maemo-developers/2009-December/022807.html
Not as written. I think I have
Marius Vollmer writes:
> ext Anderson Lizardo writes:
>
>> Is maemo-optify-deb run on autobuilder inside the scratchbox target
>> and after all dependencies have been installed?
>
> Yes. It is run after the package archives have been built and after
> pymaemo-opt
ext Anderson Lizardo writes:
> Is maemo-optify-deb run on autobuilder inside the scratchbox target
> and after all dependencies have been installed?
Yes. It is run after the package archives have been built and after
pymaemo-optify has done its thing. So maybe it is best just to look for
the e
ext Ed Bartosh writes:
> I'll definitely find a time to do whatever is needed. Moreover, I was
> asking couple of times already if it's time to enable optification by
> default in autobuilder. I was given an answer that some testing is
> still needed. I think Marius should know the latest status.
ext Frantisek Dufka writes:
>> It has not been implemented yet, and there is thus not much
>> experience with running the whole OS from the big eMMC.
>
> As for getting experience - it is easy to gain it by cloning any
> current OS version to card ;-)
Yes, we just haven't done that internally in
ext Andrew Flegg writes:
> On Sun, Jan 3, 2010 at 10:56, Matan Ziv-Av wrote:
>>
>> What do you mean "optify is the default"? optification is a temporary
>> hack, and it is being replaced by a real solution as soon as possible.
>
> I'll put money on it being a temporary hack for the lifetime of
>
ext Thomas Tanner writes:
> /usr/local seems to be in all search paths
You might be right, but my gut doesn't trust this, not with a system
with as little respect to tradition as Maemo has (i.e., our own new
components will in all likelyhood get this spectacularily wrong).
Also, putting stuff i
ext Till Harbaum / Lists writes:
> it's likely wait too late for such a question, but why doesn't just
> /opt/bin, /opt/share etc exist with the system looking into those
> paths as well?
My gut feeling is that this is not feasible in the short term, and
not good enough for the long term.
It is
ext Attila Csipa writes:
> A broader question is if the 500K as a *number* should be part of the blocker
> paragraph. [...]
I think the only sane thing to do is to look at the ratio of files in
/opt to those not in /opt, and require that ratio to be at least the
same as the ratio of the space i
ext Nathan Anderson writes:
> It appears that maemo-optify doesn't work (not sure where the --auto
> came from) doesn't work on the diablo builder.
Looks like maemo-optify in Diablo is too old. It shouldn't be there at
all, I think, but it's better to keep it up-to-date, so I have updated
ext Yves-Alexis Perez writes:
> On 16/12/2009 09:33, Marius Vollmer wrote:
>> (The main thing missing from debhelper IMO is better support for -dbg
>> packages.)
>
> Hmmh, what exactly do you need? Because with the tiny.rules, the only
> thing needed is the -dbg pa
"Denis-Courmont Remi (Nokia-D/Helsinki)"
writes:
> On Tuesday 15 December 2009 22:10:39 ext Jeremiah Foster, you wrote:
>> > * debian/compat: 7 -> 5
>> > * debian/control: Build-Depends: debhelper (>= 7) -> debhelper (>= 5)
>> > * And maybe comment out a few dh_* calls from debian/rules, which
>
ext Teemu Ikonen writes:
> [...] Do you have any specific idea on why debhelper 7 does not run on
> Fremantle SDK (I suppose there's no need to run it on the device)? Is
> there any chance at all to get it working, by upgrading perl or some
> other magic?
Yes, there is a chance, but it is not p
ext Anderson Lizardo writes:
> If you have plans to begin enabling auto-optification by default,
> please inform us here on the list so we can begin adding the
> debian/optify file to avoid optifying packages that were manually
> optified by other means (e.g. python packages).
If a package alre
1 - 100 of 441 matches
Mail list logo
