reportbug will not run as root non-interactively

2019-03-10 Thread Tong Sun
Hi,

I want to reportbug from docker, but am getting:

  reportbug will not run as root non-interactively.

I.e.,

  % reportbug --template -S normal sbuild-debian-developer-setup
  Warning: no reportbug configuration found.  Proceeding in novice mode.
  reportbug will not run as root non-interactively.

Any suggestions?

I reportbug from docker because I'm using Ubuntu and the only Debian I
have is in docker.

thanks



Re: About Debian Freeze

2019-03-10 Thread Tong Sun
On Sun, Mar 10, 2019 at 5:04 PM Andrey Rahmatullin wrote:
>
> On Sun, Mar 10, 2019 at 04:29:19PM -0400, Tong Sun wrote:
> > How long does it normally take for a Full-freeze to turn into a release?
> Several months.
>
> > The https://release.debian.org/buster/freeze_policy.html only list to
> > Full-freeze, so I'm wondering when it is good to do packaging again.
> > thx.
> You can upload to experimental.

Thanks.

Sorry for the double posting -- I *thought* I was using the wrong from
address when it didn't show up on mlist archive after several minutes.



Re: About Debian Freeze

2019-03-10 Thread Andrey Rahmatullin
On Sun, Mar 10, 2019 at 04:29:19PM -0400, Tong Sun wrote:
> How long does it normally take for a Full-freeze to turn into a release?
Several months.

> The https://release.debian.org/buster/freeze_policy.html only list to
> Full-freeze, so I'm wondering when it is good to do packaging again.
> thx.
You can upload to experimental.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


About Debian Freeze

2019-03-10 Thread Tong Sun
How long does it normally take for a Full-freeze to turn into a release?

The https://release.debian.org/buster/freeze_policy.html only list to
Full-freeze, so I'm wondering when it is good to do packaging again.
thx.



About Debian Freeze

2019-03-10 Thread Tong Sun
How long does it normally take for a Full-freeze to turn into a release?

The https://release.debian.org/buster/freeze_policy.html only list to
Full-freeze, so I'm wondering when it is good to do packaging again.
thx.



Bug#923180: Please sponsor my game bug=923180

2019-03-10 Thread Markus Koschany
Hello Pedro,

Am 08.03.19 um 02:49 schrieb Pedro Pena:
> Hello Markus,
> 
> I found an online appstream generator that helped me create the appstream 
> file.
> 
> I built the package without any errors. and just uploaded it.
> 
> I installed the package hoping to see the appstream data rendered in 
> the package manager but I guess it only displays info from the
> control file when it isn't an official debian package.
> 
> Please let me know if I'm  missing anything.

I think we are very close now to upload infinitetux. I have attached two
patches. The first one will change the installation directory to
/usr/share/games. The other one will use the --release flag instead of
-source and -target. This prevents an error when using OpenJDK 8 to run
the game.

Please remove the executable bit from all java and resource files. chmod
a-x. Currently the game creates an infinitetux-data directory in the
user's home directory where it saves tiles.dat. This directory should be
hidden and renamed to .infinitetux. You could also consider to follow
the XDG specification.

https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

Last but not least, please add some VCS links to debian/control and
change the maintainer field to

Debian Games Team 

and add yourself as Uploader.

Uploaders: qbancoffee 

This way it is easier for others to make changes to the package and keep
it in good shape.

Otherwise the rest looks good to me. I will import the next revision
into our Git repository. You can ask for access here:

https://salsa.debian.org/games-team

Cheers,

Markus
From 691369953345d31a88636c2f0f2aabdf0bb126f3 Mon Sep 17 00:00:00 2001
From: Markus Koschany 
Date: Sun, 10 Mar 2019 15:22:56 +0100
Subject: [PATCH 1/2] Install infinitetux.jar into /usr/share/games.

---
 debian/infinitetux.links | 2 +-
 debian/install   | 2 +-
 debian/rules | 5 +++--
 3 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/debian/infinitetux.links b/debian/infinitetux.links
index 7c61489..6a78453 100644
--- a/debian/infinitetux.links
+++ b/debian/infinitetux.links
@@ -1 +1 @@
-/usr/share/infinitetux/infinitetux.jar /usr/games/infinitetux
+/usr/share/games/infinitetux/infinitetux.jar /usr/games/infinitetux
diff --git a/debian/install b/debian/install
index b317498..2f17a48 100644
--- a/debian/install
+++ b/debian/install
@@ -1,4 +1,4 @@
-../infinitetux.jar usr/share/infinitetux
+infinitetux.jar usr/share/games/infinitetux
 infinitetux.appdata.xml usr/share/metainfo
 infinitetux.desktop usr/share/applications
 infinitetux.png usr/share/icons/hicolor/256x256/apps
diff --git a/debian/rules b/debian/rules
index 091190d..7a62756 100755
--- a/debian/rules
+++ b/debian/rules
@@ -5,8 +5,9 @@
 override_dh_auto_build:
 	JAVA_HOME=/usr/lib/jvm/default-java
 	jh_build --no-javadoc --javacopts="-source 1.8 -target 1.8" \
-	--main=com.mojang.mario.FullScreenFrameLauncher ../infinitetux.jar src
+	--main=com.mojang.mario.FullScreenFrameLauncher infinitetux.jar src
 
 override_dh_install:
-	jar uf ../infinitetux.jar -C src/main/resources .
+	jar uf infinitetux.jar -C src/main/resources .
 	dh_install
+
-- 
2.20.1

From 824bce75f919d57e0019e3e842074583caaeeecc Mon Sep 17 00:00:00 2001
From: Markus Koschany 
Date: Sun, 10 Mar 2019 15:29:58 +0100
Subject: [PATCH 2/2] Use -release 8 option.

---
 debian/rules | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 7a62756..90c82a9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,7 +4,7 @@
 
 override_dh_auto_build:
 	JAVA_HOME=/usr/lib/jvm/default-java
-	jh_build --no-javadoc --javacopts="-source 1.8 -target 1.8" \
+	jh_build --no-javadoc --javacopts="--release 8" \
 	--main=com.mojang.mario.FullScreenFrameLauncher infinitetux.jar src
 
 override_dh_install:
-- 
2.20.1



signature.asc
Description: OpenPGP digital signature


Bug#923405: marked as done (RFS: pandoc-plantuml-filter/0.1.1-1 [ITP])

2019-03-10 Thread Debian Bug Tracking System
Your message dated Sun, 10 Mar 2019 13:25:10 +0100
with message-id <43d48484-1c02-4465-8097-320a873cb...@hanno-stock.de>
and subject line Package is now in the NEW queue 
has caused the Debian Bug report #923405,
regarding RFS: pandoc-plantuml-filter/0.1.1-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
923405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923405
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "pandoc-plantuml-filter"

 * Package name: pandoc-plantuml-filter
   Version : 0.1.1-1
   Upstream Author : Timo Furrer
 * URL : https://github.com/timofurrer/pandoc-plantuml-filter
 * License : MIT
   Section : misc

  It builds those binary packages:

pandoc-plantuml-filter - Pandoc filter: converts PlantUML code blocks to 
PlantUML images

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/pandoc-plantuml-filter

  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pandoc-plantuml-filter/pandoc-plantuml-filter_0.1.1-1.dsc

  The package is maintained in git under 
https://salsa.debian.org/python-team/applications/pandoc-plantuml-filter
  and will be maintained in the Python Application Packagin Team (also set as 
maintainer).

  More information about pandoc-plantuml-filter can be obtained from 
https://github.com/timofurrer/pandoc-plantuml-filter.

  Regards,
   Hanno Stock
--- End Message ---
--- Begin Message ---
Package is now in the NEW queue --- End Message ---