Re: gbp import-orig has defeated me [and 1 more messages]
Shengjing Zhu writes ("Re: gbp import-orig has defeated me"):
> I think you have configured your git to auto convert the line ending
> when commit.
>
> In the pristine-tar tarball,
> $ file googletest-release-1.8.1/googlemock/msvc/2005/gmock.sln
> googletest-release-1.8.1/googlemock/msvc/2005/gmock.sln: UTF-8 Unicode
> (with BOM) text, with CRLF line terminators
>
> In your master and upstream branch
> $ file googletest-1.8.1/googlemock/msvc/2005/gmock.sln
> googletest-1.8.1/googlemock/msvc/2005/gmock.sln: UTF-8 Unicode (with BOM) tex
Well spotted.
> I import the orig tarball in my env, these files are CRLF in my git tree.
> I'm not sure what git config influences this, but maybe core.eol,
> core.autocrlf, core.safecrlf.
Debian packging git tools could perhaps suppress these options, or
warn about them.
I know that dgit and git-deborig already take care to suppress
.gitattributes. I hadn't considered the eol configurastion
parameters. Maybe they need to be squashed or warned about too -
although unlike with .gitattributes, the default git configuration is
safe.
Steve Robbins writes ("Re: gbp import-orig has defeated me"):
> I think you've pointed in the right direction. I have started
> reading through
> https://adaptivepatchwork.com/2012/03/01/mind-the-end-of-your-line/
> and discovered that I have one non-default: core.autocrlf=input.
> According to the article, this is recommended for linux. Maybe
> that's not true;
I think you should not set any of these options. I disagree with the
discussion in that article surrounding the suggestion to use
core.autocrlf=input. Almost no-one should do this on Linux.
In the Debian context, if the orig tarball contains files with cr-lf
line endings, then so must your git tree. So you must not tell git to
convert things.
If these files with cr line endings are a nuisance should probably
complain to upstream. It is highly unusual to provide a tarball
containing DOS/Windows-format text files. In the meantime you'll have
to repack the tarball :-/.
> or maybe I just need to generate a .gitattributes file? I'll try
> that tomorrow.
Please don't do that. (I don't think it would work, anyway.)
See also:
https://manpages.debian.org/stretch/dgit/dgit.7.en.html#GITATTRIBUTES
This applies even if you are not intending to upload with dgit.
But, of course, you should upload with dgit.
Good luck.
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Bug#910077: ITP: binoculars -- Surface X-ray diffraction 2D detector data reduction
Package: wnpp Severity: wishlist Owner: Picca Frédéric-Emmanuel * Package name: binoculars Version : 0.0.1 Upstream Author : Willem Onderwaater * URL : https://github.com/id03/binoculars * License : GPL-3+ Programming Lang: Python Description : Surface X-ray diffraction 2D detector data reduction BINoculars is a tool for data reduction and analysis of large sets of surface diffraction data that have been acquired with a two-dimensional X-ray detector. The intensity of each pixel of a two-dimensional detector is projected onto a three-dimensional grid in reciprocal-lattice coordinates using a binning algorithm. This allows for fast acquisition and processing of high-resolution data sets and results in a significant reduction of the size of the data set. The subsequent analysis then proceeds in reciprocal space. It has evolved from the specific needs of the ID03 beamline at the ESRF, but it has a modular design and can be easily adjusted and extended to work with data from other beamlines or from other measurement techniques.
Bug#910085: ITP: gnukhata-core -- Free Accounting Software (Core Engine)
Package: wnpp Severity: wishlist Owner: Manas Kashyap X-Debbugs-CC: debian-devel@lists.debian.org * Package name: gnukhata-core Version : 5.25.0 Upstream Author : Krishnakant Mane * URL : http://gnukhata.in * License : GPL - 3 Programming Lang: Python Description : it is a Free Accounting Software which can be deployed by both profit making and non-profit making organisations. . The advantages of GNUKhata are . - It is lightweight and scales up with large volumes of data - It is robust and can be used on a wide variety of data categories - It is modular, thus facilitating addition of extensions for different tasks - The user interface is designed to be intuitive and friendly even for beginners - The reports are displayed on browser and can be printed or saved to PDF - Deployers will find the implementation easy to achieve. - GNUKhata is a free software, sometimes referred to as free and open source software or FOSS
Re: gbp import-orig has defeated me [and 1 more messages]
Hello, On Tue 02 Oct 2018 at 12:59PM +0100, Ian Jackson wrote: > I think you should not set any of these options. I disagree with the > discussion in that article surrounding the suggestion to use > core.autocrlf=input. Almost no-one should do this on Linux. > > In the Debian context, if the orig tarball contains files with cr-lf > line endings, then so must your git tree. So you must not tell git to > convert things. > > If these files with cr line endings are a nuisance should probably > complain to upstream. It is highly unusual to provide a tarball > containing DOS/Windows-format text files. In the meantime you'll have > to repack the tarball :-/. I would like to suggest: % # clone from salsa % git remote add -f upstream https://github.com/google/googletest % git merge release-1.8.1 % dch -v1.8.1-1 New upstream release. % git deborig i.e. make your own tarball rather than putting in so much effort to use exactly the one from upstream. -- Sean Whitton signature.asc Description: PGP signature
Re: gbp import-orig has defeated me [and 1 more messages]
Sean Whitton writes ("Re: gbp import-orig has defeated me [and 1 more
messages]"):
> On Tue 02 Oct 2018 at 12:59PM +0100, Ian Jackson wrote:
> > If these files with cr line endings are a nuisance should probably
> > complain to upstream. It is highly unusual to provide a tarball
> > containing DOS/Windows-format text files. In the meantime you'll have
> > to repack the tarball :-/.
>
> I would like to suggest:
>
> % # clone from salsa
> % git remote add -f upstream https://github.com/google/googletest
> % git merge release-1.8.1
> % dch -v1.8.1-1 New upstream release.
> % git deborig
>
> i.e. make your own tarball rather than putting in so much effort to use
> exactly the one from upstream.
I had somehow overlooked in this discussion that obviously there would
be a git upstream. In which case yes, Sean's suggestion is obviously
right.
Going to a lot of effort to reuse (and maybe fix up) a broken tarball
from upstream does seem silly.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Problem sending my key to keyring.debian.org
Hi, I'm having issues sending my updated key to keyring.debian.org: $ gpg --keyserver keyring.debian.org --send-keys E823DA111E22D7857E1D865863F7800A23D7B252 gpg: sending key 63F7800A23D7B252 to hkp://keyring.debian.org gpg: keyserver send failed: No keyserver available gpg: keyserver send failed: No keyserver available Do you have any idea what I could do wrong here? Thanks for your help, Joseph
Updating the New Debian Developer welcome email
Hi,
Yesterday I received my New Debian Developer welcome email (\o/) and
noticed that it's still referencing alioth for the hosting of VCS
repositories.
I couldn't find in which repo the template for this email was hosted.
Could you point me to the right repo so I can do a MR for this please?
The paragraph I'd like to propose a change for is:
The machine hosting most of our VCS repositories
({svn,bzr,git,arch,hg}.debian.org) is alioth.debian.org. It's handled
by a separate team (ad...@alioth.debian.org) as it allows login by
non-Debian developers. You probably already have a *-guest account
there. Please refer to https://wiki.debian.org/AliothFAQ to learn
anything you need to know, including how to activate your account and
how to request the removal of your old -guest account.
Thanks
Joseph
Bug#910121: RFP: lua-inspect -- Lua table visualizer, ideal for debugging
Package: wnpp Severity: wishlist * Package name: lua-inspect Version : 3.1.1-0 Upstream Author : Enrico García Cota * URL : https://luarocks.org/modules/kikito/inspect * License : MIT Programming Lang: Lua Description : Lua table visualizer, ideal for debugging This library transforms any Lua value into a human-readable representation. It is especially useful for debugging errors in tables. The objective here is human understanding (i.e. for debugging), not serialization or compactness. --- I'd like this to be packaged, since it will be a test requirement for Neovim's next release.
Sending using my @debian.org in gmail
Hi guys, Wondering if anybody here succeeded to configure your debian email in the "Send mail as" configuration in gmail (for the gmail users). If so do you have tips on how you didi it? My main problem seems to be that gmail forces the authentication and master.debian.org doesn't allow it. It returns: "Unspecified Error (SENT_SECOND_EHLO): Smtp server does not advertise AUTH capability, code: 0" I've also tried to send emails after configuring thunderbird but encountered some issues as well. Seems master.debian.org doesn't allow to send to non debian.org address, its that correct? Thanks for your help, Joseph
Re: Updating the New Debian Developer welcome email
On Tue, Oct 02, 2018 at 05:45:35PM -0700, Joseph Herlant wrote: > Yesterday I received my New Debian Developer welcome email (\o/) Congrats! > and > noticed that it's still referencing alioth for the hosting of VCS > repositories. > > I couldn't find in which repo the template for this email was hosted. > Could you point me to the right repo so I can do a MR for this please? DSA manages user accounts. After a little digging, I found the template[0]. [0]: https://salsa.debian.org/dsa-team/mirror/userdir-ldap/blob/master/templates/welcome-message-Debian Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Re: Sending using my @debian.org in gmail
On 2018-10-02 8:52 p.m., Joseph Herlant wrote: > Hi guys, > > Wondering if anybody here succeeded to configure your debian email in > the "Send mail as" configuration in gmail (for the gmail users). If so > do you have tips on how you didi it? I did. > My main problem seems to be that gmail forces the authentication and > master.debian.org doesn't allow it. It returns: "Unspecified Error > (SENT_SECOND_EHLO): Smtp server does not advertise AUTH capability, > code: 0" It looks like you are trying to use Debian smtp servers. I just use smtp.gmail.com. There is a Gmail trick where you can add one send-as email and provide smtp.gmail.com credentials. You might have to create an app password. I think that this guide does something similar to what I did: - https://blog.alexlenail.me/i-want-to-send-emails-from-my-google-domains-email-through-gmail-992bb3eae4c9 Let me know if this works out for you. Cheer, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Re: Problem sending my key to keyring.debian.org
On Tue, Oct 02, 2018 at 05:39:34PM -0700, Joseph Herlant wrote: > I'm having issues sending my updated key to keyring.debian.org: > [...] > Do you have any idea what I could do wrong here? Two thoughts: first, give it another try. I was able to refresh my keyring using the debian keyserver a few seconds ago: $ gpg --refresh-keys --keyserver keyring.debian.org gpg: refreshing 229 keys from hkp://keyring.debian.org ... gpg: new signatures: 160 ... Second, the keyservers all communicate with each other. If one is down, aim for another. e.g. keyserver.ubuntu.com or other choices from https://sks-keyservers.net/status/ Eventually your key will make it everywhere. Thanks signature.asc Description: PGP signature
Re: Problem sending my key to keyring.debian.org
On 2018-10-02 9:10 p.m., Seth Arnold wrote: > Second, the keyservers all communicate with each other. If one is down, > aim for another. e.g. keyserver.ubuntu.com or other choices from keyring.debian.org pulls updates from the keyserver network? I wasn't sure, and I would always send to keyring.debian.org separately. Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature
Re: Problem sending my key to keyring.debian.org
Hi, On Tue, Oct 2, 2018 at 6:10 PM Seth Arnold wrote: > Two thoughts: first, give it another try. I was able to refresh my > keyring using the debian keyserver a few seconds ago: > > $ gpg --refresh-keys --keyserver keyring.debian.org > gpg: refreshing 229 keys from hkp://keyring.debian.org > ... > gpg: new signatures: 160 > ... Ok, so that's really a problem on my end. I've been having this issue since I started trying to update it yesterday and still have now. Tried 4 or 5 times during the day, same issue. Same error while trying to refresh. > Second, the keyservers all communicate with each other. If one is down, > aim for another. e.g. keyserver.ubuntu.com or other choices from > https://sks-keyservers.net/status/ > > Eventually your key will make it everywhere. I'm surprised keyring.debian.org is automatically synced, but that's good to know. It's on other (gnu, mit etc) keyservers so it'll get there eventually. Thanks! :) Joseph
Re: Problem sending my key to keyring.debian.org
On Wed, Oct 3, 2018 at 9:16 AM Alexandre Viau wrote: > keyring.debian.org pulls updates from the keyserver network? No, it does not. > I wasn't sure, and I would always send to keyring.debian.org separately. This is still necessary. -- bye, pabs https://wiki.debian.org/PaulWise
Re: Updating the New Debian Developer welcome email
Hi, I filed the bug yesterday in nm.debian.org package but got a reply that the welcome message is managed by admin team, not NM. https://bugs.debian.org/910057 Are there discussions about updating welcome email in Debian RT already? Yao Wei (This email is sent from a phone; sorry for HTML email if it happens.) > On Oct 3, 2018, at 08:56, James McCoy wrote: > >> On Tue, Oct 02, 2018 at 05:45:35PM -0700, Joseph Herlant wrote: >> Yesterday I received my New Debian Developer welcome email (\o/) > > Congrats! > >> and >> noticed that it's still referencing alioth for the hosting of VCS >> repositories. >> >> I couldn't find in which repo the template for this email was hosted. >> Could you point me to the right repo so I can do a MR for this please? > > DSA manages user accounts. After a little digging, I found the > template[0]. > > [0]: > https://salsa.debian.org/dsa-team/mirror/userdir-ldap/blob/master/templates/welcome-message-Debian > > Cheers, > -- > James > GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB >
Re: Problem sending my key to keyring.debian.org
On Wed, Oct 03, 2018 at 09:38:43AM +0800, Paul Wise wrote: > On Wed, Oct 3, 2018 at 9:16 AM Alexandre Viau wrote: > > keyring.debian.org pulls updates from the keyserver network? > No, it does not. > > I wasn't sure, and I would always send to keyring.debian.org separately. > This is still necessary. Oh. :( I'm sorry to have given bad advice. Thanks pabs signature.asc Description: PGP signature
Re: Sending using my @debian.org in gmail
Hi! :) On Tue, Oct 2, 2018 at 6:04 PM Alexandre Viau wrote: > It looks like you are trying to use Debian smtp servers. I just use > smtp.gmail.com. > > There is a Gmail trick where you can add one send-as email and provide > smtp.gmail.com credentials. > > You might have to create an app password. > > I think that this guide does something similar to what I did: > - > https://blog.alexlenail.me/i-want-to-send-emails-from-my-google-domains-email-through-gmail-992bb3eae4c9 > > Let me know if this works out for you. Awesome, that works now. Thank you very much! :) I'll add that to the wiki page in case somebody else gets the issue. Joseph
Re: Sending using my @debian.org in gmail
> I'll add that to the wiki page in case somebody else gets the issue. FYI: updated https://wiki.debian.org/MigrateToDDAccount with the details. Not sure if that would be an issue to mention gmail specifically there as it's vendor-specific. Feel free to remove it if it's a problem. Joseph
Re: Updating the New Debian Developer welcome email
Thank you both for your replies. I went ahead and pushed a MR: https://salsa.debian.org/aerostitch/userdir-ldap/merge_requests/1 > Are there discussions about updating welcome email in Debian RT already? I notified the DSA team on #debian-admin as Mattia was saying in #910057 We'll see the follow-ups. Thanks again, Joseph
Re: gbp import-orig initially defeated me [but now I've won]
Hi, Thanks to all! I have gotten past the issue and created a build now. On Tuesday, October 2, 2018 6:59:54 AM CDT Ian Jackson wrote: > I think you should not set any of these options. I disagree with the > discussion in that article surrounding the suggestion to use > core.autocrlf=input. Almost no-one should do this on Linux. Hmm. Good to know. I changed back to the default. I can't recall when I changed it, but I suspect it was in response to reading the github page: https://help.github.com/articles/dealing-with-line-endings/ > In the Debian context, if the orig tarball contains files with cr-lf > line endings, then so must your git tree. So you must not tell git to > convert things. Makes sense. -Steve
