Re: Bug#602511: Fwd: Re: upstart support for nodm
Hi, Am Donnerstag, den 07.07.2011, 01:35 +0200 schrieb Enrico Zini: > On Tue, Feb 08, 2011 at 11:31:40PM +0530, Joachim Breitner wrote: > > > But then I find that dh_installinit would not install the regular init > > script if an upstart job is present, uses a compatibility link > > in /etc/init.d and adds a dependency on upstart-job, which seems to be > > only provided by upstart. I’m not sure if we want to force all users of > > nodm to switch to upstart – or is there an alternative? > > > > Enrico, what is your level of caring about nodm ATM? > > It goes in bursts, mainly depending on when I have customers who would > like me to work on it. > > I've just finished a rewrite so that nodm is now a real package manager, > tomorrow I'll do some real world testing and if all goes well, an upload > of the new version to unstable. Great, I always found nodm a far better approach than dpkg! (Sorry, CNR ;-)) > On Mon, Feb 14, 2011 at 10:06:45AM -0800, Steve Langasek wrote: > > > Also, I strongly counsel *against* shipping this, or any, upstart job in a > > Debian package until this policy bug is *fixed*. The conversation is > > ongoing, and deploying such upstart jobs now realistically just runs the > > (very high) risk that you'll have more work to do on your package later once > > the policy interfaces are refined and implemented. > > That is fine with me, I'll do that. > > I must admit that I've just found myself in a rather intense WTF moment, > after finding out that the nodm package from the master branch was > depending on upstart and not shipping an init.d file. > > I'm now going to move the upstart work that has been committed (thank > you for it, though!) to a separate "upstart" branch, and I'll upload > without it for now. Sounds good to me, and thanks for the ongoing maintenance. BTW, since I stopped using the Freerunner and, after your rewrite (which I appreciate!), don’t really know any of the nodm code, would you mind taking over maintenance completely? I doubt that I add much value here any more. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
unsuscribe
Nuova grafica e nuove funzionalità! Crea subito Gratis la tua nuova Casella di Posta Katamail -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/41765.1310024...@katamail.com
TeX packages
Hello, Is it possible to run mktexlsr and updmap-sys (and, possibly, other TeX things) just once when installing or removing packages which need to run them in postinst/postrm? I've been trying to remove some not-really-needed latex-cjk-* packages to minimize my old laptop's system installed size, and the removal process appeared to run for ages... -- WBR, Andrew signature.asc Description: PGP signature
Re: How to warn user about breaking change in location of runtime file?
Hi Jonathan, Thanks for comprehensive and very helpful answer! [top-posted because it was difficult to find something valueless to skip for getting rid of reply scrolling] On 06.07.2011 10:22, Jonathan Nieder wrote: > Hi, > > Leonid Borisenko wrote: > >> I want to move socket location from '/run/uwsgi//socket' to >> '/run/uwsgi/app//socket'. If user relied on socket location, >> then upgrade of uwsgi package will require manual editing of frontend >> server configuration. Until editing (and reloading of upstream server), >> behavior of the whole server stack will be broken. > [...] >> I've asked about it in debian-mentors [1]. In short: I've asked for >> advice in choosing between: 1) mentioning of change in NEWS.Debian, 2) >> providing debconf note, 3) both 1. and 2., 4) something else. I've >> recieved no answers though. > > uwsgi was never in a stable release and users have only had a few > weeks to get used to the current behavior, so I'd suggest mentioning > the change and what configuration change might be needed in > NEWS.Debian and leaving it at that. > > Still, I like this question so much that I think it deserves a more > thorough answer. So imagine that the old socket location had been > used for a longer period; what could you do? Just mentioning the > change in NEWS is not so pleasant, since it requires action on the > part of the sysadmin. In that case, I believe your best option would > be to provide a symlink in /run/uwsgi//socket to the new > location and file a bug against the release-notes package to document > that this symlink would disappear in (next Debian release)+1. > > In some configurations, a debconf note blocks the installation until a > human has acknowledged it, which might seem like an appealing feature. > NEWS.Debian.gz entries work even better (if apt-listchanges is > installed), since they are shown before the preconfiguration stage of > an upgrade begins, allowing the administrator to back out if it is not > a good time. Once an upgrade begins, they do not interfere, and after > the upgrade, they are easy to inspect automatically or by hand. The > reasons described at [*] also apply, of course. > > Thanks for your work, and hope that helps. > Jonathan > > [*] > http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#s6.5.1 > > -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1589df.5000...@gmail.com
Re: ESA Summer of Code in Space 2011
On Thu, 07 Jul 2011, Paul Wise wrote: > On Wed, 2011-07-06 at 20:12 -0300, Henrique de Moraes Holschuh wrote: > > On Thu, 07 Jul 2011, Paul Wise wrote: > > > Does Debian have any space related software? > > > > Yes. > > Do you know of any specific packages? apt-cache shows a lot of them, keywords "orbital", "celestial", "space", "orbit". And there is also octave and R, plus the numbercrunching libraries like ATLAS. > > There is this: > > http://sophia.estec.esa.int/socis2011/org_admin_mentor_agreement > > > > 3. INDEMNITY [..] > > A similar clause is present in the Google Summer of Code. In fact the > SOCSIS one is a word-for-word copy with s/Google/SOCSIS (wdiff below). I looked for it before to posting, and didn't manage to find it. My bad. > http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2011/mentoragmt > Are you suggesting that Debian should pull out of the Google Summer of > Code? or that it is OK for Debian to also join the SOCSIS? Well, ESA can't be a more high-profile target [to patent trolls and submarine patents] than google. If the DPL and the SPI lawyers are okay with it for GSOC, I suppose there is no reason to not also join the SOCSIS. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110707104135.ga24...@khazad-dum.debian.net
Re: [Soc-coordination] ESA Summer of Code in Space 2011
On Thu, Jul 07, 2011 at 07:41:35AM -0300, Henrique de Moraes Holschuh wrote: > On Thu, 07 Jul 2011, Paul Wise wrote: > > On Wed, 2011-07-06 at 20:12 -0300, Henrique de Moraes Holschuh wrote: > > > On Thu, 07 Jul 2011, Paul Wise wrote: > > > > Does Debian have any space related software? > > > > > > Yes. > > > > Do you know of any specific packages? > > apt-cache shows a lot of them, keywords "orbital", "celestial", "space", > "orbit". And there is also octave and R, plus the numbercrunching > libraries like ATLAS. I saw this stuff like 1 week ago [0], but IMHO it isn't very well suited for what we do in Debian and upstream projects should apply directly. After all, the code is supposed to go to their repository so you need to work directly with those upstream and stuff will flow into Debian later. However: > > Are you suggesting that Debian should pull out of the Google Summer of > > Code? or that it is OK for Debian to also join the SOCSIS? > > Well, ESA can't be a more high-profile target [to patent trolls and > submarine patents] than google. If the DPL and the SPI lawyers are okay > with it for GSOC, I suppose there is no reason to not also join the SOCSIS. If you think in Debian we have some project that could benefit of this, please feel free to apply and do all the organization stuff here independently of the GSoC stuff. Ana -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110707114918.ga20...@pryan.ekaia.org
Re: TeX packages
On Thu, Jul 07, 2011 at 11:53:17AM +0300, Andrew O. Shadoura wrote: > Is it possible to run mktexlsr and updmap-sys (and, possibly, other > TeX things) just once when installing or removing packages which need > to run them in postinst/postrm? I've been trying to remove some > not-really-needed latex-cjk-* packages to minimize my old > laptop's system installed size, and the removal process appeared to run > for ages... I think these processes could be moved over to dpkg triggers, it just takes someone to do the work. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110707122629.GA24304@pris
Re: [Soc-coordination] ESA Summer of Code in Space 2011
Maybe, some Remote Sense software are related with it. These RS software are maintained by DebianGIS team. -- YunQiang Su -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKcpw6XVxajhqo6uiZewKRVxgg46fpFvTNrGR=ito=dt98o...@mail.gmail.com
Re: ESA Summer of Code in Space 2011
On Thu, Jul 07, 2011 at 07:41:35AM -0300, Henrique de Moraes Holschuh wrote: > > Do you know of any specific packages? > > apt-cache shows a lot of them, keywords "orbital", "celestial", "space", > "orbit". And there is also octave and R, plus the numbercrunching > libraries like ATLAS. I'd also like to advertise http://blends.alioth.debian.org/science/tasks/astronomy http://blends.alioth.debian.org/science/tasks/astronomy-dev here. Perhaps some packages are missing in the task and should be added. Any volunteer to check? > Well, ESA can't be a more high-profile target [to patent trolls and > submarine patents] than google. If the DPL and the SPI lawyers are okay > with it for GSOC, I suppose there is no reason to not also join the SOCSIS. Would be cool Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110707132734.gb5...@an3as.eu
Re: [Soc-coordination] ESA Summer of Code in Space 2011
On Thu, Jul 07, 2011 at 01:49:18PM +0200, Ana Guerrero wrote: > > If you think in Debian we have some project that could benefit of this, > please feel free to apply and do all the organization stuff here independently > of the GSoC stuff. There might be a chance for a Debian Astronomy Blend (feel free tp find a better name) as spin-off from Debian Science. In the long run this could be advertised as an ESA default system. However, this is more work than just a SoC project and it should be only started if there are engaged people who want to put some effort into this. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110707133207.gc5...@an3as.eu
Re: TeX packages
On Thu, Jul 07, 2011 at 01:26:29PM +0100, Jon Dowland wrote: > On Thu, Jul 07, 2011 at 11:53:17AM +0300, Andrew O. Shadoura wrote: > > Is it possible to run mktexlsr and updmap-sys (and, possibly, other > > TeX things) just once when installing or removing packages which need > > to run them in postinst/postrm? I've been trying to remove some > > not-really-needed latex-cjk-* packages to minimize my old > > laptop's system installed size, and the removal process appeared to run > > for ages... > > I think these processes could be moved over to dpkg triggers, it just takes > someone to do the work. I think, whatever can be covered by triggers, already is. tex-common has trigger support for some time now. Hauke -- .''`. Jan Hauke Rahmwww.jhr-online.de : :' : Debian Developer www.debian.org `. `'` Member of the Linux Foundationwww.linux.com `- Fellow of the Free Software Foundation Europe www.fsfe.org signature.asc Description: Digital signature
Re: [Soc-coordination] ESA Summer of Code in Space 2011
I am interesting in to package Opticks - a remote sense software. or Maybe i18n even, if time is enough. Will we (Debian) apply as a mentor organization ? PS: add cc to debian-...@lists.debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e15d5ea.9040...@gmail.com
Re: Bug#602511: Fwd: Re: upstart support for nodm
On Thu, Jul 07, 2011 at 09:36:38AM +0200, Joachim Breitner wrote: > BTW, since I stopped using the Freerunner and, after your rewrite (which > I appreciate!), don’t really know any of the nodm code, would you mind > taking over maintenance completely? I doubt that I add much value here > any more. I rather you studied the new code and gave a hand :P It's fine, I don't mind taking over maintenance completely, only it's going to be in bursts as it's been so far, and having at least a comaintainer who can look after minor packaging issues or simple BTS interaction would be a good idea. It doesn't have to be you, of course. Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini signature.asc Description: Digital signature
Re: TeX packages
Jan Hauke Rahm wrote: On Thu, Jul 07, 2011 at 01:26:29PM +0100, Jon Dowland wrote: On Thu, Jul 07, 2011 at 11:53:17AM +0300, Andrew O. Shadoura wrote: Is it possible to run mktexlsr and updmap-sys (and, possibly, other TeX things) just once when installing or removing packages which need to run them in postinst/postrm? I've been trying to remove some not-really-needed latex-cjk-* packages to minimize my old laptop's system installed size, and the removal process appeared to run for ages... I think these processes could be moved over to dpkg triggers, it just takes someone to do the work. I think, whatever can be covered by triggers, already is. tex-common has trigger support for some time now. Hauke I'm not a maintainer but I'd say this. 1) you may do as you said by hand the installer won't mind 2) you could adjust the scripts to check for file existence / newer - the pkg install scripts often have such checks - you can adjust them and it should work fine 3) you could mark effected packages Pre-Depends. however I think your saying each pkg is marked to auto-update (for q/a reasons). it is simply not list aware, there currently isn't a callback to rely on (other than a sleeper that waits for completion conditions). I'm unsure if Pre-Depends is always last on remove / fifo filo I mean. Hope I helped, John -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e15e247.1070...@cox.net
Re: TeX packages
Jan Hauke Rahm wrote: On Thu, Jul 07, 2011 at 01:26:29PM +0100, Jon Dowland wrote: On Thu, Jul 07, 2011 at 11:53:17AM +0300, Andrew O. Shadoura wrote: Is it possible to run mktexlsr and updmap-sys (and, possibly, other TeX things) just once when installing or removing packages which need to run them in postinst/postrm? I've been trying to remove some not-really-needed latex-cjk-* packages to minimize my old laptop's system installed size, and the removal process appeared to run for ages... I think these processes could be moved over to dpkg triggers, it just takes someone to do the work. I think, whatever can be covered by triggers, already is. tex-common has trigger support for some time now. Hauke I'm not a maintainer. I don't see the validity of this response (which I responded to). RE: the request was reduce triggering and the answer suggested only how to add triggering (while not saying how the tail end would be detected) The dpkg-triggers goes beyond being a make(1) compatible process in a very few aspects of it - doesn't it? A make process would guaruntee order while dpkg-triggers leaves "overwritten" requests that "may be activated later" in no documented order. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e15e9e2.1050...@cox.net
Re: TeX packages
John D. Hendrickson and Sara Darnell, le Thu 07 Jul 2011 13:16:18 -0400, a écrit : > Jan Hauke Rahm wrote: > >On Thu, Jul 07, 2011 at 01:26:29PM +0100, Jon Dowland wrote: > >>On Thu, Jul 07, 2011 at 11:53:17AM +0300, Andrew O. Shadoura wrote: > >>>Is it possible to run mktexlsr and updmap-sys (and, possibly, other > >>>TeX things) just once when installing or removing packages which need > >>>to run them in postinst/postrm? I've been trying to remove some > >>>not-really-needed latex-cjk-* packages to minimize my old > >>>laptop's system installed size, and the removal process appeared to run > >>>for ages... > >>I think these processes could be moved over to dpkg triggers, it just takes > >>someone to do the work. > > > >I think, whatever can be covered by triggers, already is. tex-common has > >trigger support for some time now. > > I'm not a maintainer. I don't see the validity of this response (which I > responded to). It's completely valid. He believes it's already implemented fully (and I believe too, actually). > RE: the request was reduce triggering and the answer suggested only how to > add triggering (while not saying how the tail end would be detected) How to add *dpkg* triggering, which is management for triggers, to factorize them. Samuel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110707172313.ga4...@const.famille.thibault.fr
Orphaning some packages...
Hello, My usage of debian a slightly changed during the last 6 months. Im thus about to orphan some of my packages I no longer have any interest, and willl ask from being removed from some "Uploaders" fields. These packages are free for adoption: - magicor - mirage - monster-masher - moodle-debian-edu-theme - planner - qsynth - slashem - vym - gftp - efte - argyll Packages I co-maintain and I will ask for being removed as Uploaders - lisaac - moodle - dvtm My future work will be more focused on the usage of Debian as a server (Web, DBs, Nagios, ) and regarding perl packages. I want to apologize for my quite silent Debian activity during the last 6 months; especially regarding my work as part of the perl team, FD member, AM and admin of collab. I got lot of changes in my life like new job, new flat, ..., all of this in a new country and everything is quite stabilized right now. Take this announce as a "come back" with new motivation :) Im incrementaly managing my time for getting back to a normal debian activity. Greetings, -- Xavier Oswald GNU/Linux Debian Developer - http://www.debian.org/ GPG key ID: 0x464B8DE3 signature.asc Description: Digital signature
Re: Orphaning some packages...
On Thu, Jul 7, 2011 at 7:13 PM, Xavier Oswald wrote: > Im thus about to orphan some of my packages I no longer have any interest, and > willl ask from being removed from some "Uploaders" fields. > > These packages are free for adoption: > - magicor ... > - monster-masher ... > - slashem ... Perhaps the Debian games team can take these, is anyone from the team particularly interested? -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6H4Bx3q9hCo9U4ERdt-Nqg8+J7Y_mRWzP=mbwobce1...@mail.gmail.com
Re: TeX packages - side topic make and sleep
.TH SHMAKE 1 "06 Jul 2011" "\fBshmake\fR 1.0" "User Commands" .SH NAME shmake \- easily template for dependancy situations, runs commands accordingly .SH SYNOPSIS \fBshmake\fR [options] File [label] .SH DESCRIPTION Runs each left command in File when all files on it's right are ready (touched). .LP This program provides any commands with a quick and simplest to use automatic dependancy resolver. It has a as few features deemed needed and is end-point alterable for spot needs / plain text. .LP For ordering and pausing commands which beget dependant needs. For programs who's flow needs to be plain to see, easily modifiable, and automatically resolved. .LP File File is simple lr format. See examples of the simple LR File below. .LP .TP \fB-h\fR -\fB-help\fR .TP \fB-n\fR show what commands would launch next but don't launch .TP \fB-q\fR quiet .TP \fB-s\fR stop if any dep is unmet .TP \fB-w\fR seconds to wait between scans label show if label is ready. if it's an aside and is, launch it (for item readiness check or asides) .LP Default is to scan File until goal completion (it pauses between scans). If there is no set goal it continually checks up on / runs commands if needs be. .LP File is a 2 column list of steps toward a goal (see examples further below). .IP lefta command label which is invoked when right is met .IP right a list dependent commands / labels to wait for .IP goalif on left, right determines success and quit .LP Detours. One of these 'fakes' can be pre-pended to any label: .IP % inv, makes prepended item 'invisible' .IP - false, always missing and never runs .IP ^ nodate, no updating / ignore date .IP @ aside, launches only as aside (left only, see below) .IP # comment on rest of line .SH MANUAL The LR list is read in order, launching each left who's right is ready. If there is no complete "goal" it scanning starts again from top. .LP Goals. A left label "goal" is special. When it's conditions are met \fBshmake\fR quits with success. "goal" can appear multiple times and have differing depends. .LP \fBshmake\fR(1) prints progress while running that is verbosely self explanitory. .LP Command. If label.sh exists it will be invoked as command. If not, 'File.sh' is invoked with parameter "label". That's File from '\fBshmake\fR File'. .LP Dependancies. After any command 'label' runs it will (should) 'touch label' to indicate success. These label files are used to determine what is finished. That is how "right becomes met" / ready. .LP Auto Updating. If any dependant of a command is \fBnewer\fR(1) than command command then command is invoked [to update]. This solves another difficult dependancy problem of which needs / don't need reworking. .LP Stopping. If scanning needs to stop \fBtouch\fR(1) file "stop" and it will stop normally when the current label finishes. Ctrl-C if you must. .LP Format. Any labels at the start of line are left and all labels until the next left are a right. .LP Other possible 'detour' modifies do not really add convenience because they are better achieved with simpler L-R notation. If I missed something make has this needs let me know ! .LP Re-Scan. If File changed while \fBshmake\fR(1) is running \fBshmake\fR uses it. This is for allowing changes that shouldn't want quitting out. Just keep in mind if saving and editing while it's running please. .LP The aside. seeing shdeps \fB--help\fR, 'shdeps file fun' will show if fun is is ready and quit. But if it's an aside, @fun, then shdeps first launches it (asides never launch otherwise). see example above. @ used on the right are ignored. .LP \fBmake\fR(1) uses first left as goal and can't change goals. .SH EXAMPLES COMMANDSFILES / DEPENDENCIES .LP spool pages.spurious .LP chapspool summary.pg .LP doitprintready chap .LP - .LP fun1 collect_sounds .LP fun2 collect_sights .LP fun3 fun2 find_map .LP fun4 fun3 fun1 request .LP goal fun4 visited .LP .SH USES As a precaution and convenince for developing anything with steps that may change or be partially replaced. For preventing static dummy checks from creeping into worker steps (ruinous if design alters). For programs wishing to utilize dependency solving without need of redesigning it. .LP \fBshmake\fR is useful when .TP \fB-o\fR when there are many steps which may not be complete and redoing done steps is avoided (ex. printing chapters of a book with a distiller script) .TP \fB-o\fR there is no order commands except to work with current status .SH FILES example.deplist.\fBshmake\fR example.sh.\fBshmake\fR .SH BUGS please mail any bugs you find I'd like \fBshmake\fR to be simple for everyone .SH LICENSE pre-release; not yet licensed .SH VERSION Version 0.01 .SH AUTHOR John D. Hendrickson, deb...@sourceforge.net .SH SEE ALSO \fBmake\fR(1) Samuel Thibault wrote: John D. Hendrickson and Sara Darnell, le Thu 07 Jul 2011 13:16:18 -0
Please keep mobile-broadband-provider-info (and other similar packages) updated in stable
Debian package mobile-broadband-provider-info contains database of mobile broadband service providers It would be good to keep these kind of packages current in Debian stable, too. I think it satisfies some criteria for squeeze-updates suite ( copied from http://www.debian.org/News/2011/20110215 ) This suite will contain updates that satisfy one of the following criteria: * The update is urgent and not of a security nature. Security updates will continue to be pushed through the security archive. Examples include packages broken by the flow of time (c.f. spamassassin and the year 2010 problem) and fixes for bugs introduced by point releases. * The package in question is a data package and the data must be updated in a timely manner (e.g. tzdata). * Fixes to leaf packages that were broken by external changes (e.g. video downloading tools and tor). * Packages that need to be current to be useful (e.g. clamav). Alternately point releases can be used for this. Backporting these kind of packages shouldn't be necessary. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110707182442.GA2536@lisko
Re: Pre-Depends on remove - what order?
Question. Pre-Depends should, by "grading" float to the top for a dpkg install list. What about remove? Is Pre-Depends guaranteed to be first, last, or neither on remove? Personally? I sometimes get problems sometimes with dpkg's trying to install things with allot of depnds before things with few depends (though all if successful may be satisfied and a well chosen list). I think "guarantee" as to order is a bit stiff of a word with the current "grading system" but I'd like to hear comments on that too. Any help or comments please? One "remove" and "pre-depends" especially ? Thanks, John -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e160310.3010...@cox.net
Re: Orphaning some packages...
Hi Xavier, On Donnerstag, 7. Juli 2011, Xavier Oswald wrote: > Im thus about to orphan some of my packages I no longer have any interest, > and willl ask from being removed from some "Uploaders" fields. [...] > - moodle-debian-edu-theme Actually I wonder whether this package should go, it has not been used much in Debian Edu TTBOMK, cc:ing the list for more input. > Take this announce as a "come back" with new motivation :) > Im incrementaly managing my time for getting back to a normal debian > activity. \o/ Enjoy your new focus! cheers, Holger -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201107072351.07973.hol...@layer-acht.org
Re: Orphaning some packages...
Hi, > - gftp I would like to take care about gftp. Co-maintainers or sponsors are welcome. Cheers, Cleto. signature.asc Description: OpenPGP digital signature
Re: TeX packages - side topic make and sleep
Dear John, dear Sara, thank you for contributing the manual pages. Having translated several manpages last year I am used to some licence statement at the very beginning of the manual, e.g.: .\" Copyright (c) 1995 Michael Chastain (m...@shell.portal.com), 15 April 1995. .\" .\" This is free documentation; you can redistribute it and/or ... (I copied it from bdflush.2). Kind regards, Martin -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1632e9.7060...@gmx.de
Re: TeX packages
Hi everyone,
I am the one who implemented triggers for tex-common, one of the maintainers.
On Do, 07 Jul 2011, Andrew O. Shadoura wrote:
> Is it possible to run mktexlsr and updmap-sys (and, possibly, other
> TeX things) just once when installing or removing packages which need
> to run them in postinst/postrm? I've been trying to remove some
> not-really-needed latex-cjk-* packages to minimize my old
> laptop's system installed size, and the removal process appeared to run
> for ages...
Can you provide a log showing what went wrong in your case?
On Do, 07 Jul 2011, Jon Dowland wrote:
> I think these processes could be moved over to dpkg triggers, it just takes
> someone to do the work.
As Hauke said, updmap and mktexlsr is already handled by triggers.
And all TeX related packages I know of already use dh_installtex
so they should be using trigger, too.
Sometimes we *have* to run these commands out of trigger sequenece
right in the postinst, esp when formats are concerned.
With TL2011 updmap runs will be *MUCH* faster as we switched to
a perl script that runs in a fraction of the time of the old
shell script.
Best wishes
Norbert
Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan TeX Live & Debian Developer
DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
HUTTOFT (n.)
The fibrous algae which grows in the dark, moist environment of
trouser turn-ups.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110707224115.gb30...@gamma.logic.tuwien.ac.at
Re: TeX packages - side topic make and sleep
Martin Eberhard Schauer wrote: Dear John, dear Sara, thank you for contributing the manual pages. Having translated several manpages last year I am used to some licence statement at the very beginning of the manual, e.g.: .\" Copyright (c) 1995 Michael Chastain (m...@shell.portal.com), 15 April 1995. .\" .\" This is free documentation; you can redistribute it and/or ... (I copied it from bdflush.2). Kind regards, Martin It was supposed to have a quick introduction so as not to bother those who weren't interested. (my mouse button clicks itself at times) "a make that sleeps" I wrote the tiny script not planning on distributing it. It is GPL or any licence debian compat you like. Enjoy! BTW I just wrote it a week ago for testing sh v. make in some situations, it's alpha just like it says :) Jan had been right that a maintainer could solve the Tex issue using "triggers" with maintainer class efforts (I'm unsure the person was asking for a fix or a long term maintainer sol'n actually) Thanks much hope it was no bother, John -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e165415.1040...@cox.net
Re: TeX packages - side topic make and sleep
Martin Eberhard Schauer wrote: Dear John, dear Sara, thank you for contributing the manual pages. Having translated several manpages last year I am used to some licence statement at the very beginning of the manual, e.g.: .\" Copyright (c) 1995 Michael Chastain (m...@shell.portal.com), 15 April 1995. .\" .\" This is free documentation; you can redistribute it and/or ... (I copied it from bdflush.2). Kind regards, Martin (only because license was mentioned) I wrote the tiny script not planning on distributing it. It is GPL or any licence debian compat you like. Enjoy! It was supposed to have a quick introduction so as not to bother those who weren't interested. (my broken mouse button clicks itself at times) "a make that sleeps" I wrote it a week ago for testing sh v. make in some situations - it's alpha just like it says :) Jan had been right that a maintainer could solve the Tex issue using "triggers" with maintainer class efforts (I'm unsure the person was asking for a fix or a long term maintainer sol'n actually) Thanks much hope it was no bother, John -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e1661b2.2090...@cox.net
Re: TeX packages
Hello, On Fri, 8 Jul 2011 07:41:15 +0900 Norbert Preining wrote: > On Do, 07 Jul 2011, Andrew O. Shadoura wrote: > > Is it possible to run mktexlsr and updmap-sys (and, possibly, other > > TeX things) just once when installing or removing packages which > > need to run them in postinst/postrm? I've been trying to remove some > > not-really-needed latex-cjk-* packages to minimize my old > > laptop's system installed size, and the removal process appeared to > > run for ages... > Can you provide a log showing what went wrong in your case? Nothing went wrong, it was just doing mktexlsr/updmap-sys after each package's removal. And no, I have no log, unfortunately :( > On Do, 07 Jul 2011, Jon Dowland wrote: > > I think these processes could be moved over to dpkg triggers, it > > just takes someone to do the work. > As Hauke said, updmap and mktexlsr is already handled by triggers. > And all TeX related packages I know of already use dh_installtex > so they should be using trigger, too. > Sometimes we *have* to run these commands out of trigger sequenece > right in the postinst, esp when formats are concerned. > With TL2011 updmap runs will be *MUCH* faster as we switched to > a perl script that runs in a fraction of the time of the old > shell script. Well, I think I need to upgrade the packages and to try to reproduce the situation. -- WBR, Andrew signature.asc Description: PGP signature
