Bug#1037878: ultracopier: diff for NMU version 2.2.6.0-1.1
Thanks, much appreciated. Feel free to upload it right away. Best regards, Thomas On 10 September 2023 09:12:35 WEST, Marcos Talau wrote: >Control: tags 1037878 + patch >Control: tags 1037878 + pending > > >Dear maintainer, > >I've prepared an NMU for ultracopier (versioned as 2.2.6.0-1.1) and >uploaded it to DELAYED/2. Please feel free to tell me if I >should delay it longer. > >Regards. >
Bug#1037878: Processed: tagging 1037878
Unfortunately I won't be able to do it until August but anyone feel free to do an NMU. My apologies. Best regards, Thomas On 21 July 2023 07:04:57 GMT+08:00, alpha_one_x86 wrote: >Fixed into the last version, please update to Ultracopier 2.2.6.7
Bug#937437: pyfeed: Python2 removal in sid/bullseye
Hi Moritz, I've filled #962985 and #962986. I don't see why these library packages should be kept without reverse dependency. Best regards, Thomas.
Bug#735793: urwid-satext: FTBFS: dpkg-source: error: unrepresentable changes to source
Control: tags 735793 + pending I pushed a fix in the git repository. Unfortunately I won't have access to my gpg key for a few days so I can't upload the result. I notified my co- maintainer and I expect him to do an upload very soon but in the worst case I'll do it myself in about a week. Best regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735813: salutatoi: FTBFS: dpkg-source: error: unrepresentable changes to source
Control: tags 735813 + pending I pushed a fix in the git repository. Unfortunately I won't have access to my gpg key for a few days so I can't upload the result. I notified my co- maintainer and I expect him to do an upload very soon but in the worst case I'll do it myself in about a week. Best regards, Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722485: [Pkg-dspam-misc] Bug#722485: dspam: Same problem with stable (3.10.1+dfsg-11) and testing (3.10.2+dfsg-11) versions
Le vendredi 1 novembre 2013 11:24:34 Gabriel Francisco a écrit : Package: dspam Version: 3.10.2+dfsg-11 Followup-For: Bug #722485 Dear Maintainer, how are you? I'm fine although not much available right now, thank you for asking :) Thank you for reminding me about this issue. I know what is the root of the problem and had already attempted to make a fix but I failed to understand all the interaction of the lines I wrote with the rest of the code. The problem is that the code assume the files are not corrupted and that causes a segfault when it is the case. As to why the file gets corrupted in the first place, it's more difficult to understand. If you find that the problem always appear after the same number of email received that would give me a big clue but if the number is fluctuating that could just be some race condition. At least for the immediate problem the problem is known and it is quite easily fixable. However, upstream development seems rather dead and I don't have much time to look into it right now (I can't promise any deadline). Furthermore, I don't think it is good to fix everything on Debian side, even if it's critical bug. I'll check with upstream if someone is still around but if not I'll write a note recommending to switch away from dspam. Best regards, Thomas Preud'homme -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722484: Bug#726138: dspam css file size dramatically increased after upgrade
Given the problem with the last upload, I'll revert it for now and see how to solve the problem without breakage. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722484: Info received (libdspam7-drv-hash segfaults since 3.10.2+dfsg-10)
Control: reopen 722484 m...@blackshift.org Le lundi 7 octobre 2013 23:01:47, vous avez écrit : Hello I've deleted /var/spool/dspam/data and let dspam deliver a mail, that produces this backtrace: #0 0xb6f118ec in raise () from /lib/arm-linux-gnueabi/libpthread.so.0 No symbol table info available. #1 0xb6a5acf4 in __aeabi_ldiv0 () from /usr/lib/arm-linux-gnueabi/dspam/libhash_drv.so No symbol table info available. #2 0xb6a59b9c in _hash_drv_seek (map=map@entry=0xb57073d8, offset=offset@entry=16147856, hashcode=optimized out, flags=flags@entry=1) at hash_drv.c:1194 header = optimized out rec = optimized out fpos = optimized out iterations = 0 Ok, this bug was very likely introduced with the patch I made to handle corrupted css file. Unfortunetely I don't have the time to fix the patch now. I'm very busy for a few weeks but I'll try to take a look at it as soon as possible. Best regards. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722484: Info received (libdspam7-drv-hash segfaults since 3.10.2+dfsg-10)
Le mercredi 9 octobre 2013 14:56:23, vous avez écrit : Yes the bug was introduced between 3.10.2+dfsg-9 and 3.10.2+dfsg-10. As I'm running -9 without problems. Although the incremental diff from -9 to -10 doesn't look suspicious at the first glance: diff --git a/src/hash_drv.c b/src/hash_drv.c index 349b491..daae2e7 100644 --- a/src/hash_drv.c +++ b/src/hash_drv.c @@ -1187,32 +1187,36 @@ unsigned long _hash_drv_seek( unsigned long fpos; unsigned long iterations = 0; if (offset = map-file_len) return 0; fpos = sizeof(struct _hash_drv_header) + ((hashcode % header-hash_rec_max) * sizeof(struct _hash_drv_spam_record)); According to the backtrace's line number the diff-by-zero should happen here. But the modulo, which is IIRC implemented on ARM as divide/multiply/difference, was here all the time. Was there a compiler change? Maybe some new optimisations brakes the code. Without having looked at the code, I suspect that hash_rec_max is updated from _hash_drv_seek's return value. Since I added a check to detect when the end of file is going to be reached, the function returns 0 in case where it was not the case before. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722057: Bug not fixed in libhash_drv
Control: clone 722057 -1 Control: retitle 722057 libdspam7-drv-hash: dspam segfaults [cssclean] Control: reopen -1 thanks Reopening since only the crash in cssclean was fixed. The sample of dmesg suggest that there is a similar kind of bug in libhash_drv. Sorry for forgetting about this. signature.asc Description: This is a digitally signed message part.
Bug#722485: closing 722485
close 722485 thanks Bug closed in upload of dspam 3.10.2+dfsg-9. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722057: libdspam7-drv-hash: dspam segfaults [libhash_drv on _hash_drv_seek()]
Le samedi 7 septembre 2013 23:46:14 Thomas Preud'homme a écrit : By the way, could you send me that css file so that I can run some test on it? It's better to not send it to the bug log as it might contain some private information. I don't know exactly what is stored in those files so better be safe than sorry. Alright, I managed to reproduce the issue with the file you sent me. From what I could gather quickly in gdb the file is corrupted. Cssclean assume the file respect some constraint but since they are not respected it reads too far in memory which causes the segfault. The bug didn't happened for me when I was running as simple user because it could not read the configuration. I'll forward the problem upstream but given how silent is the development since one year (not a single commit, almost no message on mailing list), I doubt they will fix it. This means I'll probably do the fix myself but I don't have much time right now. Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#722057: libdspam7-drv-hash: dspam segfaults [libhash_drv on _hash_drv_seek()]
Le samedi 7 septembre 2013 09:51:28 Raphael Droz a écrit : I happened to be in a situation where I can't even fully flush the postfix queue without having Dspam to segfault. I end up installing dspam-dbg and gdb and attach to the process [I wasn't able to run the process without the init-script]. Symbols for libdspam7-drv-hash are found in libdspam7-dbg. Could you install it and give me stacktrace you get with it? Thanks a lot signature.asc Description: This is a digitally signed message part.
Bug#722057: libdspam7-drv-hash: dspam segfaults [libhash_drv on _hash_drv_seek()]
Le samedi 7 septembre 2013 21:13:24 vous avez écrit : On Sat, Sep 07, 2013 at 08:33:21PM +0200, Thomas Preud'homme wrote: Le samedi 7 septembre 2013 09:51:28 Raphael Droz a écrit : I happened to be in a situation where I can't even fully flush the postfix queue without having Dspam to segfault. I end up installing dspam-dbg and gdb and attach to the process [I wasn't able to run the process without the init-script]. Symbols for libdspam7-drv-hash are found in libdspam7-dbg. Could you install it and give me stacktrace you get with it? thanks! sadly for now I've postsuper'ed -r ALL emails for now. But I installed libdspam7-dbg, relink postfix to dspam and I will need to wait for another email to come to mailman in order reproduce it. But could you offer me another reliable way to make Dspam dumps its core somewhere automatically instead of this situation where I'm waiting for hours through ssh with $ gdb pid-of-dspam ? Unfortunetely, dspam being setgid, it can't produce coredump on segfault even if coredump are enabled. It seems a call to prctl with option PR_SET_DUMPABLE can remediate this but it means dspam would need to be recompiled. thx Thanks for the bug report and for helping to resolve it. I'll take a look at the CSS problem later. Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#721848: freeciv-client-sdl depends on ttf-arphic-uming
Source: freeciv-client-sdl Version: 2.3.4-1 Severity: serious Justification: §3.5 Dear Maintainer, freeciv-client-sdl depends on ttf-arphic-uming package which is no longer built by fonts-arphic-uming. Please change the dependency to depends on fonts-arphic-uming instead. Best regards. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'oldstable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#709002: [pdfsam] unable to load java after upgrade
Le lundi 20 mai 2013 08:39:20, Marco Righi a écrit : 08:35:09,411 FATAL GuiClient Error: java.lang.NoClassDefFoundError: com/jgoodies/common/base/SystemUtils at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:277) at java.net.URLClassLoader.access$000(URLClassLoader.java:73) at java.net.URLClassLoader$1.run(URLClassLoader.java:212) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:205) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at com.jgoodies.looks.plastic.PlasticLookAndFeel.clinit(PlasticLookAndFeel.j ava:137) at org.pdfsam.guiclient.utils.ThemeUtility.setTheme(ThemeUtility.java:160) at org.pdfsam.guiclient.configuration.Configuration.setLookAndFeel(Configurati on.java:192) at org.pdfsam.guiclient.configuration.Configuration.init(Configuration.java:16 9) at org.pdfsam.guiclient.configuration.Configuration.init(Configuration.java: 54) at org.pdfsam.guiclient.configuration.Configuration.getInstance(Configuration. java:59) at org.pdfsam.guiclient.gui.frames.JMainFrame.init(JMainFrame.java:90) at org.pdfsam.guiclient.GuiClient.main(GuiClient.java:61) To all those who have this problem, it can be avoided by setting the theme (theme) and look and feel (LAF) to 0 in .pdfsam/config.xml. Best regards, Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
Bug#709002: reassign 709002 to libjgoodies-looks-java
Le jeudi 30 mai 2013 15:53:10, tony mancill a écrit : On 05/30/2013 06:47 AM, Thomas Preud'homme wrote: reassign 709002 libjgoodies-looks-java thanks A ClassNotFoundException poped up in pdfjam but it seems to me to be a problem of libjgoodies-looks-java not specifying the jar for libjgoodies-common-java in its classpath. Thank you Thomas, I'll take a look. Great. I've found that lib.common.jar is defined to the correct location of jgoodies-common.jar but it doesn't seem that lib.common.jar is a special property so I have the feeling this is useless. Regards, tony Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#704940: Bug#705552: unblock: subversion/1.6.17dfsg-4+deb7u2
Le jeudi 18 avril 2013 14:38:15, Adam D. Barratt a écrit :
Upstream appear to believe it {does,should}n't -
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704940#32
Oh good. I hadn't time to look at that yet. Should I upload the NMU then?
Regards,
Adam
Best regards,
Thomas
signature.asc
Description: This is a digitally signed message part.
Bug#704940: Bug#705552: unblock: subversion/1.6.17dfsg-4+deb7u2
Le jeudi 18 avril 2013 21:46:18, Adam D. Barratt a écrit :
Control: tags 705552 + confirmed
On Thu, 2013-04-18 at 14:54 +0200, Thomas Preud'homme wrote:
Le jeudi 18 avril 2013 14:38:15, Adam D. Barratt a écrit :
Upstream appear to believe it {does,should}n't -
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704940#32
Oh good. I hadn't time to look at that yet. Should I upload the NMU then?
Please go ahead; thanks.
Done.
Regards,
Adam
Thanks.
Thomas
signature.asc
Description: This is a digitally signed message part.
Bug#702764: libdspam7-drv-pgsql: fails to install: ERROR: language plpgsql already exists
Le lundi 11 mars 2013 07:37:48, vous avez écrit : Package: libdspam7-drv-pgsql Version: 3.10.2+dfsg-7 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. Thanks for the bug report Andreas. Fortunetely, this is already known and there is even an unblock request for that: #702293. Right now I'm just waiting for a confirmation for a new upload. Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#702453: update from squeeze to wheezy breaks because of broken dependencies
tags 702453 + patch
thanks
Hi Thomas,
thanks for your bug report.
Le mercredi 6 mars 2013 19:47:45, Thomas Rechberger a écrit :
Did an upgrade from a default squeeze install to wheezy on Vmware
Workstation 8. The apt-get dist-upgrade process failed during installation
of gir1.2-cogl-1.0 because gir1.0-clutter-1.0 is still installed.
The installation was in a non working state after reboot and lost also the
network connection.
Upgrade process was followed as written in:
http://www.debian.org/releases/wheezy/i386/release-notes/ch-upgrading.de.ht
ml
After dpkg -r --force-depends gir1.0-clutter-1.0 the upgrade was able to
continue.
I suggest that the old gir1.0-clutter-1.0 should be removed by new package
before the new one is installed.
Right. Adding a conflicts should do it. They share one file and should thus
not be unpacked at the same time. See attached patch.
Unfortunetely, I couldn't reproduce the bug on my system so I can't check that
this patch work.
Best regards,
Thomas
diff -Nru cogl-1.10.2/debian/changelog cogl-1.10.2/debian/changelog
--- cogl-1.10.2/debian/changelog 2012-06-21 09:29:54.0 +0200
+++ cogl-1.10.2/debian/changelog 2013-03-10 21:12:33.0 +0100
@@ -1,3 +1,11 @@
+cogl (1.10.2-6.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Add conflict in gir1.2-cogl-1.0 with gir1.0-clutter-1.0 to ensure dpkg
+will not unpack them at the same time (Closes: #702453).
+
+ -- Thomas Preud'homme robo...@debian.org Sun, 10 Mar 2013 21:12:31 +0100
+
cogl (1.10.2-6) unstable; urgency=low
* debian/rules: Set the gles2-libname to libGLESv2.so.2 as shipped by Mesa
diff -Nru cogl-1.10.2/debian/control cogl-1.10.2/debian/control
--- cogl-1.10.2/debian/control 2012-06-21 09:31:14.0 +0200
+++ cogl-1.10.2/debian/control 2013-03-10 12:15:56.0 +0100
@@ -122,6 +122,7 @@
${misc:Depends}
Replaces: gir1.2-clutter-1.0 ( 1.7)
Breaks: gir1.2-clutter-1.0 ( 1.7)
+Conflicts: gir1.0-clutter-1.0
Description: GObject introspection data for the Cogl 1.0 library
This package contains introspection data for the Clutter scene
graph library.
signature.asc
Description: This is a digitally signed message part.
Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user
Le vendredi 8 mars 2013 03:32:29, Stefan Lippers-Hollmann a écrit : Hi On Thursday 07 March 2013, Thomas Preud'homme wrote: tags 655969 + patch thanks Le samedi 26 janvier 2013 19:22:23, Jonathan Wiltshire a écrit : On Wed, Jan 18, 2012 at 01:34:08AM +0100, Stefan Lippers-Hollmann wrote: Thanks for the notice, while I don't exactly share that severity classification (although that is of course covered by the policy text), I'll work on this as soon as possible. Ping? It's been a year, and with a popcon of over 60,000 a *lot* of people are going to start seeing this prompt very soon... What about this patch? It checks whether the md5 of the lirc/hardware.conf conffile installed on the system matches the md5 of the file as modified by the postinst in an automatic install. If that is the case, it sets the file back to the content as shipped in the .deb package so that dpkg doesn't detect the file as modified. I reproduced the bug in pbuilder and the bug disappear when using this patch. […] Thanks for looking into this bug, the patch itself is correct and will avoid the reported piuparts upgrade issue (which is technically RC), so please feel free to upload the NMU (I'd appreciate it). Great, I've been suggested to add a test for the version being upgraded from and testing if the file exist. Once done, I'll upload it (should be today or sunday). Just be aware that it only papers over a larger issue that forces most lircd users actually driving various lirc hardware to reconfigure their config file regardless of this change; please see http://anonscm.debian.org/viewvc/pkg- lirc/lirc/trunk/debian/NEWS?view=mark up or https://lists.debian.org/debian-backports/2012/04/msg00076.html for background information. Ack, the patch is not as useful as it could be. Can't lirc be installed by a Recommends dependency? If yes, it might be that the package is not of interest of the user and this message would thus annoy him/her. If lirc is on the contrary always installed when the user intend to use it, then the best approach is probably to tag it wheezy-ignore. It would be an even smaller change than this patch. For these reasons, I probably would have asked for a wheezy-ignore, in order to get a complete fix into jessie, rather than only fixing the reported bug. However your proposed nmudiff won't interfere with those for-jessie changes and I'd appreciate if you could upload it. If lirc is always installed to be used (never pulled by a Recommends), then tag it wheezy-ignore is probably the best approach indeed. Thanks for the background. Thanks a lot. Regards Stefan Lippers-Hollmann [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=14;bug=655969 Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user
[Note to RT: this is about adding a wheezy-ignore tag for #655969] Le vendredi 8 mars 2013 17:27:33, Stefan Lippers-Hollmann a écrit : Hi On Friday 08 March 2013, Thomas Preud'homme wrote: Le vendredi 8 mars 2013 03:32:29, Stefan Lippers-Hollmann a écrit : […] On Thursday 07 March 2013, Thomas Preud'homme wrote: […] Thanks for looking into this bug, the patch itself is correct and will avoid the reported piuparts upgrade issue (which is technically RC), so please feel free to upload the NMU (I'd appreciate it). Great, I've been suggested to add a test for the version being upgraded from and testing if the file exist. Once done, I'll upload it (should be today or sunday). ack, thanks a lot. Just be aware that it only papers over a larger issue that forces most lircd users actually driving various lirc hardware to reconfigure their config file regardless of this change; please see http://anonscm.debian.org/viewvc/pkg- lirc/lirc/trunk/debian/NEWS?view=mark up or https://lists.debian.org/debian-backports/2012/04/msg00076.html for background information. Ack, the patch is not as useful as it could be. Can't lirc be installed by a Recommends dependency? If yes, it might be that the package is not of interest of the user and this message would thus annoy him/her. If lirc is on the contrary always installed when the user intend to use it, then the best approach is probably to tag it wheezy-ignore. It would be an even smaller change than this patch. [detailed analysis below, feel free to skip this list] The rdepends of lirc, excluding packages built from the lirc source package itself, are: - vdr Video Disk Recorder for DVB cards Recommends: lirc, ttf-bitstream-vera | ttf-freefont vdr has three different ways of navigation (channel selection, lirc is probably the most important one which always works (provided you have properly configured hardware), keyboard based navigation is only possible through selected frontends (e.g. xineliboutput-sxfe, only this special frontend can transport key presses to the vdr dæmon) or web based, through e.g vdr-plugin-live. This makes it, while not mandatory, rather likely that a vdr user also uses lirc hardware; it's probably a wishlist bug that vdr doesn't have an alternative recommends on inputlirc (an alternative lircd implementation) - inputlirc Zeroconf LIRC daemon using input event devices Suggests: lirc, input-utils not pulled in automatically, the suggests looks weird at a first glance (as inputlirc can provide a full lircd replacement for a subset (only event based-) devices also supported by lircd, but the reasons for this are the supporting tools of the lirc package (mostly irw, to generate button -- keycode mappings, eventually irexec). Technically speaking, it might make sense to split out these tools out of the lirc package, but that would leave lircd/ lircmd in a tiny package of their own - something ftp-master doesn't exactly prefer. - kremotecontrol frontend for using remote controls Recommends: lirc This one is a tough call, isolated to kremotecontrol, the Recommends is correct, but kremotecontrol is a hard dependency of kdeutils (meta package, probably installed for most KDE users), which in turn is a hard dependency of kde-full… Besides the typical lirc | inputlirc suggestion, this may be a larger cause for lirc installations even if the user actually has not need for it; it's also a relatively new dependency, as its KDE3 predecessor -kdelirc- was not part of kdeutils at the time. Technically the dependency chain is totally correct and weakening it wouldn't be a logical conclusion for these meta packages, but given the lirc is only useful, if you have special, non-standard hardware (an IR receiver and a remote to use it) a suggests might be more in order. kremotecontrol didn't exist in squeeze, only its predecessor kdelirc, which was a seperate source package and not part of kdeutils; it was only suggested by kdetv, no hard dependencies or recommends. Yes this one. I had a vague memory of lirc being installed for me with KDE but I wasn't sure I could trust my memory. Thank you for the apt-rdepends foo :) […] Pulling in the lirc (or inputlirc for that matter) package, which means the dæmon, without a strong indication that the user actually owns IR receivers/ transceivers and wants to use them is most likely a bug. lirc (or inputlirc) cannot do anything useful, unless properly configured, which means at least selecting the driver type (out of ~60 options - userspace and staging drivers, most of them can't be autoprobed), specifying the device node it should listen on (in many cases a custom udev rule is also needed, to get a stable event device symlink) and the remote button -- key event mapping is required
Bug#655969: [Pkg-lirc-maint] Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user
tags 655969 + patch thanks Le samedi 26 janvier 2013 19:22:23, Jonathan Wiltshire a écrit : On Wed, Jan 18, 2012 at 01:34:08AM +0100, Stefan Lippers-Hollmann wrote: Thanks for the notice, while I don't exactly share that severity classification (although that is of course covered by the policy text), I'll work on this as soon as possible. Ping? It's been a year, and with a popcon of over 60,000 a *lot* of people are going to start seeing this prompt very soon... What about this patch? It checks whether the md5 of the lirc/hardware.conf conffile installed on the system matches the md5 of the file as modified by the postinst in an automatic install. If that is the case, it sets the file back to the content as shipped in the .deb package so that dpkg doesn't detect the file as modified. I reproduced the bug in pbuilder and the bug disappear when using this patch. Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#655969: [Pkg-lirc-maint] Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user
How many times will I forget to attach a file? Sorry. Thomas diff -Nru lirc-0.9.0~pre1/debian/changelog lirc-0.9.0~pre1/debian/changelog --- lirc-0.9.0~pre1/debian/changelog 2011-03-06 22:16:30.0 +0100 +++ lirc-0.9.0~pre1/debian/changelog 2013-02-12 18:25:50.0 +0100 @@ -1,3 +1,10 @@ +lirc (0.9.0~pre1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Avoid prompt when conffiles are not modified (Closes: #655969). + + -- Thomas Preud'homme robo...@debian.org Tue, 12 Feb 2013 18:24:27 +0100 + lirc (0.9.0~pre1-1) unstable; urgency=low [ Sven Mueller ] diff -Nru lirc-0.9.0~pre1/debian/lirc.preinst lirc-0.9.0~pre1/debian/lirc.preinst --- lirc-0.9.0~pre1/debian/lirc.preinst 1970-01-01 01:00:00.0 +0100 +++ lirc-0.9.0~pre1/debian/lirc.preinst 2013-03-07 15:51:25.0 +0100 @@ -0,0 +1,26 @@ +#!/bin/sh + +set -e + +case $1 in + upgrade) + oldconfmd5=$(md5sum /etc/lirc/hardware.conf | cut -d ' ' -f 1) + if [ $oldconfmd5 = 566ee1cfca73380a6ec4af14c7d874cd ] + then + sed -i s/^\(DRIVER\)=\/\1=\UNCONFIGURED/ /etc/lirc/hardware.conf + fi;; + install|abort-upgrade) + ;; + + *) + echo preinst called with unknown argument \`$1' 2 + exit 1 + ;; +esac + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 signature.asc Description: This is a digitally signed message part.
Bug#655969: [Pkg-lirc-maint] Bug#655969: lirc: prompting due to modified conffiles which where not modified by the user
Updated patch with (much) more comments. Thomas diff -Nru lirc-0.9.0~pre1/debian/changelog lirc-0.9.0~pre1/debian/changelog --- lirc-0.9.0~pre1/debian/changelog 2011-03-06 22:16:30.0 +0100 +++ lirc-0.9.0~pre1/debian/changelog 2013-03-07 16:58:28.0 +0100 @@ -1,3 +1,11 @@ +lirc (0.9.0~pre1-1.1) unstable; urgency=low + + * Non-maintainer upload. + * Avoid prompt when conffiles are not modified by the system administrator +(Closes: #655969). + + -- Thomas Preud'homme robo...@debian.org Tue, 12 Feb 2013 18:24:27 +0100 + lirc (0.9.0~pre1-1) unstable; urgency=low [ Sven Mueller ] diff -Nru lirc-0.9.0~pre1/debian/lirc.preinst lirc-0.9.0~pre1/debian/lirc.preinst --- lirc-0.9.0~pre1/debian/lirc.preinst 1970-01-01 01:00:00.0 +0100 +++ lirc-0.9.0~pre1/debian/lirc.preinst 2013-03-07 17:15:35.0 +0100 @@ -0,0 +1,36 @@ +#!/bin/sh + +set -e + +case $1 in + upgrade) + oldconfmd5=$(md5sum /etc/lirc/hardware.conf | cut -d ' ' -f 1) + # In Squeeze, lirc's postinst empties the value of DRIVER + # from /etc/lirc/hardware.conf if the value equals + # UNCONFIGURED. Since this file defaults to UNCONFIGURED, + # it is subsequently modified by the postinst. + # + # The code below check whether the md5 of the file matches the + # one of the file after a default install. If that is the case, + # the code reverts the change made by the postinst to prevent + # asking questions to the administrator when no file were + # modified. + if [ $oldconfmd5 = 566ee1cfca73380a6ec4af14c7d874cd ] + then + sed -i s/^\(DRIVER\)=\/\1=\UNCONFIGURED/ /etc/lirc/hardware.conf + fi;; + install|abort-upgrade) + ;; + + *) + echo preinst called with unknown argument \`$1' 2 + exit 1 + ;; +esac + +# dh_installdeb will replace this with shell code automatically +# generated by other debhelper scripts. + +#DEBHELPER# + +exit 0 signature.asc Description: This is a digitally signed message part.
Bug#699743: emms: fails to upgrade lenny - squeeze - wheezy: emms-setup.el:96:8:Error: Symbol's value as variable is void: emms-directory
Le jeudi 7 février 2013 06:48:48, Arnaud Fontaine a écrit : Hello, Seems to be the same issue as #693472.EMMS Depends against emacsen-common should probably be tightened to = 2.0.5. I managed to reproduce the bug in pbuilder and then tried this fix but it didn't work. Despite the tightened dependency, it still fails to upgrade with the same content in the log. Regards, signature.asc Description: This is a digitally signed message part.
Bug#698580: libdspam7-drv-{my, pg}sql: prompting due to modified conffiles which were not modified by the user: /etc/dspam/dspam.d/{my, pg}sql.conf
Here is a first version patch. It solve the problem for people upgrading from the lenny version but it will create problems for people migrating from the current wheezy version since the dbconfig template would cease to be a conffile. I'm currently thinking whether a fix for this new issue is worthwhile or not, considering it would increase the size of the diff against the current testing version. Best regards. diff -Nru dspam-3.10.1+dfsg/debian/changelog dspam-3.10.1+dfsg/debian/changelog --- dspam-3.10.1+dfsg/debian/changelog 2013-01-19 21:11:32.0 +0100 +++ dspam-3.10.1+dfsg/debian/changelog 2013-01-21 22:26:19.0 +0100 @@ -1,3 +1,10 @@ +dspam (3.10.1+dfsg-8) testing-proposed-updates; urgency=low + + * Avoid unnecessary prompt if configuration files have not been modified by +the user (Closes: 698580). + + -- Thomas Preud'homme robo...@debian.org Mon, 21 Jan 2013 22:25:00 +0100 + dspam (3.10.1+dfsg-7) testing-proposed-updates; urgency=low * Disable multi-arch since it create many problems with regards to the diff -Nru dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.dirs dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.dirs --- dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.dirs 2013-01-19 21:11:32.0 +0100 +++ dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.dirs 2013-01-21 22:26:19.0 +0100 @@ -1,3 +1,4 @@ etc/dspam/dspam.d +usr/share/libdspam7-drv-mysql usr/share/dbconfig-common/data/libdspam7-drv-mysql/install usr/share/dbconfig-common/data/libdspam7-drv-mysql/upgrade diff -Nru dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.install.in dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.install.in --- dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.install.in 2013-01-19 21:11:32.0 +0100 +++ dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.install.in 2013-01-21 22:26:19.0 +0100 @@ -1,7 +1,7 @@ debian/sqlfiles/install/mysql usr/share/dbconfig-common/data/libdspam7-drv-mysql/install debian/sqlfiles/upgrade/mysql usr/share/dbconfig-common/data/libdspam7-drv-mysql/upgrade usr/lib/@DEB_HOST_MULTIARCH@/dspam/libmysql_drv.so* -src/mysql.confetc/dspam/dspam.d/ +src/mysql.confusr/share/libdspam7-drv-mysql src/tools.mysql_drv/mysql_objects-4.1.sql usr/share/doc/libdspam7-drv-mysql/sql/ src/tools.mysql_drv/purge-4.1.sql usr/share/doc/libdspam7-drv-mysql/sql/ src/tools.mysql_drv/virtual_user_aliases.sql usr/share/doc/libdspam7-drv-mysql/sql/ diff -Nru dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.postinst dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.postinst --- dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.postinst 2013-01-19 21:11:32.0 +0100 +++ dspam-3.10.1+dfsg/debian/libdspam7-drv-mysql.postinst 2013-01-21 22:26:19.0 +0100 @@ -9,7 +9,7 @@ # Set some variables dbc_generate_include=template:/etc/dspam/dspam.d/mysql.conf -dbc_generate_include_args=-U -o template_infile='/etc/dspam/dspam.d/mysql.conf' +dbc_generate_include_args=-U -o template_infile='/usr/share/libdspam7-drv-mysql/mysql.conf' # Run dbconfig dbc_go libdspam7-drv-mysql $@ diff -Nru dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.dirs dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.dirs --- dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.dirs 2013-01-19 21:11:32.0 +0100 +++ dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.dirs 2013-01-21 22:26:19.0 +0100 @@ -1,4 +1,5 @@ etc/dspam/dspam.d +usr/share/libdspam7-drv-pgsql usr/share/dbconfig-common/data/libdspam7-drv-pgsql/install usr/share/dbconfig-common/data/libdspam7-drv-pgsql/upgrade usr/share/dbconfig-common/data/libdspam7-drv-pgsql/install-dbadmin diff -Nru dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.install.in dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.install.in --- dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.install.in 2013-01-19 21:11:32.0 +0100 +++ dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.install.in 2013-01-21 22:26:19.0 +0100 @@ -2,7 +2,7 @@ debian/sqlfiles/install/pgsql usr/share/dbconfig-common/data/libdspam7-drv-pgsql/install debian/sqlfiles/upgrade/pgsql usr/share/dbconfig-common/data/libdspam7-drv-pgsql/upgrade usr/lib/@DEB_HOST_MULTIARCH@/dspam/libpgsql_drv.so* -src/pgsql.conf etc/dspam/dspam.d/ +src/pgsql.conf usr/share/libdspam7-drv-pgsql src/tools.pgsql_drv/pgsql_objects.sql usr/share/doc/libdspam7-drv-pgsql/sql/ src/tools.pgsql_drv/purge-pe.sql usr/share/doc/libdspam7-drv-pgsql/sql/ src/tools.pgsql_drv/virtual_users.sql usr/share/doc/libdspam7-drv-pgsql/sql/ diff -Nru dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.postinst dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.postinst --- dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.postinst 2013-01-19 21:11:32.0 +0100 +++ dspam-3.10.1+dfsg/debian/libdspam7-drv-pgsql.postinst 2013-01-21 22:26:19.0 +0100 @@ -6,7
Bug#695275: closed by Thomas Preud'homme robo...@debian.org (Bug#695275: fixed in dspam 3.10.2+dfsg-3)
Le dimanche 6 janvier 2013 12:41:10, Helmut Grohne a écrit : Control: reopen -1 Control: found -1 dspam/3.10.2+dfsg-3 On Thu, Dec 20, 2012 at 07:06:07AM +, Debian Bug Tracking System wrote: * Only lock dspam user account when the last libdspam7 package is purged (Thanks Jakub Wilk for the review, Closes: #695275). The fix is still incomplete. Only the libdspam7 issue given as an example was fixed. libdspam7-drv-mysql.postrm and the like are still affected. Helmut Ah yes sorry. I searched explicitely for user locking but of course it's the case for any shared (among arch) resources modified/removed on purge. Best regards, Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
Bug#695275: handling of shared resources in M-A:same packages of dspam
Le dimanche 6 janvier 2013 17:09:48, Helmut Grohne a écrit :
[Adding multiarch-devel to CC for a comment on point 3.]
On Sun, Jan 06, 2013 at 12:50:35PM +0100, Thomas Preud'homme wrote:
Ah yes sorry. I searched explicitely for user locking but of course it's
the case for any shared (among arch) resources modified/removed on
purge.
Actually looking at it again I believe that simply removing Multi-Arch
for wheezy would be the best thing to do. My reasons for that are:
1) The release time likes one-line-fixes.
Yep and keeping multiarch would be a much bigger change.
2) None of those libraries has external (i.e. outside of src:dspam)
reverse dependencies. So the benefit of Multi-Arch is kind of
limited.
We were saying this on IRC few minutes ago.
3) Handling shared resources in M-A:same packages is yet an unsolved
problem. As more packages stumble across this problem there will
likely be a helper for such situations. This will not happen for
wheezy, so save yourself a bit of time and just defer this issue.
Yeah but I'm not sure a helper would be enough. I was already writing such a
small helper for myself (see below) but I stumbled upon the problem of
dbconfig-common in my case. It's used with debconf to install conf files and
it would be invoked twice if a multiarchified package was installed for 2
different architectures. I'm sure there is some other such example.
% cat debian/last_arch_installed
#!/bin/sh
# Multi-arch was added in dpkg in the same version as the db:Status-Abbrev
# virtual field was added to dpkg-query. Hence, either this bug cannot be
# encountered, or db:Status-Abbrev virtual field is available in dpkg-query.
! dpkg --assert-multi-arch ||
! dpkg-query '-f=${db:Status-Abbrev}\n' -W $1 | grep -vE '(.n|pc)'
/dev/null
Helmut
Best regards,
Thomas Preud'homme
signature.asc
Description: This is a digitally signed message part.
Bug#688853: dspam: long line in message body causes '530 5.2.0 Message is empty. Aborting.'
severity 688853 normal retitle 688853 Incorrect error message when a line is too long in a message thanks Le jeudi 27 septembre 2012 07:23:49, Andrey a écrit : 'Broken pipe' error occurs in Exim because Dspam just drops connection while Exim trying to send data to the socket though 530 reply occurs also. I don't know whether this is the SMTP RFC rules? And this behavior causes delay and retries to send email to the other Dspam users. AFAIK it's legal. See [1]. You can send an error when message is too big or when a line is too long and this necessarily happen before all data are sent. Hence there is no problem on dspam part except that the error message should be different. [1] http://tools.ietf.org/html/rfc5321#section-4.5.3.1.9 I'm thus changing the bug title and severity. Feel free to duplicate it to exim if you think there is a bug in exim (either because it doesn't handle the error correctly at all or because only default configuration doesn't handle it). Best regards, Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
Bug#688853: dspam: long line in message body causes '530 5.2.0 Message is empty. Aborting.'
Le mercredi 26 septembre 2012 11:07:09, vous avez écrit : Package: dspam Version: 3.10.1+dfsg-3~bpo60+1 Severity: critical dspam sends '530 5.2.0 Message is empty. Aborting.' while receiving incorrect spam message with long-long line, for example with length about 300K bytes: From what I read so far, dspam only reads a maximum of 1023 bytes per line but discard the whole line after that. I guess because of this it must be confuse by the quantity of bytes read and continues to read when there is no more data. The error you mention is raised by dspam when a message is empty. I'll continue to investigate. Thomas signature.asc Description: This is a digitally signed message part.
Bug#688853: dspam: long line in message body causes '530 5.2.0 Message is empty. Aborting.'
severity 688853 grave thanks Le mercredi 26 septembre 2012 14:40:20, Thomas Preud'homme a écrit : Le mercredi 26 septembre 2012 11:07:09, vous avez écrit : Package: dspam Version: 3.10.1+dfsg-3~bpo60+1 Severity: critical dspam sends '530 5.2.0 Message is empty. Aborting.' while receiving incorrect spam message with long-long line, for example with length about 300K bytes: From what I read so far, dspam only reads a maximum of 1023 bytes per line but discard the whole line after that. I guess because of this it must be confuse by the quantity of bytes read and continues to read when there is no more data. The error you mention is raised by dspam when a message is empty. I'll continue to investigate. Sorry I read to fast. What happen is that dspam read data from the socket by block of 1023 bytes and then search for a line in it by searching for the newline character with strchr. If it doesn't find a newline character, it returns NULL in cascade from pop_buffer up to read_sock through daemon_getline. When this returns NULL, it consider there is an error and return the error you saw. I didn't think much about it yet but I think a solution should be easy. Thomas signature.asc Description: This is a digitally signed message part.
Bug#644392: Bug confirmed
tags 644392 - moreinfo severity 644392 grave thanks Only raising severity to grave as the data loss only happen with exim and not by default: users need to uncomment a line in dspam.conf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#644392: Bug confirmed
tags 644392 + pending patch thanks Here is a proposed debdiff. Since I don't have my gpg key with me right now I'll need someone to NMU this change for me. diff -Nru dspam-3.10.1+dfsg/debian/changelog dspam-3.10.1+dfsg/debian/changelog --- dspam-3.10.1+dfsg/debian/changelog 2012-02-11 05:05:38.0 +0800 +++ dspam-3.10.1+dfsg/debian/changelog 2012-08-12 01:01:23.0 +0800 @@ -1,3 +1,13 @@ +dspam (3.10.1+dfsg-5) testing-proposed-updates; urgency=low + + * Team upload. + * Upload via testing-proposed-updates as unstable contains a new upstream +version. + * Cherry-pick patch from upstream to recommend using -oi when using dspam +with exim (Closes: #644392). + + -- Thomas Preud'homme robo...@celest.fr Sat, 11 Aug 2012 22:25:43 +0800 + dspam (3.10.1+dfsg-4) unstable; urgency=low * Apply patch from upstream to use POSIX::ctime() instead of deprecated diff -Nru dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf --- dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf 2012-02-11 05:05:38.0 +0800 +++ dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf 2012-08-12 01:01:23.0 +0800 @@ -22,7 +22,7 @@ # Other popular configurations: #TrustedDeliveryAgent /usr/cyrus/bin/deliver # Cyrus #TrustedDeliveryAgent /bin/maildrop # Maildrop -#TrustedDeliveryAgent /usr/sbin/exim -oMr spam-scanned $u # Exim +#TrustedDeliveryAgent /usr/sbin/exim -oMr spam-scanned -oi $u # Exim TrustedDeliveryAgent /usr/sbin/exim4 # Exim # #TrustedDeliveryAgent /usr/bin/procmail diff -Nru dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc --- dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc 1970-01-01 08:00:00.0 +0800 +++ dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc 2012-08-12 01:01:07.0 +0800 @@ -0,0 +1,62 @@ +Description: Fix documentation about exim integration + +Using dspam with exim requires to call exim with option -oi to avoid mails +from being truncated. This commit modify the documentation and configuration +file to add the -oi option when calling exim. + +Author: Kenneth Marshall k...@rice.edu +Origin: upstream, http://sourceforge.net/mailarchive/message.php?msg_id=29626440 +Bug-Debian: http://bugs.debian.org/644392 +Forwarded: http://sourceforge.net/mailarchive/forum.php?thread_name=20120802190055.GF15829%40aart.rice.eduforum_name=dspam-user +Last-Update: 2012-08-12 + +--- dspam-3.10.1+dfsg.orig/CHANGELOG dspam-3.10.1+dfsg/CHANGELOG +@@ -1,3 +1,5 @@ ++[20121202:2115] sbajic: Update documentation for Exim integration. ++ + Version 3.10.1 + -- + +--- dspam-3.10.1+dfsg.orig/doc/exim.txt dspam-3.10.1+dfsg/doc/exim.txt +@@ -1,4 +1,4 @@ +-$Id: exim.txt,v 1.1 2005/03/11 21:16:03 jonz Exp $ ++$Id: exim.txt,v 1.2 2012/08/02 21:09:23 sbajic Exp $ + + EXIM 4 INTEGRATION + +@@ -40,11 +40,17 @@ domain as part of the username: + + command = /usr/local/bin/dspam --deliver=innocent --user $local_part@$domain -- %u + +-Finally, you will need to configure and compile DSPAM. DSPAM will most likely +-end up calling exim again for delivery, using the spam-scanned protocol to +-identify scanned messages. The most common example is: +- +- ./configure --with-delivery-agent=/usr/sbin/exim -oMr spam-scanned ++Finally, you will need to configure and compile DSPAM. You can configure ++DSPAM with the appropriate LDA using --with-delivery-agent= at configure ++time or by specifying TrustedDeliveryAgent in dspam.conf. DSPAM will most ++likely end up calling exim again for delivery, using the spam-scanned ++protocol to identify scanned messages. The most common example is: ++ ++ ./configure --with-delivery-agent=/usr/local/sbin/exim -oMr spam-scanned -oi ++ ++Note: DSPAM expects the LDA to NOT provide the line with a single dot (.) ++processing to indicate the end of data that a MTA must provide to meet the ++SMTP RFC, hence the -oi option to exim above. + + RUNNING WITHOUT PRIVILEGED EXIM USERS + +--- dspam-3.10.1+dfsg.orig/src/dspam.conf.in dspam-3.10.1+dfsg/src/dspam.conf.in +@@ -43,7 +43,7 @@ StorageDriver @libdir@/dspam/@storage_dr + # Other popular configurations: + #TrustedDeliveryAgent /usr/cyrus/bin/deliver # Cyrus + #TrustedDeliveryAgent /bin/maildrop # Maildrop +-#TrustedDeliveryAgent /usr/local/sbin/exim -oMr spam-scanned # Exim ++#TrustedDeliveryAgent /usr/local/sbin/exim -oMr spam-scanned -oi # Exim + # + TrustedDeliveryAgent @delivery_agent@ + diff -Nru dspam-3.10.1+dfsg/debian/patches/series dspam-3.10.1+dfsg/debian/patches/series --- dspam-3.10.1+dfsg/debian/patches/series 2012-02-11 05:05:38.0 +0800 +++ dspam-3.10.1+dfsg/debian/patches/series 2012-08-12 01:01:03.0 +0800 @@ -5,3 +5,4 @@ 005_dspam-notify.diff 006_default-daemon-port.diff 007_ctime.pl.diff +fix_exim_integration_doc
Bug#644392: Bug confirmed
Updated debdiff pointed at upstream commit. Thanks to David Prévot for the suggestion. diff -Nru dspam-3.10.1+dfsg/debian/changelog dspam-3.10.1+dfsg/debian/changelog --- dspam-3.10.1+dfsg/debian/changelog 2012-02-11 05:05:38.0 +0800 +++ dspam-3.10.1+dfsg/debian/changelog 2012-08-12 01:01:23.0 +0800 @@ -1,3 +1,13 @@ +dspam (3.10.1+dfsg-5) testing-proposed-updates; urgency=low + + * Team upload. + * Upload via testing-proposed-updates as unstable contains a new upstream +version. + * Cherry-pick patch from upstream to recommend using -oi when using dspam +with exim (Closes: #644392). + + -- Thomas Preud'homme robo...@celest.fr Sat, 11 Aug 2012 22:25:43 +0800 + dspam (3.10.1+dfsg-4) unstable; urgency=low * Apply patch from upstream to use POSIX::ctime() instead of deprecated diff -Nru dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf --- dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf 2012-02-11 05:05:38.0 +0800 +++ dspam-3.10.1+dfsg/debian/dspam-documents/exim4/dspam.conf 2012-08-12 01:01:23.0 +0800 @@ -22,7 +22,7 @@ # Other popular configurations: #TrustedDeliveryAgent /usr/cyrus/bin/deliver # Cyrus #TrustedDeliveryAgent /bin/maildrop # Maildrop -#TrustedDeliveryAgent /usr/sbin/exim -oMr spam-scanned $u # Exim +#TrustedDeliveryAgent /usr/sbin/exim -oMr spam-scanned -oi $u # Exim TrustedDeliveryAgent /usr/sbin/exim4 # Exim # #TrustedDeliveryAgent /usr/bin/procmail diff -Nru dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc --- dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc 1970-01-01 08:00:00.0 +0800 +++ dspam-3.10.1+dfsg/debian/patches/fix_exim_integration_doc 2012-08-12 01:01:07.0 +0800 @@ -0,0 +1,62 @@ +Description: Fix documentation about exim integration + +Using dspam with exim requires to call exim with option -oi to avoid mails +from being truncated. This commit modify the documentation and configuration +file to add the -oi option when calling exim. + +Author: Kenneth Marshall k...@rice.edu +Origin: upstream, http://dspam.git.sourceforge.net/git/gitweb.cgi?p=dspam/dspam;a=commitdiff;h=e515570c74b0e48e714c5b45f11de2a5b3482459 +Bug-Debian: http://bugs.debian.org/644392 +Forwarded: http://sourceforge.net/mailarchive/forum.php?thread_name=20120802190055.GF15829%40aart.rice.eduforum_name=dspam-user +Last-Update: 2012-08-12 + +--- dspam-3.10.1+dfsg.orig/CHANGELOG dspam-3.10.1+dfsg/CHANGELOG +@@ -1,3 +1,5 @@ ++[20121202:2115] sbajic: Update documentation for Exim integration. ++ + Version 3.10.1 + -- + +--- dspam-3.10.1+dfsg.orig/doc/exim.txt dspam-3.10.1+dfsg/doc/exim.txt +@@ -1,4 +1,4 @@ +-$Id: exim.txt,v 1.1 2005/03/11 21:16:03 jonz Exp $ ++$Id: exim.txt,v 1.2 2012/08/02 21:09:23 sbajic Exp $ + + EXIM 4 INTEGRATION + +@@ -40,11 +40,17 @@ domain as part of the username: + + command = /usr/local/bin/dspam --deliver=innocent --user $local_part@$domain -- %u + +-Finally, you will need to configure and compile DSPAM. DSPAM will most likely +-end up calling exim again for delivery, using the spam-scanned protocol to +-identify scanned messages. The most common example is: +- +- ./configure --with-delivery-agent=/usr/sbin/exim -oMr spam-scanned ++Finally, you will need to configure and compile DSPAM. You can configure ++DSPAM with the appropriate LDA using --with-delivery-agent= at configure ++time or by specifying TrustedDeliveryAgent in dspam.conf. DSPAM will most ++likely end up calling exim again for delivery, using the spam-scanned ++protocol to identify scanned messages. The most common example is: ++ ++ ./configure --with-delivery-agent=/usr/local/sbin/exim -oMr spam-scanned -oi ++ ++Note: DSPAM expects the LDA to NOT provide the line with a single dot (.) ++processing to indicate the end of data that a MTA must provide to meet the ++SMTP RFC, hence the -oi option to exim above. + + RUNNING WITHOUT PRIVILEGED EXIM USERS + +--- dspam-3.10.1+dfsg.orig/src/dspam.conf.in dspam-3.10.1+dfsg/src/dspam.conf.in +@@ -43,7 +43,7 @@ StorageDriver @libdir@/dspam/@storage_dr + # Other popular configurations: + #TrustedDeliveryAgent /usr/cyrus/bin/deliver # Cyrus + #TrustedDeliveryAgent /bin/maildrop # Maildrop +-#TrustedDeliveryAgent /usr/local/sbin/exim -oMr spam-scanned # Exim ++#TrustedDeliveryAgent /usr/local/sbin/exim -oMr spam-scanned -oi # Exim + # + TrustedDeliveryAgent @delivery_agent@ + diff -Nru dspam-3.10.1+dfsg/debian/patches/series dspam-3.10.1+dfsg/debian/patches/series --- dspam-3.10.1+dfsg/debian/patches/series 2012-02-11 05:05:38.0 +0800 +++ dspam-3.10.1+dfsg/debian/patches/series 2012-08-12 01:01:03.0 +0800 @@ -5,3 +5,4 @@ 005_dspam-notify.diff 006_default-daemon-port.diff 007_ctime.pl.diff +fix_exim_integration_doc
Bug#657904: console-setup: Shouldn't console-setup package put files in /usr/share/doc/console-setup?
[1] and [2] could be used as a starting point to migrate from directory to symlink. [1] http://lists.debian.org/debian-dpkg/2012/01/msg00023.html [2] http://lists.debian.org/debian-dpkg/2012/01/msg00024.html Best regards, Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
Bug#676668: ultracopier: Contains non-free files and fails to respect GPL
Package: ultracopier Version: 0.2.0.16-1 Severity: serious Tags: upstream Justification: Policy 2.2.1 Version 0.2.0.16 of ultracopier contains in its src/styles subdirectories some images. Some of them are distributed under a free license but with README forbidding commercial use (src/styles/IcOsX) while some other being distributed under GPL but the corresponding SVG source is not distributed (eg. src/styles/Oxygen). The new version 0.3.0.5 solve all these problems. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ultracopier depends on: ii libc6 2.13-33 ii libgcc1 1:4.7.0-12 ii libqt4-network 4:4.8.1-2 ii libqtcore4 4:4.8.1-2 ii libqtgui4 4:4.8.1-2 ii libstdc++6 4.7.0-12 ultracopier recommends no packages. ultracopier suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669587: latex-xcolor: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2)
Le mercredi 23 mai 2012 20:09:40, Thomas Preud'homme a écrit : Here is a patch I made according to the suggestion of the thread named above. I'll find a DD to do an NMU in case you don't have the time to do the upload yourself. As recommanded by devref, I took care of only fixing this issue, All the best, Thomas Preud'homme Updated patch which fix the problem of files not included that had the previous patch. Best regards. reverted: --- latex-xcolor-2.11/debian/prerm +++ latex-xcolor-2.11.orig/debian/prerm @@ -1,39 +0,0 @@ -#! /bin/sh -# prerm script for latex-xcolor -# -# see: dh_installdeb(1) - -set -e - -# summary of how this script can be called: -#* prerm `remove' -#* old-prerm `upgrade' new-version -#* new-prerm `failed-upgrade' old-version -#* conflictor's-prerm `remove' `in-favour' package new-version -#* deconfigured's-prerm `deconfigure' `in-favour' -# package-being-installed version `removing' -# conflicting-package version -# for details, see http://www.debian.org/doc/debian-policy/ or -# the debian-policy package - - -case $1 in -remove|upgrade|deconfigure) -# install-info --quiet --remove /usr/info/latex-xcolor.info.gz -;; -failed-upgrade) -;; -*) -echo prerm called with unknown argument \`$1' 2 -exit 1 -;; -esac - -# dh_installdeb will replace this with shell code automatically -# generated by other debhelper scripts. - -#DEBHELPER# - -exit 0 - - reverted: --- latex-xcolor-2.11/debian/preinst +++ latex-xcolor-2.11.orig/debian/preinst @@ -1,44 +0,0 @@ -#! /bin/sh -# preinst script for latex-xcolor -# -# see: dh_installdeb(1) - -set -e - -# summary of how this script can be called: -#* new-preinst `install' -#* new-preinst `install' old-version -#* new-preinst `upgrade' old-version -#* old-preinst `abort-upgrade' new-version -# -# for details, see http://www.debian.org/doc/debian-policy/ or -# the debian-policy package - - -case $1 in -install|upgrade) -#if [ $1 = upgrade ] -#then -#start-stop-daemon --stop --quiet --oknodo \ -#--pidfile /var/run/latex-xcolor.pid \ -#--exec /usr/sbin/latex-xcolor 2/dev/null || true -#fi -;; - -abort-upgrade) -;; - -*) -echo preinst called with unknown argument \`$1' 2 -exit 1 -;; -esac - -# dh_installdeb will replace this with shell code automatically -# generated by other debhelper scripts. - -#DEBHELPER# - -exit 0 - - diff -u latex-xcolor-2.11/debian/rules latex-xcolor-2.11/debian/rules --- latex-xcolor-2.11/debian/rules +++ latex-xcolor-2.11/debian/rules @@ -87,6 +87,7 @@ # dh_installinfo dh_installman dh_link + dh_installtex dh_strip dh_compress dh_fixperms diff -u latex-xcolor-2.11/debian/control latex-xcolor-2.11/debian/control --- latex-xcolor-2.11/debian/control +++ latex-xcolor-2.11/debian/control @@ -1,7 +1,7 @@ Source: latex-xcolor Section: tex Build-Depends: debhelper (= 4.0.0) -Build-Depends-Indep: texlive-latex-base +Build-Depends-Indep: texlive-latex-base, tex-common Priority: optional Maintainer: OHURA Makoto oh...@debian.org Standards-Version: 3.7.2 reverted: --- latex-xcolor-2.11/debian/postinst +++ latex-xcolor-2.11.orig/debian/postinst @@ -1,46 +0,0 @@ -#! /bin/sh -# postinst script for latex-xcolor -# -# see: dh_installdeb(1) - -set -e - -# summary of how this script can be called: -#* postinst `configure' most-recently-configured-version -#* old-postinst `abort-upgrade' new version -#* conflictor's-postinst `abort-remove' `in-favour' package -# new-version -#* deconfigured's-postinst `abort-deconfigure' `in-favour' -# failed-install-package version `removing' -# conflicting-package version -# for details, see http://www.debian.org/doc/debian-policy/ or -# the debian-policy package -# - -case $1 in -configure) - -if [ -x /usr/bin/mktexlsr ] ; then -/usr/bin/mktexlsr -fi - -;; - -abort-upgrade|abort-remove|abort-deconfigure) - -;; - -*) -echo postinst called with unknown argument \`$1' 2 -exit 1 -;; -esac - -# dh_installdeb will replace this with shell code automatically -# generated by other debhelper scripts. - -#DEBHELPER# - -exit 0 - - diff -u latex-xcolor-2.11/debian/changelog latex-xcolor-2.11/debian/changelog --- latex-xcolor-2.11/debian/changelog +++ latex-xcolor-2.11/debian/changelog @@ -1,3 +1,13 @@ +latex-xcolor (2.11-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: +- Use dh_installtex to generate calls to mktexlsr in postinst and postrm +in order to avoid creating /usr/local/share/texmf/ls-R (Closes: #669587). + * Remove useless preinst and prerm scripts. + + -- Thomas Preud'homme robo...@celest.fr Wed, 23 May 2012 17:07:57 +0200 + latex-xcolor (2.11-1
Bug#624810: subversion security updates fail to build on kfreebsd-* too
Le mercredi 12 octobre 2011 12:07:12, Thijs Kinkhorst a écrit : found 624810 1.6.12dfsg-5 thanks Hi, The package FTBFS on ia64 and kfreebsd-* when binNMUed for the current Python transition. Here are the relevant snippets from the build logs: The same problem is also exists on kfreebsd-* in stable-security. This means that the security updates for subversion in Squeeze (1.6.12dfsg-5 and 1.6.12dfsg-6) have still not reached stable users on kfreebsd. See the table here: http://packages.debian.org/squeeze/subversion For reference, here's a full build log on kfreebsd-amd64 for the 1.6.12dfsg-5 update. It seems to show the same problems as described in this bug: http://people.debian.org/~thijs/subversion_1.6.12dfsg-5-kfreebsd- amd64-20110301-2215.gz Can you please look into this, as this both keeps unsafe versions of subversion in kfreebsd, but also prevents the set of subversion updates for all archs to be included into point releases. Could it be related to [1]? [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/ruby18/files/patch- ext_socket_socket.c thanks, Thijs Best regards, Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
Bug#669587: latex-xcolor: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2)
Le vendredi 20 avril 2012 09:20:57, vous avez écrit : Package: latex-xcolor Version: 2.11-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package left unowned files on the system after purge, which is a violation of policy 6.8: http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-removed etails As putting files into /usr/local is also a violation of http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.1.2 I'm setting the severity to serious. From the attached log (scroll to the bottom...): 0m53.8s ERROR: FAIL: Package purging left files on system: /usr/local/share/texmf/not owned /usr/local/share/texmf/ls-Rnot owned This problem is usually caused by running mktexlsr (or texhash) without path arguments from a maintainer script. The recommende solution is to switch to use dh_installtex and have this generate most (or perhaps even all) of the maintainer scripts content. Otherwise run mktexlsr with the tree as argument where the package installs its files, which is usually mktexlsr /usr/share/texmf There has been some further discussion about these bugs in this thread: http://lists.debian.org/debian-tex-maint/2012/04/msg00306.html Please have a look at the Debian-TeX-Policy (in the tex-common package) for the current practice of handling TeX packages. For further TeX packaging related questions contact debian-tex-ma...@lists.debian.org cheers, Andreas Here is a patch I made according to the suggestion of the thread named above. I'll find a DD to do an NMU in case you don't have the time to do the upload yourself. As recommanded by devref, I took care of only fixing this issue, All the best, Thomas Preud'homme diff -u latex-xcolor-2.11/debian/rules latex-xcolor-2.11/debian/rules --- latex-xcolor-2.11/debian/rules +++ latex-xcolor-2.11/debian/rules @@ -72,6 +72,7 @@ binary-indep: build install dh_testdir dh_testroot + dh_prep dh_installchangelogs ChangeLog dh_installdocs dh_installexamples xcolor?.tex @@ -87,6 +88,7 @@ # dh_installinfo dh_installman dh_link + dh_installtex dh_strip dh_compress dh_fixperms diff -u latex-xcolor-2.11/debian/control latex-xcolor-2.11/debian/control --- latex-xcolor-2.11/debian/control +++ latex-xcolor-2.11/debian/control @@ -1,6 +1,6 @@ Source: latex-xcolor Section: tex -Build-Depends: debhelper (= 4.0.0) +Build-Depends: debhelper (= 4.0.0), tex-common Build-Depends-Indep: texlive-latex-base Priority: optional Maintainer: OHURA Makoto oh...@debian.org reverted: --- latex-xcolor-2.11/debian/postinst +++ latex-xcolor-2.11.orig/debian/postinst @@ -1,46 +0,0 @@ -#! /bin/sh -# postinst script for latex-xcolor -# -# see: dh_installdeb(1) - -set -e - -# summary of how this script can be called: -#* postinst `configure' most-recently-configured-version -#* old-postinst `abort-upgrade' new version -#* conflictor's-postinst `abort-remove' `in-favour' package -# new-version -#* deconfigured's-postinst `abort-deconfigure' `in-favour' -# failed-install-package version `removing' -# conflicting-package version -# for details, see http://www.debian.org/doc/debian-policy/ or -# the debian-policy package -# - -case $1 in -configure) - -if [ -x /usr/bin/mktexlsr ] ; then -/usr/bin/mktexlsr -fi - -;; - -abort-upgrade|abort-remove|abort-deconfigure) - -;; - -*) -echo postinst called with unknown argument \`$1' 2 -exit 1 -;; -esac - -# dh_installdeb will replace this with shell code automatically -# generated by other debhelper scripts. - -#DEBHELPER# - -exit 0 - - diff -u latex-xcolor-2.11/debian/changelog latex-xcolor-2.11/debian/changelog --- latex-xcolor-2.11/debian/changelog +++ latex-xcolor-2.11/debian/changelog @@ -1,3 +1,12 @@ +latex-xcolor (2.11-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: +- Call dh_installtex instead of mktexlsr in postinst to avoid creating + /usr/local/share/texmf/ls-R file (Closes: #669587). + + -- Thomas Preud'homme robo...@celest.fr Wed, 23 May 2012 17:07:57 +0200 + latex-xcolor (2.11-1) unstable; urgency=low * New upstream release reverted: --- latex-xcolor-2.11/debian/postrm +++ latex-xcolor-2.11.orig/debian/postrm @@ -1,40 +0,0 @@ -#! /bin/sh -# postrm script for latex-xcolor -# -# see: dh_installdeb(1) - -set -e - -# summary of how this script can be called: -#* postrm `remove' -#* postrm `purge' -#* old-postrm `upgrade' new-version -#* new-postrm `failed-upgrade' old-version -#* new-postrm `abort-install' -#* new-postrm `abort-install' old-version -#* new-postrm `abort-upgrade' old-version -#* disappearer's-postrm `disappear' roverwritr new-version -# for details, see http://www.debian.org/doc/debian-policy/ or -# the debian-policy package - - -case $1
Bug#605154: closing 605154
close 605154 5.1.3-12 thanks Salome was removed from Debian [1]. [1] http://packages.qa.debian.org/s/salome/news/20120126T112738Z.html -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589864: closing 589864
close 589864 5.5.26-5 thanks Tomcat 5.5 is no longer part of Debian and according to the submitter this bug doesn't affect tomcat6. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#590301: closing 590301
close 590301 22.3+1-1 thanks emacs22 has been removed from Debian. The issue is fixed in emacs23 according to [1] [1] http://security-tracker.debian.org/tracker/CVE-2010-0825 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555668: closing 555668
close 555668 0.2.2-2-rm thanks Package has been removed from Debian and is only part of oldstable now. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619263: More info
I got the same problem a few minutes ago and it got solved by upgrading from 1:3.4.6-2 to 1:3.5.2~rc2-1 Best regards, Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
Bug#656502: blender: [FTBFS] Does not build with libav 0.8~beta2
Source: blender
Version: 6.3.1
Severity: serious
Tags: patch upstream
Justification: Fails to build from source
In addition to #654428, blender also fails to build from source because
of API changes in libav 0.9~beta2. Attached is a patch which fix all (3)
the issues I found until #654428 build failure.
Note the change related to avformat_alloc_output_context2 in
ffmpeg_compat.h header. Blender is likely to need the same kind of
change when a future version of libav will be uploaded to Debian.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: armhf (armv7l)
Kernel: Linux 2.6.38-ac2-ac100 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Description: Adapt to libavutil API changes
Add include for libavutil/mathematics.h in ffmpeg_compat.h and writeffmpeg.c
since it is no longer included in libavutil/avutil.h
Author: Thomas Preud'homme robo...@celest.fr
Origin: vendor
Forwarded: no
Last-Update: 2012-01-19
---
--- blender-2.61.orig/intern/ffmpeg/ffmpeg_compat.h
+++ blender-2.61/intern/ffmpeg/ffmpeg_compat.h
@@ -35,6 +35,7 @@
#include libavcodec/avcodec.h
#include libavutil/rational.h
+#include libavutil/mathematics.h
#if (LIBAVFORMAT_VERSION_MAJOR 52) || ((LIBAVFORMAT_VERSION_MAJOR = 52) (LIBAVFORMAT_VERSION_MINOR = 101))
#define FFMPEG_HAVE_PARSE_UTILS 1
--- blender-2.61.orig/source/blender/blenkernel/intern/writeffmpeg.c
+++ blender-2.61/source/blender/blenkernel/intern/writeffmpeg.c
@@ -36,6 +36,7 @@
#include libavformat/avformat.h
#include libavcodec/avcodec.h
#include libavutil/rational.h
+#include libavutil/mathematics.h
#include libswscale/swscale.h
#include libavcodec/opt.h
From 63b4c577c951245904fd59ac8c6021bab18b0de4 Mon Sep 17 00:00:00 2001
From: Antonio Ospite osp...@studenti.unina.it
Date: Sat, 17 Dec 2011 15:45:16 +0100
Subject: [PATCH] Make blender compile with FFmpeg from Debian.
X-Face: z*RaLf`X@C75u6Ig9}{oW$H;1_\2t5)({*|jhMpyWR#k60!#=#/Vb;]yA5GWI5`6u+
;6b'@y|8wwB;4/e!7wYYrcqdJFY,~%Gk_4]cq$Ei/7jN3ah(m`ku?pX.+~:_/wC~dwn^)MizBG
!pE^+iDQQ1yC6^,)YDKkxDd!T\I~93J_`4)A{':UrE
avformat_alloc_output_context2() should be in the libavformat 53.2.0 but
it isn't in Debian, re-define it.
Signed-off-by: Antonio Ospite osp...@studenti.unina.it
---
intern/ffmpeg/ffmpeg_compat.h | 61 +
1 files changed, 61 insertions(+), 0 deletions(-)
diff --git a/intern/ffmpeg/ffmpeg_compat.h b/intern/ffmpeg/ffmpeg_compat.h
index dfdad22..5259f69 100644
--- a/intern/ffmpeg/ffmpeg_compat.h
+++ b/intern/ffmpeg/ffmpeg_compat.h
@@ -48,6 +48,67 @@
#define FFMPEG_HAVE_AVIO 1
#endif
+#if (LIBAVFORMAT_VERSION_MAJOR 53) || ((LIBAVFORMAT_VERSION_MAJOR == 53) (LIBAVFORMAT_VERSION_MINOR 21))
+/* XXX The last check above should be (LIBAVFORMAT_VERSION_MINOR 2),
+ * look at http://patches.libav.org/patch// but ffmpeg in Debian is
+ * strange: 53.2.0 should have avformat_alloc_output_context2() but it does
+ * not.
+ */
+#include libavutil/avstring.h
+static int avformat_alloc_output_context2(AVFormatContext **avctx, AVOutputFormat *oformat,
+ const char *format, const char *filename)
+{
+AVFormatContext *s = avformat_alloc_context();
+int ret = 0;
+
+*avctx = NULL;
+if (!s)
+goto nomem;
+
+if (!oformat) {
+if (format) {
+oformat = av_guess_format(format, NULL, NULL);
+if (!oformat) {
+av_log(s, AV_LOG_ERROR, Requested output format '%s' is not a suitable output format\n, format);
+ret = AVERROR(EINVAL);
+goto error;
+}
+} else {
+oformat = av_guess_format(NULL, filename, NULL);
+if (!oformat) {
+ret = AVERROR(EINVAL);
+av_log(s, AV_LOG_ERROR, Unable to find a suitable output format for '%s'\n,
+ filename);
+goto error;
+}
+}
+}
+
+s-oformat = oformat;
+if (s-oformat-priv_data_size 0) {
+s-priv_data = av_mallocz(s-oformat-priv_data_size);
+if (!s-priv_data)
+goto nomem;
+if (s-oformat-priv_class) {
+*(const AVClass**)s-priv_data= s-oformat-priv_class;
+av_opt_set_defaults(s-priv_data);
+}
+} else
+s-priv_data = NULL;
+
+if (filename)
+av_strlcpy(s-filename, filename, sizeof(s-filename));
+*avctx = s;
+return 0;
+nomem:
+av_log(s, AV_LOG_ERROR, Out of memory\n);
+ret = AVERROR(ENOMEM);
+error:
+avformat_free_context(s);
+return ret;
+}
+#endif
+
#if (LIBAVCODEC_VERSION_MAJOR 53) || ((LIBAVCODEC_VERSION_MAJOR == 53) (LIBAVCODEC_VERSION_MINOR 1)) || ((LIBAVCODEC_VERSION_MAJOR == 53) (LIBAVCODEC_VERSION_MINOR == 1) (LIBAVCODEC_VERSION_MICRO = 1)) || ((LIBAVCODEC_VERSION_MAJOR == 52) (LIBAVCODEC_VERSION_MINOR = 121
Bug#653725: cyrus-sasl2: diff for NMU version 2.1.25.dfsg1-2.1
tags 653725 + patch thanks Dear maintainer, I've prepared an NMU for cyrus-sasl2 (versioned as 2.1.25.dfsg1-2.1) but did not upload it to DELAYED yet as I'm not a DD. However I will seek a sponsor for this if I don't get any news from you in the next days. Please feel free to tell me not to if you plan to do an upload fixing this issue yourself. Best regards. diff -Nru cyrus-sasl2-2.1.25.dfsg1/debian/changelog cyrus-sasl2-2.1.25.dfsg1/debian/changelog --- cyrus-sasl2-2.1.25.dfsg1/debian/changelog 2011-09-27 13:00:32.0 +0200 +++ cyrus-sasl2-2.1.25.dfsg1/debian/changelog 2012-01-17 23:38:23.0 +0100 @@ -1,3 +1,10 @@ +cyrus-sasl2 (2.1.25.dfsg1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Stop relying on the structure of debugging package (Closes: #653725). + + -- Thomas Preud'homme robo...@celest.fr Tue, 17 Jan 2012 23:36:09 +0100 + cyrus-sasl2 (2.1.25.dfsg1-2) unstable; urgency=low [ Roberto C. Sanchez ] diff -Nru cyrus-sasl2-2.1.25.dfsg1/debian/rules cyrus-sasl2-2.1.25.dfsg1/debian/rules --- cyrus-sasl2-2.1.25.dfsg1/debian/rules 2011-09-27 13:00:32.0 +0200 +++ cyrus-sasl2-2.1.25.dfsg1/debian/rules 2012-01-17 23:35:56.0 +0100 @@ -227,10 +227,9 @@ dh_installinit --name=saslauthd start 20 2 3 4 5 . stop 20 1 . override_dh_strip: - dh_strip -psasl2-bin -plibsasl2-2 -plibsasl2-modules -plibsasl2-modules-ldap -plibsasl2-modules-otp -plibsasl2-modules-sql -plibsasl2-modules-gssapi-mit -plibsasl2-dev -Nlibsasl2-modules-gssapi-heimdal --dbg-package=cyrus-sasl2-dbg + dh_strip -Xlibgssapiv2.so.2.0. -psasl2-bin -plibsasl2-2 -plibsasl2-modules -plibsasl2-modules-ldap -plibsasl2-modules-otp -plibsasl2-modules-sql -plibsasl2-modules-gssapi-mit -plibsasl2-dev -Nlibsasl2-modules-gssapi-heimdal --dbg-package=cyrus-sasl2-dbg + dh_strip -Xlibgs2.so.2.0. -Xlibscram.so.2.0. -plibsasl2-modules-gssapi-mit --dbg-package=cyrus-sasl2-mit-dbg dh_strip -plibsasl2-modules-gssapi-heimdal -Nsasl2-bin -Nlibsasl2-2 -Nlibsasl2-modules -Nlibsasl2-modules-ldap -Nlibsasl2-modules-otp -Nlibsasl2-modules-sql -Nlibsasl2-modules-gssapi-mit -Nlibsasl2-dev --dbg-package=cyrus-sasl2-heimdal-dbg - mkdir -p debian/cyrus-sasl2-mit-dbg/usr/lib/debug/usr/lib/$(DEB_HOST_MULTIARCH)/sasl2 - mv debian/cyrus-sasl2-dbg/usr/lib/debug/usr/lib/$(DEB_HOST_MULTIARCH)/sasl2/libgssapiv2.so.2.0.* debian/cyrus-sasl2-mit-dbg/usr/lib/debug/usr/lib/$(DEB_HOST_MULTIARCH)/sasl2/ override_dh_makeshlibs: dh_makeshlibs -X/usr/lib/$(DEB_HOST_MULTIARCH)/sasl2
Bug#654904: tcc: FTBFS [armel] unknown structures, types and macros
Package: tcc
Version: 0.9.26~git20120104.83d57c0-1
Severity: serious
Tags: patch pending
Justification: Fails to build from source
tcc fails to build from source on armel because it compiles
unconditionally tccasm.c even if inline assembly is not supported for
this architecture (CONFIG_TCC_ASM undefined). The patch is simple,
include a #ifdef CONFIG_TCC_ASM right after the #include tcc.h and
#endif at the end of the file.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages tcc depends on:
ii dpkg 1.16.1.2
ii install-info 4.13a.dfsg.1-8
ii libc6 2.13-24
Versions of packages tcc recommends:
ii libc6-dev [libc-dev] 2.13-24
tcc suggests no packages.
-- no debconf information
diff --git a/tccasm.c b/tccasm.c
index 527c006..d1d2af1 100644
--- a/tccasm.c
+++ b/tccasm.c
@@ -19,6 +19,7 @@
*/
#include tcc.h
+#ifdef CONFIG_TCC_ASM
ST_FUNC int asm_get_local_label_name(TCCState *s1, unsigned int n)
{
@@ -1115,3 +1116,4 @@ ST_FUNC void asm_global_instr(void)
cstr_free(astr);
}
+#endif /* CONFIG_TCC_ASM */
Bug#654631: tcc on amd64 wrongly expect crt* files to be in /usr/lib64/x86_64-linux-gnu
Package: tcc Version: 0.9.26~git20110616.330d2ee-1 Severity: grave Justification: renders package unusable Dear Maintainer, tcc consider the location of dynamic linker to decide the location of crt*.o files. Since the dynamic linker is located at /lib64/ld-linux-x86-64.so.2 on Debian, it searches crt*.o files on /usr/lib64/x86_64-linux-gnu instead of /usr/lib/x86_64-linux-gnu. A more recent snapshot of the upstream development branch along with an appropriate update of override_dh_auto_configure target in debian/rules will fix this issue. *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tcc depends on: ii dpkg 1.16.1.2 ii install-info 4.13a.dfsg.1-8 ii libc6 2.13-24 Versions of packages tcc recommends: ii libc6-dev [libc-dev] 2.13-24 tcc suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#614470: gio-desktop-app-info-lookup extension point deprecated
extension point is now deprecated, see commit 9b262f1c5fe5a6fd879f17cd7b80d8c54e33d80c in upstream glib git repository. A possible temporary solution would be to remove -DG_DISABLE_DEPRECATED from libgiofm_la_CFLAGS in src/Makefile.am. However, since it's just an extension (if I read it correctly, I'm no expert of glib at all) I guess the real solution would be to just remove gio subdirectory. signature.asc Description: This is a digitally signed message part.
Bug#614462: (no subject)
The bug comes from linux/socket.h (included by linux/if.h) don't define struct sockaddr anymore (it seems to be stripped from the linux include/linux/if.h by excluded everything between #ifdef __KERNEL__ and #endif). According to [0] it is not going to be reverted and the software needs to cope with that. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573159#10 Since linux.h is only used in libexplain/buffer/ifreq_settings.c through libexplain/ac/linux/if.h to provide more complete information, a solution could be to just remove the test for linux/if.h in etc/configure.ac signature.asc Description: This is a digitally signed message part.
Bug#636541: tcc: Set a wrong path to ELF interpreter (breaks ELF ABI)
Source: tcc Version: 0.9.25-8 Severity: serious Justification: Policy 9.1.1 From tcc 0.9.25-8 tcc sets ELF interpreter in generated binary with multiarch path (eg. /lib64/x86_64-linux-gnu/ld-linux-x86-64.so.2 on amd64). This breaks ELF ABI and violate policy per §9.1.1 (section about FHS). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable-updates'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633896: closing 633896
close 633896 0.9.26~git20110616.330d2ee-2 thanks tcc 0.9.26~git20110616.330d2ee-2 contains a fix for this issue and builds now fine on Debian GNU/kFreeBSD (see [0] and [1]). [0] https://buildd.debian.org/status/fetch.php?pkg=tccarch=kfreebsd-i386ver=0.9.26%7Egit20110616.330d2ee-2stamp=1310766907 [1] https://buildd.debian.org/status/fetch.php?pkg=tccarch=kfreebsd-amd64ver=0.9.26%7Egit20110616.330d2ee-2stamp=1310767634 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#633495: closing 633495
close 633495 0.9.25-8 thanks Problem lied in array_test which was defined with one parameter but called without parameter. This issue is fixed in 0.9.25-8 and the problem will be reported upstream. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632089: ping
I've just come across this bug report — I probably unsuscribe from tcc by mistake — but there is a patch in progress. Should be ready by 2011-07-05. Best regards. signature.asc Description: This is a digitally signed message part.
Bug#583073: Intend to NMU lbdb for this issue
tags 583073 + patch pending thanks Hello Rolland, this bug is open for a year now and the bug is serious, so I think an nmu would be welcome. Attached is the debdiff output of the changes. I intend to do the NMU in one week to DELAYED/2 if there is no reaction until then, but the actual upload could be done in a bit more time as I need to find a sponsor first. Best regards. diff -Nru lbdb-0.37/debian/changelog lbdb-0.37+nmu1/debian/changelog --- lbdb-0.37/debian/changelog 2010-05-18 20:03:31.0 +0200 +++ lbdb-0.37+nmu1/debian/changelog 2011-06-05 21:03:11.0 +0200 @@ -1,3 +1,11 @@ +lbdb (0.37+nmu1) unstable; urgency=low + + * Non-maintainer upload. + * Build-Depend on libvformat-dev instead of libvformat1-dev +(Closes: #583073). + + -- Thomas Preud'homme robo...@celest.fr Sun, 05 Jun 2011 21:03:08 +0200 + lbdb (0.37) unstable; urgency=low * Fix bashisms in m_bbdb (Closes: #530113). diff -Nru lbdb-0.37/debian/control lbdb-0.37+nmu1/debian/control --- lbdb-0.37/debian/control 2010-05-18 20:03:31.0 +0200 +++ lbdb-0.37+nmu1/debian/control 2011-06-05 21:03:02.0 +0200 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Roland Rosenfeld rol...@debian.org Standards-Version: 3.8.4 -Build-Depends: debhelper (= 5), perl, libvformat1-dev +Build-Depends: debhelper (= 5), perl, libvformat-dev Homepage: http://www.spinnaker.de/lbdb/ Package: lbdb
Bug#625100: Fixed package waiting for sponsor
Hi all, the bug is already fixed and the patch have been merged upstream. I'm just waiting for my sponsor to upload the package which shouldn't take long. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577661: Status of DSPAM in Debian
Le lundi 28 mars 2011 08:38:13, Julien Valroff a écrit : Hi, Le lundi 28 mars 2011 à 00:24:26 (+0200 CEST), Christoph Haas a écrit : Also, most of the DSPAM uploaders are MIA. Well, I think all are MIA except Christoph Haas. Could you please update the list in your upload? Same with the DM flag (!?). You're right - I have already sent several calls to them, with no answer. I only leave Christoph and Matthijs as I know they aren't MIA. We are alive indeed. :) But honestly I have never been using dspam in production and my experience with it is close to zero. The reason I'm listed as uploader is probably back from the time that Matthijs was no DD yet and I was helping by sponsoring the package. I was evaluating anti-spam software but was never enthusastic about dspam. OK, I understand now. I assume that Matthijs is the main person to ask here. All I could offer is sponsorship just like any other DD and I'm currently pretty busy with another huge Debian package. I'd have to give the dspam package a complete check and I doubt I'll find the time for that. Matthijs, I know you have lost interest in packaging DSPAM and are already busy with other things, should I remove you from the Uploaders? I'd even like to ask to get me removed from debian/control if possible. Done. You are obviously welcome to join us (me?) at any time. In case I am alone in pkg-dspam after this, I'll close the pkg-dspam project on Alioth, and I'll take over the package. The RFH sent a few months ago is still valid, and I am happy to co-maintain the project with whoever is interested (Thomas, still there?). Still there yes but pretty busy with personnal stuff lately. Will try to do a bit of bug triaging / fixing this WE. Feel free to ping me from time to time when I don't give news. Cheers, Julien Cheers, Thomas Preud'homme signature.asc Description: This is a digitally signed message part.
Bug#611197: Missing build dependency on libgnome2-dev
It seems gpmudmon-applet is lacking a build-dependency on libgnome2-dev. signature.asc Description: This is a digitally signed message part.
Bug#610702: Pointer to official texts
Indeed, and the law stating this can be found in english at [1]. It's the article L. 113-9 (last one on the page) [1] http://195.83.177.9/code/liste.phtml?lang=ukc=36r=2495#art9764 signature.asc Description: This is a digitally signed message part.
Bug#608680: Only supported for x86 target
-march=native is only supported for (Intel 386 and AMD x86-64)-like targets. A simple solution would be to just disable this flag. Another option would be to populate CPPFLAGS in debian/rules with -march=native depending on the output of dpkg-architecture and the value of DEB_BUILD_OPTIONS. signature.asc Description: This is a digitally signed message part.
Bug#599674: buildd.debian.org: [p-a-s] tcc doesn't build on armel
Package: buildd.debian.org Severity: serious Tags: sid squeeze Justification: fails to build from source tcc has never built on armel due to a failure in the test suite. Could you replace the current line for tcc by this one: %tcc: i386 kfreebsd-i386 hurd-i386 amd64 kfreebsd-amd64 # C compiler. Thanks a lot and best regards. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537622: I got a fix
tag 537622 + pending thank you I got a patch for this issue. I just have to comment it so that I'll understand it in the future. I'll make an upload within 1 week. signature.asc Description: This is a digitally signed message part.
Bug#566930: Infos gathered
I'm not familiar with dpkg-divert so I could mistake but it seems it doesn't work as your script except since dpkg-divert with /usr/share/man/man8/cfdisk doesn't display anything while dpkg-divert with /usr/share/man/man8/cfdisk.8.gz does display something (see below) # dpkg -S /usr/share/man/man8/cfdisk.8.gz détournement par gnu-fdisk depuis : /usr/share/man/man8/cfdisk.8.gz détournement par gnu-fdisk en : /usr/share/man/man8/cfdisk.8.gz.distrib gnu-fdisk, util-linux: /usr/share/man/man8/cfdisk.8.gz and what seems the most interesting to me : # dpkg-divert --list /usr/share/man/man8/cfdisk # dpkg-divert --list /usr/share/man/man8/fdisk but # dpkg-divert --list /usr/share/man/man8/cfdisk.8.gz diversion of /usr/share/man/man8/cfdisk.8.gz to /usr/share/man/man8/cfdisk.8.gz.distrib by gnu-fdisk Best regards signature.asc Description: This is a digitally signed message part.
Bug#564851: More infos
I made some tests and it seems it comes from another part of xserver-xorg but I still don't know which one (evdev or the core xorg ?). I purged synaptics and the problem still happen with the additional mouse (package xserver-xorg- input-mouse is still installed). I forgot to mention that even if I let the pointer in the middle of the screen, it slightly move of a few pixels like what happen when there is a lack of sensibility on an optic mouse. Hope this help. signature.asc Description: This is a digitally signed message part.
Bug#562055: grub-common: Bashism in /etc/grub.d/30_os-prober
Package: grub-common
Version: 1.98~20091221-1
Severity: grave
Tags: patch
Justification: renders package unusable
Line 40 function osx_entry is defined as followed : function osx_entry {
This is a bashism and should be corrected to osx_entry() {
--- etc/grub.d/30_os-prober 2009-12-21 22:34:49.0 +0100
+++ /etc/grub.d/30_os-prober2009-12-22 10:42:47.0 +0100
@@ -37,7 +37,7 @@
exit 0
fi
-function osx_entry {
+osx_entry() {
cat EOF
menuentry ${LONGNAME} (${2}-bit) (on ${DEVICE}) {
EOF
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages grub-common depends on:
ii base-files 5.0.0 Debian base system miscellaneous f
ii dpkg 1.15.5.4 Debian package management system
ii gettext-base 0.17-8GNU Internationalization utilities
ii install-info 4.13a.dfsg.1-5Manage installed documentation in
ii libc6 2.10.2-2 GNU C Library: Shared libraries
ii libfreetype6 2.3.11-1 FreeType 2 font engine, shared lib
ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime
Versions of packages grub-common recommends:
ii os-prober 1.35 utility to detect other OSes on a
Versions of packages grub-common suggests:
pn grub-emu none (no description available)
pn multiboot-doc none (no description available)
-- no debconf information
--- etc/grub.d/30_os-prober 2009-12-21 22:34:49.0 +0100
+++ /etc/grub.d/30_os-prober2009-12-22 10:42:47.0 +0100
@@ -37,7 +37,7 @@
exit 0
fi
-function osx_entry {
+osx_entry() {
cat EOF
menuentry ${LONGNAME} (${2}-bit) (on ${DEVICE}) {
EOF
