Re: RFA libtorrent and rtorrent
2006/9/23, Arnaud Fontaine <[EMAIL PROTECTED]>: > "Goswin" == Goswin von Brederlow <[EMAIL PROTECTED]> writes: Goswin> How about comaintainership? Could you two (or three looking Goswin> further in the thread) work well together? Hey, Why not? I'm interested by co-maintainership. I think that's great! Please contact me in private so we could arrenge something together ;) Bye, Arnaud Fontaine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- ~ghostbar @ debian etch 2.6.15 http://ghostbar.no-ip.biz/ Linux Counter# 382503 San Cristobal, Tachira - Venezuela. 0110011101101110 011100110111010001100010011101110010 Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Intel Atom Processor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Steffen Moeller wrote:
> Kushal Koolwal wrote:
>>> I got your point, you mean we(group of debian) should make a blueprint for
>>> some Device like Netbook / UMPC /> MIDs.
>> Yes. Exactly!
>>
>>> what is your blueprint based debian like?
>> At this point of time I am not sure what is going to look like. May be it
>> will help me if you can tell me what exactly do you mean by it. I apologize
>> for my unfamiliarity with some of the terms.
>>
>>> maybe we can start a project named mobian (mobile debian) ?
>> Yes this would be awesome. This will bring Debian up to the speed of likes
>> of Ubuntu. I would be happy to assist in this with whatever knowledge and
>> skills I have.
>>
>> Thanks for effort and initiative.
>
> The EeePCs are sold throughout large resellers (Saturn, Staples, ...) in
> Germany and at least until the new ones get out they all ship with
> Debian - perfectly visible to every potential customer passing by. I have not
> seen Debian or Linux on any product before in these shops. So, I
> really think that for the perception of Debian (and Linux at large) it would
> be good if there was some initiative that gives Debian on these
> machines some backup.
>
> To have a connected user base itself would already be a plus. Some flyer to
> print out would be good that points to this community site so we can
> put such next to these machines in the shop. And Asus would probably help to
> get this across to their customers, too. People would then learn
> how to submit bug reports and get some indication of what software to
> install. Even the software that is distributed with the EeePC and that
> is on display in the store is not fully usable, for instance try to change
> the your coordinates in Celestia, the dialog of which is beyond the
> screen size. Would an alioth project and pages on wiki.d.o be sufficient?
>
> Best,
>
> Steffen
>
>
You mean like these ones:
http://alioth.debian.org/projects/debian-eeepc
http://wiki.debian.org/DebianEeePC
I don't think that works as you said since this group exists since 2007...
Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkiIrIUACgkQOKCtW8rKsRi+tQCguUZb8Ax+8mNAcX6z/wDxL2Qx
cuAAoNpoVyDSZPNkestk6lGg/SXKJC0Z
=LMvz
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Testing debconf scripts
Hi, I was trying to test my own debconf scripts but I couldn't even test debconf-scripts from mysql that they do work. Anyone can help me out with this? I try running directly the postinst but nothing shows. Anyone had worked with this? Regards. -- Jose Luis Rivas - GPG (old/new): 0xCACAB118 / 0x7C4DF50D San Cristóbal, Venezuela - http://ghostbar.ath.cx/ Debian Project Developer - http://debian.org/ signature.asc Description: OpenPGP digital signature
Re: How to avoid stealth installation of systemd?
On 01/07/14, 05:35pm, Juliusz Chroboczek wrote: > >> gentle persuasion [...] is more in line with point 4 of the Debian > >> Social Contract than [...] bullying? > > > May I suggest that you treat others the way you want to be treated? > > I am not a Debian Developer. I am not bound by the Social Contract. FYI, you are bound to https://www.debian.org/code_of_conduct. The reason why that document exists is because the Social Contract has barely something about behaviour. > > Are we to expect a higher standard of behaviour from a Debian Developer > than from a random user who is pissed off because his system has just been > broken? Or is being a Debian Developer power without responsibility, as > some of your esteemed colleagues appear to believe? Either Debian Developer or a regular user who's pissed of or happy, we expect the same higher standard. CoC applies to everyone. > > > The suggestion to just add conflicts is also not quite helpful. > > I'm not sure I'm following. There was no reason whatsoever to install > systemd on my system, yet it got installed and broke the ACPI scripts. To > my untrained eyes, it looks like a conflict is missing somewhere. Knowing what exactly installed systemd in your system should be helpful. It's not like systemd got installed by itself without being a dependency of another package. Kind regards. -- Jose Luis Rivas | ghostbar The Debian Project → <http://www.debian.org> GPG D278 F9C1 5E54 61AA 3C1E 2FCD 13EC 43EE B9AC 8C43 signature.asc Description: Digital signature
Re: Reintroducing FFmpeg to Debian
On 28/07/14, 01:20am, Andreas Cadhalpun wrote: > Hi all, > > some of you may have noticed a weird ffmpeg package in the NEW queue[1]. > Let me explain: > > In 2011 Libav[2] was forked from FFmpeg[3]. It was a time of great > uncertainty, the fork happened with much drama that didn't help making a > technical cut, and at that peculiar time Debian switched to Libav. Hi Andreas and everyone, FWIW, my experience with this is that I had to make my own FFmpeg package a while ago [0] because I needed it for a project I was working on at the moment [1]. [0] https://github.com/ghostbar/FFmpeg.deb [1] https://github.com/ghostbar/RTSP-Streaming.js The reason for having to package my own FFmpeg is the current libav which is taking the space of ffmpeg seemed to conflict with every other ffmpeg package out there, including marillat's and for my project I actually needed ffmpeg, not libav since it didn't had the functionality. (More specifically: the ability to take still images from an rtsp stream). Not having FFmpeg available in the debian repositories is a nuissance, and certainly having libav instead which seems to be a fork yet not having the full FFmpeg functionality and using the same package name is worst. I didn't figured this out at first because the binary said `ffmpeg`. Of course, I'm talking about [2] since now that seems to not be an issue yet remains the lack of functionality. [2] https://packages.debian.org/wheezy/ffmpeg If the issue is that this would mean having to fix security bugs twice then it would be reasonable to stop shipping libav and instead ship ffmpeg, since has more functionality and AFAICS from their repos bunch of active bug-fixing. I honestly do not understand why ffmpeg is not in the repos nor why there seems to be an active movement to block it. Kind regards. -- Jose Luis Rivas · ghostbar <http://ghostbar.co> The Debian Project · <http://www.debian.org> GPG · D278 F9C1 5E54 61AA 3C1E 2FCD 13EC 43EE B9AC 8C43 signature.asc Description: Digital signature
Re: dgit and git-dpm
On 29/10/14, 07:44pm, Thorsten Glaser wrote: > Ian Jackson dixit: > > [ NMU ] > >A dgit user should be able to do this without reading the debdiff: > > This is a dangerous habit to get into – I’d prefer users of even > dgit, no matter how good it may be, to not rely on that. This is > a social issue, not a technical one. > Please explain yourself, is not obvious what social issue you're referring to if dgit is replicating debdiff and dpkg-buildpackage behavior. -- ⨳ GPG 0x13EC43EE B9AC8C43 ⨳ https://ghostbar.co signature.asc Description: Digital signature
[VAC] now -> ?
Hey people, I'm moving from Barquisimeto to Caracas - Venezuela, tomorrow. Don't know when I will have internet in my new home and as is Caracas I'll mostly not be at home but for sleep-time. I need to setup all my things, my kid and all that stuff so probably will be unresponsive for a few months while I adapt. All my packages are co-maintained/group-maintained, so this email is just intended to anyone trying to contact me so I can do something for them within Debian. I'll be available anyway for key-signing within Caracas if anyone is passing by. Cheers! -- Jose Luis Rivas - GPG: 0x7C4DF50D / 0xCACAB118 The Debian Project Developer Venezuela signature.asc Description: OpenPGP digital signature
Keeping feature requests and other non-real bugs in Debian's BTS?
Hi, I would like to keep as clean as possible the BTS of my packages. With `rtorrent` particularly I have found lots of feature-requests bugs which were already sent to upstream but haven't been fixed and are there taking dust. Should we keep them? Cant I just close them since are no Debian-specific? What about keeping just debian-specific bugs in Debian's BTS? What's the policy here? Kind Regards. -- Jose Luis Rivas The Debian Project -- http://debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5222803d.9070...@debian.org
Re: Non-source Javascript files in upstream source
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El 26/04/14, 06:20pm, Peter Samuelson escribió: > > [Manuel A. Fernandez Montecelo] > > If you agree that "source-is-missing" also applies in those cases, do > > you also think that we should immediately declare all source packages > > in Debian containing a 'configure' script as somehow non free (unless > > we can check unambigously that they were generated by the .ac) > > There's 2 reasons to care if configure was built from the configure.ac > in the tarball. The immediately practical reason is to ensure that if > we or our users need to patch it, we can patch the actual source, and > still be able to build correctly. (These things do tend to bitrot if > you don't watch them.) Basically that means always rebuilding from > source - which is already a best practice in Debian. Not every package > does it, but IMO every package _should_. > > The other reason to care is of course to comply with our free software > guidelines. For that purpose, I think it's entirely reasonable to > assume good faith in upstream. If we find out that some upstream > intentionally tricks us by shipping a mismatching configure, just so > they can point and laugh at the DFSG violation, the solution is very > simple: remove the package from Debian, because such upstreams clearly > can't be trusted not to trick us in more malicious ways. > I think is unfair to compare `configure` files with minified JavaScript, starting by the fact that you can't read the minified JavaScript and distinguish if is doing something wrong compared with the source of the same un-minified JavaScript. I think is fine to ship these minified JS files as long as you have a reproducible way to show that is the same as the source. Maybe a dh script should be born for this and my head says the prototype may look like `dh_js_minify_reproduc --source source.js --output min.js - --rules-should-apply='--with-license --with-copyright' and throw an error if it's a mismatch. Kind regards. > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/20140426232014.gd4...@p12n.org > - -- Jose Luis Rivas -- GPG: 0xB9AC8C43 http://www.joseluisrivas.net/ -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNcQeUACgkQOKCtW8rKsRhndwCfWOT9rNfsvyf9A+wNRH3G1xJr 03IAoL8NazLacbwzqYqjIqQxLlKu2EIR =z0qp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140426233149.gc12...@arya.ghostbar.co
Re: Non-source Javascript files in upstream source
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 El 26/04/14, 06:20pm, Peter Samuelson escribió: > > [Manuel A. Fernandez Montecelo] > > If you agree that "source-is-missing" also applies in those cases, do > > you also think that we should immediately declare all source packages > > in Debian containing a 'configure' script as somehow non free (unless > > we can check unambigously that they were generated by the .ac) > > There's 2 reasons to care if configure was built from the configure.ac > in the tarball. The immediately practical reason is to ensure that if > we or our users need to patch it, we can patch the actual source, and > still be able to build correctly. (These things do tend to bitrot if > you don't watch them.) Basically that means always rebuilding from > source - which is already a best practice in Debian. Not every package > does it, but IMO every package _should_. > > The other reason to care is of course to comply with our free software > guidelines. For that purpose, I think it's entirely reasonable to > assume good faith in upstream. If we find out that some upstream > intentionally tricks us by shipping a mismatching configure, just so > they can point and laugh at the DFSG violation, the solution is very > simple: remove the package from Debian, because such upstreams clearly > can't be trusted not to trick us in more malicious ways. > I think is unfair to compare `configure` files with minified JavaScript, starting by the fact that you can't read the minified JavaScript and distinguish if is doing something wrong compared with the source of the same un-minified JavaScript. I think is fine to ship these minified JS files as long as you have a reproducible way to show that is the same as the source. Maybe a dh script should be born for this and my head says the prototype may look like `dh_js_minify_reproduc --source source.js --output min.js - --rules-should-apply='--with-license --with-copyright' and throw an error if it's a mismatch. Kind regards. > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/20140426232014.gd4...@p12n.org > - -- Jose Luis Rivas -- GPG: 0xB9AC8C43 http://www.joseluisrivas.net/ - -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140426233149.gc12...@arya.ghostbar.co -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlNcVbEACgkQOKCtW8rKsRjmGQCfVPeh/hut08w4cnyIzmsNYi9W LcoAoIc6H549oQNmsXcMvYXZNAlIauXZ =Y5kV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140427005617.ga27...@arya.ghostbar.co
Re: Non-source Javascript files in upstream source
On 27/04/14, 06:18pm, Nicolas wrote: > > > > Jo Nicolas, > > > > You could generate the minified javascript from normal javascript files. > > > > > I know that but non minified files don't work. It gives errors "Uncaught > SyntaxError: Unexpected token ILLEGAL" Then the issue is with the source files. That's not right. If you want you can mail me privately and I will help you patching them. Maybe the actual upstream source has it right. Kind regards. -- Jose Luis Rivas -- GPG: 0xB9AC8C43 http://www.joseluisrivas.net/ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140427102043.ga...@arya.ghostbar.co
Re: Ghostscript licensing changed to AGPL
Hi Jonas, On 06/05/14, 11:05am, Jonas Smedegaard wrote: > Ghostscript have changed its license from GPL-3+ to AGPL-3+ since > version 9.07. > > Ghostscript includes a library - libgs9 - licensed as AGPL-3+ like the > rest of the project. It also includes a set of Type1 fonts apparently¹ > licensed the same. > > I've tried² suggest relicensing of the library part, mentioning the the > problems AGPL has for libraries and fonts, and referring to our recent > thread here. Seems they have no interest in such change - or perhaps I > simply failed in getting the message across - perhaps others here can > help explain them the problems better than me. I saw it and I fail to see what exactly they want to achieve with this change since AGPLv3 is for web apps. I see you exposed your position very well but they didn't gave specifics on what they want to avoid with this besides "protect against commercial use of GPL Ghostscript" which I believe is bad enough in DFSG terms. > > Seems that these projects may link against Ghostscript, and therefore > (possibly) effectively becomes AGPL-3+ with this change: > > * gimp > * texlive-bin (texlive-binaries) Actually with this one is worst, since the LPPL is not compatible with the GPL, lets not even talk about GPLv3 or AGPLv3 :-/ [snip] > > AGPL Ghostscript is now in experimental. How to proceed? I think we should get some feedback from debian-legal before doing anything. We need to be aware of their intention, how they plan to proceed on their "protection against commercial use" of Ghostscript and what are the implications for the currently linked applications. Kind Regards. -- Jose Luis Rivas | ghostbar The Debian Project → <http://www.debian.org> GPG 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140507014416.ga2...@arya.ghostbar.co
Re: Bug #702005: Where can i get more attention on this?
On 08/05/14, 01:05pm, Ian Jackson wrote:
> Ian Jackson writes ("Re: Bug #702005: Where can i get more attention on
> this?"):
> > [some stuff to Luis Alejandro Martínez Faneyth ]
>
> Unfortunately, Luis's mail domain is hosted at Hotmail which hates
> chiark:
>
> l...@huntingbears.com.ve
> SMTP error from remote mail server after MAIL
> FROM: SIZE=4130:
> host 3fd47c7f131f4ca31143ff3af72008.pamx1.hotmail.com [65.54.188.78]:
> 550 SC-002 (BAY0-PAMC1-F10) Unfortunately, messages from 212.13.197.229
> weren't sent. Please contact your Internet service provider since part of
> their network is on our block list. You can also refer your provider to
> http://mail.live.com/mail/troubleshooting.aspx#errors.
>
> (I know of the causes of this; I disagree with Hotmail and resolving
> things is nontrivial.)
>
> So hopefully Luis will see my reply here on -devel or in the bug.
>
> Luis, if you want to email me, please use a different email address
> that doesn't go to Hotmail.
>
I already pointed Luis's to your email on the list's archive on IRC and
on Twitter. I'll point it out in IM in a few hours anyway so I make sure
he does see it.
Thanks Ian.
--
Jose Luis Rivas | ghostbar
The Debian Project → <http://www.debian.org>
GPG 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140508125003.ga1...@arya.ghostbar.co
Re: howto handle jquery embedding by build-depends
On 08/05/14, 08:01am, Daniel Baumann wrote: > src:lxc contains documentation (*.sgml only) and build-depends on > docbook2x, no jquery is needed or installed as build-depends. the > resulting bin:lxc-dev then contains a *compressed* jquery.js put there > by docbook2x. lintian detects this and warns about it (W: > embedded-javascript-library). > > i think we have the following possibilities to handle such embedding of > files by build-depends, where the embedded files were not part of the > original source (starting with least favourable one): > > A: ignore it and overwrite the lintian warning > > B: overwrite the lintian warning, use a built-using: relation in > control (in lxc case, against docbook2x which imports the > jquery.js) > > C: post-process the binary package content at buildtime to replace > the embedded files through proper depends (e.g. for jquery, > replace the file with a symlink to /usr/share/javascript/jquery > /jquery.js and have a depends or recommends on libjs-jquery). > > this could potentially have side effects if the copy of the > to-be-embedded file (jquery.js) inside the tool that imports it > (docbook2x) is not in sync with the standalone packaged version > (libjs-jquery), so that we end up with a newer/incompatible > version. > > for lxc, i'd go with C. > > did i miss anything? (yes, i haven't fully read the last thread about > jquery on debian-devel a couple of weeks ago, i think it only covered > the 'what to do with embedded js in source packages'-cases, not this > 'what to do with embedded js in binary packages not being part of the > source package'-case). I actually think there's a D option and is based on the solution that Daniel Kahn Gillmor gave on a similar issue I had with powertop, which is using native javascript instead of jquery. [0] Of course, this wouldn't be on lxc but directly on docbook2x and that would fix it for more packages than only lxc. [0] https://bugs.debian.org/695890 Other people in this thread has already pointed out the issues with several versions of jQuery and I honestly believe native javascript should be enough for the transformations docbook2x seems to be using. BTW, I failed to see on docbook2x website how is that javascript is used at all. Would you give me a hint so I don't need to build the package myself to check if this is actually a viable solution in this case as well? Kind regards. -- Jose Luis Rivas | ghostbar The Debian Project → <http://www.debian.org> GPG 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140508130217.gb1...@arya.ghostbar.co
Re: Misc Developer News (#35)
On 27/05/14, 05:41pm, Bastian Venthur wrote: > On 27.05.2014 11:47, Paul Wise wrote: > > [...] > > > Common mistakes with OpenPGP keys in Debian > > --- > > > > Jo Shields reported[6] on common mistakes that Debian members and > > contributors are making with their OpenPGP keys. His advice is to > > add UIDs for all used mail addresses, get all your UIDs signed, > > make sure you have an encryption subkey, use exact naming in your > > UIDs, make sure your webmail plugin works and avoid Enigmail. > > [...] > > "avoid Enigmail" sounds a bit odd, given that Thunderbird/Icedove is a > very commonly used client and Enigmail -- as far as I know -- the de > facto standard extension for PGP for Thunderbird. > > Could you elaborate a bit on the problems of using Enigmail? In the > quoted blog post I read something about Thunderbird inserting spurious > line breaks into signed mails. That might have something to do with > the "format=flowed"-issue in the mail headers. But as far as I know > this option is disabled by default in Icedove. > I've seen the issue with people sending me emails using Thunderbird in Windows, never from another OS, has the ^M at the end, and from the comments it seems with Windows was the last time he used Thunderbird + Enigmail. -- Jose Luis Rivas -- http://joseluisrivas.net | http://ghostbar.co GPG: 4096R/D278 F9C1 5E54 61AA 3C1E 2FCD 13EC 43EE B9AC 8C43 -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140527070812.ga2...@arya.ghostbar.co
Bug#632162: O: mybashburn -- Burn data and create songs with interactive dialog box
X-Debbugs-CC: debian-devel@lists.debian.org package: wnpp severity: normal This package has been in very bad shape since long time ago, upstream is not responding since 2008 and there have been no changes since that time. Maybe this should be removed, but there could be someone who would like to take over upstream and/or debian maintenance. Regards. -- Jose Luis Rivas. San Cristóbal, Venezuela. Debian Project Developer GPG 0xCACAB118 (old) 0x7C4DF50D (new) http://ghostbar.ath.cx/about -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/banlktinkoj4yo3chtg0_7pmadgg++b6...@mail.gmail.com
Re: Improving your archive and package system for small package
On 03/09/15, 03:13pm, Bastien ROUCARIES wrote: > I was thinking generally, perl latex python have a lot of small > package. Each language could not come with its own solution. Maybe > creating a tool agregating small debian package in a big one. But > doing something only for javascript is not a solution. > > Bastien The use of small packages in nodejs is different to that on perl, latex and python. They are very used and they are way too much. There are several solutions for the same problem and everyone uses a different one. I use nodejs everyday in my work and opensource projects and I refuse to package them into debian precisely by this reason. -- ⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co signature.asc Description: Digital signature
Re: Script to generate common license texts
I have used neosnippet for it https://github.com/ghostbar/vim-snippets/blob/master/snippets/_/licenses.snip -- ⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co
Re: finally end single-person maintainership
On Tue Apr 9, 2024 at 1:52 PM -03, Wookey wrote: > On 2024-04-08 21:44 +0900, Simon Richter wrote: > > > Testing a package requires me to > > commit everything into git first, so I have to remember to squash all these > > commits later. > > Right - this was (one of the) main thing(s) that annoyed me enough to > just go back to the non-git based workflow. I want to make changes and > try them. I don't want to have to commit every damn time - it's not > done yet - I'll commit it after I'm satisfied that it works. But I > don't know that until I've made a whole set of changes and it builds. Use gbp-buildpackage --git-ignore-new. By default checks for uncommited, so you don't ship to Debian things that are not commited. If you use this flag, the burden of checking this lands on you. Yet, you can still use the regular workflow to build stuff, just dpkg-buildpackage -us -uc. > So now I've got a pile of changes which should really be separate > commits and logically separate things often affect the same files, and > even the same lines, so really I need to commit some chunks and not > others and tidy it all up. Yes this makes a nice set of commits but > it's _so_ much work in comparison to just editing the damn files, and > then effectively doing one fat 'commit' when I dupload. Often > something ends up stalled for weeks or months or years because I've > got some chunks in the wrong places and sorting it out is painful, so > I go do something else and lose all my state. You all know how that > goes... Use git commit -p, I tend to throw -v as well, so when I am writing the commit description I also get the diff of that commit. With -p you basically select by blocks what goes into your commit with simple y and n. You can also split blocks. If you prefer to just make a bunch of small commits and then combine them all into one big-fat commit, just use git rebase -i HEAD~N with N being how many commits you want to rebase. This will give you a file text where you decide which commits are squashed onto the top one, you can also re-arrange. After you save that file, it'll allow you to modify the commit. So you can do a bunch of git commit -m 'random' and with git rebase -i create a proper commit message from a bunch of commits. > I realise this (like my previous message) will result in a load of > people telling me git _is_ better and I'm just doing it wrong, or > should learn better tools. And they may even be right, (and I will > probably learn some things from this thread), but I don't believe the > goal we agree on (fixing other people's packages should be culturally > accepted) _requires_ this change in tooling (which is a heavy cost for > at least some of us). Git is the default tooling in the whole open-source ecosystem. Maybe a poll would be good to know how much people actually is against using Git as default, after so many years with proper git tooling in Debian. I would not be surprised if the loud bunch in the mailing lists end-up being very very small. I understand is hard to have your workflows changed, but IMO it's been too many years that Git is the default VCS everywhere. There's no other workflow you need to change, if you use Git. > The point here is that 'requiring salsa' is actually code for 'no, > you can't just use the tarball-based VCS any more - you have to use > git'. Removing that interface is a very big deal - it has served > quite well for 30 years. Yes it old-fashioned and crufty and > (presumably) only a minority still use it as the primary interface, > but any GR on this should acknowledge what we are requiring of people > still using it, not just frame this as 'and add salsa'. It's more > fundamental than that (or I am misunderstanding).. This is untrue. All the git tooling depends on non-git tooling for the build. I actually have a setup for building everything on docker and does not use any git tooling, because that's just sugar-coating for the non-git tools. > Also what do you git people do to replace uscan? Currently I go to my > existing version, or a newly-acquired apt get or dget source. I do > 'uscan' and if there is a new upstream version I have a nice separate > directly that is easy to dirdiff (then fixup any packaging and > dupload). If there isn't I can move on. You can use uscan. > git world seems to make this way more complicated. I have to set up > two different repos - one for salsa one for upstream, then pull them, > maybe into different branches, and fight the diff config to let me > dirdiff two different commits. And the upstream pull will always pull > changes, not just only do it is there is an actual release (tag). > > None of that feels like an improvement over 'uscan'. One word for the > standard process of updating to a new version. And if the patches > still apply it's probably all done (I always do a meld review too to > see what changed). I see, you are confusing two things here. Having the source from Git vs using tarballs. And using Salsa
Re: Debian and our frenemies of containers and userland repos
On 10/4/19 10:49, Enrico Weigelt, metux IT consult wrote: > On 24.07.19 08:17, Marc Haber wrote: > >> Do we have a build technology that uses containers instead of chroots >> yet? > > Something like docker-buildpackage ? > For this purpose I built deb-build-pkg which is a pretty straight-forward way to build debian packages, it's a simple bash script that only requires bash and docker in your system in order to build the packages. https://github.com/resnullius/deb-build-pkg/blob/master/deb-build-pkg -- __.https://wiki.debian.org/JoseLuisRivas ___'/___ rsa4096/D278F9C15E5461AA3C1E2FCD13EC43EEB9AC8C43
Re: Debian and our frenemies of containers and userland repos
On 10/5/19 12:25, Bernd Zeimetz wrote: > > > On 10/5/19 3:31 AM, Paul Wise wrote: >> On Fri, Oct 4, 2019 at 10:49 PM Enrico Weigelt wrote: >>> On 24.07.19 08:17, Marc Haber wrote: >>> Do we have a build technology that uses containers instead of chroots yet? >>> >>> Something like docker-buildpackage ? >> >> AFAICT, docker-buildpackage doesn't exist but whalebuilder does. > > https://github.com/metux/docker-buildpackage > > > Having something that works with git-buildpackage would be really nice, > though. Even better if it would allow to use the k8s API to build things... > deb-build-pkg build -o ../ https://github.com/resnullius/deb-build-pkg It's a simple bash script. Maybe I should write better docs than the help already available with `deb-build-pkg --help`. It's not using k8s API but I don't see a reason why it would not be compatible. Building a Deployment yaml on-the-fly and you're ready. Just calling something different than the `run_docker()` function. With deb-build-pkg you don't even need to be in a Debian system to build stuff. -- __.https://wiki.debian.org/JoseLuisRivas ___'/___ rsa4096/D278F9C15E5461AA3C1E2FCD13EC43EEB9AC8C43
Re: Init systems and docker
Hello Scott, On 10/11/19 18:49, Scott Kitterman wrote: > I have had bugs filed against more than one package I maintain regarding > issues > with sysv init scripts when used in docker. > > I have been told by docker users (I'm not one) that systemd as provided on > Debian can't be used in docker. I have no idea if that's true or not. I try > really hard to know as little about init systems as possible and trust our > maintainers who work on such things. > > If it is true, then to the extent we want Debian to be useful for docker does > that mean we ought to maintain sysv init scripts? If it's not true, can > someone point me to documentation that explains using systemd on Debian in > docker? > > Thanks. > > I'm sure I'll fail, but I'm really not trying to start another email list > flamefest. I'd just like to understand this a little better so I can > properly > maintain my packages. > > Scott K > > Here's a little bit of history on trying to make systemd work into containers and the reason why it was tried (IMO, a silly one): https://lwn.net/Articles/676831/ In short: they should not be using systemd inside the container and if they want to the issue is not on how Debian ships systemd but that they are not using the --privilege parameter for launching their container. The extended version: There's not much sense in using systemd inside a docker container, to be honest. Generally you want to launch your service as custom as possible and the ENTRYPOINT allows you to do just that. Docker already sends the SIGKILL to the PID 1, which should be the service you're shipping in that container. Ideally (and this is one the best practices I've seen people using) containers should be built following something like the UNIX paradigm, so: they ship one service and only one which then communicates with others via some network protocol. People trying to use systemd inside a container is probably trying to ship several services in just one image which is essentially an anti-pattern on containerization. On the other hand, not all people is using a container to launch a service installed via the package manager, so very few would benefit from having systemd doing the init of the service they installed. In my opinion, there's no requirement at all to maintain sysv scripts, at least not under the assumption that they are required by docker containers because they are not. Actually, no init script at all is required by docker containers. -- __.https://wiki.debian.org/JoseLuisRivas ___'/___ rsa4096/D278F9C15E5461AA3C1E2FCD13EC43EEB9AC8C43
Re: Init systems and docker
Forgot to add that docker has a recommended way of running multiple processes per container and it actually avoids init systems launching its own micro init: https://docs.docker.com/config/containers/multi-service_container/ On 10/11/19 19:25, Jose-Luis Rivas wrote > Here's a little bit of history on trying to make systemd work into > containers and the reason why it was tried (IMO, a silly one): > https://lwn.net/Articles/676831/ > > In short: they should not be using systemd inside the container and if > they want to the issue is not on how Debian ships systemd but that they > are not using the --privilege parameter for launching their container. > > The extended version: > > There's not much sense in using systemd inside a docker container, to be > honest. Generally you want to launch your service as custom as possible > and the ENTRYPOINT allows you to do just that. Docker already sends the > SIGKILL to the PID 1, which should be the service you're shipping in > that container. > > Ideally (and this is one the best practices I've seen people using) > containers should be built following something like the UNIX paradigm, > so: they ship one service and only one which then communicates with > others via some network protocol. People trying to use systemd inside a > container is probably trying to ship several services in just one image > which is essentially an anti-pattern on containerization. > > On the other hand, not all people is using a container to launch a > service installed via the package manager, so very few would benefit > from having systemd doing the init of the service they installed. > > In my opinion, there's no requirement at all to maintain sysv scripts, > at least not under the assumption that they are required by docker > containers because they are not. Actually, no init script at all is > required by docker containers. > -- __.https://wiki.debian.org/JoseLuisRivas ___'/___ rsa4096/D278F9C15E5461AA3C1E2FCD13EC43EEB9AC8C43
Re: Init systems and docker
Hello Tomas!
On 10/12/19 13:00, Tomas Pospisek wrote:
> I have to say that I disagree with you and many others on this thread.
> Maybe Docker was *meant* for single application containers, I do not know.
>
> However running a service ("a single application") often implies
> surrounding services. F.ex. you want logs to be saved? Maybe you need to
> run cron or at? Maybe you want to get notified about problems, stats,
> whatever via email?
In all the professional instances of containerization I have seen, these
are provided by external containers/services, so you don't have to
maintain several configuration in several places. Logs go to stdout and
from there you collect them into whatever service you have for this,
process them and use that processing to send notifications or make them
searchable.
>
> Now you can start re-implementing all the existing "surrounding" service
> solutions on the outside of the container. Which is a *lot* of complex
> work in my experience. The quick fix to those "surrounding" problems is
> often enough to stand onto proven-to-work shoulders and to install the
> "surrounding services" *inside* the container:
>
> apt-get install cron at rsyslogd etc. etc.
>
> Now the next problem is how to start those. Easiest way is to hook the
> provided Debian init scripts into whatever mini-init system one chooses.
> And so forth.
>
> So I imagine people that want to run stuff in containers are usually
> very glad if init scripts are available, work and can be re-used.
>
> John Goerzen is maintaining Debian docker images (thanks!) that contain
> a useful set of the mentioned "surrounding" services, that are quite
> popular AFAIK.
>
> Being you, I'd ask for patches. I think running stuff in
> Docker/Kubernetes is a good solution for a lot of problems. I think
> Debian should grow to accommodate those architectures. And I think
> Debian *will* accommodate them (see John's work and a lot of other nice
> efforts in that direction not least by Ubuntu), it just takes time to
> find the sweet spot solutions, to spread the knowledge and knowhow etc.
> A lot of container loads are Debian based, not the least a lot of
> Kubernetes' own people's
Debian already does for a part of container users. You don't need
patches, support is already there. The ones complaining right now
haven't read the right part in Docker's manual to get it running.
Cheers.
--
__.https://wiki.debian.org/JoseLuisRivas
___'/___ rsa4096/D278F9C15E5461AA3C1E2FCD13EC43EEB9AC8C43
Re: Init systems and docker
On 10/14/19 05:49, Marc Haber wrote: > > So, +1 to be able to run a default systemd-based Debian with systemd > as pid 1 in a docker container. Hi Marc, you can do this already. As explained somewhere else in the thread, just run docker run with the --privilege flag. Cheers. -- __.https://wiki.debian.org/JoseLuisRivas ___'/___ rsa4096/D278F9C15E5461AA3C1E2FCD13EC43EEB9AC8C43
Re: Bug#815675: ITP: ftpbackup -- Script to backups your data from a Debian system to a ftp space
On 23/02/16, 08:37am, Nikolaus Rath wrote: > > I'm actually rather shocked that a Debian Developer would consider > letting this into the archive. Carl, I hope you just filed the ITP > before having looked at the program? > He wrote it. L6: # Copyright © 2013-2016 Carl Chenet -- ⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co
Re: hdparm needs a new maintainer
On 01/03/16, 05:02pm, Ivan Gimenez wrote: > Hi > > For me it is ok, I am just a newbie in packaging. > > I have received help from a debian mentor Anibal Montalve Salazar < > ani...@debian.org>, but I got no references for gbp > (yet another Debian packaging toolchain ? ) Yes: https://wiki.debian.org/PackagingWithGit > > what is exactly a collab-maint repository, a Git repo for the package host > somewhere ? Yes: https://wiki.debian.org/Alioth/CollabMaintImport?highlight=%28CategoryAlioth%29 and https://wiki.debian.org/Alioth/Git?highlight=%28CategoryAlioth%29 -- ⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co signature.asc Description: PGP signature
Re: Next steps for gitlab.debian (Re: GitLab B.V. to host free-software GitLab for Debian project)
On 08/06/16, 10:41pm, Ben Hutchings wrote: > On Wed, 2016-06-08 at 19:40 +0200, Alexander Wirt wrote: > > On Wed, 08 Jun 2016, Jonathan Dowland wrote: > > > > > On Wed, Jun 08, 2016 at 09:47:56AM +0200, Alexander Wirt wrote: > > > > I am also not very keen on using a system with a "open core / > > > > enterprise" > > > > model. For such a crucial service I would really prefer a real open > > > > source > > > > system. But maybe I am alone with that oppinion. > > > > > > You are not alone, but please do not call Gitlab CE not "real open > > > source". > > I do for every software which forces me to sign things like: > > https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/legal/individual_contributor_license_agreement.md > [...] > > I don't see what's so unreasonable about that. They're asking you to > provide the same licence for your contributions, as the licence for the > existing Gitlab software. Every FOSS project expects that, even if > they don't make such a formal statement of it. > > Ben. Nodejs requires that as well. Nothing wrong with it. And in that case, calling node.js not real open source, would be quite a mistake. -- ⨳ PGP 0x13EC43EEB9AC8C43 ⨳ https://ghostbar.co
Re: Private code: to forge, or not to forge?
On Wed Oct 16, 2024 at 1:18 PM -03, Iustin Pop wrote: > Hi all, this is offtopic (sorry!), but since we kept discussing Salsa - > I wonder, what are people doing for private code? ... > > What do people think? And thanks for reading. Hi Iustin, I use soft-serve and abuse Git hooks for CI/CD, since it's in a small VPS. IMO, bash is more efficient than YAML. I love its TUI. https://github.com/charmbracelet/soft-serve
Re: RFA libtorrent and rtorrent
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Qingning Huo escribió: > Hi, > > Because of recent changes in my Real Life, I cannot spend enough time on > libtorrent and rtorrent as I would like. Whoever want to adopt are > welcome to take over their maintenance. I would recommend them be > adopted together, because they are closely related (same author), and > new upstream versions are always released at the same time. > > Regards, > > Qingning > Hi Qingning, I want to take both packages. Please write me in private wherever I need to know exactly about something weird on this packages. Cheers, - -- ~ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve San Cristobal - Venezuela. TALUG -- http://linuxtachira.org CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFEbEfOKCtW8rKsRgRAg4JAJ9iwXVZRzsdR/qQDOQfqy84FnHy7gCgn6a5 ydNuJQbWI/UvLfPcHi2i/+I= =yvYH -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFA libtorrent and rtorrent
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Arnaud Fontaine escribió: >> "Qingning" == Qingning Huo <[EMAIL PROTECTED]> writes: > > Qingning> Because of recent changes in my Real Life, I cannot spend > Qingning> enough time on libtorrent and rtorrent as I would like. > Qingning> Whoever want to adopt are welcome to take over their > Qingning> maintenance. I would recommend them be adopted together, > Qingning> because they are closely related (same author), and new > Qingning> upstream versions are always released at the same time. > > Hey, > > I'm interesting by taking care of this package. Is it still possible ? > Will you fill a RFA ? > > Regards, > Arnaud Fontaine > > Hi Arnaud, I already take both, thanks anyway. - -- ~ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve San Cristobal - Venezuela. TALUG -- http://linuxtachira.org CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFE1jkOKCtW8rKsRgRArnKAKDbK5obZmBIGQrZwkkDFNWkBpsjmQCfSZMX 5EWUSDo0QzFh+85FrDAPRUk= =6EkA -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug is very vague, should I close it?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >Package: rtorrent >Version: 0.4.1-1a0.mrvn.1 >Severity: wishlist > >Hi, > >I would like to see some features like DHT in rtorrent to make it more >competitive with other clients. For an overview see > >http://en.wikipedia.org/wiki/Comparison_of_BitTorrent_software > >MfG > Goswin This bug probably will never be solved until rtorrent get all features of all torrent clients... So, should I close this bug? There's a lot of bugs requesting specific features[1] so I don't think this bug it's necessary. Please CC answers to [EMAIL PROTECTED] [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=rtorrent&archive=no&pend-exc=pending-fixed&pend-exc=fixed&pend-exc=done&sev-inc=minor&sev-inc=wishlist#_0_6_3 - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhZX3OKCtW8rKsRgRAuFuAKCoVlUqjyyTgD9BSmz/nUODxVDRVQCgyirN 029JDSq7b3bgUHnB073Dn2E= =wp9R -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#403506: ITP: fdisk -- linux fdisk replacement based on libparted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron Johnson escribió: > On 12/17/06 09:43, Julien Louis wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Julien Louis <[EMAIL PROTECTED]> > >> * Package name: fdisk >> Version : 0.9.1 >> Upstream Author : Leslie P. Polzer <[EMAIL PROTECTED]> >> * URL : http://www.gnu.org/software/fdisk/ >> * License : GPL >> Programming Lang: C >> Description : linux fdisk replacement based on libparted > > Since util-linux already has /sbin/fdisk, naming a package fdisk > seems ambiguous. Should be named something like `fdisk-gnu` or `fdiskgnu`, the binary too for avoid problems with the `fdisk` binary that already exists. Cheers!! - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhbdzOKCtW8rKsRgRAjlOAKDOtfOBx5aTjMmLffHANMwUjMa50wCfSgQf 9lI9jYhW178b5+JxZcaht6M= =wfgt -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm maintaining libtorrent package, this source builds 2 binaries, libtorrent-rakshasa (is libtorrent9 last version in debian archive) and libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive), I get this warning from lintian when I build the package. Now running lintian... W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10 Finished running lintian. The version I'm building is libtorrent-0.11.0 so I don't think I should call the binary libtorrent10. What should I do? Thanks and Cheers!! - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhb+VOKCtW8rKsRgRAm69AKCWHPwAP31Vj3yGDcS/xTILRwa4ngCeMPSH eSc1P96vM8AavyzfsvQxY8Y= =rZbg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug is very vague, should I close it?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ben Finney escribió: > Jose Luis Rivas Contreras <[EMAIL PROTECTED]> writes: [...] >> >> So, should I close this bug? There's a lot of bugs requesting >> specific features[1] so I don't think this bug it's necessary. > > You could enlist the bug submitter's help. Ask them to retitle the bug > and be more specific about a particular feature, or to close it and > submit separate wishlist bugs for each feature they want. > So I will close the bug since all the features are already requested in another wishlist bugs. Thanks!! - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhq8EOKCtW8rKsRgRAjlgAKCuqnyeHA1b44sGJKxPem8ogQFqmwCdEIK9 7JaeIq6lvHejrmNO9JB9RaU= =RENe -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: > On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> I'm maintaining libtorrent package, this source builds 2 binaries, >> libtorrent-rakshasa (is libtorrent9 last version in debian archive) and >> libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive), >> I get this warning from lintian when I build the package. >> >> Now running lintian... >> W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10 >> Finished running lintian. >> >> The version I'm building is libtorrent-0.11.0 so I don't think I should >> call the binary libtorrent10. > > Please check the real soname with objdump -p libtorrent-0.11.0 |grep > SONAME The real soname is libtorrent.so.10 So, should I name it libtorrent10? - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhrBZOKCtW8rKsRgRAneOAJ94txj+uSnxu4NWWF+nB3+ZzHT4ZQCfQnM4 8WYy9Hb8+jyzwpbjzIo09qw= =zZr/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: > On Mon, Dec 18, 2006 at 11:14:33AM -0400, Jose Luis Rivas Contreras wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >>> On Sun, Dec 17, 2006 at 06:07:18PM -0400, Jose Luis Rivas Contreras wrote: >>>> -BEGIN PGP SIGNED MESSAGE- >>>> Hash: SHA1 >>>> >>>> I'm maintaining libtorrent package, this source builds 2 binaries, >>>> libtorrent-rakshasa (is libtorrent9 last version in debian archive) and >>>> libtorrent-rakshasa-dev (is libtorrent9 last version in debian archive), >>>> I get this warning from lintian when I build the package. >>>> >>>> Now running lintian... >>>> W: libtorrent-rakshasa: package-name-doesnt-match-sonames libtorrent10 >>>> Finished running lintian. >>>> >>>> The version I'm building is libtorrent-0.11.0 so I don't think I should >>>> call the binary libtorrent10. >>> Please check the real soname with objdump -p libtorrent-0.11.0 |grep >>> SONAME >> The real soname is libtorrent.so.10 >> >> So, should I name it libtorrent10? > > Either the soname should be libtorrent.so.11, or you might > want to rename libtorrent-0.11.0 to libtorrent-0.10.0 or something. I can't that version already pass... > > If the soname really is and should be libtorrent.so.10, you want to name > it libtorrent-rakshasa10 or something. But it should have the 10 in it. Ok, so I'm renaming the package to libtorrent10-rakshasa and -dev. > >>From what I understand there are 2 incompatible libtorrent packages, so > you want to reflect that in the name of the package. > Yes, there's libtorrent-rasterbar (in a RFP, but I want to avoid problems in a near future), my packages were libtorrent9 and libtorrent9-dev, so I add to the name of the libraries "-rakshasa" to reflect that in the name. Thanks and Cheers!! - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhr0pOKCtW8rKsRgRAr5zAJ4qLKHfOrr9fe3C2lcJpU4F62KkTgCg0eMF UGHUzA0TBliBAp4kbZTrj+0= =ZJAe -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: > On Mon, Dec 18, 2006 at 12:09:13PM -0400, Jose Luis Rivas Contreras wrote: >>>>>> The version I'm building is libtorrent-0.11.0 so I don't think I should >>>>>> call the binary libtorrent10. >>>>> Please check the real soname with objdump -p libtorrent-0.11.0 |grep >>>>> SONAME >>>> The real soname is libtorrent.so.10 >>>> >>>> So, should I name it libtorrent10? >>> Either the soname should be libtorrent.so.11, or you might >>> want to rename libtorrent-0.11.0 to libtorrent-0.10.0 or something. >> I can't that version already pass... > > If the soname is set to libtorrent.so.10, it means applications will > start to look for a file called "/usr/lib/libtorrent.so.10". That will > probably be a symlink in your case to libtorrent-0.11.0, which looks > rather confusing to me. > > In libtorrent9 you have a file called "/usr/lib/libtorrent.so.9". But > there doesn't seem to be a file named libtorrent-0.9.0.so or something, > so I'm a little confused what changed. No, there's only libtorrent.so.10 libtorrent.so.10.0.0 in my build (libtorrent-0.11.0) I'm more confused since I renamed the package to libtorrent10-rakshasa and libtorrent-rakshasa10 and lintian keeps giving me the warning... Jose - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFhsdYOKCtW8rKsRgRAg2iAKCqVE6x7lYUQoSKGvBsUrA4q4kdwgCfVRZ/ SRiDJbmdP0TU7pDbvE1Tbkc= =oOay -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kurt Roeckx escribió: > On Mon, Dec 18, 2006 at 12:52:40PM -0400, Jose Luis Rivas Contreras wrote: >>> If the soname is set to libtorrent.so.10, it means applications will >>> start to look for a file called "/usr/lib/libtorrent.so.10". That will >>> probably be a symlink in your case to libtorrent-0.11.0, which looks >>> rather confusing to me. >>> >>> In libtorrent9 you have a file called "/usr/lib/libtorrent.so.9". But >>> there doesn't seem to be a file named libtorrent-0.9.0.so or something, >>> so I'm a little confused what changed. >> No, there's only libtorrent.so.10 libtorrent.so.10.0.0 in my build >> (libtorrent-0.11.0) > > So, your source package is "libtorrent" version is 0.11.0, which has a > binary package libtorrent10-rakshasa with a library called > libtorrent.so.10, and also has that soname. Yes > > That all looks good. > >> I'm more confused since I renamed the package to libtorrent10-rakshasa >> and libtorrent-rakshasa10 and lintian keeps giving me the warning... > > I think in this case you can probably ignore the warning. > > Do you conflict with the -dev package of the other libtorrent package? > You'll both want to have a /usr/lib/libtorrent.so, so you should > conflict. - -dev is used just for building rtorrent and -dev needs libtorrent-rakshasa so if I conflict them -dev can't build. > > You probably now don't have a conflict with other library package now, > but at some point this might happen. And I think this should be > avoided. > > I think either one or both should really change the name of the library > itself, to avoid all confusion, and also make them not conflict. For > instance, you could name it librakshasatorrent (or librtorrent). Well, the one with rasterbar will name it libtorrent-rasterbar and I will name the library libtorrent-rakshasa, so, I think there's no conflict. > > The ideal solution would be that there really was only 1 libtorrent > package, and that both current of them worked on 1 library. Well, rakshasa is used by rtorrent, and rasterbar is used by another bittorrent clients. > > > Kurt > > Thanks!! Jose - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFh1C2OKCtW8rKsRgRAkYVAJ4rDfVvgxvmuaJ6ueZ12nj2KtRHIACg0l+l dEBZkTiLNTrVxh5fJ6ywrZ4= =eh+/ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Name of a binary package according to sonames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Felipe Sateler escribió: > Jose Luis Rivas Contreras wrote: > >> I'm more confused since I renamed the package to libtorrent10-rakshasa >> and libtorrent-rakshasa10 and lintian keeps giving me the warning... > > I am giving a try at the rasterbar's library, and ran into the same issue. I > asked on #debian-mentors and they told me that a lintian override was > needed in that case. > Yes, that's what I will do, that's the only solution. :/ Thanks!! Jose - -- ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503 http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug San Cristobal - Venezuela. TALUG -- http://linuxtachira.org Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFh1DsOKCtW8rKsRgRAhc2AKCDCWD4D6e10hakmlcMIZKjwP9J8ACgluAq n0s71KCyvGLfYb8BSlEmFcY= =cUuJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mailing lsit code of conduct, again
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frans Pop wrote:
> Ben Finney wrote:
>> Russ Allbery <[EMAIL PROTECTED]> writes:
>>> We don't enforce it anyway, and all this provision seems to do in
>>> practice is create these annoying arguments periodically.
>> No, that's not all it does. It also has the significant effect that
>> discussions in these forums do not, in the main, generate needless
>> individual copies of messages in the participants's mailboxes. I, and
>> presumably the people who drafted the code of conduct, continue to
>> find that a very favourable outcome of this provision.
>
> Fully agreed. I'd hate to see this dropped from the CoC.
>
> Clint Adams sent a request to d-www to have the CoC changed and I have
> replied with a strong NACK to that suggestion. If the CoC should be
> changed, it should be done after a proper discussion (on d-project
> probably) and at least be done in coordination with the listmasters, not as
> the result of an individual request by a random DD.
>
> Cheers,
> FJP
I believe it could be easier that the mailing list software left the
mailing list in the reply-header. The main issue is that when you hit
"Reply" the only one who is left in the headers is actually who sent the
email and if you hit "Reply All" obviously the author of the last email
is listed too.
There's a good reason why this haven't been done yet? Other mailing
lists which I've been subscribed use this.
Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIMErPOKCtW8rKsRgRAiieAKCaf3a+JQZhCNQP3/vdvhQpNBgMIACfUBLA
MpQ/DR0Ce5xQj2OZXi2wrkk=
=mtbj
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Anyone
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] escribió: > Hello, debian-devel. > > Yes, this library needed for generating pdf docs from PHP. > Could you package it into next version? > Hi, 1 - Exists RFP: http://www.us.debian.org/devel/wnpp/requested 2 - We can't guess without hints ;-) Jose Luis, - -- ghostbar @ linux/debian 'sid' x86 - #382503 WeBlog: http://ghostbar.ath.cx/ - http://talug.org.ve http://debian.org.ve - irc.debian.org #debian-ve San Cristóbal, Venezuela. Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGDsY8OKCtW8rKsRgRAnypAKCejmcIYCp1LaJt9PJ1H+npcQBwvQCeKOfP qJbz6eoFe6JbVzmltkTIbEc= =Z/kn -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Three-package clearance sale
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Clint Adams escribió: > zsh30 - zsh 3.0 Hi, this includes all zsh packages? or just zsh30?... Jose Luis, - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://talug.org.ve http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGGt5fOKCtW8rKsRgRAgaCAJ4yF7MN+9NhduvExlraBVoCTNchKACfV9mH QgVuEj5xTzYe2A0agH4D+4Q= =DWqz -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apparently-corrupted-elf-binary lintian problems on recent sid and amd64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Enrico Zini escribió: > I'm tring to build version -2 for upload, but it's giving me this > problem. Since the changes are very minor, the problem can be > reproduced with the -1 version that is in Debian now. > > What's going on? How can I build this thing correctly here? Hey, I built your package adding a `*/' in lines 85 and 86 of `debian/rules' before of `*.[a|la]'. I got a lintian and linda clean package. Maybe that's your problem. [EMAIL PROTECTED]:~/tests/scim-chewing$ lintian -i /var/cache/pbuilder/result/scim-chewing_0.3.1-1_i386.deb [EMAIL PROTECTED]:~/tests/scim-chewing$ linda -i /var/cache/pbuilder/result/scim-chewing_0.3.1-1_i386.deb [EMAIL PROTECTED]:~/tests/scim-chewing$ Regards, Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGRjhSOKCtW8rKsRgRAkPTAJ91alWdwsyT4Ln99BVOq015hSh+TACgt2nM 2qHW9GZlvRsPA1gCk0t4ZZo= =k2k7 -END PGP SIGNATURE- -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian desktop -situation, proposals for discussion and change. Users point of view.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mgr. Peter Tuharsky escribió: > Stanislav, > > > I see Your point, however this is far from "user-friendliness". > > First solution -use other distro. Wow, what a great idea. Looking at > statistics and Linux users in neighborhood, You can be _sure_ they > discovered that way already :-) > > Be also sure, that unwilling to do more for desktop users, Debian will > not be less, but increasingly more server-oriented distro (I like Debian > on server!). I like Debian either. What about maintainer/developer-friendly thing? I mean, you want that us change all our infrastructure, but then he gives you as solution to change one line and exec one command and you think that's not user-friendly? There's no magical ways to do this, if you want newer packages then use lenny and if you want even more newer use sid. I use sid because of that and my system is pretty stable. Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTDSzOKCtW8rKsRgRAv1yAJ9kd5ARNDxEsPct0rIdyyMosRrj2ACfQTRC 7yBRzG5rtH3LptRcnRJ8T7s= =9zdg -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#364438: broken afer upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hey, this is a very old bug about an upgrade a year ago, no one confirms it, should I close it? Refer to http://bugs.debian.org/364438 for more info. Regards, Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTKDfOKCtW8rKsRgRAqXaAJ9MWbIgyaKPJeDzMkV/iBfbBb05vACfbDBT tCtrhQI8hNz/AGJRr2zD8G4= =Z03x -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howard Young escribió: > looking through the list I now see that may be quite possible to achieve > what I wanted using, some sort of match priority command and piping it > back into the remove command. You should try using aptitude, it does what you want ;-) Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTdSDOKCtW8rKsRgRAvbNAKCUCrYD9dUbnEqk4MMvSCigbhLjoQCfYBNl 9RgSNO/Pk7pTIua5llUeblg= =sQur -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: apt-get
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Amir Tabatabaei escribió: > I'm satisfied but I do of course miss this feature. I think I'm too much > used to it that I don't want to try anything else. But you are right, > switching will be hard and after some while everything will be normal > again. I will try to use aptitude from now on. Lets see how nice it > is... No, it's not hard, it's very easy, aptitude seems to much to apt-get so there's no difficult ;) Jose Luis. - -- ghostbar on Linux/Debian 'sid' i686 - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGTjN4OKCtW8rKsRgRAiYKAKC8BIO3n5ImeSSizXPL/F0cDzqw0ACdGyLV 5grtcNW9sqN1CwqF/AVDZJk= =gf9z -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Is Chris Leishman (masklin) MIA?
Hi, Checking some things for a build-dependency I will need, I found that Chris Leishman (aka masklin)[0] had not uploaded a package since 27/10/2004[1] and the packages have clearly new updates. I think he's clearly MIA and sending him an email for checking would be a waste of time and his packages should be orphaned as quickly as could. Regards, Jose Luis. [0] http://qa.debian.org/[EMAIL PROTECTED] [1] http://packages.qa.debian.org/libx/libxml++2.6/news/20041027T014703Z.html -- ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 signature.asc Description: OpenPGP digital signature
Bug#448274: general: Create a meta package named debian-kde-desktop
Rafael wrote: > Package: general > Severity: wishlist > > I suggest the creation of a meta package named for example debian-kde-desktop > which should > install the most common used KDE aplications in a Desktop and KDE Desktop > with Debian artwork. > At style of meta package kubuntu-desktop in Ubuntu project. > A general configuration may be: > -Open Office as office suit. > -Kaffeine as video player. > -Amarok as audio player. > -D3lphin as default File Manager (It is easy configure KDE 3.5 for it). > -Konqueror and Iceweasel web browsers availables. > -Gwenview as image viewer. > -Gimp as image editor. > -Kwrite or kate as text editor. > -Adept suit for Package Management (adept-manager, adept-updater, > adept-notifier, > adept-installer), including software-properties-kde. > -Kmail as mail manager. > -Gdebi-kde for manual installation of Debian Packages. > -Ark for file compression. > -k3b for CD/DVD burning and Audio/Video extraction. > -speedcrunch calculator. > -gtk-qt-engine configured for a well presentation of possible installed gtk > aplications in KDE. > -xmodmap and kmilo well configured for having special keyboard keys available. > -kooka for use scanner. > -kdpf or acroread for PDF viewing. > -qt4-qtconfig installed for configure qt 4 aplications apparience (as > speedcrunch). > -ksystemlog for view system logs. > -kmix for volume management. > > And any other aplication useful for Desktop use and management. The idea is > to install one > aplication for each function trying to choose the best aplication for each > function, > for example is a waste of disk having installed gwenview and kview, > kaffeine + kaboodle + noatun, speedcrunch + kcalc, adept + kpackage ... > > > You shoud do the same for XFCE Desktop and Gnome. I guess you mean like the meta-package `kde', as the meta-package `gnome' and as the meta-package `xfce4' already does? Regards, Jose Luis. -- ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve GPG: 0xCACAB118 signature.asc Description: OpenPGP digital signature
Re: old bugs are still shown on the bugs page
Kamaraju S Kusumanchi wrote: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339581 has been fixed on > Apr 17, 2007. But it still shows up in http://bugs.debian.org/texmacs . Is > this a bug in the BTS or am I missing something stupid? Maybe it's because a version with the bug is still available in oldstable? Not so sure. Regards, Jose Luis. -- ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve GPG: 0xCACAB118 signature.asc Description: OpenPGP digital signature
Re: Making contributing to Debian easier ; "gift" bug tag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lucas Nussbaum wrote:
> Hi,
>
> I've been thinking about ways to make contributing to Debian easier. I
> sometimes run into the situation where someone asks me "I'd like to
> contribute to Debian, what could I do?", and I have problems directing
> him to things where he could actually help.
>
> So I worked on two things:
>
> == "Help Debian!" web page ==
> I think that we need a page that gives an overview of how a newcomer
> could help. And a sexy one. Christian Perrier's slides from FOSS.in[0] are
> a very good basis, but we need to work on converting this into something
> suitable for a web page.
>
> I started writing some stuff on http://wiki.debian.org/HelpDebian/Start
> . Feel free to improve that, or to point me to pages I could use as a
> basis. The plan is to move this to a separate, stable, web page, with
> pics, etc. There's also a few notes on http://wiki.debian.org/HelpDebian .
>
Well, in Spanish there's a similar initiative, anyone interested can
check http://wiki.debian.org/ComoContribuir that translated is "HowToHelp".
And the tag idea it's very nice.
Regards.
- --
Jose Luis Rivas. San Cristóbal, Venezuela. PGP: 0xCACAB118
http://ghostbar.ath.cx/{about,acerca} - http://debian.org.ve
`ghostbar' @ irc.debian.org/#debian-ve,#debian-devel-es
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHb/3UOKCtW8rKsRgRAlaGAJ9MgZzokn0Q/36ClsXiyT8dORCzhgCfasGq
ZsDLm+bkN0XUeQyZN80kzEE=
=QUyh
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
