Bug#669181: debhelper: Undefined subroutine Debian::Debhelper::Buildsystem::cmake::compat
Package: debhelper Version: 9.20120418 Severity: serious Hello: While using 9.20120418 with a package that uses compat 9 I get: Undefined subroutine Debian::Debhelper::Buildsystem::cmake::compat called at /usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm line 47. make[1]: *** [override_dh_auto_configure] Error 2 Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669188: locales: Please mark as Multi-Arch: foreign
Package: locales Version: 2.13-28 User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch Hello: When using an amd64 system and installing a i386 package that depends on locales, locales-all:i386 gets installed instead since locales is not Multi-Arch: foreign. The locales-all package is huge so this would help. The change is fairly trivial since the package is already arch: all. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669188: locales: Please mark as Multi-Arch: foreign
Package: locales Version: 2.13-28 User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch Hello: When using an amd64 system and installing a i386 package that depends on locales, locales-all:i386 gets installed instead since locales is not Multi-Arch: foreign. The locales-all package is huge so this would help. The change is fairly trivial since the package is already arch: all. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-glibc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caecnbvxnsuwrgp5yyr0asdffpnqp6mgy-chkgfkb9zseh-u...@mail.gmail.com
Bug#669181: debhelper: Undefined subroutine Debian::Debhelper::Buildsystem::cmake::compat
Package: debhelper Version: 9.20120418 Severity: serious Hello: While using 9.20120418 with a package that uses compat 9 I get: Undefined subroutine Debian::Debhelper::Buildsystem::cmake::compat called at /usr/share/perl5/Debian/Debhelper/Buildsystem/cmake.pm line 47. make[1]: *** [override_dh_auto_configure] Error 2 Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668967: awn-extras-applets: Please update to 0.4.1~bzr1539
Source: awn-extras-applets Version: 0.4.0-5 Severity: wishlist Tags: patch Hello: Could this package be updated to 0.4.1~bzr1539 in a similar fashion to avant-window-navigator that got updated to version 0.4.1~bzr830. This would help fix bug 619387 and 648412 since bzr1538 plus the attached DEP-3 quilt patch fixes those issues. Also I had other issues when using awn 0.4.1 with the 0.4.0 applets but I don't remember them anymore since I compiled both packages from upstream bzrr8XX and bzr15XX to fix it last year. Also the dependencies for awn-applets-c-core should probably include gnome-menus since cairo menu tries to read gnome-applications.menu and settings.menu (no longer exists) and does not display the menu while giving these messages: ** (awn-applet:30327): CRITICAL **: gmenu_tree_directory_get_contents: assertion `directory != NULL' failed ** (awn-applet:30327): CRITICAL **: gmenu_tree_item_unref: assertion `item != NULL' failed It could be a Recommends too. The gnome-menus packages currently gets installed via transitivity of recommended packages but it should be depended/recommended directly. Hope this helps, Miguel weather.patch Description: Binary data
Bug#663293: avant-window-navigator: upcoming vala 0.10 removal
Hello: Currently, Awn is only compatible with vala 0.10. It will at least need to migrate to GDBus. Actually it also compiles with vala 0.12 too. It fails with 0.14/0.16/etc as mentioned before. I compiled it earlier in an up to date sid amd64 chroot using gcc-4.6 and gcc-4.7. This should help close #665418 since this is the last block. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668963: avant-window-navigator: Please document the undocumented changes done to the source
Source: avant-window-navigator Version: 0.4.1~bzr830-2 Hello: It seems that the source was modified after being downloaded from bzr. If a pristine copy of upstream is not possible then these changes probably should be at least be documented in a README.source with an optional get-orig-source routine that reproduces the changes done by the maintainer. The diff from the original source in bzr is huge but if all that it was done before repackaging was this: rm -rf debian/ ./autogen.sh command to pregenerate the vala files Then most likely this could have been done from withing the rules files with the exception of the removal of the upstream debian folder. This is explained in better explained in DD reference 6.7.8.2 http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-origtargz and debian policy 4.9 for the get-orig-source target http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668849: dpkg-dev: Please add and use a DEB_DEBIAN_DIR variable in pkg-info.mk
Package: dpkg-dev
Version: 1.16.2
Severity: wishlist
Hello:
Debian policy 4.9 [1] says this about the get-orig-source target:
This target may be invoked in any directory, and should take care to
clean up any temporary files it may have left.
If one wants to use let say:
TARBALL = $(DEB_SOURCE)_$(DEB_VERSION_UPSTREAM).orig.tar.gz
and runs for example
mkdir -p temp cd temp ../debian/rules get-orig-source
This will generate several:
awk: cannot open debian/control (No such file or directory)
tail: cannot open `debian/changelog' for reading: No such file or directory
and the get-orig-source routine just keeps going as normal resulting
in possibly unwanted behavior.
One of the many possible uses for pkg-info.mk is to help with
get-orig-source routines. Currently I was testing something similar to
# Get the information needed by get-orig-source.
# include /usr/share/dpkg/pkg-info.mk
# This requires dpkg-dev = 1.16.1, hardcodes debian/{control,changelog} and
# makes get-orig-source fail when called from different paths.
DEB_DEBIAN_DIR = $(dir $(firstword $(MAKEFILE_LIST)))
DEB_SOURCE = $(shell dpkg-parsechangelog
-l$(DEB_DEBIAN_DIR)/changelog |\
awk '/^Source: / { print $$2 }')
DEB_VERSION_UPSTREAM= $(shell dpkg-parsechangelog
-l$(DEB_DEBIAN_DIR)/changelog |\
sed -nr '/^Version:/s/Version:
(.*:)?(.*)-(.*)/\2/p')
If possible adding a DEB_DEBIAN_DIR variable and
-l$(DEB_DEBIAN_DIR)/changelog to dpkg-parsechangelog in pkg-info.mk
should make the script work as before and with get-orig-source.
Also DEB_DEBIAN_DIR is useful if one uses something like
REMOVE_DFSG = $(DEB_DEBIAN_DIR)/get-orig-source-remove
where get-orig-source-remove contains a list of all the files and
directories to remove when making a source DFSG-free.
Hope this helps and makes sense,
Miguel
[1] http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#668849: dpkg-dev: Please add and use a DEB_DEBIAN_DIR variable in pkg-info.mk
Package: dpkg-dev
Version: 1.16.2
Severity: wishlist
Hello:
Debian policy 4.9 [1] says this about the get-orig-source target:
This target may be invoked in any directory, and should take care to
clean up any temporary files it may have left.
If one wants to use let say:
TARBALL = $(DEB_SOURCE)_$(DEB_VERSION_UPSTREAM).orig.tar.gz
and runs for example
mkdir -p temp cd temp ../debian/rules get-orig-source
This will generate several:
awk: cannot open debian/control (No such file or directory)
tail: cannot open `debian/changelog' for reading: No such file or directory
and the get-orig-source routine just keeps going as normal resulting
in possibly unwanted behavior.
One of the many possible uses for pkg-info.mk is to help with
get-orig-source routines. Currently I was testing something similar to
# Get the information needed by get-orig-source.
# include /usr/share/dpkg/pkg-info.mk
# This requires dpkg-dev = 1.16.1, hardcodes debian/{control,changelog} and
# makes get-orig-source fail when called from different paths.
DEB_DEBIAN_DIR = $(dir $(firstword $(MAKEFILE_LIST)))
DEB_SOURCE = $(shell dpkg-parsechangelog
-l$(DEB_DEBIAN_DIR)/changelog |\
awk '/^Source: / { print $$2 }')
DEB_VERSION_UPSTREAM= $(shell dpkg-parsechangelog
-l$(DEB_DEBIAN_DIR)/changelog |\
sed -nr '/^Version:/s/Version:
(.*:)?(.*)-(.*)/\2/p')
If possible adding a DEB_DEBIAN_DIR variable and
-l$(DEB_DEBIAN_DIR)/changelog to dpkg-parsechangelog in pkg-info.mk
should make the script work as before and with get-orig-source.
Also DEB_DEBIAN_DIR is useful if one uses something like
REMOVE_DFSG = $(DEB_DEBIAN_DIR)/get-orig-source-remove
where get-orig-source-remove contains a list of all the files and
directories to remove when making a source DFSG-free.
Hope this helps and makes sense,
Miguel
[1] http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667653: mpg123 FTBFS on armhf
I pulled that change into another 1.13 release, it is a bit different from your patch. Could you (peter?) test http://mpg123.org/download/mpg123-1.13.8.tar.bz2 if it builds now? I'll make it officialy public, then. Final report. I tested it with: --with-cpu=neon + -marm = WORKS --with-cpu=neon + -mthumb = WORKS --with-cpu=arm_nofpu + -marm= WORKS --with-cpu=arm_nofpu + -mthumb = WORKS Seems that using the new LSL notation was not needed and the old MOV with inline shift still work in this case. Regards, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667653: mpg123 FTBFS on armhf
I pulled that change into another 1.13 release, it is a bit different from your patch. Could you (peter?) test http://mpg123.org/download/mpg123-1.13.8.tar.bz2 if it builds now? I'll make it officialy public, then. Final report. I tested it with: --with-cpu=neon + -marm = WORKS --with-cpu=neon + -mthumb = WORKS --with-cpu=arm_nofpu + -marm= WORKS --with-cpu=arm_nofpu + -mthumb = WORKS Seems that using the new LSL notation was not needed and the old MOV with inline shift still work in this case. Regards, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#667653: mpg123 FTBFS on armhf
As mpg123 upstream it would be cool to get note of such issues without having to look for them in the debian bts. Having some bot subscribe and post to mpg123-de...@lists.sourceforge.net would be splendit; but if that is too troublesome, sending an info to maintai...@mpg123.org would be just as fine (using the generic address in case I vanish in future). But perhaps I overlooked a generic way to subscribe an address to all future reports. Hello: I have not tried it myself but I think this is what you are asking for: http://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system Section 4.10.1 explains the subscribe and the keyword options. I would filter out some of them since it would be too verbose IMO. Second: There is no inline assembly in mpg123. The file at hand (layer3.c) is plain C all around. So, without further data, I must assume that this is a bug in gcc that is worked around by adding -marm. You might consider asking gcc folks about this. I had some free time so I looked into this. The armhf architecture defaults to -mthumb instead of -marm and: 1) --with-cpu=arm_nofpu it fails with -mthumb and works with -marm (-DOPT_ARM -DREAL_IS_FIXED) 2) --with-cpu=neon it works with both. (-DOPT_NEON -DREAL_IS_FLOAT) This lead me to believe that it was most likely related to -DOPT_ARM. I saw that layer3.c includes #include mpg123lib_intern.h and that in that file there is a block: # elif defined(OPT_ARM) /* for arm */ # define REAL_MUL_ASM(x, y, radix) \ snip I patched this file by basically doing -# elif defined(OPT_ARM) +# elif defined(OxPT_ARxM) Without the patch it FTBFS but with the patch it builds. Looking at the ASM code it seems that these 2 asm block use PRE-UAL ARM syntax which only work in ARM and not thumb. The newer UAL syntax works with both. Here is a link that mentions some of the changes: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204j/Cjagjjbc.html Attached is a patch to really fix this and the orr problem with a header inside the patch explaining the changes. Using -marm was really a workaround to hide the problem but not a real solution to this and disabled all the advantages of using -mthumb. Reference for thumb2 instructions: http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001m/QRC0001_UAL.pdf Hope this helps, Miguel 0005-thumbs2.patch Description: Binary data
Bug#664998: Too much CPU used
I cannot reproduce that on my personal box. I have a Duron at 800 MHz with debian squeeze on it. Running mpg123 -v needs around 1% of CPU! There must be something else going on. Also please note that nowadays, the audio output happily gobbles up way more CPU than mpg123 needs. An example is the ALSA library resampling 44100 Hz material to 48000 Hz. Can you produce a profile of your CPU-consuming mpg123 (using the perf tool, for example)? Hello Santiago: One of the upstream authors replied to your bug report but forgot to CC you. This is email is just to relay the message. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#667653: mpg123 FTBFS on armhf
As mpg123 upstream it would be cool to get note of such issues without having to look for them in the debian bts. Having some bot subscribe and post to mpg123-de...@lists.sourceforge.net would be splendit; but if that is too troublesome, sending an info to maintai...@mpg123.org would be just as fine (using the generic address in case I vanish in future). But perhaps I overlooked a generic way to subscribe an address to all future reports. Hello: I have not tried it myself but I think this is what you are asking for: http://www.debian.org/doc/manuals/developers-reference/resources.html#pkg-tracking-system Section 4.10.1 explains the subscribe and the keyword options. I would filter out some of them since it would be too verbose IMO. Second: There is no inline assembly in mpg123. The file at hand (layer3.c) is plain C all around. So, without further data, I must assume that this is a bug in gcc that is worked around by adding -marm. You might consider asking gcc folks about this. I had some free time so I looked into this. The armhf architecture defaults to -mthumb instead of -marm and: 1) --with-cpu=arm_nofpu it fails with -mthumb and works with -marm (-DOPT_ARM -DREAL_IS_FIXED) 2) --with-cpu=neon it works with both. (-DOPT_NEON -DREAL_IS_FLOAT) This lead me to believe that it was most likely related to -DOPT_ARM. I saw that layer3.c includes #include mpg123lib_intern.h and that in that file there is a block: # elif defined(OPT_ARM) /* for arm */ # define REAL_MUL_ASM(x, y, radix) \ snip I patched this file by basically doing -# elif defined(OPT_ARM) +# elif defined(OxPT_ARxM) Without the patch it FTBFS but with the patch it builds. Looking at the ASM code it seems that these 2 asm block use PRE-UAL ARM syntax which only work in ARM and not thumb. The newer UAL syntax works with both. Here is a link that mentions some of the changes: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0204j/Cjagjjbc.html Attached is a patch to really fix this and the orr problem with a header inside the patch explaining the changes. Using -marm was really a workaround to hide the problem but not a real solution to this and disabled all the advantages of using -mthumb. Reference for thumb2 instructions: http://infocenter.arm.com/help/topic/com.arm.doc.qrc0001m/QRC0001_UAL.pdf Hope this helps, Miguel 0005-thumbs2.patch Description: Binary data ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#664998: Too much CPU used
I cannot reproduce that on my personal box. I have a Duron at 800 MHz with debian squeeze on it. Running mpg123 -v needs around 1% of CPU! There must be something else going on. Also please note that nowadays, the audio output happily gobbles up way more CPU than mpg123 needs. An example is the ALSA library resampling 44100 Hz material to 48000 Hz. Can you produce a profile of your CPU-consuming mpg123 (using the perf tool, for example)? Hello Santiago: One of the upstream authors replied to your bug report but forgot to CC you. This is email is just to relay the message. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mpg123/master: Add -marm to CFLAGS to fix FTBFS on armhf.
Add -marm to CFLAGS to fix FTBFS on armhf. Closes: #667658 Thanks: peter green for the patch. Hello: I already had fixed this FTBFS by adding this: ifeq ($(ARCH),armhf) CONF_arm:=--with-cpu=neon CFLAGS += -mfpu=neon endif This also added the optimizations that you wanted the package to build with earlier but had FTBFS since Debian uses -mfpu=vfpv3-d16 by default. The patch was only needed if --with-cpu=arm_nofpu since the git branch before the patch did not FTBFS. If the idea was to be able to build with the current default --with-cpu=neon OR with a user selected --with-cpu=arm_nofpu then it could have been added inside the current IF as CFLAGS += -mfpu=neon -marm instead of adding another IF check. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#666987: dpkg-buildflags: DEB_*_MAINT_* overrides user options.
Package: dpkg-dev
Version: 1.16..2
Hello:
I noticed that some of the options I set in DEB_BUILD_OPTIONS and
DEB_*_APPEND get overriden by DEB_*_MAINT_*.
Also I noticed http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653846
seems to suggest to set
DEB_CFLAGS_MAINT_APPEND=-Os
DEB_CFLAGS_MAINT_APPEND=-O3
for when one wants to override the default optimization level and from
what I remember there are some packages that do this.
The problem is that when the user wants to do:
DEB_BUILD_OPTIONS=noopt dpkg-buildpackage -b
DEB_CFLAGS_APPEND=-O0 dpkg-buildpackage -b
or even try to cheat and do
DEB_CFLAGS_MAINT_APPEND=-O0 dpkg-buildpackage -b
the DEB_*_MAINT_* in the rules file takes priority (DEB_*_MAINT_APPEND
basically overrides anything) since it get added after the -O0 and it
needs to be changed manually in the rules file.
I would guess the DEB_BUILD_OPTIONS=noopt problem should be reported
against the package that suffer from this case but should not the user
options in
DEB_flag_* (or $XDG_CONFIG_HOME/dpkg/buildflags.conf) override the
DEB_flag_MAINT_* equivalent?
If I change BuildFlags.pm
from:
sub load_config {
my ($self) = @_;
$self-load_system_config();
$self-load_user_config();
$self-load_environment_config();
$self-load_maintainer_config();
}
to:
sub load_config {
my ($self) = @_;
$self-load_system_config();
$self-load_user_config();
$self-load_maintainer_config();
$self-load_environment_config();
}
At least the DEB_CFLAGS_APPEND=-O0 dpkg-buildpackage -b case works.
-Miguel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666987: dpkg-buildflags: DEB_*_MAINT_* overrides user options.
I'm not sure what the proper approach would be. On the other hand, I'm not entirely convinced that it's important to let the user have the last word in cases where maintainers have opted for a specific optimization level: - building with -Os is typically made for udeb and I don't see a compelling reason to have the possibility to change the maintainer choice via the environment variable - building with -O3 is often picked as a work-around when -O2 doesn't give the expected result, why would you want to pick another optimization level? if you want -O0, then it's the noopt option that you should be using Well any flag not only optimization levels are affected but -OX is probably the most common case. Also some packages do export DEB_CFLAGS_MAINT_SET=$(dpkg-buildflags --get CFLAGS) which makes the -02 and the other flags permanent. Anyway I just wanted to be able to be sure that the flags I wanted to use for testing or building a local package for my system where actually used without having to manually check each source to see if there is a DEB_*_MAINT_* now or in the future that disables those flags. I think the user should have the last say when building locally since the user is willingly trying to use a flag locally but the current method just adds the annoyance of either having to modify the rules file, modify the BuildFlags.pm file or creating a gcc/g++ wrapper. -Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666987: dpkg-buildflags: DEB_*_MAINT_* overrides user options.
Well any flag not only optimization levels are affected but -OX is probably the most common case. Any flag that allow overriding a previous value of the same flag and that maintainers are likely to change... wich doesn't make many. True, I was also thinking about the silly case when someone used DEB_*_MAINT_SET which I would guess break noopt and disable any user flag. Also some packages do export DEB_CFLAGS_MAINT_SET=$(dpkg-buildflags --get CFLAGS) which makes the -02 and the other flags permanent. This is a pretty stupid thing to do. What package is doing this? Is there a reason given? In any case, feel free to open a bug against the affected packages. Oh I was trying to search how many packages currently use DEB_*_MAINT_* options and found that one with a web search. I did not try an exhaustive search (should not be that many anyway) since it was 5am and this is more of a wishlist type of change since from the original email I gathered that this behavior was intentional by dpkg. The package that did this was http://packages.debian.org/sid/crash from what I remember. I will open the bug when I get home in a couple of hours if there is none. But obviously if you put yourself not as a user who needs the resulting package, but as a developer who is doing tests to see how many packages break with a given flag, then this decision might annoy you. True, I noticed this testing some packages with gcc-4.7 and custom flags with a custom pbuilder script. I was trying to remove the ugly gcc-wrapper that I used to insert/remove flags and try a cleaner approach and then found this. We can invert the order between the maintainer environment variable and the user environment variable but I'd like the input of others because I can't really make up my mind on whether it's right and a realy useful thing to do. This sounds reasonable, thanks!. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666987: dpkg-buildflags: DEB_*_MAINT_* overrides user options.
Package: dpkg-dev
Version: 1.16..2
Hello:
I noticed that some of the options I set in DEB_BUILD_OPTIONS and
DEB_*_APPEND get overriden by DEB_*_MAINT_*.
Also I noticed http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=653846
seems to suggest to set
DEB_CFLAGS_MAINT_APPEND=-Os
DEB_CFLAGS_MAINT_APPEND=-O3
for when one wants to override the default optimization level and from
what I remember there are some packages that do this.
The problem is that when the user wants to do:
DEB_BUILD_OPTIONS=noopt dpkg-buildpackage -b
DEB_CFLAGS_APPEND=-O0 dpkg-buildpackage -b
or even try to cheat and do
DEB_CFLAGS_MAINT_APPEND=-O0 dpkg-buildpackage -b
the DEB_*_MAINT_* in the rules file takes priority (DEB_*_MAINT_APPEND
basically overrides anything) since it get added after the -O0 and it
needs to be changed manually in the rules file.
I would guess the DEB_BUILD_OPTIONS=noopt problem should be reported
against the package that suffer from this case but should not the user
options in
DEB_flag_* (or $XDG_CONFIG_HOME/dpkg/buildflags.conf) override the
DEB_flag_MAINT_* equivalent?
If I change BuildFlags.pm
from:
sub load_config {
my ($self) = @_;
$self-load_system_config();
$self-load_user_config();
$self-load_environment_config();
$self-load_maintainer_config();
}
to:
sub load_config {
my ($self) = @_;
$self-load_system_config();
$self-load_user_config();
$self-load_maintainer_config();
$self-load_environment_config();
}
At least the DEB_CFLAGS_APPEND=-O0 dpkg-buildpackage -b case works.
-Miguel
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666987: dpkg-buildflags: DEB_*_MAINT_* overrides user options.
I'm not sure what the proper approach would be. On the other hand, I'm not entirely convinced that it's important to let the user have the last word in cases where maintainers have opted for a specific optimization level: - building with -Os is typically made for udeb and I don't see a compelling reason to have the possibility to change the maintainer choice via the environment variable - building with -O3 is often picked as a work-around when -O2 doesn't give the expected result, why would you want to pick another optimization level? if you want -O0, then it's the noopt option that you should be using Well any flag not only optimization levels are affected but -OX is probably the most common case. Also some packages do export DEB_CFLAGS_MAINT_SET=$(dpkg-buildflags --get CFLAGS) which makes the -02 and the other flags permanent. Anyway I just wanted to be able to be sure that the flags I wanted to use for testing or building a local package for my system where actually used without having to manually check each source to see if there is a DEB_*_MAINT_* now or in the future that disables those flags. I think the user should have the last say when building locally since the user is willingly trying to use a flag locally but the current method just adds the annoyance of either having to modify the rules file, modify the BuildFlags.pm file or creating a gcc/g++ wrapper. -Miguel -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666987: dpkg-buildflags: DEB_*_MAINT_* overrides user options.
Well any flag not only optimization levels are affected but -OX is probably the most common case. Any flag that allow overriding a previous value of the same flag and that maintainers are likely to change... wich doesn't make many. True, I was also thinking about the silly case when someone used DEB_*_MAINT_SET which I would guess break noopt and disable any user flag. Also some packages do export DEB_CFLAGS_MAINT_SET=$(dpkg-buildflags --get CFLAGS) which makes the -02 and the other flags permanent. This is a pretty stupid thing to do. What package is doing this? Is there a reason given? In any case, feel free to open a bug against the affected packages. Oh I was trying to search how many packages currently use DEB_*_MAINT_* options and found that one with a web search. I did not try an exhaustive search (should not be that many anyway) since it was 5am and this is more of a wishlist type of change since from the original email I gathered that this behavior was intentional by dpkg. The package that did this was http://packages.debian.org/sid/crash from what I remember. I will open the bug when I get home in a couple of hours if there is none. But obviously if you put yourself not as a user who needs the resulting package, but as a developer who is doing tests to see how many packages break with a given flag, then this decision might annoy you. True, I noticed this testing some packages with gcc-4.7 and custom flags with a custom pbuilder script. I was trying to remove the ugly gcc-wrapper that I used to insert/remove flags and try a cleaner approach and then found this. We can invert the order between the maintainer environment variable and the user environment variable but I'd like the input of others because I can't really make up my mind on whether it's right and a realy useful thing to do. This sounds reasonable, thanks!. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: [SCM] mpg123/master: Pass --with-cpu=arm_nofpu to configure for armhf too.
On Sun, Apr 1, 2012 at 4:26 AM, ales...@users.alioth.debian.org wrote: The following commit has been merged in the master branch: commit 726c947f2edde84a0a86ed972cb61a5e669501b7 Author: Alessio Treglia ales...@debian.org Date: Sun Apr 1 10:25:41 2012 +0200 Pass --with-cpu=arm_nofpu to configure for armhf too. diff --git a/debian/rules b/debian/rules index bc8a8cd..9f82935 100755 --- a/debian/rules +++ b/debian/rules @@ -17,13 +17,7 @@ CONF_COMMON:=--enable-static=no --enable-shared --enable-lfs-alias \ --with-module-suffix=.so CONF_i486:=--with-cpu=x86_dither -ifeq ($(ARCH),armel) CONF_arm:=--with-cpu=arm_nofpu -else -ifeq ($(ARCH),armhf) -CONF_arm:=--with-cpu=neon -endif -endif SOVERSION:=0 LIB_PKG:=libmpg123-$(SOVERSION) -- mpg123 packaging ___ pkg-multimedia-commits mailing list pkg-multimedia-comm...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-commits Hello: To make this work you could have done: ifeq ($(ARCH),armhf) CONF_arm:=--with-cpu=neon CFLAGS += -mfpu=neon endif and moved ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mpg123/master: Pass --with-cpu=arm_nofpu to configure for armhf too.
Hello: To make this work you could have done: ifeq ($(ARCH),armhf) CONF_arm:=--with-cpu=neon CFLAGS += -mfpu=neon endif and moved (Not sure why the email got sent before I was done.) CPPFLAGS:=$(shell dpkg-buildflags --get CPPFLAGS) CFLAGS:=$(shell dpkg-buildflags --get CFLAGS) CXXFLAGS:=$(shell dpkg-buildflags --get CXXFLAGS) LDFLAGS:=$(shell dpkg-buildflags --get LDFLAGS) to the top or at least above the if statement. I had made the change really quick but did not commit it since I wanted to test it first with qemu first but by the time I finished I had fallen asleep (took way longer to make qemu work than to compile, heh). Anyway reverting the optimization or adding the -mfpu flag works. - Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#666438: gtest: Could the CMakeLists.txt be shipped?
Source: gtest Version: 1.6.0-1 Severity: wishlist Hello: Since the autotools scripts are deprecated, could the cmake scripts be shipped similar to Ubuntu? Besides the wont-fix bug that won't matter after the static libraries get removed, this is the only change from Ubuntu left. Below is the diff and the changelog entries related to it. -Miguel gtest (1.6.0-1ubuntu4) precise; urgency=low * debian/libgtest-dev.install: - also add the cmake subdirectory as it's needed by CMakeLists.txt -- Didier Roche didro...@ubuntu.com Thu, 08 Mar 2012 16:26:48 +0100 gtest (1.6.0-1ubuntu3) precise; urgency=low * debian/libgtest-dev.install: - ship the CMakeLists.txt in /usr/src/gtest/ to enable inclusion in cmake project now that we don't distribute static library. (ideally that would go in the cmake directory and we will generate the file to look at /usr/src/gtest/) -- Didier Roche didro...@ubuntu.com Thu, 08 Mar 2012 13:52:03 +0100 gtest (1.6.0-1ubuntu2) precise; urgency=low * Stop distributing static library (although still build it, to ensure gtest works). Upstream recommends against shipping the libary at all, just the source. (See: http://code.google.com/p/googletest/wiki/FAQ) The Debian maintainer plans to do this also (see BTS: 639795); do it in Ubuntu now to fulfil MIR requirements. -- Christopher James Halse Rogers r...@ubuntu.com Thu, 08 Mar 2012 17:45:29 +1100 diff -pruN 1.6.0-1/debian/libgtest-dev.install 1.6.0-1ubuntu4/debian/libgtest-dev.install --- 1.6.0-1/debian/libgtest-dev.install 2011-06-12 17:28:34.0 + +++ 1.6.0-1ubuntu4/debian/libgtest-dev.install 2012-03-08 15:22:38.0 + @@ -1,4 +1,4 @@ -*/libgtest.a usr/lib -*/libgtest_main.a usr/lib include/gtest usr/include src usr/src/gtest +CMakeLists.txt usr/src/gtest +cmake usr/src/gtest -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666439: google-mock: Could the CMakeLists.txt be shipped?
Source: google-mock Version: 1.6.0-1 Severity: wishlist Hello: Since the autotools scripts are deprecated, could the cmake scripts be shipped similar to the way Ubuntu does with libgtest-dev? Adding CMakeLists.txt usr/src/gmock to the google-mock.install or something similar would be nice. A note from the gtest changelog (since it's related to this request): * debian/libgtest-dev.install: - ship the CMakeLists.txt in /usr/src/gtest/ to enable inclusion in cmake project now that we don't distribute static library. (ideally that would go in the cmake directory and we will generate the file to look at /usr/src/gtest/) -Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666440: pbuilder: echobacktime: command not found
Hello: echobacktime is defined in /usr/lib/pbuilder/pbuilder-buildpackage-funcs therefore adding the missing: . /usr/lib/pbuilder/pbuilder-buildpackage-funcs to the affected: /usr/lib/pbuilder/pbuilder-createbuildenv /usr/lib/pbuilder/pbuilder-updatebuildenv should fix this until it gets properly fixed by a new upload. Hope this helps, -Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#666440: pbuilder: echobacktime: command not found
Hello: echobacktime is defined in /usr/lib/pbuilder/pbuilder-buildpackage-funcs therefore adding the missing: . /usr/lib/pbuilder/pbuilder-buildpackage-funcs to the affected: /usr/lib/pbuilder/pbuilder-createbuildenv /usr/lib/pbuilder/pbuilder-updatebuildenv should fix this until it gets properly fixed by a new upload. Hope this helps, -Miguel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651223: gtk2-engines-murrine: add multiarch support
reopen 651223 ! Hello: It seems you forgot to add Multi-Arch: same in the control file. The rest seems fine. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664967: Segfaulting is caused by copyObject in version 0.12.1-3
Hello: I managed to reproduce the segfaults and I believe I just fixed this in the version available in the git repository. If you want, you can try to compile it and report if it fixed your issue. The following or something similar should work for building the packages: sudo apt-get install git git clone git://anonscm.debian.org/pkg-multimedia/mediatomb.git sudo apt-get build-dep mediatomb cd mediatomb sed -i s/(0.12.1-4)/(0.12.1-4~local1)/g debian/changelog dpkg-buildpackage -b cd .. sudo dpkg -i mediatomb_*_all.deb mediatomb-common_*.deb mediatomb-daemon_*_all.deb Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#664967: Segfaulting is caused by copyObject in version 0.12.1-3
Hello: I managed to reproduce the segfaults and I believe I just fixed this in the version available in the git repository. If you want, you can try to compile it and report if it fixed your issue. The following or something similar should work for building the packages: sudo apt-get install git git clone git://anonscm.debian.org/pkg-multimedia/mediatomb.git sudo apt-get build-dep mediatomb cd mediatomb sed -i s/(0.12.1-4)/(0.12.1-4~local1)/g debian/changelog dpkg-buildpackage -b cd .. sudo dpkg -i mediatomb_*_all.deb mediatomb-common_*.deb mediatomb-daemon_*_all.deb Hope this helps, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#567484: pbuilder: -e$DEBEMAIL instead of -e$DEBFULLNAME
That makes sense: with no args, dpkg-buildpackage does the right thing if DEBEMAIL is set and DEBFULLNAME is set. So let the work be done by dpkg-buildpackage. I’ve found that most Debian tools work best if DEBFULLNAME is not set and DEBEMAIL is Foo Bar f...@debian.org. Only tool that gives me issues using the DEBFULLNAME / DEBEMAIL correctly is pbuilder. But that is rather off-topic The issue is rather simple. If I send a package to build with pbuilder even with hooks to modify the source and to add a new changelog entry it should always reach the dpkg-buildpackage line with a valid FULLNAME/EMAIL in the last changelog entry. Why are we running the -e option to change the behavior of dpkg-genchanges? -emaintaineraddress Use maintaineraddress as the name and email address of the maintainer for this upload, rather than using the information from the source tree's changelog. The package was changed by the person in the last entry of the changelog not the value of whatever you decide to put in DEBEMAIL therefore the Changed-by tag should be as the default dpkg-buildpackage/dpkg-genchanges behavior does. The only reason I patch this is so that the lintian hook that I run do not give me a failure due to a silly E: caused by pbuilder using the -e option without an apparent need. -Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567484: pbuilder: -e$DEBEMAIL instead of -e$DEBFULLNAME
tags: patch
Some more info:
jcdubacq pbuilder does that:DPKG_COMMANDLINE=dpkg-buildpackage -us -uc
${DEBEMAIL:+\-e$DEBEMAIL\} $DEBBUILDOPTS
jcdubacq whereas it should do that: DPKG_COMMANDLINE=dpkg-buildpackage -us
-uc ${DEBEMAIL:+${DEBFULLNAME:+\-e$DEBFULLNAME $DEBEMAIL\}} $DEBBUILDOPTS
jcristau jcdubacq: no it should not use that at all
jcdubacq some hours ago, I was told DEBEMAIL should be only the address
jcristau correct.
jcdubacq if only the address is in DEBEMAIL, lintian says
changed-by-name-missing
jcristau but there's no reason for pbuilder to use dpkg-buildpackage -e
That makes sense: with no args, dpkg-buildpackage does the right thing
if DEBEMAIL is set and DEBFULLNAME is set.
So let the work be done by dpkg-buildpackage.
Hello
Any updates on this? As stated in the previous comment in this bug
report dpkg-buildpackage does the right thing without parameters. I
have used the attached trivial patch and reapplied after every upgrade
to the package for almost 2 years and it works fine.
Hope this helps,
Miguel
--- /usr/lib/pbuilder/pbuilder-buildpackage.orig 2011-01-21 14:34:39.0 -0500
+++ /usr/lib/pbuilder/pbuilder-buildpackage 2011-01-21 14:35:26.0 -0500
@@ -122,7 +122,7 @@
executehooks A
-DPKG_COMMANDLINE=env PATH=\$PATH\ dpkg-buildpackage -us -uc ${DEBEMAIL:+\-e$DEBEMAIL\} $DEBBUILDOPTS
+DPKG_COMMANDLINE=env PATH=\$PATH\ dpkg-buildpackage -us -uc $DEBBUILDOPTS
(
: Build process
Compiz 0.9.7.0 + 0.9.5.92 packaging.
Hello: I noticed a while back that the packages for compiz in sid are outdated and the packages in experimental don't even install for various reason. While browsing the web I learned that upstream went through some changes to say the least and moved their development to launchpad. Coincidentally, they had just released a new version when I checked. I'm not entirely sure if they consider 0.9.7.0 a stable release or not but they released it on 03/02 (core) and 03/03 (plugins) [1][2][3]. Like a lot of software lately that I use (wine 1.4, emerald (not sure why it got removed), 20 or so multiarchified packages so I can install wine and kill ia32-libs, etc), I decided to package it for my personal use. While doing this I learned how much of a pain/mess the way upstream organize their software is. Also after trying to figure out why they kept merging old code over new code destroying their fixes and other issues, I decided to share the packaging that I did. Some good must come out of this heh. I uploaded the 6 packages to https://github.com/micove . I did not package compiz-fusion-bcop and compiz-fusion-plugins-unsupported since they are basically dead upstream. Also I did not package compizconfig-backend-kconfig since it seems dead and the KDE portion of compiz apparently is not being worked on upstream and it's broken/needs fixing from what I read. The last one is compizconfig-backend-gconf which I never use and with the removal of the compiz-gnome package by the NMU in sid, I mentally moved it with the other 3 into the dead/unsupported category. They seem to be systematically shrinking and only really working on core [1] while the other packages are rarely updated. There could be some issues with the packages. From the top of my head: - I did not update the standard versions since I was not sure if DEP5 was required. -The settings are now moved from a compiz folder to a compiz-1 folder and I believe they don't get passed to the new version. From what I remember, Ubuntu used to have a patch or something to move the settings not sure. - I acknowledged the sid NMU while doing an NMU which is rather silly but I left it in. - Some minor issues like splitting the compiz-core package which is 98% data, making up a better package name for the new library or patching some of the random lintian Info or Pedantic that I saw. - The release closes a lot of bugs from the tracker but I did not have time to go through the combined list of the bugs for the packages. From the ones I saw the RC ones are fixed. I have been running it using the emerald wm for a day or two and after changing a few settings via patching to workaround a few bugs (ok a lot of segfaults and impressive complete system locks), It seems to behave nicely if I forget about the increased cpu usage. I only enable the plugins I need so my experience may not be really representative. I tried to document everything I did in the commit messages and patch headers and made the changelogs fairly verbose. Hope this helps, Miguel P.S. I'm not part of the mailing list so please CC me. [1] https://launchpad.net/compiz-core [2] https://launchpad.net/compiz-plugins-main [3] https://launchpad.net/compiz-plugins-extra -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAEcnbVzHS=-eYFGR2BDkCxOWgYb0tWMvcZbH=vs_jnjvn_n...@mail.gmail.com
Accepted soundtouch 1.6.0-3 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Mar 2012 21:03:50 -0500 Source: soundtouch Binary: libsoundtouch-dev libsoundtouch0 libsoundtouch0-dbg soundstretch soundstretch-dbg Architecture: source amd64 Version: 1.6.0-3 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Miguel Colon debian.mic...@gmail.com Description: libsoundtouch-dev - Development files for the sound stretching library libsoundtouch0 - Sound stretching library libsoundtouch0-dbg - Debugging symbols for the sound stretching library soundstretch - Stretches and pitch-shifts sound independently soundstretch-dbg - Debugging symbols for the soundstretch program Changes: soundtouch (1.6.0-3) unstable; urgency=low . * debian/copyright: - Fix the syntax in the license paragraph. - Update copyright years. - Update to finalized DEP-5 copyright-format 1.0. * Bump Standards-Version to 3.9.3. * Bump the debhelper version and compatibility level to 9. - Adds hardening support. - Drops the need to explicitly use DEB_HOST_MULTIARCH in the rules file. * Mark libsoundtouch-dev as Multi-Arch: same. Checksums-Sha1: 53ff53408eb36e76ada36fd702075fa858a940e1 2221 soundtouch_1.6.0-3.dsc 9871dcbf75a68665a3515bb9dda4727beb0358e7 94852 soundtouch_1.6.0.orig.tar.gz 288b50c833171cda6f7664bed95aa076df30c14f 7985 soundtouch_1.6.0-3.debian.tar.gz 43992cfa8c2f8c591538d8ea89bec8fd5fdf1695 12608 libsoundtouch-dev_1.6.0-3_amd64.deb 57f2e6e2a6835f0482d32ad946761cc9f4aca058 40854 libsoundtouch0_1.6.0-3_amd64.deb 339b8ccd45344326c038f5262852cac06e058eba 70592 libsoundtouch0-dbg_1.6.0-3_amd64.deb 85ed0f58f6476bd37f808daa45ad4f6987e6d2cd 30164 soundstretch_1.6.0-3_amd64.deb f58fe94197ab782bc5f6a47cc046538a5b632f44 40100 soundstretch-dbg_1.6.0-3_amd64.deb Checksums-Sha256: 4c1e2c18e00b2d4ca15a14541aa45ac922d25f7a98346a4462dbd2e2d763c051 2221 soundtouch_1.6.0-3.dsc 8776edaf7299ffe1e8c97285f020365a63c0e01aa4f6f7c5fd1d011c0ded278f 94852 soundtouch_1.6.0.orig.tar.gz 9e6df4c093dfffc90c7213456086567f4ced09ba767549d047df1099e3e2e6ad 7985 soundtouch_1.6.0-3.debian.tar.gz da96918e027bdacc4528c313dc9646e4210c798ebef295247aa305d1e5f9df71 12608 libsoundtouch-dev_1.6.0-3_amd64.deb c9bbc7b36deccc0b362eb8da88700609ac1dee6f752ac5866c39826187fcdb81 40854 libsoundtouch0_1.6.0-3_amd64.deb c16d3d26dae0bf92de4b991e51d7cdba37d5b98b897290746d7cb4cc1ccf3085 70592 libsoundtouch0-dbg_1.6.0-3_amd64.deb 2b27b433afad904023e46076c8c21ff33680489ddcba6b4bd3572153c63a3c4e 30164 soundstretch_1.6.0-3_amd64.deb dbe3d74ca34069b81830a9384c5bfe651ac9dc9d81ca05accbd46bd894eac89e 40100 soundstretch-dbg_1.6.0-3_amd64.deb Files: 41fee97ba41dd39fc20f03f146c1eb18 2221 libs optional soundtouch_1.6.0-3.dsc aa1c63d4d67b033f044a6a48d2be5bdd 94852 libs optional soundtouch_1.6.0.orig.tar.gz bc07b8c89d607ed39e849457946888ac 7985 libs optional soundtouch_1.6.0-3.debian.tar.gz 5069ffcdfd43f840e69bdbf4a64c418f 12608 libdevel optional libsoundtouch-dev_1.6.0-3_amd64.deb bf1eeaf084d9e91307ab02f1a1d693f1 40854 libs optional libsoundtouch0_1.6.0-3_amd64.deb 70af5ebafdd22249ed67652844992cd3 70592 debug extra libsoundtouch0-dbg_1.6.0-3_amd64.deb 18f82d7cbf5c2d3a02ae16f68e8c1eef 30164 sound optional soundstretch_1.6.0-3_amd64.deb 9c814fdee0f3d4546052f20eff7bb126 40100 debug extra soundstretch-dbg_1.6.0-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCgAGBQJPWUYeAAoJEOikiuUxHXZawxoP/R2qXZ/Wt9aO1XjtiOWeIy+h eM/i7gYBnl0MtUz8+j0rnAHn64+HSD/3y5bLgjAFNn7Dq3JfpeFhV01SzVI3iCqd I13plomY/bAsYEDm/fgWT4odvKjC8KowdQ97H/N8VnVm/x4S1ojtczRy97uIT8Uo cCGkfn0OV++1z8reszXcTkvq9W5E6nTtLAUblLaEAesHTahn/cI42Urv2BjwszPk lpvei/4VjlORY0aZFfRrCVTdC1zMClhDRZMEY+ABI+nIZIGXw7l/rgm44Evd73/L BVnMS9kFEB3UJep0ZPaqaVrbi7EV9l8ArcOmUMtmGYn3EAHKbD5TJNlSAjoT9JDz R75fILOLQnjwNdcl7ymIzpbmKbIsSa3RlG6mE/TAXPimRQpFDCy8PiJTpj1maVpd EJxcTB6Z2iMr3lZlEwOILJAhYrqHbPjqnqYUM6G1EgaDGUxIfbwd1YyGtWcxeIhW O00hIxGrJLIjn+EP5wmWJe/2UH/teWIZzxMH5iVRADkzvJnRJ2Dx/6Ms0EAnG7SF tQ8GPciRvge31toDLsnvhSodZ9i2c8jXIdRgeVDf4rP7q5TEW0dQ5e8Nrhau4AIf kH8ylvO40+vzStweBZm1IRYTNM+DV4/AqwgCtQpXGenVNL1jcdxDnv9vmiE9Rk95 RQo7mVDKvDD39Oxtt+eN =Lk5O -END PGP SIGNATURE- Accepted: libsoundtouch-dev_1.6.0-3_amd64.deb to main/s/soundtouch/libsoundtouch-dev_1.6.0-3_amd64.deb libsoundtouch0-dbg_1.6.0-3_amd64.deb to main/s/soundtouch/libsoundtouch0-dbg_1.6.0-3_amd64.deb libsoundtouch0_1.6.0-3_amd64.deb to main/s/soundtouch/libsoundtouch0_1.6.0-3_amd64.deb soundstretch-dbg_1.6.0-3_amd64.deb to main/s/soundtouch/soundstretch-dbg_1.6.0-3_amd64.deb soundstretch_1.6.0-3_amd64.deb to main/s/soundtouch/soundstretch_1.6.0-3_amd64.deb soundtouch_1.6.0-3.debian.tar.gz to main/s/soundtouch/soundtouch_1.6.0-3.debian.tar.gz soundtouch_1.6.0-3.dsc to main/s/soundtouch/soundtouch_1.6.0-3.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org
Bug#663046: schroedinger: Add multiarch support.
Source: schroedinger Version: 1.0.11-1 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663097: libxvbaw1: Marked as Multi-Arch same but files conflict.
Package: libxvbaw1 Version: 1:12-2-1 Severity: important Hello: While upgrading my amd64 system I encountered this: $ sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: libxvbaw1:i386 The following packages will be upgraded: libxvbaw1:i386 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 24 not fully installed or removed. Need to get 0 B/2,947 kB of archives. After this operation, 1,010 kB of additional disk space will be used. Do you want to continue [Y/n]? y (Reading database ... 136919 files and directories currently installed.) Preparing to replace libxvbaw1:i386 1:12-1-2 (using .../libxvbaw1_1%3a12-2-1_i386.deb) ... Unpacking replacement libxvbaw1:i386 ... dpkg: error processing /var/cache/apt/archives/libxvbaw1_1%3a12-2-1_i386.deb (--unpack): './usr/lib/libAMDXvBA.cap' is different from the same file on the system configured to not write apport reports dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) I checked the md5sum file: 18f4b310029adb9a9f216111909b1198 usr/lib/libAMDXvBA.cap a42b0601f270df829ca75a8e63b07005 usr/lib/x86_64-linux-gnu/libAMDXvBA.so.1.0 4d93a79e7eeec6408edc97bcae28a762 usr/lib/x86_64-linux-gnu/libXvBAW.so.1.0 a4734823a3a954ba1473edf8f98987f9 usr/lib/libAMDXvBA.cap 73d48657356711ce9edc7ba7a8382dc0 usr/lib/i386-linux-gnu/libAMDXvBA.so.1.0 7da87e5f5f46c7dc7a85fa27731cf708 usr/lib/i386-linux-gnu/libXvBAW.so.1.0 Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663046: schroedinger: Add multiarch support.
Source: schroedinger Version: 1.0.11-1 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel ___ pkg-gstreamer-maintainers mailing list pkg-gstreamer-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gstreamer-maintainers
[Pkg-phototools-devel] Bug#663045: openjpeg: Add multiarch support.
Source: openjpeg Version: 1.3+dfsg-4 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel ___ Pkg-phototools-devel mailing list Pkg-phototools-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-phototools-devel
Bug#661095: pulseaudio: pulse-alsa.conf show is not a compound
Hello: Just to add some information about this: They don't provide further details so I downloaded a few versions of their pulseaudio package and compared the configuration files. The older Ubuntu versions of pulseaudio have the same broken pulse-alsa.conf file as Sid does. The newest version has this instead: snip The new configuration file seems to solve the problem on my Sid system. Probably making the same change as was done in Ubuntu would be reasonable. The file included in Ubuntu is basically the file 99-pulseaudio-default.conf.example included in the package libasound2-plugins and installed at /usr/share/alsa/alsa.conf.d/99-pulseaudio-default.conf.example but they use the description from the old pulse-alsa.conf file and still included in the Debian package. I have used for several years the attached file saved as ~/.asoundrc since pulseaudio was giving me trouble long ago. It is basically /usr/share/alsa/alsa.conf.d/50-pulseaudio.conf /usr/share/alsa/alsa.conf.d/99-pulseaudio-default.conf.example both in 1 file. I think I first read the explanation for each file from http://www.pulseaudio.org/wiki/PerfectSetup#ALSAApplications when I first used the attached file. The 50-pulseaudio.conf part is redundant since it just add a name therefore using only the 99-pulseaudio-default.conf.example file as used in Ubuntu should be fine too. Hope this helps, Miguel pulse-alsa.conf Description: Binary data
Bug#663039: directfb: Add multiarch support.
Source: directfb Version: 1.2.10.0-4.3 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663040: sysfsutils: Add multiarch support.
Source: sysfsutils Version: 2.1.0+repack-1 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663042: celt: Add multiarch support.
Source: celt Version: 0.7.1-1 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663043: gtk3-engines-unico: Add multiarch support.
Source: gtk3-engines-unico Version: 1.0.1-1 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663044: libgsm: Add multiarch support.
Source: libgsm Version: 1.0.13-3 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663045: openjpeg: Add multiarch support.
Source: openjpeg Version: 1.3+dfsg-4 Hello: Please make this package compatible with multiarch, as described at http://wiki.debian.org/Multiarch/Implementation. More info: http://wiki.debian.org/ReleaseGoals/MultiArch Thanks, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661095: pulseaudio: pulse-alsa.conf show is not a compound
Hello: Just to add some information about this: They don't provide further details so I downloaded a few versions of their pulseaudio package and compared the configuration files. The older Ubuntu versions of pulseaudio have the same broken pulse-alsa.conf file as Sid does. The newest version has this instead: snip The new configuration file seems to solve the problem on my Sid system. Probably making the same change as was done in Ubuntu would be reasonable. The file included in Ubuntu is basically the file 99-pulseaudio-default.conf.example included in the package libasound2-plugins and installed at /usr/share/alsa/alsa.conf.d/99-pulseaudio-default.conf.example but they use the description from the old pulse-alsa.conf file and still included in the Debian package. I have used for several years the attached file saved as ~/.asoundrc since pulseaudio was giving me trouble long ago. It is basically /usr/share/alsa/alsa.conf.d/50-pulseaudio.conf /usr/share/alsa/alsa.conf.d/99-pulseaudio-default.conf.example both in 1 file. I think I first read the explanation for each file from http://www.pulseaudio.org/wiki/PerfectSetup#ALSAApplications when I first used the attached file. The 50-pulseaudio.conf part is redundant since it just add a name therefore using only the 99-pulseaudio-default.conf.example file as used in Ubuntu should be fine too. Hope this helps, Miguel pulse-alsa.conf Description: Binary data ___ pkg-pulseaudio-devel mailing list pkg-pulseaudio-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-pulseaudio-devel
[Pkg-phototools-devel] Bug#661525: libgphoto2-2: Drop dependency of adduser
Package: libgphoto2-2 Version: 2.4.13-1 Severity: normal Hello: I noticed that libgphoto2-2 depends on adduser. While looking at the changelog I noticed that it was included back in 2004 due to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273432 While looking at the debian folder libgphoto2-2.postinst no longer calls addgroup or any other script inside the debian folder that I could see. This dependency gives the following issue with multiarch: libgphoto2-2:i386 : Depends: adduser:i386 but it is not installable There is already a bug report for adduser to be made Multi-Arch foreign but I filled this bug report since it seems the dependency is not needed in this case. Hope this helps Miguel ___ Pkg-phototools-devel mailing list Pkg-phototools-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-phototools-devel
Bug#661517: mpg123: Missing symbols in libmpg123-0.symbols.XXX
Source: mpg123 Version: 1.12.1-3.2 Tags: patch Hello: While trying to compile mpg123 with the multiarch patch in a clean i386 chroot with pbuilder I get the following message: dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libmpg123-0/DEBIAN/symbols doesn't match completely debian/libmpg123-0.symbols.i386 --- debian/libmpg123-0.symbols.i386 (libmpg123-0_1.12.1_i386) +++ libmpg123-0.symbols.i3862012-02-27 13:53:32.0 -0500 @@ -6,6 +6,7 @@ mpg123_copy_string@Base 1.6.2 mpg123_current_decoder@Base 1.7.2 mpg123_decode@Base 1.6.2 + mpg123_decode_frame@Base 1.12.1 mpg123_decode_frame_64@Base 1.6.2 mpg123_decoder@Base 1.6.2 mpg123_decoders@Base 1.6.2 @@ -18,6 +19,7 @@ mpg123_exit@Base 1.6.2 mpg123_feature@Base 1.10.0 mpg123_feed@Base 1.6.2 + mpg123_feedseek@Base 1.12.1 mpg123_feedseek_64@Base 1.6.2 mpg123_fmt@Base 1.6.2 mpg123_fmt_all@Base 1.6.2 @@ -28,6 +30,7 @@ mpg123_format_none@Base 1.6.2 mpg123_format_support@Base 1.6.2 mpg123_framebyframe_decode@Base 1.10.0 + mpg123_framebyframe_decode_64@Base 1.12.1 mpg123_framebyframe_next@Base 1.10.0 mpg123_free_string@Base 1.6.2 mpg123_geteq@Base 1.6.2 @@ -40,45 +43,61 @@ mpg123_icy2utf8@Base 1.6.2 mpg123_icy@Base 1.6.2 mpg123_id3@Base 1.6.2 + mpg123_index@Base 1.12.1 mpg123_index_64@Base 1.6.2 mpg123_info@Base 1.6.2 mpg123_init@Base 1.6.2 mpg123_init_string@Base 1.6.2 + mpg123_length@Base 1.12.1 mpg123_length_64@Base 1.6.2 mpg123_meta_check@Base 1.6.2 mpg123_new@Base 1.6.2 mpg123_new_pars@Base 1.6.2 + mpg123_open@Base 1.12.1 mpg123_open_64@Base 1.6.2 + mpg123_open_fd@Base 1.12.1 mpg123_open_fd_64@Base 1.6.2 mpg123_open_feed@Base 1.6.2 mpg123_open_handle@Base 1.12.1 + mpg123_open_handle_64@Base 1.12.1 mpg123_outblock@Base 1.6.2 mpg123_par@Base 1.6.2 mpg123_param@Base 1.6.2 mpg123_parnew@Base 1.6.2 mpg123_plain_strerror@Base 1.6.2 + mpg123_position@Base 1.12.1 mpg123_position_64@Base 1.6.2 mpg123_rates@Base 1.6.2 mpg123_read@Base 1.6.2 mpg123_replace_buffer@Base 1.6.2 mpg123_replace_reader@Base 1.6.2 + mpg123_replace_reader_64@Base 1.12.1 mpg123_replace_reader_handle@Base 1.12.1 + mpg123_replace_reader_handle_64@Base 1.12.1 mpg123_reset_eq@Base 1.6.2 mpg123_resize_string@Base 1.6.2 mpg123_safe_buffer@Base 1.6.2 mpg123_scan@Base 1.6.2 + mpg123_seek@Base 1.12.1 mpg123_seek_64@Base 1.6.2 + mpg123_seek_frame@Base 1.12.1 mpg123_seek_frame_64@Base 1.6.2 + mpg123_set_filesize@Base 1.12.1 mpg123_set_filesize_64@Base 1.6.2 + mpg123_set_index@Base 1.12.1 mpg123_set_index_64@Base 1.10.0 mpg123_set_string@Base 1.6.2 mpg123_set_substring@Base 1.6.2 mpg123_store_utf8@Base 1.9.1 mpg123_strerror@Base 1.6.2 mpg123_supported_decoders@Base 1.6.2 + mpg123_tell@Base 1.12.1 mpg123_tell_64@Base 1.6.2 + mpg123_tell_stream@Base 1.12.1 mpg123_tell_stream_64@Base 1.6.2 + mpg123_tellframe@Base 1.12.1 mpg123_tellframe_64@Base 1.6.2 + mpg123_timeframe@Base 1.12.1 mpg123_timeframe_64@Base 1.6.2 mpg123_tpf@Base 1.6.2 mpg123_volume@Base 1.6.2 Since I compile with DPKG_GENSYMBOLS_CHECK_LEVEL=4 the package FTBFS in i386 but in amd64 it builds fine. I noticed that of the 19 new symbols found: - 15 are those in libmpg123-0.symbols.64bit.in. - The new ones seem to be: + mpg123_framebyframe_decode_64@Base 1.12.1 + mpg123_open_handle_64@Base 1.12.1 + mpg123_replace_reader_64@Base 1.12.1 + mpg123_replace_reader_handle_64@Base 1.12.1 I quickly checked the last log in: https://buildd.debian.org/status/package.php?p=mpg123 And all architectures except ia64 and amd64 show the new symbols found message. Looking at old logs it started with 1.12.1-1. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661525: libgphoto2-2: Drop dependency of adduser
Package: libgphoto2-2 Version: 2.4.13-1 Severity: normal Hello: I noticed that libgphoto2-2 depends on adduser. While looking at the changelog I noticed that it was included back in 2004 due to: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273432 While looking at the debian folder libgphoto2-2.postinst no longer calls addgroup or any other script inside the debian folder that I could see. This dependency gives the following issue with multiarch: libgphoto2-2:i386 : Depends: adduser:i386 but it is not installable There is already a bug report for adduser to be made Multi-Arch foreign but I filled this bug report since it seems the dependency is not needed in this case. Hope this helps Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#645957: Please mark adduser Multi-Arch: foreign
Please point me to the part of Debian policy that explains the Multi-Arch header in debian/control. I am reluctant to do things in Debian which are only documented in Ubuntu. Greetings Marc Hello: As stated in the TODO section of http://packages.qa.debian.org/a/adduser.html : http://wiki.debian.org/ReleaseGoals/MultiArch And as useful links: http://wiki.debian.org/Multiarch/ http://wiki.debian.org/Multiarch/Implementation The specification has always been hosted on the wiki.ubuntu.com which I think caused this whole confusion. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661543: libgd2: Add an empty libgd-tools.symbols file
Source: libgd2 Version: 2.0.36~rc1~dfsg-6 Hello: While trying to build a multiarch version of this package locally with pbuilder I noticed: dh_makeshlibs -plibgd-tools dpkg-gensymbols: warning: some libraries disappeared in the symbols file: libgd.so.2 dpkg-gensymbols: warning: the generated symbols file is empty --- debian/symbols (libgd-tools_2.0.36~rc1~dfsg-6_i386) +++ dpkg-gensymbolsq8OXHM 2011-10-15 21:13:43.0 + @@ -1,201 +0,0 @@ This happens on all architectures since the file symbols will be used for all packages generated by this source and libgd-tools has no libraries. Since the chroot I use exports DPKG_GENSYMBOLS_CHECK_LEVEL=4 the package fails to build and that is how I noticed. One way to fix this with the least amount of changes is to do touch libgd-tools.symbols inside the debian folder. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#637600: Please transition speex for multiarch
Hello:
I updated the patch for the changes in 1.2~rc1-3 and it should apply
cleanly now. It takes into account the small changes to the control
file and the removal of the *.install but it should be equivalent.
The new -dbg package could not be made multiarch since it contains the
dbg for the libraries and the binaries (sort of misleading). If the
binaries had their own -dbg package, libspeex-dbg could be made
Multi-Arch: same.
-Miguel
=== modified file 'debian/control'
--- debian/control 2010-03-29 15:13:22 +
+++ debian/control 2011-08-12 18:52:22 +
@@ -2,7 +2,7 @@
Section: sound
Priority: optional
Maintainer: Ron Lee r...@debian.org
-Build-Depends: debhelper ( 4.1.0), libogg-dev, dpkg-dev (= 1.13.19)
+Build-Depends: debhelper (= 8.1.3), libogg-dev, dpkg-dev (= 1.13.19)
Build-Depends-Indep: doxygen, graphviz
Standards-Version: 3.9.2.0
Homepage: http://www.speex.org/
@@ -22,7 +22,9 @@
Package: libspeex1
Architecture: any
+Multi-Arch: same
Section: libs
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}
Suggests: speex
Conflicts: libopal-2.2 (= 2.2.11~dfsg1-3),
@@ -42,6 +44,7 @@
Package: libspeex-dev
Architecture: any
+Multi-Arch: same
Section: libdevel
Depends: libspeex1 (= ${binary:Version})
Suggests: pkg-config
@@ -55,7 +58,9 @@
Package: libspeexdsp1
Architecture: any
+Multi-Arch: same
Section: libs
+Pre-Depends: ${misc:Pre-Depends}
Depends: ${shlibs:Depends}
Description: The Speex extended runtime library
Speex is an audio codec especially designed for compressing voice at low
@@ -68,6 +73,7 @@
Package: libspeexdsp-dev
Architecture: any
+Multi-Arch: same
Section: libdevel
Depends: libspeexdsp1 (= ${binary:Version}), libspeex-dev (= ${binary:Version})
Suggests: pkg-config
=== modified file 'debian/libspeex-dev.install'
--- debian/libspeex-dev.install 2008-04-14 23:22:26 +
+++ debian/libspeex-dev.install 2011-08-12 18:53:55 +
@@ -5,6 +5,6 @@
usr/include/speex/speex_header.h
usr/include/speex/speex_stereo.h
usr/include/speex/speex_types.h
-usr/lib/libspeex.a
-usr/lib/libspeex.so
-usr/lib/pkgconfig/speex.pc
+usr/lib/*/libspeex.a
+usr/lib/*/libspeex.so
+usr/lib/*/pkgconfig/speex.pc
=== modified file 'debian/libspeexdsp-dev.install'
--- debian/libspeexdsp-dev.install 2008-04-14 23:22:26 +
+++ debian/libspeexdsp-dev.install 2011-08-12 18:53:55 +
@@ -3,6 +3,6 @@
usr/include/speex/speex_jitter.h
usr/include/speex/speex_preprocess.h
usr/include/speex/speex_resampler.h
-usr/lib/libspeexdsp.a
-usr/lib/libspeexdsp.so
-usr/lib/pkgconfig/speexdsp.pc
+usr/lib/*/libspeexdsp.a
+usr/lib/*/libspeexdsp.so
+usr/lib/*/pkgconfig/speexdsp.pc
=== modified file 'debian/rules'
--- debian/rules 2010-03-29 15:13:22 +
+++ debian/rules 2011-08-12 18:53:30 +
@@ -25,6 +25,7 @@
DEB_HOST_ARCH_CPU ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
+DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
objdir= objs
@@ -69,6 +70,7 @@
cd $* ../configure --host=$(DEB_HOST_GNU_TYPE) \
--build=$(DEB_BUILD_GNU_TYPE) \
--prefix=/usr \
+ --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
$(EXTRA_CONFIG_FLAGS)
build: build-arch
@@ -93,11 +95,11 @@
dh_testdir
cd $(objdir) $(MAKE) install DESTDIR=$(CURDIR)/debian/tmp
if [ -d $(objdir_sse) ]; then \
- dh_install -plibspeex1$(objdir_sse)/libspeex/.libs/libspeex.so.*usr/lib/sse2; \
- dh_install -plibspeexdsp1 $(objdir_sse)/libspeex/.libs/libspeexdsp.so.* usr/lib/sse2; \
+ dh_install -plibspeex1$(objdir_sse)/libspeex/.libs/libspeex.so.*usr/lib/$(DEB_HOST_MULTIARCH)/sse2; \
+ dh_install -plibspeexdsp1 $(objdir_sse)/libspeex/.libs/libspeexdsp.so.* usr/lib/$(DEB_HOST_MULTIARCH)/sse2; \
fi
- dh_install -plibspeex1$(objdir)/libspeex/.libs/libspeex.so.*usr/lib
- dh_install -plibspeexdsp1 $(objdir)/libspeex/.libs/libspeexdsp.so.* usr/lib
+ dh_install -plibspeex1$(objdir)/libspeex/.libs/libspeex.so.*usr/lib/$(DEB_HOST_MULTIARCH)
+ dh_install -plibspeexdsp1 $(objdir)/libspeex/.libs/libspeexdsp.so.* usr/lib/$(DEB_HOST_MULTIARCH)
dh_install -plibspeex-dev -plibspeexdsp-dev -pspeex --sourcedir=debian/tmp
touch $@
Bug#661393: FTBFS: Enabling hardening on amd64 causes relocation errors
Source: keyutils Version: 1.5.5-1 Severity: important Tags: patch Hello: The last release enabled hardening but caused the following errors in amd64: /usr/bin/ld: keyctl.o: relocation R_X86_64_32S against `commands' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: request-key.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: key.dns_resolver.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC If hardening is disabled the errors go away but I doubt that is desired. As an attachment I included a patch for a possible way to fix the FTBFS. The log of the errors can be found: https://buildd.debian.org/status/fetch.php?pkg=keyutilsarch=amd64ver=1.5.5-1stamp=1327720867 The 2nd and 3rd -fPIC error messages appear when you add -fPIC flag to the object file of the previous line. Hope this helps, Miguel Description: Use -fPIC for the generated *.o. Errors caused by enabling hardening in amd64: /usr/bin/ld: keyctl.o: relocation R_X86_64_32S against `commands' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: request-key.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: key.dns_resolver.o: relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC Forwarded: no Author: Miguel Colon debian.mic...@gmail.com Last-Update: 2012-02-26 --- keyutils-1.5.5.orig/Makefile +++ keyutils-1.5.5/Makefile @@ -127,7 +127,7 @@ keyutils.os: keyutils.c keyutils.h Makef # ### %.o: %.c keyutils.h Makefile - $(CC) $(CPPFLAGS) $(CFLAGS) -o $@ -c $ + $(CC) $(CPPFLAGS) $(CFLAGS) -fPIC -o $@ -c $ keyctl: keyctl.o $(DEVELLIB) $(CC) -L. $(CFLAGS) $(LDFLAGS) $(RPATH) -o $@ $ -lkeyutils
Bug#649514: src:nvidia-cg-toolkit: should this package be orphaned?
Hello: While working on packaging the new release 3.1 from 6 days ago, I noticed that I never replied to this. I just wanted to add that I tried to contact both maintainers. One confirmed that he resigned as stated on the git history while the other never replied to several emails. Since I tend to delete my email messages after a year I only have March 1st 2011 and July 23rd 2011 as the last dates I tried to contact the last maintainer. If it helps the current maintainer or anyone else I uploaded the latest version of the package to: http://mentors.debian.net/debian/pool/non-free/n/nvidia-cg-toolkit/nvidia-cg-toolkit_3.1.0010-0.1.dsc It has some suggestions from when the Debian NVIDIA Maintainers and others reviewed it but it probably needs a second look since that was a while back. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639857: nvidia-cg-toolkit: Fails to install with libc6 (= 2.13-17)
Package: nvidia-cg-toolkit Version: 2.1.0017.deb1+nmu3 Severity: important Dear Maintainer, Recently I noticed that with libc6 (= 2.13-17), the amd64 version of this package fails to completely install with the following error: Installing NVIDIA Cg Toolkit components: Cg compiler, header files, libraries, Failed to copy file /tmp/HI3zhWHHMr/usr/lib64/libCg.so to /usr/lib64/libCg.so: No such file or directory at /usr/bin/nvidia-cg-toolkit-installer line 321. The problem is that libc6 removed the /usr/lib64 symlink that was used by the nvidia-cg-toolkit-installer script. The package is then left in an inconsistent state since some files like the headers seem to get installed but the libraries and other files don't get installed while the file is marked as installed by dpkg. The i386 version seems to still install fine. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635321: Unable to reproduce with soundtouch 1.6.0-1 or 1.6.0-2
Hello: Today I tried to reproduce this bug but I could not do it. I also could not find a change in soundtouch BPM routines from 1.5.0 to 1.6.0 that could have caused it. Here is a log of what I did but I cut out some of the verbose: $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-2 $ sudo apt-get install banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:06:18.659] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:07:13.017] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ rm -rf ~/.config/banshee-1/ I went to http://snapshot.debian.org/package/soundtouch/1.6.0-1/#libsoundtouch0_1.6.0-1 and installed the 1.6.0-1 as originally reported. $ sudo dpkg -i libsoundtouch0_1.6.0-1_amd64.deb $ sudo apt-get install banshee/sid -qq $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:08:58.164] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:09:59.268] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 Both soundtouch 1.6.0-1 and 1.6.0-2 worked fine with Banshee from sid and experimental. For a final test I tried the version that was originally reported: $ rm -rf ~/.config/banshee-1/ $ sudo dpkg -i libgdata1.7-cil_1.7.0.1-1_all.deb banshee_2.1.0-1_amd64.deb libmtp8_1.0.6-7_amd64.deb $ banshee [Info 21:32:02.028] Running Banshee 2.1.0: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-05-17 11:03:27 UTC] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.0-1 So the current 2.0.1, the reported 2.1.0-1 and the current version from experimental seem to work with a current and up to date system. I guess that there was a different package that caused the original crash and that package got updated again and the original issue was resolved. If the original submitter could confirm it would help. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#635321: Unable to reproduce with soundtouch 1.6.0-1 or 1.6.0-2
Hello: Today I tried to reproduce this bug but I could not do it. I also could not find a change in soundtouch BPM routines from 1.5.0 to 1.6.0 that could have caused it. Here is a log of what I did but I cut out some of the verbose: $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-2 $ sudo apt-get install banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:06:18.659] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:07:13.017] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ rm -rf ~/.config/banshee-1/ I went to http://snapshot.debian.org/package/soundtouch/1.6.0-1/#libsoundtouch0_1.6.0-1 and installed the 1.6.0-1 as originally reported. $ sudo dpkg -i libsoundtouch0_1.6.0-1_amd64.deb $ sudo apt-get install banshee/sid -qq $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:08:58.164] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:09:59.268] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 Both soundtouch 1.6.0-1 and 1.6.0-2 worked fine with Banshee from sid and experimental. For a final test I tried the version that was originally reported: $ rm -rf ~/.config/banshee-1/ $ sudo dpkg -i libgdata1.7-cil_1.7.0.1-1_all.deb banshee_2.1.0-1_amd64.deb libmtp8_1.0.6-7_amd64.deb $ banshee [Info 21:32:02.028] Running Banshee 2.1.0: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-05-17 11:03:27 UTC] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.0-1 So the current 2.0.1, the reported 2.1.0-1 and the current version from experimental seem to work with a current and up to date system. I guess that there was a different package that caused the original crash and that package got updated again and the original issue was resolved. If the original submitter could confirm it would help. Hope this helps, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Bug#635321: Unable to reproduce with soundtouch 1.6.0-1 or 1.6.0-2
Hello: Today I tried to reproduce this bug but I could not do it. I also could not find a change in soundtouch BPM routines from 1.5.0 to 1.6.0 that could have caused it. Here is a log of what I did but I cut out some of the verbose: $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-2 $ sudo apt-get install banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:06:18.659] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:07:13.017] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ rm -rf ~/.config/banshee-1/ I went to http://snapshot.debian.org/package/soundtouch/1.6.0-1/#libsoundtouch0_1.6.0-1 and installed the 1.6.0-1 as originally reported. $ sudo dpkg -i libsoundtouch0_1.6.0-1_amd64.deb $ sudo apt-get install banshee/sid -qq $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.0.1-4+b2 $ banshee [Info 21:08:58.164] Running Banshee 2.0.1: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-28 13:30:52 UTC] snip $ sudo apt-get install -t experimental banshee -qq $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 $ banshee [Info 21:09:59.268] Running Banshee 2.1.3: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-08-25 13:36:14 BST] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.3-1 Both soundtouch 1.6.0-1 and 1.6.0-2 worked fine with Banshee from sid and experimental. For a final test I tried the version that was originally reported: $ rm -rf ~/.config/banshee-1/ $ sudo dpkg -i libgdata1.7-cil_1.7.0.1-1_all.deb banshee_2.1.0-1_amd64.deb libmtp8_1.0.6-7_amd64.deb $ banshee [Info 21:32:02.028] Running Banshee 2.1.0: [Debian GNU/Linux unstable (sid) (linux-gnu, x86_64) @ 2011-05-17 11:03:27 UTC] snip $ apt-cache policy libsoundtouch0 | grep Installed Installed: 1.6.0-1 $ apt-cache policy banshee | grep Installed Installed: 2.1.0-1 So the current 2.0.1, the reported 2.1.0-1 and the current version from experimental seem to work with a current and up to date system. I guess that there was a different package that caused the original crash and that package got updated again and the original issue was resolved. If the original submitter could confirm it would help. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Accepted soundtouch 1.6.0-1 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 16 Jul 2011 21:36:02 -0400 Source: soundtouch Binary: libsoundtouch-dev libsoundtouch0 libsoundtouch0-dbg lib32soundtouch-dev lib32soundtouch0 lib32soundtouch0-dbg soundstretch soundstretch-dbg Architecture: source amd64 Version: 1.6.0-1 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Miguel Colon debian.mic...@gmail.com Description: lib32soundtouch-dev - Development files for the sound stretching library (32 bit) lib32soundtouch0 - Sound stretching library (32 bit) lib32soundtouch0-dbg - Debugging symbols for the sound stretching library (32 bit) libsoundtouch-dev - Development files for the sound stretching library libsoundtouch0 - Sound stretching library libsoundtouch0-dbg - Debugging symbols for the sound stretching library soundstretch - Stretches and pitch-shifts sound independently soundstretch-dbg - Debugging symbols for the soundstretch program Changes: soundtouch (1.6.0-1) unstable; urgency=low . [ Alessio Treglia ] * Bump Standards. . [ Miguel Colon ] * Imported Upstream version 1.6.0 * Bump debhelper to version 8. * debian/rules: - Remove workaround that was needed when using debhelper 7. * debian/patches: - Drop 00_upstream_fixes.patch - merged upstream. - Refresh 01_remove_sse.patch. - Drop 03_WavFile.patch - fixed upstream. * Remove debian/clean file. * debian/copyright - Update as per DEP-5 rev.174 (no changes needed). - Update copyright years. - Update the URI of the format specification. Checksums-Sha1: 2ac616e71ea1ab9d8de3eee9b155bbde1b532608 1476 soundtouch_1.6.0-1.dsc 9871dcbf75a68665a3515bb9dda4727beb0358e7 94852 soundtouch_1.6.0.orig.tar.gz af8fcebcfcb4a54eb10e060fa5fd539a5a45ea5f 8221 soundtouch_1.6.0-1.debian.tar.gz 80949b3e3924060dcd2d259b2483550415185163 12568 libsoundtouch-dev_1.6.0-1_amd64.deb f7b0bcaa13912d14bee49481d31b486f70eefd52 40470 libsoundtouch0_1.6.0-1_amd64.deb 857752ff0ed2252034ba328680bf29c7b6db3caf 71762 libsoundtouch0-dbg_1.6.0-1_amd64.deb 1ec9d47f03e773200b0cd3b5209ba0932676c9b7 1248 lib32soundtouch-dev_1.6.0-1_amd64.deb 90437e56c42024b99323f145964a66e8aff8f726 24974 lib32soundtouch0_1.6.0-1_amd64.deb 465d66858c8b09550206982d76f9dcca2a675538 68178 lib32soundtouch0-dbg_1.6.0-1_amd64.deb 1290aebadfc95bddf62f18909e9bde5d818b839b 29754 soundstretch_1.6.0-1_amd64.deb 75283d057eef73b134151d871ffe3a6a2198a057 38730 soundstretch-dbg_1.6.0-1_amd64.deb Checksums-Sha256: a317ddaa2e84bf3e219467e98ee5d05d7c6cf5a820f748e5e31b3f79678271a0 1476 soundtouch_1.6.0-1.dsc 8776edaf7299ffe1e8c97285f020365a63c0e01aa4f6f7c5fd1d011c0ded278f 94852 soundtouch_1.6.0.orig.tar.gz b1f5491a3fef4c19d2acde72089f3bcb3c4ad777248047a39448b48cded4c7de 8221 soundtouch_1.6.0-1.debian.tar.gz 1e8b6e2390b916832216a4682d895889bf89636742fe7d841bb628686e3145f8 12568 libsoundtouch-dev_1.6.0-1_amd64.deb 65a29838ae1b2812e00a4a8328e7ce05c6d174b85cf1c8a5d1cb6fb01547 40470 libsoundtouch0_1.6.0-1_amd64.deb 8d8826fedeae6544f895ec7193ba90d52173d3e6edf04c2617ce90ede7865122 71762 libsoundtouch0-dbg_1.6.0-1_amd64.deb 02ba2d36a0ce36ea1abb41974d99cc91bc14530f58ceec242cf8185ec416 1248 lib32soundtouch-dev_1.6.0-1_amd64.deb fa35fe466c4a0c1f90ddc98e1cbc44acef6e6526ce6e58d8c8996ead1313 24974 lib32soundtouch0_1.6.0-1_amd64.deb bda53f7232226353ff509b177a69d4794d5148c3986b109f70947fbc26060355 68178 lib32soundtouch0-dbg_1.6.0-1_amd64.deb 2671c6b1ab2db642a205a0e7f5663e76d5a15090c0b305453299855a625c1432 29754 soundstretch_1.6.0-1_amd64.deb 0e921f9e2f59512c5f28428040d5a79c30d2485bea9a674319004b9e9a404ce7 38730 soundstretch-dbg_1.6.0-1_amd64.deb Files: 1bbad1da826b34d8b2410d5f8d2b0316 1476 libs optional soundtouch_1.6.0-1.dsc aa1c63d4d67b033f044a6a48d2be5bdd 94852 libs optional soundtouch_1.6.0.orig.tar.gz 8dab96598c4c92b6b7319ead26807b78 8221 libs optional soundtouch_1.6.0-1.debian.tar.gz 66f2d5064c49a3fb60008afcb49c84a1 12568 libdevel optional libsoundtouch-dev_1.6.0-1_amd64.deb 32f5ddf45275881fed57a66cb5619254 40470 libs optional libsoundtouch0_1.6.0-1_amd64.deb 119cab03f6e20648f559a6a165538c0b 71762 debug extra libsoundtouch0-dbg_1.6.0-1_amd64.deb fd4601db87cd9a3dddf9293ef5f921d2 1248 libdevel optional lib32soundtouch-dev_1.6.0-1_amd64.deb b88d5f674f3ed9ff748c7abf4344c3f2 24974 libs optional lib32soundtouch0_1.6.0-1_amd64.deb 563e9141d666dd5ab8e896a9180eef10 68178 debug extra lib32soundtouch0-dbg_1.6.0-1_amd64.deb 974509399ad2ff0bb47b5d2abb3f1699 29754 sound optional soundstretch_1.6.0-1_amd64.deb bce4e810ff3d2cb27d71348666fac0ea 38730 debug extra soundstretch-dbg_1.6.0-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk4isGgACgkQRdSMfNz8P9CKaACfW8SRla4f5bm/B1jW4Jv02jFW LYEAn0LuDbcEvgzR5nT9V8SfMXnaPiix =V6GP -END PGP SIGNATURE- Accepted: lib32soundtouch-dev_1.6.0
Re: RFS: nvidia-cg-toolkit (updated package)
Hi all:
Since I received 3 email within the last 24 hours I will try to answer
all the question here.
I started this package over a year ago and made packages for 6-7
nvidia toolkit releases while merging the changelog so I might not
remember all the reasons I did things like that since I never made a
local git for it. I only uploaded the last 2 releases to Debian
Mentors. All the specific answers are below:
On Sun, May 1, 2011 at 10:19 AM, Michael Tautschnig m...@debian.org wrote:
You seem to be putting lots of energy in this package. Yet your changes go far
beyond what an ordinary NMU should be like. As there has been a sequence of
NMUs
already probably it would be best if you took over the package. Yet you will
have to follow proper procedures to do so. Have you gotten in touch with the
current official maintainer(s)? Looking at your changelog you seem to have
spoken to at least one of them. Please provide some information about this
process (here, not in the package) and please perform the proper procedure to
take over the package, if you intend to do so in long term. If all you want to
do is an NMU, then please make sure you keep the changes to a minimum.
Best regards,
Michael
Yeah I realize the changes are way over a standard NMU. My original
plan was to email the original maintainers the changes so they could
incorporate them. I sent a few email and finally opened a bug report
since I never got a reply. Since the package is not officially
orphaned and I'm not a DD/DM I was waiting to see if it got orphaned
and then was planning on contacting the nvidia devel list to see if
they wanted to include it under their team umbrella.
On Mon, May 2, 2011 at 11:32 PM, Russ Allbery r...@debian.org wrote:
Also, if you're interested in maintaining packages of this sort in
general, you may want to consider joining the NVIDIA packaging team by
subscribing to the pkg-nvidia-devel mailing list on
lists.alioth.debian.org. We're currently maintaining the CUDA packages as
well as the NVIDIA graphics drivers and libraries, and while I don't have
any time to work on NVIDIA packaging myself, I'm happy to do uploads for
others and some package review. Other people on the team may also be
willing to help.
--
Russ Allbery (r...@debian.org) http://www.eyrie.org/~eagle/
As I mentioned above I was considering this but I was waiting to hear
from the maintainers since I did not want to hijack or do anything
that may have been perceived as rude by them.
On Tue, May 3, 2011 at 5:59 AM, Andreas Beckmann deb...@abeckmann.de wrote:
I just had a brief look over the package.
What's curious is that you need a login at nvidia to download the
software, but the license explicitely allows redistribution.
Yes this started within the last week or so since I try to check every
1-2 weeks for a new version and I first saw this 3-4 days ago.
* as Andres Mejia has resigned, you should also drop the
DM-Upload-Allowed: yes
from debian/control as there are no non-DD uploaders left
Seems that I missed it when I removed Andres Mejia name.
* the debian/watch file can be generated with a single sed call with
two -e '...' -e '...' parameters
* the watch file is not useful since it points to a page that requires
a login :-(
Yeah, when I noticed this 3-4 days ago I knew the watch file /
get-orig-source routine became obsolete.
* why do we need override_dh_gencontrol: and override_dh_builddeb:? dh
should work fine without
This is for compatibility with ubuntu lucid or to be more
correct/precise with debhelper 7 or at least some versions of it. I
compile these on my ppa and from what I remember the i386 version
tried to run those 2 commands for the ia32 package which is amd64
only. I never saw this error on my local machine on Debian since it
had debhelper 8 and compiling in maverick also worked fine without
those overrides. I used to bump the debhelper dependency to 8 but
decided to use this method since it worked in debhelper 7/8.
* the doc package should only Recommends/Suggests: the toolkit (if you
add a dependency at all), otherwise you have an Arch: all package that's
uninstallable everywhere except on i386/amd64. But why shouldn't you
read the docs on a different arch or without installing the toolkit?
The -doc package contains several example programs that would require
the toolkit to compile. To ensure that those program compiled I made
it depend on the same source version to avoid compatibility issues. To
be honest I thought I had it as a Recommends but thanks for pointing
it out. Also I was thinking of splitting the package since the
documentation is truly an arch:all package but the examples are really
an arch: i386 amd64 package but never got around to it.
* use Suggests: nvidia-cg-toolkit-doc (= ${source:Version}) as this is
an arch:all package that does not get binNMUed. See deb-substvars(5)
True.
* the runtime libraries should probably be split to a
Bug#620151: fglrx-modules-dkms Linux 2.6.39 support
Package: fglrx-modules-dkms Version: 1:11-3-1 Severity: wishlist Tags: patch Hello: linux/spinlock_types.h had the following comment until 2.6.38: /* * SPIN_LOCK_UNLOCKED defeats lockdep state tracking and is hence * deprecated. * Please use DEFINE_SPINLOCK() or __SPIN_LOCK_UNLOCKED() as * appropriate. */ #define SPIN_LOCK_UNLOCKED __SPIN_LOCK_UNLOCKED(old_style_spin_init) This definition got removed in 2.6.39. A possible solution is included in the attached DEP-3 compliant patch. The patch restores the missing define locally until it gets fixed upstream by AMD. I tested this patch with 2.6.38, 2.6.38.1 , 2.6.38.2 and 2.6.39-rc1 with fglrx 11.2-2 and 11.3-1 and all seems to work. I removed the smp_lock.h part of the patch that I had made for 11-2 since it got included as the 06 patch in 11-3 and I was waiting for the merge window for 2.6.39 to close. The smp_lock.h issue technically only affected 2.6.39-rc0 and up since that commit got merged during the 2.6.39 merge window that ended today. Hope this helps, Miguel Description: Add Linux 2.6.39 support linux/spinlock_types.h had the following comment until 2.6.38: . /* * SPIN_LOCK_UNLOCKED defeats lockdep state tracking and is hence * deprecated. * Please use DEFINE_SPINLOCK() or __SPIN_LOCK_UNLOCKED() as * appropriate. */ #define SPIN_LOCK_UNLOCKED __SPIN_LOCK_UNLOCKED(old_style_spin_init) . This definition got removed in 2.6.39. Restore it locally until it gets fixed upstream. Author: Miguel Colon debian.mic...@gmail.com Forwarded: no Last-Update: 2011-03-30 --- fglrx-driver-11-3.orig/common/lib/modules/fglrx/build_mod/firegl_public.c +++ fglrx-driver-11-3/common/lib/modules/fglrx/build_mod/firegl_public.c @@ -1071,7 +1071,12 @@ static int __init firegl_init_module(voi dev-pubdev.signature = FGL_DEVICE_SIGNATURE; for (i = 0; i __KE_MAX_SPINLOCKS; i++) +#if LINUX_VERSION_CODE KERNEL_VERSION(2,6,39) dev-spinlock[i] = SPIN_LOCK_UNLOCKED; +#else +dev-spinlock[i] = __SPIN_LOCK_UNLOCKED(old_style_spin_init); +#endif + for (i=0; i __KE_MAX_SEMAPHORES; i++) sema_init(dev-struct_sem[i], 1);
Accepted soundtouch 1.5.0-5 (source i386)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 10 Mar 2011 14:49:09 -0500 Source: soundtouch Binary: libsoundtouch-dev libsoundtouch0 libsoundtouch0-dbg lib32soundtouch-dev lib32soundtouch0 lib32soundtouch0-dbg soundstretch soundstretch-dbg Architecture: source i386 Version: 1.5.0-5 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Miguel Colon debian.mic...@gmail.com Description: lib32soundtouch-dev - Development files for the sound stretching library (32 bit) lib32soundtouch0 - Sound stretching library (32 bit) lib32soundtouch0-dbg - Debugging symbols for the sound stretching library (32 bit) libsoundtouch-dev - Development files for the sound stretching library libsoundtouch0 - Sound stretching library libsoundtouch0-dbg - Debugging symbols for the sound stretching library soundstretch - Stretches and pitch-shifts sound independently soundstretch-dbg - Debugging symbols for the soundstretch program Changes: soundtouch (1.5.0-5) unstable; urgency=low . [ Miguel Colon ] * Remove soundtouch.pc during the clean routine. * Remove 04_remove_asm.patch since 02_remove_sse.patch already does this. * Remove obsolete README.Debian file. * Update and rename the files in debian/patches. . [ Alessio Treglia ] * Put soundtouch.pc into debian/clean. * Update libsoundtouch0.docs, README.Debian has been deleted. Checksums-Sha1: 8da3b2ba80903d41b51f0eef46524ae03407c1c2 1480 soundtouch_1.5.0-5.dsc 10109c28da79b51a3884f8c70c2c311319c7fcbb 9804 soundtouch_1.5.0-5.debian.tar.gz 3f85873f3fc7ce5baa21c3ec4ba3abd70cab11c2 12248 libsoundtouch-dev_1.5.0-5_i386.deb 874fcde971f74995cfec50ef61099ccfb9d37586 39362 libsoundtouch0_1.5.0-5_i386.deb 80a55ed4bfa10d6f34ce6f4596991888b73ce096 65312 libsoundtouch0-dbg_1.5.0-5_i386.deb cad4299735e374eb29004081f561b78cf24ada7d 28720 soundstretch_1.5.0-5_i386.deb 86cbd6acfe8c43896b924b226aa209c454cd2d34 37252 soundstretch-dbg_1.5.0-5_i386.deb Checksums-Sha256: 05b3e241651a959a19c114a33a41394dba949bca0c7994b8ad15c77e77077725 1480 soundtouch_1.5.0-5.dsc c59aa21ad4dbdeb13088a0b7ba1e089ce3607f858f869505bbe98e7270b7d9e0 9804 soundtouch_1.5.0-5.debian.tar.gz 93b247312cb1c513f6664a2f19dfd7d45c3f218b40f1d5a1d82912cdb60cd4af 12248 libsoundtouch-dev_1.5.0-5_i386.deb cc0d05c8a01a22322be6fc0fd35aa217474173ec842ff0ad96ec9982be53d07e 39362 libsoundtouch0_1.5.0-5_i386.deb 3f5ce31262f099742f49c7b8e8732a98a4f627c35b8672e541c6c458d089aaef 65312 libsoundtouch0-dbg_1.5.0-5_i386.deb a599dced2924d13062eb5d8857ececed3cf7ed8226d0ca9f2cd897ddeecae121 28720 soundstretch_1.5.0-5_i386.deb 3d559d8a856a4dc6837965bd3679fea66f259bea175c2cfc60c8550bc11d6768 37252 soundstretch-dbg_1.5.0-5_i386.deb Files: 2d5b5f0deb9e9f330cc73dd799e9a52a 1480 libs optional soundtouch_1.5.0-5.dsc a4848a278661ef3ae359d5e048fb99ae 9804 libs optional soundtouch_1.5.0-5.debian.tar.gz 87dee8b034b9811244e087b7ff94e8b6 12248 libdevel optional libsoundtouch-dev_1.5.0-5_i386.deb e7e34fcbdd2938da1facb404e22a46fd 39362 libs optional libsoundtouch0_1.5.0-5_i386.deb 661b63f4665ae1437cc0e57a26f1c53c 65312 debug extra libsoundtouch0-dbg_1.5.0-5_i386.deb 129edbc5dce351b861cec84011443406 28720 sound optional soundstretch_1.5.0-5_i386.deb 2c62e25a31bd3ad1ae238769387e932f 37252 debug extra soundstretch-dbg_1.5.0-5_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk18erUACgkQRdSMfNz8P9CNoQCggXGnOvJAED4duC+BGufqhW+S 34cAnAjFep2ipOCj5WguMH4HDnfdgVln =5Z1K -END PGP SIGNATURE- Accepted: libsoundtouch-dev_1.5.0-5_i386.deb to main/s/soundtouch/libsoundtouch-dev_1.5.0-5_i386.deb libsoundtouch0-dbg_1.5.0-5_i386.deb to main/s/soundtouch/libsoundtouch0-dbg_1.5.0-5_i386.deb libsoundtouch0_1.5.0-5_i386.deb to main/s/soundtouch/libsoundtouch0_1.5.0-5_i386.deb soundstretch-dbg_1.5.0-5_i386.deb to main/s/soundtouch/soundstretch-dbg_1.5.0-5_i386.deb soundstretch_1.5.0-5_i386.deb to main/s/soundtouch/soundstretch_1.5.0-5_i386.deb soundtouch_1.5.0-5.debian.tar.gz to main/s/soundtouch/soundtouch_1.5.0-5.debian.tar.gz soundtouch_1.5.0-5.dsc to main/s/soundtouch/soundtouch_1.5.0-5.dsc -- To UNSUBSCRIBE, email to debian-devel-changes-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pyh7l-0003ns...@franck.debian.org
Bug#617399: ihu hangs instead of cleanly closing
Package: ihu Version: 0.6.0-2 Tags: squeeze wheezy sid Hello: Step to reproduce using ihu version 0.6.0-2 : 1) Open a terminal window and run ihu from it. 3) Hit the X button in the upper-right corner of the window 4) The window gets closed but the process is still running. 5) Send a SIGINT to force termination Results: $ ihu ^CSIGINT caught. Terminating... If I go to the menu and do File - Quit or Ctrl key + Q it closes cleanly so the bug only appears when using the X button in the corner of the window to close. I found this a few months back but forgot to report it. This currently happens with a standard sid gnome install and it should happen in squeeze but since the last time I checked things might have changed. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615654: ihu and a nmu
Hi Miguel, thanks for your work! I'll check your package and I'll integrate your change in the official package in the next days. Just as an Addendum: Reinhard Tartler wrote: the library uses libgmpxx, not libgmp. I did the same mistake myself, and came to the conclusion that the test should be fixed to test a symbol that is actually in libgmpxx. Might want to look into this. Hope this helps. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615654: ihu and a nmu
Dear maintainer, I've prepared an NMU for ihu (versioned as 0.6.0-2.1). I plan to upload it to http://mentors.debian.net/ in the next few hours since I have to finish running some of the test. The reason for the NMU is that this package from my understanding is currently blocking the ffmpeg/soundtouch transition: http://release.debian.org/transitions/ffmpeg.html http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614726 Regards. Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615654: ihu and a nmu
Hello: I just uploaded it to mentors.debian.net: Your upload of the package 'ihu' to mentors.debian.net was successful. Sponsors can now download it. The URL of your package is: http://mentors.debian.net/debian/pool/main/i/ihu The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/i/ihu/ihu_0.6.0-2.1.dsc The test/things I did: - Built with pbuilder in a clean sid chroot (i386/amd64) - debdiff old deb with nmu to confirm no missing files and sane looking control file. - Lintian check it (could have updated the standard version but did not) - Simplified rules file and made it 3.0 quilt since 98% of the diff was auto-generated files (config.guess/config.sub/moc and others) and it was FTBFS due to old autoreconf tools. - CFLAGS and DEB_BUILD_OPTIONS get done by debhelper 7. - Fixed clean routine to remove some auto-generated files that did not get cleaned. - Made sure to use the new soundtouch library. - Installed/remove/purged and made sure it ran (never used it before so it was a basic test of functionality). I tried to keep the changes to a minimum since it's a NMU. Please review it and make suggestions/edits. If it looks fine please upload it. If it's bad just ignore it :) or inform me how can it be improved. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615654: ihu and a nmu
Dear maintainer, I've prepared an NMU for ihu (versioned as 0.6.0-2.1). I plan to upload it to http://mentors.debian.net/ in the next few hours since I have to finish running some of the test. The reason for the NMU is that this package from my understanding is currently blocking the ffmpeg/soundtouch transition: http://release.debian.org/transitions/ffmpeg.html http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614726 Regards. Miguel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615654: ihu and a nmu
Hello: I just uploaded it to mentors.debian.net: Your upload of the package 'ihu' to mentors.debian.net was successful. Sponsors can now download it. The URL of your package is: http://mentors.debian.net/debian/pool/main/i/ihu The respective dsc file can be found at: http://mentors.debian.net/debian/pool/main/i/ihu/ihu_0.6.0-2.1.dsc The test/things I did: - Built with pbuilder in a clean sid chroot (i386/amd64) - debdiff old deb with nmu to confirm no missing files and sane looking control file. - Lintian check it (could have updated the standard version but did not) - Simplified rules file and made it 3.0 quilt since 98% of the diff was auto-generated files (config.guess/config.sub/moc and others) and it was FTBFS due to old autoreconf tools. - CFLAGS and DEB_BUILD_OPTIONS get done by debhelper 7. - Fixed clean routine to remove some auto-generated files that did not get cleaned. - Made sure to use the new soundtouch library. - Installed/remove/purged and made sure it ran (never used it before so it was a basic test of functionality). I tried to keep the changes to a minimum since it's a NMU. Please review it and make suggestions/edits. If it looks fine please upload it. If it's bad just ignore it :) or inform me how can it be improved. Hope this helps, Miguel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611529: Update to build with soundtouch 1.5
Hello: The proposed patched was made before libsoundtouch0-dev got renamed to libsoundtouch-dev. When the changes recommended in this patch get applied please also add these changes: 1) Strip the soname from the name of the build dependency. Change the two instances of libsoundtouch0-dev ( previously libsoundtouch1-dev) in the control file to libsoundtouch-dev. 2) Tighten dependency on libsoundtouch-dev to libsoundtouch-dev (= 1.5.0) . The reasoning is that soundtouch.pc is only found in libsoundtouch-dev = 1.5.0 . Thanks in advance. Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615536: FTBFS due to change in DSO Linking
Source: liquidsoap Version: 0.9.2-3 Severity: serious Hello: Due to recent changes in the gcc linker this error occurs. OCAMLC -o liquidsoap /usr/bin/ld: /usr/lib/ocaml/soundtouch/libsoundtouch_stubs.a(soundtouch_stubs.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' /usr/bin/ld: note: '__gxx_personality_v0@@CXXABI_1.3' is defined in DSO //usr/lib64/libstdc++.so.6 so try adding it to the linker command line //usr/lib64/libstdc++.so.6: could not read symbols: Invalid operation collect2: ld returned 1 exit status File caml_startup, line 1, characters 0-1: Error: Error during linking Happens with both gcc-4.4 and gcc-4.5. Adding -lstdc++ to the configure/configure.ac: LDFLAGS=$LDFLAGS -L$prefix/lib to LDFLAGS=$LDFLAGS -L$prefix/lib -lstdc++ Seems to fix the problem and the package builds again. Thanks in advance. Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611530: Update to soundtouch 1.5
Hello: The proposed patch was made before libsoundtouch0-dev got renamed to libsoundtouch-dev. Please use libsoundtouch-dev as the build dependency. Thanks in advance. Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612050: libsoundtouch1-dev was renamed to libsoundtouch-dev
Hello: Please replace build dependency libsoundtouch1-dev with libsoundtouch-dev. libsoundtouch-dev currently provides libsoundtouch1-dev as a convenience but please use libsoundtouch-dev. The old name still appears in 0.10.19-2.1 in these fies: build-deps build-deps.in control . Would be nice if this change is incorporated when the new version in experimental gets uploaded to sid. Thanks in advance. Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#612050: libsoundtouch1-dev was renamed to libsoundtouch-dev
Hello: Please replace build dependency libsoundtouch1-dev with libsoundtouch-dev. libsoundtouch-dev currently provides libsoundtouch1-dev as a convenience but please use libsoundtouch-dev. The old name still appears in 0.10.19-2.1 in these fies: build-deps build-deps.in control . Would be nice if this change is incorporated when the new version in experimental gets uploaded to sid. Thanks in advance. Miguel ___ pkg-gstreamer-maintainers mailing list pkg-gstreamer-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-gstreamer-maintainers
Bug#615536: FTBFS due to change in DSO Linking
Source: liquidsoap Version: 0.9.2-3 Severity: serious Hello: Due to recent changes in the gcc linker this error occurs. OCAMLC -o liquidsoap /usr/bin/ld: /usr/lib/ocaml/soundtouch/libsoundtouch_stubs.a(soundtouch_stubs.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' /usr/bin/ld: note: '__gxx_personality_v0@@CXXABI_1.3' is defined in DSO //usr/lib64/libstdc++.so.6 so try adding it to the linker command line //usr/lib64/libstdc++.so.6: could not read symbols: Invalid operation collect2: ld returned 1 exit status File caml_startup, line 1, characters 0-1: Error: Error during linking Happens with both gcc-4.4 and gcc-4.5. Adding -lstdc++ to the configure/configure.ac: LDFLAGS=$LDFLAGS -L$prefix/lib to LDFLAGS=$LDFLAGS -L$prefix/lib -lstdc++ Seems to fix the problem and the package builds again. Thanks in advance. Miguel -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611529: Update to build with soundtouch 1.5
Hello: The proposed patched was made before libsoundtouch0-dev got renamed to libsoundtouch-dev. When the changes recommended in this patch get applied please also add these changes: 1) Strip the soname from the name of the build dependency. Change the two instances of libsoundtouch0-dev ( previously libsoundtouch1-dev) in the control file to libsoundtouch-dev. 2) Tighten dependency on libsoundtouch-dev to libsoundtouch-dev (= 1.5.0) . The reasoning is that soundtouch.pc is only found in libsoundtouch-dev = 1.5.0 . Thanks in advance. Miguel -- To UNSUBSCRIBE, email to debian-ocaml-maint-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimrr_dxs7d_zeriyyahdq48vcng3o1hv_hp-...@mail.gmail.com
Bug#615536: FTBFS due to change in DSO Linking
Source: liquidsoap Version: 0.9.2-3 Severity: serious Hello: Due to recent changes in the gcc linker this error occurs. OCAMLC -o liquidsoap /usr/bin/ld: /usr/lib/ocaml/soundtouch/libsoundtouch_stubs.a(soundtouch_stubs.o): undefined reference to symbol '__gxx_personality_v0@@CXXABI_1.3' /usr/bin/ld: note: '__gxx_personality_v0@@CXXABI_1.3' is defined in DSO //usr/lib64/libstdc++.so.6 so try adding it to the linker command line //usr/lib64/libstdc++.so.6: could not read symbols: Invalid operation collect2: ld returned 1 exit status File caml_startup, line 1, characters 0-1: Error: Error during linking Happens with both gcc-4.4 and gcc-4.5. Adding -lstdc++ to the configure/configure.ac: LDFLAGS=$LDFLAGS -L$prefix/lib to LDFLAGS=$LDFLAGS -L$prefix/lib -lstdc++ Seems to fix the problem and the package builds again. Thanks in advance. Miguel -- To UNSUBSCRIBE, email to debian-ocaml-maint-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=zgsstydvuady0bkysd05qqsy0ywfb6et4h...@mail.gmail.com
Accepted soundtouch 1.5.0-4 (source amd64)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 26 Feb 2011 23:39:41 +0100 Source: soundtouch Binary: libsoundtouch-dev libsoundtouch0 libsoundtouch0-dbg lib32soundtouch-dev lib32soundtouch0 lib32soundtouch0-dbg soundstretch soundstretch-dbg Architecture: source amd64 Version: 1.5.0-4 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Changed-By: Miguel Colon debian.mic...@gmail.com Description: lib32soundtouch-dev - Development files for the sound stretching library (32 bit) lib32soundtouch0 - Sound stretching library (32 bit) lib32soundtouch0-dbg - Debugging symbols for the sound stretching library (32 bit) libsoundtouch-dev - Development files for the sound stretching library libsoundtouch0 - Sound stretching library libsoundtouch0-dbg - Debugging symbols for the sound stretching library soundstretch - Stretches and pitch-shifts sound independently soundstretch-dbg - Debugging symbols for the soundstretch program Closes: 615140 615141 615269 Changes: soundtouch (1.5.0-4) unstable; urgency=low . [ Alessio Treglia ] * Deapply patch after git-buildpackage'ing, abort on upstream changes. . [ Miguel Colon ] * Change file permissions to 644 in debian/* * Add 09_WavFile.patch: Don't crash with 24/32 Wav files. (LP: #639927) * Fix the 08_nostrip.patch: Do not patch autogenerated files. * Update 01_upstream_fixes.patch: Do not install the soundtouch-1.4.pc file. * libsoundtouch-dev: needs to provide libsoundtouch1-dev (Closes: #615140) * Do not remove libsoundtouch1c2 if installed. (Closes: #615141, #615269) Checksums-Sha1: ddc53dd3ac6ffda292a60d31f1a9efb509b4895d 2123 soundtouch_1.5.0-4.dsc e71b6eb6d84887277081f0f53c1738c15183c97b 10330 soundtouch_1.5.0-4.debian.tar.gz 9a473249ac1c98ba4dfca46beeabb474cbb22f07 12204 libsoundtouch-dev_1.5.0-4_amd64.deb f700f29659c7011666ba526896786e92d1d134be 40616 libsoundtouch0_1.5.0-4_amd64.deb c26701406bf77417f43d14d22348f19d711bc9c4 64684 libsoundtouch0-dbg_1.5.0-4_amd64.deb 718feef78ef3df3b44be0cda4d95b920339ceca7 1248 lib32soundtouch-dev_1.5.0-4_amd64.deb 7b3e961e35db269ddffb7380d8fdaa332d5e192f 25392 lib32soundtouch0_1.5.0-4_amd64.deb 49ae2dde4c5ffed9198d731deede73d62816c83b 63790 lib32soundtouch0-dbg_1.5.0-4_amd64.deb 68a6090c6fc6041ba05535f7def7e6b9084f585e 29412 soundstretch_1.5.0-4_amd64.deb e9bc6c978436b675c09c1efdfcd36b26ce99606e 35672 soundstretch-dbg_1.5.0-4_amd64.deb Checksums-Sha256: ea23610ca6b0e0de893b34f0c8ee91115f56f1062dc1557763dbb30018702b82 2123 soundtouch_1.5.0-4.dsc 7daf200606269754ff47fe57280ee8a224eabca57fba76cb66367df4efef3dd0 10330 soundtouch_1.5.0-4.debian.tar.gz 3578e3b66df46da56129adaaf0312a5f265acd9a6bb98b61c2e53aa58b6eb25e 12204 libsoundtouch-dev_1.5.0-4_amd64.deb c4413a4a12726e4cdb085459efb01d6ae87b2a786e073c6a70325425d20578da 40616 libsoundtouch0_1.5.0-4_amd64.deb 13f647f8f4f186d90ace116a24f0ec01233cb12fd25aa354670956017398 64684 libsoundtouch0-dbg_1.5.0-4_amd64.deb 59ef80e1f6d6ad4583353a535e595097f2eaba030639406ffce0b8ce990e0284 1248 lib32soundtouch-dev_1.5.0-4_amd64.deb bf0eab253fbfb869a054a9e0d9a2a5e99474ff267ca2e83a68c88e0f462933a8 25392 lib32soundtouch0_1.5.0-4_amd64.deb 63e437bf1f18f349853095e5169f2803c16663b0cb1a15e5587a9e1d2b6985a5 63790 lib32soundtouch0-dbg_1.5.0-4_amd64.deb 270bd8c251ba5aa3ffb5044e12799dabc8b04f61149276681f15720348ed2b6d 29412 soundstretch_1.5.0-4_amd64.deb 3aec52b042d75861ed5cdba9f57d9479069f207f0f8a639351df8dde845dc396 35672 soundstretch-dbg_1.5.0-4_amd64.deb Files: da0e26bf28068d8a42e14dbe7fece23c 2123 libs optional soundtouch_1.5.0-4.dsc 010687f5a183dbf79427d44576d8fbd9 10330 libs optional soundtouch_1.5.0-4.debian.tar.gz 55d975ddf47716f35f671d3a057f7a7c 12204 libdevel optional libsoundtouch-dev_1.5.0-4_amd64.deb 34767e315016a8bf86a364b61adce30e 40616 libs optional libsoundtouch0_1.5.0-4_amd64.deb d99d3e00ce141a320bf1f5edc311eb35 64684 debug extra libsoundtouch0-dbg_1.5.0-4_amd64.deb 512fcd6924b10b5ebf53e60912b45882 1248 libdevel optional lib32soundtouch-dev_1.5.0-4_amd64.deb f3f1b897b0a05dca0d782185ae38a026 25392 libs optional lib32soundtouch0_1.5.0-4_amd64.deb e898d150876186777ab30fe092a51fee 63790 debug extra lib32soundtouch0-dbg_1.5.0-4_amd64.deb fa9ca6f5fd1bfbc3c1f0447483fdea42 29412 sound optional soundstretch_1.5.0-4_amd64.deb 319e41575a79d55f4b7d2f92623b 35672 debug extra soundstretch-dbg_1.5.0-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iQIcBAEBCgAGBQJNaYHDAAoJEBWetcTvyHdMS8kP/RP+cD8z8m061ylOjebNrPOV n21pKeGHBKV0aQxuhl33L1NjjBz0aIb/+zOGvjjHXqKq1Bghg0ddtbAZDt0FlcAz 2d93+k+lnXUFPBvtBgMbuT1UDblua09Qc2sRCN+ZUm1PLvMEi72InkvV1qjB9Qvs w+ruV1R81gdCFnHzZM03ioLuFUC+FfvCqJ84fcnPqHJNokPFqPTbHUjf8DVgt42+ 7+KZ7x7CZE45ByIAo3yBatHl/DIkIaTyXBGib84/WafiZXOBS+LHKvZdUGQjDztT 5oCUadwMfPL6ZzAIVi7CX2vrnJb/o6yGKMcWyWbI2SHJH3F46ddWRGjk/yEs0lJ1 Qv5pCllHu59b3+buMpFTh6m3OKYC/FJIElLfSYE
Bug#615269: audacity: Dependency conflict on installation on libsoundtouch
On Sat, Feb 26, 2011 at 5:12 PM, Benjamin Drung bdr...@debian.org wrote: reassign 615269 libsoundtouch0 1.5.0-3 thanks Am Samstag, den 26.02.2011, 17:07 +0100 schrieb Daniel Andersson: I don't know if it's Pidgin, Audacity or libsoundtouch that should be contacted, but I asked on #debian and someone suggested Audacity. The problem lies in soundtouch. libsoundtouch0 conflicts with libsoundtouch1c2, but these two package should be installable side-by-side. I'm not really sure what happened but I guess gst-plugins-bad0.10 (and others) were supposed to get updated or gotten a sourceful NMU and never did. Since otherwise this would have happened when moving the package from experimental. I commited some changes to git that should close this by letting libsoundtouch1c2 and libsoundtouch0 be installable side by side. This line which has all the affected packages now works (assuming the user never removed libsoundtouch1c2 and libsoundtouch1-dev for OCAML): sudo apt-get install ardour djplay mixxx audacity freecycle gstreamer0.10-plugins-bad ihu yatm libsoundtouch-ocaml libsoundtouch-ocaml-dev liquidsoap This should help fix this mess until all the BinNMU/NMU/Regular uploads get eventually done. Hopefully the git version gets approved and uploaded soon. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615141: libsoundtouch0: conflicts with gstreamer-plugins-bad libpurple/pidgin
Hello: A possible fix has been commited to git. Waiting for it to get approved and uploaded. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615512: Rebuild against libsoundtouch-dev in Sid
Source: djplay Version: 0.5.0-3.1 Severity: wishlist Hello: Please replace build dependency libsoundtouch1-dev with libsoundtouch-dev. libsoundtouch-dev currently provides libsoundtouch1-dev as a convenience but please use libsoundtouch-dev. Thanks in advance. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613677: slv2: Please recompile against versioned redland
Hey all: Just a FYI. Bug #613673 already got fixed/closed. Not sure if there is any other holdup. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615529: Rebuild against libsoundtouch-dev in Sid
Source: ihu Version: 0.6.0-2 Severity: wishlist Hello: Please replace build dependency libsoundtouch1-dev with libsoundtouch-dev. libsoundtouch-dev currently provides libsoundtouch1-dev as a convenience but please use libsoundtouch-dev instead. Thanks in advance. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#615269: audacity: Dependency conflict on installation on libsoundtouch
On Sat, Feb 26, 2011 at 5:12 PM, Benjamin Drung bdr...@debian.org wrote: reassign 615269 libsoundtouch0 1.5.0-3 thanks Am Samstag, den 26.02.2011, 17:07 +0100 schrieb Daniel Andersson: I don't know if it's Pidgin, Audacity or libsoundtouch that should be contacted, but I asked on #debian and someone suggested Audacity. The problem lies in soundtouch. libsoundtouch0 conflicts with libsoundtouch1c2, but these two package should be installable side-by-side. I'm not really sure what happened but I guess gst-plugins-bad0.10 (and others) were supposed to get updated or gotten a sourceful NMU and never did. Since otherwise this would have happened when moving the package from experimental. I commited some changes to git that should close this by letting libsoundtouch1c2 and libsoundtouch0 be installable side by side. This line which has all the affected packages now works (assuming the user never removed libsoundtouch1c2 and libsoundtouch1-dev for OCAML): sudo apt-get install ardour djplay mixxx audacity freecycle gstreamer0.10-plugins-bad ihu yatm libsoundtouch-ocaml libsoundtouch-ocaml-dev liquidsoap This should help fix this mess until all the BinNMU/NMU/Regular uploads get eventually done. Hopefully the git version gets approved and uploaded soon. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#615141: libsoundtouch0: conflicts with gstreamer-plugins-bad libpurple/pidgin
Hello: A possible fix has been commited to git. Waiting for it to get approved and uploaded. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#613677: slv2: Please recompile against versioned redland
Hey all: Just a FYI. Bug #613673 already got fixed/closed. Not sure if there is any other holdup. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mma packaging annotated tag, upstream/1.7, created. upstream/1.7
Hello: Assuming you did a gbp-pull and git-buildpackage is configured correctly it should work. Also when I created the missing tag a while ago I confirmed that upstream/1.7 contain the correct source when compared to a tarball I downloaded from upstream and I also merged upstream/1.7 to master and verified that everything was peachy. So the git in alioth should be fine. Try doing a gbp-pull or cloning it again. You will get build errors during dh_install since files got renamed. I could fix them but not sure if you already fixed it all. Cheers, Miguel On Wed, Feb 2, 2011 at 7:53 AM, Joel Roth jo...@pobox.com wrote: Michael and others, I wonder if I made a mistake in merging the upstream version. When I try building this package, I get a huge raft of errors. Could someone see if these are common or readily solved? thanks, Joel -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mma packaging annotated tag, upstream/1.7, created. upstream/1.7
Hello: That should work. Try to pull the commit I just made to make sure. It should complain at dh_installchangelogs now. Cheers, Miguel On Wed, Feb 2, 2011 at 9:16 AM, Joel Roth jo...@pobox.com wrote: On Wed, Feb 02, 2011 at 08:09:44AM +, Miguel Colon wrote: Hello: Assuming you did a gbp-pull and git-buildpackage is configured correctly it should work. Also when I created the missing tag a while ago I confirmed that upstream/1.7 contain the correct source when compared to a tarball I downloaded from upstream and I also merged upstream/1.7 to master and verified that everything was peachy. So the git in alioth should be fine. Try doing a gbp-pull or cloning it again. You will get build errors during dh_install since files got renamed. I could fix them but not sure if you already fixed it all. Thanks Miguel, Looks better. With git-buildpackage, I now get as far as dh_install: dh_installdirs dh_install cp: cannot stat `./mma': No such file or directory The following line in mma.install appears to be at fault. mma usr/bin The executable is actally called mma.py. I'd like to do this: mma.py usr/bin/mma But according to 'man dh_install' the destination must be a directory. Any suggestions? thanks again, Joel -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] mma packaging annotated tag, upstream/1.7, created. upstream/1.7
Hello: Sure, I fixed a few things since I only planned to make 1 commit but made a mistake since I forgot about the dh_install limitations. Anyway since you seem to be doing well on your own now I was gonna leave it at this but I noticed that you added a new manpage on the source. When using quilt (3.0) all the changes should be done inside the debian folder and the source left untouched. You should revert the commit that adds docs/man/mma-gb.1 and add it as a patch in debian/patches that creates this file and (if applicable) report it upstream (this link should give you some info: http://dep.debian.net/deps/dep3/) . At this point you will probably also want to add a .gitignore file to ignore the .pc folder. Cheers, Miguel On Wed, Feb 2, 2011 at 5:44 PM, Joel Roth jo...@pobox.com wrote: On Wed, Feb 02, 2011 at 09:45:50AM +, Miguel Colon wrote: Hello: That should work. Try to pull the commit I just made to make sure. It should complain at dh_installchangelogs now. Great. It goes much further. A few lintian warnings remain. W: mma source: changelog-should-mention-nmu W: mma source: source-nmu-has-incorrect-version-number 1.7-1 W: mma source: no-human-maintainers W: mma source: ancient-standards-version 3.7.3 (current is 3.9.1) W: mma: binary-without-manpage usr/bin/mma-gb Will study the patches you made. Regards, Joel Cheers, Miguel -- Joel Roth ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: Libsoundtouch{0,1}-dev?
So looks like a transition to me, and we probably need to readjust ardour's build dependency (to libsoundtouch-dev). I can take care of this if agreed upon. Hello, yes it's a transition I was the one that made renamed it. Perhaps Alessio wants to provide further clarification. Last time I spoke with Alessio about it from what I understood and remember he was waiting for post-squeeze. But better to wait for an official response since I might have misunderstood. Ardour (perhaps among others) build-depends on libsoundtouch1-dev, but this is not built by the archive as soundtouch provides libsoundtouch-dev but not libsoundtouch1-dev. Is this just a typo in soundtouch packaging, or do we have a more serious problem? The source packages affected are: Package: ardour Package: audacity Package: djplay Package: freecycle Package: gst-plugins-bad0.10 Package: ihu Package: ocaml-soundtouch Package: rezound Package: yatm In addition: - liquidsoap just needs to be rebuilt whenever ocaml-soundtouch get updated since it depends on libsoundtouch-ocaml-dev and not libsoundtouch directly. - mixx just needs to be rebuilt since it depends on libsoundtouch-dev so it should be fine after a binary upload or something. I basically got this information by adding sid/experimental source repos to the source.list and doing: grep-dctrl -FBuild-Depends libsoundtouch -sPackage /var/lib/apt/lists/*Sources | sort | uniq and confirming with apt-cache rdepends (not sure if there was a better way or if doing it with these 2 commands is not exhaustive enough) I locally recompiled all the packages in a clean chroot when I made the initial rename and what I just posted are my notes from that time. Also, from what I wrote down, all packages except ocaml-soundtouch and liquidsoap worked with just renaming the build dependency but as luck would have it ardour is the only package that I forgot to document the changes I made to it so it would build. Finally I remember Alessio uploading a new version of audacity and freecycle to experimental using the renamed library so the transition on those 2 I assume is done or started. Hope I made some sense. Cheers, Miguel ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#611779: fglrx-modules-dkms Linux 2.6.38 support
Package: fglrx-modules-dkms Version: 1:11-1-1.1 Severity: wishlist Tags: patch Hello: The following commits breaks 2.6.38 kernel support: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff The error message from the log is: LD /var/lib/dkms/fglrx/11-1/build/built-in.o CC [M] /var/lib/dkms/fglrx/11-1/build/firegl_public.o /var/lib/dkms/fglrx/11-1/build/firegl_public.c: In function ‘fglrx_pci_suspend’: /var/lib/dkms/fglrx/11-1/build/firegl_public.c:853: error: implicit declaration of function ‘acquire_console_sem’ /var/lib/dkms/fglrx/11-1/build/firegl_public.c:875: error: implicit declaration of function ‘release_console_sem’ make[1]: *** [/var/lib/dkms/fglrx/11-1/build/firegl_public.o] Error 1 make: *** [_module_/var/lib/dkms/fglrx/11-1/build] Error 2 A possible solution is included in the following DEP-3 compliant patch (also attached): http://paste.debian.net/106284 As a disclaimer this patch will enable support for 2.6.38-rc3 and up but -rc1 and -rc2 won't be supported. Should not be a big issue since a debian package for this kernel is not yet available and only users that compile the kernel themselves are affected. If there are any errors on the patch feel free to modify it. Thanks for the great work! Here is a quote of the patch: Description: Add Linux 2.6.38 support The following commit renamed acquire_console_sem to console_lock and release_console_sem to console_unlock on the Linux kernel: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff Author: Miguel Colon debian.mic...@gmail.com Forwarded: no Last-Update: 2011-02-01 --- fglrx-driver-11-1.orig/common/lib/modules/fglrx/build_mod/firegl_public.c +++ fglrx-driver-11-1/common/lib/modules/fglrx/build_mod/firegl_public.c @@ -850,7 +850,12 @@ static int fglrx_pci_suspend(struct pci_ * happen much less frequent then without this workaround. */ if (state == PM_EVENT_SUSPEND) +#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,38) +console_lock(); +#else acquire_console_sem(); +#endif + if (firegl_cail_powerdown(privdev, state)) ret = -EIO; @@ -872,7 +877,11 @@ static int fglrx_pci_suspend(struct pci_ } if (state == PM_EVENT_SUSPEND) +#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,38) +console_unlock(); +#else release_console_sem(); +#endif KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, ret, NULL); @@ -896,7 +905,11 @@ static int fglrx_pci_resume(struct pci_d if (PMSG_EVENT(pdev-dev.power.power_state) == 0) return 0; if (PMSG_EVENT(pdev-dev.power.power_state) == PM_EVENT_SUSPEND) +#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,38) +console_lock(); +#else acquire_console_sem(); +#endif #ifdef FIREGL_USWC_SUPPORT // Restore the PAT after resuming from S3 or S4. @@ -921,7 +934,11 @@ static int fglrx_pci_resume(struct pci_d firegl_cail_powerup(privdev); if (PMSG_EVENT(pdev-dev.power.power_state) == PM_EVENT_SUSPEND) +#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,38) +console_unlock(); +#else release_console_sem(); +#endif PMSG_EVENT(pdev-dev.power.power_state) = 0; KCL_DEBUG_TRACEOUT(FN_FIREGL_ACPI, 0, NULL); -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-rc2-custom-original (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fglrx-modules-dkms depends on: ii dkms 2.1.1.2-5 Dynamic Kernel Module Support Fram fglrx-modules-dkms recommends no packages. Versions of packages fglrx-modules-dkms suggests: ii fglrx-driver 1:11-1-1.1 non-free ATI/AMD RadeonHD display -- no debconf information Description: Add Linux 2.6.38 support The following commit renamed acquire_console_sem to console_lock and release_console_sem to console_unlock on the Linux kernel: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=ac751efa6a0d70f2c9daef5c7e3a92270f5c2dff Author: Miguel Colon debian.mic...@gmail.com Forwarded: no Last-Update: 2011-02-01 --- fglrx-driver-11-1.orig/common/lib/modules/fglrx/build_mod/firegl_public.c +++ fglrx-driver-11-1/common/lib/modules/fglrx/build_mod/firegl_public.c @@ -850,7 +850,12 @@ static int fglrx_pci_suspend(struct pci_ * happen much less frequent then without this workaround. */ if (state == PM_EVENT_SUSPEND) +#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,38) +console_lock(); +#else acquire_console_sem(); +#endif + if (firegl_cail_powerdown(privdev, state)) ret = -EIO; @@ -872,7 +877,11 @@ static int fglrx_pci_suspend(struct pci_ } if (state == PM_EVENT_SUSPEND) +#if LINUX_VERSION_CODE = KERNEL_VERSION(2,6,38
Bug#611779: Version Information
Hello again, I used the reportbug package and it reported the version of the NMU package I made to test the patch. The bug is on 1:11-1-1 that is available on the experimental repository and technically in all the others one too. Cheers, Miguel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Introduction
Heh, thank y'all. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Introduction
Hello Multimedia Team: I was working on updating the soundtouch package that was orphaned some time ago. I uploaded it to mentors.debian.net and Alessio Treglia was kind enough to sponsor it. I'm interested on joining the team so I can continue maintaining this package and possibly help on others. I have an alioth account micove-guest and already subscribed to both mailing list as instructed in the http://wiki.debian.org/DebianMultimedia/Join page. I also have experience using debhelper/quilt and always build on a clean chroot using pbuilder. I also have read the debian policy / debian's new maintainers guide / debian's developer reference / DEP-3 guidelines / DEP-5 guidelines / etc. I don't have much experience using git besides downloading from projects using clone/checkout/pull but I will read http://wiki.debian.org/PackagingWithGit and other sources to get a better hang on it. Look forward to your guidance and assistance. Regards, - Miguel Colon ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
RFS: soundtouch (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.5.0-0.1 of soundtouch. It builds these binary packages: lib32soundtouch0 - Sound stretching library (32 bit) lib32soundtouch0-dev - Development files for sound stretching library (32 bit) libsoundtouch0 - Sound stretching library libsoundtouch0-dev - Development files for sound stretching library soundstretch - Stretches and pitch-shifts sound independently The package appears to be lintian clean. The upload would fix these bugs: 516905, 543729, 585557 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/s/soundtouch - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/s/soundtouch/soundtouch_1.5.0-0.1.dsc I would be glad if someone uploaded this package for me. The package seems to be orphaned and the person that intends to adopt it seems to be unavailable. Please CC me with any comments or suggestions. Kind regards Miguel Colon -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktik+iwmayahmxjmhxbx5vgtl=-vjsj=ggiu3y...@mail.gmail.com
Bug#546981: soundtouch -- development files for sound stretching library
Hello: Any updates on this? I tried to contact Paul on this back on August but never got a reply. I made a package of this back in August and just uploaded it to mentors.debian.net URL: http://mentors.debian.net/debian/pool/main/s/soundtouch I upgraded the package to quilt 3.0, made it lintian clean, and made sure to follow policy 3.9.1. Hope this helps in any way or gets sponsored. Kind regards Miguel Colon -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546981: soundtouch -- development files for sound stretching library
Hello: Any updates on this? I tried to contact Paul on this back on August but never got a reply. I made a package of this back in August and just uploaded it to mentors.debian.net URL: http://mentors.debian.net/debian/pool/main/s/soundtouch I upgraded the package to quilt 3.0, made it lintian clean, and made sure to follow policy 3.9.1. Hope this helps in any way or gets sponsored. Kind regards Miguel Colon -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktinjx0ok2s58nj_4rk_86ytvbse0gdzgnpswm...@mail.gmail.com
