Bug#857423: link to sso page is broken
On Tue, Mar 14, 2017 at 9:02 PM, Raphael Hertzog wrote: > On Tue, 14 Mar 2017, anatoly techtonik wrote: >> Git is not linked to Debian bugtracker to reference and close bugs >> automatically, isn't it? > > There's no general rule but this repository has no such integration (most > packaging repository use some integration that parses debian/changelog > but here it's not really relevant). I mean it really helps to learn the code. And it would be nice if BTS code was also available. Right now it lists only copyright info - https://www.debian.org/Bugs/ CC: ow...@bugs.debian.org
Bug#857423: link to sso page is broken
Package: tracker.debian.org Login page https://tracker.debian.org/accounts/login/ refers to non-existing https://sso.debian.org/spkac/enroll/ page for SSO login.
Bug#857422: fails to send report from root in container
Package: reportbug
Version: 6.6.3
Trying to submit report under root fails after editing message with vim.
Report will be sent to "Debian Bug Tracking System"
Submit this report on tracker.debian.org (e to edit)
[Y|n|a|c|e|i|l|m|p|q|d|t|s|?]?
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2211, in
main()
File "/usr/bin/reportbug", line 1081, in main
return iface.user_interface()
File "/usr/bin/reportbug", line 2203, in user_interface
self.options.envelopefrom)
File "/usr/lib/python2.7/dist-packages/reportbug/submit.py", line
316, in send_report
msgname = os.path.expanduser(outfile) or ('/var/tmp/%s.bug' % package)
File "/usr/lib/python2.7/posixpath.py", line 261, in expanduser
if not path.startswith('~'):
AttributeError: 'NoneType' object has no attribute 'startswith'
--
anatoly t.
Bug#830892: A better patch
Attached patch sets --user option only if no --system, --prefix or --target are defined, which are mutually exclusive to this option. diff --git a/pip/commands/install.py b/pip/commands/install.py index 13b328f..dcc4cd4 100644 --- a/pip/commands/install.py +++ b/pip/commands/install.py @@ -55,12 +55,6 @@ class InstallCommand(RequirementCommand): def __init__(self, *args, **kw): super(InstallCommand, self).__init__(*args, **kw) -default_user = True -if running_under_virtualenv(): -default_user = False -if os.geteuid() == 0: -default_user = False - cmd_opts = self.cmd_opts cmd_opts.add_option(cmdoptions.constraints()) @@ -110,7 +104,6 @@ class InstallCommand(RequirementCommand): '-I', '--ignore-installed', dest='ignore_installed', action='store_true', -default=default_user, help='Ignore the installed packages (reinstalling instead).') cmd_opts.add_option(cmdoptions.no_deps()) @@ -122,7 +115,6 @@ class InstallCommand(RequirementCommand): '--user', dest='use_user_site', action='store_true', -default=default_user, help="Install to the Python user install directory for your " "platform. Typically ~/.local/, or %APPDATA%\Python on " "Windows. (See the Python documentation for site.USER_BASE " @@ -132,10 +124,10 @@ class InstallCommand(RequirementCommand): cmd_opts.add_option( '--system', -dest='use_user_site', -action='store_false', -help="Install using the system scheme (overrides --user on " - "Debian systems)") +dest='use_system_location', +action='store_true', +help="Install into operating system location (Debian changes " + "defaults to install to user dir)") cmd_opts.add_option( '--egg', @@ -233,6 +225,15 @@ class InstallCommand(RequirementCommand): if options.build_dir: options.build_dir = os.path.abspath(options.build_dir) + +# computing install location defaults +if (not options.use_user_site and not options.prefix_path and not +options.target_dir and not options.use_system_location): +if not running_under_virtualenv() and os.geteuid() != 0: +options.use_user_site = True +options.ignore_installed = True + + options.src_dir = os.path.abspath(options.src_dir) install_options = options.install_options or [] if options.use_user_site: @@ -241,6 +242,11 @@ class InstallCommand(RequirementCommand): "Can not combine '--user' and '--prefix' as they imply " "different installation locations" ) +if options.use_system_location: +raise CommandError( +"Can not combine '--user' and '--system' as they imply " +"different installation locations" +) if virtualenv_no_global(): raise InstallationError( "Can not perform a '--user' install. User site-packages "
Bug#717834: Fwd: Kill DEHS
On Fri, Aug 28, 2015 at 12:38 AM, Lucas Nussbaum wrote: > > Given that UDD does more, it could also implement a stripped down > version. But I'm not sure what is the functionality you are looking for. > Monitor a specific package using RSS? Stats? > As for me, the most useful Debian External Health Status is the stats for the upstream package, so RSS is not as important as getting the status of upstream support. 1. If link with upstream is correct, and the history of all the checks 2. Version of same upstream code in different other distributions 3. CVEs and bugs for this upstream version, including different dists 4. If there is a new version, does it automatically builds 5. Which upstream version breaks automatic package build 6. Which upstream version changes API/ABI compatibility So, it is more like continuous integration for upstream service. It will be also nice to get .deb from this service for testing new versions. -- anatoly t.
Bug#717834: Fwd: Kill DEHS
On Thu, Aug 27, 2015 at 4:45 PM, anarcat wrote: > On Thu, Jul 25, 2013 at 05:01:46PM +0300, anatoly techtonik wrote: > > Package: qa.debian.org > > > > DEHS service at http://dehs.alioth.debian.org/ looks alive, but in > > fact it is dead and its database is offline for almost two years, > > which is shown by multiple reports in ML over that time > > http://lists.alioth.debian.org/pipermail/dehs-devel/ > > > > It's time to kill it so that it won't confuse people anymore, and > > redirect people from http://wiki.debian.org/DEHS to something like: > > > > 1. ROSA Upstream Tracker - see it in action - > > http://upstream-tracker.org/updates/rosa/2012/ - it is GPL'ed, so it > > should be easy to port it to Debian. > > This now says it is unmaintained: > > http://upstream.rosalinux.ru/ > > "Unfortunately, we cannot support the service anymore. Sorry for > inconvenience. The suitable replacement for this tool will be available > at github.com/lvc soon. ROSA Laboratory, 21 July 2015. " > > The database itself says "has been generated on 2014-09-04"... so is > probably not a good way forward. > Indeed. > > 2. http://people.ubuntuwire.org/~lucas/merges.html > > I am not sure how that helps. > It should be replaced with UDD, because basically it is UDD view. > > 3. http://duck.debian.net > > Maybe? > > > 4. Anything else? > > So what's the solution here? > > Should we bug duck people to implement this? > > UDD seems to help here, but it does much more than this... > > I am using the latter now, in combination with feed2imap: > > - name: Debian todo > url: > https://udd.debian.org/dmd/?email1=anarcat%40debian.org&email2=&email3=&packages=&ignpackages=&format=rss#todo > target: [ *target, debian-udd-todo ] > It looks like the DEHS functionality can be easily reimplemented with simple Python app and a uptodate replica of UDD database. The DEHS structure: - Pkgs without watch file - Pkgs not in sync with upstream - Pkgs with watch file but no upstream version checkable - DEHS statistics - with/without watch diagram - working/bogus/empty watch - daily graphs - with - without - failed - uptodate packages -- anatoly t.
Bug#771714: cp preserves mode with --no-preserve=mode (should clear x)
Package: coreutils This is a continuation of archived https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488024 The above bug closed as wontfix in Debian, but seems fixed in Ubuntu https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/379233 Why it is important to make "cp --no-preserve=mode" work? Given: 1. Debian 7.7 2. Alien mounted FS system where all files are executable 3. cp --no-preserve=mode /alien/inventory /tmp/ Expected: -rw-r--r-- 1 rootroot 456 Dec 1 20:20 inventory Actual: -rwxr-xr-x 1 rootroot 456 Dec 1 20:20 inventory The reasons why it is important are listed in Ubuntu bug. In my case I am setting up environment with Ansible, which supports executable inventory files, but this file is not. -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768359: git clone unconditionally creates worktree with permission 755 & ~umask instead of 777 & ~umask
On Fri, Nov 7, 2014 at 2:39 AM, Jonathan Nieder wrote:
> tags 768359 + upstream patch fixed-upstream
> quit
>
> Hi,
>
> anatoly techtonik wrote:
>
>> git clone unconditionally creates main dir with 755
>> mode ignoring ACL and POSIX permissions if they
>> are different.
>>
>> More info here:
>> https://stackoverflow.com/questions/10637416/git-clone-respects-umask-except-for-top-level-project-directory
>>
>> Fix is available in 1.7.11.3 commit
>
> Thanks for a clear report.
>
> [...]
>> Severity: important
>
> Can you say a little more about this? The old behavior of using
> (0755 & ~umask) instead of (0777 & ~umask) wouldn't be a security
> problem, making a worktree shared within a group tends to require
> writing the setgid ("sticky") bit anyway, and using chmod once works
> as a workaround.
>
> So it seems like a normal bug, instead of one with a major effect on
> usability.
>
> That said, if I have missed something that makes this a more major
> problem (e.g., if it breaks some other tool in wheezy) then I'd be
> happy to apply the fix.
I am not proficient with umask + setguid sticky, but Git doesn't
respects whatever it was set in user session for sure. My specific
case - when I mkdir in /var/www, the directory is created with group
write permissions. When I git clone repository, the directory created
by git doesn't have group write permission.
This affects other users in my group who will try to `git pull` there.
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768359: git: clone unconditionally creates dir with 755 ignoring ACL and POSIX permisson setup
Package: git Version: 1:1.7.10.4-1+wheezy1 Severity: important Dear Maintainer, git clone unconditionally creates main dir with 755 mode ignoring ACL and POSIX permissions if they are different. More info here: https://stackoverflow.com/questions/10637416/git-clone-respects-umask-except-for-top-level-project-directory Fix is available in 1.7.11.3 commit 45d4fdc2dc74c657a9c2e95bf04aed539fdcb0a4 -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) 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 git depends on: ii git-man 1:1.7.10.4-1+wheezy1 ii libc62.13-38+deb7u6 ii libcurl3-gnutls 7.26.0-1+wheezy10 ii liberror-perl0.17-1 ii libexpat12.1.0-1+deb7u1 ii perl-modules 5.14.2-21+deb7u2 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages git recommends: ii less 444-4 ii openssh-client [ssh-client] 1:6.0p1-4+deb7u2 ii patch2.6.1-3 ii rsync3.0.9-4 Versions of packages git suggests: ii gettext-base 0.18.1.1-9 pn git-arch pn git-cvs pn git-daemon-run | git-daemon-sysvinit pn git-doc pn git-el pn git-email pn git-gui pn git-svn pn gitk pn gitweb -- no debconf information -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744852:
Well, even with mailto: integration it takes me absolute minimal of 8 actions (all mouse clicks) to go through a full cycle if subscription to a single bug, so I confirm that the issue exists. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#761007: /robots.txt is invalid, prevents bugs from being indexed by Internet Archive
Package: bugs.debian.org Access to Debian bug reports in Internet Archive is blocked by robots.txt http://web.archive.org/web/*/https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736214 Current contents of https://bugs.debian.org/robots.txt: [cut here] User-Agent: Googlebot, bingbot, yandexbot, baiduspider, ia_archiver Allow: /cgi-bin/bugreport.cgi?bug= Allow: /cgi-bin/pkgreport.cgi?pkg=*;dist=unstable$ Disallow: /*/ User-agent: * Disallow: / [cut here] Looks like a problem is caused by User-Agent line, which lists user agents through comma instead of specifying every agent on separate line: [cut here] User-Agent: Googlebot User-Agent: bingbot User-Agent: yandexbot User-Agent: baiduspider User-Agent: ia_archiver Allow: /cgi-bin/bugreport.cgi?bug= Allow: /cgi-bin/pkgreport.cgi?pkg=*;dist=unstable$ Disallow: /*/ User-agent: * Disallow: / [cut here] Specifying each agent on separate line makes sense, because user-agent string can contain some special character and be pretty long. See section `3.2 File Format Description` for details: http://www.robotstxt.org/norobots-rfc.txt -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744852:
If you use web-based client, the process is not that painful after setting mailto: handler correctly. As for actual SSO integration I believe it depends on #277744. http://googlesystem.blogspot.com/2012/02/open-mailto-links-using-gmail-in-google.html -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717834: Fwd: Kill DEHS
Package: qa.debian.org DEHS service at http://dehs.alioth.debian.org/ looks alive, but in fact it is dead and its database is offline for almost two years, which is shown by multiple reports in ML over that time http://lists.alioth.debian.org/pipermail/dehs-devel/ It's time to kill it so that it won't confuse people anymore, and redirect people from http://wiki.debian.org/DEHS to something like: 1. ROSA Upstream Tracker - see it in action - http://upstream-tracker.org/updates/rosa/2012/ - it is GPL'ed, so it should be easy to port it to Debian. 2. http://people.ubuntuwire.org/~lucas/merges.html 3. http://duck.debian.net 4. Anything else? -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717824: anonscm.debian.org needs a feedback channel
Package: general http://anonscm.debian.org/ doesn't have any coordinates in site footer to report issues such as this one http://anonscm.debian.org/viewvc/python-modules/packages/python-pyftpdlib/trunk/debian/watch?r1=13515&r2=13521 and others. -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717561: closed by Mònica Ramírez Arceda (bug 717561 is RFP for package fabric already in Debian)
I searched using this form and it doesn't show anything http://packages.debian.org/search?keywords=fabric&searchon=names&suite=stable§ion=all -- anatoly t. On Tue, Jul 23, 2013 at 12:00 AM, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the wnpp package: > > #717561: RFP: fabric -- a simple pythonic tool for remote deployment and SSH > automation > > It has been closed by Mònica Ramírez Arceda . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Mònica Ramírez Arceda > by > replying to this email. > > > -- > 717561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717561 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > -- Forwarded message -- > From: "Mònica Ramírez" Arceda > To: 717561-cl...@bugs.debian.org > Cc: > Date: Mon, 22 Jul 2013 22:51:00 +0200 > Subject: bug 717561 is RFP for package fabric already in Debian > Hi, > > I'm closing this bug because this package is already in Debian: > http://packages.qa.debian.org/fabric > > Regards. > > -- Forwarded message -- > From: anatoly techtonik > To: Debian BTS Submit > Cc: > Date: Mon, 22 Jul 2013 13:45:12 +0300 > Subject: RFP: fabric -- a simple pythonic tool for remote deployment and SSH > automation > Package: wnpp > Severity: wishlist > > Package name : fabric > Version : 1.6.1 > Upstream Author : https://github.com/fabric/fabric/blob/1.6/AUTHORS > URL : http://docs.fabfile.org/ > License : BSD (https://github.com/fabric/fabric/blob/1.6/LICENSE) > Description : Python library and command-line tool for streamlining > the use of SSH for application deployment or systems administration > tasks. > > It provides operations for executing local or remote shell commands > (normally or via sudo), uploading/downloading files and auxiliary > functions such as prompting the running user for input, or aborting > execution. > > -- > anatoly t. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#717561: RFP: fabric -- a simple pythonic tool for remote deployment and SSH automation
Package: wnpp Severity: wishlist Package name : fabric Version : 1.6.1 Upstream Author : https://github.com/fabric/fabric/blob/1.6/AUTHORS URL : http://docs.fabfile.org/ License : BSD (https://github.com/fabric/fabric/blob/1.6/LICENSE) Description : Python library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides operations for executing local or remote shell commands (normally or via sudo), uploading/downloading files and auxiliary functions such as prompting the running user for input, or aborting execution. -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702715:
If the package is broken and doesn't work at all, what is the reason to upload it to unstable with low priority?
Bug#653068:
The same problem trying Debian Squeeze in virt-manager with qxl on Fedora 17: unaligned pointer 0x8ef20002 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#581626: trac crash seems likely to be due to sqlite or python, not trac directly
On Tue, Dec 6, 2011 at 7:17 AM, Daniel Kahn Gillmor wrote: > > Are you still able to reproduce this error? > > No. I am using Trac 0.12 in custom virtualenv installation that's independent of Debian libraries. Even though Martin does a great job in maintaining Trac packages, changing something in Debian requires too much pain, so I decided not to waste time anymore.
Bug#646549:
affects 649349 xen-hypervisor-4.1-amd64 affects 646945 svn-buildpackage -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646549:
I'd say the priority should be raised to critical. See bug #646945 for another symptom.
Bug#146207:
On Mon, Oct 31, 2011 at 7:24 PM, Christian PERRIER wrote: > Quoting anatoly techtonik (techto...@gmail.com): >> Why is it so hard to fix this, i.e. to teach aptitude update apt-get >> structures for packages that aptitude puts on hold? >> >> This inconsistency is already causing troubles with SCM tools. >> http://trac.mcs.anl.gov/projects/bcfg2/ticket/1066 >> >> > > Anybody is free to send a patch if this is "not so hard". > > (please note that I am *not* the aptitude maintainer) Ok, I'll ask it the other way. Can anybody, who investigated the problem tell - why is it so hard to fix this? P.S. I can send patches in Python, not C++ -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#146207:
Why is it so hard to fix this, i.e. to teach aptitude update apt-get structures for packages that aptitude puts on hold? This inconsistency is already causing troubles with SCM tools. http://trac.mcs.anl.gov/projects/bcfg2/ticket/1066 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646945: [Svn-bp-devel] 'Illegal instruction' when executing)
Thanks for the explanation. I'll work more closely with the person, who created this machine and let you know if the problem persists in a new setup. -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646945: closed by Neil Williams (Re: [Svn-bp-devel] Bug#646945: svn-buildpackage: 'Illegal instruction' when executing)
reopen On Sat, Oct 29, 2011 at 4:35 PM, Debian Bug Tracking System wrote: > >> I understand that, but I am nor Perl expert, neither have time to >> become one, so unless somebody tells me what to do, chances that I can >> do anything on my own are minimal. If that `svn-buildpackage` was >> written in Python, I'd just run 'python -v -m pdb `which >> svn-buildpackage`' and could get you the source line with the error in >> no time. > > I'm fairly sure it's not actually a bug in the source code of the Perl > scripts themselves, so that approach won't get far. I see no reason to > think this is a problem within svn-buildpackage itself, it is something > to do with your VM configuration. That's not helpful. Perl executes ok. Other perl scripts also execute ok. So the problem in the way Perk executed this particular script. Maybe in the way Perl imports external modules. Think about it - you should know. Perhaps the problem is in some binary extension or svn bindings. I don't have experience with that. >> > Also try creating a Wheezy chroot and testing in that. >> >> Oh no. That's too hardcore. I don't want to pollute this VM more than >> necessary. > > debootstrap wheezy dir/ > chroot dir/ I am running Squeeze, not Wheezy. Is it ok? > It's not hard. Something had to call that to create the VM in the > first place. It's how Debian Installer creates the installation. The machine was created with Xen. Will it create other dirs like pbuilder does somewhere in /var (or /usr)? I'd really like to keep this machine clean of any extra stuff. >> > Anything and everything. I can't tell you which ones because this >> > problem only affects this one single machine. I also use svn-bp on >> > various virtual environments for buildd operations, again without any >> > errors. >> >> I certainly don't have time for that, and I am not running Debian >> anywhere else. > > (yet you're expecting to use svn-buildpackage to build Debian packages > to use on presumably other Debian machines?) I need to a stable version 0.6 of Bitten (which is trac-bitten) that was not released yet in Debian. I can't build it on other machine, because latest Python policy (not new version of package) requires versions of packages like buildhelper that are absent on previous versions. >> > If it only persists on this one system, the chances of identifying the >> > actual problem approach zero. >> >> I see. I good reason to consider decoupling our application from >> Debian. Thanks for trying, though. ,) > > I think you are blaming the wrong package - just because one package > shows the error does not mean that the bug actually lies in that > package. I suspect a problem in the VM itself and it's the kind of > problem that will show up if you switch to using something else. i.e. > it is likely to be a persistent problem with that one VM. I was about to say that there are no problems with VM, because even `dmesg`... and then I checked dmesg and found this: [7288028.138482] svn-buildpackag[8557] trap invalid opcode ip:7fefad14a8b0 sp:7fffd51ad528 error:0 in ld-2.11.2.so[7fefad137000+1e000] [7288037.187741] svn-buildpackag[8560] trap invalid opcode ip:7fb20fff78b0 sp:7fff59f41e68 error:0 in ld-2.11.2.so[7fb20ffe4000+1e000] [7288040.851023] svn-buildpackag[8561] trap invalid opcode ip:7fb5271a68b0 sp:7fff9bd085e8 error:0 in ld-2.11.2.so[7fb527193000+1e000] [7288046.695367] svn-buildpackag[8562] trap invalid opcode ip:7fc71a79e8b0 sp:7fff0a766438 error:0 in ld-2.11.2.so[7fc71a78b000+1e000] [7288049.664150] svn-buildpackag[8563] trap invalid opcode ip:7f469df398b0 sp:7fffce8d6ad8 error:0 in ld-2.11.2.so[7f469df26000+1e000] [7288091.143575] svn-buildpackag[8573] trap invalid opcode ip:7fa6f27bb8b0 sp:7fffa4b7d068 error:0 in ld-2.11.2.so[7fa6f27a8000+1e000] [7288094.079603] svn-buildpackag[8574] trap invalid opcode ip:7f7841c128b0 sp:7fff321b5aa8 error:0 in ld-2.11.2.so[7f7841bff000+1e000] [7288096.356146] svn-buildpackag[8575] trap invalid opcode ip:7f8e473ba8b0 sp:7fff2ebe8098 error:0 in ld-2.11.2.so[7f8e473a7000+1e000] [7288129.539053] svn-buildpackag[8659] trap invalid opcode ip:7fef85d4a8b0 sp:7fff3715dbf8 error:0 in ld-2.11.2.so[7fef85d37000+1e000] [7288140.879078] svn-buildpackag[8660] trap invalid opcode ip:7feb04c668b0 sp:7fffea506928 error:0 in ld-2.11.2.so[7feb04c53000+1e000] [7288149.588406] svn-buildpackag[8661] trap invalid opcode ip:7fac1d7a48b0 sp:7fff69145048 error:0 in ld-2.11.2.so[7fac1d791000+1e000] [7288152.363837] svn-buildpackag[8662] trap invalid opcode ip:7fdb3595a8b0 sp:7fff52f4e4b8 error:0 in ld-2.11.2.so[7fdb35947000+1e000] [7288952.542530] svn-buildpackag[20366] trap invalid opcode ip:7f9befd4d8b0 sp:7fff3fc0deb8 error:0 in ld-2.11.2.so[7f9befd3a000+1e000] [7347887.781547] svn-buildpackag[27047] trap invalid opcode ip:7f51ed2d48b0 sp:78b4f768 error:0 in ld-2.11.2.so[7f51ed2c1000+1e000] [7347897.159074] svn-buildpackag[27048] trap invalid opcode ip:7f7252d4b8b0 sp:7d8db788 error:0 in ld-2.11.2.so[7f7252d38000+1e000
Bug#646945: [Svn-bp-devel] Bug#646945: svn-buildpackage: 'Illegal instruction' when executing
On Sat, Oct 29, 2011 at 2:35 PM, Neil Williams wrote: > On Sat, 29 Oct 2011 13:46:48 +0300 > anatoly techtonik wrote: > >> On Sat, Oct 29, 2011 at 1:36 PM, Neil Williams wrote: >> > tag 646945 + unreproducible >> > quit > > i.e. you're going to have to do all the tests yourself and it's likely > that unless you work out what is wrong, this bug will not be identified. I understand that, but I am nor Perl expert, neither have time to become one, so unless somebody tells me what to do, chances that I can do anything on my own are minimal. If that `svn-buildpackage` was written in Python, I'd just run 'python -v -m pdb `which svn-buildpackage`' and could get you the source line with the error in no time. >> > Do you get problems with any other Perl scripts? >> >> None that I know of. Do you have any specific examples that I can run? > > dpkg-buildpackage > dpkg-parsechangelog Both work as expected. > Also try svn-inject and svn-upgrade. Both fail with the same 'Illegal instruction'. > Also try creating a Wheezy chroot and testing in that. Oh no. That's too hardcore. I don't want to pollute this VM more than necessary. >> > (apt-get --reinstall install svn-buildpackage) >> >> Done. Didn't help. This system is brand new VM box - there is no extra >> stuff installed, so it is not usual desktop or server box on steroids. >> Perhaps something is missing from svn-buildpackage dependencies? > > .. or a misconfiguration somewhere in the base system. I suspect that Bcfg2 could break some things, but you've seen the dependencies yourself. There is no hardcore hacking on this box, especially with Perl. > I've tested in a clean pbuilder chroot and svn-bp is fine with it's own > dependencies. Then, when I use `debcheckout svn-buildpackage` and > install it's build-dependencies, it builds itself fine without errors. As I said - I am not a Perl expert, but in Python world if Python code misbehaves so badly that it doesn't even execute - I am able to figure out what happens very quickly regardless of the platform (well, unless it is some web-service that requires os-specific methods to get to the entrypoint). >> > The first commands svn-buildpackage tries are calls to subversion >> > itself and that's probably the first place to check for something which >> > is compiled. >> >> What should I run to check? > > Anything and everything. I can't tell you which ones because this > problem only affects this one single machine. I also use svn-bp on > various virtual environments for buildd operations, again without any > errors. I certainly don't have time for that, and I am not running Debian anywhere else. > If it only persists on this one system, the chances of identifying the > actual problem approach zero. I see. I good reason to consider decoupling our application from Debian. Thanks for trying, though. ,) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646945: [Svn-bp-devel] Bug#646945: svn-buildpackage: 'Illegal instruction' when executing
On Sat, Oct 29, 2011 at 1:36 PM, Neil Williams wrote: > tag 646945 + unreproducible > quit > > On Fri, 28 Oct 2011 17:53:48 +0300 > anatoly techtonik wrote: > > I (and the rest of the team @ work) use svn-bp on squeeze on a daily > basis, I don't see these problems. > >> svn-buildpackage doesn't execute at all failing with the message >> Illegal instruction > > Do you get problems with any other Perl scripts? None that I know of. Do you have any specific examples that I can run? > Can you reinstall the package in case of some corruption problems? > > (apt-get --reinstall install svn-buildpackage) Done. Didn't help. This system is brand new VM box - there is no extra stuff installed, so it is not usual desktop or server box on steroids. Perhaps something is missing from svn-buildpackage dependencies? > The first commands svn-buildpackage tries are calls to subversion > itself and that's probably the first place to check for something which > is compiled. What should I run to check? > Does subversion work on your system? Yes. $ svn --version svn, version 1.6.12 (r955767) compiled May 31 2011, 16:12:12 ... >> Versions of packages svn-buildpackage depends on: >> ii devscripts 2.10.69+squeeze1 scripts to make the life of a >> Debi Not sure how should I check this. > Also check things like dpkg-parsechangelog. dpkg-parsechangelog works ok. >> ii subversion 1.6.12dfsg-6 Advanced version control system -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646945: [Svn-bp-devel] Bug#646945: svn-buildpackage: 'Illegal instruction' when executing
On Sat, Oct 29, 2011 at 9:59 AM, Jan Hauke Rahm wrote: > tag 646945 + moreinfo > thanks > > Hi, > > thanks for trying to improve Debian! > > On Fri, Oct 28, 2011 at 05:53:48PM +0300, anatoly techtonik wrote: >> Package: svn-buildpackage >> Version: 0.8.3 >> Severity: important >> >> svn-buildpackage doesn't execute at all failing with the message >> Illegal instruction > > Can you be a bit more specific? When exactly did you encounter this > behaviour. I've never seen this before. A test case would be nice. Also, > please run svn-buildpackage with --svn-verbose to have a bit more > output. I don't know how to be more specific. $ svn-buildpackage --svn-verbose Illegal instruction $ which svn-buildpackage /usr/bin/svn-buildpackage $ less `which svn-buildpackage` #!/usr/bin/perl ... $ which perl /usr/bin/perl $ -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646945: svn-buildpackage: 'Illegal instruction' when executing
Package: svn-buildpackage Version: 0.8.3 Severity: important svn-buildpackage doesn't execute at all failing with the message Illegal instruction -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages svn-buildpackage depends on: ii devscripts 2.10.69+squeeze1 scripts to make the life of a Debi ii file 5.04-5Determines file type using "magic" ii libcapture-tiny-perl 0.08-1module to capture STDOUT and STDER ii libfile-libmagic-perl 0.96-1Perl interface to libmagic for det ii liblocale-gettext-perl 1.05-6Using libc functions for internati ii libsvn-perl1.6.12dfsg-6 Perl bindings for Subversion ii liburi-perl1.54-2module to manipulate and access UR ii perl 5.10.1-17squeeze2 Larry Wall's Practical Extraction ii subversion 1.6.12dfsg-6 Advanced version control system ii unp2.0~pre4 unpack (almost) everything with on ii wget 1.12-2.1 retrieves files from the web Versions of packages svn-buildpackage recommends: ii debhelper 8.0.0 helper programs for debian/rules svn-buildpackage suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#601839: debian/rules: reword build-arch, build-indep one line fix
Package: debian-policy Severity: normal I propose a clarification to build-arch and build-indep fields: http://www.debian.org/doc/debian-policy/ch-source.html#s-debianrules - The build target should depend on those of the targets build-arch and build-indep that are provided in the rules file. + The build target should depend on build-arch and build-indep targets if they are provided in the rules file. Please, correct me if its wrong, but please make the wording more simple. Thanks. -- System Information: Debian Release: squeeze/sid APT prefers maverick-updates APT policy: (500, 'maverick-updates'), (500, 'maverick-security'), (500, 'maverick-backports'), (500, 'maverick') Architecture: i386 (i686) Kernel: Linux 2.6.35-22-generic (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 -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#441887: www.debian.org: APT-HOWTO is out of date
Could you, please, provide links to replacements from the headers of corresponding sections? The documentation is still available from the web, and its (Obsolete Documentation) confuses people without providing any hints where to look for updated information. For example, the HOW-TO its the top link for me when I search "build debian package from source". Unlike other manuals this one is concise and goes straight to the point. Maybe migrate some pages to Wiki? -- anatoly t. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575127: trac-bitten: need bitten-slave only binary package
Package: trac-bitten Version: 0.6b2 Severity: normal I'd like to install some Bitten slaves without installing Trac dependecy. Bitten allows that. Debian is not. -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.26.5-flamur5 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562963: Trac: wrong plugin names
Attaching the patch here as it won't be integrated upstream, because 0.11 branch accepts only critical bugfixes. 0.12 uses different approach that modifies behavior of plugin loader and backporting this can break things. -- anatoly t. On Mon, Jan 4, 2010 at 9:54 PM, anatoly techtonik wrote: > I've filed a ticket upstream at http://trac.edgewall.org/ticket/8929 > with the latest version of the patch for 0.11-stable > > It applies to branch clearly and executes as well. Previous version > was not complete. > -- > anatoly t. > > > > On Mon, Jan 4, 2010 at 6:01 PM, W. Martin Borgert wrote: >> tags 562963 +patch >> thanks >> >> Quoting "anatoly techtonik" : >>> >>> Here is a patch prototype for 0.11-dev branch. It won't work from the >>> start probably, because I don't have time to test it right now and >>> there is no guarantee I'll return to it next week. But it's better >>> than nothing. >> >> Anatoly, many thanks, I will try the patch these days! >> >> > correct_plugin_info.diff Description: Binary data
Bug#562963: Trac: wrong plugin names
I've filed a ticket upstream at http://trac.edgewall.org/ticket/8929 with the latest version of the patch for 0.11-stable It applies to branch clearly and executes as well. Previous version was not complete. -- anatoly t. On Mon, Jan 4, 2010 at 6:01 PM, W. Martin Borgert wrote: > tags 562963 +patch > thanks > > Quoting "anatoly techtonik" : >> >> Here is a patch prototype for 0.11-dev branch. It won't work from the >> start probably, because I don't have time to test it right now and >> there is no guarantee I'll return to it next week. But it's better >> than nothing. > > Anatoly, many thanks, I will try the patch these days! > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#562963: Trac: wrong plugin names
Here is a patch prototype for 0.11-dev branch. It won't work from the start probably, because I don't have time to test it right now and there is no guarantee I'll return to it next week. But it's better than nothing. -- anatoly t. On Sun, Jan 3, 2010 at 2:41 PM, anatoly techtonik wrote: > Hello, Martin > > Unfortunately. Trac plugins should be packaged as EGGs, because Trac > uses information from EGG distribution to display in web-admin. So far > I haven't found a way to get this information for imported module > installed in a plain directory, i.e. the one that doesn't end with > .egg like. > > For example WikiNotification plugin when installed with setuptools, > ends into tracwikinotification-0.2.1-py2.6.egg directory with EGG-INFO > and WikiBotification subdirs. First subdir is used by Trac to display > plugin info (via pkg_resources from setuptools) and the second > contains with actual module code. The path is detected by path to > files of imported module. > > In Debian there is Account Manager for example. It is imported from > /usr/share/pyshared/acct_mgr and actual meta information is in > /usr/share/pyshared/TracAccountManager-0.2.1dev.egg-info So far I > haven't found a way how to link these. > > I'll keep you updated. > -- > anatoly t. > > > > On Sat, Jan 2, 2010 at 4:38 PM, W. Martin Borgert wrote: >> Quoting "anatoly techtonik" : >>> >>> Yep. I know that. It is because plugin system in original WebAdmin >>> plugin was designed with eggs in mind (whatever that means). I already >>> have a patch to fix that, but I want to be sure it covers all cases. >> >> Would you mind to send the patch to 562...@bugs.debian.org, so >> that we can look at it? Even if your solution does not cover all >> cases or has other issues, you are at least one step ahead :~) >> >> The bug report is visible here: http://bugs.debian.org/562963 >> >> > get_module_path.diff Description: Binary data
Bug#562963: Trac: wrong plugin names
Hello, Martin Unfortunately. Trac plugins should be packaged as EGGs, because Trac uses information from EGG distribution to display in web-admin. So far I haven't found a way to get this information for imported module installed in a plain directory, i.e. the one that doesn't end with .egg like. For example WikiNotification plugin when installed with setuptools, ends into tracwikinotification-0.2.1-py2.6.egg directory with EGG-INFO and WikiBotification subdirs. First subdir is used by Trac to display plugin info (via pkg_resources from setuptools) and the second contains with actual module code. The path is detected by path to files of imported module. In Debian there is Account Manager for example. It is imported from /usr/share/pyshared/acct_mgr and actual meta information is in /usr/share/pyshared/TracAccountManager-0.2.1dev.egg-info So far I haven't found a way how to link these. I'll keep you updated. -- anatoly t. On Sat, Jan 2, 2010 at 4:38 PM, W. Martin Borgert wrote: > Quoting "anatoly techtonik" : >> >> Yep. I know that. It is because plugin system in original WebAdmin >> plugin was designed with eggs in mind (whatever that means). I already >> have a patch to fix that, but I want to be sure it covers all cases. > > Would you mind to send the patch to 562...@bugs.debian.org, so > that we can look at it? Even if your solution does not cover all > cases or has other issues, you are at least one step ahead :~) > > The bug report is visible here: http://bugs.debian.org/562963 > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#533176: debhelper: clarify "current directory" in dh_install man
Package: debhelper Version: 5.0.42 Severity: minor It would be nice if dh_install man page included some hints about what is "the current directory" in the following paragraph: "The name of the files (or directories) to install should be given relative to the current directory, while the installation directory is given relative to the package build directory." -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.26.5-flamur5 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages debhelper depends on: ii binutils2.17-3 The GNU assembler, linker and bina ii coreutils 5.97-5.3 The GNU core utilities ii dpkg-dev1.13.26 package building tools for Debian ii file4.17-5etch3 Determines file type using "magic" ii html2text 1.3.2a-3 An advanced HTML to text converter ii perl5.8.8-7etch6 Larry Wall's Practical Extraction ii po-debconf 1.0.8manage translated Debconf template debhelper recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#515048: wipe2fs: does not install from source
Package: wipe2fs Version: 0.2.1-1 Severity: important Justification: fails to build from source $ sudo apt-get -b source wipe2fs Reading package lists... Done ../configure --build i486-linux-gnu --prefix=/usr checking ext2fs/ext2fs.h usability... no checking ext2fs/ext2fs.h presence... no checking for ext2fs/ext2fs.h... no configure: error: ext2fs.h not found make: *** [build] Error 1 Build command 'cd wipe2fs-0.2.1 && dpkg-buildpackage -b -uc' failed. E: Child process failed $ locate ext2fs /usr/include/ext2fs/ext2_fs.h /usr/include/ext2fs/ext2fs.h -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.26.5-flamur5 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
