Bug#848217: ITP: lua-inotify -- Inotify bindings for Lua

[Sophie Brun]

Package: wnpp
Severity: wishlist
Owner: Sophie Brun 

* Package name: lua-inotify
  Version : 0.4
  Upstream Author : Robert Hoelz 
* URL : https://github.com/hoelzro/linotify
* License : MIT
  Programming Lang: C
  Description : Inotify bindings for Lua

This is a Lua binding for the Linux inotify library.

contacting all bug reporters for a package?

[Daniel Pocock]

Is there any easy way to contact everybody who made a bug report against
a package and ask them to check if the latest upload fixes it?  Or is
there any script for maintainers to do this?

If somebody has opened 2 ore more bugs maybe they may prefer to only
receive a single email summarizing all their bugs for that package.

For example, nfs-utils has over 100 active bug reports and although I
spent some time updating it I'm not keen to go through all the bugs one
by one.

Given that a lot of things were fixed upstream between 1.2.8 and 1.3.4
it is quite possible some people can close their own bugs, or even
better, tell us if the bug is still unfixed and potentially RC.

Regards,

Daniel

Bug#848222: ITP: textql -- execute SQL against structured text like CSV or TSV

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)" 

* Package name: textql
  Version : 2.0.3
  Upstream Author : Copyright (c) 2014, Paul Bergeron
* URL : https://github.com/dinedal/textql/
* License : Expat
  Programming Lang: golang
  Description : execute SQL against structured text like CSV or TSV

 TextQL allows you to easily execute SQL against structured text like
 CSV or TSV.



-- 
ChangZhuo Chen (陳昌倬) 
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Re: contacting all bug reporters for a package?

[gregor herrmann]

On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:

> Is there any easy way to contact everybody who made a bug report against
> a package and ask them to check if the latest upload fixes it?  Or is
> there any script for maintainers to do this?

I'm not sure this is a good idea ... Anyway, I'd as a start try
something like

% bts select src:nfs-utils status:open | uniq | xargs printf 
"%s-submit...@bugs.debian.org\n"
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   BOFH excuse #362:  Plasma conduit breach 

Re: Bug#843073: dpkg-shlibdeps fix for merged /usr

[Guillem Jover]

On Mon, 2016-12-12 at 04:26:20 +0100, Marco d'Itri wrote:
> On Nov 21, Guillem Jover  wrote:
> > First I have to go over a list of queued pending items and then I'll
> > get to this during this week. I have not yet reviewed the patches (in
> > part because I didn't do much Debian stuff last week due to lack of
> > motivation after an unpleasant interaction precisely due to this
> > issue, and TBH it has become one of those energey drainers), there's
> > a pending run in rebootstrap by Helmut (which is now waiting for a
> > gixed gcc), and then I need to write a mail summary of the current
> > situation and implications.

> Do you have any updates about reviewing this patch?

Now that Helmut has done an initial successful build with rebootstrap,
I'm planning on reviewing and merging this after having sent that summary
mail, either for .16 or .17, which I'd like to upload in quick succession,
starting this week.

Thanks,
Guillem

Re: Auto-detecting -dev package dependences from pkg-config

[Guillem Jover]

Hi!

On Sun, 2016-12-11 at 21:48:17 -0800, Josh Triplett wrote:
> [Please CC me on replies.]

> I'd like to build some tools (possibly including a dh_pkgconfig) to do
> this automatically; those tools could generate a pkgconfig:Depends
> substvar for use in debian/control.  Before starting on those tools, I'd
> like to get some feedback on this idea.

There's also . I'd be happy to
include such tool in dpkg itself. I think this is one of the current
limitations we have in dpkg-dev compared to say rpm, which has many
build-time dependency generators.

> Does this seem like a reasonable approach?

Yes. And, I'd rather see this down in dpkg-dev than in debhelper if
possible.

Thanks,
Guillem

Bug#848241: ITP: node-has-cors -- Detect support for Cross-Origin Resource Sharing

[Paolo Greppi]

Package: wnpp
Severity: wishlist
Owner: Paolo Greppi 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-has-cors
  Version : 1.1.0
  Upstream Author : Nathan Rajlich http://n8.io/)
* URL : https://github.com/component/has-cors
* License : Expat
  Programming Lang: JavaScript
  Description : Detects support for Cross-Origin Resource Sharing

 Node.js module to detect support for CORS (Cross-Origin Resource
 Sharing), the mechanism that allows restricted resources on a web
 page to be requested from another domain outside the domain from
 which the resource originated.
 .
 Node.js is an event-based server-side JavaScript engine.

This is just 4 lines of code, but quite popular on npm registry (3M
downloads in the last month).
Besides it's required by node-engine.io-client which in turn is one of
the bits required by engine.io, socket.io and etherpad-lite.

Paolo

Re: contacting all bug reporters for a package?

[Don Armstrong]

On Thu, 15 Dec 2016, gregor herrmann wrote:
> On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:
> > Is there any easy way to contact everybody who made a bug report
> > against a package and ask them to check if the latest upload fixes
> > it? Or is there any script for maintainers to do this?
> 
> I'm not sure this is a good idea ... Anyway, I'd as a start try
> something like
> 
> % bts select src:nfs-utils status:open | uniq | xargs printf 
> "%s-submit...@bugs.debian.org\n"

bts select src:nfs-utils status:open|bts status file:- 
fields:originator|sort|uniq

will give you the unique email addresses. [Well, realname + e-mail addresses.]

-- 
Don Armstrong  https://www.donarmstrong.com

If it jams, force it. If it breaks, it needed replacing anyway.
 -- Lowery's Law

Bug#848245: ITP: leap-cli -- command-line tool for managing LEAP platform service provider infrastrucutre

[micah]

Package: wnpp
Severity: wishlist
Owner: Micah Anderson 

* Package name: leap-cli
  Version : 1.9.0
  Upstream Author : LEAP Encryption Access Project 

* URL : http://leap.se
* License : MIT
  Programming Lang: Ruby
  Description : command-line tool for managing LEAP platform service 
provider infrastrucutre

The leap command line tool is used by sysadmins to manage everything about a
service provider’s infrastructure, including:

* Create, initialize, and deploy nodes.
* Manage keys and certificates.
* Query information about the node configurations.
* Everything about your provider is managed by editing JSON configuration files
  and running leap commands.

The leap command-line tool is run on your workstation, and never on a server you
are deploying to.

It is also run from within a provider instance: The leap command requires that
the current working directory is a valid provider instance, except when running
leap new to create a new provider instance.

Re: contacting all bug reporters for a package?

[Jonathan Dowland]

On Thu, Dec 15, 2016 at 11:26:52AM +0100, gregor herrmann wrote:
> On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:
> 
> > Is there any easy way to contact everybody who made a bug report against
> > a package and ask them to check if the latest upload fixes it?  Or is
> > there any script for maintainers to do this?
> 
> I'm not sure this is a good idea ...

Me neither, although I suppose it's no worse than being manually pinged, which
happens quite often for me (often for 10+ year old bugs)

In this case, the bug I'd filed against nfs-utils had indeed been fixed at some
point, so it worked out worthwhile I suppose!

In related news, I was surprised to receive 7 copies of a 1M control@b.d.o
email recently.


-- 
Jonathan Dowland
Please do not CC me, I am subscribed to the list.


signature.asc
Description: Digital signature

Re: contacting all bug reporters for a package?

[Don Armstrong]

On Thu, 15 Dec 2016, Jonathan Dowland wrote:
> In related news, I was surprised to receive 7 copies of a 1M
> control@b.d.o email recently.

That was me; sorry about that. Presumably you got all of the copies
because they were to different aliases which eventually ended up hitting
you.

[I had to unarchive a slew of bugs which were archived because of a
versioning screwup.]


-- 
Don Armstrong  https://www.donarmstrong.com

PowerPoint is symptomatic of a certain type of bureaucratic
environment: one typified by interminable presentations with lots of
fussy little bullet-points and flashy dissolves and soundtracks masked
into the background, to try to convince the audience that the goon
behind the computer has something significant to say.
 -- Charles Stross _The Jennifer Morgue_ p33

De 10 Fatale Fouten in de Verkoop

[Roger Van Loocke]

De 10 Fatale Fouten in de Verkoop  

   Als u deze e-mail in tekstformaat ontvangt, zonder afbeeldingen,
klik hier [1]! 

Een te lage omzet of marge : hoe snel weer groeien? Strategische
informatie voor bedrijfsleiders. Als u hier niets mee te maken heeft,
gelieve ons te verontschuldigen voor het ongemak. In dat geval kan u
uw adres  [2]uit onze lijst schrappen. [3]  

T.a.v. de Directie
Van: R. Van Loocke - CEO 

WELKE ZIJN DE WERKELIJKE REDENEN VAN EEN VERMINDERD ZAKENCIJFER?

GOEDEDAG,
 HEBBEN UW VERKOPERS SOMS DE NEIGING OM HUN GEBREK AAN RESULTATEN TE
VERRECHTVAARDIGEN DOOR DE CRISIS OF ANDERE EXTERNE FACTOREN AAN TE
ROEPEN? "WE ZIJN TE DUUR, HET IS OMDAT ONZE PRODUCTEN..., DE KLANTEN
HEBBEN DAAR GEEN GELD VOOR, ..."

 In deze moeilijke tijden is het cruciaal dat verkopers vechten voor
hun omzetcijfer en de marges verdedigen. Helaas zijn er veel verkopers
die zaken missen, ontmoedigd geraken, of zich te snel laten vangen aan
de valstrik van kortingen geven, volledig overtuigd "dat er niets aan
te doen is". 

WAT U MISSCHIEN NIET WEET...

EEN MARKTONDERZOEK BIJ 10.000 VERKOPERS HEEFT AAN HET LICHT GEBRACHT
DAT DE HELFT VAN DE MISLUKKINGEN IN DE VERKOOP EEN RECHTSTREEKS GEVOLG
IS VAN DE MENTALITEIT VAN DE VERKOPER EN ZIJN ATTITUDE. EN DIT HEEFT
NIETS TE MAKEN MET DE CRISIS OF PRIJZEN.

 En, er niet van bewust zijn dat ze steeds weer dezelfde fatale fouten
begaan, blijven ze zo hun gebrek aan resultaten wijten aan externe
factoren. Toch is het bewezen dat bij meer dan de helft van de
mislukkingen, het wel degelijk aan de verkoper ligt.

Het eerste wat kan gedaan worden, is duidelijk de remmen te (h)
erkennen.Daarom bieden we u gratis een zeer speciaal dossier aan,
genaamd De 10 fatale fouten in de verkoop [4].

 Dit dossier is een samenvatting van 20 jaar ervaring en zal het voor
u mogelijk maken heel duidelijk de problemen te identificeren die uw
omzetcijfer negatief kunnen beïnvloeden.  Daarna, en als deze fouten
"u aanspreken", zou de volgende actie erin bestaan u de geschikte
remedies te bezorgen. Dan kunnen we u een training aanbieden die in
Europa zijn gelijke niet kent. Deze is uitsluitend gebaseerd op de
aanpak van de beste verkopers in de wereld. Deze training kan u helpen
om heel snel de ingesteldheid, de vechtlust en de effectiviteit van uw
medewerkers om te vormen.

Ontvang uw gratis exemplaar van "De 10 fatale fouten in de verkoop
[5]" [6], lees het, en begin meteen met het oplossen van eventuele
probleemsituaties.

 We hopen van harte dat de cruciale informatie die u erin vindt voor u
nuttig zal zijn en u misschien zin zal doen krijgen om verder te gaan.

 Hartelijke groeten,

Roger Van Loocke
 CEO U-Man Belgium  

   [7]   [8]   [9]   [10] 

  U-Man Belgium : Werfheide 3 - 2812 Muizen - België
 +32 15 43 66 20 / +32 15 43 31 13
 i...@uman.be / www.uman.be  

 powered by
 [11] 

 

 Deze e-mail werd verstuurd naar debian-devel@lists.debian.org [12].
Uitschrijven [13] - Profiel update [14] 

 

 privacy policy [15]



Links:
--
[1]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11867/index.html
[2]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11868/index.html
[3]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11869/index.html
[4]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11870/index.html
[5]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11871/index.html
[6]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11872/index.html
[7]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11873/index.html
[8]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11874/index.html
[9]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11875/index.html
[10]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11876/index.html
[11]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11877/index.html
[12]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11878/index.html
[13]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11879/index.html
[14]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11880/index.html
[15]
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11881/index.html

Online versie: 
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11882/index.html
Deze e-mail werd verstuurd naar debian-devel@lists.debian.org.
Profiel aanpassen: 
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11884/index.html
Uitschrijven: 
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11883/index.html
Privacy policy: 
http://umanbelgium.fb.ma.addemar.com/c381/e826030/h5327b/l11885/index.html
Powered by Addemar: http://poweredby.addemar.com/

Re: contacting all bug reporters for a package?

[Daniel Pocock]

On 15/12/16 17:43, Jonathan Dowland wrote:
> On Thu, Dec 15, 2016 at 11:26:52AM +0100, gregor herrmann wrote:
>> On Thu, 15 Dec 2016 11:11:27 +0100, Daniel Pocock wrote:
>> 
>>> Is there any easy way to contact everybody who made a bug
>>> report against a package and ask them to check if the latest
>>> upload fixes it?  Or is there any script for maintainers to do
>>> this?
>> 
>> I'm not sure this is a good idea ...
> 
> Me neither, although I suppose it's no worse than being manually
> pinged, which happens quite often for me (often for 10+ year old
> bugs)
> 

Yes, I don't think this would be effective if every package maintainer
was doing it regularly.

Given the significant number of fixes upstream, the significant number
of bugs open for the package, the imminent freeze and the lack of
stability for NFS on jessie (due to at least one kernel bug), I
figured it was a reasonable approach in this case, giving a range of
interested people an opportunity to make the package better.

Based on feedback from one bug reporter, I could have included an
explicit disclaimer/apology that I hadn't read the individual bug
reports, although that was kind of implied by the message text[1]

If doing this again, maybe I would also refine it to try and exclude
the email going to people who contributed patches.  If only a few of
the bugs have patches then it is probably not too hard to thank them
personally while sending the bulk email to the rest.

> In this case, the bug I'd filed against nfs-utils had indeed been
> fixed at some point, so it worked out worthwhile I suppose!
> 

Great, I'm glad my upload may have helped

Regards,

Daniel


1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793661#10

Re: python3 reportbug in experimental: call for testing

[Andrey Rahmatullin]

On Wed, Dec 14, 2016 at 04:48:31PM +, Simon McVittie wrote:
> I've sent a patch series to #651590 which worked in at least basic testing
> (fixing gaps in pygtkcompat's compatibility shims, and moving towards
> using Gtk via g-i directly instead of via pygtkcompat).

This is what I get with 7.1.0 after choosing the bug severity:

(reportbug:7142): Gtk-CRITICAL **: gtk_text_attributes_ref: assertion 'values 
!= NULL' failed
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 2233, in 
main()
  File "/usr/bin/reportbug", line 1107, in main
return iface.user_interface()
  File "/usr/bin/reportbug", line 2149, in user_interface
package, severity, mode, charset=charset, tags=tags)
  File "/usr/bin/reportbug", line 182, in handle_editing
editor, charset)
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1561, in 
func
op = klass(parent)
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 539, in 
__init__
self.widget = self.create_widget()
  File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1173, in 
create_widget
expander = Gtk.Expander("Other system information")
TypeError: GObject.__init__() takes exactly 0 arguments (1 given)

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: python3 reportbug in experimental: call for testing

[Sandro Tosi]

On Thu, Dec 15, 2016 at 2:41 PM, Andrey Rahmatullin  wrote:
> On Wed, Dec 14, 2016 at 04:48:31PM +, Simon McVittie wrote:
>> I've sent a patch series to #651590 which worked in at least basic testing
>> (fixing gaps in pygtkcompat's compatibility shims, and moving towards
>> using Gtk via g-i directly instead of via pygtkcompat).
>
> This is what I get with 7.1.0 after choosing the bug severity:
>
> (reportbug:7142): Gtk-CRITICAL **: gtk_text_attributes_ref: assertion 'values 
> != NULL' failed
> Traceback (most recent call last):
>   File "/usr/bin/reportbug", line 2233, in 
> main()
>   File "/usr/bin/reportbug", line 1107, in main
> return iface.user_interface()
>   File "/usr/bin/reportbug", line 2149, in user_interface
> package, severity, mode, charset=charset, tags=tags)
>   File "/usr/bin/reportbug", line 182, in handle_editing
> editor, charset)
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1561, 
> in func
> op = klass(parent)
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 539, in 
> __init__
> self.widget = self.create_widget()
>   File "/usr/lib/python3/dist-packages/reportbug/ui/gtk2_ui.py", line 1173, 
> in create_widget
> expander = Gtk.Expander("Other system information")
> TypeError: GObject.__init__() takes exactly 0 arguments (1 given)

i think this is #848208

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Getting DEB_HOST_MULTIARCH from maintscripts

[Mathieu Parent (Debian)]

Hi,

I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to
create the appropriate symlink with update-alternatives.

What is the best way to do this?

Context:
my current hack (with a wildcard):
https://anonscm.debian.org/cgit/pkg-samba/cifs-utils.git/commit/?id=e5c9d43b5f1df09c7cd3c51f87cf5e70d704377a
the introduced bug: https://bugs.debian.org/848275

Regards
-- 
Mathieu Parent

Re: Getting DEB_HOST_MULTIARCH from maintscripts

[Wookey]

On 2016-12-15 22:50 +0100, Mathieu Parent (Debian) wrote:
> Hi,
> 
> I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to
> create the appropriate symlink with update-alternatives.
> 
> What is the best way to do this?

Depend on dpkg-dev and use dpkg-architecture?

dpkg-architecture -q DEB_HOST_MULTIARCH

I don't know of a better way.

There has been some talk of making dpkg-architecture available in
plain dpkg for exactly this sort of thing, but I don't see a bug about
it, and it needs gcc to do its job IIRC.


Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: Digital signature

Re: Getting DEB_HOST_MULTIARCH from maintscripts

[Sven Joachim]

On 2016-12-15 22:13 +, Wookey wrote:

> On 2016-12-15 22:50 +0100, Mathieu Parent (Debian) wrote:
>> Hi,
>> 
>> I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to
>> create the appropriate symlink with update-alternatives.
>> 
>> What is the best way to do this?
>
> Depend on dpkg-dev and use dpkg-architecture?

Please not.

> dpkg-architecture -q DEB_HOST_MULTIARCH
>
> I don't know of a better way.

Resolve $DEB_HOST_MULTIARCH at build time[1], when dpkg-architecture is
known to be around.

Cheers,
   Sven


1. https://wiki.debian.org/Multiarch/Implementation#Dynamic_debian.2F.2A_files

Re: Bug#847809: ITP: tcvt -- multicolumn virtual terminal

[Ferenc Wágner]

Adrien CLERC  writes:

> Le 11/12/2016 à 23:39, Ferenc Wágner a écrit :
>
>> * Package name: tcvt
>>   Version : git snapshot 82c24e2
>>   Upstream Author : Helmut Grohne 
>> * URL : http://subdivi.de/~helmut/tcvt/
>
> From the main page:
> Multibyte encodings such as utf8 are not supported, because Python is buggy.
>
> Is that still an issue? I highly doubt that a terminal application that
> doesn't support UTF8 is useful nowadays.

Unfortunately, this is still an issue and indeed limits the
applicability domain of the software.  However, it became feasible to
fix by dropping Python 2 support and work is ongoing now.
-- 
Regards,
Feri

Re: kronatools_2.7+dfsg-1_amd64.changes REJECTED

[Andreas Tille]

Hi Thorsten,

On Thu, Dec 15, 2016 at 10:00:10PM +, Thorsten Alteholz wrote:
> 
> according to [1] it is even a word mark, so I don't think it is a good 
> idea to let anything related to diagnostic software with krona in its 
> name into the archive.

Thanks for your torough checking. As discussed long ago[2]

  "KronaTools" may work, since the actual trademark is just "Krona". You could 
also use "Radiant", which was the original name (and still in SourceForge with 
a redirect). We avoided Radiant so our name could be trademarked, but you 
wouldn't have that problem I'm guessing.

It would help to hear other opinions before trying another upload to
new: What name do you think is a proper name for this project in Debian.

Any opinions?

Kind regards

 Andreas.

> [1] 
> https://www.dhs.gov/department-homeland-security-intellectual-property-policy

[2] 
https://lists.alioth.debian.org/pipermail/debian-med-packaging/2016-August/045589.html
https://github.com/marbl/Krona/issues/16 

-- 
http://fam-tille.de

Re: Auto-detecting -dev package dependences from pkg-config

[Paul Wise]

On Thu, Dec 15, 2016 at 8:43 PM, Guillem Jover wrote:

> There's also . I'd be happy to
> include such tool in dpkg itself. I think this is one of the current
> limitations we have in dpkg-dev compared to say rpm, which has many
> build-time dependency generators.

AppStream/DEP-11 was invented so Debian could catch up with rpm in this regard.

https://wiki.debian.org/DEP-11
https://wiki.debian.org/AppStream

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: Getting DEB_HOST_MULTIARCH from maintscripts

[Christian Seiler]

On 12/15/2016 10:50 PM, Mathieu Parent (Debian) wrote:
> I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to
> create the appropriate symlink with update-alternatives.
> 
> What is the best way to do this?

Generate them from .in files at the appropriate time, resolving
the variable manually. See for example:

https://sources.debian.net/src/dietlibc/0.34~cvs20160606-3/debian/rules/#L107-L110
https://sources.debian.net/src/dietlibc/0.34%7Ecvs20160606-3/debian/dietlibc-dev.postinst.in/

Regards,
Christian

Re: kronatools_2.7+dfsg-1_amd64.changes REJECTED

[Ian Jackson]

Andreas Tille writes ("Re: kronatools_2.7+dfsg-1_amd64.changes REJECTED"):
> On Thu, Dec 15, 2016 at 10:00:10PM +, Thorsten Alteholz wrote:
> > according to [1] it is even a word mark, so I don't think it is a good 
> > idea to let anything related to diagnostic software with krona in its 
> > name into the archive.
> 
> Thanks for your torough checking. As discussed long ago[2]
> 
>   "KronaTools" may work, since the actual trademark is just
>   "Krona". You could also use "Radiant", which was the original name
>   (and still in SourceForge with a redirect). We avoided Radiant so
>   our name could be trademarked, but you wouldn't have that problem
>   I'm guessing.

The upstream you are dealing with, here, clearly don't really
understand trademarks very well.  If "krona" is trademarked (and that
DHS page claims it is) then "kronatools" would clearly be a breach.

You'll have to call it something without the word "krona" in.

> It would help to hear other opinions before trying another upload to
> new: What name do you think is a proper name for this project in Debian.

I haven't been able to figure out what this program does.  Your links
don't give your own Description and the upstream say:

  Krona Tools is a set of scripts to create Krona charts from several
  Bioinformatics tools as well as from text and XML files.

Either this is circular, or "Krona chart" was a medical (or
medico-informatical) term before this software existed and it
shouldn't have been trademarked (although I doubt anyone wants to
fight that).

radiant-diagnostic or something maybe ?  (I see there is also a Ruby
CMS called "radiant".)

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.

Work-needing packages report for Dec 16, 2016

[wnpp]

The following is a listing of packages for which help has been requested
through the WNPP (Work-Needing and Prospective Packages) system in the
last week.

Total number of orphaned packages: 1037 (new: 4)
Total number of packages offered up for adoption: 149 (new: 0)
Total number of packages requested help for: 45 (new: 0)

Please refer to http://www.debian.org/devel/wnpp/ for more information.



The following packages have been orphaned:

   wmdrawer (#847602), orphaned 6 days ago
 Description: a button launcher
 Installations reported by Popcon: 77
 Bug Report URL: http://bugs.debian.org/847602

   wmlongrun (#847600), orphaned 6 days ago
 Description: program to monitor longrun status
 Installations reported by Popcon: 31
 Bug Report URL: http://bugs.debian.org/847600

   xkbset (#847599), orphaned 6 days ago
 Description: Small utility to change the AccessX settings of
   XKEYBOARD
 Installations reported by Popcon: 355
 Bug Report URL: http://bugs.debian.org/847599

   xvkbd (#847601), orphaned 6 days ago
 Description: software virtual keyboard for X11
 Installations reported by Popcon: 578
 Bug Report URL: http://bugs.debian.org/847601

1033 older packages have been omitted from this listing, see
http://www.debian.org/devel/wnpp/orphaned for a complete list.



No new packages have been given up for adoption, but a total of 149 packages
are awaiting adoption.  See http://www.debian.org/devel/wnpp/rfa_bypackage
for a complete list.



For the following packages help is requested:

   athcool (#278442), requested 4433 days ago
 Description: Enable powersaving mode for Athlon/Duron processors
 Installations reported by Popcon: 23
 Bug Report URL: http://bugs.debian.org/278442

   autopkgtest (#846328), requested 15 days ago
 Description: automatic as-installed testing for Debian packages
 Reverse Depends: debci-worker openstack-pkg-tools
 Installations reported by Popcon: 557
 Bug Report URL: http://bugs.debian.org/846328

   balsa (#642906), requested 1908 days ago
 Description: An e-mail client for GNOME
 Reverse Depends: balsa-dbg
 Installations reported by Popcon: 702
 Bug Report URL: http://bugs.debian.org/642906

   cardstories (#624100), requested 2061 days ago
 Description: Find out a card using a sentence made up by another
   player
 Installations reported by Popcon: 7
 Bug Report URL: http://bugs.debian.org/624100

   cups (#532097), requested 2749 days ago
 Description: Common UNIX Printing System
 Reverse Depends: bluez-cups boomaga chromium
   cinnamon-settings-daemon cloudprint cups cups-backend-bjnp
   cups-browsed cups-bsd cups-client (64 more omitted)
 Installations reported by Popcon: 174022
 Bug Report URL: http://bugs.debian.org/532097

   cyrus-sasl2 (#799864), requested 449 days ago
 Description: authentication abstraction library
 Reverse Depends: 389-ds-base 389-ds-base-libs 389-dsgw adcli
   autofs-ldap cairo-dock-mail-plug-in claws-mail
   claws-mail-acpi-notifier claws-mail-address-keeper
   claws-mail-archiver-plugin (127 more omitted)
 Installations reported by Popcon: 192867
 Bug Report URL: http://bugs.debian.org/799864

   dee (#831388), requested 153 days ago
 Description: model to synchronize mutiple instances over DBus
 Reverse Depends: dee-tools gir1.2-dee-1.0 libdee-1.0-4-dbg
   libdee-dev zeitgeist-core
 Installations reported by Popcon: 63660
 Bug Report URL: http://bugs.debian.org/831388

   developers-reference (#759995), requested 838 days ago
 Description: guidelines and information for Debian developers
 Installations reported by Popcon: 19588
 Bug Report URL: http://bugs.debian.org/759995

   devscripts (#800413), requested 443 days ago
 Description: scripts to make the life of a Debian Package maintainer
   easier
 Reverse Depends: apt-build apt-listdifferences aptfs arriero
   bzr-builddeb customdeb debci debian-builder debmake debpear (26 more
   omitted)
 Installations reported by Popcon: 13058
 Bug Report URL: http://bugs.debian.org/800413

   ejabberd (#767874), requested 773 days ago
 Description: distributed, fault-tolerant Jabber/XMPP server written
   in Erlang
 Reverse Depends: ejabberd-contrib ejabberd-mod-cron
   ejabberd-mod-log-chat ejabberd-mod-logsession ejabberd-mod-logxml
   ejabberd-mod-message-log ejabberd-mod-muc-log-http
   ejabberd-mod-post-log ejabberd-mod-pottymouth ejabberd-mod-rest (4
   more omitted)
 Installations reported by Popcon: 702
 Bug Report URL: http://bugs.debian.org/767874

   fbcat (#565156), requested 2528 days ago
 Description: framebuffer gra

Re: Getting DEB_HOST_MULTIARCH from maintscripts

[Mathieu Parent (Debian)]

2016-12-16 1:24 GMT+01:00 Christian Seiler :
> On 12/15/2016 10:50 PM, Mathieu Parent (Debian) wrote:
>> I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to
>> create the appropriate symlink with update-alternatives.
>>
>> What is the best way to do this?
>
> Generate them from .in files at the appropriate time, resolving
> the variable manually. See for example:
>
> https://sources.debian.net/src/dietlibc/0.34~cvs20160606-3/debian/rules/#L107-L110
> https://sources.debian.net/src/dietlibc/0.34%7Ecvs20160606-3/debian/dietlibc-dev.postinst.in/

Thanks.

This is what I've done:

https://anonscm.debian.org/cgit/pkg-samba/cifs-utils.git/commit/?id=b0fa211e28982d471a988a7f91df32934da64f98

NB: I was a bit confused that dh-exec was not called for maintscript.

Regards
-- 
Mathieu Parent

Re: Getting DEB_HOST_MULTIARCH from maintscripts

[Christian Seiler]

On 12/16/2016 05:03 AM, Mathieu Parent (Debian) wrote:
> 2016-12-16 1:24 GMT+01:00 Christian Seiler :
>> On 12/15/2016 10:50 PM, Mathieu Parent (Debian) wrote:
>>> I need to have access to $DEB_HOST_MULTIARCH in prerm and postinst to
>>> create the appropriate symlink with update-alternatives.
>>>
>>> What is the best way to do this?
>>
>> Generate them from .in files at the appropriate time, resolving
>> the variable manually. See for example:
>>
>> https://sources.debian.net/src/dietlibc/0.34~cvs20160606-3/debian/rules/#L107-L110
>> https://sources.debian.net/src/dietlibc/0.34%7Ecvs20160606-3/debian/dietlibc-dev.postinst.in/
> 
> Thanks.
> 
> This is what I've done:
> 
> https://anonscm.debian.org/cgit/pkg-samba/cifs-utils.git/commit/?id=b0fa211e28982d471a988a7f91df32934da64f98

Small side note: in your case (single Arch: any package) I don't think
it's necessary to split -arch and -indep override targets (I only do
that in dietlibc because it also builds a Arch: all -doc package where
I don't want to run the full build), and you could just use a simple
override_dh_auto_install: and override_dh_auto_clean:. Doesn't really
hurt either, but makes debian/rules more complicated than necessary in
your case.

> NB: I was a bit confused that dh-exec was not called for maintscript.

What do you mean? Whenever I use dh-exec it's either a) for renaming
files in debian/*.install or b) for having substvars available in
debian/*.install. Ah, now I see, you thought that it might be able to
replace substvars in postinst... I don't believe that'll work, since
postinst isn't a regular debhelper conffile, but instead always has a
shebang - so debhelper will never try to execute it - in contrast to
things like debian/*.install, which by default are not executable, so
debhelper can distinguish between the "simple file" and "script that
produces the actual contents of that file" - it couldn't do that for
things that are supposed to be scripts.

Regards,
Christian