Re: How to craft a watch file if upstream has directory layout major_version/minor_versions

[Paul Wise]

On Mon, Nov 14, 2016 at 9:10 PM, Andreas Tille wrote:

> I wonder how to write d/watch to catch the latest version for
> libsis-jhdf5-java which is in a directory hierarchy[1].  Currently the
> last version is 14.12.6 - but if the major version changes the directory
> changes as well.  Any hint how to safely get the latest version?

No idea how to get the tarball, but this works for the version:

version=3
http://svnsis.ethz.ch/repos/cisd/jhdf5/tags/release/(\d+\.\d+\.x)/(\d+\.\d+\.\d+).

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: remove a git repository

[Herbert Fortes]

On 14-11-2016 17:45, Sean Whitton wrote:

Hello Herbert,

On Mon, Nov 14, 2016 at 04:05:42PM -0200, Herbert Fortes wrote:

I can not edit .git/config that's the problem. I tried. I think
because I am using a guest account.


I doubt it is this.  Who owns the repo?  You could just ask them to do
it.



I am the maintainer of the package. The repo
is on collab-maint.



Regards,
Herbert

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Gianfranco Costamagna]

Hi,

>No, it's fine. I am still not 100% sure what happened here though, could you 
>explain?  :)



dget -u mentors.dsc

dpkg-buildpackage -S -d
dput ftp-master ../hylafax_*source.changes

not sure what I can explain, maybe I can just say that we can exclude:
1) the fact that another upload was already in deferred (AFAIK dak checks the 
same version,
but you can upload in deferred many lower or higher versions)
2) some sort of problem with that particular package

lets see what can be a problem
1) you have some issues with your key (I would exclude this, because you 
already uploaded something else)
2) you uploaded something different than me:
I did a source upload, you did an amd64 one.
You have that buildinfo file, maybe dak is not handling it correctly?
https://ftp-master.debian.org/deferred/

if you want to debug it further I can dcut it and let you try another time, or 
do a source only upload.

otherwise in 15 hours it will reach unstable.

G.

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Chris Lamb]

No, it's fine. I am still not 100% sure what happened here though, could you 
explain?  :)

—lamby 

Gianfranco Costamagna wrote:

> Hi Chris,
> 
>
> 
> >lets see my test :)
> 
> it seems to have worked, let me know if I have to leave it or
> you want me to cancel it
> (I signed the version on mentors)
> 
> G.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Gianfranco Costamagna]

Hi Chris,



>lets see my test :)

it seems to have worked, let me know if I have to leave it or
you want me to cancel it
(I signed the version on mentors)

G.

Bug#832941: RFS: 4pane (debian: to exclusive)

[David Hart]

Dear Sean,

>> >I'd recommend including the upstream code in the git repository, too.
>> >But what you've done is fine -- thanks!
>> 
>> I've now added that too.
>
>I think you misunderstood what I was suggesting.
I'm certain I did ;)

>You've committed the
>tarball to git, but I meant adding the unpacked upstream source.
>
>Unfortunately, your change means that I can't build your package from
>the git repository, so it's hard for me to continue my review.  Please
>consider using gbp-import-dsc(1), or reverting to only having debian/ in
>git if you prefer.

For simplicity, I've just removed the tarball. It can always be done properly
in the future when I understand better what is required.

>Also, the Vcs-* fields still point to the upstream source, not the
>packaging repository.

Does this need to be fixed before you can use the repo. If so, what should I
enter there?
Vcs-Git: https://github.com/dghart/4pane-debian-dir -b master
Vcs-browser: https://github.com/dghart/4pane-debian-dir/tree/master
or something different?

Regards,

David Hart

Re: remove a git repository

[Sean Whitton]

Hello Herbert,

On Mon, Nov 14, 2016 at 04:05:42PM -0200, Herbert Fortes wrote:
> I can not edit .git/config that's the problem. I tried. I think
> because I am using a guest account.

I doubt it is this.  Who owns the repo?  You could just ask them to do
it.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Gianfranco Costamagna]

Hi,

>  No files to delete



dput -e 1 ftp-master ../hylafax_6.0.6-7_source.changes 
Uploading hylafax_6.0.6-7.dsc
Uploading hylafax_6.0.6-7.debian.tar.xz
Uploading hylafax_6.0.6-7_source.changes

lets see my test :)

G.

Re: remove a git repository

[Herbert Fortes]

On 14-11-2016 11:26, Sean Whitton wrote:
> Hello Herbert,
> 
> On Mon, Nov 14, 2016 at 10:32:28AM -0200, Herbert Fortes wrote:
>> I did a mess on gthumb repository and I tried to
>> fix it. What I want to do is a kind  of roll back 
>> because I jumped one Debian revision.
> 
> You should never rewrite published branch history.  What if someone else
> cloned it?  Rewriting tags is much less harmful, though.
> 
>> Before start the fix process I did a backup. :)
>> BACKUP_gthumb.git[0] and gthumb.git[1] but I can 
>> not use it. I do not have the rights to re-write
>> the gthumb.git.
> 
> You can SSH to alioth and edit .git/config to allow you to force-push,
> if you're really sure you want to do that.
> 

I can not edit .git/config that's the problem. I tried. I think
because I am using a guest account.

I will see how to upgrade the status.

Thanks Sean and Adam Borowski.



Regards,
Herbert

Re: remove a git repository

[Adam Borowski]

On Mon, Nov 14, 2016 at 10:32:28AM -0200, Herbert Fortes wrote:
> I did a mess on gthumb repository and I tried to
> fix it. What I want to do is a kind  of roll back 
> because I jumped one Debian revision.
> 
> Before start the fix process I did a backup. :)
> BACKUP_gthumb.git[0] and gthumb.git[1] but I can 
> not use it. I do not have the rights to re-write
> the gthumb.git.

If you have the rights to delete a branch, push -f can be simulated with a
delete + push.  Whether this is the right thing to do is another matter.
 
> What do I do ?

Generally, git repositories shouldn't ever be force-pushed if there's a
non-negligible likelihood of someone having pulled from your branch, which
usually translates to public-vs-private repositories.

However, in this case it's probably just you using that repository for now,
so force-pushing might be reasonable if the alternative is broken history.

> If I should leave the way it is now, how to remove the backup ?

I don't know; I'd recommend using branches for backups in the future -- they
take nearly no space (as opposed to two full copies of the repository),
allow easy cherry-picks and rebases, etc.


Meow!
-- 
A true bird-watcher waves his tail while doing so.

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Chris Lamb]

Gianfranco Costamagna wrote:

> I would do this to fix:
> $ dcut ftp-master rm --searchdirs -f "hylafax*"
> # wait for dcut

  Log of processing your commands file 
/dcut.Chris_Lamb__lamby_debian_org_.1479120511.22075.commands:

  rm --searchdirs --searchdirs -f hylafax*
  -f did not match anything
  hylafax* did not match anything
  No files to delete

Alas...


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Re: remove a git repository

[Sean Whitton]

Hello Herbert,

On Mon, Nov 14, 2016 at 10:32:28AM -0200, Herbert Fortes wrote:
> I did a mess on gthumb repository and I tried to
> fix it. What I want to do is a kind  of roll back 
> because I jumped one Debian revision.

You should never rewrite published branch history.  What if someone else
cloned it?  Rewriting tags is much less harmful, though.

> Before start the fix process I did a backup. :)
> BACKUP_gthumb.git[0] and gthumb.git[1] but I can 
> not use it. I do not have the rights to re-write
> the gthumb.git.

You can SSH to alioth and edit .git/config to allow you to force-push,
if you're really sure you want to do that.

-- 
Sean Whitton

How to craft a watch file if upstream has directory layout major_version/minor_versions

[Andreas Tille]

Hi,

I wonder how to write d/watch to catch the latest version for
libsis-jhdf5-java which is in a directory hierarchy[1].  Currently the
last version is 14.12.6 - but if the major version changes the directory
changes as well.  Any hint how to safely get the latest version?

Kind regards

  Andreas.


[1] http://svnsis.ethz.ch/repos/cisd/jhdf5/tags/release/14.12.x/

-- 
http://fam-tille.de

remove a git repository

[Herbert Fortes]

Hi,

I did a mess on gthumb repository and I tried to
fix it. What I want to do is a kind  of roll back 
because I jumped one Debian revision.

Right now the 'Tag' section is ok and if you
click on 'Branch' links everything seems ok too. 
But the process to fix the mess was not 100% 
correct as can be seen on 'Age' section. I would 
like to start again.

Before start the fix process I did a backup. :)
BACKUP_gthumb.git[0] and gthumb.git[1] but I can 
not use it. I do not have the rights to re-write
the gthumb.git.

[0] - https://anonscm.debian.org/cgit/collab-maint/BACKUP_gthumb.git
[1] - https://anonscm.debian.org/cgit/collab-maint/gthumb.git

What do I do ? If I should leave the way it is now,
how to remove the backup ?



Regards,
Herbert

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Gianfranco Costamagna]

Hi,

>Oh, it's almost certainly because we already have a package in

>DELAYED/X from me. I wonder which will end up in the archive.

Nov 12 09:55:43 processing /hylafax_6.0.6-7_amd64.changes
Nov 12 09:55:43 /hylafax_6.0.6-7_amd64.changes is already present on target 
host:
Nov 12 09:55:43 5-day/hylafax_6.0.6.orig.tar.gz
Nov 12 09:55:43 Job hylafax_6.0.6-7_amd64.changes removed.
Nov 12 13:48:07 hylafax_6.0.6-6.1_amd64.changes moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax_6.0.6-6.1.dsc moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax_6.0.6.orig.tar.gz moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax_6.0.6-6.1.debian.tar.xz moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax-client-dbg_6.0.6-6.1_amd64.deb moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax-client_6.0.6-6.1_amd64.deb moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax-server-dbg_6.0.6-6.1_amd64.deb moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax-server_6.0.6-6.1_amd64.deb moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 13:48:07 hylafax_6.0.6-6.1_2016T132927z-48b86b8b.buildinfo moved to 
/srv/upload.debian.org/DEFERRED/4-day
Nov 12 23:09:39 processing /hylafax_6.0.6-7_amd64.changes
Nov 12 23:09:39 /hylafax_6.0.6-7_amd64.changes is already present on target 
host:
Nov 12 23:09:39 4-day/hylafax_6.0.6.orig.tar.gz
Nov 12 23:09:39 Job hylafax_6.0.6-7_amd64.changes removed.



somewhere seems that you uploaded twice the same 
hylafax_6.0.6-7_amd64.changes, and dak removed it

I would do this to fix:
$ dcut ftp-master rm --searchdirs -f "hylafax*"
# wait for dcut

$ dput ftp-master hylafax_6.0.6-7_source.changes

(yeah, I like source only uploads :p )

otherwise, please let me know, and I'll try to see if it reaches unstable :)

thanks!

G.

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Andrew Shadura]

On 11 November 2016 at 23:56, Joachim Wiedorn  wrote:
> Package: sponsorship-requests
> Severity: important
>
> Dear mentors,
>
> I am looking for a sponsor for my package "hylafax"
>
>  * Package name: hylafax
>Version : 3:6.0.6-7
>Upstream Author : Sam Leffler and Silicon Graphics Inc.
>  * URL : http://www.hylafax.org
>  * License : MIT / HylaFAX variant
>Section : comm

I wonder how many people are still sending and receiving faxes. And
how many people in fact still have and use a fax modem :)

-- 
Cheers,
  Andrew

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Chris Lamb]

Chris Lamb wrote:

> Well, I've successfully uploaded ~10 packages in the last few days
> so I've no idea what is special about hylafax... :/

Oh, it's almost certainly because we already have a package in
DELAYED/X from me. I wonder which will end up in the archive.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#844035: RFS: hylafax/3:6.0.6-7 [RC] -- Flexible client/server fax software

[Chris Lamb]

Joachim Wiedorn wrote:

> It seems the address of the ftp-master changed in 
> the last time. I read mails of 'debian-announce'
> about that:
> 
>   ssh.upload.debian.org
>   ftp.upload.debian.org

Well, I've successfully uploaded ~10 packages in the last few days
so I've no idea what is special about hylafax... :/



Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#832704: RFS: nixnote2/2.0~beta10+dfsg-1 [ITP] -- Open Source Evernote client

[Boyuan Yang]

在 2016年11月13日星期日 CST 下午2:43:47，Sean Whitton 写道：
> plus some other minor comments below.  The blocker:
> 
> hephaestus ~ % nixnote2
> QSqlDatabase: QSQLITE driver not loaded
> QSqlDatabase: available drivers: QMYSQL3 QMYSQL
> ERROR 2016-11-13 14:38:58.946 ( sql/databaseconnection.cpp @ 44 ) Error
> opening database:  QSqlError(-1, "Driver not loaded", "Driver not loaded")
> 
> Any ideas?

A missing dependency libqt4-sql-sqlite caused this problem. It seems that
the automatic dh_shlibdeps failed to list it inside Depends list (it only 
listed libqt4-sql). A explicit dependency was added the latest commit.

> > * Some minor modification to package description in debian/control.
> 
> 1. There's a grammatical error in your change: s/provide/provides/.
> 
> 2. The sentence doesn't really make sense.  Maybe s/and/to/ is what you
> meant?

Fixed.

> > * Copyright information update for beta10 version.
> 
> 3. Are you installing the plugins at present, 'hunspell' and 'webcam'?
> Contents of package suggests not.  Upstream seems to think they belong
> in separate binary packages.  What do you think about that?

Added debian/README.Debian file to explain the situation. The plugin structure
won't support Qt5, plus upstream placed the plugin inside /usr/share, which is 
not acceptable. The building system (CMake) for plugins is not in standard 
status, too. My choice is not to install the plugins and wait until upstream 
provides with a better solution.

Patching may be possible but that would be painful.

> > Blhc on debomatic reported some missing CXXFLAGS (-fPIE). However
> > since new gcc has already set -fPIE by default since 6.2.0-7, this
> > should be harmless.
> 
> Yes.  Lintian would be complaining if it wasn't being passed.

Again this needs patching, so I would choose to look into it later until some 
real problem comes up.

> 4. I'm curious why you nuked gbp.conf.  Entirely up to you, of course.

I found git-buildpackage not reading the "debian/gbp.conf" at all unless I 
list it explicitly inside environment variable, which is different from words 
written in man 5 gbp.conf. Command line arguments should be a better choice 
for me.

> 5. Your Forwarded: headers got eaten at some point.  Would be nice to
> restore them.

Well it is a problem hiding in gbp pq, which will eat non-mandatory headers 
when exporting patches because git commit does not preserve those information. 
Maybe I fill file a bug report (feature request?) later.

> 6. You could install the new screenshot.png to
> /usr/share/doc/nixnote2/examples (see dh_installexamples(1)).

Done.


Git repository updated on
https://anonscm.debian.org/git/collab-maint/nixnote2.git
Package on debian-mentors updated:
https://mentors.debian.net/package/nixnote2
Package built on debomatic:
http://debomatic-amd64.debian.net/distribution#unstable/
nixnote2/2.0~beta10+dfsg-1/


Sincerely,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part.