Re: Moving package with quilt to new upstream version
Il giorno mer, 15/09/2010 alle 13.14 -0300, Henrique de Moraes Holschuh ha scritto: [...] > "man quilt" explains it all. thanks > IMO, you should try to get yourself better acquinted with quilt before > using it, or you can end up with a mess. Right. That's why I am testing this process while upstream only produced and rc version. Thanks, Giuseppe -- 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/1284568082.4749.190.ca...@scarafaggio
Moving package with quilt to new upstream version
Hi all, I have recently packaged hylafax 6.0.4-10 using quilt. Now I am moving to a new upstream release 6.0.5 and I am trying to update my package following http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream but I failed to it properly. What I do: 1. untar new upstream release 6.0.5 2. remove its debian directory 3. untar hylafax_6.0.4-10.debian.tar.gz into new source root 4. change debian version in changelog via dch 5. execute "while quilt push; do quilt refresh; done" here it fails with message "No patches in series" because it doesn't look for debian/patches/series but only for patches/series. If I change to the debian directory and then issue the same command, I get all patches rejected because quilt is looking for files to patch in debian directory instead of its parent. So, how do you move your quilt patches to a new upstream release? Thanks, Giuseppe -- 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/1284566327.4749.174.ca...@scarafaggio
Re: [RFC] New hylafax package: getting rid of the twin directories structure
Il giorno lun, 11/05/2009 alle 15.06 +0200, Marco d'Itri ha scritto: [...] > > With 2.6 kernels, we may use the "bind" option in order to mount > > a /etc/hylafax on /var/spool/hylafax/etc. So, I am finally moving to > > this new configuration, but I have a few concern that I would like to > > share, looking for suggestion. > I am sure that there is a good reason, but what prevents you from making > the program just use /etc/hylafax? chrooting? yes, daemons are chrooted in /var/spool/hylafax -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
[RFC] New hylafax package: getting rid of the twin directories structure
Hi all, I am packaging the new hylafax version, 6.0. Now that Lenny has been released I am taking squeeze as base distribution, but I would also give support to older distribution. Starting from sarge, all users where strongly advised to update to 2.6 kernel; etch and lenny started delivering packages that do not work with kernel 2.4. Now I believe that 2.4 kernel is no more supported. Current hylafax package requires a lot of configuration files in a specific directory, i.e. /var/spool/hylafax/etc, while Debian keep configuration files in /etc. So, the init.d script for hylafax, clone the /etc/hylafax/ directory and copy everything on /var/spool/hylafax/etc. This is a problem because of duplicated data and because it require a method to keep both directories in sync. Keeping all conffiles only in /var/spool/hylafax/etc is against Debian policy, keeping all of them in /etc/hylafax won't work for hylafax daemons chrooted in /var/spool/hylafax/. Symbolic links doesn't solve the problem either. With 2.6 kernels, we may use the "bind" option in order to mount a /etc/hylafax on /var/spool/hylafax/etc. So, I am finally moving to this new configuration, but I have a few concern that I would like to share, looking for suggestion. First of all, hylafax package support many configuration: you may start all daemons from init.d script, or you may have a few othe started via inittab, or you may have some of them started via inetd. All configuration may be mixed. Currently, both directories are kept update by the script in /etc/init.d. If any daemon is run via inittab or inetd, then they get only the configuration found in /var/spool/hylafax/etc. Currently, the main configuration is in /etc/hylafax. Whenever anything is changed, i.e. using faxadduser, then the command also update /var/spool/hylafax/etc. Option 1. The new way, in my opinion, is to check if any daemon is run via inetd or inittab. If any, then keep the current way. Then check for mount/bind capability, if not preset, then keep the current way. Otherwise backup and remove /var/spool/hylafax/etc while *installing* the new package. Then bind and unbind the new file system when starting and stopping hylafax using init.d script. Option 2. do not backup and remove the old directory so, if any daemon starts via inetd or inittab, they would find a valid configuration. Keep binding and unbinding from the init.d script even if daemons are run via inetd or inittab. Option 3. prompt the user for selecting the preferred way. Option 4. create an option in /etc/defaults/hylafax to make init.d script only bind/unbind, without starting/stopping daemon. This could be useful to people still running daemons via inittab or inetd, but willing to use the bind/unbind way. In any case, when this package is installed (not upgraded), follow Option 1. Any suggestion? Thanks, Giuseppe -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#525481: Wrong usage of gnome proxy settings
Il giorno sab, 25/04/2009 alle 10.15 +0200, Mike Hommey ha scritto: > On Sat, Apr 25, 2009 at 09:56:54AM +0200, Giuseppe Sacco wrote: > > Hi Mike, > > > > Il giorno ven, 24/04/2009 alle 22.30 +0200, Mike Hommey ha scritto: > > [...] > > > I'm not sure iceweasel uses gnome settings, but uses what gnome exports > > > in the *_proxy environment variable. Can you check what they look like? > > > > giuse...@scarafaggio:~/src/django/mberi$ env | grep prox > > http_proxy=http://192.168.1.53:3128/ > > no_proxy=localhost,127.0.0.0/8,192.168.0.0/16,scarafaggio > > I'm pretty sure iceweasel doesn't support the CIDR notation (e.g. > 127.0.0.0/8). I think iceweasel completely ignore the no_proxy variable, since this does not work either: $ killall iceweasel $ env no_proxy=127.0.0.1,localhost,127.0.0.0/8,192.168.0.0/16,scarafaggio \ iceweasel http://127.0.0.1/ still load the web page via proxy server. Bye, Giuseppe -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
new hylafax in experimental
Hi all, a new hylafax version is going to be released in the next few weeks. I have therefore uploaded a new version 4.3.1~rc3-1 to experimental, since I don't want to mess with the current version in etch, 4.3.0-9. Please test the new version, so that we may understand if 4.3.1 is ready to be included in etch. Thanks, Giuseppe signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: how to execute a data-file's preferred app from the cmd-line?
Il giorno gio, 29/06/2006 alle 16.44 -0500, Gunnar Wolf ha scritto: > Török Edvin dijo [Thu, Jun 22, 2006 at 09:23:32AM +0300]: > > >kfmclient exec foobar.odt > > What if I am using gnome? Should I use gnome-open then? > > Ah, and how do I determine if I am running gnome or kde? > > (look in the output of `ps x'?) > > Don't. The machine might be multiuser (i.e. LTSP). Its users will > have different sessions. Or you may use the environment variable DESKTOP_SESSION.
Re: Debian Light Desktop - meta package
Il giorno gio, 13/04/2006 alle 11.46 +0200, Eduard Bloch ha scritto: [...] > > - evince > > As other pointed out, does basically the same job as xpdf but pulls half > of the Gnome. If you just want to display PDF files then probably xpdf is a better option, but Evince has a really nice feature: it show TIFF multipage. This is the *only* free software program I am aware of, that can show multipage tiff file. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Evolution Contacts
Il giorno mer, 02/11/2005 alle 09.15 +, Ross Burton ha scritto: > On Tue, 2005-11-01 at 15:14 -0500, Alejandro Bonilla wrote: > > Someone sent an email I dunno if here or in evolution-hackers ML but I also > > lost All my contacts after upgrading yesterday in Sid! ;0( > > Close Evolution and killall evolution-data-server-1.4, then restart > Evolution. That *should* work. I think it is bug #336761, #336897. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Alioth Project Approved - and now?
Il giorno lun, 27/06/2005 alle 17.43 +0900, Miles Bader ha scritto: > Lionel Elie Mamane <[EMAIL PROTECTED]> writes: > >> Hmmm, why SSH1 and even telnet and not SSH2? > > > > You misread: There is NO telnet. As for SSH2, it works fine, but SSH1 > > doesn't work. Probably a typo . > > Does anyone still use ssh1? It seems quite common for it not to be > supported these days... I do. I use ssh1 since it is very quick compared to ssh2. I use it when accessing slow virtual machines (bochs) and when connecting from PDA devices. Bye, Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Greylisting for @debian.org email, please
Il giorno dom, 19-06-2005 alle 19:19 +0200, Josselin Mouette ha scritto: > Le dimanche 19 juin 2005 à 19:11 +0200, Frans Pop a écrit : > > If I am blocked by something like SORBS when answering installation > > reports or something like that, I will sometimes resend a mail through my > > ISP, sometimes I just say "@[EMAIL PROTECTED]@ you, if you don't want to > > receive my > > mail, then don't". > > Gee, same reaction I suppose. I also have no regret in closing abruptly > bug reports opened by such clueless people. when this happens to me, I send all email to submitter-@bugs.debian.org, since Debian accept my email and will forward it in the right way. Bye, Giuseppe
Re: And now for something completely different... etch!
Il giorno gio, 09-06-2005 alle 19:06 +0200, Frans Pop ha scritto: > On Thursday 09 June 2005 18:45, Marco d'Itri wrote: > > On Jun 09, Adrian von Bidder <[EMAIL PROTECTED]> wrote: > > > Dropping 2.4 can easily be done on relatively short notice prior to > > > etch release, so no need to worry about now. > > > > It would be too late, because at that time we would have wasted a > > couple of years trying to support them. > > This kind of decision should be taken early in the development cycle. > > Making the decision early would also help d-i development as we could then > start cleaning e.g. keyboard selection (and console-data). > Being able to rely on sysfs being present would also simplify hardware > detection in some cases. Right, this would really simplify d-i development. My personal opinion is that 2.6.8 isn't enought mature to be used on server installation with multidisk, lvm and XFS. But, when Etch will be released, we will probably have 2.6.25 or such available. I think, in this case, 2.6 could really be offered as a complete replacement for 2.4. Giuseppe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: #284724: Interpretation of NON-BREAK SPACE
Il giorno sab, 12-02-2005 alle 09:43 +, Alastair McKinstry ha scritto: [...] > Does anyone have copies (or pointers to free versions of) SUS and any > rulings on this matter? What are developers opinions on this: should > this be treated as a shell (and other scripting language) bug, ie. > should all characters in the class [:space:] be treated as a token > seperator in shells/languages, or just the ASCII SPACE? I believe that non breaking space is just something related to the layout of a document, so the semantic of a sentence or command including such characters should just tread them as normal spaces. Just my 0,02¤, Giuseppe
Re: NMU for libpaper
Hi Hamish, Il ven, 2004-10-22 alle 15:39, Hamish Moffatt ha scritto: [...] > Rather than NMU just for this bug, you could try to contact the > maintainer again and adopt the package if unsuccessful, or with his > consent. Echelon says Stephen Zander was last seen in early August. Thanks for your suggetions, but I already sent Stephen three messages during the last month. Every message returned because his mailbox is full. Moreover, as you may see from this thread in d-d http://lists.debian.org/debian-devel/2004/08/msg01016.html , he was already contacted here and he never reply. So, you are right: I should adopt the package. Thanks, Giuseppe
NMU for libpaper
It seems that libpaper package is unmaintaned, but i would like to do an NMU using a large patch. The relevant bug report (with patch) is #188899 and this would also close hylafax bug report #269184. Does anyone see any problem in applying this patch? Bye, Giuseppe
Re: debian-security-announce-$lang@lists?
Il Tue, Aug 13, 2002 at 09:23:57PM +0200, Martin Schulze ha scritto: [...] > Currently, all DSAs are released via mail in english on > [EMAIL PROTECTED] and copied to www.debian.org > afterwards, where they will be picked up by seven[1] fellow translators Just for the records. From this morning we also have Italian :-) > 1. Danish, French, German, Japanese, Portuguese, Spanish and Swedish Bye, Giuseppe
