Bug#1061577: Naming of non-crates.io packages in Debian (was: Re: Processed: retitle 1061577 to rust-io: RUSTSEC-2020-0021…)
On Wed, 28 Feb 2024 23:27:20 +0100 Jonas Smedegaard wrote:
> Quoting Debian Bug Tracking System (2024-01-27 09:42:03)
> > Processing commands for cont...@bugs.debian.org:
> >
> > > retitle 1061577 rust-io: RUSTSEC-2020-0021: CVE-2020-35876:
> > > use-after-free buffer access when a future is leaked
> > Bug #1061577 [src:rust-rio] rust-rio: use-after-free buffer access when a
> > future is leaked
> > Changed Bug title to 'rust-io: RUSTSEC-2020-0021: CVE-2020-35876:
> > use-after-free buffer access when a future is leaked' from 'rust-rio:
> > use-after-free buffer access when a future is leaked'.
> > > thanks
> > Stopping processing here.
>
> The Debian source package src:rust-rio does *not* contain the Rust crate
> rio. That Rust crate originates from Github repository "sacejam/rio",
> whereas the Debian package originates from different Github repository
> "oxigrah/rio" which contains Rust crates rio_api, rio_turtle and
> rio_xml.
>
> Closing as a non-bug.
>
> - Jonas
>
> --
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136 Website: http://dr.jones.dk/
> * Sponsorship: https://ko-fi.com/drjones
>
> [x] quote me freely [ ] ask before reusing [ ] keep private
Jonas: you may want to check your keyboard for the P key ;) It's missing from
both repository name specifiers.
That aside, the package you uploaded as src:rust-rio is actually a combination
of crates.io packages rio_api, rio_turtle, and rio_xml. Despite the upstream
repository being named rio, it ("a low level library which provides conformant
and fast parsers and formatters for RDF related file formats") is very different
from the crates.io package rio, "bindings for io_uring".
As a convention in the Rust ecosystem, a crate name alone refers to crate
published on crates.io with that name. So rio means crates.io/crates/rio, the
io_uring bindings package, not the RDF thing(s). The src:rust-* namespace
currently follows that convention. It's rather confusing that src:rust-rio isn't
the io_uring one, regardless of packaging practices. Please consider using a
more descriptive or namespaced name. It may be a good chance to discuss about
naming of non-crates.io packages in Debian, thus sending to debian-rust.
--
Sdrager,
Blair Noctis
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1061772: RFP: jujutsu -- Git-compatible VCS that is both simple and powerful
On Mon, 29 Jan 2024 10:08:29 -0500 Antoine Beaupre wrote: > Package: wnpp > Severity: wishlist > X-Debbugs-Cc: debian-r...@lists.debian.org > > * Package name: jujutsu > Version : 0.13.0 > Upstream Contact: Martin von Zweigbergk <https://github.com/martinvonz> > * URL : https://martinvonz.github.io/jj/ > * License : Apache-2.0 > Programming Lang: Rust > Description : Git-compatible VCS that is both simple and powerful For packager information, the CLI has changed to be the jj-cli crate; the jujutsu one has a notice saying that. Also it requires the gix stack, which is still a huge pain point. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1028432: debcargo patch to build with clap 4.
On Tue, 14 Nov 2023 16:38:16 -0500 James McCoy wrote: > On Tue, Jan 10, 2023 at 10:32:04PM +, Peter Michael Green wrote: > > Package: rust-debcargo > > > > I've attached a patch which makes debcargo build with clap 4, debcargo > > builds and it's cargo tests run succesfully, but I haven't actually done any > > testing of the command line interface with this patch. > > debcargo was updated to clap 4 via > https://salsa.debian.org/rust-team/debcargo/-/merge_requests/54. This > is part of the 2.6.1 release. > > Debian package still needs to be updated, though. Debian now has 2.6.1 packaged. This might mark this bug donw. However, the version of src:rust-cargo in Debian (0.66) and used by debcargo (0.63, relaxed to 0.66 with patch) hasn't switched, so debcargo still has clip 3 in its build graph. 0.67 made the switch. Fabian pushed packaging of 0.70 to debcargo-conf, but that requires coordination with src:cargo and downstream crates. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1034385: please package new upstream release in experimental
On Thu, 13 Apr 2023 22:08:09 + John Scott wrote: > Source: rust-sequoia-sq > Severity: wishlist > > Hi, > > It would be nice to have a new upstream version with support for fetching > keys via DANE. > > > -- System Information: > Debian Release: 12.0 > APT prefers testing-debug > APT policy: (500, 'testing-debug'), (500, 'testing'), (2, > 'unstable-debug'), (2, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386, arm64 FYI, sequoia-sq 0.31 is now packaged, which has DANE support. It's also migrated to testing. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1007026: rust-weedle - needs nom 5
On Thu, 9 Feb 2023 21:26:59 + Peter Green wrote: > reopen 1007026 > thanks > > > * Revert to nom 4, porting to nom 7 seems to be non-trivial and I do not > > want to further increase the proliferation of nom versions in Debian. > > As I said in the initial mail, I did indeed patch weedle to revert > to nom 4. However in doing so I caused an API break. As such I don't > think this package in it's current state is fit for release. > weedle is depended on, in Debian, only by wasm-bindgen-webidl, which is depended on by nothing, even on crates.io. They could probably be RM'd altogether. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051808: [Pkg-rust-maintainers] Bug#1051808: rust-users: RUSTSEC-2023-0059
On Wed, 13 Sep 2023 04:07:24 +0100 Peter Green wrote: > > rust-users is currently unmaintained upstream. > > > > In a fork a proposed patch can be found. > > > > What is the rust-users situation with respect of Debian as it is > > unmantained upstream? > > So we have two options, patch it or move away from it to a fork > > The crate "uzers" which is a fork of this crate was recently > uploaded to Debian and I have just uploaded version 0.11.3 of > it. I believe that said version includes a fix for this issue. > > Uzers is listed as an alternative on the rustsec entry, but at > least so-far there doesn't seem to have been a whole lot of uptake. > crates.io only lists one reverse dependency of said fork, which > is itself a fork of exa. > Currently packaged downstreams are pam, sniffglue, and please (packaged as pleaser). I've sent pull requests to [pam] & [sniffglue] and opened an issue for [please]. Hopefully we can soon see them migrate. pam: https://github.com/1wilkens/pam/pull/39 sniffglue: https://github.com/kpcyrd/sniffglue/pull/124 -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#969590: sqop: Cannot use certificates for signature verification?
Hi Guillem, > Package: sqop > Version: 0.17.0-2 > Severity: normal > I was trying out sqop, to potentially add native support for it into > dpkg-dev, but when trying to verify a signature, it does not seem work > as expected and I'm at a loss due to the lack of man page (see the > other report :). Since even oldstable (11/bulleye as of 2023-11-27) has 0.22.1 of sqop, and stable (12/bookworm) has 0.27.3, unstable 0.31.0, is this still relevant? (It also ships a man page.) -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#972829: rust-lldb, depends on nonexistent package in buster.
On Sat, 24 Oct 2020 16:12:48 +0100 peter green wrote: > Package: rust-lldb > Version: 1.41.1+dfsg1-1~deb10u1 > Severity: serious > > rust-lldb in buster now depends on python3-lldb-7, however it does not appear > that this package has ever existed in Debian. It should have been python-lldb-7. Now that buster is oldoldstable, is this still relevant? -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#953648: bindgen: segfault on powerpc
Hi Daniel, It this still relevant? > https://gitlab.com/sequoia-pgp/nettle-sys/-/issues/8 The project owner closed it because a later version of rust-nettle-sys no longer had this problem. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#976601: rustc: version in buster fails to build Rust code, aborting with "undefined symbol: llvm.x86.subborrow.64"
Hi Sascha, Since we now have bookworm as stable and rustc 1.63.0 in it, is this bug still relevant? -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052696: sccache: FTBFS in sid
On Tue, 26 Sep 2023 11:40:24 +0200 Gianfranco Costamagna wrote: > (11900+ lines of inlined build log) Hi Gianfranco, It would be great if you had kindly sent the log as a separate attachment or pasted its r-b URL. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1037192: sd: version is lower than in squeeze
On Mon, 23 Oct 2023 17:28:50 +0200 Orión González wrote: > A contributor suggested that 1.0 release should be on hold until some new > features get stabilized > https://github.com/chmln/sd/issues/203#issuecomment-1775390770 > > This might mean that the 1.0 release might take many more months. 1.0 has been released: https://github.com/chmln/sd/releases/tag/v1.0.0 I'm now preparing the update. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1036165: ITP: atuin -- Rich shell history using a SQLite database with optional encrypted sync
On 2023-11-16 16:02, Arturo Borrero Gonzalez wrote: > Hi there, > > thanks for working on this. > > Do you have a repository where you are developing this? > > regards. Hi, I'm afraid the work has stalled. I don't want to upload the half (or rather, 1/10) baked draft. I do still intend to package it but now with a low priority. Feel free to take it if you have the time, or mark it as RFP. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1054312: ITP: btm -- customizable graphical process/system monitor for the terminal
On Sat, 21 Oct 2023 16:42:22 +0200 Jonas Smedegaard wrote: > Package: wnpp > Severity: wishlist > Owner: Jonas Smedegaard > X-Debbugs-Cc: debian-de...@lists.debian.org > > * Package name: btm > Version : 0.9.6 > Upstream Contact: Clement Tsang > * URL : https://clementtsang.github.io/bottom > * License : Expat > Programming Lang: Rust > Description : customizable graphical process/system monitor for the > terminal > > bottom (executable name btm) > is a customizable graphical process/system monitor for the terminal, > inspired by gtop, gotop, and htop. > . > By default, bottom is somewhat like a dashboard - > a bunch of different widgets, all showing different things, > and they all cram together to fit into one terminal. > > This package will be maintained in the collaborative Debian section of > salsa, at https://salsa.debian.org/debian/btm > Hi Jonas, Thanks for packaging it! May I ask why the package is named btm? There's nothing else in Debian that's also called bottom. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052683: ITP: railway -- GUI application for searching train journeys
On Tue, 26 Sep 2023 09:11:01 +0200 Arnaud Ferraris wrote: > Package: wnpp > Severity: wishlist > Owner: Arnaud Ferraris > X-Debbugs-Cc: debian-de...@lists.debian.org, aferra...@debian.org > > * Package name: railway > Version : 2.0.0 > Upstream Contact: Julian Schmidhuber > * URL : https://gitlab.com/schmiddi-on-mobile/railway > * License : GPL > Programming Lang: Rust > Description : GUI application for searching train journeys > > Railway is a graphical application allowing one to look up travel information > for many different railways, all without needing to navigate through different > websites. > > It lets the user search for journeys, view their details (timetable, price, > delays, plaftorm if available) and bookmark them. This application also has an > adaptive user interface for use on mobile devices. > Please consider renaming it to something like gnome-railway (since it's a GNOME application) or diebahn (its old name). "Railway" is too broad for an application that almost exclusively serves the Europe. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1051320: ITP: xh -- Friendly and fast tool for sending HTTP requests
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: xh Version : 0.18.0 Upstream Contact: Mohamed Daahir * URL : https://github.com/ducaale/xh * License : MIT Programming Lang: Rust Description : Friendly and fast tool for sending HTTP requests It reimplements as much as possible of HTTPie's excellent design, with a focus on improved performance. This is a Rust package and fits in the Rust team process. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#800584: RFP: python-peewee - a small, expressive orm
FYI, it's packaged as https://tracker.debian.org/pkg/peewee. -- Sdrager, Blair Noctis OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1043208: Retitle Bug#1043208 ITP rust-gix to rust-gitoxide
retitle 1043208 ITP: rust-gitoxide - Pure Rust implementation of Git thanks gix is part of the gitoxide project, better reflect the fact. gitoxide the program is thus included, but saved for later effort. -- Sdrager, Blair Noctis
Bug#1043208: ITP: rust-gix - Pure Rust implementation of Git
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: rust-gix Version : 0.51.0 Upstream Contact: Sebastian Thiel * URL : https://crates.io/crates/gitoxide * License : Apache-2.0 OR MIT Programming Lang: Rust Description : Pure Rust implementation of Git The gix crate, with its gix-* subcrates (subpackages), provides a pure Rust implementation to various primitives of Git. It's used by programs such as gitoxide (their origin), cargo, starship, etc. This package will be maintained in the Debian Rust Team. Unlike the usual process, due to the vast number of subcrates, the team decided to maintain all of them in its own Git [repository]. This is an umbrella ITP; we won't be filing ITPs for each and every subcrate. repository: https://salsa.debian.org/rust-team/gitoxide -- Sdrager, Blair Noctis
Bug#1037192: sd: version is lower than in squeeze
Actually the maintainer is OK with bumping to 1.0, saving the effort to go epoch: https://github.com/chmln/sd/issues/200 I'll wait for its release. The point release is unfortunately missed, however. -- Sdrager, Blair Noctis
Bug#1037192: sd: version is lower than in squeeze
On 2023-07-08 17:31, Andreas Beckmann wrote: > On Thu, 6 Jul 2023 01:58:50 +0800 Blair Noctis wrote: >> On Wed, 07 Jun 2023 14:12:08 +0200 Andreas Beckmann wrote: >> > Package: sd >> > Version: 0.7.6-1 > >> > squeeze had a sd binary package built from (unrelated) src:sd at >> > version 0.74-1 while bookworm has one built from src:rust-sd at >> > version 0.7.6-1 which is lower, violating the archive property of >> > monotonically increasing version numbers. > >> TIL about that. Do you think I can use epoch here? Or should I change its >> name? > > IMO that is one of the correct uses for an epoch, similar to git which also > reused an old package name (probably predating the git version control). > > Note that the upload needs to be done as 1:0.7.6-2, i.e. with increment of the > Debian revision to avoid clashes in the .deb file name (in some cases the > epoch > is not part of the file name for historic reasons). Thanks, I'll go for that. > >> (Sorry about the late reply, the email didn't reach me.) > > And if you don't Cc the submitter, I don't see your reply ;-) Ha, I'm sending To both the submitter and bug@bugs.d.o so it will _definitely_ be seen ;) -- Sdrager, Blair Noctis
Bug#1040514: rust-markdown: panicks when no arguments provided
On Fri, 7 Jul 2023 06:57:48 +0200 =?utf-8?B?0L3QsNCx?= wrote: > Package: rust-markdown > Version: 0.3.0-1+b5 > Severity: normal > > Dear Maintainer, > > $ rust-markdown > ["rust-markdown"] > thread 'main' panicked at 'index out of bounds: the len is 1 but the index is > 1', src/main.rs:9:27 > note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace > > also no manual so idk why Quote upstream: > Note: this is a new crate that reuses an old name. The old crate (0.3.0 and lower) has a bunch of problems. Make sure to use the new crate, currently in alpha at 1.0.0-alpha.10. When it's out of alpha (i.e. back to normal version numbers), I may try to update it. For now, please consider using something else. If you need a CLI to parse and/or convert Markdown, there's pandoc. If you need a Rust library, there's pulldown-cmark. Just what I know of, feel free to search for better alternatives. -- Sdrager, Blair Noctis
Bug#1037192: sd: version is lower than in squeeze
On Wed, 07 Jun 2023 14:12:08 +0200 Andreas Beckmann wrote: > Package: sd > Version: 0.7.6-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > squeeze had a sd binary package built from (unrelated) src:sd at > version 0.74-1 while bookworm has one built from src:rust-sd at > version 0.7.6-1 which is lower, violating the archive property of > monotonically increasing version numbers. > > The highest version of src:sd ever seen in the archive seems to be > 0.75-1. > > Andreas > > Hi Andreas, TIL about that. Do you think I can use epoch here? Or should I change its name? (Sorry about the late reply, the email didn't reach me.) Control: owner -1 ! -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1040316: python3-minimal fails to install
On Tue, 04 Jul 2023 14:37:49 +0300 Adrian Bunk wrote:
> Package: python3-minimal
> Version: 3.11.4-3
> Severity: grave
>
> https://buildd.debian.org/status/fetch.php?pkg=phoc=amd64=0.29.0%2Bds-1=1688470391=0
>
> ...
> Setting up python3-minimal (3.11.4-3) ...
> Traceback (most recent call last):
> File "/usr/bin/py3compile", line 323, in
> main()
> File "/usr/bin/py3compile", line 294, in main
> compile(files, compile_versions, options.force,
> File "/usr/bin/py3compile", line 203, in compile
> interpreter.magic_number(version),
> ^
> File "/usr/share/python3/debpython/interpreter.py", line 233, in
> magic_number
> result = self._execute('import importlib;
> print(importlib.util.MAGIC_NUMBER)', version)
>
> ^^
> File "/usr/share/python3/debpython/interpreter.py", line 359, in _execute
> raise Exception('{} failed with status code {}'.format(command,
> output['returncode']))
> Exception: ('python3.11', '-c', 'import importlib;
> print(importlib.util.MAGIC_NUMBER)') failed with status code 1
> dpkg: error processing package python3-minimal (--configure):
> installed python3-minimal package post-installation script subprocess
> returned error exit status 1
> ...
>
>
`import importlib` doesn't bring in `importlib.util`, need `import
importlib.util`.
IDK if that's the cause though.
--
Sdrager,
Blair Noctis
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1029456: RFP: veracrypt -- Cross-platform on-the-fly encryption.
Control: noowner -1 Control: retitle -1 RFP: veracrypt -- Cross-platform on-the-fly encryption As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814352, it has a shady licensing model making it DFSG incompatible. IDK why wnpp-check wouldn't show that one, so I'll leave this message here. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1029456: RFP: veracrypt -- Cross-platform on-the-fly encryption.
Control: owner -1 ! Control: retitle -1 ITP: veracrypt -- Cross-platform on-the-fly disk encryption with strong security based on TrueCrypt thanks -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#940960: ITP: linenoise -- Minimal replacement for readline
On 2023-06-18 05:10, Jeremy Sowden wrote: >>> Yes, absolutely. Apologies for taking three weeks to reply. >>> >>> J. >> >> And I took two days ;) This time took literally two weeks, haha. Dragged away by $work. > You've gone a for a less elaborate build process for the shared library > than I did: > > > https://github.com/antirez/linenoise/pull/174/commits/ab860406520ad7fc5e7e8e91fcf60cdc43a786f0 > > but that's probably fine. I do have one observation, however. The > shared library should be liblinenoise.so.0.0.0 and there should be two > sym-links: liblinenoise.so.0, which is needed by the library's > dependencies at run-time, and liblinenoise.so which is needed by its > dependencies at build-time. > > I've attached a patch-series with some suggested changes. > > J. I've applied the patches after reading them. It's great to learn from code. OTOH I saw your salsa repo. Since you've done that much I think it's probably better to let you finish it? -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1039632: RM: rust-aes-soft -- ROM; deprecated upstream
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-aes-s...@packages.debian.org, n...@sail.ng Control: affects -1 + src:rust-aes-soft Deprecated upstream in favor of the aes crate. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1039631: RM: rust-aes-ctr -- ROM; deprecated upstream
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-aes-...@packages.debian.org, n...@sail.ng Control: affects -1 + src:rust-aes-ctr Deprecated upstream in favor of the aes crate. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1039630: RM: rust-secret-service -- ROM; Inactive upstream, deprecated deps
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-secret-serv...@packages.debian.org, n...@sail.ng Control: affects -1 + src:rust-secret-service Also has a few actively developed alternatives. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1039629: RM: rust-block-modes -- ROM; Deprecated upstream
Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: rust-block-mo...@packages.debian.org, n...@sail.ng Control: affects -1 + src:rust-block-modes Deprecated upstream in favor of https://github.com/RustCrypto/block-modes. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#940960: ITP: linenoise -- Minimal replacement for readline
On 2023-06-12 05:55, Jeremy Sowden wrote: > On 2023-05-21, at 18:00:45 +0800, Blair Noctis wrote: >> On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote: >>> It occurs to me that it might make more sense for you to take the lead >>> in packaging linenoise since you have an interest in getting it into >>> Debian. Would you like me to transfer ownership of the ITP bug to you? >>> Happy to lend a hand if you need one. >> >> Hmm, can I ask for a review while I upload to mentors.d.n? Wanna make >> sure I did it right. > > Yes, absolutely. Apologies for taking three weeks to reply. > > J. And I took two days ;) Here it goes: https://mentors.debian.net/package/linenoise/ -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#940960: ITP: linenoise -- Minimal replacement for readline
On 2023-06-12 05:55, Jeremy Sowden wrote: > On 2023-05-21, at 18:00:45 +0800, Blair Noctis wrote: >> On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote: >>> It occurs to me that it might make more sense for you to take the lead >>> in packaging linenoise since you have an interest in getting it into >>> Debian. Would you like me to transfer ownership of the ITP bug to you? >>> Happy to lend a hand if you need one. >> >> Hmm, can I ask for a review while I upload to mentors.d.n? Wanna make >> sure I did it right. > > Yes, absolutely. Apologies for taking three weeks to reply. > > J. And I took two days ;) Here it goes: https://mentors.debian.net/package/linenoise/ -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1037312: linux-image-5.10.0-23-amd64: Kernel BUG at fs/buffer.c:3351 during 'btrfs check --init-csum-tree
Package: src:linux Version: 5.10.179-1 Severity: normal X-Debbugs-Cc: emanvi...@gmail.com Dear Maintainer, During long 'btrfs check --init-csum-tree' (eg, after 20 hours?), kernel reported the following bug, and upon 2nd instance, halted computer. Memory tested for 2 days, with no reports of errors. Badblocks test run for 4 days on HDD being fixed-up. Problem is reproducible. I note that memory utilization by 'btrfs check' seems very high -- over 4GB -- but this is my first time running btrfs check --init-csum-tree. I have filed this against kernel because snippet below says it is a kernel ug, though it may be a btrfs problem, since that was the only foreground application running at the time. 'btrfs --version' returns 'btrfs-progs version 6.2' Jun 10 05:37:36 biostar kernel: [48550.102034] [ cut here ] Jun 10 05:37:36 biostar kernel: [48550.102036] kernel BUG at fs/buffer.c:3351! Jun 10 05:37:36 biostar kernel: [48550.102042] invalid opcode: [#1] SMP PTI Jun 10 05:37:36 biostar kernel: [48550.102885] CPU: 1 PID: 93 Comm: kswapd0 Tainted: G OE 5.10.0-23-amd64 #1 Debian 5.10.179-1 Jun 10 05:37:36 biostar kernel: [48550.103747] Hardware name: MSI MS-7A69/Z270M MORTAR (MS-7A69), BIOS 1.60 06/29/2018 Jun 10 05:37:36 biostar kernel: [48550.104619] RIP: 0010:free_buffer_head+0x46/0x50 Jun 10 05:37:36 biostar kernel: [48550.105495] Code: e8 4f a2 f8 ff b8 01 00 00 00 65 ff 0d 13 04 b1 48 65 0f c1 05 0f 04 b1 48 3d ff 0f 00 00 7e 05 e8 df fe ff ff c3 cc cc cc cc <0f> 0b 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 fd e8 22 57 Jun 10 05:37:36 biostar kernel: [48550.106428] RSP: 0018:afb2002f3aa0 EFLAGS: 00010a87 Jun 10 05:37:36 biostar kernel: [48550.107370] RAX: 9aece53950b0 RBX: 9aece5395410 RCX: 80270015 Jun 10 05:37:36 biostar kernel: [48550.108321] RDX: 7fff9aece53950b0 RSI: 9aece5395068 RDI: 9aece5395068 Jun 10 05:37:36 biostar kernel: [48550.109273] RBP: d81e88841500 R08: 0001 R09: Jun 10 05:37:36 biostar kernel: [48550.110231] R10: 0001 R11: 00039300 R12: 9aeb8e1ff134 Jun 10 05:37:36 biostar kernel: [48550.92] R13: 0001 R14: afb2002f3dc8 R15: afb2002f3bc4 Jun 10 05:37:36 biostar kernel: [48550.112158] FS: () GS:9aece6c4() knlGS: Jun 10 05:37:36 biostar kernel: [48550.113139] CS: 0010 DS: ES: CR0: 80050033 Jun 10 05:37:36 biostar kernel: [48550.114114] CR2: 557a7821c430 CR3: 00010b40a006 CR4: 003706e0 Jun 10 05:37:36 biostar kernel: [48550.115106] DR0: DR1: DR2: Jun 10 05:37:36 biostar kernel: [48550.116116] DR3: DR6: fffe0ff0 DR7: 0400 Jun 10 05:37:36 biostar kernel: [48550.117113] Call Trace: Jun 10 05:37:36 biostar kernel: [48550.118108] try_to_free_buffers+0xa7/0x110 Jun 10 05:37:36 biostar kernel: [48550.119113] shrink_page_list+0xa62/0xd80 Jun 10 05:37:36 biostar kernel: [48550.120096] shrink_inactive_list+0x163/0x3d0 Jun 10 05:37:36 biostar kernel: [48550.121056] shrink_lruvec+0x436/0x6a0 Jun 10 05:37:36 biostar kernel: [48550.122017] shrink_node+0x2ab/0x6f0 Jun 10 05:37:36 biostar kernel: [48550.122979] balance_pgdat+0x2e5/0x610 Jun 10 05:37:36 biostar kernel: [48550.123920] kswapd+0x1f6/0x390 Jun 10 05:37:36 biostar kernel: [48550.124843] ? add_wait_queue_exclusive+0x70/0x70 Jun 10 05:37:36 biostar kernel: [48550.125754] ? balance_pgdat+0x610/0x610 Jun 10 05:37:36 biostar kernel: [48550.126663] kthread+0x118/0x140 Jun 10 05:37:36 biostar kernel: [48550.127571] ? __kthread_bind_mask+0x60/0x60 Jun 10 05:37:36 biostar kernel: [48550.128478] ret_from_fork+0x1f/0x30 Jun 10 05:37:36 biostar kernel: [48550.129381] Modules linked in: ufs qnx4 hfsplus hfs cdrom minix msdos jfs xfs vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nls_ascii nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg nf_log_ipv6 soundwire_intel ip6t_REJECT nf_reject_ipv6 soundwire_generic_allocation snd_soc_core snd_compress intel_rapl_msr soundwire_cadence intel_rapl_common xt_hl snd_hda_codec x86_pkg_temp_thermal ip6_tables intel_powerclamp snd_hda_core snd_hwdep coretemp soundwire_bus kvm_intel snd_pcm ip6t_rt i915 snd_timer kvm joydev irqbypass rapl mei_hdcp snd nf_log_ipv4 nf_log_common drm_kms_helper intel_cstate mei_me soundcore ipt_REJECT cec nf_reject_ipv4 mei intel_uncore intel_pmc_core evdev sg iTCO_wdt ee1004 xt_LOG intel_pmc_bxt intel_wmi_thunderbolt i2c_algo_bit iTCO_vendor_support watchdog pcspkr mxm_wmi efi_pstore xt_comment acpi_pad button xt_multiport nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 Jun 10 05:37:36 biostar kernel: [48550.129426] nf_defrag_ipv4 nft_compat nft_counter nf_tables nfnetlink drivetemp drm fuse configfs efivarfs
Bug#940960: ITP: linenoise -- Minimal replacement for readline
On Wed, 17 May 2023 18:40:26 +0100 Jeremy Sowden wrote: > It occurs to me that it might make more sense for you to take the lead > in packaging linenoise since you have an interest in getting it into > Debian. Would you like me to transfer ownership of the ITP bug to you? > Happy to lend a hand if you need one. > > J. Hmm, can I ask for a review while I upload to mentors.d.n? Wanna make sure I did it right. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1036165: ITP: atuin -- Rich shell history using a SQLite database with optional encrypted sync
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: atuin Version : 14.0.1 Upstream Contact: Ellie Huxtable * URL : https://atuin.sh/ * License : MIT Programming Lang: Rust Description : Rich shell history replacement using SQLite with optional encrypted sync server Atuin replaces your existing shell history with a SQLite database, and records additional context for your commands. Additionally, it provides optional and fully encrypted synchronisation of your history between machines, via an Atuin server (using the same binary). This is a Rust package and fits in the Rust team process. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#940960: ITP: linenoise -- Minimal replacement for readline
On 2023/5/14 03:24, Jeremy Sowden wrote: > I came across linenoise because of a request to support it in nftables. > The request came from someone who wanted to install nftables in a > resource-constrained environment where the existing libreadline support > was too heavyweight. In the case of osquery, would it possible to go > the other way? Do you think that upstream would be open to adding > support for libreadline if we offered patches? > > J. Feasible on the resource level I think, it links to many libraries anyway. But for using readline… they actually switched away from it in 2016: https://github.com/osquery/osquery/pull/2613 Considering their rather radical approach of vendoring everything, I don't have too much hope for that. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#940960: ITP: linenoise -- Minimal replacement for readline
On 2023/5/9 04:20, Jeremy Sowden wrote:
> Thanks for the offer. :) I've cloned the osquery repo and it appears to
> use the C++ Linenoise NG fork:
No problem ;) It uses the -ng fork, but the fork's repo was archived in 2017,
which leads me back to the original. And
> which is what I started packaging. The reason that I stopped work on it
> was that linenoise is intended to be used by adding the sources to the
> code-base of the application that wants the functionality. I created a
> PR to add support for building it as a shared library:
is "solved" by adding a make target that builds a .so ("solved" only in my
opinion, of course). But…
> and there has been no response (mind you, there are a lot of open PR's
> going back years), so I wasn't sure whether it was worth adding to
> Debian.
This is indeed a problem, which I overlooked at first. A second check shows 59
open issues vs 24 closed, and as you said 73 open PRs vs 54 closed, an obvious
sign of abandonment, overlooked largely due to its recent commits.
> I've had a quick look at the linenoise-ng repo and it appears to be
> API-compatible with the original and has a [c]make file, so it may be a
> better candidate for packaging -- particularly now that you have
> provided a use-case for it. I'll take a closer look and see how much of
> my work can be salvaged.
Speaking of API-compatible — I asked in #debian-mentors and someone expressed
strong concern over the lack of versioning of the original, while -ng at least
has a macro that defines its version.
In the compatibility sense I'm now more on the -ng side. Personally I don't like
cmake… but it's fine on this level.
The use case is a big headache, vendoring everything with its various own
compilation tweaks baked in cmake files. linenoise is hardly a problem compared
to that… Still, happy to help ;)
--
Sdrager,
Blair Noctis
OpenPGP_signature
Description: OpenPGP digital signature
Bug#940960: ITP: linenoise -- Minimal replacement for readline
Hi Jeremy, It's been a few years since this ITP was filed. Do you still plan to package it? I'm packaging osquery which depends on this. Happy to help ;) -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#995770: tagging 995770 wontfix
On Tue, 05 Oct 2021 18:26:04 +0200 Yadd wrote: > tags 995770 + wontfix > thanks Hi Yadd, Would you mind giving a little explanation on why? I'm considerably slowed down by this when packaging rustc, a fairly large package, and frustrated by the fact that it's single-threadly doing: read archive, update archive, reconstructing the entirety of the file on disk due to the update, repeat. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1032589: sq-wot: Please update
On Thu, 9 Mar 2023 10:21:22 -0600 Gunnar Wolf wrot
> The online published documentation no longer matches sq-wot's
> functionality.
FYI you can check the docs for 0.2 at
https://docs.rs/sequoia-wot/0.2.0/sequoia_wot/index.html, or any other version,
by clicking `sequoia-wot-{version}` at the upper left corner, and choosing from
lower right corner of the popup.
--
Sdrager,
Blair Noctis
OpenPGP_signature
Description: OpenPGP digital signature
Bug#920386: build_user configuration crashes with "uninitialized value $chroot_arch in scalar chomp"
Hi, I met this problem too when trying to build under the sbuild user, since it's rather strange that sbuild runs as my host user inside the schroot. Is there any update? What should I do if I want to fix this? Thanks. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1032176: ITP: ouch - unified compression and decompression CLI
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: ouch Version : 0.4.1 Upstream Contact: Vinícius R. Miguel * URL : https://crates.io/crates/ouch * License : MIT Programming Lang: Rust Description : Unified compression and decompression CLI ouch is a unified CLI that compresses to and decompresses from various formats, currently tar, zip, gz, xz/lzma, bz(2), lz4, sz, zst. It's easy to use and quite fast. I intend to package and maintain it in the Debian Rust team. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#946187: ITP: starship
On 2023/2/27 22:38, Daniele Tricoli wrote: > Hi Blair, > hi all, sorry for not writing here before. > > On 27/02/2023 15:01, Blair Noctis wrote: >> Hi Daniele, >> >> I'm happy to help packaging starship. Seeing that you haven't updated since >> March last year, is there any problem with it? > > Not with the package itself, it was only a rough year. I was able to upload a > couple of dependencies but than I did not have time to work on it. > Now I'm sabbatical and I'm trying to catch up with various things but your > help > is really appreciated. > Blair, the packaging stuff is already under the umbrella of the Rust Team: > https://salsa.debian.org/rust-team/debcargo-conf/-/tree/master/src/starship > > Are you ok joining the rust team? Thanks for the help. > > Cheers, > That's great news to hear! Welcome back, and wish you a smooth '23. I'm already in and have packaged some stuff. Also in #debian-rust, so we can talk about details more casually (if that's your style). -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#946187: ITP: starship
Hi Daniele, I'm happy to help packaging starship. Seeing that you haven't updated since March last year, is there any problem with it? -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1031072: librust-rspotify-dev is not installable
On Sat, 11 Feb 2023 08:45:32 + Peter Green wrote: > > > > The following packages have unmet dependencies: > > librust-rspotify-dev : Depends: librust-base64-0.12+default-dev > > Depends: librust-itertools-0.9+default-dev > > Depends: librust-rand-0.7+default-dev > > Depends: librust-reqwest-0.9+default-dev but it is > > not installable > > > As far as I can tell, rspotify was packaged as a dependency of spotify-tui. > > The problem is that while there is a new version of rspotify that has > modernised dependencies, spotify-tui was never updated to modernise it's > dependencies and was eventually removed from Debian. > > https://github.com/Rigellute/spotify-tui/issues/915 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018166 > > I don't think there is much value in fixing this package, until/unless > either spotify-tui is updated upstream and someone wants to get it > back into Debian or some other package comes up that needs rspotify > > I intend to package [ncspot], which depends on rspotify. I'll work on it after freeze, please don't RM it. [ncspot]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020522 -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1031039: rust-aes-ctr build depends on librust-aes-soft-0.3+default-dev but it is not installable
On Fri, 10 Feb 2023 19:04:20 +0200 Adrian Bunk wrote: > Source: rust-aes-ctr > Version: 0.3.0-2 > Severity: serious > Tags: ftbfs > > The following packages have unmet dependencies: > builddeps:rust-aes-ctr : Depends: librust-aes-soft-0.3+default-dev but it is > not installable > > [aes-ctr] and aes-soft are both deprecated upstream, we are [planning] to update to aes then RM them. [aes-ctr]: https://crates.io/crates/aes-ctr [aes-soft]: https://crates.io/crates/aes-soft [planning]: https://lists.debian.org/debian-rust/2022/11/msg2.html -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1031051: librust-rustls-dev depends on librust-ring-dev which is missing on mips, ppc*, s390x, riscv, sparc64, c32
Package: librust-rustls-dev Version: 0.20.8-4 Severity: serious X-Debbugs-Cc: n...@sail.ng Dear maintainer, Your package librust-rustls-dev depends on librust-ring-dev that fails to build on mips, ppc, s390x, riscv, sparc64, c32. That renders librust-tokio-utils-dev FTBFS on said archs, in turn librust-reqwest-0.11+rustls-tls-dev, in turn tealdeer. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1030366: rust-tree-magic-mini: Depends/Build-Depends on cruft package librust-petgraph+default-dev
On Fri, 03 Feb 2023 10:42:56 -0500 Scott Kitterman wrote: > Package: rust-tree-magic-mini > Version: 3.0.3-2 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > > Source package rust-petgraph version 0.6.2-1 no longer builds > librust-petgraph+default-dev: > - broken Depends: > rust-tree-magic-mini: librust-tree-magic-mini-dev > - broken Build-Depends: > rust-tree-magic-mini: librust-petgraph+default-dev (0.5-~~ >=) > > Once this is decrufted, the package will FTBFS and be uninstallable. Might be caused by librust-serde-fmt changing from arch:any to arch:all, breaking value-bag, all the way up to petgraph: > report: > - > package: sbuild-build-depends-main-dummy > version: 0.invalid.0 > architecture: amd64 > status: broken > reasons: >- > missing: > pkg: > package: librust-value-bag-dev > version: 1.0.0~alpha.9-3 > architecture: amd64 > unsat-dependency: librust-serde-fmt-1+default-dev:amd64 > depchains: > - >depchain: > - > package: sbuild-build-depends-main-dummy > version: 0.invalid.0 > architecture: amd64 > depends: librust-indexmap-1+default-dev:amd64 (>= 1.7-~~) | > librust-indexmap-1+default-dev:amd64 (>= 1.7-~~) > - > package: librust-indexmap-dev > version: 1.9.2-1 > architecture: amd64 > depends: librust-quickcheck-1-dev:amd64 | > librust-quickcheck-1-dev:amd64 > - > package: librust-quickcheck-dev > version: 1.0.3-2 > architecture: amd64 > depends: librust-rand-0.8+getrandom-dev:amd64 | > librust-rand-0.8+getrandom-dev:amd64 > - > package: librust-rand-dev > version: 0.8.5-1 > architecture: amd64 > depends: librust-log-0.4+default-dev:amd64 (>= 0.4.4-~~) | > librust-log-0.4+default-dev:amd64 (>= 0.4.4-~~) > - > package: librust-log-dev > version: 0.4.17-3 > architecture: amd64 > depends: librust-value-bag-1.0.0+error-dev:amd64 | > librust-value-bag-1.0.0+error-dev:amd64 > -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1025690: rust-clap-3: please upgrade to v4
> $ dev/list-rdeps.sh clap > Versions of rust-clap in unstable: > librust-clap-dev 3.2.23-1 > > Versions of rdeps of rust-clap in unstable, that also exist in testing: > librust-bat-dev 0.22.1-1 depends > on librust-clap-3+default-dev (>= 3.2.20-~~), > librust-bindgen+clap-dev 0.60.1-2 depends > on librust-clap-3+default-dev, > librust-cargo-binutils-dev 0.3.5-2 depends > on librust-clap-2+default-dev (>= 2.33-~~), > librust-cargo-c-dev 0.9.11-1 depends > on librust-clap-3+cargo-dev (>= 3.1-~~), librust-clap-3+color-dev (>= > 3.1-~~), librust-clap-3+default-dev (>= 3.1-~~), librust-clap-3+derive-dev > (>= 3.1-~~), > librust-cargo-dev0.63.1-2 depends > on librust-clap-3+default-dev (>= 3.1.0-~~), > librust-cbindgen+clap-dev0.24.3-2 depends > on librust-clap-3+default-dev (>= 3.1-~~), > librust-clap-complete-dev3.1.1-2 depends > on librust-clap-3+std-dev (>= 3.1.0-~~), > librust-clap-complete-fig-dev3.1.0-1+b1 depends > on librust-clap-3+std-dev (>= 3.1.0-~~), > librust-criterion-dev0.3.6-3 depends > on librust-clap-2-dev (>= 2.33), > librust-debcargo-dev 2.6.0-1 depends > on librust-clap-3+cargo-dev, librust-clap-3+default-dev, > librust-clap-3+derive-dev, > librust-dotenv+clap-dev 0.15.0-2+b4 depends > on librust-clap-2+default-dev, > librust-filespooler-dev 1.2.2-2 depends > on librust-clap-3+derive-dev (>= 3.1-~~), librust-clap-3+std-dev (>= > 3.1-~~), > librust-git-absorb-dev 0.6.7-1 depends > on librust-clap-2+default-dev (>= 2.33-~~), > librust-hexyl-dev0.8.0-2+b3 depends > on librust-clap-2+color-dev, librust-clap-2+default-dev, > librust-clap-2+suggestions-dev, librust-clap-2+wrap-help-dev, > X librust-rav1e-dev0.5.1-5 depends > on librust-clap-2+color-dev, > librust-resource-proof-dev 1.0.39-4 depends > on librust-clap-3+default-dev, librust-clap-3+derive-dev, > librust-sequoia-wot-dev 0.2.0-1+b2 depends > on librust-clap-2+default-dev (>= 2.33-~~), librust-clap-2+wrap-help-dev > (>= 2.33-~~), > librust-structopt+color-dev 0.3.26-2 depends > on librust-clap-2+color-dev (>= 2.33-~~), > librust-structopt+debug-dev 0.3.26-2 depends > on librust-clap-2+debug-dev (>= 2.33-~~), > librust-structopt+default-dev0.3.26-2 depends > on librust-clap-2+default-dev (>= 2.33-~~), > librust-structopt-dev0.3.26-2 depends > on librust-clap-2-dev (>= 2.33-~~), > librust-structopt+doc-dev0.3.26-2 depends > on librust-clap-2+doc-dev (>= 2.33-~~), > librust-structopt+no-cargo-dev 0.3.26-2 depends > on librust-clap-2+no-cargo-dev (>= 2.33-~~), > librust-structopt+suggestions-dev0.3.26-2 depends > on librust-clap-2+suggestions-dev (>= 2.33-~~), > librust-structopt+wrap-help-dev 0.3.26-2 depends > on librust-clap-2+wrap-help-dev (>= 2.33-~~), > librust-structopt+yaml-dev 0.3.26-2 depends > on librust-clap-2+yaml-dev (>= 2.33-~~), > > Source packages in unstable whose autopkgtests are triggered by rust-clap: > rust-addr2line 0.18.0-1 triggered > by librust-clap-dev=3.2.23-1 > rust-bindgen 0.60.1-2 triggered > by librust-clap-dev=3.2.23-1 > rust-clap-complete 3.1.1-2 triggered > by librust-clap-dev=3.2.23-1 > rust-exacl 0.9.0-2 triggered > by librust-clap-dev=3.2.23-1 > rust-hdrhistogram7.5.0-1 triggered > by librust-clap-dev=3.2.23-1 > rust-stderrlog 0.5.3-1 triggered > by librust-clap-dev=3.2.23-1 > rust-zstd0.11.2-1 triggered > by librust-clap-dev=3.2.23-1 We can expect a steady (read: slow) upgrade. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#931002: Removed package(s) from unstable
On Sun, 8 Sep 2019 13:58:06 +0200 (CEST) Santiago Vila wrote:> This was automatically closed by ftpmaster because the package was > removed from unstable, but this still does not fix the FTBFS problem > in stable. It's now only in oldstable, nothing depends on it, and it requires a nightly rustc which we currently don't have. Is it safe to close this? -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1013302: ntopng FTBFS /build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: Can't reference 'this' before calling super in derived class constructors
On Tue, 21 Jun 2022 09:08:56 +0100 Peter Green wrote:> > /build/1st/ntopng-5.2.1+dfsg1/debian/missing-sources/gauge.coffee:179:3: error: Can't reference 'this' before calling super in derived class constructors > > @value = 1 * @elem.innerHTML > > ^ > > make[1]: *** [debian/rules:24: override_dh_auto_build] Error 1 Simply adding two lines of `super()` solves this, but I'm curious if we could get rid of the coffee script. It's there supposedly because there were only minimized JavaScript and we need a way to reproduce them. Now upstream has the "original" JS file present. Original in quotes because it's still generated from a coffee script, but *its upstream* distributes the coffee script together with generated JS. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#969609: rust-zstd: unbuildable, uninstallable, depends on non-existent rust-zstd-safe
Hi, rust-zstd-sys 2.0.1 has been ACCEPTED, rust-zstd-safe 5.0.2 is in NEW. rust-zstd should follow. -- Sdrager, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1021604: ITP: httpstat -- visualize curl statistics
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: httpstat Version : 1.3.2 Upstream Author : Xiao Meng * URL : https://github.com/reorx/httpstat * License : MIT Programming Lang: Python Description : visualize curl statistics This command line tool shows statistics of a curl request, including response headers and time used by each stage of the request, in a simple graph. This tool helps analyze time cost of HTTP and other requests. It's a Python package and fits in the Python team packaging process. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#783086: Project archived
Hi, This packaged is archived on GitHub. Its README recommends oauthlib as an alternative, which is already packaged as python3-oauthlib (python-oauthlib seems to be its deprecated version). -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1014339: please coordinate using ITP bugreports
Hi Jonas, rust-rmp and rust-rmp-serde are now accepted. Please let me know if there is any problem with it. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1020727: rust-web-sys: please provide feature console
On Sun, 25 Sep 2022 22:05:38 +0200 Jonas Smedegaard wrote: > Please provide feature console, needed by packages I am preparing for > Debian. Hi Jonas, As this is marked blocking rust-femme, web-sys is required by femme only when femme has wasm32 feature enabled, which may better be patched off for now. And quoting web-sys d/changelog: > rust-web-sys (0.3.35-1.1) unstable; urgency=medium > > * Non-maintainer upload. > * Reduce the Provides field to the 2 values actually used in the Debian > archive so that we don't break reprepro with a field of more than > 256 Kb and so that we are below the new DAK-enforced limit of 64 Kb. > > -- Raphaël Hertzog Fri, 17 Jan 2020 10:17:12 +0100 -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1018724: rust-jemalloc-sys FTBFS on riscv64(gc)
On Mon, 29 Aug 2022 23:02:02 +0800 Blair Noctis wrote:
> After some tests I found that its bundled, pre-generated configure script may
> be the cause. jemalloc itself successfully builds using its autogen.sh script.
The cause should be upstream config.{guess,sub} not having a riscv64gc entry.
jemalloc itself did build, but recognized as a general riscv64.
--
Regards,
Blair Noctis
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1019481: ITP: rust-kv-log-macro -- kv-log-macro is a log macro for log's kv-unstable backend.
On 2022/9/25 14:42, Jonas Smedegaard wrote: > Quoting Blair Noctis (2022-09-25 07:32:07) >> On Sat, 10 Sep 2022 11:52:48 +0200 Jonas Smedegaard wrote:> >> This >> package is needed by rust-async-std. >>> It will be maintained in the Debian section of Salsa, at >>> https://salsa.debian.org/debian/rust-kv-log-macro >> >> Jonas, would you mind me packaging it in the Rust team? It's successfully >> built >> locally, and would be one less "side" package for you to worry about. > > Thanks for the offer but no need: I already prepared the package, it is > only waiting for bug#1019504 to be fixed (which makes me wonder if your > "successfully built locally" skipped some tests). > > If you want to help, then please instead look into fixing bug#1019504. I happen to have built the whole dependency chain while working on async-std some time ago, so no, I guess I didn't skip tests. I'm still happy to leave it to you. And speaking of that bug, it's being worked on, since its deps sval and value-bag are now in NEW. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1019481: ITP: rust-kv-log-macro -- kv-log-macro is a log macro for log's kv-unstable backend.
On Sat, 10 Sep 2022 11:52:48 +0200 Jonas Smedegaard wrote:> This package is needed by rust-async-std. > It will be maintained in the Debian section of Salsa, at > https://salsa.debian.org/debian/rust-kv-log-macro Jonas, would you mind me packaging it in the Rust team? It's successfully built locally, and would be one less "side" package for you to worry about. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1020522: ITP: ncspot - cross-platform TUI client for Spotify
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: ncspot Version : 0.11.1 Upstream Author : Henrik Friedrichsen * URL : https://github.com/hrkfdn/ncspot/ * License : BSD-2-Clause Programming Lang: Rust Description : cross-platform TUI client for Spotify ncspot is a cross-platform TUI client for Spotify. It has most of the features provided by the official client, yet maintains a small memory footprint. It's a Rust crate and fits in the Rust team packaging process. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1019874: python3-specutils: FTBFS on riscv64, segfault in Fortran library
Package: python3-specutils Version: 1.8.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: n...@sail.ng Dear Maintainer, This package currently fails a test on riscv64 (buildd log [1]): > specutils/io/asdf/tags/tests/test_spectra.py . [ > 1%] > specutils/io/default_loaders/tests/test_apogee.py sss[ > 1%] > specutils/io/default_loaders/tests/test_jwst_reader.py . [ > 5%] > xsss.[ > 6%] > specutils/manipulation/model_replace.py Fatal Python error: Segmentation fault > > Current thread 0x003fa5ed5010 (most recent call first): > File "/usr/lib/python3/dist-packages/scipy/linalg/_basic.py", line 464 in > solve_banded > File "/usr/lib/python3/dist-packages/scipy/interpolate/_cubic.py", line 781 > in __init__ > File > "/<>/.pybuild/cpython3_3.10/build/specutils/manipulation/model_replace.py", > line 171 in _interpolate_spline > File > "/<>/.pybuild/cpython3_3.10/build/specutils/manipulation/model_replace.py", > line 155 in _compute_spline_values > File > "/<>/.pybuild/cpython3_3.10/build/specutils/manipulation/model_replace.py", > line 79 in model_replace > File "", > line 1 in segfault happened when `solve_banded` called into a runtime chosen variant of LAPACK procedure `gtsv`, which in local testing was `dgtsv`. 1: https://buildd.debian.org/status/fetch.php?pkg=specutils=riscv64=1.8.0-1=1661681347=0 -- System Information: Debian Release: bookworm/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: riscv64 -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1019183: librust-uuid+rand-dev: impossible to install package
On Mon, 05 Sep 2022 06:52:57 +0200 Jonas Smedegaard wrote: librust-uuid+rand-dev is impossible to install: Depends on missing package librust-uuid-dev (= 0.8.1-5) Hi Jonas, librust-uuid-dev is now 1.1.2, which has no "rand" feature. You may want to use feature "v4" which is the randomly generated UUID v4, or "fast-rng" that references a "private_rand" feature, using the rand crate rather than getrandom. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#898400: ITP: sccache - compiler cache for fast recompilation of C/C++/Rust code
On 2022/9/1 22:01, Jonas Smedegaard wrote: Quoting Blair Noctis (2022-09-01 14:52:42) I see that you've removed some dependencies of dist-* feature and for Windows, which I didn't realize could be done. However I'm not sure why the redis, memcached, gcs, azure, s3 features are removed. They are removed to get sccache into Debian sooner: When additional dependencies are in Debian we can link against those as well. Progressive approach, a lesson learned. uuid is 0.8.1 in unstable, 1.1 on crates.io. Patching it is fairly easy: Nice that patching is easy. Better would be to upgrade rust-uuid, but until that is done I am ok carrying a patch with sccache. Thanks! My wording was a bit off - it's patching sccache to use uuid 1.1, not to patch uuid itself. I do plan to update uuid to 1.1. zstd is 0.5.1 in unstable, 0.11 on crates.io. I tried 0.11 on it with no errors. But there's #969609 [1], not sure if I should push it. I don't understand what you mean by "push it". What needs doing regarding bug#969609 is (as I see it, but the bug belongs in the Rust team so I contradict anything said in that team then listen to them!) to package rust-zstd-safe - as indicated in the subject of that bugreport. counted-array, local-encoding, pulldown-cmark, skeptic, tokio-serde, tower, tower-layer are packaged locally, with local-encoding patched to use skeptic 0.13 instead of 0.4, removing the dependency on tempdir. I'll push them later on. Again, not sure what you mean by "push them" - perhaps you are talking Rust-team lingo of pushing to the all-crates-in-one-giant-git repo - which I in Debian lingo would call packaging officially for Debian. Oh, the lingo systems ;) I meant pushing the changes to the git repo(s), not necessarily the Rust team's all-in-one repo, and not necessarily packaging the updates. I just didn't find a word good enough to describe "push to a git repo" in the broader context. Btw, do you mind using salsa's issues and merge requests, or prefer emails? I prefer not having to use Salsa - but I am not a hardcore do-it-all-with-mail either: I prefer pushing to git and then share in email an URI to wherever you pushed it - e.g. a git clone or (when you have write access) a temporary branch (I like the naming scheme wip/* for such throwaway branches). Just another way to collaboration, totally understand ;) Speaking of write access: You should now have access to the repo in Salsa: https://salsa.debian.org/debian/sccache Received the notification email, thanks. I'll fisrt try to apply the uuid patch when uuid 1.1 is up in the archive. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#898400: ITP: sccache - compiler cache for fast recompilation of C/C++/Rust code
Hi Jonas,
I see that you've removed some dependencies of dist-* feature and for
Windows, which I didn't realize could be done. However I'm not sure
why the redis, memcached, gcs, azure, s3 features are removed.
zstd is 0.5.1 in unstable, 0.11 on crates.io. I tried 0.11 on it with
no errors. But there's #969609 [1], not sure if I should push it.
uuid is 0.8.1 in unstable, 1.1 on crates.io. Patching it is fairly
easy:
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -268,7 +268,7 @@
optional = true
[dependencies.uuid]
-version = "0.8"
+version = "1.1"
features = ["v4"]
[dependencies.version-compare]
--- a/src/dist/client_auth.rs
+++ b/src/dist/client_auth.rs
@@ -513,7 +513,7 @@
let port = server.local_addr().port();
let redirect_uri = format!("http://localhost:{}/redirect;, port);
- let auth_state_value = Uuid::new_v4().to_simple_ref().to_string();
+ let auth_state_value = Uuid::new_v4().as_simple().to_string();
let (verifier, challenge) =
code_grant_pkce::generate_verifier_and_challenge()?;
code_grant_pkce::finish_url(
client_id,
@@ -567,7 +567,7 @@
let port = server.local_addr().port();
let redirect_uri = format!("http://localhost:{}/redirect;, port);
- let auth_state_value = Uuid::new_v4().to_simple_ref().to_string();
+ let auth_state_value = Uuid::new_v4().as_simple().to_string();
implicit::finish_url(client_id, auth_url, _uri,
_state_value);
info!("Listening on http://localhost:{} with 1 thread.", port);
--- a/tests/harness/mod.rs
+++ b/tests/harness/mod.rs
@@ -633,7 +633,7 @@
"{}_{}_{}",
CONTAINER_NAME_PREFIX,
tag,
- Uuid::new_v4().to_hyphenated_ref()
+ Uuid::new_v4().as_hyphenated()
)
}
counted-array, local-encoding, pulldown-cmark, skeptic, tokio-serde,
tower, tower-layer are packaged locally, with local-encoding patched
to use skeptic 0.13 instead of 0.4, removing the dependency on
tempdir. I'll push them later on.
Btw, do you mind using salsa's issues and merge requests, or prefer
emails?
1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969609
--
Regards,
Blair Noctis
OpenPGP_signature
Description: OpenPGP digital signature
Bug#898400: ITP: sccache - compiler cache for fast recompilation of C/C++/Rust code
Hi Jonas, Sorry for the formatting - it looks different in Thunderbird. Guess I'll start by packaging dependencies "the team's way", and try to get familiar with "the old way". -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#898400: ITP: sccache - compiler cache for fast recompilation of C/C++/Rust code
On 2022/9/1 12:50, Jonas Smedegaard wrote: Dependencies are updated and patched to keep up with crates.io versions. That said, I'm using the debcargo-conf "toolchain" [1]. Does the team have some coordination on this? Do you mean to say that you updated and patched the packaging that I have already prepared, or that you started from scratch and needed to essentially repeat (team-style) some parts of what I'd already done? Those are local changes, just to get sccache itself up. Please note that sccache is *not* maintained in the Rust team, as I disagree with the method used (and mandated) within that team - which seams to be *exactly* the "toolchain" that you are pointing to here. If that doesn't discourage you from collaborating directly with me on getting sccache into Debian, then great: Please have a look at what I've already put together and tell me if any of it is not obvious to you... Of course not ;) I'll try that and see if I can help. If you prefer working same style as the Debian Rust team, then that's great too: Please join that team (if you haven't already) and help package some of the dependencies still missing in Debian, as listed at https://salsa.debian.org/debian/sccache/-/blob/debian/latest/debian/TODO but please then leave packaging of sccache itself to me. I'm fine with either style; the team's way seems a little easier to me, but then again, I'm a newbie still figuring out about packaging. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#898400: ITP: sccache - compiler cache for fast recompilation of C/C++/Rust code
On Sun, 03 Apr 2022 18:31:59 +0200 Jonas Smedegaard wrote: > Control: owner -1 ! > Control: retitle -1 sccache - compiler cache for fast recompilation of C/C++/Rust code > > I am currently looking into packaging sccache for Debian. > Hi Jonas, was trying this too then saw your ITP, happy to help. I've manged to build a binary package, and using it on itself looks good (at least it didn't fail cargo build or cargo test). Dependencies are updated and patched to keep up with crates.io versions. That said, I'm using the debcargo-conf "toolchain" [1]. Does the team have some coordination on this? 1: https://salsa.debian.org/rust-team/debcargo-conf/ -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1018759: ITP: sd - intuitive find and replace CLI
On 2022/8/30 19:00, Andrey Rahmatullin wrote: On Tue, Aug 30, 2022 at 06:44:36PM +0800, Blair Noctis wrote: An RFP is at #1016929 [1]. 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016929 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016929> You should have retitled and owned the RFP instead of creating a separate ITP. You should do that now, as described on https://www.debian.org/devel/wnpp/#l3 , and merge this bug into that one. Done. Thanks for pointing out! -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1018761: ITP: tealdeer - simplified, example based and community-driven man pages
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name : tealdeer Version : 1.5.0 Upstream Author : Danilo Bargen * URL : https://github.com/dbrgn/tealdeer * License : MIT or Apache-2.0 Programming Lang: Rust Description : simplified, example based and community-driven man pages tealdeer is a very fast CLI implementation of tldr, the collaborative cheatsheets of console commands. It's a Rust crate and fits in the Rust team packaging process. -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1018759: ITP: sd - intuitive find and replace CLI
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name : sd Version : 0.7.6 Upstream Author : Gregory * URL : https://github.com/chmln/sd.git * License : MIT Programming Lang: Rust Description : an intuitive find and replace CLI sd uses Python and JavaScript style regex syntax, without the quirks of sed and awk. While sed can do many things, sd focuses on doing one thing and doing it well, has common-sense defualts and a focus on daily use. It's also faster. - Find and replace expressions are separate, unlike sed: sd before after sed s/before/after/g - Modify files in-place: sd before after file.txt sed -i'' 's/before/after/g' file.txt - String-literal mode - Named or unnamed catch groups sd is a modern alternative to the sed command. It's a Rust crate and fits in the Rust team packaging process. An RFP is at #1016929 [1]. 1: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016929 <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016929> -- Regards, Blair Noctis OpenPGP_signature Description: OpenPGP digital signature
Bug#1018724: rust-jemalloc-sys FTBFS on riscv64(gc)
Source: rust-jemalloc-sys Version: 0.3.2-2 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: n...@sail.ng rust-jemalloc-sys is currently FTBFS on riscv64 [1], reporting that riscv64gc is not recognized. After some tests I found that its bundled, pre-generated configure script may be the cause. jemalloc itself successfully builds using its autogen.sh script. I filed an issue for this upstream [2]. 1: https://buildd.debian.org/status/logs.php?pkg=rust-jemalloc-sys 2: https://github.com/tikv/jemallocator/issues/36 -- System Information: Debian Release: bookworm/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: riscv64 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Regards, Blair Noctis OpenPGP_0xC21D9AD423A39727.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#1018166: RM: rust-spotify-tui -- ROM; FTBFS for the last year
Upstream has no commits on master since Nov 2021. The main developer lacked time: https://github.com/Rigellute/spotify-tui/issues/1000 Regards, Blair Noctis
Bug#1018181: ITP: just - Save and run project-specific commands
Package: wnpp Severity: wishlist Owner: Blair Noctis X-Debbugs-Cc: debian-de...@lists.debian.org, n...@sail.ng * Package name: just Version : 1.4.0 Upstream Author : Casey Rodarmor * URL : https://github.com/casey/just * License : CC0-1.0 Programming Lang: Rust Description : Save and run project-specific commands just is a command runner with a configuration file similar to Makefile but can be written in arbitrary languages. It has improvements over make e.g. no .PHONY, is cross-platform, has detailed error output, and comes with command line completions for popular shells. This package provides an alternative to make in daily development, with modern and friendly experience. Also, its author RFP'd it, #971726. The package is a Rust crate, thus fits in the Rust team packaging process. -- Regards, Blair Noctis OpenPGP_0xC21D9AD423A39727.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Bug#773140: unblock: rabbitmq-server/3.3.5-1.1
rabbitmq-server maintainers, are there any other RC bugs that you're planning to file on the package? No other RC bugs. I submitted https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773259, which I hope has an appropriate severity of important. I've asked a couple developers their opinion on whether rabbitmq-server attempting to use SSLv3 [1] would be a bug. Rabbit's method to verify SSLv3 is disabled [2] uses s_client with the -ssl3 option which no longer works [3]. I believe this is a non-issue since SSLv3 is disabled in Jessie [4], but I would appreciate a confirmation. I apologize for the late bugs and 3.4.1-1 debacle, I had some terrible misunderstandings. -Blair 1. https://groups.google.com/forum/#!topic/rabbitmq-users/jk45xOPqeGY 2. https://gist.github.com/michaelklishin/3f47bae850bdd9f1a79a 3. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766297 4. https://lists.debian.org/debian-release/2014/11/msg00690.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773259: XSS and response-splitting bugs in management plugin
Package: rabbitmq-server Version: 3.3.5-1 Severity: important RabbitMQ 3.4.1 fixes a couple of bugs in the management plugin that may have security implications. These can probably be considered less severe than the bug described here: https://groups.google.com/forum/#!topic/rabbitmq-users/DMkypbSvIyM (which was fixed in 3.4.0). From the release notes: 26437 prevent /api/* from returning text/html error messages which could act as an XSS vector (since 2.1.0) 26433 fix response-splitting vulnerability in /api/downloads (since 2.1.0) Bug 26437 allowed an attacker to create a URL to /api/... which would provoke an internal server error, resulting in the server returning an html page with text from the URL embedded and not escaped. This was fixed by ensuring all URLs below /api/ only ever return responses with a content type of application/json, even in the case of an internal server error. Bug 26433 allowed an attacker to specify a URL to /api/definitions which would cause an arbitrary additional header to be returned. This was fixed by stripping out CR/LF from the download query string parameter. Above text from: https://groups.google.com/forum/#!topic/rabbitmq-users/-3Z2FyGtXhs -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#773134: rabbitmq_management incorrectly trusts 'X-Forwarded-For' header
Package: rabbitmq-server Version: 3.3.5-1 Severity: serious RabbitMQ 3.3.0 introduced a mechanism (the 'loopback_users' configuration item) allowing access for some users to be restricted to only connect via localhost. By default the guest user is restricted in this way. Unfortunately, the HTTP framework used by the management plugin trusts the easily-forged 'X-Forwarded-For' header when determining the remote address. It is therefore possible to subvert this access control mechanism for the HTTP API. Attackers would still need to know or guess the username and password. Above text was taken from: https://groups.google.com/forum/#!topic/rabbitmq-users/DMkypbSvIyM -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753475: (no subject)
Hello, Thanks for logging this bug. This bug matches and existing bug in RabbitMQ's internal bugtracker. Best Regards, Blair -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699120: zookeeper: Request upgrade to 3.4.5
Package: zookeeper Version: 3.3.6+dfsg-1ubuntu1 Severity: wishlist Hello, The latest Zookeeper is now 3.4.5 [1] which adds Kerberos authentication of clients [2], multi-updates, an improved REST API and improved operational support [3]. Cloudera considers 3.4.4 the first stable release in the 3.4.x line and as such are including it in their CDH4.2 release [4]. [1] http://zookeeper.apache.org/doc/r3.4.5/ [2] https://issues.apache.org/jira/browse/ZOOKEEPER-938 [3] http://blog.cloudera.com/blog/2011/11/apache-zookeeper-3-4-0-has-been-released/ [4] http://blog.cloudera.com/blog/2012/09/apache-zookeeper-3-4-4-has-been-released/ -- System Information: Debian Release: wheezy/sid APT prefers raring-updates APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 'raring') Architecture: amd64 (x86_64) Kernel: Linux 3.8.0-2-generic (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 zookeeper depends on: ii adduser 3.113+nmu3ubuntu1 ii libzookeeper-java3.3.6+dfsg-1ubuntu1 ii openjdk-7-jre-headless [java6-runtime-headless] 7u9-2.3.4-1ubuntu1 zookeeper recommends no packages. zookeeper suggests no packages. -- Configuration Files: /etc/zookeeper/conf_example/myid changed [not included] /etc/zookeeper/conf_example/zoo.cfg changed [not included] -- 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#675394: mdadm: Each file copy to array grown by MDADM results in copies with different md5sum values
Package: mdadm Version: 3.1.4-1+8efb9d1+squeeze1 Severity: normal Bottom line: since growing my raid array, and switching raid levels using MDADM, I am unable to successfully copy a file to my array. The resulting file always has different md5sum values from the original file, and is corrupted. In addition to this, it appears that all files on my raid array have different md5sums after this procedure. File System: XFS mdadm --detail /dev/md127 /dev/md127: Version : 0.90 Creation Time : Sun Jan 25 22:44:41 2009 Raid Level : raid6 Array Size : 8790815616 (8383.58 GiB 9001.80 GB) Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB) Raid Devices : 8 Total Devices : 8 Preferred Minor : 127 Persistence : Superblock is persistent Update Time : Mon May 7 00:51:55 2012 State : clean Active Devices : 8 Working Devices : 8 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 64K UUID : d861d754:1a1065fe:c230666b:5103eba0 Events : 0.386680 Number Major Minor RaidDevice State 0 8 1290 active sync /dev/sdi1 1 8 331 active sync /dev/sdc1 2 8 492 active sync /dev/sdd1 3 8 1133 active sync /dev/sdh1 4 8 174 active sync /dev/sdb1 5 8 965 active sync /dev/sdg 6 8 806 active sync /dev/sdf 7 8 647 active sync /dev/sde This raid re-arrangement was done the following way: 1) Started with 5 devices in raid 5 array, functioning correctly. 2) Shutdown -h 3) Installed 3 additional hard disks, all same manufacturer and size, however newer firmware. I verified the firmware was compatible via the manufacturers website. 4) Booted up, determined device names 5) successfully Added the drives to the array, by :mdadm /dev/md127 --add /dev/sdg etc. 6) successfully grew the array mdadm --grow /dev/md127 -n 8 -l 6, took a very long time as expected 7) successfully resized the file system xfs_growfs -d /dev/md127 Then, I started noticing problems with files on the array. No need to get into them specifically. Regarding the source of the problems, the md5sums from the files on the raid array no longer matched the original md5sums from files copied to the array prior to the above commands. I figured I would confirm the problem with the following test procedure: 1) mkdir Test_Files/ 2) dd if=/dev/urandom bs=1024 count=500 of=5GB_Rand, dd if=/dev/zero bs=1024 count=500 of=5GB_Zero 3) md5sum test: Original Test Files created on Boot Drive blair@debian:~$ md5sum /home/blair/Test_Files/5GB_Rand 0fed0abb19ea7962830e54108631ddac /home/blair/Test_Files/5GB_Rand blair@debian:~$ md5sum /home/blair/Test_Files/5GB_Zero 20096e4b3b80a3896dec3d7fdf5d1bfc /home/blair/Test_Files/5GB_Zero 4) Copied files to /dev/md127 raid array 5) md5sum test on copied files: blair@debian:~$ md5sum /mnt/movies/Test_Files/5GB_Rand 419175a78977007f3d5e97dcaf414b61 /mnt/movies/Test_Files/5GB_Rand blair@debian:~$ md5sum /mnt/movies/Test_Files/5GB_Zero 5846bed2b52532719d4812172a8078ce /mnt/movies/Test_Files/5GB_Zero 6) Copied files from md/127 array back to Boot Drive 7) md5sum test: blair@debian:~$ md5sum /home/blair/Test_Files/Test_Files_Copy/5GB_Rand 419175a78977007f3d5e97dcaf414b61 /home/blair/Test_Files/Test_Files_Copy/5GB_Rand blair@debian:~$ md5sum /home/blair/Test_Files/Test_Files_Copy/5GB_Zero 5846bed2b52532719d4812172a8078ce /home/blair/Test_Files/Test_Files_Copy/5GB_Zero I am not sure what I have done in the process that would have created this problem. I am filing this bug report to mdadm because I have successfully grown my raid in the past, using mdadm. In that instance it was from 4 devices to 5 devices, both on raid 5 (no level switch), and growing the xfs filesystem accordingly. These file problems started as soon as I executed the recent grow to 8 devices and level 6 as indicated above. In addition, it is worth mentioning that to install the additional drives in my array for it's current configuration, I have installed a SATA host adapter (SYBA SY-PEX40008 PCI Express SATA II). This was needed because my M/b only has 6 sata ports on board. I specifically chose that hardware due to a friend successfully running a similar set up with Raid 6, 8 devices, and that SYBA adapter. -- Package-specific info: --- mdadm.conf DEVICE partitions CREATE owner=root group=disk mode=0660 auto=yes HOMEHOST system MAILADDR root --- /etc/default/mdadm INITRDSTART='all
Bug#664451: apr: [PATCH] apr_file_trunc() bug causes svn repository corruption
Package: apr Severity: important Tags: upstream squeeze wheezy sid Dear Maintainer, All APR released before 1.4.6 have a bug in apr_file_trunc() that can result in files being longer than they should be: http://svn.apache.org/repos/asf/apr/apr/branches/1.4.x/CHANGES This can cause corruption in Subversion fsfs repositories. The next release of svn 1.6.x and the 1.7.3 release works around this issue by flushing the APR file buffer before truncating it: http://svn.apache.org/viewvc?view=revisionrevision=1240892 For Debian versions on 1.4.x, updating to 1.4.6 is probably easiest. For older releases, one could take these two commits from apr's trunk and apply them to the 1.x.y branch. I haven't done this myself, but my hunch says it should work without much effort: http://svn.apache.org/viewvc?view=revisionrevision=1044432 http://svn.apache.org/viewvc?view=revisionrevision=100 Regards, Blair -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric'), (100, 'oneiric-backports') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-16-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#649114: New upstream hdf5 1.8.8 release
Package: hdf5 Version: 1.8.7-2~exp7 Hello, HDF 1.8.8 has been released: http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.8-RELEASE.txt . It would be great if the next HDF5 release in Debian would be 1.8.8 instead of 1.8.7. Thank you, Blair Zajac -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613669: [PATCH] 0.3.4 commits ready for review
I made the changes to Tzafrir's git repository to update the package to 0.3.4. The commits are up at: https://github.com/blair/pkg-rbtools A couple of notes. When I did the commit to update to 0.3.4 I did the following: git clone git://git.debian.org/~tzafrir/rbtools.git pkg-rbtools cd pkg-rbtools rsync -avH ../RBTools-0.3.4/ ./ delete everything from local dir that isn't in RBTools-0.3.4 except for .git/ and debian/ update debian/changelog and debian/watch debuild -S -sa git commit -a The debuild -S -sa deletes stuff that was in the upstream tarball, so I don't know if that's OK or not: $ diff -ru ../RBTools-0.3.4 . Only in .: debian Only in .: .git Only in ../RBTools-0.3.4/RBTools.egg-info: dependency_links.txt Only in ../RBTools-0.3.4/RBTools.egg-info: entry_points.txt Only in ../RBTools-0.3.4/RBTools.egg-info: PKG-INFO Only in ../RBTools-0.3.4/RBTools.egg-info: SOURCES.txt Only in ../RBTools-0.3.4/RBTools.egg-info: top_level.txt Let me know what's the correct thing to do here. Regards, Blair -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613669: Preparing a patch
I'm looking to get python-rbtools 0.3.4 in Ubuntu 12.04 and the advise I've received is to get the update into Debian first and then they'll sync it. I've done a patch for Ubuntu and am working on moving the patch over to Debian's source. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613669: Preparing a patch to update to 0.3.4
Hello, I'm looking to get python-rbtools 0.3.4 in Ubuntu 12.04 and the advice I've received is to get the update into Debian first and then Ubuntu will sync it. I've done a patch for Ubuntu and am working on moving the patch over to Debian's source. Blair -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#589737: Grub2 upadate - multiple partitions on netbook - eeepc, acer aspire, etc
Hi, I'm running debian sid/squeeze on an eeepc 1000 with multiple flash hard-drives. I have a separate partition (sda1) for /boot. My /root (sda2) and /home (sdb1) are also on separate partitions which are encrypted. [see below partition table for reference] The problem started when I recently accepted an update to install grub2 on my machine. After updating the software, I rebooted to the following error: Unknown symbol error in grub2 : 'grub_xputs' I hope this helps anyone else with this problem. I have read somewhere that multiple drives will cause problems with grub2. Here's what I did to remove the update and restore my system to the previous grub-legacy. 1. Get the cd which you used to install your system or the current 'live' cd. 2. Reboot your system and boot from the cd media. 3. At the splash screen prompt move the indicator from 'Install' past 'Advanced' to 'Help' and press [enter]. 4. Enter 'rescue' (without quotes) in command prompt 5. debian installer with blue screen will start. You should see 'Rescue' in the upper left-hand corner of the screen (you will not partition any drives in this mode). You will need to select language, location, and keyboard (English, USA is default). 6. the installer will try to configure the network. You can skip through this step or continue without configuring when prompted to do so. 7. You should be prompted to drop to shell in /root. You should choose the partition which /root is mounted on... If your /root is encrypted like mine, you will also be prompted for the passphrase in order to mount the partition. 8. Once you have been dropped into terminal mode [note the '#' symbol at the left-bottom of screen], mount the partition where your /boot files are located. In my system, this is partition 'sda1'. Therefore type (without quotes)#: 'mount /dev/sdXN' [where 'X' is the LETTER and 'N' is the NUMBER of the boot drive on your system] 9. You will now remove the grub2 update and restore the working grub-legacy so that you can boot into your system. You must note which drive letter [NOT NUMBER] will boot your system (on my system, drive 'sdX' is partitioned into two drives. Drive 'sdX1' is the boot drive but for these purposes, I am interested to install to the MBR (Master Boot Record) of drive 'sdX' [again drive LETTER, not NUMBER -where 'X' represents the drive letter which boots your system] 10. Type the following lines when prompted: sudo aptitude purge grub2 grub-pc sudo aptitude install grub sudo update-grub sudo grub-install /dev/sdX [see #9 above, drive letter, not number] 11. reboot system 12. enjoy your operating system again below is my partition table as an illustrative example: Disk /dev/sda: 8069 MB, 8069677056 bytes 255 heads, 63 sectors/track, 981 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x294a294a Device Boot Start End Blocks Id System /dev/sda1 * 1 16 120832 83 Linux Partition 1 does not end on cylinder boundary. /dev/sda2 16 853 6726656 83 Linux Partition 2 does not end on cylinder boundary. Disk /dev/sdb: 32.3 GB, 32279224320 bytes 255 heads, 63 sectors/track, 3924 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00014367 Device Boot Start End Blocks Id System /dev/sdb1 1392531520768 83 Linux -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549920: chown/ls -ld fails on mac os
Have a look at the attached diff --- On Fri, 10/9/09, Clint Adams sch...@debian.org wrote: From: Clint Adams sch...@debian.org Subject: Re: Bug#549920: chown/ls -ld fails on mac os To: john blair mailtome200420032...@yahoo.com, 549...@bugs.debian.org Date: Friday, October 9, 2009, 9:34 AM On Tue, Oct 06, 2009 at 12:11:50PM -0700, john blair wrote: *STAT64_SUPPORT was not not set Can you tell me which conditions indicate stat64 support on MacOS/Darwin? *fakeroot didn't intercept versioned symbols, such as fts_read$INODE64 I know nothing about symbol versioning with dyld or whatever is being used, so I don't know if this is possible. *Also, fakeroot didn't intercept fts_children (or rather fts_children$INODE64), which is what ls -ald calls. This is theoretically the easy one. fakeroot.diff Description: Binary data
Bug#549920: chown/ls -ld fails on mac os
Package: fakeroot Version: 1.13 Severity: important I built fakeroot-1.13 and fakeroot-1.12.5 for mac os 10.4. On both of them I tried to run the following script with fakeroot #!/bin/bash mkdir -p /tmp/newdir /usr/sbin/chown -R root:wheel /tmp/newdir ls -ld /tmp/newdir with the following result drwxr-xr-x 2 john wheel 68 Oct 5 22:29 /tmp/newdir Instead of root owning newdir, its owned by me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549920: chown/ls -ld fails on mac os
Btw I am trying this on 10.5 and it doesn't work drwxr-xr-x 2 john wheel 68 Oct 6 11:59 /tmp/newdir drwxr-xr-x 2 john wheel 68 Oct 6 11:59 /tmp/newdir drwxr-xr-x 2 john wheel 68 Oct 6 11:59 /tmp/newdir drwxr-xr-x 2 john wheel 68 Oct 6 11:59 /tmp/newdir According to one of my colleague: ls -ld does a lstat64() syscall, and the syscall is not intercepted by fakeroot. There is a wrapper for lstat64, but it is not enabled (because STAT64_SUPPORT is not set). If we set STAT64_SUPPORT then it gets intercepted properly. But the call from ls does not get intercepted. The ls executable is implemented on top of the fts_*(3) API, in particular fts_read$INODE64, which is implemented by the C library internally by doing a lstat64() call. In summary: *STAT64_SUPPORT was not not set *fakeroot didn't intercept versioned symbols, such as fts_read$INODE64 *Also, fakeroot didn't intercept fts_children (or rather fts_children$INODE64), which is what ls -ald calls. --- On Tue, 10/6/09, Clint Adams sch...@debian.org wrote: From: Clint Adams sch...@debian.org Subject: Re: Bug#549920: chown/ls -ld fails on mac os To: john blair mailtome200420032...@yahoo.com, 549...@bugs.debian.org Date: Tuesday, October 6, 2009, 9:40 PM On Tue, Oct 06, 2009 at 03:31:53AM -0700, john blair wrote: I built fakeroot-1.13 and fakeroot-1.12.5 for mac os 10.4. On both of them I tried to run the following script with fakeroot #!/bin/bash mkdir -p /tmp/newdir /usr/sbin/chown -R root:wheel /tmp/newdir ls -ld /tmp/newdir with the following result drwxr-xr-x 2 john wheel 68 Oct 5 22:29 /tmp/newdir Instead of root owning newdir, its owned by me. Could you try this and see if it gives any clues? #!/bin/bash mkdir -p /tmp/newdir /usr/sbin/chown -R daemon /tmp/newdir ls -ld /tmp/newdir /usr/sbin/chgrp -R wheel /tmp/newdir ls -ld /tmp/newdir /usr/sbin/chown root /tmp/newdir ls -ld /tmp/newdir /usr/sbin/chown daemon:wheel /tmp/newdir ls -ld /tmp/newdir -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#491034: cdinst problem (root bridge?)
From: Frans Pop [EMAIL PROTECTED] Subject: Re: Bug#491034: cdinst problem (root bridge?) To: [EMAIL PROTECTED] Cc: Charles Blair [EMAIL PROTECTED] On Wednesday 16 July 2008, Charles Blair wrote: Can you also try: install noapic install noapic nolapic install acpi=noirq install noacpi Please also try a Lenny beta2 installation image [1] which uses a different kernel version, even if only to see if the problem is specific to the 2.6.18 kernel that Etch uses. Use of the lennybeta2 cdinst made my previous problem go away. I got a message at the very beginning suggesting I use the amd64 version rather than the i386 version (my machine is an HP small forms desktop). I ignored this message and stayed with the i386 out of laziness. So far, things seem to be working. Thank you very much for your help. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491034: cdinst problem (root bridge?)
Package: installation-reports Boot method: CD Image version: debian-40r3-i386-netinst.iso Date: 7-12-2008, approx noon Central time Machine: New HP desktop Processor: celeron Memory: Partitions: did not get to partitioning stage of install Output of lspci -nn and lspci -vnn: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [E] Detect network card:[ ] Configure network: [ ] Detect CD: [O] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: I downloaded the netinst file and burned it to a CD using the windows-supplied cdburn. When I booted from the CD, I got the usual display and pressed ENTER for default installation. After a screen or so of display, the machine stopped, with the last few lines: ACPI: Interpreter enabled ACPI: using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (.00) ACPI: assume root bridge [\_SP_.PCI0] bus is 0 The machine would not respond to control-alt-del, control-C, or ESC. I could only turn it off by unplugging it! I tried to follow a suggestion from the debian-user mailing list, typing install pci=noacpi instead of just pressing ENTER. The machine ground to a halt again, with the last few lines: ACPI: bus type pci registered ACPI: Interpreter enabled ACPI: using PIC ... PnP: PNP ACPI: found 17 devices PnPBIOS: Disabled by ACPI PNP PCI: Probing PCI hardware ACPI: Assume root bridge [\_SB_.PCI0] bus is 0. Thanks for your help! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#249765: Crisp and hot items for everyone
Flash and dash them with your bling I bought a pair of these and my wife could not even spot any difference. http://www.pogerinu.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#46825: Don't Let Yourself Down
Hot chicks dig bigger, larger, mega pricks http://www.spentraks.com/ How to make your woman come -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#82493: Please don't forget this
Every girl loves a man who measures up in bed heres how. http://www.Justonemoren.com/ 9 inches perfect -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#279001: Lindsay loves stripping for the camera
Raise temperatures in the bedroom with your massive hot rod. http://www.Almostfurti.com/ Be large even when flaccid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#144238: The secret to a perfect climax
Every male has the inner potential to be 9 inches long unleash that potential today. http://www.ittninq.com/ Pink and perfect lips -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#213237: Sichere Arbeitspl#228;tze
Wir sind ein dynamisches Unternehmen. Zur Verst#228;rkung unseres Teams suchen wir einen Regionalmanager. Voraussetzungen: Wohnort: die USA, Deutschland flexibel, zuverl#228;ssig, verantwortungsvoll gute PC Kenntnisse (Email, Microsoft World) und Internetanschlu#223; minimal 3 Stunden pro Tag frei Wir versprechen Ihnen einen angenehmen und sicheren Arbeitsplatz bieten Ihnen ein leistungsorientiertes Gehalt und ausgezeichnete Karrierechancen #252;berlassen es Ihnen selbst ,wie Sie Ihre Arbeitszeit organisieren Das Wesentliche bei der Arbeit: 1. Geld von einem unserer Kunden bekommen 2. das Geld #252;ber Western Union transferieren lassen Ihr Verdienst betr#228;gt 2400$ pro Monat. Von jeder Geldsumme, die man #252;berwiesen hat, kriegt man 2 % zus#228;tzlich. Die Probezeit dauert 2 Wochen. In dieser Zeit kriegen Sie kein festes Gehalt, sondern nur 2 % von jeder #220;berweisung. Haben Sie Interesse an dieser Position, dann senden Sie Ihre Bewerbung an: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#316848: automata augite automatic
Pickup Prescriptoins and eMdications immediately http://anselmanchorage.abreact%2Epotorswe.com some automataaugite -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#178139: bantus aching bamako
Buy Perscriptions and Medictaions right now! www.www.aldermenbandage.basic%2ekusanra.com but bantusaching -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296642: Give yourself the edge over the other guys
Give yourself the edge over the other guys http://www.starleyt.com/?phknwbxsld Don't be left behind! Millions of men are already benefiting from using pheromons to attract women, without them you are at a disadvantage! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
